Chapter 5. Creating and managing resources for bare-metal instances

Procedure

1. Access the remote shell for the OpenStackClient pod from your workstation:

   $ oc rsh -n openstack openstackclient

   Copy to Clipboard Toggle word wrap

2. Create the virtual network interface (VIF):

   $ openstack port create --network <network> <name>

   Copy to Clipboard Toggle word wrap

3. If you are using the neutron network interface, then create a Bare Metal Provisioning service port with the binding profile information:

   $ openstack baremetal port create <physical_mac_address> --node <node_uuid> \
        --local-link-connection switch_id=<switch_mac_address> \
        --local-link-connection switch_info=<switch_hostname> \
        --local-link-connection port_id=<switch_port_for_connection> \
        --pxe-enabled true \
        --physical-network <phys_net>

   Copy to Clipboard Toggle word wrap
   • Replace <switch_mac_address> with the MAC address or OpenFlow-based datapath_id of the switch.
   • Replace <switch_hostname> with the name of the bare-metal node that hosts the switch.
   • Replace <switch_port_for_connection> with the port ID on the switch, for example, Gig0/1, or rep0-0.
   • Replace <phys_net> with the name of the physical network you want to associate with the bare-metal port. The Bare Metal Provisioning service uses the physical network to map the Networking service virtual ports to physical ports and port groups. If not set then any VIF is mapped to that port when there no bare-metal port with a suitable physical network assignment exists.

4. Exit the openstackclient pod:

   $ exit

   Copy to Clipboard Toggle word wrap

Procedure

1. Access the remote shell for the OpenStackClient pod from your workstation:

   $ oc rsh -n openstack openstackclient

   Copy to Clipboard Toggle word wrap

2. Create a port group:

   $ openstack baremetal port group create \
    --node <node_uuid> --name <group_name> \
    [--address <mac_address>] [--mode <mode>]  \
    --property miimon=100 --property xmit_hash_policy="layer2+3"
    [--support-standalone-ports]

   Copy to Clipboard Toggle word wrap
   • Replace <node_uuid> with the UUID of the node that this port group belongs to.
   • Replace <group_name> with the name for this port group.
   • Optional: Replace <mac_address> with the MAC address for the port group. If you do not specify an address, the deployed instance port group address is the same as the Networking service port. If you do not attach the Networking service port, the port group configuration fails.
   • Optional: Replace <mode> with mode of the port group.
   • Specify if the group supports fallback to standalone ports.
   Note

   You must configure port groups manually in standalone mode either in the image or by generating the configdrive and adding it to the node’s instance_info. Ensure that you have cloud-init version 0.7.7 or later for the port group configuration to work.

3. Associate a port with a port group:

   • During port creation:

     $ openstack baremetal port create --node <node_uuid> --address <mac_address> --port-group <group_name>

     Copy to Clipboard Toggle word wrap

   • During port update:

     $ openstack baremetal port set <port_uuid> --port-group <group_uuid>

     Copy to Clipboard Toggle word wrap

4. Boot an instance by providing an image that has cloud-init or supports bonding.

   To check if the port group is configured properly, run the following command:

   # cat /proc/net/bonding/bondX

   Copy to Clipboard Toggle word wrap

   Here, X is a number that cloud-init generates automatically for each configured port group, starting with a 0 and incremented by one for each configured port group.

5. Exit the openstackclient pod:

   $ exit

   Copy to Clipboard Toggle word wrap

1. Ports or port groups do not have a physical network or have a physical network that matches one of the VIF’s available physical networks.
2. Prefer ports and port groups that have a physical network to ports and port groups that do not have a physical network.
3. Prefer port groups to ports.
4. Prefer ports with PXE enabled.

Procedure

1. Access the remote shell for the OpenStackClient pod from your workstation:

   $ oc rsh -n openstack openstackclient

   Copy to Clipboard Toggle word wrap

2. List the VIF IDs that are connected to the bare-metal node:

   $ openstack baremetal node vif list <node>
   +--------------------------------------+
   | ID                                   |
   +--------------------------------------+
   | 4475bc5a-6f6e-466d-bcb6-6c2dce0fba16 |
   +--------------------------------------+

   Copy to Clipboard Toggle word wrap
   • Replace <node> with the name or UUID of the bare-metal node.

3. After the VIF is attached, the Bare Metal Provisioning service updates the virtual port in the Networking service with the MAC address of the physical port. Check this port address:

   $ openstack port show 4475bc5a-6f6e-466d-bcb6-6c2dce0fba16 -c mac_address -c fixed_ips
   +-------------+-----------------------------------------------------------------------------+
   | Field       | Value                                                                       |
   +-------------+-----------------------------------------------------------------------------+
   | fixed_ips   | ip_address='192.168.24.9', subnet_id='1d11c677-5946-4733-87c3-23a9e06077aa' |
   | mac_address | 00:2d:28:2f:8d:95                                                           |
   +-------------+-----------------------------------------------------------------------------+

   Copy to Clipboard Toggle word wrap

4. Create a new port on the network where you created the bare-metal node:

   $ openstack port create --network baremetal --fixed-ip ip-address=192.168.24.24 <port_name>

   Copy to Clipboard Toggle word wrap

5. Remove the port from the bare-metal instance it was attached to:

   $ openstack server remove port <instance_name> 4475bc5a-6f6e-466d-bcb6-6c2dce0fba16

   Copy to Clipboard Toggle word wrap

6. Check that the IP address no longer exists on the list:

   $ openstack server list

   Copy to Clipboard Toggle word wrap

7. Check if there are VIFs attached to the node:

   $ openstack baremetal node vif list <node>
   $ openstack port list

   Copy to Clipboard Toggle word wrap

8. Add the newly created port:

   $ openstack server add port <instance_name> <port_name>

   Copy to Clipboard Toggle word wrap

9. Verify that the new IP address shows the new port:

   $ openstack server list

   Copy to Clipboard Toggle word wrap

10. Check if the VIF ID is the UUID of the new port:

    $ openstack baremetal node vif list <node>
    +--------------------------------------+
    | ID                                   |
    +--------------------------------------+
    | 6181c089-7e33-4f1c-b8fe-2523ff431ffc |
    +--------------------------------------+

    Copy to Clipboard Toggle word wrap

11. Check if the Networking service port MAC address is updated and matches one of the Bare Metal Provisioning service ports:

    $ openstack port show 6181c089-7e33-4f1c-b8fe-2523ff431ffc -c mac_address -c fixed_ips
    +-------------+------------------------------------------------------------------------------+
    | Field       | Value                                                                        |
    +-------------+------------------------------------------------------------------------------+
    | fixed_ips   | ip_address='192.168.24.24', subnet_id='1d11c677-5946-4733-87c3-23a9e06077aa' |
    | mac_address | 00:2d:28:2f:8d:95                                                            |
    +-------------+------------------------------------------------------------------------------+

    Copy to Clipboard Toggle word wrap

12. Reboot the bare-metal node so that it recognizes the new IP address:

    $ openstack server reboot overcloud-baremetal-0

    Copy to Clipboard Toggle word wrap

    After you detach or attach interfaces, the bare-metal OS removes, adds, or modifies the network interfaces that have changed. When you replace a port, a DHCP request obtains the new IP address, but this might take some time because the old DHCP lease is still valid. To initiate these changes immediately, reboot the bare-metal node.