Re: [openstack-dev] [Openstack] [Neutron] auto configration of local_ip
Hi, Once we configure Interface of compute node for local_ip, then it can be used for both IPv4 and IPv6 as well based on the deployment network. Regards, Balaji.P From: Nir Yechiel [mailto:nyech...@redhat.com] Sent: Thursday, January 16, 2014 9:28 PM To: OpenStack Development Mailing List (not for usage questions) Cc: OpenStack General Mailing List Subject: Re: [openstack-dev] [Openstack] [Neutron] auto configration of local_ip From: "Martinx - ジェームズ" mailto:thiagocmarti...@gmail.com>> To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Cc: "OpenStack General Mailing List" mailto:openst...@lists.openstack.org>> Sent: Thursday, January 16, 2014 5:41:09 PM Subject: Re: [openstack-dev] [Openstack] [Neutron] auto configration of local_ip Guys, Let me ask something about this... Apparently, VXLAN can be easier to implement/maintain when using it with IPv6 (read about it here: www.nephos6.com/pdf/OpenStack-on-IPv6.pdf<http://www.nephos6.com/pdf/OpenStack-on-IPv6.pdf>), so, I'm wondering if local_ip can be an IPv6 address (for IceHouse-3 / Ubuntu 14.04) and, of course, if it is better in the end of the day. Thoughts?! Cheers! Thiago AFAIK the VXLAN draft addresses only IPv4, but IPv6 should be there in the future. On 16 January 2014 12:58, balaj...@freescale.com<mailto:balaj...@freescale.com> mailto:balaj...@freescale.com>> wrote: > 2014/1/16 NOTSU Arata mailto:no...@virtualtech.jp>>: > > The question is, what criteria is appropriate for the purpose. The > criteria being mentioned so far in the review are: > > > > 1. assigned to the interface attached to default gateway 2. being in > > the specified network (CIDR) 3. assigned to the specified interface > >(1 can be considered a special case of 3) > > > > For a certain deployment scenario, local_ip is totally different among > those nodes, but if we consider local_ip as local_interface, it may > match most of the nodes. I think it is more convenient to switch from > ip to interface parameter. > [P Balaji-B37839] We implemented this and using in our test setup. We are glad to share this through blue-print/Bug if anybody is interested. Regards, Balaji.P ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack] [Neutron] auto configration of local_ip
- Original Message - From: "Martinx - ジェームズ" To: "OpenStack Development Mailing List (not for usage questions)" Cc: "OpenStack General Mailing List" Sent: Thursday, January 16, 2014 5:41:09 PM Subject: Re: [openstack-dev] [Openstack] [Neutron] auto configration of local_ip Guys, Let me ask something about this... Apparently, VXLAN can be easier to implement/maintain when using it with IPv6 (read about it here: www.nephos6.com/pdf/OpenStack-on-IPv6.pdf ), so, I'm wondering if local_ip can be an IPv6 address (for IceHouse-3 / Ubuntu 14.04) and, of course, if it is better in the end of the day. Thoughts?! Cheers! Thiago AFAIK the VXLAN draft addresses only IPv4, but IPv6 should be there in the future. On 16 January 2014 12:58, balaj...@freescale.com < balaj...@freescale.com > wrote: > 2014/1/16 NOTSU Arata < no...@virtualtech.jp >: > > The question is, what criteria is appropriate for the purpose. The > criteria being mentioned so far in the review are: > > > > 1. assigned to the interface attached to default gateway 2. being in > > the specified network (CIDR) 3. assigned to the specified interface > > (1 can be considered a special case of 3) > > > > For a certain deployment scenario, local_ip is totally different among > those nodes, but if we consider local_ip as local_interface, it may > match most of the nodes. I think it is more convenient to switch from > ip to interface parameter. > [P Balaji-B37839] We implemented this and using in our test setup. We are glad to share this through blue-print/Bug if anybody is interested. Regards, Balaji.P ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack] [Neutron] auto configration of local_ip
Guys, Let me ask something about this... Apparently, VXLAN can be easier to implement/maintain when using it with IPv6 (read about it here: www.nephos6.com/pdf/OpenStack-on-IPv6.pdf), so, I'm wondering if local_ip can be an IPv6 address (for IceHouse-3 / Ubuntu 14.04) and, of course, if it is better in the end of the day. Thoughts?! Cheers! Thiago On 16 January 2014 12:58, balaj...@freescale.com wrote: > > 2014/1/16 NOTSU Arata : > > > The question is, what criteria is appropriate for the purpose. The > > criteria being mentioned so far in the review are: > > > > > > 1. assigned to the interface attached to default gateway 2. being in > > > the specified network (CIDR) 3. assigned to the specified interface > > >(1 can be considered a special case of 3) > > > > > > > For a certain deployment scenario, local_ip is totally different among > > those nodes, but if we consider local_ip as local_interface, it may > > match most of the nodes. I think it is more convenient to switch from > > ip to interface parameter. > > > [P Balaji-B37839] We implemented this and using in our test setup. We are > glad to share this through blue-print/Bug if anybody is interested. > > Regards, > Balaji.P > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack] [Neutron] auto configration of local_ip
> 2014/1/16 NOTSU Arata : > > The question is, what criteria is appropriate for the purpose. The > criteria being mentioned so far in the review are: > > > > 1. assigned to the interface attached to default gateway 2. being in > > the specified network (CIDR) 3. assigned to the specified interface > >(1 can be considered a special case of 3) > > > > For a certain deployment scenario, local_ip is totally different among > those nodes, but if we consider local_ip as local_interface, it may > match most of the nodes. I think it is more convenient to switch from > ip to interface parameter. > [P Balaji-B37839] We implemented this and using in our test setup. We are glad to share this through blue-print/Bug if anybody is interested. Regards, Balaji.P ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack] [Neutron] auto configration of local_ip
2014/1/16 NOTSU Arata : > The question is, what criteria is appropriate for the purpose. The criteria > being mentioned so far in the review are: > > 1. assigned to the interface attached to default gateway > 2. being in the specified network (CIDR) > 3. assigned to the specified interface >(1 can be considered a special case of 3) > For a certain deployment scenario, local_ip is totally different among those nodes, but if we consider local_ip as local_interface, it may match most of the nodes. I think it is more convenient to switch from ip to interface parameter. Nick Ma skywalker.n...@gmail.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
