Portal:Cloud VPS/Admin/Runbooks/TooManyCloudcontrolsDown

Cloud VPS

• Cloud Services overview
• Cloud VPS user docs
• Horizon web interface (help)

Get started

• About Cloud VPS projects
• Cloud VPS user roles and rights
• List of Cloud VPS projects

Instances and access

• Set up a Cloud VPS instance
• Access Cloud VPS instances
• Add disk space to instances (detachable volumes)
• Server groups
• Sudo policies
• Unmanaged instances

Networking

• Security groups and firewall settings
• Floating IP addresses
• Web proxies for exposing Cloud VPS services to the internet

Puppet

• Puppet on Cloud VPS
• Project puppetserver

Managed storage

• Database instances (Trove)
• Object storage (S3 / Swift)

Get help

• Help and communication
• Recommendations for moving to production

Programmatic usage

• OpenStack APIs
• OpenTofu

Documentation for admins

• Cloud VPS infrastructure
• Administrator documentation
• Administrator runbooks

[]

The procedures in this runbook require admin permissions to complete.

Error / Incident

All the cloudcontrol nodes are down in the system.

Cloudcontrols are the nodes that host the control plane for Openstack, so this means that no new actions can be scheduled (starting VMs, creating disks, logging in, ...). This means that even though the VMs might still be running, the system is not usable.

Cloudcontrols host a lot of services, for example:

• Galera + mariadb for all openstack services
• Nova-api, nova-scheduler, nova-conductor (VM instance management)
• RabbitMQ for all openstack services
• HAProxy for all openstack services
• Trove-api, trove-conductor (DB as a Service)
• Keystone (authentication/authorization/accounting)
• Glance (VM image management service)
• Neutron API/rpc (software defined network service)
• Cinder (block device management service)
• ...

Debugging

This might be the result of an ongoing intervention gone wrong, so first try to communicate with the rest of the team and look for any ongoing actions:

• Ask on irc (#wikimedia-cloud-admin) if someone is taking any action and forgot about it
• Check SAL (or sal.toolforge.org) for host being rebooted/taken down
• Check Netbox to make sure the host is not being decommed or network changes were not applied
• Check puppet for recent changes that might have affected the node

Then you can continue trying to figure out why the hosts are going down and not coming back up:

• Try to ssh to the host
• Try to ssh to the management port (see SRE/Dc-operations/Hardware_Troubleshooting_Runbook)

Common issues

Add here any issues you encounter.

Related information

• SAL (or sal.toolforge.org).
• Netbox
• Puppet merged changes
• SRE/Dc-operations/Hardware_Troubleshooting_Runbook
• Portal:Cloud_VPS/Infrastructure
• Portal:Cloud_VPS/Admin/Troubleshooting
• Portal:Cloud_VPS/Admin

Communication and support

Support and administration of the WMCS resources is provided by the Wikimedia Foundation Cloud Services team and Wikimedia movement volunteers. Please reach out with questions and join the conversation:

Discuss and receive general support

• Chat in real time in the IRC channel #wikimedia-cloud ^connect or the bridged Telegram group
• Discuss via email after you have subscribed to the cloud@ mailing list

Stay aware of critical changes and plans

• Subscribe to the cloud-announce@ mailing list (all messages are also mirrored to the cloud@ list)
• Read the News wiki page

Track work tasks and report bugs

Use a subproject of the #Cloud-Services Phabricator project to track confirmed bug reports and feature requests about the Cloud Services infrastructure itself

Read stories and WMCS blog posts

Read the Cloud Services Blog (for the broader Wikimedia movement, see the Wikimedia Technical Blog)

Old incidents

Provide a list of phabricator tasks of previous incidents to be able to more review previous instances of the issue.