summaryrefslogtreecommitdiffstats
path: root/docker/services/aodh-notifier.yaml
AgeCommit message (Expand)AuthorFilesLines
2017-10-09Remove package if service stopped and disabledmarios1-0/+9
2017-10-09docker: add logging(source & groups)Juan Badia Payno1-0/+2
2017-07-27Generate MySQL client config if service requires databaseDamien Ciabrini1-1/+7
2017-07-15Merge "Use a single configuration file for specifying docker containers."Jenkins1-14/+2
2017-07-14Use a single configuration file for specifying docker containers.Ian Main1-14/+2
2017-07-14Adds network/cidr mapping into a new service propertyGiulio Fidente1-0/+5
2017-07-10Copy only generated puppet files into the containerMartin André1-1/+6
2017-06-28Add heat parameter for all of config_volume imagesMartin André1-3/+10
2017-06-09Make container names consistentMartin André1-2/+2
2017-05-15Add missing type for RoleParameters parameterMartin André1-0/+1
2017-05-15Add role specific information to the service templateSaravanan KR1-0/+9
2017-05-05Mount hostpath logs on /var/logFlavio Percoco1-0/+10
2017-05-02Move containers common volumes from yaql to list_concatJuan Antonio Osorio Robles1-8/+6
2017-04-18Introduce common resources for docker templatesJuan Antonio Osorio Robles1-4/+10
2017-04-03Remove kolla_config copy from servicesMartin André1-8/+3
2017-03-15Add upgrade tasks for aodh containersPradeep Kilambi1-0/+4
2017-03-10Containerize Aodh alarm servicesPradeep Kilambi1-0/+80
ss="gh">Yardstick Test Case Description TC027 ************************************* .. _ipv6: https://wiki.opnfv.org/ipv6_opnfv_project +-----------------------------------------------------------------------------+ |IPv6 connectivity between nodes on the tenant network | | | +--------------+--------------------------------------------------------------+ |test case id | OPNFV_YARDSTICK_TC027_IPv6 connectivity | | | | +--------------+--------------------------------------------------------------+ |metric | RTT, Round Trip Time | | | | +--------------+--------------------------------------------------------------+ |test purpose | To do a basic verification that IPv6 connectivity is within | | | acceptable boundaries when ipv6 packets travel between hosts | | | located on same or different compute blades. | | | The purpose is also to be able to spot trends. Test results, | | | graphs and similar shall be stored for comparison reasons and| | | product evolution understanding between different OPNFV | | | versions and/or configurations. | | | | +--------------+--------------------------------------------------------------+ |configuration | file: opnfv_yardstick_tc027.yaml | | | | | | Packet size 56 bytes. | | | SLA RTT is set to maximum 30 ms. | | | ipv6 test case can be configured as three independent modules| | | (setup, run, teardown). if you only want to setup ipv6 | | | testing environment, do some tests as you want, "run_step" | | | of task yaml file should be configured as "setup". if you | | | want to setup and run ping6 testing automatically, "run_step"| | | should be configured as "setup, run". and if you have had a | | | environment which has been setup, you only wan to verify the | | | connectivity of ipv6 network, "run_step" should be "run". Of | | | course, default is that three modules run sequentially. | | | | +--------------+--------------------------------------------------------------+ |test tool | ping6 | | | | | | Ping6 is normally part of Linux distribution, hence it | | | doesn't need to be installed. | | | | +--------------+--------------------------------------------------------------+ |references | ipv6_ | | | | | | ETSI-NFV-TST001 | | | | +--------------+--------------------------------------------------------------+ |applicability | Test case can be configured with different run step | | | you can run setup, run benchmark, teardown independently | | | SLA is optional. The SLA in this test case serves as an | | | example. Considerably lower RTT is expected. | | | | +--------------+--------------------------------------------------------------+ |pre-test | The test case image needs to be installed into Glance | |conditions | with ping6 included in it. | | | | | | For Brahmaputra, a compass_os_nosdn_ha deploy scenario is | | | need. more installer and more sdn deploy scenario will be | | | supported soon | | | | +--------------+--------------------------------------------------------------+ |test sequence | description and expected result | | | | +--------------+--------------------------------------------------------------+ |step 1 | To setup IPV6 testing environment: | | | 1. disable security group | | | 2. create (ipv6, ipv4) router, network and subnet | | | 3. create VRouter, VM1, VM2 | | | | +--------------+--------------------------------------------------------------+ |step 2 | To run ping6 to verify IPV6 connectivity : | | | 1. ssh to VM1 | | | 2. Ping6 to ipv6 router from VM1 | | | 3. Get the result(RTT) and logs are stored | | | | +--------------+--------------------------------------------------------------+ |step 3 | To teardown IPV6 testing environment | | | 1. delete VRouter, VM1, VM2 | | | 2. delete (ipv6, ipv4) router, network and subnet | | | 3. enable security group | | | | +--------------+--------------------------------------------------------------+ |test verdict | Test should not PASS if any RTT is above the optional SLA | | | value, or if there is a test case execution problem. | | | | +--------------+--------------------------------------------------------------+