<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/22/14 2:08 PM, Kevin Benton
wrote:<br>
</div>
<blockquote
cite="mid:CAO_F6JOnW0meU5t-KQDUJgxZVA2fw4Cgw+6BOGHNNWb6NK6aOw@mail.gmail.com"
type="cite">
<div dir="ltr">Can't you simulate the same topology as the
FlatDHCPManager + Floating IPs with a shared network attached to
a router which is then attached to an external network?</div>
</blockquote>
<br>
Mmmmaybe? Floating IP support in nova-network is pretty great
(allocation, assignment, release, etc.) and allows us shuffle around
a small number of public IPs amongst a much larger number of
instances. Your suggestion doesn't address that, does it? Short of
my implementing a bunch of custom stuff on my own?<br>
<br>
-A<br>
<br>
<br>
<blockquote
cite="mid:CAO_F6JOnW0meU5t-KQDUJgxZVA2fw4Cgw+6BOGHNNWb6NK6aOw@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Dec 21, 2014 at 7:00 PM, Andrew
Bogott <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:abogott@wikimedia.org" target="_blank">abogott@wikimedia.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Greetings!<br>
<br>
I'm about to set up a new cloud, so for the second time
this year I'm facing the question of Neutron vs.
nova-network. In our current setup we're using
nova.network.manager.FlatDHCPManager with floating IPs.
This config has been working fine, and would probably be
our first choice for the new cloud as well.<br>
<br>
At this point is there any compelling reason for us to
switch to Neutron? My understanding is that the Neutron
flat network model still doesn't support anything similar
to floating IPs, so if we move to Neutron we'll need to
switch to a subnet-per-tenant model. Is that still
correct?<br>
<br>
I'm puzzled by the statement that " <a
moz-do-not-send="true">upgrades without instance
downtime will be available in the Kilo release"[1] --
surely for such a path to exist, Kilo/Neutron would need
to support all the same use cases as nova-network. If
that's right and Neutron is right on the verge of
supporting flat-with-floating then we may just cool our
jets and wait to build the new cloud until Kilo is
released. </a>I have no particular reason to prefer
Neutron, but I'd like to avoid betting on a horse right
before it's put down :)<br>
<br>
Thanks!<br>
<br>
-Andrew<br>
<br>
[1]
<a moz-do-not-send="true"
href="http://docs.openstack.org/openstack-ops/content/nova-network-deprecation.html"
target="_blank">http://docs.openstack.org/openstack-ops/content/nova-network-deprecation.html</a><br>
<br>
</div>
<br>
_______________________________________________<br>
Mailing list: <a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a moz-do-not-send="true"
href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div>Kevin Benton</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>