I think it comes down to us getting a resource looking at the BMaaS space to enable that path. I.e., I think we're on it, just trying to bring up enough resource to be able to _contribute_ to it :)
R On Oct 31, 2013, at 10:55 AM, Robert Collins <[email protected]> wrote: > On 31 October 2013 18:35, Robert Starmer (starmer) <[email protected]> wrote: >> Russell, >> >> We're planning on testing our Neutron plugins and the stackforge puppetry >> (where we've had some level of contribution). We also have the >> openstack-installer project which is being built in conjunction with Dan >> Bode, which is being pushed up to stackforge as well, leveraging a data >> model against puppet to support multiple deployment scenarios. >> >> The environment at the moment is a single machine running Zuul/Jenkins >> driving a small (4 node) OpenStack cluster, with our test scenarios >> currently leveraging an OS on OS model (not quite TripleO yet). We've >> currently put together a python management framework to spin up the test >> instances, and are just ramping up resources to migrate that to HEAT. > > What can we do to help you get onto the TripleO bandwagon :) ? > >> In order to test our plugins, we'll be adding additional infrastructure to >> allow for the direct physical/virtual resource manipulations that our >> plugins support (specifically L2 manipulations against Nexus switches, and >> L3 against the same). >> >> Robert > > > -- > Robert Collins <[email protected]> > Distinguished Technologist > HP Converged Cloud _______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
