Hi Ramy, I got the following you mentioned, so as per my understanding here are the points:
- We need to install CI master on a VM (*Using Ubuntu 14.04 in my case*). - The Master VM should have properties like 8 GB RAM, 100 GB HD. - Nodepool, Jenkins and Zull will be installed in the master VM. - We had to create slaves images and configure it to nodepool (*Creating Ubuntu 14.04 images*). - Nodepool will create it automatically later. Please guide me if I am wrong at any point. Also, your valuable suggestions are also welcome. On Wed, Aug 19, 2015 at 7:24 PM, Asselin, Ramy <[email protected]> wrote: > 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:[email protected]] > *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:[email protected]] > *Sent:* Tuesday, August 18, 2015 1:46 PM > *To:* [email protected]; 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 < > [email protected]> 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: Image removed by sender.]* > > *Thanks & Regards,* > > *Abhishek* > > *Cloudbyte Inc. <http://www.cloudbyte.com>* > > > > > > -- > > *[image: Image removed by sender.]* > > *Thanks & Regards,* > > *Abhishek* > > *Cloudbyte Inc. <http://www.cloudbyte.com>* > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- *Thanks & Regards,* *Abhishek* *Cloudbyte Inc. <http://www.cloudbyte.com>*
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
