Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

2015-11-27 Thread Kevin Benton 
> I don't see any reason why it wouldn't work with VXLAN.Well with the current approach in your code you would have to basically re-implement all of the logic in the openvswitch agent that sets up VXLAN tunnels and isolation of nodes on different VXLAN networks (either via flows or local VLANs). That will be quite a bit of work.We can already leverage the L2 agent’s logic if, instead of setting VLANs/VXLANs directly in your driver, we just wire up a patch port to br-int using the correct name that the L2 agent expects for the Neutron port the bare metal VM has. Then the L2 agent does its normal logic to get the traffic onto the right VLAN/VXLAN/GRE/whatever.On Nov 26, 2015, at 2:56 AM, Vasyl Saienko  wrote:Hello Kevin,I've added some pictures that illustrates how it works with HW switch and with VMs on devstack. On Wed, Nov 25, 2015 at 10:53 PM, Kevin Benton  wrote:This is cool. I didn't know you were working on an OVS driver for testing in CI as well. :)Does this work by getting the port wired into OVS so the agent recognizes it like a regular port so it can be put into VXLAN/VLAN or whatever the node is configured with? From what I can tell it looks like it's on a completely different bridge so they wouldn't have connectivity to the rest of the network.Driver works with VLAN at the moment, I don't see any reason why it wouldn't work with VXLAN.Ironic VMs are created on devstack by [0]. They are not registered in Nova/Neutron so neutron-ovs-agent doesn't know anything about them.In single node devstack you can't launch regular nova VM instances since compute_driver=ironic doesn't allow this. They would have connectivity to rest of network via 'br-int'.I have some POC code[1] for 'baremetal' support directly in the OVS agent so ports get treated just like VM ports. However, it requires upstream changes so if yours accomplishes the same thing without any upstream changes, that will be the best way to go. In real setup neutron will plug baremetal server to specific network via ML2 driver.We should keep as much closer to real ironic use-case scenario in testing model. That is why we should have ML2 that allows us to interact with OVS. Perhaps we can merge your approach (config via ssh) with mine (getting the 'baremetal' ports wired up for real connectivity) so we don't need upstream changes.1. https://review.openstack.org/#/c/249265/Cheers,Kevin BentonOn Wed, Nov 25, 2015 at 7:27 AM, Vasyl Saienko  wrote:Hello Community,As you know Ironic/Neutron integration is planned in Mitaka. And at the moment we don't have any CI that will test it. Unfortunately we can't test Ironic/Neutron integration on HW as we don't have it.So probably the best way is to develop ML2 driver that will work with OVS.At the moment we have a PoC [1] of ML2 driver that works with Cisco and OVS on linux.Also we have some patches to devstack that allows to try Ironic/Neutron integration on VM and real HW. And quick guide how to test it locally [0]https://review.openstack.org/#/c/247513/https://review.openstack.org/#/c/248048/https://review.openstack.org/#/c/249717/https://review.openstack.org/#/c/248074/ I'm interested in Neutron/Ironic integration. It would be great if we have it in Mitaka.I'm asking Community to check [0] and [1] and share your thoughts. Also I would like to request a repo on openstack.org for [1][0] https://github.com/jumpojoy/ironic-neutron/blob/master/devstack/examples/ironic-neutron-vm.md[1] https://github.com/jumpojoy/generic_switch--SincerelyVasyl Saienko__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev-- Kevin Benton__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev[0] https://github.com/openstack-dev/devstack/blob/master/tools/ironic/scripts/create-node[1] https://review.openstack.org/#/c/249717--SincerelyVasyl Saienko__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

2015-11-26 Thread Yuriy Yekovenko 
Hi All,

Just want to notify that I've created tempest bug [0] to verify Ironic
multitenancy and going to work on it.
Please let me know if you have any comments/suggestions regarding the test
scenario described there.

[0] https://bugs.launchpad.net/tempest/+bug/1520230

Best regards,
Yuriy Yekovenko
Senior QA Engineer
Mirantis Inc

On Thu, Nov 26, 2015 at 1:39 PM, Vasyl Saienko 
wrote:

> Hi Sukhdev,
>
> I didn't have a change to be present on previous meeting due to personal
> reasons, but I will be on next meeting.
> It is important to keep CI testing as much possible closer to real Ironic
> use-case scenario.
>
> At the moment we don't have any test-case that covers ironic/neutron
> integration in tempests.
> I think it is nice time to discuss it. So my vision of ironic/neutron
> test-case is next:
>
> 1. Setup Devstack with 3 ironic nodes
> 2. In project: *demo *
>
>- create a network 10.0.100.0/24
>- boot vm on it with fixed ip 10.0.100.10
>- boot vm2 on it with fixed ip 10.0.100.11
>
> 3. In project: *alt_demo*
>
>- create network 10.0.100.0/24 with same prefix as in project *demo *
>- boot vm on it with fixed ip 10.0.100.20
>
> 4. Wait for both instances become active
>
> 5. Check that we *can't* ping *demo: vm* from *alt_demo vm*
>
> 6. Check that we *can* access to vm1 from vm in project demo
>
> 7. Make sure that there is no packets with MAC of *alt_demo vm *on *demo:
> vm *(can use tcpdump)
> --
> Sincerely
> Vasyl Saienko
>
> On Wed, Nov 25, 2015 at 11:06 PM, Sukhdev Kapur 
> wrote:
>
>> Hi Vasyl,
>>
>> This is great. Kevin and I was working on the similar thing. I just
>> finished testing his patch and gave a +1.
>> This is a missing (and needed) functionality for getting the
>> Ironic/Neutron integration completed.
>>
>> As Kevin suggests, it will be best if we can combine these approaches and
>> come up with the best solution.
>>
>> If you are available, please join us in our next weekly meeting at 8AM
>> (pacific time) at #openstack-meeting-4.
>> I am sure team will be excited to know about this solution and this will
>> give an opportunity to make sure we cover all angles of this testing.
>>
>> Thanks
>> -Sukhdev
>>
>>
>> On Wed, Nov 25, 2015 at 7:27 AM, Vasyl Saienko 
>> wrote:
>>
>>> Hello Community,
>>>
>>> As you know Ironic/Neutron integration is planned in Mitaka. And at the
>>> moment we don't have any CI that will test it. Unfortunately we can't test
>>> Ironic/Neutron integration on HW as we don't have it.
>>> So probably the best way is to develop ML2 driver that will work with
>>> OVS.
>>>
>>> At the moment we have a PoC [1] of ML2 driver that works with Cisco and
>>> OVS on linux.
>>> Also we have some patches to devstack that allows to try Ironic/Neutron
>>> integration on VM and real HW. And quick guide how to test it locally [0]
>>>
>>> https://review.openstack.org/#/c/247513/
>>> https://review.openstack.org/#/c/248048/
>>> https://review.openstack.org/#/c/249717/
>>> https://review.openstack.org/#/c/248074/
>>>
>>> I'm interested in Neutron/Ironic integration. It would be great if we
>>> have it in Mitaka.
>>> I'm asking Community to check [0] and [1] and share your thoughts.
>>>
>>>  Also I would like to request a repo on openstack.org for [1]
>>>
>>>
>>> [0]
>>> https://github.com/jumpojoy/ironic-neutron/blob/master/devstack/examples/ironic-neutron-vm.md
>>> [1] https://github.com/jumpojoy/generic_switch
>>>
>>> --
>>> Sincerely
>>> Vasyl Saienko
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

2015-11-26 Thread Vasyl Saienko 
Hi Sukhdev,

I didn't have a change to be present on previous meeting due to personal
reasons, but I will be on next meeting.
It is important to keep CI testing as much possible closer to real Ironic
use-case scenario.

At the moment we don't have any test-case that covers ironic/neutron
integration in tempests.
I think it is nice time to discuss it. So my vision of ironic/neutron
test-case is next:

1. Setup Devstack with 3 ironic nodes
2. In project: *demo *

   - create a network 10.0.100.0/24
   - boot vm on it with fixed ip 10.0.100.10
   - boot vm2 on it with fixed ip 10.0.100.11

3. In project: *alt_demo*

   - create network 10.0.100.0/24 with same prefix as in project *demo *
   - boot vm on it with fixed ip 10.0.100.20

4. Wait for both instances become active

5. Check that we *can't* ping *demo: vm* from *alt_demo vm*

6. Check that we *can* access to vm1 from vm in project demo

7. Make sure that there is no packets with MAC of *alt_demo vm *on *demo:
vm *(can use tcpdump)
--
Sincerely
Vasyl Saienko

On Wed, Nov 25, 2015 at 11:06 PM, Sukhdev Kapur 
wrote:

> Hi Vasyl,
>
> This is great. Kevin and I was working on the similar thing. I just
> finished testing his patch and gave a +1.
> This is a missing (and needed) functionality for getting the
> Ironic/Neutron integration completed.
>
> As Kevin suggests, it will be best if we can combine these approaches and
> come up with the best solution.
>
> If you are available, please join us in our next weekly meeting at 8AM
> (pacific time) at #openstack-meeting-4.
> I am sure team will be excited to know about this solution and this will
> give an opportunity to make sure we cover all angles of this testing.
>
> Thanks
> -Sukhdev
>
>
> On Wed, Nov 25, 2015 at 7:27 AM, Vasyl Saienko 
> wrote:
>
>> Hello Community,
>>
>> As you know Ironic/Neutron integration is planned in Mitaka. And at the
>> moment we don't have any CI that will test it. Unfortunately we can't test
>> Ironic/Neutron integration on HW as we don't have it.
>> So probably the best way is to develop ML2 driver that will work with OVS.
>>
>> At the moment we have a PoC [1] of ML2 driver that works with Cisco and
>> OVS on linux.
>> Also we have some patches to devstack that allows to try Ironic/Neutron
>> integration on VM and real HW. And quick guide how to test it locally [0]
>>
>> https://review.openstack.org/#/c/247513/
>> https://review.openstack.org/#/c/248048/
>> https://review.openstack.org/#/c/249717/
>> https://review.openstack.org/#/c/248074/
>>
>> I'm interested in Neutron/Ironic integration. It would be great if we
>> have it in Mitaka.
>> I'm asking Community to check [0] and [1] and share your thoughts.
>>
>>  Also I would like to request a repo on openstack.org for [1]
>>
>>
>> [0]
>> https://github.com/jumpojoy/ironic-neutron/blob/master/devstack/examples/ironic-neutron-vm.md
>> [1] https://github.com/jumpojoy/generic_switch
>>
>> --
>> Sincerely
>> Vasyl Saienko
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

2015-11-26 Thread Vasyl Saienko 
Hello Kevin,

I've added some pictures that illustrates how it works with HW switch and
with VMs on devstack.


On Wed, Nov 25, 2015 at 10:53 PM, Kevin Benton  wrote:

> This is cool. I didn't know you were working on an OVS driver for testing
> in CI as well. :)
>
> Does this work by getting the port wired into OVS so the agent recognizes
> it like a regular port so it can be put into VXLAN/VLAN or whatever the
> node is configured with? From what I can tell it looks like it's on a
> completely different bridge so they wouldn't have connectivity to the rest
> of the network.
>
> Driver works with VLAN at the moment, I don't see any reason why it
wouldn't work with VXLAN.
Ironic VMs are created on devstack by [0]. They are not registered in
Nova/Neutron so neutron-ovs-agent doesn't know anything about them.
In single node devstack you can't launch regular nova VM instances since
compute_driver=ironic doesn't allow this. They would have connectivity to
rest of network via 'br-int'.

I have some POC code[1] for 'baremetal' support directly in the OVS agent
> so ports get treated just like VM ports. However, it requires upstream
> changes so if yours accomplishes the same thing without any upstream
> changes, that will be the best way to go.
>
>
In real setup neutron will plug baremetal server to specific network via
ML2 driver.
We should keep as much closer to real ironic use-case scenario in testing
model. That is why we should have ML2 that allows us to interact with OVS.


> Perhaps we can merge your approach (config via ssh) with mine (getting the
> 'baremetal' ports wired up for real connectivity) so we don't need upstream
> changes.
>
> 1. https://review.openstack.org/#/c/249265/
>
> Cheers,
> Kevin Benton
>
> On Wed, Nov 25, 2015 at 7:27 AM, Vasyl Saienko 
> wrote:
>
>> Hello Community,
>>
>> As you know Ironic/Neutron integration is planned in Mitaka. And at the
>> moment we don't have any CI that will test it. Unfortunately we can't test
>> Ironic/Neutron integration on HW as we don't have it.
>> So probably the best way is to develop ML2 driver that will work with OVS.
>>
>> At the moment we have a PoC [1] of ML2 driver that works with Cisco and
>> OVS on linux.
>> Also we have some patches to devstack that allows to try Ironic/Neutron
>> integration on VM and real HW. And quick guide how to test it locally [0]
>>
>> https://review.openstack.org/#/c/247513/
>> https://review.openstack.org/#/c/248048/
>> https://review.openstack.org/#/c/249717/
>> https://review.openstack.org/#/c/248074/
>>
>> I'm interested in Neutron/Ironic integration. It would be great if we
>> have it in Mitaka.
>> I'm asking Community to check [0] and [1] and share your thoughts.
>>
>>  Also I would like to request a repo on openstack.org for [1]
>>
>>
>> [0]
>> https://github.com/jumpojoy/ironic-neutron/blob/master/devstack/examples/ironic-neutron-vm.md
>> [1] https://github.com/jumpojoy/generic_switch
>>
>> --
>> Sincerely
>> Vasyl Saienko
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Kevin Benton
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
[0]
https://github.com/openstack-dev/devstack/blob/master/tools/ironic/scripts/create-node
[1] https://review.openstack.org/#/c/249717

--
Sincerely
Vasyl Saienko
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

2015-11-25 Thread Sukhdev Kapur 
Hi Vasyl,

This is great. Kevin and I was working on the similar thing. I just
finished testing his patch and gave a +1.
This is a missing (and needed) functionality for getting the Ironic/Neutron
integration completed.

As Kevin suggests, it will be best if we can combine these approaches and
come up with the best solution.

