Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Jeremy Stanley]

On 2016-03-22 12:49:32 -0700 (-0700), Remo Mattei wrote:
> hi guys I have been on this list for many months and have not
> being able to attend, can someone remind me when the meeting is? I
> would love to provide / help and share some tips. 

This was a one-time conference call (earlier today) with the data
center management at HPE to work out cabling and configuration
requirements for the hardware currently being relocated.
-- 
Jeremy Stanley

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Remo Mattei]

hi guys I have been on this list for many months and have not being able to 
attend, can someone remind me when the meeting is? I would love to provide / 
help and share some tips. 

Thanks 
> On Mar 22, 2016, at 12:19, Cody A.W. Somerville  
> wrote:
> 
> 
> 
> On Tue, Mar 22, 2016 at 3:07 PM, Paul Belanger  > wrote:
> On Tue, Mar 22, 2016 at 11:45:12AM -0700, Colleen Murphy wrote:
> > 3) how many vlans?
> >  - one untagged for pxe/management, one tagged for public
> >
> I had to drop off after this point, but did we talk about them (HP team) 
> wiring
> up 2 network interfaces, assuming our NICs support it?  I know we currently 
> are
> doing everything with a single interface.
> 
> Even if we continue to use the single NIC, asking to have the 2nd wired might 
> be
> worth it for down the road.
> 
> > 4) keep 10.10.16.0/24  for internal network
> >
> > 5) Do we need nic bonding?
> >  - no
> >
> 
> Agreed. I was going to make the same point. 
> 
> 
> -- 
> Cody A.W. Somerville
> !DSPAM:1,56f19b36257132002351958! 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
> 
> !DSPAM:1,56f19b36257132002351958!

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Cody A.W. Somerville]

On Tue, Mar 22, 2016 at 3:07 PM, Paul Belanger 
wrote:

> On Tue, Mar 22, 2016 at 11:45:12AM -0700, Colleen Murphy wrote:
> > 3) how many vlans?
> >  - one untagged for pxe/management, one tagged for public
> >
> I had to drop off after this point, but did we talk about them (HP team)
> wiring
> up 2 network interfaces, assuming our NICs support it?  I know we
> currently are
> doing everything with a single interface.
>
> Even if we continue to use the single NIC, asking to have the 2nd wired
> might be
> worth it for down the road.
>
> > 4) keep 10.10.16.0/24 for internal network
> >
> > 5) Do we need nic bonding?
> >  - no
> >


Agreed. I was going to make the same point.


-- 
Cody A.W. Somerville
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Paul Belanger]

On Tue, Mar 22, 2016 at 11:45:12AM -0700, Colleen Murphy wrote:
> On Mon, Mar 21, 2016 at 10:17 AM, Colleen Murphy 
> wrote:
> 
> > On Thu, Mar 17, 2016 at 11:48 AM, Colleen Murphy 
> > wrote:
> >
> >> The networking team at HPE received our request and would like to have a
> >> call next week to review it. Our liaison, Venu, should have a draft network
> >> diagram we can review. Who would like to join, and what times/days work
> >> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
> >> meeting).
> >>
> >> Colleen
> >>
> > A call has been scheduled for 1800-1845 UTC on Tuesday, March 22.
> > Invitations were sent out to folks who expressed interest in attending and
> > I can share the meeting phone number and conference ID with anyone who was
> > missed.
> >
> > Allison brought up using the asterisk server for the call and it was not
> > responded to - I suspect either they didn't understand or didn't feel
> > comfortable with it. It would be my preference to not push the issue, as
> > they are extending the invitation to us, not the other way around. Instead
> > I can commit to taking and dispersing detailed notes.
> >
> > Colleen
> >
> Notes from today's meeting:
> 
> 1) 1G or 10G?
>  - 10G useful for image transfers and mirrors in cloud
>  - Venu to connect with DC ops ensure 10G
> 
> 2) ipv6?
>  - Venu to ask verizon to activate /48 block, will take a couple of days
> 
> 3) how many vlans?
>  - one untagged for pxe/management, one tagged for public
> 
I had to drop off after this point, but did we talk about them (HP team) wiring
up 2 network interfaces, assuming our NICs support it?  I know we currently are
doing everything with a single interface.

Even if we continue to use the single NIC, asking to have the 2nd wired might be
worth it for down the road.

> 4) keep 10.10.16.0/24 for internal network
> 
> 5) Do we need nic bonding?
>  - no
> 
> 6) Any load balancing requirement?
>  - no
>  - if we were to add load balancing we would host it ourselves
> 
> 5) Access requirements?
>  - full inbound/outbound internet access - no ports blocked
>  - firewalls managed locally
> 
> The network diagram will need to have some parts redacted before we can
> share it publicly.
> 
> Colleen

> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Colleen Murphy]

On Mon, Mar 21, 2016 at 10:17 AM, Colleen Murphy 
wrote:

> On Thu, Mar 17, 2016 at 11:48 AM, Colleen Murphy 
> wrote:
>
>> The networking team at HPE received our request and would like to have a
>> call next week to review it. Our liaison, Venu, should have a draft network
>> diagram we can review. Who would like to join, and what times/days work
>> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
>> meeting).
>>
>> Colleen
>>
> A call has been scheduled for 1800-1845 UTC on Tuesday, March 22.
> Invitations were sent out to folks who expressed interest in attending and
> I can share the meeting phone number and conference ID with anyone who was
> missed.
>
> Allison brought up using the asterisk server for the call and it was not
> responded to - I suspect either they didn't understand or didn't feel
> comfortable with it. It would be my preference to not push the issue, as
> they are extending the invitation to us, not the other way around. Instead
> I can commit to taking and dispersing detailed notes.
>
> Colleen
>
Notes from today's meeting:

1) 1G or 10G?
 - 10G useful for image transfers and mirrors in cloud
 - Venu to connect with DC ops ensure 10G

2) ipv6?
 - Venu to ask verizon to activate /48 block, will take a couple of days

3) how many vlans?
 - one untagged for pxe/management, one tagged for public

4) keep 10.10.16.0/24 for internal network

5) Do we need nic bonding?
 - no

6) Any load balancing requirement?
 - no
 - if we were to add load balancing we would host it ourselves

5) Access requirements?
 - full inbound/outbound internet access - no ports blocked
 - firewalls managed locally

The network diagram will need to have some parts redacted before we can
share it publicly.

Colleen
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Anita Kuno]

On 03/17/2016 03:13 PM, Paul Belanger wrote:
> On Thu, Mar 17, 2016 at 03:10:25PM -0400, Anita Kuno wrote:
>> On 03/17/2016 03:05 PM, Paul Belanger wrote:
>>> On Thu, Mar 17, 2016 at 02:55:33PM -0400, Anita Kuno wrote:
 On 03/17/2016 02:48 PM, Colleen Murphy wrote:
> The networking team at HPE received our request and would like to have a
> call next week to review it. Our liaison, Venu, should have a draft 
> network
> diagram we can review. Who would like to join, and what times/days work
> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
> meeting).
>
> Colleen
>
>
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>

 Is there any possibility we can use asterisk? Then we can just dial in:
 https://wiki.openstack.org/wiki/Infrastructure/Conferencing

 Thanks Colleen for putting this together,
 Anita.

>>> I'd also like to suggest we record the audio, if people are okay with that. 
>>> This
>>> way people who cannot make the call will be able to review at a later date.
>>>
>>
>> I'm supportive of this suggestion. I've already tested asterisk for
>> recording and my experience is it works well. The issue raised last time
>> was where to store the audio file generated.
>>
>> Note, we would have to have permission of participants for recording. I
>> just got an audible "agreed" with the person saying their name when we
>> did it before.
>>
>> Last time I uploaded to afs after recording.
>>
> Right, we could default specific conference rooms in asterisk that record by
> default.  We'd also play a nice warning to each user explaining this.  After
> the conference room was deleted, we'd then sync the recording to some 
> location.
> 
> There might not be enough time to do all that for this call, but moving 
> forward
> it would be an option.

That sounds reasonable. Yeah we just need something to cover off privacy
laws about recording for various countries. The warning should satisfy
informed consent.

Thanks,
Anita.

> 
>> Thanks Paul,
>> Anita.


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Colleen Murphy]

The networking team at HPE received our request and would like to have a
call next week to review it. Our liaison, Venu, should have a draft network
diagram we can review. Who would like to join, and what times/days work
best? I would propose Tuesday at 1800 UTC (one hour before the Infra
meeting).

Colleen
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Paul Belanger]

