gt;>>
>>>
>>> Thanks,
>>>
>>> John
>>>
>>>
>>>
>>> *From:* Pavlo Shchelokovskyy [mailto:pshchelokovs...@mirantis.com]
>>> *Sent:* Tuesday, November 14, 2017 8:16 AM
>>> *To:* OpenStack Develop
ay, November 14, 2017 8:16 AM
>> *To:* OpenStack Development Mailing List (not for usage questions) <
>> openstack-dev@lists.openstack.org>
>> *Subject:* [openstack-dev] [ironic] inclusion of
>> openstack/networking-generic-switch project under OpenStack baremetal
>>
hn
>
>
>
> *From:* Pavlo Shchelokovskyy [mailto:pshchelokovs...@mirantis.com]
> *Sent:* Tuesday, November 14, 2017 8:16 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* [openstack-dev] [ironic] inclusion of
&g
ubject: [openstack-dev] [ironic] inclusion of
openstack/networking-generic-switch project under OpenStack baremetal program
Hi all,
as this topic it was recently brought up in ironic IRC meeting, I'd like to
start a discussion on the subject.
A quick recap - networking-generic-switch project (n-g-s) wa
Hi!
Thanks for raising this.
On 11/14/2017 05:16 PM, Pavlo Shchelokovskyy wrote:
Hi all,
as this topic it was recently brought up in ironic IRC meeting, I'd like to
start a discussion on the subject.
A quick recap - networking-generic-switch project (n-g-s) was born out of
necessity to do
On Tue, Nov 14, 2017 at 9:16 AM, Pavlo Shchelokovskyy
wrote:
> As a core in n-g-s myself I'm happy with either 1) or 2), but not really
> fond of 3) as it kind of stretches the networking-baremetal scope too much
> IMHO.
Personally, I'm happy with 1 or 2. I
Hi all,
as this topic it was recently brought up in ironic IRC meeting, I'd like to
start a discussion on the subject.
A quick recap - networking-generic-switch project (n-g-s) was born out of
necessity to do two things:
- test the "network isolation for baremetal nodes" (a.k.a. multi-tenancy)