Hi Eduard, I set up most of the interactions manually between master/slave jenkins. Take a look at https://wiki.openstack.org/wiki/Arista-third-party-testing See if this helps. I do describe the configuration steps in this wiki.
regards.. -Sukhdev On Tue, Nov 4, 2014 at 12:06 AM, Eduard Matei < [email protected]> wrote: > Hi, > I'm working on setting up a Jenkins CI testing for our Cinder driver. > Trying to follow: > http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/ > I have some issues/questions, as we already have a Jenkins CI platform, (a > master and a couple of slaves) already running, so i can only add a slave > and extend the master: > - what should the master run (JJB, Zuul, Nodepool) ? > - can i install manually those on the master (no puppet)? > - same for the slave ( > http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/) > - can i just run the script with a "dummy" config data repository? > - regarding the Upstream Service Account: the ssh key should be the key of > the "cinder" user (non-root) on the slave ? > > Thanks, > > -- > > *Eduard Biceri Matei, Senior Software Developer* > www.cloudfounders.com > | [email protected] > > > > *CloudFounders, The Private Cloud Software Company* > > Disclaimer: > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If you are not the named addressee or an employee or agent responsible for > delivering this message to the named addressee, you are hereby notified that > you are not authorized to read, print, retain, copy or disseminate this > message or any part of it. If you have received this email in error we > request you to notify us by reply e-mail and to delete all electronic files > of the message. If you are not the intended recipient you are notified that > disclosing, copying, distributing or taking any action in reliance on the > contents of this information is strictly prohibited. > E-mail transmission cannot be guaranteed to be secure or error free as > information could be intercepted, corrupted, lost, destroyed, arrive late or > incomplete, or contain viruses. The sender therefore does not accept > liability for any errors or omissions in the content of this message, and > shall have no liability for any loss or damage suffered by the user, which > arise as a result of e-mail transmission. > > > _______________________________________________ > OpenStack-Infra mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > >
_______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
