Hi,
Cross posting to the operators and devs.
In Liberty, pluggable IPAM was added to Neutron. With it, a built-in
pluggable driver, equivalent to the old non-pluggable IPAM was added
as a reference implementation. In a greenfield deployment, you could
choose to use this driver by setting the fol
Neutron Mitaka release [5] with this fix [6] is in the works.
- Consume service plugins queues in RPC workers was merged [8].
If there is something that I missed, please let me know.
Carl Baldwin
[1] https://www.openstack.org/summit/austin-2016/summit-schedule/events/9103
[2] https://bugs.launch
xist. Add the URL
I am looking forward to a well organized and productive discussion at
the summit and I'm eager to see you all there.
Carl Baldwin
[1] https://www.openstack.org/summit/austin-2016/summit-schedule/events/9103
[2]
http://docs.openstack.org/developer/neutron/policies/bugs.htm
On Fri, Feb 26, 2016 at 4:21 AM, Belmiro Moreira
wrote:
> Hi,
> thanks Carl for info about the DHCP plans.
Olá, Belmiro.
> Our DHCP concern is because currently the DHCP agent needs to be assigned
> to a network and then it creates a port for each subnet.
Right, this is a concern for me too.
>
(resending with reply-all)
The routed networks work will include a change to the DHCP scheduler
which will work something like this:
1. Neutron subnets will have optional affinity to a segment
2. DHCP agents will (somewhat indirectly) report which segments to
which they are attached*.
3. Where to
On Thu, Feb 4, 2016 at 5:41 AM, Tomas Vondra wrote:
> Hi Carl,
> sorry for the late reply, but these links of yours expanded to about 12 tabs
> in my browser, most with serveral pages of text. "Given lots of thought" may
> be an understatement.
>
> Both the specs sound very resonable to me. The se
On Wed, Feb 10, 2016 at 5:06 AM, Neil Jerram wrote:
> In terms of how floating IPs are represented in the Neutron data model:
> currently they require a relationship between an external Network, a
> Router and a tenant Network. The floating IP pool is defined as a
> subnet on the external Network
On Fri, Jan 29, 2016 at 2:21 AM, Robert Starmer wrote:
> I don't think there's anything wrong with your suggestion, as I can't find a
> path where the extra address is actually used (it doesn't get used in any
> NAT mapping, so it is really vestigial). The question now is, will anyone in
> the com
On Thu, Jan 14, 2016 at 2:45 AM, Tomas Vondra wrote:
> Hi!
> I have just deployed an OpenStack Kilo installation with DVR and expected
> that it will consume one Public IP per network node as per
> http://assafmuller.com/2015/04/15/distributed-virtual-routing-floating-ips/,
> but it still eats one
On Thu, Jan 14, 2016 at 9:59 AM, Mike Spreitzer wrote:
> I think OpenStack's position should be that it is the operator's choice how
> to assign/use addresses. And OpenStack's advice to the operators should be
> to follow the RFC (duh!).
Of course, I don't speak for OpenStack. This is my opinio
On Tue, Jan 12, 2016 at 11:32 AM, Dan Sneddon wrote:
> I can confirm that OpenStack doesn't have Carrier Grade NAT (CGN), but
> this RFC simply sets aside a set of addresses which can be used for CGN
> (100.64.0.0/10), and lays out some required and best practices for
> running a CGN network.
>
>
(Cross-posting to the operators list for feedback)
Thank you Ihar for starting this up. In the absence of any kind of
blog or other outlet of my own to disseminate this, let me share my
plans here...
Routed Networks:
My plans for Mitaka (and beyond) are around routed networks. During
Liberty,
Hi all,
Cross posting to openstack-dev and openstack-operators
We discussed supporting multiple types of routers within a Neutron in
the L3 meeting this morning [1]. The team would like more feedback
from the community in order to refine use cases and also to consider
possible approaches to achi
Jacob,
I don't have your original email from which to reply. So, hopefully
this finds you just as well. The bad news is that I don't have an
immediate answer to address this. However, I thought it was worth
mentioning where the future may lead.
I have been thinking about the scenario that you
14 matches
Mail list logo