juju-solutions / bundle-observable-swarm Goto Github PK

Suggest to expose services such as Swarm and Kibana, or at a minimum remind users they need to expose the service and then instructions on how to access the service.

I think we would rather error on folks having a good first user experience than security concerns. We should of course note in the readme which services are exposed by default and how to remove external access.

I did not know I needed to run an action to load the Kibana dashboard or what Kibana menus to traverse. This bug is to make those instructions explicit to users. Specifically how to load the Kibana dashboard via the action and then what menus to traverse to see the data.

The readme indicates to run
docker status

However that is not a valid Docker command. To get status I suggest:
docker stats
or
docker ps -a

When I visit https://jujucharms.com/u/containers/observable-swarm/bundle/1 and click on "Submit a bug" the link goes to https://github.com/juju-solutions/layer-swarm/issues not here.

swarm/1 was the leader and that is where I found the swarm_credentials.tar file.

We could either determine who is the leader with something like

juju run --service swarm "is-leader" --format=yaml | grep -A 1 True | awk '{ print $2 }'

but in talking with @chuckbutler the plan is to put the credential file on all units.