Hi, Nick, For “have a test case which can be verified using a an OpenSource implementation ….. ensure that tests can be done without any special hardware or proprietary software”, I totally agree the requirement for without proprietary software, however, I’m not sure about your exact meaing of “special hardware”.
I had a quick chat with Daniel in the summit on this also. Several NFV tasks, like large page, guest NUMA, SR-IOV, require hardware support. Those features are widely supported in volume servers already for a long time, but can’t be achieved, or can’t be achieved well, in VM yet, thus can’t be verified in current gate. IMHO, even VM can support/emulate such feature, it’s not so good to use VM to verify them. How about have a standard 3rd party CI test for hardware based feature testing and make it an extensible framework? I think there are requirement at least from both ironic and NFV? Our team have 3rd party CI test for PCI pass-through and OAT trusted computing, which can’t be achieved through CI now. These tests are based on real hardware environment instead of VM. We didn’t publish result yet because of some IT logistic support. Thanks --jyh From: Nicolas Barcet [mailto:[email protected]] Sent: Monday, May 19, 2014 10:19 AM To: openstack-dev Subject: [openstack-dev] [NFV] Mission statement prosal Hello, As promised during the second BoF session (thanks a lot to Chris Wright for leading this), here is a first try at defining the purpose of our special interest group. --- Mission statement for the OpenStack NFV Special Interest Group: The SIG aims to define and prioritize the use cases which are required to run Network Function Virtualization (NFV) instances on top of OpenStack. The requirements are to be passed on to various projects within OpenStack to promote their implementation. The requirements expressed by this group should be made so that each of them have a test case which can be verified using a an OpenSource implementation. This is to ensure that tests can be done without any special hardware or proprietary software, which is key for continuous integration tests in the OpenStack gate. --- Comments, suggestions and fixes are obviously welcome! Best, Nick
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
