Cisco Cisco Intelligent Automation for Cloud 4.3.1 Installation Guide
12
Configuring OpenStack
OpenStack Configuration Notes
1.
If you are using all-in-one deployment or a scenario with only one available compute node make sure that you have
set both allow_resize_to_same_host and allow_migrate_to_same_host to true in configuration file at
/etc/nova/nova.conf.
set both allow_resize_to_same_host and allow_migrate_to_same_host to true in configuration file at
/etc/nova/nova.conf.
Note:
These options allow you to resize the instance on one node.
Set resize_confirm_window=x. By default, this is set to 0, but you need to change this to x seconds in order to
automatically confirm the resize after x seconds.
automatically confirm the resize after x seconds.
2.
If you are running OpenStack within a virtual machine set, in order to use QEMU you must set the following options
in configuration file on your compute host(s) at /etc/nova/nova.conf:
in configuration file on your compute host(s) at /etc/nova/nova.conf:
libvirt_type=qemu
Cinder service=mandatory
Note:
Configuration changes are applied only after the restart of Nova services.
3.
If you would like OpenStack to report debugging information into an httpd log file, specify the following
parameters in the configuration files found at /etc/openstack-dashboard/local_settings:
parameters in the configuration files found at /etc/openstack-dashboard/local_settings:
DEBUG=True
TEMPLATE_DEBUG=DEBUG
Note:
The file may be a significant size; this may negatively affect performance.
4.
Check that you have opened all necessary ports in your firewall:
8776 - Block Storage (cinder)
8774 - Compute (nova) endpoints
5000 - Identity service public endpoint
9696- Networking (neutron)
5672 - Message Broker (AMQP traffic)
Note:
You can find a list of the recommended ports here:
Note:
For the correct steps needed to install the OpenStack solution on your environment, refer to the OpenStack
documentation located on the OpenStack website at:
.
OpenStack Considerations
OpenStack Node Bootstrapping
During node bootstrapping, the following node attributes are automatically assigned:
stack_instance
: Name of the Stack Instance (shared by all servers in the same stack)
iac_organization
: Name of the IAC organization (including tenant prefix) for customer who ordered the stack
Bootstrapping of ACM roles onto OpenStack Instances
The Linux Bootstrapping credentials input for the Chef or Puppet Platform Element need to have an OS-specific
username depending on the template being used. For example, if the version of Linux being used is Ubuntu, the
username should be “ubuntu”; if using CentOS, the username will be “centos”. If the business is using multiple OS types,
the platform element will need to be updated prior to deploying a different os type. The key-pair to these accounts will
be set by IAC during the instance creation and therefore be used by the ACM bootstrapping process later on.
username depending on the template being used. For example, if the version of Linux being used is Ubuntu, the
username should be “ubuntu”; if using CentOS, the username will be “centos”. If the business is using multiple OS types,
the platform element will need to be updated prior to deploying a different os type. The key-pair to these accounts will
be set by IAC during the instance creation and therefore be used by the ACM bootstrapping process later on.