How to stop Openstack services after conjure-up installation
I think this a noob question but I've successfully installed openstack using conjure-up using nova LXD. However, I want to stop all the services temporarily preferably using conjure-up. Is there a way to do it?
Attaching the juju status.
nikhil@nikhil-desktop:~$ juju status
Model Controller Cloud/Region Version
conjure-up-openstack-novalxd-308 conjure-up-localhost-916 localhost/localhost 2.1.1
App Version Status Scale Charm Store Rev OS Notes
ceph-mon 10.2.5 active 3 ceph-mon jujucharms 9 ubuntu
ceph-osd 10.2.5 active 3 ceph-osd jujucharms 241 ubuntu
ceph-radosgw 10.2.5 active 1 ceph-radosgw jujucharms 247 ubuntu
glance 12.0.0 active 1 glance jujucharms 256 ubuntu
keystone 9.2.0 active 1 keystone jujucharms 264 ubuntu
lxd 2.0.9 active 1 lxd jujucharms 9 ubuntu
mysql 5.6.21-25.8 active 1 percona-cluster jujucharms 250 ubuntu
neutron-api 8.3.0 active 1 neutron-api jujucharms 249 ubuntu
neutron-gateway 8.3.0 active 1 neutron-gateway jujucharms 234 ubuntu
neutron-openvswitch 8.3.0 active 1 neutron-openvswitch jujucharms 240 ubuntu
nova-cloud-controller 13.1.2 active 1 nova-cloud-controller jujucharms 294 ubuntu
nova-compute 13.1.2 active 1 nova-compute jujucharms 265 ubuntu
ntp waiting 0 ntp jujucharms 17 ubuntu
openstack-dashboard 9.1.0 active 1 openstack-dashboard jujucharms 245 ubuntu exposed
rabbitmq-server 3.5.7 active 1 rabbitmq-server jujucharms 61 ubuntu
Unit Workload Agent Machine Public address Ports Message
ceph-mon/0* active idle 0 10.252.232.10 Unit is ready and clustered
ceph-mon/1 active idle 1 10.252.232.76 Unit is ready and clustered
ceph-mon/2 active idle 2 10.252.232.214 Unit is ready and clustered
ceph-osd/0 active idle 3 10.252.232.196 Unit is ready (1 OSD)
ceph-osd/1* active idle 4 10.252.232.160 Unit is ready (1 OSD)
ceph-osd/2 active idle 5 10.252.232.56 Unit is ready (1 OSD)
ceph-radosgw/0* active idle 6 10.252.232.178 80/tcp Unit is ready
glance/0* active idle 7 10.252.232.161 9292/tcp Unit is ready
keystone/0* active idle 8 10.252.232.100 5000/tcp Unit is ready
mysql/0* active idle 9 10.252.232.158 Unit is ready
neutron-api/0* active idle 10 10.252.232.242 9696/tcp Unit is ready
neutron-gateway/0* active idle 11 10.252.232.171 Unit is ready
nova-cloud-controller/0* active idle 12 10.252.232.243 8774/tcp Unit is ready
nova-compute/0* active idle 13 10.252.232.205 Unit is ready
lxd/0* active executing 10.252.232.205 (config-changed) Unit is ready
neutron-openvswitch/0* active idle 10.252.232.205 Unit is ready
openstack-dashboard/0* active idle 14 10.252.232.228 80/tcp,443/tcp Unit is ready
rabbitmq-server/0* active idle 15 10.252.232.212 5672/tcp Unit is ready
Machine State DNS Inst id Series AZ
0 started 10.252.232.10 juju-9b743a-0 xenial
1 started 10.252.232.76 juju-9b743a-1 xenial
2 started 10.252.232.214 juju-9b743a-2 xenial
3 started 10.252.232.196 juju-9b743a-3 xenial
4 started 10.252.232.160 juju-9b743a-4 xenial
5 started 10.252.232.56 juju-9b743a-5 xenial
6 started 10.252.232.178 juju-9b743a-6 xenial
7 started 10.252.232.161 juju-9b743a-7 xenial
8 started 10.252.232.100 juju-9b743a-8 xenial
9 started 10.252.232.158 juju-9b743a-9 xenial
10 started 10.252.232.242 juju-9b743a-10 xenial
11 started 10.252.232.171 juju-9b743a-11 xenial
12 started 10.252.232.243 juju-9b743a-12 xenial
13 started 10.252.232.205 juju-9b743a-13 xenial
14 started 10.252.232.228 juju-9b743a-14 xenial
15 started 10.252.232.212 juju-9b743a-15 xenial
Relation Provides Consumes Type
mon ceph-mon ceph-mon peer
mon ceph-mon ceph-osd regular
mon ceph-mon ceph-radosgw regular
ceph ceph-mon glance regular
ceph ceph-mon nova-compute regular
cluster ceph-radosgw ceph-radosgw peer
identity-service ceph-radosgw keystone regular
cluster glance glance peer
identity-service glance keystone regular
shared-db glance mysql regular
image-service glance nova-cloud-controller regular
image-service glance nova-compute regular
amqp glance rabbitmq-server regular
cluster keystone keystone peer
shared-db keystone mysql regular
identity-service keystone neutron-api regular
identity-service keystone nova-cloud-controller regular
identity-service keystone openstack-dashboard regular
lxd-migration lxd lxd peer
lxd lxd nova-compute regular
cluster mysql mysql peer
shared-db mysql neutron-api regular
shared-db mysql nova-cloud-controller regular
cluster neutron-api neutron-api peer
neutron-plugin-api neutron-api neutron-gateway regular
neutron-plugin-api neutron-api neutron-openvswitch regular
neutron-api neutron-api nova-cloud-controller regular
amqp neutron-api rabbitmq-server regular
cluster neutron-gateway neutron-gateway peer
quantum-network-service neutron-gateway nova-cloud-controller regular
amqp neutron-gateway rabbitmq-server regular
neutron-plugin neutron-openvswitch nova-compute regular
amqp neutron-openvswitch rabbitmq-server regular
cluster nova-cloud-controller nova-cloud-controller peer
cloud-compute nova-cloud-controller nova-compute regular
amqp nova-cloud-controller rabbitmq-server regular
lxd nova-compute lxd subordinate
neutron-plugin nova-compute neutron-openvswitch subordinate
compute-peer nova-compute nova-compute peer
amqp nova-compute rabbitmq-server regular
ntp-peers ntp ntp peer
cluster openstack-dashboard openstack-dashboard peer
cluster rabbitmq-server rabbitmq-server peer
So there isn't a way to stop/suspend services via conjure-up. You'd need to use lxc stop <instance> and lxc list
You can uninstall with conjure-down
I think this is an interesting idea and so leave this open as a feature enhancement
any updates? thanks.
This did not make this cycle's feature work, we will look into adding it in our next 6 month development cycle (starting around sept 1)
What if we "systemctl stop/start lxc.service" ? This should prevent containers starting at boot time thus lower the impact on the laptop when one does not need Openstack running.
I was wrong, the lxc service is masked. Instead you can control the lxc profiles like so :
- $juju controllers
- $lxc profile edit MODEL Just change the boot.autostart: "true" to "false" and you're home free
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.