open stack operations guide

OpenStack operations guideFernando López / Alessandro M. MartelloneCloud Architect, TID / CREATE-Net

fernando.lopezaguilar@telefonica.com, @flopezaguilaralessandro.martellone@create-net.org

• source openrc

– export OS_TENANT_NAME=<name of the tenant>

– export OS_USERNAME=<user name>

– export OS_PASSWORD=<user password>

– export OS_AUTH_URL=<keystone url>

– export OS_AUTH_STRATEGY=keystone

– export SERVICE_TOKEN=<service token>

– export SERVICE_ENDPOINT=<keystone service endpoint>

• OpenStack Identity

– service keystone start/stop/restart

Services management

• Following this presentation you will be able to:

– Manage flavours, images, keypair via CLI

– Launch a VM via CLI

– Services management

– Logging and monitoring

– Backup

• You should have deployed an environment with at least 1 controller and 1 compute node.

Goals

• Flavor list

• Image list

• Add keypair

Flavor, image list, keypair

Launch an instance from an image

• Image Service

– service glance-api start/stop/restart

– service glance-registry start/stop/restart

Services management

• OpenStack Compute

– service nova-api start/stop/restart

– service nova-scheduler start/stop/restart

– service nova-conductor start/stop/restart

– service nova-cert start/stop/restart

– service nova-consoleauth start/stop/restart

– service nova-novncproxy start/stop/restart

Services management

• OpenStack Block Storage

– service cinder-api start/stop/restart

– service cinder-scheduler start/stop/restart

Services management

Logging and monitoringWhere are log files located?

• Because your cloud is most likely composed of many

servers, you must check logs on each of those servers to

properly piece an event together.

• A better solution is to send the logs of all servers to a

central location so that they can all be accessed from the

same area.

• ITBox manages centrally the logs in /var/log/remote

directory.

Logging and monitoring

• A basic type of alert monitoring is to simply check and see

whether a required process is running. For example,

ensure that the nova-api service is running on the cloud

controller:

ps aux | grep nova-api nova 12786 0.0 0.0 37952 1312 ? Ss

Feb11 0:00 su -s /bin/sh -c exec nova-api --config-

file=/etc/nova/nova.conf nova nova 12787 0.0 0.1 135764

57400

Logging and monitoring

• You can create automated alerts for critical processes by

using Nagios and NRPE. For example, to ensure that the

nova-compute process is running on compute nodes,

create an alert on your Nagios server that looks like this:

– define service {

host_name c01.example.com

check_command check_nrpe_1arg!check_nova-compute

use generic-service notification_period 24x7

contact_groups sysadmins

service_description nova-compute

}

Logging and monitoring

• We will describe only how to back up configuration files and databases that the various OpenStack components need to run.

– Database

– Compute

– Image catalog

• /var/lib/glance/images. where the images are stored (If you are using a file-based backend of glance)

• /var/lib/cinder where the volumes are stored.

– Object Storage

• At http://bit.ly/1iDL0z5 an backup script.

Backup

Thanks!Thanks!