| commit | f04b63959c6b09266c86b4ef5e7413922f45661b | [log] [tgz] |
|---|---|---|
| author | Scott Baker <smbaker@gmail.com> | Fri Mar 20 08:29:46 2020 -0700 |
| committer | Scott Baker <smbaker@gmail.com> | Mon Mar 23 08:27:51 2020 -0700 |
| tree | 1bbc5ace40acb99b2bf86d713386bb5a53643926 | |
| parent | 72cfd3690bf36a40f05b880a0b7b38654ef6ee52 [diff] |
SEBA-964 Remove hardcoded hostnames and replace with config system; Move code to canonical golang directory structure; Update licensing; Update README.md Change-Id: I4b00301eef4e87e81fc731a5af20cf7b7ed68678
To build and publish the docker image, issue the following commands:
make docker-build make docker-push
You may preface the above commands with DOCKER_REPOSITORY= and/or DOCKER_TAG= to specify a custom docker repository and/or tag.
Nem-ondemand-proxy is deployed as a container and may be deployed using either docker-compose or kubernetes. Kubernetes is the recommended method and may be done by executing the following command:
cd kubernetes kubectl apply -f nem-ondemand-proxy.yaml
To teardown the proxy, use the following:
cd kubernetes kubectl delete -f nem-ondemand-proxy.yaml
In addition to deploying the container, you may also want to setup a Kubernetes port-forward. Scripts in the kubernetes directory are provided as an example.
You will need to know the device id of the ONU you wish to query. This may be done with voltctl device list.
There is no dedicated client yet, and it is recommended to use grpcurl. For example,
# perform on-demand query on device with id 2910b26bbb29521d93fab21b grpcurl -plaintext -d '{"id": "2910b26bbb29521d93fab21b"}' localhost:50052 on_demand_api.NemService/OmciTest