Connect to nebula server from another server about nebula-python HOT 3 CLOSED

Dear @herman72,

This error refers to storage-client cannot reach storaged via '127.0.0.1', 9779.

The storage client gets to know the stroaged interface via meta-client instance, and it's assumed(configured out-of-box in like nebula-docker-compose)not exposed outside of the nebula graph cluster(not like the graphd and metad).

If the python application only needs to do nGQL/openCypher queries(not the vertices scanning), we only need the graph-client.

If you indeed need the storage-client, corresponding network configuration should be done to ensure the storaged is accessible from where your python client is running on.

If you would like to first-time quickly try and play with everything(including storage-client) with a docker-compose deployed nebula cluster(not willing to change anything in the compose yaml file), you can try running your client from a container with the same network of the docker-compose like:

assumed the network name is nebula-docker-compose_nebula-net

$ docker run -dit --name ng-python --network nebula-docker-compose_nebula-net ubuntu:latest bash

$ docker exec -it ng-python bash
$ apt update
$ apt install python3 python3-pip
$ pip3 install nebula2-python==2.0.0
python

Thanks!

from nebula-python.

Dear @herman72,

This error refers to storage-client cannot reach storaged via '127.0.0.1', 9779.

The storage client gets to know the stroaged interface via meta-client instance, and it's assumed(configured out-of-box in like nebula-docker-compose)not exposed outside of the nebula graph cluster(not like the graphd and metad).

If the python application only needs to do nGQL/openCypher queries(not the vertices scanning), we only need the graph-client.

If you indeed need the storage-client, corresponding network configuration should be done to ensure the storaged is accessible from where your python client is running on.

If you would like to first-time quickly try and play with everything(including storage-client) with a docker-compose deployed nebula cluster(not willing to change anything in the compose yaml file), you can try running your client from a container with the same network of the docker-compose like:

assumed the network name is nebula-docker-compose_nebula-net

$ docker run -dit --name ng-python --network nebula-docker-compose_nebula-net ubuntu:latest bash

$ docker exec -it ng-python bash
$ apt update
$ apt install python3 python3-pip
$ pip3 install nebula2-python==2.0.0
python

Thanks!

Thanks!

from nebula-python.

thank you, closing it, if you consider it's not yet resolved, please feel free to reopen it, thanks.

from nebula-python.