Process restart information
Process/Service Function In service patchable Managed by Restart command Patch Restart command Restart dependency Impact(if restarted while in operation) Special handling required
ceilometer-polling Daemon that polls Openstack services and build meters Y PMON /etc/init.d/openstack-ceilometer-polling restart N As batch_polled_samples is set to True, may lose some samples that are in the pollsters memory if the process is restarted exactly when they have just finished polling for samples and are about to publish these samples to RabbitMQ. This is about 10 millisecond window for cpu_source and 0.03 millisecond 1 second window for meter related sources. N
ceilometer-agent-notification Daemon that listens to notifications on message queue, converts them to Events and Samples and applies pipeline actions Y SM sm-restart-safe service ceilometer-agent-notification
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/ceilometer-agent-notification stop
/bin/sh /usr/lib/ocf/resource.d/openstack/ceilometer-agent-notification start
N May lose some samples/events if the process is restarted while they are being transformed or converted. N
ceilometer-collector Daemon that gathers and records event and metering data created by notification and polling agents Y SM sm-restart-safe service ceilometer-collector
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/ceilometer-collector stop
/bin/sh /usr/lib/ocf/resource.d/openstack/ceilometer-collector start
N May lose some samples/events if the process is restarted while they are being persisted in Postgres DB. This is a tiny window especially with recent optimization work (no message signature verification, one single call to create_sample stored proc).
Note: Making sure that child processes and their database connections are released when a parent process is stopped is part of collector functionality. It is not specific to in-service patching.
N
ceilometer-api Service to query and view data recorded by the collector Y SM sm-restart-safe service ceilometer-api
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/ceilometer-api stop
/bin/sh /usr/lib/ocf/resource.d/openstack/ceilometer-api start
N While the service is restarted, horizon or CLI ceilometer request will fail. Horizon request will be re-established automatically in its next polling interval. CLI command needs to be re-issued. N
ceilometer-expirer-active Cron job that purges expired samples and events as well as related meter and resource data Y CRON N/A

To run the expirer manually: /usr/bin/ceilometer-expirer-active
N There is no need to restart after patch. The change will take effect next time the expirer cron job is run.
Unless there are new features specifically planned for expirer, this code is very stable.
N
haproxy A Proxy service that is responsible for forwarding external REST API requests to Open Stack and Titanium Cloud services that listening on the internal interfaces. Y SM sm-restart-safe service haproxy
which runs the following:

