Open Stack

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 <hongbin.lu at huawei.com>
 To: Guz Egor <guz_egor at yahoo.com>; OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org> 
 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_egor at 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:王华 <wanghua.humble at gmail.com>
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at 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 <liyong.qiao at 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-request at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev    

  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160331/73b0fe12/attachment.html>