On Thu, Mar 17, 2016 at 03:10:25PM -0400, Anita Kuno wrote:
> On 03/17/2016 03:05 PM, Paul Belanger wrote:
> > On Thu, Mar 17, 2016 at 02:55:33PM -0400, Anita Kuno wrote:
> >> On 03/17/2016 02:48 PM, Colleen Murphy wrote:
> >>> The networking team at HPE received our request and would like to have a
> >>> call next week to review it. Our liaison, Venu, should have a draft 
> >>> network
> >>> diagram we can review. Who would like to join, and what times/days work
> >>> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
> >>> meeting).
> >>>
> >>> Colleen
> >>>
> >>>
> >>>
> >>> ___
> >>> OpenStack-Infra mailing list
> >>> OpenStack-Infra@lists.openstack.org
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> >>>
> >>
> >> Is there any possibility we can use asterisk? Then we can just dial in:
> >> https://wiki.openstack.org/wiki/Infrastructure/Conferencing
> >>
> >> Thanks Colleen for putting this together,
> >> Anita.
> >>
> > I'd also like to suggest we record the audio, if people are okay with that. 
> > This
> > way people who cannot make the call will be able to review at a later date.
> > 
> 
> I'm supportive of this suggestion. I've already tested asterisk for
> recording and my experience is it works well. The issue raised last time
> was where to store the audio file generated.
> 
> Note, we would have to have permission of participants for recording. I
> just got an audible "agreed" with the person saying their name when we
> did it before.
> 
> Last time I uploaded to afs after recording.
> 
Right, we could default specific conference rooms in asterisk that record by
default.  We'd also play a nice warning to each user explaining this.  After
the conference room was deleted, we'd then sync the recording to some location.

There might not be enough time to do all that for this call, but moving forward
it would be an option.

> Thanks Paul,
> Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Anita Kuno]

On 03/17/2016 02:48 PM, Colleen Murphy wrote:
> The networking team at HPE received our request and would like to have a
> call next week to review it. Our liaison, Venu, should have a draft network
> diagram we can review. Who would like to join, and what times/days work
> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
> meeting).
> 
> Colleen
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

Is there any possibility we can use asterisk? Then we can just dial in:
https://wiki.openstack.org/wiki/Infrastructure/Conferencing

Thanks Colleen for putting this together,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Ricardo Carrillo Cruz]

Works for me, I'll attend.

Regards

2016-03-17 22:11 GMT+01:00 Yolanda Robla Mota :

> Works for me, thanks!
>
> El 17/03/16 a las 19:48, Colleen Murphy escribió:
>
> The networking team at HPE received our request and would like to have a
> call next week to review it. Our liaison, Venu, should have a draft network
> diagram we can review. Who would like to join, and what times/days work
> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
> meeting).
>
> Colleen
>
>
> ___
> OpenStack-Infra mailing 
> listOpenStack-Infra@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
>
> --
> Yolanda Robla Mota
> Cloud Automation and Distribution Engineer+34 
> 605641639yolanda.robla-m...@hpe.com
>
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
>
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Paul Belanger]

On Thu, Mar 17, 2016 at 02:55:33PM -0400, Anita Kuno wrote:
> On 03/17/2016 02:48 PM, Colleen Murphy wrote:
> > The networking team at HPE received our request and would like to have a
> > call next week to review it. Our liaison, Venu, should have a draft network
> > diagram we can review. Who would like to join, and what times/days work
> > best? I would propose Tuesday at 1800 UTC (one hour before the Infra
> > meeting).
> > 
> > Colleen
> > 
> > 
> > 
> > ___
> > OpenStack-Infra mailing list
> > OpenStack-Infra@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> > 
> 
> Is there any possibility we can use asterisk? Then we can just dial in:
> https://wiki.openstack.org/wiki/Infrastructure/Conferencing
> 
> Thanks Colleen for putting this together,
> Anita.
> 
I'd also like to suggest we record the audio, if people are okay with that. This
way people who cannot make the call will be able to review at a later date.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Anita Kuno]

On 03/17/2016 03:05 PM, Paul Belanger wrote:
> On Thu, Mar 17, 2016 at 02:55:33PM -0400, Anita Kuno wrote:
>> On 03/17/2016 02:48 PM, Colleen Murphy wrote:
>>> The networking team at HPE received our request and would like to have a
>>> call next week to review it. Our liaison, Venu, should have a draft network
>>> diagram we can review. Who would like to join, and what times/days work
>>> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
>>> meeting).
>>>
>>> Colleen
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>>
>> Is there any possibility we can use asterisk? Then we can just dial in:
>> https://wiki.openstack.org/wiki/Infrastructure/Conferencing
>>
>> Thanks Colleen for putting this together,
>> Anita.
>>
> I'd also like to suggest we record the audio, if people are okay with that. 
> This
> way people who cannot make the call will be able to review at a later date.
> 

I'm supportive of this suggestion. I've already tested asterisk for
recording and my experience is it works well. The issue raised last time
was where to store the audio file generated.

Note, we would have to have permission of participants for recording. I
just got an audible "agreed" with the person saying their name when we
did it before.

Last time I uploaded to afs after recording.

Thanks Paul,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Yolanda Robla Mota]

Works for me, thanks!

El 17/03/16 a las 19:48, Colleen Murphy escribió:
The networking team at HPE received our request and would like to have 
a call next week to review it. Our liaison, Venu, should have a draft 
network diagram we can review. Who would like to join, and what 
times/days work best? I would propose Tuesday at 1800 UTC (one hour 
before the Infra meeting).


