Re: [openstack-dev] [neutron][networking-odl][qa] What's the recommended behavior for SG Rules with ethertype='IPv6' and protocol='icmp' ?

On Fri, Mar 24, 2017 at 7:27 PM, Brian Haley wrote: > On 03/24/2017 06:41 AM, Ghanshyam Mann wrote: > >> Hi All, >> >> Tempest is testing SG rule creation and pinging scenario tests with >> ethertype='IPv6' and protocol='icmp' [0]. >> In case of ethertype='IPv6', currently neutron accept protocol

Re: [openstack-dev] [Neutron] AGAIN HELP CONFIRM OR DISCUSS:create a port when network contain ipv4 subnets and ipv6 subnets, allocate ipv6 address to the port.

Hello ZhaoBo, The short summary of the BP [1] is that when a network contains an IPv6 SLAAC/dhcpv6-stateless subnet, we use RADVD daemon to advertise the prefix. RADVD deamon periodically advertises the prefix info which is a "multicast message" received by all the hosts/VMs on the network. Wh

Re: [openstack-dev] [Neutron]Unit test failed but devstack was okay

Hi Zhi Chang, You will have to use sorted to fix the test failure. i.e., self.assertEqual(sorted(['2.2.2.2','1.1.1.1']),sorted(dns_list)) --Sridhar. On 07/20/2015 11:17 AM, Zhi Chang wrote: Hi, all. I write a unit test in devstack and runs all tests okay on my environment. Why does Jenkin

Re: [openstack-dev] [tempest] How to run tempest tests

If the deployment does not support IPv6, we use the following convention to skip the tests at class level. https://github.com/openstack/tempest/blob/master/tempest/api/network/base.py#L65 Regards, --Sridhar. On 11/28/2014 01:50 PM, om prakash pandey wrote: Hi Folks, I would like to know abou

Re: [openstack-dev] [All] Proposal to add examples/usecase as part of new features / cli / functionality patches

Current *-specs already include sections like "Data Model Impact/REST Api Impact etc". So what about including a new section like "UseCase examples", which can be updated as a separate patch once the associated CLI changes are merged? Thanks, --Sridhar. On 11/27/2014 10:19 AM, Deepak Shetty wr