Hi Abhi,

That’s correct. The ‘elements’ are used to setup the Jenkins slave.

Regarding how the image is built. I think the instructions are clear, but I 
wrote them. Let me know which part is not clear.

Step 3 in the readme link your reference is the command to build the image.
nodepool image-build <image-name>
The image-name is what you have in the nodepool.yaml file.

You may run into issues because the elements defined by openstack-infra  may 
not work in your environment. In that case, you’ll have to override them.

Step 4 starts nodepool, which will use the image built in step 3 and upload it 
to your providers.
You can manually upload it using
nodepool image-upload all <image-name>


From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Monday, August 17, 2015 10:46 PM
To: openstack-in...@lists.openstack.org; OpenStack Development Mailing List 
(not for usage questions) <openstack-dev@lists.openstack.org>
Cc: Asselin, Ramy <ramy.asse...@hp.com>; Abhishek Shrivastava 
Subject: Re: [openstack-infra][third-paty][CI][nodepool]Using Nodepool for 
creating slaves.

Also adding the following:

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 

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

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

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 

Thanks & Regards,
Cloudbyte Inc.<http://www.cloudbyte.com>

Thanks & Regards,
Cloudbyte Inc.<http://www.cloudbyte.com>
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to