Colleen


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


--
Yolanda Robla Mota
Cloud Automation and Distribution Engineer
+34 605641639
yolanda.robla-m...@hpe.com

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Jeremy Stanley]

On 2016-03-17 23:20:11 +0100 (+0100), Ricardo Carrillo Cruz wrote:
> Works for me, I'll attend.

Yes, I'm available for 1800 UTC Tuesday if we can keep it to an
hour, since our OpenStack Infra team meeting starts at 1900.
-- 
Jeremy Stanley

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Jeremy Stanley]

On 2016-02-29 14:29:34 -0800 (-0800), Colleen Murphy wrote:
> On Mon, Feb 29, 2016 at 1:13 PM, Colleen Murphy  wrote:
> > So the request I'm going to send off is:
> >
> > -  "LR5" HPE network for direct connectivity to the Internet
> > - Private management network for management and iLO
> >
> Updated: Private management network for management and iLO, which needs to
> be reachable from our nodes
> 
> >
> > - Ideally, two drops for the private management network and the public
> > network, but at a minimum one drop with one tagged and one untagged network
> > - Allocation of /19 IP network block for IPv4 and a /48 for IPv6 within
> > the LR5 network
> > - Reverse DNS for both network blocks delegated to (yet to be identified)
> > nameservers under our control

Looks great--thanks for rounding that list up!
-- 
Jeremy Stanley

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Colleen Murphy]

On Mon, Feb 29, 2016 at 1:13 PM, Colleen Murphy  wrote:

> On Thu, Feb 25, 2016 at 7:40 PM, Jeremy Stanley  wrote:
>
>> On 2016-02-25 17:05:57 -0700 (-0700), Cody A.W. Somerville wrote:
>> [...]
>> > - Allocation of /19 IP network block.
>> [...]
>>
>> Ideally also a /48 of IPv6 addresses routed to the same environment.
>>
>> Oh, and we're going to want reverse DNS for both the IPv4 /19 and
>> IPv6 /48 delegated to (yet to be identified) nameservers under our
>> control.
>>
>> So the request I'm going to send off is:
>
> -  "LR5" HPE network for direct connectivity to the Internet
> - Private management network for management and iLO
>
Updated: Private management network for management and iLO, which needs to
be reachable from our nodes

>
> - Ideally, two drops for the private management network and the public
> network, but at a minimum one drop with one tagged and one untagged network
> - Allocation of /19 IP network block for IPv4 and a /48 for IPv6 within
> the LR5 network
> - Reverse DNS for both network blocks delegated to (yet to be identified)
> nameservers under our control
>
> Colleen
>
>
>
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Colleen Murphy]

On Thu, Feb 25, 2016 at 7:40 PM, Jeremy Stanley  wrote:

> On 2016-02-25 17:05:57 -0700 (-0700), Cody A.W. Somerville wrote:
> [...]
> > - Allocation of /19 IP network block.
> [...]
>
> Ideally also a /48 of IPv6 addresses routed to the same environment.
>
> Oh, and we're going to want reverse DNS for both the IPv4 /19 and
> IPv6 /48 delegated to (yet to be identified) nameservers under our
> control.
>
> So the request I'm going to send off is:

-  "LR5" HPE network for direct connectivity to the Internet
- Private management network for management and iLO
- Ideally, two drops for the private management network and the public
network, but at a minimum one drop with one tagged and one untagged network
- Allocation of /19 IP network block for IPv4 and a /48 for IPv6 within the
LR5 network
- Reverse DNS for both network blocks delegated to (yet to be identified)
nameservers under our control

Colleen
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Jeremy Stanley]

On 2016-02-25 17:05:57 -0700 (-0700), Cody A.W. Somerville wrote:
[...]
> - Allocation of /19 IP network block.
[...]

Ideally also a /48 of IPv6 addresses routed to the same environment.

Oh, and we're going to want reverse DNS for both the IPv4 /19 and
IPv6 /48 delegated to (yet to be identified) nameservers under our
control.
-- 
Jeremy Stanley

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Cody A.W. Somerville]

HPE provides a number of baremetal nodes in two of their public cloud data
centers, referred to as "US East" and "US West", for the infracloud
project. As part of the sunset of HPE's public cloud, this hardware needs
to be relocated. HPE has determined both sets of hardware will be relocated
to their ecopod data centers in Houston, Texas. This e-mail is to discuss
and review the networking requirements that we will communicate to HPE for
post-relocation deployment.

- "LR5" HPE network - this means direct connectivity to the Internet.
- Allocation of /19 IP network block.
- Private management network for management and ilo.
- Provider network using the 10G cards (some seem to have Mellanox
infiniband).

Best regards,

Cody
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra