Chapter 4. Test the deployment

1. Source the credentials to access the overcloud:

   $ source /home/stack/overcloudrc

2. Create an external neutron network that will be used to access the instance from outside of the overcloud:

   $ openstack network create --external --project service --external  --provider-network-type flat --provider-physical-network datacentre

3. Create the corresponding neutron subnet for the new external network (created in the previous step):

   $ openstack subnet create  --project service --no-dhcp --network external --gateway 192.168.37.1 --allocation-pool start=192.168.37.200,end=192.168.37.220 --subnet-range 192.168.37.0/24 external-subnet

4. Download the cirros image to be used for creating overcloud instances:

   $ wget http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img

5. Upload the cirros image into glance on the overcloud:

   $ openstack image create cirros --public --file ./cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format bare

6. Create a tiny flavor to use for overcloud instances:

   $ openstack flavor create m1.tiny --ram 512 --disk 1 --public

7. Create a tenant network based on VXLAN to host the instances:

   $ openstack network create net_test --provider-network-type=vxlan --provider-segment 100

8. Create a subnet for the tenant network (created in the previous step):

   $ openstack subnet create --network net_test --subnet-range 123.123.123.0/24 test

9. Find and store the ID of the tenant network:

   $ net_mgmt_id=$(openstack network list | grep net_test | awk '{print $2}')

10. Create an instance called cirros1 and attach it to the net_test network:

    $ openstack server create --flavor m1.tiny --image cirros --nic net-id=$net_mgmt_id cirros1

11. Create a second instance called cirros2, also attached to the net_test network:

    $ openstack server create --flavor m1.tiny --image cirros --nic net-id=$net_mgmt_id cirros2

1. Find and store the ID of the admin project:

   $ admin_project_id=$(openstack project list | grep admin | awk '{print $2}')

2. Find and store the admin project’s default security group:

   $ admin_sec_group_id=$(openstack security group list | grep $admin_project_id | awk '{print $2}')

3. Add a rule to the admin default security group to allow ICMP traffic ingress:

   $ openstack security group rule create $admin_sec_group_id --protocol icmp --ingress

4. Add a rule to the admin default security group to allow ICMP traffic egress:

   $ openstack security group rule create $admin_sec_group_id --protocol icmp --egress

5. Add a rule to the admin default security group to allow SSH traffic ingress:

   $ openstack security group rule create $admin_sec_group_id --protocol tcp --dst-port 22 --ingress

6. Add a rule to the admin default security group to allow SSH traffic egress:

   $ openstack security group rule create $admin_sec_group_id --protocol tcp --dst-port 22 --egress

1. From horizon, you should be able to access the novnc console for an instance. Use the password from overcloudrc to login to horizon as admin. The default login for cirros images is the user name cirros, and cubswin:) as the password.

2. From the novnc console, verify that the instance received a DHCP address:

   $ ip addr show

   Note

   Another method of doing this is by using the nova console-log <instance id> from the undercloud, which will show if a DHCP lease was obtained.

3. Now repeat the steps 1 and 2 for all other instances.
4. From one instance, attempt to ping the other instances. This will validate the basic Tenant network connectivity in the overcloud.
5. Verify that you can reach other instances by using a Floating IP.

1. Create a floating IP on the external network to be associated with cirros1 instance:

   $ openstack floating ip create external

2. Create a router which will be used to handle NAT between the floating IP and cirros1 tenant IP:

   $ openstack router create test

3. Set the gateway of the router to be the external network:

   $ openstack router set test --external-gateway external

4. Add and interface to the router attached to the tenant network:

   $ openstack router add subnet test test

5. Find and store the floating IP created in Step 23:

   $ floating_ip=$(openstack floating ip list | head -n -1 | grep -Eo '[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+')

6. Associate the floating IP with the cirros1 instance:

   $ openstack server add floating ip cirros1 $floating_ip

7. From a node that has external network access, attempt to login to the instance:

   $ ssh cirros@$floating_ip

Procedure

1. Login onto the undercloud.

