Hi Carl.
Adding some numbers from CERN to the discussion, we currently have:
* ~40 cells
* ~185 segments (called clusters in the our doc linked in the etherpad)
* ~185*10 subnets, although it's not easy to compute the actual number
today in our nova-network setup
With the move to neutron (new cel
>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.
The DHCP agent doesn't create a port per subnet. It only creates a port per
network and adds extra IPs to that port as extra subnets are added to the
network.
In the
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.
>
Hi,
thanks Carl for info about the DHCP plans.
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.
In our infrastructure we only consider a network with several hundred
subnets.
By default the DHCP agent runs in the net
> On 26 Feb 2016, at 9:20 AM, Carl Baldwin wrote:
>
> (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 indir
To follow up on the relay idea. In our implementation we have looked at trying
to enable ip_helper on the switches to forward dhcp to a set of defined neutron
dhcp servers. The issue is that this turns the dhcp requests from a broadcast
packet to a unicast packet. With the default way neutron
(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
There is also a bit of info on cells from the Manchester meetup in the Large
Deployment team ether pad:
https://etherpad.openstack.org/p/MAN-ops-Large-Deployment-Team
I've added the link to the cells etherpad.
--Rocky
___
OpenStack-operators mailing l
The CERN guys had some concerns on how dhcp was working in a segment
environment. I’ll leave them to give details.
Tim
On 25/02/16 14:53, "Andrew Laski" wrote:
>
>
>On Thu, Feb 25, 2016, at 05:01 AM, Tim Bell wrote:
>>
>> CERN info added.. Feel free to come back for more information if n
On Thu, Feb 25, 2016, at 05:01 AM, Tim Bell wrote:
>
> CERN info added.. Feel free to come back for more information if needed.
An additional piece of information we're specifically interested in from
all cellsv1 deployments is around the networking control plane setup. Is
there a single nova-n
On 25 February 2016 at 10:01, Tim Bell wrote:
>
> CERN info added.. Feel free to come back for more information if needed.
>
> Tim
> On 24/02/16 22:47, "Edgar Magana" wrote:
>
>>It will be awesome if we can add this doc into the networking guide :-)
>>
>>
>>Edgar
>>
>>On 2/24/16, 1:42 PM, "Matt
CERN info added.. Feel free to come back for more information if needed.
Tim
On 24/02/16 22:47, "Edgar Magana" wrote:
>It will be awesome if we can add this doc into the networking guide :-)
>
>
>Edgar
>
>
>
>
>On 2/24/16, 1:42 PM, "Matt Riedemann" wrote:
>
>>The nova and neutron teams ar
It will be awesome if we can add this doc into the networking guide :-)
Edgar
On 2/24/16, 1:42 PM, "Matt Riedemann" wrote:
>The nova and neutron teams are trying to sort out existing deployment
>network scenarios for cells v1 so we can try and document some of that
>and get an idea if th
The nova and neutron teams are trying to sort out existing deployment
network scenarios for cells v1 so we can try and document some of that
and get an idea if things change at all with cells v2.
Therefore we're asking that deployers running cells please document
anything you can in an etherpa
14 matches
Mail list logo