/bin/sh /etc/init.d/haproxy stop
/bin/sh /etc/init.d/haproxy start
/usr/local/sbin/patch-restart-haproxy N While the service is restarted, the outstanding requests will fail and new requests will get connection error until the service is re-enabled. Y
sm Service management daemon N PMON /etc/init.d/sm restart N Will cause all services disabled on the active controller before the standby controller takes over the control. N
sm-api Daemon that provides sm api N PMON N N
sm-eru Daemon that records sm eru data N N N
sm-watchdog Daemon that loads NFS watchdog module to look for and handle stalled NFS threads N N N
neutron-server Service that manages network functions Y SM sm-restart-safe service neutron-server
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/neutron-server stop
/bin/sh /usr/lib/ocf/resource.d/openstack/neutron-server start
/bin/neutron-restart neutron-server
or
/bin/neutron-restart --all
N Will cause neutron services to not be available while restarting, which will prevent instances from being created while it is down. Could cause RPCs from computes to fail while it is restarting. N
neutron-dhcp-agent Agent on compute node that manages DHCP servers for tenant networks Y PMON /etc/init.d/neutron-dhcp-agent restart /bin/neutron-restart neutron-dhcp-agent
or
/bin/neutron-restart --all
N Will prevent binding new DHCP servers while it is down. Requires special handling to kill metadata haproxy processes for networks. Y
neutron-metadata-agent Agent on compute node serving metadata to nodes Y PMON /etc/init.d/neutron-metadata-agent restart /bin/neutron-restart neutron-metadata-agent
or
/bin/neutron-restart --all
N Nodes will not be able to receive metadata while it is down N
neutron-sriov-nic-agent Agent on compute node responsible for setting SR-IOV port information Y PMON /etc/init.d/neutron-sriov-nic-agent restart /bin/neutron-restart neutron-sriov-nic-agent
or
/bin/neutron-restart --all
N Will not be able to set device parameters while restarting N
neutron-bgp-dragent BGP dynamic routing agent on controller node Y PMON /etc/init.d/neutron-bgp-dragent restart /bin/neutron-restart neutron-bgp-dragent
or
/bin/neutron-restart --all
N Will not be able to set device parameters while restarting N
keystone-all Keystone provides services that support an identity, token management, and service catalog and policy functionality. Y SM sm-restart-safe service keystone
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/keystone stop
/bin/sh /usr/lib/ocf/resource.d/openstack/keystone start
/usr/local/sbin/patch-restart-processes keystone-all N While the service is restarted, the outstanding requests will fail and new requests will get connection error until the service is re-enabled. N
aodh-api Aodh service that handles API requests for openstack alarming. Y SM sm-restart-safe service aodh-api
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/aodh-api stop
/bin/sh /usr/lib/ocf/resource.d/openstack/aodh-api start
N While the service is restarted, the outstanding requests will fail and new requests will get connection error until the service is re-enabled. N
aodh-evaluator Aodh service that performs threshold evaluation for openstack alarming. Y SM sm-restart-safe service aodh-evaluator
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/aodh-evaluator stop
/bin/sh /usr/lib/ocf/resource.d/openstack/aodh-evaluator start
N While the service is restarted no openstack alarm threshold evaluations will be executed until the service is re-enabled. N
aodh-listener Aodh service that generates alarms based on events. Y SM sm-restart-safe service aodh-listener
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/aodh-listener stop
/bin/sh /usr/lib/ocf/resource.d/openstack/aodh-listener start
N While the service is restarted no openstack event based alarms will be generated until the service is re-enabled. N
aodh-notifier Aodh service that sends openstack alarm notifications. Y SM sm-restart-safe service aodh-notifier
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/aodh-notifier stop
/bin/sh /usr/lib/ocf/resource.d/openstack/aodh-notifier start
N While the service is restarted no openstack alarm threshold notifications will be issued until the service is re-enabled. N
aodh-expirer-active Cron job that purges expired openstack alarms Y CRON N/A

To run the expirer manually: /usr/bin/aodh-expirer-active
N There is no need to restart after patch. The change will take effect next time the expirer cron job is run.
Unless there are new features specifically planned for expirer, this code is very stable.
N
heat-api Heat service for API requests for openstack orchestration. Y SM sm-restart-safe service heat-api
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/heat-api stop
/bin/sh /usr/lib/ocf/resource.d/openstack/heat-api start
N While the service is restarted, horizon or CLI heat requests will fail. Horizon will re-established automatically. CLI commands needs to be re-issued. Heat stack updates in progress may fail. N
heat-api-cfn Heat service for AWS Cloudformation API requests. Y SM sm-restart-safe service heat-api-cfn
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/heat-api-cfn stop
/bin/sh /usr/lib/ocf/resource.d/openstack/heat-api-cfn start
N While the service is restarted, cloudformation API requests such as autoscaling will not be processed. N
heat-api-cloudwatch Heat service for AWS Cloudwatch metric collection. Y SM sm-restart-safe service heat-api-cloudwatch
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/heat-api-cloudwatch stop
/bin/sh /usr/lib/ocf/resource.d/openstack/heat-api-cloudwatch start
N While the service is restarted, stats sent from VMs will not be processed. N
heat-engine Heat service for AWS Cloudwatch metric collection. Y SM sm-restart-safe service heat-engine
which runs the following:

/bin/sh /usr/lib/ocf/resource.d/openstack/heat-engine stop
/bin/sh /usr/lib/ocf/resource.d/openstack/heat-engine start
N While the service is restarted, openstrack heat orchestration commands will not be processed. Stacks being created, deleted or updated will fail and need to be re-initiated. N
heat-purge-deleted-active Cron job that purges deleted openstack heat stacks from the database Y CRON N/A

