Cisco Cisco Intelligent Automation for Cloud 4.3.1 User Guide
51
Setting Up the Infrastructure
Connecting the Cloud Platform Elements
l.
Enter a Project Name. Enter the Project Name for which system administrator have the access rights. This Project
name is used only to acquire authentication token for the operations. If no Project Name is provided, the user
name will be used as the tenant name by default.
name is used only to acquire authentication token for the operations. If no Project Name is provided, the user
name will be used as the tenant name by default.
m.
Enter the Password assigned to the account used to connect to the OpenStack Cloud Manager server.
n.
Re-enter the password to confirm it.
5.
Click Submit Order.
Defining the Puppet Labs’ Puppet Master Platform Element
You must be logged in as the Cloud Provider Technical Administrator to perform this task. Complete the following steps
to define the connection information for the Puppet Labs platform element that will be used in Cisco Intelligent
Automation for Cloud 4.3.1.
to define the connection information for the Puppet Labs platform element that will be used in Cisco Intelligent
Automation for Cloud 4.3.1.
1.
Launch Cisco Intelligent Automation for Cloud 4.3.1 and log in as a Cloud Provider Technical Administrator.
2.
Choose Setup > System Settings > Connections tab.
3.
On the Connections tab, click Connect Cloud Infrastructure to open the form.
4.
On the Connect Cloud Infrastructure form, choose Puppet from the Platform Element Type list.
5.
Specify the following connection information for the Puppet platform element:
a.
Enter the Connection Name. This is the “friendly name” for the Puppet platform element connection.
b.
Optional. Enter information that describes the Puppet platform element.
c.
Enter the Host Name. This is the host name or IP address for the Puppet platform element.
d.
Enter the SSH Login and the SSH Password assigned to the account used to connect to the Puppet PE.
e.
Re-enter the SSH Password to confirm it.
f.
Enter the Private Key. (This is Optional. Not all deployments require this.)
6.
Check the Show Additional Options check box (optional). Here you can add additional information such as:
a.
Installer Package Base URL. This is the Base URL for downloading the Puppet Enterprise installer package.
Default location is PuppetLabs repository. This can also be a local HTTP resource where installer packages are
stored.
Default location is PuppetLabs repository. This can also be a local HTTP resource where installer packages are
stored.
Note:
Default is used when the field is left blank. This fieldhould only be populated when using a local HTTP resource.
b.
Alternate Module Path. By default, discovery uses the modulepath as defined in puppet.conf. You can point
discovery to an alternate path such as a GIT working copy. In defining an alternate path, you can use
$environment to dynamically insert the environment in the path.
discovery to an alternate path such as a GIT working copy. In defining an alternate path, you can use
$environment to dynamically insert the environment in the path.
c.
Hiera Node Classification Path
Note:
New nodes are classified using Hiera Yaml files, and, by default, are saved to the Puppet Master location
specified by the first folder specified in the module path. These files can be stored in an alternate location, perhaps
separate from your modules. In defining the hiera path, you can use $environment to dynamically insert the
environment in the path. Remember, this location must match what is defined in your hiera.yaml file in the Puppet
Master’s configuration directory.
separate from your modules. In defining the hiera path, you can use $environment to dynamically insert the
environment in the path. Remember, this location must match what is defined in your hiera.yaml file in the Puppet
Master’s configuration directory.
d.
Set up Linux Proxy.