On Mon, Nov 17, 2014 at 1:29 PM, Ian Wells <ijw.ubu...@cack.org.uk> wrote:
> On 12 November 2014 11:11, Steve Gordon <sgor...@redhat.com> wrote: > > NUMA >> ==== >> >> We still need to identify some hardware to run third party CI for the >> NUMA-related work, and no doubt other things that will come up. It's >> expected that this will be an interim solution until OPNFV resources can be >> used (note cdub jokingly replied 1-2 years when asked for a "rough" >> estimate - I mention this because based on a later discussion some people >> took this as a serious estimate). >> >> Ian did you have any luck kicking this off? Russell and I are also >> endeavouring to see what we can do on our side w.r.t. this short term >> approach - in particular if you find hardware we still need to find an >> owner to actually setup and manage it as discussed. >> > > > In theory to get started we need a physical multi-socket box and a virtual >> machine somewhere on the same network to handle job control etc. I believe >> the tests themselves can be run in VMs (just not those exposed by existing >> public clouds) assuming a recent Libvirt and an appropriately crafted >> Libvirt XML that ensures the VM gets a multi-socket topology etc. (we can >> assist with this). >> > > With apologies for the late reply, but I was off last week. And because I > was off last week I've not done anything about this so far. > > I'm assuming that we'll just set up one physical multisocket box and > ensure that we can do a cleanup-deploy cycle so that we can run whatever > x86-dependent but otherwise relatively hardware agnostic tests we might > need. Seems easier than worrying about what libvirt and KVM do and don't > support at a given moment in time. > > I'll go nag our lab people for the machines. I'm thinking for the > cleanup-deploy that I might just try booting the physical machine into a > RAM root disk and then running a devstack setup, as it's probably faster > than a clean install, but I'm open to options. (There's quite a lot of > memory in the servers we have so this is likely to work fine.) > > That aside, where are the tests going to live? > Great question, I am thinking these tests are a good candidate for functional (devstack) based tests that live in the nova tree. > > -- > Ian. > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