To run the expirer manually: /usr/bin/heat-purge-deleted-active
N There is no need to restart after patch. The change will take effect next time the cron job is run.
Unless there are new features specifically planned, this code is very stable.
N
Glance Glance imaging service - a single script restarts both glance-api and glance-registry. Y SM /usr/bin/restart-glance
N While the service is restarted, the outstanding requests will continue and new requests will get connection error until the service is re-enabled. The graceful restart takes more than 30 secs the process is killed. Timers are configurable from the restart script N
Cinder Cinder volume service - a single script restarts cinder-volume, cinder-scheduler, cinder-api and cinder-backup. Y SM /usr/bin/restart-cinder
N While the service is restarted, the outstanding requests will continue and new requests will get connection error until the service is re-enabled. Timers are configurable from the restart script N
Horizon Horizon - Openstack Dashboard GUI used to control openstack and Titanium Cloud operations Y SM sm-restart service horizon
/usr/bin/horizon-patching-restart N When horizon is restarted via the patch restart command all users will be logged out. If they try to log back in before the server is up again they will see an internal server error. It usually takes less than a minute for the service to restart N
IO-Monitor Daemon which monitors cinder devices and raises alarms for excessive storage IO load. Y PMON pmon-restart io-monitor-manager /usr/local/sbin/patch-restart-processes io-monitor-manager N Generally there should be no impact. It is very unlikely for the system to encounter an excessive storage IO load which will only last a couple of seconds until the io-monitor process is restarted, such that it will not be detected. N
vim Virtual Infrastructure Manager Y SM sm-restart-safe service vim N While the service is restarting, requests through the VIM API or through the Nova API Proxy will fail. Any instance actions normally triggered due to instance state changes (from nova) will not occur until the process starts up again and audits the instance states. N
vim-api Virtual Infrastructure Manager API Y SM sm-restart-safe service vim-api N While the service is restarting, requests through the external VIM API will fail. N
vim-webserver Virtual Infrastructure Manager Web Server Y SM sm-restart-safe service vim-webserver N No impact. This service is for design use only. N
nova-api Nova API Service Y SM sm-restart-safe service nova-api
/bin/nova-restart N While the service is restarted, the outstanding requests will fail and new requests will get connection error until the service is re-enabled. N
nova-placement-api Nova Placement API Service Y SM sm-restart-safe service nova-placement-api
/bin/nova-restart N While the service is restarted, the outstanding requests will fail and new requests will get connection error until the service is re-enabled. N
nova-conductor Nova Conductor Service Y SM sm-restart-safe service nova-conductor
/bin/nova-restart N While the service is restarted, the outstanding requests will fail and new requests will get connection error until the service is re-enabled. N
nova-scheduler Nova Scheduler Service Y SM sm-restart-safe service nova-scheduler
/bin/nova-restart N While the service is restarted, the outstanding requests will fail and new requests will get connection error until the service is re-enabled. N
nova-console-auth Nova Console Auth Service Y SM sm-restart-safe service nova-console-auth
/bin/nova-restart N While the service is restarted, the outstanding requests will fail and new requests will get connection error until the service is re-enabled. N
nova-novnc Nova VNC Service Y SM sm-restart-safe service nova-novnc
/bin/nova-restart N While the service is restarted, the outstanding requests will fail and new requests will get connection error until the service is re-enabled. N
nova-compute Nova Compute Service Y PMON /usr/local/sbin/pmon-restart nova-compute
/bin/nova-restart N While the services is restarted, the outstanding requests will fail and new requests will get connection error until the service is re-enabled. N
ceph-osd & ceph-mon Ceph OSD and Monitor processes Y PMON /etc/ceph/ceph_pmon_wrapper.sh restart
/etc/ceph/ceph_pmon_wrapper.sh restart N Ceph processes on a node will restart (ceph-mon and ceph-osd). The restart will take at most 30s and functionality should not be affected. Note that this command should not be executed at the same time on storage-0 and any of the controller nodes as we do not support restarting two of the three ceph-mon at the same time. Restarting it on controller-0, controller-1 & storage-0, at the same time with glance, cinder, nova, ceph-rest-api, sysinv or ceph-manager on the active controller should be avoided due to ~30 secs delay to ceph APIs. This delay happens when any of the ceph-mon changes state and may cause timeouts when dependent services restart. Recommendations: (1) On the active controller, restart Ceph before the other service; (2) updating ctrl-0,ctrl-1 & storage-0 at the same time should be avoided.
Process/Service Function In service patchable Managed by Restart command Patch Restart command Restart dependency Impact(if restarted while in operation) Special handling required