Friday, April 6, 2018

Editing the undercloud.conf and performing the undercloud install Pike OpenStack tropleO undercloud

After the python tripleo client has been installed, Copy the sample undercloud.conf 

sudo cp /usr/share/instack-undercloud/undercloud.conf.sample ~/undercloud.conf

Edit the undercloud.conf 

here is how the undercloud.conf looks like after the editing has been done.

(undercloud) [stack@pike ~]$ grep -v -e ^$ -e ^# undercloud.conf
[DEFAULT]
undercloud_hostname = pike.sujitnet11.net
local_ip = 172.16.128.177/16
network_gateway = 172.16.0.1
undercloud_nameservers = 172.16.0.1
undercloud_ntp_servers = 69.195.159.158
overcloud_domain_name = sujitnet11.net
local_interface = ens3
local_mtu = 1500
network_cidr = 172.16.0.0/16
masquerade_network = 172.16.0.0/16
dhcp_start = 172.16.201.11
dhcp_end = 172.16.201.51
inspection_interface = br-ctlplane
inspection_iprange = 172.16.201.52,172.16.201.100
inspection_extras = true
inspection_enable_uefi = true
enable_node_discovery = true
discovery_default_driver = pxe_ipmitool
undercloud_update_packages = true
enable_ui = true
enable_validations = true
ipxe_enabled = true
scheduler_max_attempts = 30
clean_nodes = false
enabled_drivers = pxe_ipmitool,pxe_drac,pxe_ilo
[auth]

(undercloud) [stack@pike ~]$


There are other things that also you can set in the undercloud,conf, but for a simple and straight forward deployement for my scenario, this works well.


Perform the undercloud install 



Install the undercloud as per the parameters that have been specified in the undercloud.conf file.


Please note that undercloud install cannot be run as the root user, we have the stack user to perform this.

openstack undercloud install



Output Truncated 
.
.
.

2018-04-02 20:32:09,075 INFO: os-refresh-config completed successfully
2018-04-02 20:32:11,091 INFO: Created flavor "baremetal" with profile "None"
2018-04-02 20:32:11,166 INFO: Created flavor "control" with profile "control"
2018-04-02 20:32:11,238 INFO: Created flavor "compute" with profile "compute"
2018-04-02 20:32:11,319 INFO: Created flavor "ceph-storage" with profile "ceph-storage"
2018-04-02 20:32:11,396 INFO: Created flavor "block-storage" with profile "block-storage"
2018-04-02 20:32:11,471 INFO: Created flavor "swift-storage" with profile "swift-storage"
2018-04-02 20:32:11,479 INFO: Configuring Mistral workbooks
2018-04-02 20:32:31,529 INFO: Mistral workbooks configured successfully
2018-04-02 20:32:58,278 INFO: Configuring an hourly cron trigger for tripleo-ui logging
2018-04-02 20:33:00,220 INFO: Added _member_ role to admin user
2018-04-02 20:33:00,235 INFO:
###############################################################
Undercloud install complete.

The file containing this installation's passwords is at
/home/stack/undercloud-passwords.conf.

There is also a stackrc file at /home/stack/stackrc.

These files are needed to interact with the OpenStack services, and should be
secured.

###############################################################

[stack@pike ~]$


--
The undercloud installation creates the stackrc Environment file that has the information to connect to the undercloud Openstack instance. 

Source it using 

As the user stack
cd ~/
source stackrc 

or 

. stackrc

Unless you source these you cannot run the openstack commands on the undercloud server 



Go to the Main page of the OpenStack Tripleo on KVM : Openstack Pike TripleO undercloud deployment with overcloud controller HA on KVM (libvirt)

No comments:

Post a Comment