Extend/Design the "deploy.py" script to be more useful
Bug #1519134 reported by
Angus Salkeld
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-mesos |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
ATM it's sole aim is to write the needed config to zookeeper and post the apps to marathon.
What might a user want to do?
1. deploy
2. view the current zookeeper config (tree and each item)
3. destroy (delete the openstack apps and delete stuff from zookeeper)
4. diagnosis - commands to get at the systems logs and drill down to apps that are failed.
"kolla-mesos whats-wrong"
5. (this can remain TODO for now) update the deployment
6. tweak individual options (like turn on debug in one service)
Some ideas:
kolla-mesos deploy
kolla-mesos update
kolla-mesos destroy
kolla-mesos config show
kolla-mesos config get <item>
kolla-mesos config set <item>
kolla-mesos logs <filtering/depth options> (one might be "kolla-mesos logs --failed-apps")
| Changed in kolla-mesos: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| Changed in kolla-mesos: | |
| importance: | High → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix proposed to kolla-mesos (master) | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix merged to kolla-mesos (master) | #2 |
To post a comment you must log in.
Related fix proposed to branch: master
Review: https:/