Hey guys! We need to get a build slave spun up for quantum.
Normally - this would mean making sure that we had packaging and build-deps done properly ... but that's going to be a little bit. SO If someone could grab the github.com/openstack/openstack-ci-puppet, add something in manifests/site.pp that contains the packages that need to be installed (assume hostname quantum.slave.openstack.org) and submit that to gerrit, we can get this show on the road Monty On 08/05/2011 09:55 AM, Dan Wendlandt wrote: > > > On Fri, Aug 5, 2011 at 9:49 AM, Joseph Heck <he...@me.com > <mailto:he...@me.com>> wrote: > > I've set up an initial job for you - "quantum" > at https://jenkins.openstack.org/view/Nova/job/quantum/ > > (Monty: I didn't know if I should make it's own tab/space for this > or not, so I stuck it in Nova to start...) > > The pip-requires file has a few little issues, so I've also made a > branch to correct that, merge request coming in a few minutes. > > Quick question - is there a mandatory requirement for pep8 version 0.5? > > > Looking at the history of the pip-requires file, it seems like that was > just copied over when we pulled in the unit-testing framework from > another project (glance I believe?). I don't think there's anything > Quantum specific about it. > > dan > > > > -joe > > On Aug 5, 2011, at 9:33 AM, Dan Wendlandt wrote: >> Thanks Joe, >> >> Basic build and unit tests are probably the best place to start. >> The quantum dependencies should be very similar to nova and other >> openstack projects. Things will get more complicated with >> functional/system test as there are different quantum "plugins" >> that may have more exotic dependencies so I'd suggested viewing >> that as a second step. >> >> There is a tools/pip-requires file that should describe all >> dependencies. You can run basic unit tests using ./run_tests.sh >> (see: http://wiki.openstack.org/QuantumTesting for more info). >> Definitely ping the list with any other questions you need for >> setup. >> >> Dan >> >> >> On Fri, Aug 5, 2011 at 9:24 AM, Joseph Heck <he...@me.com >> <mailto:he...@me.com>> wrote: >> >> Hey Carl, >> >> (sorry all for the delay in replying) >> >> I'm relatively uninformed about Quantum right now - does >> testing it require anything special on a Jenkins host? If not, >> I'd be more than willing to help setup up some initial jobs >> for you in Jenkins to run through code and unit tests. I could >> easily see functional or system testing needing something more >> specific enabled (infrastructure or such), but the unit tests >> I would guess should be something we could get up and running >> immediately. >> >> -joe >> >> On Aug 2, 2011, at 8:52 PM, Carl Perry wrote: >>> It was my intention to setup some Jenkins infrastructure for >>> Ceph integration with OpenStack, and I was going to start >>> that by making that setup available for Netstack usage as >>> well. Monty and I briefly talked about it a few weeks ago. >>> I'll touch base with him see what we can get running in the >>> next two weeks. I have some hardware set aside for this >>> already as well. It won't be huge amount of horsepower, but >>> for testing it should be adequate. If we need/want more >>> hardware, I'm sure we can sponsor some more as well. I just >>> grabbed old servers to start with. >>> >>> -Carl >>> >>> On 8/2/11 4:40 PM, Dan Wendlandt wrote: >>>> Hi folks, >>>> >>>> Great to see so much interest around CI for Quantum. >>>> >>>> I have created a new blueprint specifically for continuous >>>> integration: >>>> >>>> https://blueprints.launchpad.net/quantum/+spec/quantum-continuous-integration >>>> >>>> <https://blueprints.launchpad.net/quantum/+spec/quantum-continuous-integration> >>>> >>>> >>>> From the various comments during the meeting, it seems like >>>> we should be able to leverage existing OpenStack Jenkins >>>> infrastructure for this, which is great, it it should mean >>>> we can be up and running quickly. I'm currently looking for >>>> one or more people to drive this work, so please respond to >>>> this thread and we'll agree on a plan for moving forward. >>>> I've targeting the blueprint for D-4, so we'll be tracking >>>> it during our regular meetings. >>>> >>>> Thanks, >>>> >>>> Dan >>>> >>>> -- >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>> Dan Wendlandt >>>> Nicira Networks, Inc. >>>> www.nicira.com <http://www.nicira.com/> | >>>> www.openvswitch.org <http://www.openvswitch.org/> >>>> Sr. Product Manager >>>> cell: 650-906-2650 <tel:650-906-2650> >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>> >>> >>> -- >>> Mailing list: https://launchpad.net/~netstack >>> Post to : netstack@lists.launchpad.net >>> <mailto:netstack@lists.launchpad.net> >>> Unsubscribe : https://launchpad.net/~netstack >>> More help : https://help.launchpad.net/ListHelp >> >> >> >> >> -- >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Dan Wendlandt >> Nicira Networks, Inc. >> www.nicira.com <http://www.nicira.com/> | www.openvswitch.org >> <http://www.openvswitch.org/> >> Sr. Product Manager >> cell: 650-906-2650 <tel:650-906-2650> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> > > > > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dan Wendlandt > Nicira Networks, Inc. > www.nicira.com <http://www.nicira.com> | www.openvswitch.org > <http://www.openvswitch.org> > Sr. Product Manager > cell: 650-906-2650 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
