[openstack-dev] [openstack-infra][third-paty][CI][nodepool]Using Nodepool for creating slaves.

Asselin, Ramy ramy.asselin at hp.com
Wed Aug 19 13:54:38 UTC 2015


Hi Xies, Abhi,

It works a bit differently.
Nodepool is responsible to launch VMs which it then registers as Jenkins Slaves.
These Jenkins slaves have “labels” which identify certain user-properties such as Operating System, image contents, etc.
When CI wants to run a test case it submits the job to Jenkins master to be run on any Jenkins slave that matches the desired “label”.
Jenkins will wait until a slave of that ‘label’ is available and assign the job once available.

Ramy


From: Xie, Xianshan [mailto:xiexs at cn.fujitsu.com]
Sent: Tuesday, August 18, 2015 10:59 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra][third-paty][CI][nodepool]Using Nodepool for creating slaves.

Hi Abhi,
   IIUC, you should create and configure slaves(these slaves can be VMs or real physical machine) in Jenkins.
And the nodepool is used to create and pool VMs automatically, and these VMs should be run on the slaves.
Then, while CI wants to build and execute a testcase, especially which attempts to be run on an isolated host, the nodepool will match a proper VM for this testcase.

Hope this might help you.


Xiexs


From: Abhishek Shrivastava [mailto:abhishek at cloudbyte.com]
Sent: Tuesday, August 18, 2015 1:46 PM
To: openstack-infra at lists.openstack.org; OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra][third-paty][CI][nodepool]Using Nodepool for creating slaves.

Also adding the following:

  *   https://github.com/openstack-infra/project-config/tree/master/nodepool/elements
Does this means that we don't have to take care of creating slaves(i.e; installing slave using scripts as we have done in master) and it will be done automatically, and also we don't have to configure slaves in Jenkins.

A bit confusing for me so if anyone can explain it to me then it will be very helpful.

On Tue, Aug 18, 2015 at 11:11 AM, Abhishek Shrivastava <abhishek at cloudbyte.com<mailto:abhishek at cloudbyte.com>> wrote:
Hi Folks,

I was going through Ramy's guide for setting up CI, there I found out the following:

  *   https://github.com/rasselin/os-ext-testing#setting-up-nodepool-jenkins-slaves
But I don't get the fact on how to create the image, also what major settings need to be done to make the config perfect for use. Can anyone help me with that?

--
[Image removed by sender.]
Thanks & Regards,
Abhishek
Cloudbyte Inc.<http://www.cloudbyte.com>



--
[Image removed by sender.]
Thanks & Regards,
Abhishek
Cloudbyte Inc.<http://www.cloudbyte.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150819/c7e773ad/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ~WRD000.jpg
Type: image/jpeg
Size: 823 bytes
Desc: ~WRD000.jpg
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150819/c7e773ad/attachment.jpg>


More information about the OpenStack-dev mailing list