2. Enter the following command to start the process:

     $ source /home/stack/stackrc

3. List all instances:

     $ openstack server list

4. Choose the required instance and note its IP address in the list.

5. Connect to the machine. You will use the IP address from the list above:

     $ ssh heat-admin@<IP from step 4>

6. Switch to superuser:

     $ sudo -i

Procedure

1. As a superuser, login to the overcloud node running OpenDaylight or an OpenDaylight node running in custom role.

2. Verify that the OpenDaylight controller is running on all controller nodes:

   # docker ps | grep opendaylight
   2363a99d514a        192.168.24.1:8787/rhosp12/openstack-opendaylight:latest         "kolla_start"            4 hours ago         Up 4 hours (healthy)                       opendaylight_api

3. Verify that HAProxy is properly configured to listen on port 8081:

   # docker exec -it haproxy-bundle-docker-0 grep -A7 opendaylight /etc/haproxy/haproxy.cfg
   listen opendaylight
     bind 172.17.0.10:8081 transparent
     bind 192.168.24.10:8081 transparent
     mode http
     balance source
     server overcloud-controller-0.internalapi.localdomain 172.17.0.22:8081 check fall 5 inter 2000 rise 2
     server overcloud-controller-1.internalapi.localdomain 172.17.0.12:8081 check fall 5 inter 2000 rise 2
     server overcloud-controller-2.internalapi.localdomain 172.17.0.13:8081 check fall 5 inter 2000 rise 2

4. Use HAproxy IP to connect the karaf account:

   # ssh -p 8101 karaf@localhost

5. List the installed features.

   # feature:list -i | grep odl-netvirt-openstack

   If there is an x in the third column of the list, as generated during the procedure, then the feature is correctly installed.

6. Verify that the API is up and running.

     # web:list | grep neutron

   This API endpoint is set in /etc/neutron/plugins/ml2/ml2_conf.ini and used by the neutron to communicate with OpenDaylight.

7. Verify that VXLAN tunnels between the nodes are up.

   # vxlan:show