If you are available, please join us in our next weekly meeting at 8AM
(pacific time) at #openstack-meeting-4.
I am sure team will be excited to know about this solution and this will
give an opportunity to make sure we cover all angles of this testing.

Thanks
-Sukhdev


On Wed, Nov 25, 2015 at 7:27 AM, Vasyl Saienko 
wrote:

> Hello Community,
>
> As you know Ironic/Neutron integration is planned in Mitaka. And at the
> moment we don't have any CI that will test it. Unfortunately we can't test
> Ironic/Neutron integration on HW as we don't have it.
> So probably the best way is to develop ML2 driver that will work with OVS.
>
> At the moment we have a PoC [1] of ML2 driver that works with Cisco and
> OVS on linux.
> Also we have some patches to devstack that allows to try Ironic/Neutron
> integration on VM and real HW. And quick guide how to test it locally [0]
>
> https://review.openstack.org/#/c/247513/
> https://review.openstack.org/#/c/248048/
> https://review.openstack.org/#/c/249717/
> https://review.openstack.org/#/c/248074/
>
> I'm interested in Neutron/Ironic integration. It would be great if we have
> it in Mitaka.
> I'm asking Community to check [0] and [1] and share your thoughts.
>
>  Also I would like to request a repo on openstack.org for [1]
>
>
> [0]
> https://github.com/jumpojoy/ironic-neutron/blob/master/devstack/examples/ironic-neutron-vm.md
> [1] https://github.com/jumpojoy/generic_switch
>
> --
> Sincerely
> Vasyl Saienko
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

2015-11-25 Thread Kevin Benton 
This is cool. I didn't know you were working on an OVS driver for testing
in CI as well. :)

Does this work by getting the port wired into OVS so the agent recognizes
it like a regular port so it can be put into VXLAN/VLAN or whatever the
node is configured with? From what I can tell it looks like it's on a
completely different bridge so they wouldn't have connectivity to the rest
of the network.

I have some POC code[1] for 'baremetal' support directly in the OVS agent
so ports get treated just like VM ports. However, it requires upstream
changes so if yours accomplishes the same thing without any upstream
changes, that will be the best way to go.

Perhaps we can merge your approach (config via ssh) with mine (getting the
'baremetal' ports wired up for real connectivity) so we don't need upstream
changes.

1. https://review.openstack.org/#/c/249265/

Cheers,
Kevin Benton

On Wed, Nov 25, 2015 at 7:27 AM, Vasyl Saienko 
wrote:

> Hello Community,
>
> As you know Ironic/Neutron integration is planned in Mitaka. And at the
> moment we don't have any CI that will test it. Unfortunately we can't test
> Ironic/Neutron integration on HW as we don't have it.
> So probably the best way is to develop ML2 driver that will work with OVS.
>
> At the moment we have a PoC [1] of ML2 driver that works with Cisco and
> OVS on linux.
> Also we have some patches to devstack that allows to try Ironic/Neutron
> integration on VM and real HW. And quick guide how to test it locally [0]
>
> https://review.openstack.org/#/c/247513/
> https://review.openstack.org/#/c/248048/
> https://review.openstack.org/#/c/249717/
> https://review.openstack.org/#/c/248074/
>
> I'm interested in Neutron/Ironic integration. It would be great if we have
> it in Mitaka.
> I'm asking Community to check [0] and [1] and share your thoughts.
>
>  Also I would like to request a repo on openstack.org for [1]
>
>
> [0]
> https://github.com/jumpojoy/ironic-neutron/blob/master/devstack/examples/ironic-neutron-vm.md
> [1] https://github.com/jumpojoy/generic_switch
>
> --
> Sincerely
> Vasyl Saienko
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Kevin Benton
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

2015-11-25 Thread Vasyl Saienko 
Hello Community,

As you know Ironic/Neutron integration is planned in Mitaka. And at the
moment we don't have any CI that will test it. Unfortunately we can't test
Ironic/Neutron integration on HW as we don't have it.
So probably the best way is to develop ML2 driver that will work with OVS.

At the moment we have a PoC [1] of ML2 driver that works with Cisco and OVS
on linux.
Also we have some patches to devstack that allows to try Ironic/Neutron
integration on VM and real HW. And quick guide how to test it locally [0]

https://review.openstack.org/#/c/247513/
https://review.openstack.org/#/c/248048/
https://review.openstack.org/#/c/249717/
https://review.openstack.org/#/c/248074/

I'm interested in Neutron/Ironic integration. It would be great if we have
it in Mitaka.
I'm asking Community to check [0] and [1] and share your thoughts.

 Also I would like to request a repo on openstack.org for [1]


[0]
https://github.com/jumpojoy/ironic-neutron/blob/master/devstack/examples/ironic-neutron-vm.md
[1] https://github.com/jumpojoy/generic_switch

--
Sincerely
Vasyl Saienko
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev