Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
Hi Monty, Thanks for your guidance. I have appended your inputs to the blueprint [1]. [1] https://blueprints.launchpad.net/magnum/+spec/bay-with-no-floating-ips Best regards, Honbgin -Original Message- From: Monty Taylor [mailto:mord...@inaugust.com] Sent: March-31-16 1:18 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? A few things: Public IPs and Floating IPs are not the same thing. Some clouds have public IPs. Some have floating ips. Some have both. I think it's important to be able to have magnum work with all of the above. If the cloud does not require using a floating IP (as most do not) to get externally routable network access, magnum should work with that. If the cloud does require using a floating IP (as some do) to get externally rouatable network access, magnum should be able to work with that. In either case, it's also possible the user will not desire the thing they are deploying in magnum to be assigned an IP on a network that routes off of the cloud. That should also be supported. Shade has code to properly detect most of those situations that you can look at for all of the edge cases - however, since magnum is installed by the operator, I'd suggest making a config value for it that allows the operator to express whether or not the cloud in question requires floating ips as it's EXCEPTIONALLY hard to accurately detect. On 03/31/2016 12:42 PM, Guz Egor wrote: > Hongbin, > It's correct, I was involved in two big OpenStack private cloud > deployments and we never had public ips. > In such case Magnum shouldn't create any private networks, operator > need to provide network id/name or it should use default (we used to > have networking selection logic in > scheduler) . > > --- > Egor > > -- > -- > *From:* Hongbin Lu > *To:* Guz Egor ; OpenStack Development Mailing > List (not for usage questions) > *Sent:* Thursday, March 31, 2016 7:29 AM > *Subject:* RE: [openstack-dev] [magnum] Are Floating IPs really needed > for all nodes? > > Egor, > I agree with what you said, but I think we need to address the problem > that some clouds are lack of public IP addresses. It is not uncommon > that a private cloud is running without public IP addresses, and they > already figured out how to route traffics in and out. In such case, a > bay doesn’t need to have floating IPs and the NodePort feature seems > to work with the private IP address. > Generally speaking, I think it is useful to have a feature that allows > bays to work without public IP addresses. I don’t want to end up in a > situation that Magnum is unusable because the clouds don’t have enough > public IP addresses. > Best regards, > Hongbin > *From:*Guz Egor [mailto:guz_e...@yahoo.com] > *Sent:* March-31-16 12:08 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [magnum] Are Floating IPs really needed > for all nodes? > -1 > who is going to run/support this proxy? also keep in mind that > Kubernetes Service/NodePort > (http://kubernetes.io/docs/user-guide/services/#type-nodeport) > functionality is not going to work without public ip and this is very > handy feature. > --- > Egor > -- > -- > *From:*王华mailto:wanghua.hum...@gmail.com>> > *To:* OpenStack Development Mailing List (not for usage questions) > <mailto:openstack-dev@lists.openstack.org>> > *Sent:* Wednesday, March 30, 2016 8:41 PM > *Subject:* Re: [openstack-dev] [magnum] Are Floating IPs really needed > for all nodes? > Hi yuanying, > I agree to reduce the usage of floating IP. But as far as I know, if > we need to pull docker images from docker hub in nodes floating ips > are needed. To reduce the usage of floating ip, we can use proxy. Only > some nodes have floating ips, and other nodes can access docker hub by > proxy. > Best Regards, > Wanghua > On Thu, Mar 31, 2016 at 11:19 AM, Eli Qiao <mailto:liyong.q...@intel.com>> wrote: > > Hi Yuanying, > +1 > I think we can add option on whether to using floating ip address > since IP address are kinds of resource which not wise to waste. > On 2016年03月31日10:40, 大塚元央wrote: > > Hi team, > Previously, we had a reason why all nodes should have floating ips [1]. > But now we have a LoadBalancer features for masters [2] and minions [3]. > And also minions do not necessarily need to have floating ips [4]. > I think it’s the time to remove floating ips from all nodes. > I know we are using floating ips in gate to get
Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
Egor, I agree with you. I think Magnum should support another option to connect a bay to an existing neutron private network instead of creating one. If you like, we can discuss it separately in our next team meeting or in the design summit. Best regards, Hongbin From: Guz Egor [mailto:guz_e...@yahoo.com] Sent: March-31-16 12:42 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Hongbin Lu Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Hongbin, It's correct, I was involved in two big OpenStack private cloud deployments and we never had public ips. In such case Magnum shouldn't create any private networks, operator need to provide network id/name or it should use default (we used to have networking selection logic in scheduler) . --- Egor From: Hongbin Lu mailto:hongbin...@huawei.com>> To: Guz Egor mailto:guz_e...@yahoo.com>>; OpenStack Development Mailing List (not for usage questions) mailto:openstack-dev@lists.openstack.org>> Sent: Thursday, March 31, 2016 7:29 AM Subject: RE: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Egor, I agree with what you said, but I think we need to address the problem that some clouds are lack of public IP addresses. It is not uncommon that a private cloud is running without public IP addresses, and they already figured out how to route traffics in and out. In such case, a bay doesn’t need to have floating IPs and the NodePort feature seems to work with the private IP address. Generally speaking, I think it is useful to have a feature that allows bays to work without public IP addresses. I don’t want to end up in a situation that Magnum is unusable because the clouds don’t have enough public IP addresses. Best regards, Hongbin From: Guz Egor [mailto:guz_e...@yahoo.com] Sent: March-31-16 12:08 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? -1 who is going to run/support this proxy? also keep in mind that Kubernetes Service/NodePort (http://kubernetes.io/docs/user-guide/services/#type-nodeport) functionality is not going to work without public ip and this is very handy feature. --- Egor From: 王华 mailto:wanghua.hum...@gmail.com>> To: OpenStack Development Mailing List (not for usage questions) mailto:openstack-dev@lists.openstack.org>> Sent: Wednesday, March 30, 2016 8:41 PM Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Hi yuanying, I agree to reduce the usage of floating IP. But as far as I know, if we need to pull docker images from docker hub in nodes floating ips are needed. To reduce the usage of floating ip, we can use proxy. Only some nodes have floating ips, and other nodes can access docker hub by proxy. Best Regards, Wanghua On Thu, Mar 31, 2016 at 11:19 AM, Eli Qiao mailto:liyong.q...@intel.com>> wrote: Hi Yuanying, +1 I think we can add option on whether to using floating ip address since IP address are kinds of resource which not wise to waste. On 2016年03月31日 10:40, 大塚元央 wrote: Hi team, Previously, we had a reason why all nodes should have floating ips [1]. But now we have a LoadBalancer features for masters [2] and minions [3]. And also minions do not necessarily need to have floating ips [4]. I think it’s the time to remove floating ips from all nodes. I know we are using floating ips in gate to get log files, So it’s not good idea to remove floating ips entirely. I want to introduce `disable-floating-ips-to-nodes` parameter to bay model. Thoughts? [1]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html [2]: https://blueprints.launchpad.net/magnum/+spec/make-master-ha [3]: https://blueprints.launchpad.net/magnum/+spec/external-lb [4]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html Thanks -yuanying __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Regards, Eli Qiao (乔立勇) Intel OTC China __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.open
Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
Hi all, Thanks for your inputs. We discussed this proposal in our team meeting [1], and we all agreed to support an option to remove the need of floating IPs. A blueprint was created for implementing this feature: https://blueprints.launchpad.net/magnum/+spec/bay-with-no-floating-ips . Please feel free to assign it to yourselves if you interest to implement it. Thanks. [1] http://eavesdrop.openstack.org/meetings/containers/2016/containers.2016-04-05-16.00.txt Best regards, Hongbin From: Yuanying OTSUKA [mailto:yuany...@oeilvert.org] Sent: April-01-16 1:57 AM To: Guz Egor; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Hi Egor, I know some people still want to use floating ips to connect nodes, So I will not remove floating ips feature completely. Only introduce the option which will disable to assign floating ip to nodes. Because some people doesn’t want to assign floating ip to nodes. Thanks -yuaning 2016年3月31日(木) 13:11 Guz Egor mailto:guz_e...@yahoo.com>>: -1 who is going to run/support this proxy? also keep in mind that Kubernetes Service/NodePort (http://kubernetes.io/docs/user-guide/services/#type-nodeport) functionality is not going to work without public ip and this is very handy feature. --- Egor From: 王华 mailto:wanghua.hum...@gmail.com>> To: OpenStack Development Mailing List (not for usage questions) mailto:openstack-dev@lists.openstack.org>> Sent: Wednesday, March 30, 2016 8:41 PM Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Hi yuanying, I agree to reduce the usage of floating IP. But as far as I know, if we need to pull docker images from docker hub in nodes floating ips are needed. To reduce the usage of floating ip, we can use proxy. Only some nodes have floating ips, and other nodes can access docker hub by proxy. Best Regards, Wanghua On Thu, Mar 31, 2016 at 11:19 AM, Eli Qiao mailto:liyong.q...@intel.com>> wrote: Hi Yuanying, +1 I think we can add option on whether to using floating ip address since IP address are kinds of resource which not wise to waste. On 2016年03月31日 10:40, 大塚元央 wrote: Hi team, Previously, we had a reason why all nodes should have floating ips [1]. But now we have a LoadBalancer features for masters [2] and minions [3]. And also minions do not necessarily need to have floating ips [4]. I think it’s the time to remove floating ips from all nodes. I know we are using floating ips in gate to get log files, So it’s not good idea to remove floating ips entirely. I want to introduce `disable-floating-ips-to-nodes` parameter to bay model. Thoughts? [1]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html [2]: https://blueprints.launchpad.net/magnum/+spec/make-master-ha [3]: https://blueprints.launchpad.net/magnum/+spec/external-lb [4]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html Thanks -yuanying __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Regards, Eli Qiao (乔立勇) Intel OTC China __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
Hi Egor, I know some people still want to use floating ips to connect nodes, So I will not remove floating ips feature completely. Only introduce the option which will disable to assign floating ip to nodes. Because some people doesn’t want to assign floating ip to nodes. Thanks -yuaning 2016年3月31日(木) 13:11 Guz Egor : > -1 > > who is going to run/support this proxy? also keep in mind that Kubernetes > Service/NodePort ( > http://kubernetes.io/docs/user-guide/services/#type-nodeport) > functionality is not going to work without public ip and this is very > handy feature. > > --- > Egor > > -- > *From:* 王华 > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > *Sent:* Wednesday, March 30, 2016 8:41 PM > > *Subject:* Re: [openstack-dev] [magnum] Are Floating IPs really needed > for all nodes? > > Hi yuanying, > > I agree to reduce the usage of floating IP. But as far as I know, if we > need to pull > docker images from docker hub in nodes floating ips are needed. To reduce > the > usage of floating ip, we can use proxy. Only some nodes have floating ips, > and > other nodes can access docker hub by proxy. > > Best Regards, > Wanghua > > On Thu, Mar 31, 2016 at 11:19 AM, Eli Qiao wrote: > > Hi Yuanying, > +1 > I think we can add option on whether to using floating ip address since IP > address are > kinds of resource which not wise to waste. > > > On 2016年03月31日 10:40, 大塚元央 wrote: > > Hi team, > > Previously, we had a reason why all nodes should have floating ips [1]. > But now we have a LoadBalancer features for masters [2] and minions [3]. > And also minions do not necessarily need to have floating ips [4]. > I think it’s the time to remove floating ips from all nodes. > > I know we are using floating ips in gate to get log files, > So it’s not good idea to remove floating ips entirely. > > I want to introduce `disable-floating-ips-to-nodes` parameter to bay model. > > Thoughts? > > [1]: > http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html > [2]: https://blueprints.launchpad.net/magnum/+spec/make-master-ha > [3]: https://blueprints.launchpad.net/magnum/+spec/external-lb > [4]: > http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html > > Thanks > -yuanying > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > -- > Best Regards, Eli Qiao (乔立勇) > Intel OTC China > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
A few things: Public IPs and Floating IPs are not the same thing. Some clouds have public IPs. Some have floating ips. Some have both. I think it's important to be able to have magnum work with all of the above. If the cloud does not require using a floating IP (as most do not) to get externally routable network access, magnum should work with that. If the cloud does require using a floating IP (as some do) to get externally rouatable network access, magnum should be able to work with that. In either case, it's also possible the user will not desire the thing they are deploying in magnum to be assigned an IP on a network that routes off of the cloud. That should also be supported. Shade has code to properly detect most of those situations that you can look at for all of the edge cases - however, since magnum is installed by the operator, I'd suggest making a config value for it that allows the operator to express whether or not the cloud in question requires floating ips as it's EXCEPTIONALLY hard to accurately detect. On 03/31/2016 12:42 PM, Guz Egor wrote: Hongbin, It's correct, I was involved in two big OpenStack private cloud deployments and we never had public ips. In such case Magnum shouldn't create any private networks, operator need to provide network id/name or it should use default (we used to have networking selection logic in scheduler) . --- Egor *From:* Hongbin Lu *To:* Guz Egor ; OpenStack Development Mailing List (not for usage questions) *Sent:* Thursday, March 31, 2016 7:29 AM *Subject:* RE: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Egor, I agree with what you said, but I think we need to address the problem that some clouds are lack of public IP addresses. It is not uncommon that a private cloud is running without public IP addresses, and they already figured out how to route traffics in and out. In such case, a bay doesn’t need to have floating IPs and the NodePort feature seems to work with the private IP address. Generally speaking, I think it is useful to have a feature that allows bays to work without public IP addresses. I don’t want to end up in a situation that Magnum is unusable because the clouds don’t have enough public IP addresses. Best regards, Hongbin *From:*Guz Egor [mailto:guz_e...@yahoo.com] *Sent:* March-31-16 12:08 AM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? -1 who is going to run/support this proxy? also keep in mind that Kubernetes Service/NodePort (http://kubernetes.io/docs/user-guide/services/#type-nodeport) functionality is not going to work without public ip and this is very handy feature. --- Egor *From:*王华mailto:wanghua.hum...@gmail.com>> *To:* OpenStack Development Mailing List (not for usage questions) mailto:openstack-dev@lists.openstack.org>> *Sent:* Wednesday, March 30, 2016 8:41 PM *Subject:* Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Hi yuanying, I agree to reduce the usage of floating IP. But as far as I know, if we need to pull docker images from docker hub in nodes floating ips are needed. To reduce the usage of floating ip, we can use proxy. Only some nodes have floating ips, and other nodes can access docker hub by proxy. Best Regards, Wanghua On Thu, Mar 31, 2016 at 11:19 AM, Eli Qiao mailto:liyong.q...@intel.com>> wrote: Hi Yuanying, +1 I think we can add option on whether to using floating ip address since IP address are kinds of resource which not wise to waste. On 2016年03月31日10:40, 大塚元央wrote: Hi team, Previously, we had a reason why all nodes should have floating ips [1]. But now we have a LoadBalancer features for masters [2] and minions [3]. And also minions do not necessarily need to have floating ips [4]. I think it’s the time to remove floating ips from all nodes. I know we are using floating ips in gate to get log files, So it’s not good idea to remove floating ips entirely. I want to introduce `disable-floating-ips-to-nodes` parameter to bay model. Thoughts? [1]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html [2]: https://blueprints.launchpad.net/magnum/+spec/make-master-ha [3]: https://blueprints.launchpad.net/magnum/+spec/external-lb [4]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html Thanks -yuanying __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe <mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://
Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
Hongbin, It's correct, I was involved in two big OpenStack private cloud
deployments and we never had public ips.In such case Magnum shouldn't create
any private networks, operator need to provide network id/name or it should use
default (we used to have networking selection logic in scheduler) .
--- Egor
From: Hongbin Lu
To: Guz Egor ; OpenStack Development Mailing List (not for
usage questions)
Sent: Thursday, March 31, 2016 7:29 AM
Subject: RE: [openstack-dev] [magnum] Are Floating IPs really needed for all
nodes?
#yiv8309482815 #yiv8309482815 -- _filtered #yiv8309482815
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv8309482815
{font-family:SimSun;panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv8309482815
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv8309482815
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv8309482815
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} _filtered #yiv8309482815
{panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv8309482815
{font-family:Consolas;panose-1:2 11 6 9 2 2 4 3 2 4;}#yiv8309482815
#yiv8309482815 p.yiv8309482815MsoNormal, #yiv8309482815
li.yiv8309482815MsoNormal, #yiv8309482815 div.yiv8309482815MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv8309482815 a:link,
#yiv8309482815 span.yiv8309482815MsoHyperlink
{color:blue;text-decoration:underline;}#yiv8309482815 a:visited, #yiv8309482815
span.yiv8309482815MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv8309482815 pre
{margin:0cm;margin-bottom:.0001pt;font-size:10.0pt;}#yiv8309482815
p.yiv8309482815MsoAcetate, #yiv8309482815 li.yiv8309482815MsoAcetate,
#yiv8309482815 div.yiv8309482815MsoAcetate
{margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;}#yiv8309482815
span.yiv8309482815HTMLPreformattedChar {font-family:Consolas;}#yiv8309482815
span.yiv8309482815hoenzb {}#yiv8309482815 span.yiv8309482815BalloonTextChar
{}#yiv8309482815 span.yiv8309482815EmailStyle22 {color:#1F497D;}#yiv8309482815
.yiv8309482815MsoChpDefault {font-size:10.0pt;} _filtered #yiv8309482815
{margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv8309482815
div.yiv8309482815WordSection1 {}#yiv8309482815 Egor, I agree with what you
said, but I think we need to address the problem that some clouds are lack of
public IP addresses. It is not uncommon that a private cloud is running without
public IP addresses, and they already figured out how to route traffics in and
out. In such case, a bay doesn’t need to have floating IPs and the NodePort
feature seems to work with the private IP address. Generally speaking, I
think it is useful to have a feature that allows bays to work without public IP
addresses. I don’t want to end up in a situation that Magnum is unusable
because the clouds don’t have enough public IP addresses. Best regards,
Hongbin From: Guz Egor [mailto:guz_e...@yahoo.com]
Sent: March-31-16 12:08 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all
nodes? -1 who is going to run/support this proxy? also keep in mind that
Kubernetes Service/NodePort
(http://kubernetes.io/docs/user-guide/services/#type-nodeport) functionality is
not going to work without public ip and this is very handy feature. ---
Egor From:王华
To: OpenStack Development Mailing List (not for usage questions)
Sent: Wednesday, March 30, 2016 8:41 PM
Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all
nodes? Hi yuanying, I agree to reduce the usage of floating IP. But as
far as I know, if we need to pull docker images from docker hub in nodes
floating ips are needed. To reduce the usage of floating ip, we can use proxy.
Only some nodes have floating ips, and other nodes can access docker hub by
proxy. Best Regards, Wanghua On Thu, Mar 31, 2016 at 11:19 AM, Eli Qiao
wrote:
Hi Yuanying,
+1
I think we can add option on whether to using floating ip address since IP
address are
kinds of resource which not wise to waste. On 2016年03月31日 10:40, 大塚元央 wrote:
Hi team, Previously, we had a reason why all nodes should have floating ips
[1]. But now we have a LoadBalancer features for masters [2] and minions [3].
And also minions do not necessarily need to have floating ips [4]. I think it’s
the time to remove floating ips from all nodes. I know we are using floating
ips in gate to get log files, So it’s not good idea to remove floating ips
entirely. I want to introduce `disable-floating-ips-to-nodes` parameter to
bay model. Thoughts? [1]:
http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html [2]:
https://blueprints.launchpad.net/magnum/+spec/make-master-ha [3]:
https://blueprints.launchpad.net/magnum/+spec/external-lb [4]:
http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html
Thanks
Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
Egor, I agree with what you said, but I think we need to address the problem that some clouds are lack of public IP addresses. It is not uncommon that a private cloud is running without public IP addresses, and they already figured out how to route traffics in and out. In such case, a bay doesn’t need to have floating IPs and the NodePort feature seems to work with the private IP address. Generally speaking, I think it is useful to have a feature that allows bays to work without public IP addresses. I don’t want to end up in a situation that Magnum is unusable because the clouds don’t have enough public IP addresses. Best regards, Hongbin From: Guz Egor [mailto:guz_e...@yahoo.com] Sent: March-31-16 12:08 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? -1 who is going to run/support this proxy? also keep in mind that Kubernetes Service/NodePort (http://kubernetes.io/docs/user-guide/services/#type-nodeport) functionality is not going to work without public ip and this is very handy feature. --- Egor From: 王华 mailto:wanghua.hum...@gmail.com>> To: OpenStack Development Mailing List (not for usage questions) mailto:openstack-dev@lists.openstack.org>> Sent: Wednesday, March 30, 2016 8:41 PM Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Hi yuanying, I agree to reduce the usage of floating IP. But as far as I know, if we need to pull docker images from docker hub in nodes floating ips are needed. To reduce the usage of floating ip, we can use proxy. Only some nodes have floating ips, and other nodes can access docker hub by proxy. Best Regards, Wanghua On Thu, Mar 31, 2016 at 11:19 AM, Eli Qiao mailto:liyong.q...@intel.com>> wrote: Hi Yuanying, +1 I think we can add option on whether to using floating ip address since IP address are kinds of resource which not wise to waste. On 2016年03月31日 10:40, 大塚元央 wrote: Hi team, Previously, we had a reason why all nodes should have floating ips [1]. But now we have a LoadBalancer features for masters [2] and minions [3]. And also minions do not necessarily need to have floating ips [4]. I think it’s the time to remove floating ips from all nodes. I know we are using floating ips in gate to get log files, So it’s not good idea to remove floating ips entirely. I want to introduce `disable-floating-ips-to-nodes` parameter to bay model. Thoughts? [1]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html [2]: https://blueprints.launchpad.net/magnum/+spec/make-master-ha [3]: https://blueprints.launchpad.net/magnum/+spec/external-lb [4]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html Thanks -yuanying __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Regards, Eli Qiao (乔立勇) Intel OTC China __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
-1 who is going to run/support this proxy? also keep in mind that Kubernetes Service/NodePort (http://kubernetes.io/docs/user-guide/services/#type-nodeport)functionality is not going to work without public ip and this is very handy feature. --- Egor From: 王华 To: OpenStack Development Mailing List (not for usage questions) Sent: Wednesday, March 30, 2016 8:41 PM Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Hi yuanying, I agree to reduce the usage of floating IP. But as far as I know, if we need to pulldocker images from docker hub in nodes floating ips are needed. To reduce theusage of floating ip, we can use proxy. Only some nodes have floating ips, andother nodes can access docker hub by proxy. Best Regards,Wanghua On Thu, Mar 31, 2016 at 11:19 AM, Eli Qiao wrote: Hi Yuanying, +1 I think we can add option on whether to using floating ip address since IP address are kinds of resource which not wise to waste. On 2016年03月31日 10:40, 大塚元央 wrote: Hi team, Previously, we had a reason why all nodes should have floating ips [1]. But now we have a LoadBalancer features for masters [2] and minions [3]. And also minions do not necessarily need to have floating ips [4]. I think it’s the time to remove floating ips from all nodes. I know we are using floating ips in gate to get log files, So it’s not good idea to remove floating ips entirely. I want to introduce `disable-floating-ips-to-nodes` parameter to bay model. Thoughts? [1]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html [2]: https://blueprints.launchpad.net/magnum/+spec/make-master-ha [3]: https://blueprints.launchpad.net/magnum/+spec/external-lb [4]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html Thanks -yuanying __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Regards, Eli Qiao (乔立勇) Intel OTC China __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
Oh, that reminds me, MesosMonitor requires to use master node’s floating ip address directly to get state information. BR, Eli(Li Yong)Qiao From: 王华 [mailto:wanghua.hum...@gmail.com] Sent: Thursday, March 31, 2016 11:41 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Importance: Low Hi yuanying, I agree to reduce the usage of floating IP. But as far as I know, if we need to pull docker images from docker hub in nodes floating ips are needed. To reduce the usage of floating ip, we can use proxy. Only some nodes have floating ips, and other nodes can access docker hub by proxy. Best Regards, Wanghua On Thu, Mar 31, 2016 at 11:19 AM, Eli Qiao mailto:liyong.q...@intel.com>> wrote: Hi Yuanying, +1 I think we can add option on whether to using floating ip address since IP address are kinds of resource which not wise to waste. On 2016年03月31日 10:40, 大塚元央 wrote: Hi team, Previously, we had a reason why all nodes should have floating ips [1]. But now we have a LoadBalancer features for masters [2] and minions [3]. And also minions do not necessarily need to have floating ips [4]. I think it’s the time to remove floating ips from all nodes. I know we are using floating ips in gate to get log files, So it’s not good idea to remove floating ips entirely. I want to introduce `disable-floating-ips-to-nodes` parameter to bay model. Thoughts? [1]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html [2]: https://blueprints.launchpad.net/magnum/+spec/make-master-ha [3]: https://blueprints.launchpad.net/magnum/+spec/external-lb [4]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html Thanks -yuanying __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Regards, Eli Qiao (乔立勇) Intel OTC China __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
Hi yuanying, I agree to reduce the usage of floating IP. But as far as I know, if we need to pull docker images from docker hub in nodes floating ips are needed. To reduce the usage of floating ip, we can use proxy. Only some nodes have floating ips, and other nodes can access docker hub by proxy. Best Regards, Wanghua On Thu, Mar 31, 2016 at 11:19 AM, Eli Qiao wrote: > Hi Yuanying, > +1 > I think we can add option on whether to using floating ip address since IP > address are > kinds of resource which not wise to waste. > > > On 2016年03月31日 10:40, 大塚元央 wrote: > > Hi team, > > Previously, we had a reason why all nodes should have floating ips [1]. > But now we have a LoadBalancer features for masters [2] and minions [3]. > And also minions do not necessarily need to have floating ips [4]. > I think it’s the time to remove floating ips from all nodes. > > I know we are using floating ips in gate to get log files, > So it’s not good idea to remove floating ips entirely. > > I want to introduce `disable-floating-ips-to-nodes` parameter to bay model. > > Thoughts? > > [1]: > http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html > [2]: https://blueprints.launchpad.net/magnum/+spec/make-master-ha > [3]: https://blueprints.launchpad.net/magnum/+spec/external-lb > [4]: > http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html > > Thanks > -yuanying > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > -- > Best Regards, Eli Qiao (乔立勇) > Intel OTC China > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
Hi Yuanying, +1 I think we can add option on whether to using floating ip address since IP address are kinds of resource which not wise to waste. On 2016年03月31日 10:40, 大塚元央 wrote: Hi team, Previously, we had a reason why all nodes should have floating ips [1]. But now we have a LoadBalancer features for masters [2] and minions [3]. And also minions do not necessarily need to have floating ips [4]. I think it’s the time to remove floating ips from all nodes. I know we are using floating ips in gate to get log files, So it’s not good idea to remove floating ips entirely. I want to introduce `disable-floating-ips-to-nodes` parameter to bay model. Thoughts? [1]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html [2]: https://blueprints.launchpad.net/magnum/+spec/make-master-ha [3]: https://blueprints.launchpad.net/magnum/+spec/external-lb [4]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html Thanks -yuanying __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Regards, Eli Qiao (乔立勇) Intel OTC China <>__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [magnum] Are Floating IPs really needed for all nodes?
Hi team, Previously, we had a reason why all nodes should have floating ips [1]. But now we have a LoadBalancer features for masters [2] and minions [3]. And also minions do not necessarily need to have floating ips [4]. I think it’s the time to remove floating ips from all nodes. I know we are using floating ips in gate to get log files, So it’s not good idea to remove floating ips entirely. I want to introduce `disable-floating-ips-to-nodes` parameter to bay model. Thoughts? [1]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067213.html [2]: https://blueprints.launchpad.net/magnum/+spec/make-master-ha [3]: https://blueprints.launchpad.net/magnum/+spec/external-lb [4]: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067280.html Thanks -yuanying __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
