Hello everyone,
A new release candidate for networking-odl for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-odl/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
k.org
>> Subject: Re: [openstack-dev] [neutron][networking-odl]
>>
>> hi,
>>
>> On Thu, Nov 2, 2017 at 9:01 AM, Bhatia, Manjeet S
>> wrote:
>> > Hello Neutrinos,
>> >
>> >
>> >
>> > I’ve been trying service profile flavors fo
> -Original Message-
> From: Takashi Yamamoto [mailto:yamam...@midokura.com]
> Sent: Tuesday, November 7, 2017 10:13 PM
> To: Bhatia, Manjeet S
> Cc: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [neutron][networking-odl]
>
> hi,
>
>
hi,
On Thu, Nov 2, 2017 at 9:01 AM, Bhatia, Manjeet S
wrote:
> Hello Neutrinos,
>
>
>
> I’ve been trying service profile flavors for L3 in neutron to register the
> driver,
>
> the method I’ve been using is below
>
>
>
> I have this added to neutron.conf
>
> [service_providers]
>
> service_provid
Hello Neutrinos,
I've been trying service profile flavors for L3 in neutron to register the
driver,
the method I've been using is below
I have this added to neutron.conf
[service_providers]
service_provider =
L3_ROUTER_NAT:ODL:networking_odl.l3.l3_flavor.ODLL3ServiceProvider:default
and then t
Hello everyone,
A new release candidate for networking-odl for the end of the Pike
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-odl/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate wi
Hello everyone,
A new release candidate for networking-odl for the end of the Pike
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-odl/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate wi
On 04/03/2017 09:23 PM, Ghanshyam Mann wrote:
On Sun, Mar 26, 2017 at 9:31 PM, Sridhar Gaddam mailto:sgad...@redhat.com>> wrote:
On Fri, Mar 24, 2017 at 7:27 PM, Brian Haley mailto:haleyb@gmail.com>> wrote:
On 03/24/2017 06:41 AM, Ghanshyam Mann wrote:
Hi All,
On Sun, Mar 26, 2017 at 9:31 PM, Sridhar Gaddam wrote:
>
>
> 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'
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
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 type
as 'icmp', 'icmpv6' and 'ipv6-icmp' which again seems like dupli
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 type
as 'icmp', 'icmpv6' and 'ipv6-icmp' which again seems like duplication of
SG rules bug on neutron side but not s
Thanks for the notification. We are looking into it.
On 11/25/2016 8:09 AM, Ihar Hrachyshka wrote:
Hi,
Seems like newton branch of networking-odl is pulling neutron from
master. Whoever is responsible for the subproject, please fix.
Begin forwarded message:
*From: *"A mailing list for the O
Hi,
Seems like newton branch of networking-odl is pulling neutron from master.
Whoever is responsible for the subproject, please fix.
> Begin forwarded message:
>
> From: "A mailing list for the OpenStack Stable Branch test reports."
>
> Subject: [Openstack-stable-maint] Stable check of opens
lugins.ml2.managers
[req-f228e4bb-0808-42b5-9628-0b2cd9ad1c92 - - - - -] Failed to bind port
fcb2ecbe-07ba-41a1-8c5e-7dac6577d58b on host node-3.domain.tld for vnic_type
normal using segments [{'segmentation_id': None, 'physical_network':
u'physnet1', 'id':
de-3.domain.tld for vnic_type
normal using segments [{'segmentation_id': None, 'physical_network':
u'physnet1', 'id': u'9c2c66a2-557c-4547-912a-1f043ea76d9f', 'network_type':
u'flat'}]
2016-08-19 07:29:30.644 23329 INFO ne
Subject: Re: [openstack-dev] [Neutron][networking-odl] New error Mitaka
together with ODL-Beryllium
Hi Nikolas,
First of all, neutron-...@lists.opendaylight.org (copied) might be a better
place to ask networking-odl questions.
It seems that the external network you described is not managed by
il.com]
> Sent: Thursday, August 18, 2016 9:23 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Cc: Vishal Thapar; Nikolas Hermanns; Michal Skalski; neutron-
> d...@lists.opendaylight.org
> Subject: Re: [openstack-dev] [Neutron][networking-odl] New error Mitak
Hi Nikolas,
First of all, neutron-...@lists.opendaylight.org (copied) might be a
better place to ask networking-odl questions.
It seems that the external network you described is not managed by
OpenDaylight, so it failed port binding.
You probably want to configure multiple mechanism driver
Hey Networking-ODL folks,
I just setup a Mirantis 9.0 release together with Opendaylight Beryllium. Using
networking-odl v2 I see constantly the error:
2016-08-17 11:28:07.927 4040 ERROR neutron.plugins.ml2.managers
[req-7e834676-81b4-479b-ad45-fa39f0fabed3 - - - - -] Failed to bind port
faeaa4
20 matches
Mail list logo