8. To test that the REST API is responding correctly, you can list the modules that are using it.

   # curl -u "admin:admin" http://localhost:8181/restconf/modules

   The output will be similar (the example has been shortened).

   {"modules":{"module":[{"name":"netty-event-executor","revision":"2013-11-12","namespace":"urn:opendaylight:params:xml:ns:yang:controller:netty:eventexecutor"},{"name" ...

9. List the REST streams using the host internal_API IP.

   # curl -u "admin:admin" http://localhost:8181/restconf/streams

   You get a similar output:

   {"streams":{}}

10. Enter the following command using host internal_API IP to verify that NetVirt is ready and running:

    # curl -u "admin:admin" http://localhost:8181/restconf/operational/network-topology:network-topology/topology/netvirt:1

    The following output confirms it.

    {"topology":[{"topology-id":"netvirt:1"}]}

Procedure

1. Connect to one of the Compute nodes in the overcloud as a superuser.

2. List the Open vSwitch settings.

   # ovs-vsctl show

3. Notice multiple Managers in the output (lines 2 and 3 in the example).

       6b003705-48fc-4534-855f-344327d36f2a
           Manager "ptcp:6639:127.0.0.1"
           Manager "tcp:172.17.1.16:6640"
               is_connected: true
           Bridge br-ex
               fail_mode: standalone
               Port br-ex-int-patch
                   Interface br-ex-int-patch
                       type: patch
                       options: {peer=br-ex-patch}
               Port br-ex
                   Interface br-ex
                       type: internal
               Port "eth2"
                   Interface "eth2"
           Bridge br-isolated
               fail_mode: standalone
               Port "eth1"
                   Interface "eth1"
               Port "vlan50"
                   tag: 50
                   Interface "vlan50"
                       type: internal
               Port "vlan30"
                   tag: 30
                   Interface "vlan30"
                       type: internal
               Port br-isolated
                   Interface br-isolated
                       type: internal
               Port "vlan20"
                   tag: 20
                   Interface "vlan20"
                       type: internal
           Bridge br-int
               Controller "tcp:172.17.1.16:6653"
                   is_connected: true
               fail_mode: secure
               Port br-ex-patch
                   Interface br-ex-patch
                       type: patch
                       options: {peer=br-ex-int-patch}
               Port "tun02d236d8248"
                   Interface "tun02d236d8248"
                       type: vxlan
                       options: {key=flow, local_ip="172.17.2.18", remote_ip="172.17.2.20"}
               Port br-int
                   Interface br-int
                       type: internal
               Port "tap1712898f-15"
                   Interface "tap1712898f-15"
           ovs_version: "2.7.0"

4. Verify that the tcp manager points to the IP of the node where OpenDaylight is running.
5. Verify that the Managers show is_connected: true to ensure that connectivity to OpenDaylight from OVS is established and uses the OVSDB protocol.
6. Verify that each bridge (other than br-int) exists and matches the NIC template used for deployment with the Compute role.
7. Verify that the tcp connection corresponds to the IP where the OpenDaylight service is running.
8. Verify that the bridge br-int shows is_connected: true and an OpenFlow protocol connection to OpenDaylight is established.

1. Connect to a Compute node as a superuser.

2. List the Open vSwitch configuration settings.

   # ovs-vsctl list open_vswitch

3. Read the output. It will be similar to this example.

    _uuid               : 4b624d8f-a7af-4f0f-b56a-b8cfabf7635d
    bridges             : [11127421-3bcc-4f9a-9040-ff8b88486508, 350135a4-4627-4e1b-8bef-56a1e4249bef]
    cur_cfg             : 7
    datapath_types      : [netdev, system]
    db_version          : "7.12.1"
    external_ids        : {system-id="b8d16d0b-a40a-47c8-a767-e118fe22759e"}
    iface_types         : [geneve, gre, internal, ipsec_gre, lisp, patch, stt, system, tap, vxlan]
    manager_options     : [c66f2e87-4724-448a-b9df-837d56b9f4a9, defec179-720e-458e-8875-ea763a0d8909]
    next_cfg            : 7
    other_config        : {local_ip="11.0.0.30", provider_mappings="datacentre:br-ex"}
    ovs_version         : "2.7.0"
    ssl                 : []
    statistics          : {}
    system_type         : RedHatEnterpriseServer
    system_version      : "7.4-Maipo"

4. Verify that the value of the other_config option has the correct local_ip set for the local interface that connects to the Tenant network through VXLAN tunnels.
5. Verify that the provider_mappings value under the other_config option matches the value given in the OpenDaylightProviderMappings heat template parameter. This configuration maps the neutron logical networks to corresponding physical interfaces.

Procedure

1. Connect to the superuser account on one of the controller role nodes.
2. Make sure that the file /etc/neutron/neutron.conf contains service_plugins=odl-router_v2,trunk.

3. Check that the file /etc/neutron/plugin.ini contains the following ml2 configuration:

   [ml2]
   mechanism_drivers=opendaylight_v2
   
   [ml2_odl]
   password=admin
   username=admin
   url=http://192.0.2.9:8081/controller/nb/v2/neutron

4. On one of the overcloud controllers, verify that neutron agents are running properly.

   # openstack network agent list

5. Verify that both the Metadata and DHCP agents are in the up state (the admin_state_up option is True):

   +--------------------------------------+----------------+--------------------------+-------------------+-------+----------------+------------------------+
   | id                                   | agent_type     | host                     | availability_zone | alive | admin_state_up | binary                 |
   +--------------------------------------+----------------+--------------------------+-------------------+-------+----------------+------------------------+
   | 3be198c5-b3aa-4d0e-abb4-51b29db3af47 | Metadata agent | controller-0.localdomain |                   | :-)   | True           | neutron-metadata-agent |
   | 79579d47-dd7d-4ef3-9614-cd2f736043f3 | DHCP agent     | controller-0.localdomain | nova              | :-)   | True           | neutron-dhcp-agent     |
   +--------------------------------------+----------------+--------------------------+-------------------+-------+----------------+------------------------+