[OSTF] Test network connectivity to instance which is running on node with enabled DPDK

Bug #1567439 reported by Artem Panchenko on 2016-04-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Maksym Strukov
Mitaka
High
Maksym Strukov

Bug Description

We need to create new OSTF tests which spawns new instance on compute with DPD and checks connectivity to it via floating IP:

Check network connectivity from instance with DPDK via floating IP
        Target component: Neutron
        Scenario:
            1. Create a new security group (if it doesn`t exist yet).
            2. Create router
            3. Create network
            4. Create subnet
            5. Uplink subnet to router.
            6. Create new flavor with huge pages
            7. Create an instance using the new flavor, security group
               in created subnet. Boot it on compute with enabled DPDK.
            8. Create a new floating IP
            9. Assign the new floating IP to the instance.
            10. Check connectivity to the floating IP using ping command.
            11. Check that public IP 8.8.8.8 can be pinged from instance.
            12. Disassociate server floating ip.
            13. Delete floating ip
            14. Delete server.
            15. Delete flavor
            16. Remove router.
            17. Remove subnet
            18. Remove network
        Duration: 300 s.
        Deployment tags: neutron dpdk

Related blueprint https://blueprints.launchpad.net/fuel/+spec/test-ovs-dpdk

Changed in fuel:
status: New → Confirmed

Fix proposed to branch: master
Review: https://review.openstack.org/303549

Changed in fuel:
status: Confirmed → In Progress

Reviewed: https://review.openstack.org/303549
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=1eb65cc189ccc2125c9845d025aec937d2a56ab4
Submitter: Jenkins
Branch: master

commit 1eb65cc189ccc2125c9845d025aec937d2a56ab4
Author: Maksym Strukov <email address hidden>
Date: Fri Apr 8 20:31:06 2016 +0300

    Check connectivity from instance with DPDK via floating IP

    Scenario:
    1. Create a new security group (if it doesn`t exist yet).
    2. Create router
    3. Create network
    4. Create subnet
    5. Uplink subnet to router.
    6. Create new flavor with huge pages
    7. Create an instance using the new flavor, security group
    in created subnet. Boot it on compute with enabled DPDK.
    8. Create a new floating IP
    9. Assign the new floating IP to the instance.
    10. Check connectivity to the floating IP using ping command.
    11. Check that public IP 8.8.8.8 can be pinged from instance.
    12. Disassociate server floating ip.
    13. Delete floating ip
    14. Delete server.
    15. Delete flavor
    16. Remove router.
    17. Remove subnet
    18. Remove network

    Change-Id: I86c43896a6b7ff0e55f72dd7ffce02487ac7299e
    Closes-Bug: #1567439

Changed in fuel:
status: In Progress → Fix Committed

Reviewed: https://review.openstack.org/311078
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=6d218a93fc1ba92cf8c2eaa43f39ba7b32d32a28
Submitter: Jenkins
Branch: stable/mitaka

commit 6d218a93fc1ba92cf8c2eaa43f39ba7b32d32a28
Author: Maksym Strukov <email address hidden>
Date: Fri Apr 8 20:31:06 2016 +0300

    Check connectivity from instance with DPDK via floating IP

    Scenario:
    1. Create a new security group (if it doesn`t exist yet).
    2. Create router
    3. Create network
    4. Create subnet
    5. Uplink subnet to router.
    6. Create new flavor with huge pages
    7. Create an instance using the new flavor, security group
    in created subnet. Boot it on compute with enabled DPDK.
    8. Create a new floating IP
    9. Assign the new floating IP to the instance.
    10. Check connectivity to the floating IP using ping command.
    11. Check that public IP 8.8.8.8 can be pinged from instance.
    12. Disassociate server floating ip.
    13. Delete floating ip
    14. Delete server.
    15. Delete flavor
    16. Remove router.
    17. Remove subnet
    18. Remove network

    Change-Id: I86c43896a6b7ff0e55f72dd7ffce02487ac7299e
    Closes-Bug: #1567439
    (cherry picked from commit 1eb65cc189ccc2125c9845d025aec937d2a56ab4)

Maksym Strukov (unbelll) wrote :

Verified as fixed in 9.0-mos-364 and 10.0-224

Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers