Permalink
Switch branches/tags
Clueso-Demo DOC/addAntoraSupport DOC/changelog DOC/moveOrbitEnable FT/addWasabiSupport FT/aggregated_doc ZENKO-125-testing add-ci-mocks bennett/tmp/improvement/doc bugfix/EVE-1008-flaky-docker-builds bugfix/ZENKO-653-offline-tests bugfix/ZENKO-697-invalid-non-version-CRR bugfix/ZENKO-860-runE2E bugfix/ZENKO-915/one-to-many-flakiness bugfix/ZENKO-968-exposeNoProxyInCloudserverChart bugfix/ZENKO-1004-flaky-1toM-e2e-tests bugfix/ZENKO-1004/write-MD5-mismatch-file-contents bugfix/ZENKO-1013/useBackbeatApiMetrics bugfix/ZENKO-1022-enable-test bugfix/ZENKO-1168-initialDelayForLivenessProbes bugfix/ZENKO-1312-reduceNumberOfBackbeatProcessorPods bugfix/ZENKO-1328-Fix-nightly-cosbench bugfix/ZENKO-1375-update-nightly-target-branches bugfix/test-verbose demo/manual-deploy development/0.9 development/1.0 development/1.1 doc/ZENKO-655 doc/ZENKO-870 doc/ZENKO-921 doc/ZENKO-927 doc/ZENKO-1057 docker-image feature/S3C-1171-listv2-e2e feature/ZENKO-472-integrateCosbench feature/ZENKO-558/Ref_Guide_initial_merge feature/ZENKO-704/crr-object-monitor feature/ZENKO-776-debugging-tests feature/ZENKO-776-functional-test-stage feature/ZENKO-799-locquota-tests feature/ZENKO-860-runZenkoTests feature/ZENKO-1217-using-doc feature/ZENKO-1329-Nightly-s3-fuzzer feature/ZENKO-1358-add-cosmos-operator feature/ZENKO-1361-Add-Azure-mock feature/cosmos-chart feature/update-docker-stack-images fix-kubernetes-link fix/deployment ft/ZENKO-458-utapi-helm-chart ft/ZENKO-475 ft/ZENKO-913 ft/clueso-cleanup ft/clueso-meld ft/e2e-pause-resume-tests ft/k8s-helm-grafana ft/k8s-helm-test ft/kub-poc ft/mdmongo ft/swarm-to-kube-port ft/test_framework ft/useMongo3.6 gh-pages improvement/ZENKO-694-zenko-nfs-readme improvement/ZENKO-882/add-JS-and-MD-linting improvement/ZENKO-998-ci-upgrades improvement/ZENKO-1002-remove-mk8s-instructions improvement/backbeat-healthchecks improvement/doc-ZENKO-655 improvement/doc-ZENKO-1057 improvement/doc-ZENKO-1177 improvement/doc-ZENKO-1206 improvement/doc-ZENKO-1224 improvement/doc-ZENKO-1293-add-logos improvement/doc-ZENKO-1299-remove-css-junk improvement/doc-ZENKO-1301-fix-RST improvement/test-new-mongo-chart improvement/updateCloudserverImageTag lhs/clueso-cleanup lhs/clueso-meld lhs/clueso master q/1.0 q/1.1 reconcile-docs rf/ZENKO-388-common-backbeat temp/demo-2 test/breaking-changes test/cloudserver-replicas test/crrmetric test/crrmetrics test/ingestion-changes testing-branch-flakiness update-doc w/1.1/bugfix/ZENKO-1168-initialDelayForLivenessProbes
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
146 lines (107 sloc) 5.9 KB

Registering a Zenko Instance on Orbit Management UI

This section of documentation will help you register your Zenko instance on Orbit, for either minikube-based or MetalK8s-based or Docker Swarm-based deployments.

Minikube and MetalK8s (and other Kubernetes-based deployments)

Step 1: go to the Kubernetes dashboard

For minikube:
$ minikube dashboard

A new tab should open in your browser, taking you to the Kubernetes dashboard.

For MetalK8s:
$ kubectl proxy

While the tunnel is up and running, access the dashboard at http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/.

Step 2: finding the Zenko instance ID

Option A: from the CloudServer logs

