Cisco Cisco Intelligent Automation for Cloud 4.3.2 Installation Guide
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
13
Configuring OpenStack
Note:
Keypair is presently the only option available if the user wants to bootstrap ACM roles onto an OpenStack Linux
instance.
Important:
To use password SSH authentication instead of key-pairs, configure images to have a generic user and
password built in. After creating the instance, log into the console using the generic account and manually change the
SSH daemon to allow for password authentication option. With this done, ACM bootstrapping is not possible using
password authentication. However, after making the above changes, brownfielding ACM roles is possible using the
username and password account.
SSH daemon to allow for password authentication option. With this done, ACM bootstrapping is not possible using
password authentication. However, after making the above changes, brownfielding ACM roles is possible using the
username and password account.
OpenStack Physical Network Name, GV OpenStack.Configuration.PhysicalNetworkName
For OpenStack with the Cisco APIC plugin, Cisco IAC 4.3.2 supports deployment with a Physical Network name
configured under the ML2 plugin with value of “physnet1”
configured under the ML2 plugin with value of “physnet1”
—
a common usage for a Network name but one that is a
free-form name. You may choose to use another. Cisco IAC provides a Global Variable
(OpenStack.Configuration.PhysicalNetworkName) to change this.
(OpenStack.Configuration.PhysicalNetworkName) to change this.
Note:
For more information on Cisco APIC and OpenStack, refer to detailed APIC documentation located here: