Page tree
Skip to end of metadata
Go to start of metadata

In order to find your way around in the OPNFV installation on the ARM pod, one nice place to start is by asking the installer to provide the IP addresses of all of the various components, both virtual and bare metal, that make up the openstack environment.

First, log into the jump server at 10.10.50.12, as ubuntu/ubuntu.

From there, you can ssh into the MCP installer's salt master, which is a virtual machine called cfg01.  The IP address for cfg01 is 10.20.0.2.

ssh -i /var/lib/opnfv/mcp.rsa ubuntu@10.20.0.2

note: you may have to add "-o StrictHostKeyChecking=no" to the above line.

Once on the cfg01 vm, become root and ask salt for IP addresses of all its minions:

ubuntu@cfg01:~$ sudo -i
root@cfg01:~# salt '*' network.ip_addrs
cmp001.baremetal-mcp-ocata-ovs-ha.local:
    - 10.1.0.101
    - 10.10.50.101
    - 10.10.53.19
    - 172.16.10.101
    - 192.168.122.1
mas01.baremetal-mcp-ocata-ovs-ha.local:
    - 10.10.53.3
    - 10.20.0.3
    - 172.16.10.3
kvm02.baremetal-mcp-ocata-ovs-ha.local:
    - 10.10.53.18
    - 172.16.10.140
    - 172.16.10.142
mdb01.baremetal-mcp-ocata-ovs-ha.local:
    - 10.10.53.30
    - 172.16.10.76
ctl03.baremetal-mcp-ocata-ovs-ha.local:
    - 10.10.53.37
    - 172.16.10.13
ctl02.baremetal-mcp-ocata-ovs-ha.local:
    - 10.10.53.32
    - 172.16.10.12
dbs02.baremetal-mcp-ocata-ovs-ha.local:
    - 10.10.53.29
    - 172.16.10.52
ctl01.baremetal-mcp-ocata-ovs-ha.local:
    - 10.10.53.31
    - 172.16.10.10
    - 172.16.10.11

...and so on...

From the above list of addresses, you will be interested in the floating/virtual address of the controller.  There are three controllers, ctl01, ctl02, and ctl03.  Each has its individual IP addresses, including those on the 172.16.10.0/24 subnet, typically 172.16.10.11, 172.16.10.12, and 172.16.10.13.  The floating/virtual address moves from one elected controller to another as there are disruptions in service provided by the three controllers.  The floating/virtual address is 172.16.10.10, and is assigned in the above example to ctl01.

If you use 172.16.10.10 as your controller address (for API access, for example), that will resolve to the active elected controller.  Note that if you put any files on the server at that address, those files might not be there if another controller is elected to host the floating/virtual address.

If you want to get to compute nodes, they are cmp001 and cmp002, at 172.16.10.101 and 172.16.10.102, respectively.

To use the OpenStack CLI to interact with OpenStack, log into the floating/virtual address:

ssh -i /var/lib/opnfv/mcp.rsa ubuntu@172.16.10.10

Once there, either become root, via "sudo -i", or copy the user credentials from the /root directory into the /home/ubuntu directory

sudo cp /root/keystonerc /home/ubuntu
sudo cp /root/keystonercv3 /home/ubuntu

Then source these...

source keystonercv3

And you can now use the openstack CLI:

ubuntu@ctl01:~$ openstack network list
+--------------------------------------+--------------+--------------------------------------+
| ID                                   | Name         | Subnets                              |
+--------------------------------------+--------------+--------------------------------------+
| 5800ebea-3acb-45af-a697-c3af027c5871 | floating_net | 1d230881-5ecd-4230-acca-adc71314c618 |
+--------------------------------------+--------------+--------------------------------------+
ubuntu@ctl01:~$

 

  • No labels