From the dashboard, click on the cloudserver service, and then on one of the pods running for that service. On the top right menu, click "Logs", and then do a search of "instance ID" - you should find a line in the logs giving you a long string of random characters: this is your instance id, copy it. If you cannot find such a line in the logs, try option B.

Option B: from the Metadata MongoDB cluster

From the dashboard, click on the mongodb-replicaset service, and then on the pod that is mongodb-replicaset-0. For fresh deployments, the pod 0 should be the MongoDB master, and note MongoDB can only be queried from the master pod.

TIP: if the following procedure doesn't work for you, and you get an error like "not master and slaveOk=false", it means the pod inside which you are executing those commands is not the master. In that case, simply use db.isMaster.primary to find the master node, execute the procedure inside that node.

Then hit "Exec", in the top right menu of the dashboard, and use the CLI to query MongoDB as follows

$ mongo
MongoDB shell version v3.4.15
connecting to: mongodb://127.0.0.1:27017
MongoDB server version: 3.4.15
Welcome to the MongoDB shell.
For interactive help, type "help".
For more comprehensive documentation, see
        http://docs.mongodb.org/
Questions? Try the support group
        http://groups.google.com/group/mongodb-user
Server has startup warnings: 
2018-05-25T15:44:08.084+0000 I STORAGE  [initandlisten] 
2018-05-25T15:44:08.084+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2018-05-25T15:44:08.084+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2018-05-25T15:44:08.503+0000 I CONTROL  [initandlisten] 
2018-05-25T15:44:08.503+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2018-05-25T15:44:08.504+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2018-05-25T15:44:08.504+0000 I CONTROL  [initandlisten] ** WARNING: You are running this process as the root user, which is not recommended.
2018-05-25T15:44:08.504+0000 I CONTROL  [initandlisten] 

rs0:PRIMARY> use metadata
switched to db metadata

rs0:PRIMARY> db.PENSIEVE.findOne({_id: "auth/zenko/remote-management-token"})
{
    "_id" : "auth/zenko/remote-management-token",
    "value" : {
        "instanceId" : "abc12345-5689-4f15-b0e6-5a9c17e7ae01",
        "issueDate" : "2018-05-25T15:45:56Z",
        (...)
    }
}

In this json object, you can find your instance ID in the value dictionary.

Step 3: Registering with Orbit

Go to Orbit's homepage, hit "Get Started", and log in with your Google Account (we comply with GDPR regulations).

You will be welcomed by a charming astronaut fox, offering you to take a tour, or to install now. Feel free to take the tour to discover all of Orbit's capabilities, or hit "Install Now" if you can't wait! You will land on this page:

Orbit Setup Page

Hit "Register My Instance"

On this page, put your instance ID in the left box, and choose your instance friendly name in the right box, then simply hit "Submit Now"

Orbit Registration Page

You're all set! Enjoy Orbit and Zenko, and reach out on the forum if you need anything!

Docker Swarm deployments

Step 1: retrieve your instance ID from CloudServer logs

Find your CloudServer frontend service in your zenko stack, and search its logs:

$ docker stack services {{STACK_NAME}} | grep front
3y7vayna97bt        {{STACK_NAME}}_s3-front            replicated          1/1                 zenko/cloudserver:pensieve-3   *:30009->8000/tcp

$ docker service logs {{STACK_NAME}}_s3-front | grep -i instance
{{STACK_NAME}}_s3-front.1.khz73ag06k2k@moby    | {"name":"S3","time":1512424260154,"req_id":"115779d9564e960048a5","level":"info","message":"this deployment's Instance ID is "abc12345-5689-4f15-b0e6-5a9c17e7ae01","hostname":"843d31bf15f0","pid":28}

Step 2: Registering with Orbit

Go to Orbit's homepage, hit "Get Started", and log in with your Google Account (we comply with GDPR regulations).

You will be welcomed by a charming astronaut fox, offering you to take a tour, or to install now. Feel free to take the tour to discover all of Orbit's capabilities, or hit "Install Now" if you can't wait! You will land on this page:

Orbit Setup Page

Hit "Register My Instance"

On this page, put your instance ID in the left box, and choose your instance friendly name in the right box, then simply hit "Submit Now"

Orbit Registration Page

You're all set! Enjoy Orbit and Zenko, and reach out on the forum if you need anything!