Open Stack

> -----Original Message-----
> From: Vladik Romanovsky [mailto:vladik.romanovsky at enovance.com]
> Sent: Wednesday, January 28, 2015 4:10 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova][NFV][qa] Testing NUMA, CPU pinning
> and large pages
> 
> 
> 
> ----- Original Message -----
> > From: "Steve Gordon" <sgordon at redhat.com>
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > <openstack-dev at lists.openstack.org>
> > Sent: Tuesday, 27 January, 2015 9:46:44 AM
> > Subject: Re: [openstack-dev] [nova][NFV][qa] Testing NUMA, CPU pinning
> > and large pages
> >
> > ----- Original Message -----
> > > From: "Vladik Romanovsky" <vladik.romanovsky at enovance.com>
> > > To: openstack-dev at lists.openstack.org
> > >
> > > Hi everyone,
> > >
> > > Following Steve Gordon's email [1], regarding CI for NUMA, SR-IOV,
> > > and other features, I'd like to start a discussion about the NUMA
> > > testing in particular.
> > >
> > > Recently we have started a work to test some of these features.
> > > The current plan is to use the functional tests, in the Nova tree,
> > > to exercise the code paths for NFV use cases. In general, these will
> > > contain tests to cover various scenarios regarding NUMA, CPU
> > > pinning, large pages and validate a correct placement/scheduling.
> >
> > Hi Vladik,
> >
> > There was some discussion of the above at the Nova mid-cycle
> > yesterday, are you able to give a quick update on any progress with
> > regards to creation of the above functional tests?
> >
> 
> I have a some progress, however, currently I have some challenges with
> validating the scheduler filters outcome. I'll try to post some of it in the
> coming days.
> 
> > > In addition to the functional tests in Nova, we have also proposed
> > > two basic scenarios in Tempest [2][3]. One to make sure that an
> > > instance can boot with a minimal NUMA configuration (a topology that
> > > every host should have) and one that would request an "impossible"
> > > topology and fail with an expected exception.
> >
> > We also discussed the above tempest changes and they will likely
> > receive some more review cycles as a result of this discussion but it
> > looks like there is already some feedback from Nikola that needs to be
> > addressed. More broadly for the list it looks like we need to
> > determine whether adding a negative test in this case is a valid/desireable
> use of Tempest.
> 
> I have updated the tempest tests yesterday. The tests were waiting on a
> nova patch to be merged:
>     https://review.openstack.org/#/c/145312
> 
> However, unfortunately, I've discovered another bug in nova that prevents
> the tests from passing, somehow I missed it in the previous attempt:
>     https://review.openstack.org/#/c/150694
> 	
> Thanks,
> Vladik
> 
> >
> > Thanks,
> >
> > Steve
> >
> >

Hi Folks,

I just wanted to share some details on the Intel CI testing strategy for NFV. 

You will see two Intel CIs commenting:
#1: Intel-PCI-CI
- Yongli He and Shane Wang are leading this effort for us. 
- The focus in this environment is on PCIe and SR-IOV specific testing.
- Commenting back to review.openstack.org has started.

#2: Intel-Networking-CI
- Waldemar Znoinski is leading this effort for us.
- This is really two separate environments under the hood. 
- The focus of one environment is on our new Neutron ML2 mechanism driver that is in development on stackforge for ovs accelerated with DPDK (i.e. networking-ovs-dpdk). This environment is containers based and commenting back to review.openstack.org has started.
- The focus of the second environment is on NUMA (CPU & I/O), CPU pinning and Huge Pages. The tests will be executed on bare-metal based environment and the plan is to have the tests run on this environment commenting back in a few weeks.

The combination of PCIe + SR-IOV + NUMA (CPU & I/O) + CPU Pinning + Huge Pages + networking-ovs-dpdk (mech driver) represents our contribution to NFV testing and we think should cover the NFV extensions going into Kilo that require a CI environment. We would really welcome your feedback on this.

We will leverage as many of the related tests as possible that are submitted upstream, so the ones noted by Vladik above are of particular interest.

Regards,
Adrian


> __________________________________________________________
> ____________
> > ____ OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > OpenStack-dev-request at 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-
> request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--------------------------------------------------------------
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.