subject:"Re\: \[openstack\-dev\] \[OpenStack\-Infra\] \[ThirdPartyCI\] Need help setting up CI"

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-19 Thread Eduard Matei

Hi Ramy,
That didn't fix it, zuul-server still gets stuck Looking for lost builds,
but zuul user can read gerrit event-stream.

Any other ideas?

Thanks,
Eduard

On Mon, Jan 19, 2015 at 9:09 AM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hi Ramy, indeed user zuul could not read the event-stream (permission
> denied).
> The question is then how it could start zuul-server and read some events?
> Anyway, i copied over .ssh from user jenkins, and now user zuul can run
> that command.
> I restarted zuul-server and will keep an eye on it.
>
> Thanks,
> Eduard
>
> On Fri, Jan 16, 2015 at 8:32 PM, Asselin, Ramy 
> wrote:
>
>>  Hi Eduard,
>>
>>
>>
>> Looking at the zuul code, it seems that is just a periodic task:
>> https://github.com/openstack-infra/zuul/blob/master/zuul/launcher/gearman.py#L50
>>
>>
>>
>> So the issue is not likely those log messages, but rather the lack of
>> other log messages.
>>
>> It seems somehow zuul lost its connection to gerrit even stream…those are
>> the obvious log messages that are missing.
>>
>> And without that, no jobs will trigger a run, so I’d look there.
>>
>>
>>
>> Zuul Manual is here: http://ci.openstack.org/zuul/
>>
>> Zuul conf files is documented here:
>> http://ci.openstack.org/zuul/zuul.html#zuul-conf
>>
>> And the gerrit configurations are here:
>> http://ci.openstack.org/zuul/zuul.html#gerrit
>>
>>
>>
>> Double check you can manually read the event stream as the zuul user
>> (sudo su - zuul) using those settings and this step:
>>
>> http://ci.openstack.org/third_party.html#reading-the-event-stream
>>
>>
>>
>> Ramy
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Friday, January 16, 2015 6:57 AM
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi Punith,
>>
>> That's the whole log :) Not a lot happening after restart, just default
>> initialization.
>>
>> Zuul-merger is not restarted.
>>
>> Layout.yaml is default.
>>
>> Gearman plugin tested in Jenkins, reports success.
>>
>>
>>
>> I disabled now the restart job to see how long it will "Look for lost
>> builds".
>>
>>
>>
>> Have a nice weekend,
>>
>>
>>
>> Eduard
>>
>>
>>
>> On Fri, Jan 16, 2015 at 1:15 PM, Punith S  wrote:
>>
>>   Hi eduard,
>>
>>
>>
>> can you post the whole zuul.log or debug.log after the zuul and
>> zuul-merger restart along with your layout.yaml
>>
>> did you test the connection of gearman pulgin in jenkins ?
>>
>>
>>
>> thanks
>>
>>
>>
>> On Fri, Jan 16, 2015 at 4:20 PM, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>  Hi Ramy,
>>
>> Still couldn't get my custom code to execute between installing devstack
>> and starting tests... i'll try with some custom scripts and skip devstack-*
>> scripts.
>>
>>
>>
>> Meanwhile i see another issue:
>>
>> 2015-01-16 11:02:26,283 DEBUG zuul.IndependentPipelineManager: Finished
>> queue processor: patch (changed: False)
>>
>> 2015-01-16 11:02:26,283 DEBUG zuul.Scheduler: Run handler sleeping
>>
>> 2015-01-16 11:06:06,873 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:11:06,873 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:16:06,874 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:21:06,874 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:26:06,875 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:31:06,875 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:36:06,876 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:41:06,876 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:46:06,877 DEBUG zuul.Gearman: Looking for lost builds
>>
>>
>>
>> Zuul is stuck in "Looking for lost builds" and it misses comments so it
>> doesn't trigger jobs on patches.
>>
>> Any idea how to fix this? (other than restart it every 30 mins, in which
>> case it misses the results of running jobs so it doesn't post the results).
>&

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-18 Thread Eduard Matei

Hi Ramy, indeed user zuul could not read the event-stream (permission
denied).
The question is then how it could start zuul-server and read some events?
Anyway, i copied over .ssh from user jenkins, and now user zuul can run
that command.
I restarted zuul-server and will keep an eye on it.

Thanks,
Eduard

On Fri, Jan 16, 2015 at 8:32 PM, Asselin, Ramy  wrote:

>  Hi Eduard,
>
>
>
> Looking at the zuul code, it seems that is just a periodic task:
> https://github.com/openstack-infra/zuul/blob/master/zuul/launcher/gearman.py#L50
>
>
>
> So the issue is not likely those log messages, but rather the lack of
> other log messages.
>
> It seems somehow zuul lost its connection to gerrit even stream…those are
> the obvious log messages that are missing.
>
> And without that, no jobs will trigger a run, so I’d look there.
>
>
>
> Zuul Manual is here: http://ci.openstack.org/zuul/
>
> Zuul conf files is documented here:
> http://ci.openstack.org/zuul/zuul.html#zuul-conf
>
> And the gerrit configurations are here:
> http://ci.openstack.org/zuul/zuul.html#gerrit
>
>
>
> Double check you can manually read the event stream as the zuul user (sudo
> su - zuul) using those settings and this step:
>
> http://ci.openstack.org/third_party.html#reading-the-event-stream
>
>
>
> Ramy
>
>
>
>
>
>
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Friday, January 16, 2015 6:57 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Punith,
>
> That's the whole log :) Not a lot happening after restart, just default
> initialization.
>
> Zuul-merger is not restarted.
>
> Layout.yaml is default.
>
> Gearman plugin tested in Jenkins, reports success.
>
>
>
> I disabled now the restart job to see how long it will "Look for lost
> builds".
>
>
>
> Have a nice weekend,
>
>
>
> Eduard
>
>
>
> On Fri, Jan 16, 2015 at 1:15 PM, Punith S  wrote:
>
>   Hi eduard,
>
>
>
> can you post the whole zuul.log or debug.log after the zuul and
> zuul-merger restart along with your layout.yaml
>
> did you test the connection of gearman pulgin in jenkins ?
>
>
>
> thanks
>
>
>
> On Fri, Jan 16, 2015 at 4:20 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi Ramy,
>
> Still couldn't get my custom code to execute between installing devstack
> and starting tests... i'll try with some custom scripts and skip devstack-*
> scripts.
>
>
>
> Meanwhile i see another issue:
>
> 2015-01-16 11:02:26,283 DEBUG zuul.IndependentPipelineManager: Finished
> queue processor: patch (changed: False)
>
> 2015-01-16 11:02:26,283 DEBUG zuul.Scheduler: Run handler sleeping
>
> 2015-01-16 11:06:06,873 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:11:06,873 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:16:06,874 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:21:06,874 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:26:06,875 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:31:06,875 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:36:06,876 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:41:06,876 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:46:06,877 DEBUG zuul.Gearman: Looking for lost builds
>
>
>
> Zuul is stuck in "Looking for lost builds" and it misses comments so it
> doesn't trigger jobs on patches.
>
> Any idea how to fix this? (other than restart it every 30 mins, in which
> case it misses the results of running jobs so it doesn't post the results).
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Fri, Jan 16, 2015 at 1:43 AM, Asselin, Ramy 
> wrote:
>
>  Hi Eduard,
>
>
>
> Glad you’re making progress.
>
>
>
> $BASE/new/devstack/ is available at the time pre_test_hook is called, so
> you should be able to make all the changes you need there.
>
>
>
> The sample shows how to configure the driver using local.conf devstack
> hooks.
>
> See here for more details: [1] [2]
>
>
>
> Regarding test, you can do both.
>
> Cinder requires you run tempest.api.volume[3]
>
>
>
> And you can setup a 2nd job that runs your internal functional tests as
> well.
>
>
>
> Ramy
>
>
>
> [1] http://docs.openstack.org/developer/devstack/configuration.html
>
> [2] http://docs.openstack.org/developer/devstack/plugi

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-16 Thread Eduard Matei

Hi Punith,
That's the whole log :) Not a lot happening after restart, just default
initialization.
Zuul-merger is not restarted.
Layout.yaml is default.
Gearman plugin tested in Jenkins, reports success.

I disabled now the restart job to see how long it will "Look for lost
builds".

Have a nice weekend,

Eduard

On Fri, Jan 16, 2015 at 1:15 PM, Punith S  wrote:

>  Hi eduard,
>
> can you post the whole zuul.log or debug.log after the zuul and
> zuul-merger restart along with your layout.yaml
> did you test the connection of gearman pulgin in jenkins ?
>
> thanks
>
> On Fri, Jan 16, 2015 at 4:20 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>> Hi Ramy,
>> Still couldn't get my custom code to execute between installing devstack
>> and starting tests... i'll try with some custom scripts and skip devstack-*
>> scripts.
>>
>> Meanwhile i see another issue:
>> 2015-01-16 11:02:26,283 DEBUG zuul.IndependentPipelineManager: Finished
>> queue processor: patch (changed: False)
>> 2015-01-16 11:02:26,283 DEBUG zuul.Scheduler: Run handler sleeping
>> 2015-01-16 11:06:06,873 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:11:06,873 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:16:06,874 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:21:06,874 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:26:06,875 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:31:06,875 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:36:06,876 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:41:06,876 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:46:06,877 DEBUG zuul.Gearman: Looking for lost builds
>>
>> Zuul is stuck in "Looking for lost builds" and it misses comments so it
>> doesn't trigger jobs on patches.
>> Any idea how to fix this? (other than restart it every 30 mins, in which
>> case it misses the results of running jobs so it doesn't post the results).
>>
>> Thanks,
>> Eduard
>>
>> On Fri, Jan 16, 2015 at 1:43 AM, Asselin, Ramy 
>> wrote:
>>
>>>  Hi Eduard,
>>>
>>>
>>>
>>> Glad you’re making progress.
>>>
>>>
>>>
>>> $BASE/new/devstack/ is available at the time pre_test_hook is called, so
>>> you should be able to make all the changes you need there.
>>>
>>>
>>>
>>> The sample shows how to configure the driver using local.conf devstack
>>> hooks.
>>>
>>> See here for more details: [1] [2]
>>>
>>>
>>>
>>> Regarding test, you can do both.
>>>
>>> Cinder requires you run tempest.api.volume[3]
>>>
>>>
>>>
>>> And you can setup a 2nd job that runs your internal functional tests as
>>> well.
>>>
>>>
>>>
>>> Ramy
>>>
>>>
>>>
>>> [1] http://docs.openstack.org/developer/devstack/configuration.html
>>>
>>> [2] http://docs.openstack.org/developer/devstack/plugins.html
>>>
>>> [3]
>>> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Third_Party_CI_Requirements
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>>> *Sent:* Thursday, January 15, 2015 4:57 AM
>>>
>>> *To:* OpenStack Development Mailing List (not for usage questions)
>>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>>> help setting up CI
>>>
>>>
>>>
>>> Hi Ramy,
>>>
>>>
>>>
>>> The issue with disconnect/abort no longer happens, so i guess it was
>>> some issues with networking.
>>>
>>>
>>>
>>> Regarding the ssh keys i finally used Jenkins Configuration Provider
>>> Plugin to inject ssh keys as a pre-build step, then i added a manual
>>> execution step to scp the logs to the server, so now everything appears to
>>> be working.
>>>
>>>
>>>
>>> Now for the REAL tests:
>>>
>>> looking at
>>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
>>> it seems i need to put the code to install my "third party libs" in the
>>> pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
>>> B

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-16 Thread Punith S

 Hi eduard,

can you post the whole zuul.log or debug.log after the zuul and zuul-merger
restart along with your layout.yaml
did you test the connection of gearman pulgin in jenkins ?

thanks

On Fri, Jan 16, 2015 at 4:20 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hi Ramy,
> Still couldn't get my custom code to execute between installing devstack
> and starting tests... i'll try with some custom scripts and skip devstack-*
> scripts.
>
> Meanwhile i see another issue:
> 2015-01-16 11:02:26,283 DEBUG zuul.IndependentPipelineManager: Finished
> queue processor: patch (changed: False)
> 2015-01-16 11:02:26,283 DEBUG zuul.Scheduler: Run handler sleeping
> 2015-01-16 11:06:06,873 DEBUG zuul.Gearman: Looking for lost builds
> 2015-01-16 11:11:06,873 DEBUG zuul.Gearman: Looking for lost builds
> 2015-01-16 11:16:06,874 DEBUG zuul.Gearman: Looking for lost builds
> 2015-01-16 11:21:06,874 DEBUG zuul.Gearman: Looking for lost builds
> 2015-01-16 11:26:06,875 DEBUG zuul.Gearman: Looking for lost builds
> 2015-01-16 11:31:06,875 DEBUG zuul.Gearman: Looking for lost builds
> 2015-01-16 11:36:06,876 DEBUG zuul.Gearman: Looking for lost builds
> 2015-01-16 11:41:06,876 DEBUG zuul.Gearman: Looking for lost builds
> 2015-01-16 11:46:06,877 DEBUG zuul.Gearman: Looking for lost builds
>
> Zuul is stuck in "Looking for lost builds" and it misses comments so it
> doesn't trigger jobs on patches.
> Any idea how to fix this? (other than restart it every 30 mins, in which
> case it misses the results of running jobs so it doesn't post the results).
>
> Thanks,
> Eduard
>
> On Fri, Jan 16, 2015 at 1:43 AM, Asselin, Ramy 
> wrote:
>
>>  Hi Eduard,
>>
>>
>>
>> Glad you’re making progress.
>>
>>
>>
>> $BASE/new/devstack/ is available at the time pre_test_hook is called, so
>> you should be able to make all the changes you need there.
>>
>>
>>
>> The sample shows how to configure the driver using local.conf devstack
>> hooks.
>>
>> See here for more details: [1] [2]
>>
>>
>>
>> Regarding test, you can do both.
>>
>> Cinder requires you run tempest.api.volume[3]
>>
>>
>>
>> And you can setup a 2nd job that runs your internal functional tests as
>> well.
>>
>>
>>
>> Ramy
>>
>>
>>
>> [1] http://docs.openstack.org/developer/devstack/configuration.html
>>
>> [2] http://docs.openstack.org/developer/devstack/plugins.html
>>
>> [3]
>> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Third_Party_CI_Requirements
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Thursday, January 15, 2015 4:57 AM
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi Ramy,
>>
>>
>>
>> The issue with disconnect/abort no longer happens, so i guess it was some
>> issues with networking.
>>
>>
>>
>> Regarding the ssh keys i finally used Jenkins Configuration Provider
>> Plugin to inject ssh keys as a pre-build step, then i added a manual
>> execution step to scp the logs to the server, so now everything appears to
>> be working.
>>
>>
>>
>> Now for the REAL tests:
>>
>> looking at
>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
>> it seems i need to put the code to install my "third party libs" in the
>> pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
>> BEFORE installing devstack. The problem is we need our "third party libs"
>> to be installed (actually configured) AFTER installing devstack, since they
>> install on top of devstack and do some configuration on devstack.
>>
>>
>>
>> How could i integrate my code into devstack-vm-gate-wrap.sh so that my
>> libs are installed after devstack but before running tempest.
>>
>> Also, as a side question, do i need to run all the test (since they
>> already run in dsvm-tempest-full) or can i run only our internal
>> functionality tests? (in this case i don't need devstack-vm-gate-wrap.sh
>> and i can run custom code directly from jenkins job).
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Eduard
>>
>>
>>
>> On Wed, Jan 14, 2015 at 6:49 PM, As

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-16 Thread Eduard Matei

Hi Ramy,
Still couldn't get my custom code to execute between installing devstack
and starting tests... i'll try with some custom scripts and skip devstack-*
scripts.

Meanwhile i see another issue:
2015-01-16 11:02:26,283 DEBUG zuul.IndependentPipelineManager: Finished
queue processor: patch (changed: False)
2015-01-16 11:02:26,283 DEBUG zuul.Scheduler: Run handler sleeping
2015-01-16 11:06:06,873 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:11:06,873 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:16:06,874 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:21:06,874 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:26:06,875 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:31:06,875 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:36:06,876 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:41:06,876 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:46:06,877 DEBUG zuul.Gearman: Looking for lost builds

Zuul is stuck in "Looking for lost builds" and it misses comments so it
doesn't trigger jobs on patches.
Any idea how to fix this? (other than restart it every 30 mins, in which
case it misses the results of running jobs so it doesn't post the results).

Thanks,
Eduard

On Fri, Jan 16, 2015 at 1:43 AM, Asselin, Ramy  wrote:

>  Hi Eduard,
>
>
>
> Glad you’re making progress.
>
>
>
> $BASE/new/devstack/ is available at the time pre_test_hook is called, so
> you should be able to make all the changes you need there.
>
>
>
> The sample shows how to configure the driver using local.conf devstack
> hooks.
>
> See here for more details: [1] [2]
>
>
>
> Regarding test, you can do both.
>
> Cinder requires you run tempest.api.volume[3]
>
>
>
> And you can setup a 2nd job that runs your internal functional tests as
> well.
>
>
>
> Ramy
>
>
>
> [1] http://docs.openstack.org/developer/devstack/configuration.html
>
> [2] http://docs.openstack.org/developer/devstack/plugins.html
>
> [3]
> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Third_Party_CI_Requirements
>
>
>
>
>
>
>
>
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Thursday, January 15, 2015 4:57 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Ramy,
>
>
>
> The issue with disconnect/abort no longer happens, so i guess it was some
> issues with networking.
>
>
>
> Regarding the ssh keys i finally used Jenkins Configuration Provider
> Plugin to inject ssh keys as a pre-build step, then i added a manual
> execution step to scp the logs to the server, so now everything appears to
> be working.
>
>
>
> Now for the REAL tests:
>
> looking at
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
> it seems i need to put the code to install my "third party libs" in the
> pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
> BEFORE installing devstack. The problem is we need our "third party libs"
> to be installed (actually configured) AFTER installing devstack, since they
> install on top of devstack and do some configuration on devstack.
>
>
>
> How could i integrate my code into devstack-vm-gate-wrap.sh so that my
> libs are installed after devstack but before running tempest.
>
> Also, as a side question, do i need to run all the test (since they
> already run in dsvm-tempest-full) or can i run only our internal
> functionality tests? (in this case i don't need devstack-vm-gate-wrap.sh
> and i can run custom code directly from jenkins job).
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Wed, Jan 14, 2015 at 6:49 PM, Asselin, Ramy 
> wrote:
>
>  Double check your ssh public/private key, authorized keys configuration
> in the slave & log server.
>
> They should all match up. No passwords should be requested.
>
> Try doing a manual scp as Jenkins user from the slave to the log server
> (as Jenkins user there too).
>
>
>
> Regarding manually setting up the publisher, I don’t know. Jenkins Job
> Builder configuration I referenced below should work correctly.
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Wednesday, January 14, 2015 6:56 AM
>
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Ramy,
>
>

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-15 Thread Eduard Matei

Hi Amit,
This is the only logging i see:
2015-01-15 14:48:28,034 DEBUG zuul.Gerrit: Change  status: NEW
2015-01-15 14:48:28,035 INFO zuul.Gerrit: Updating information for 146460,5
2015-01-15 14:51:07,851 DEBUG zuul.Gearman: Looking for lost builds
2015-01-15 14:56:07,852 DEBUG zuul.Gearman: Looking for lost builds
2015-01-15 15:01:00,627 DEBUG zuul.Scheduler: Prepare to exit
2015-01-15 15:01:00,627 DEBUG zuul.Scheduler: Waiting for exit
2015-01-15 15:01:00,627 DEBUG zuul.Scheduler: Run handler awake
2015-01-15 15:01:00,627 DEBUG zuul.Scheduler: Checking if all builds are
complete
2015-01-15 15:01:00,628 DEBUG zuul.Scheduler: All builds are complete
2015-01-15 15:01:00,628 DEBUG zuul.Scheduler: Exiting


At 15.01 it was restarted by jenkins and between 14:48 and 15:01 there was
a job that finished but Gerrit didn't post the results.

Eduard

On Thu, Jan 15, 2015 at 3:06 PM, Amit Das  wrote:

> Hi Eduard,
>
> Can you put the logs or details for below comment:
>
> it seems that sometimes Zuul gets stuck (sometimes in Looking for lost
>> builds, sometimes doing nothing) and it misses notifications.
>
>
> I guess, we too have been facing the same issue with Zuul.
>
>
> Regards,
> Amit
> *CloudByte Inc.* <http://www.cloudbyte.com/>
>
> On Thu, Jan 15, 2015 at 6:29 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>> Hi,
>> Just so i don't start another thread: it seems that sometimes Zuul gets
>> stuck (sometimes in Looking for lost builds, sometimes doing nothing) and
>> it misses notifications.
>> I added a Jenkins timer job to restart it every 30 minutes. Is there a
>> fix for this or something to change in config?
>>
>> Thanks,
>> Eduard
>>
>> On Thu, Jan 15, 2015 at 2:56 PM, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>> Hi Ramy,
>>>
>>> The issue with disconnect/abort no longer happens, so i guess it was
>>> some issues with networking.
>>>
>>> Regarding the ssh keys i finally used Jenkins Configuration Provider
>>> Plugin to inject ssh keys as a pre-build step, then i added a manual
>>> execution step to scp the logs to the server, so now everything appears to
>>> be working.
>>>
>>> Now for the REAL tests:
>>> looking at
>>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
>>> it seems i need to put the code to install my "third party libs" in the
>>> pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
>>> BEFORE installing devstack. The problem is we need our "third party libs"
>>> to be installed (actually configured) AFTER installing devstack, since they
>>> install on top of devstack and do some configuration on devstack.
>>>
>>> How could i integrate my code into devstack-vm-gate-wrap.sh so that my
>>> libs are installed after devstack but before running tempest.
>>> Also, as a side question, do i need to run all the test (since they
>>> already run in dsvm-tempest-full) or can i run only our internal
>>> functionality tests? (in this case i don't need devstack-vm-gate-wrap.sh
>>> and i can run custom code directly from jenkins job).
>>>
>>> Thanks,
>>>
>>> Eduard
>>>
>>> On Wed, Jan 14, 2015 at 6:49 PM, Asselin, Ramy 
>>> wrote:
>>>
>>>>  Double check your ssh public/private key, authorized keys
>>>> configuration in the slave & log server.
>>>>
>>>> They should all match up. No passwords should be requested.
>>>>
>>>> Try doing a manual scp as Jenkins user from the slave to the log server
>>>> (as Jenkins user there too).
>>>>
>>>>
>>>>
>>>> Regarding manually setting up the publisher, I don’t know. Jenkins Job
>>>> Builder configuration I referenced below should work correctly.
>>>>
>>>>
>>>>
>>>> Ramy
>>>>
>>>>
>>>>
>>>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>>>> *Sent:* Wednesday, January 14, 2015 6:56 AM
>>>>
>>>> *To:* OpenStack Development Mailing List (not for usage questions)
>>>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>>>> help setting up CI
>>>>
>>>>
>>>>
>>>> Hi Ramy,
>>>>
>>>>
>>>>
>>>> I think i managed to setup SCP plugin and updated zuul.conf

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-15 Thread Amit Das

Hi Eduard,

Can you put the logs or details for below comment:

it seems that sometimes Zuul gets stuck (sometimes in Looking for lost
> builds, sometimes doing nothing) and it misses notifications.


I guess, we too have been facing the same issue with Zuul.


Regards,
Amit
*CloudByte Inc.* <http://www.cloudbyte.com/>

On Thu, Jan 15, 2015 at 6:29 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hi,
> Just so i don't start another thread: it seems that sometimes Zuul gets
> stuck (sometimes in Looking for lost builds, sometimes doing nothing) and
> it misses notifications.
> I added a Jenkins timer job to restart it every 30 minutes. Is there a fix
> for this or something to change in config?
>
> Thanks,
> Eduard
>
> On Thu, Jan 15, 2015 at 2:56 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>> Hi Ramy,
>>
>> The issue with disconnect/abort no longer happens, so i guess it was some
>> issues with networking.
>>
>> Regarding the ssh keys i finally used Jenkins Configuration Provider
>> Plugin to inject ssh keys as a pre-build step, then i added a manual
>> execution step to scp the logs to the server, so now everything appears to
>> be working.
>>
>> Now for the REAL tests:
>> looking at
>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
>> it seems i need to put the code to install my "third party libs" in the
>> pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
>> BEFORE installing devstack. The problem is we need our "third party libs"
>> to be installed (actually configured) AFTER installing devstack, since they
>> install on top of devstack and do some configuration on devstack.
>>
>> How could i integrate my code into devstack-vm-gate-wrap.sh so that my
>> libs are installed after devstack but before running tempest.
>> Also, as a side question, do i need to run all the test (since they
>> already run in dsvm-tempest-full) or can i run only our internal
>> functionality tests? (in this case i don't need devstack-vm-gate-wrap.sh
>> and i can run custom code directly from jenkins job).
>>
>> Thanks,
>>
>> Eduard
>>
>> On Wed, Jan 14, 2015 at 6:49 PM, Asselin, Ramy 
>> wrote:
>>
>>>  Double check your ssh public/private key, authorized keys
>>> configuration in the slave & log server.
>>>
>>> They should all match up. No passwords should be requested.
>>>
>>> Try doing a manual scp as Jenkins user from the slave to the log server
>>> (as Jenkins user there too).
>>>
>>>
>>>
>>> Regarding manually setting up the publisher, I don’t know. Jenkins Job
>>> Builder configuration I referenced below should work correctly.
>>>
>>>
>>>
>>> Ramy
>>>
>>>
>>>
>>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>>> *Sent:* Wednesday, January 14, 2015 6:56 AM
>>>
>>> *To:* OpenStack Development Mailing List (not for usage questions)
>>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>>> help setting up CI
>>>
>>>
>>>
>>> Hi Ramy,
>>>
>>>
>>>
>>> I think i managed to setup SCP plugin and updated zuul.conf but it only
>>> uploads the console.html not the logs
>>>
>>> I have an SCP site pointing to the apache server and the root location
>>> is /srv/static, and in the dsvm job manually added a post-build step,
>>> Publish Artifacts to SCP Repository, with source: logs/** and destination
>>> logs/${LOG_PATH} and also checked Copy Console Log.
>>>
>>>
>>>
>>> The destination path is created, but it only contains console.html.
>>>
>>>
>>>
>>> I tried to manually scp the directory, but the jenkins user in the
>>> devstack_slave asks for a password when trying to ssh to apache server.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Eduard
>>>
>>>
>>>
>>> On Wed, Jan 14, 2015 at 10:40 AM, Eduard Matei <
>>> eduard.ma...@cloudfounders.com> wrote:
>>>
>>>  Thanks Ramy, i'll try to set it up manually.
>>>
>>>
>>>
>>> Meanwhile i found another problem: jobs are failing because of error or
>>> are being aborted.
>>>
>>> FATAL: java.io.IOException: Unexpected termination of the channel
>>>

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-15 Thread Eduard Matei

Hi,
Just so i don't start another thread: it seems that sometimes Zuul gets
stuck (sometimes in Looking for lost builds, sometimes doing nothing) and
it misses notifications.
I added a Jenkins timer job to restart it every 30 minutes. Is there a fix
for this or something to change in config?

Thanks,
Eduard

On Thu, Jan 15, 2015 at 2:56 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hi Ramy,
>
> The issue with disconnect/abort no longer happens, so i guess it was some
> issues with networking.
>
> Regarding the ssh keys i finally used Jenkins Configuration Provider
> Plugin to inject ssh keys as a pre-build step, then i added a manual
> execution step to scp the logs to the server, so now everything appears to
> be working.
>
> Now for the REAL tests:
> looking at
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
> it seems i need to put the code to install my "third party libs" in the
> pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
> BEFORE installing devstack. The problem is we need our "third party libs"
> to be installed (actually configured) AFTER installing devstack, since they
> install on top of devstack and do some configuration on devstack.
>
> How could i integrate my code into devstack-vm-gate-wrap.sh so that my
> libs are installed after devstack but before running tempest.
> Also, as a side question, do i need to run all the test (since they
> already run in dsvm-tempest-full) or can i run only our internal
> functionality tests? (in this case i don't need devstack-vm-gate-wrap.sh
> and i can run custom code directly from jenkins job).
>
> Thanks,
>
> Eduard
>
> On Wed, Jan 14, 2015 at 6:49 PM, Asselin, Ramy 
> wrote:
>
>>  Double check your ssh public/private key, authorized keys configuration
>> in the slave & log server.
>>
>> They should all match up. No passwords should be requested.
>>
>> Try doing a manual scp as Jenkins user from the slave to the log server
>> (as Jenkins user there too).
>>
>>
>>
>> Regarding manually setting up the publisher, I don’t know. Jenkins Job
>> Builder configuration I referenced below should work correctly.
>>
>>
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Wednesday, January 14, 2015 6:56 AM
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi Ramy,
>>
>>
>>
>> I think i managed to setup SCP plugin and updated zuul.conf but it only
>> uploads the console.html not the logs
>>
>> I have an SCP site pointing to the apache server and the root location is
>> /srv/static, and in the dsvm job manually added a post-build step, Publish
>> Artifacts to SCP Repository, with source: logs/** and destination
>> logs/${LOG_PATH} and also checked Copy Console Log.
>>
>>
>>
>> The destination path is created, but it only contains console.html.
>>
>>
>>
>> I tried to manually scp the directory, but the jenkins user in the
>> devstack_slave asks for a password when trying to ssh to apache server.
>>
>>
>>
>> Thanks,
>>
>> Eduard
>>
>>
>>
>> On Wed, Jan 14, 2015 at 10:40 AM, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>  Thanks Ramy, i'll try to set it up manually.
>>
>>
>>
>> Meanwhile i found another problem: jobs are failing because of error or
>> are being aborted.
>>
>> FATAL: java.io.IOException: Unexpected termination of the channel
>>
>> hudson.remoting.RequestAbortedException 
>> <http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
>>  java.io.IOException: Unexpected termination of the channel
>>
>>
>>
>> Is this related to another warning i got:
>>
>> WARNING: devstack run took > 15 minutes, this is a very slow node.
>>
>>
>>
>> Is there a timeout for how long a job is allowed to run?
>>
>> Most jobs take between 40 and 60 minutes, some are able to run successfully, 
>> some are aborted or get this error.
>>
>>
>>
>> Hardware is Xeon E3-1220 Quad core 3.10 Ghz, 32 GB RAM and 3x 1TB sata HDD.
>>
>> Devstack slaves are configured as m1.large (4 vCPUs, 8 GB vRAM and 80 GB 
>> vHDD).
>>
>>
>>
>> Thanks,
>&g

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-15 Thread Eduard Matei

Hi Ramy,

The issue with disconnect/abort no longer happens, so i guess it was some
issues with networking.

Regarding the ssh keys i finally used Jenkins Configuration Provider Plugin
to inject ssh keys as a pre-build step, then i added a manual execution
step to scp the logs to the server, so now everything appears to be working.

Now for the REAL tests:
looking at
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
it seems i need to put the code to install my "third party libs" in the
pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
BEFORE installing devstack. The problem is we need our "third party libs"
to be installed (actually configured) AFTER installing devstack, since they
install on top of devstack and do some configuration on devstack.

How could i integrate my code into devstack-vm-gate-wrap.sh so that my libs
are installed after devstack but before running tempest.
Also, as a side question, do i need to run all the test (since they already
run in dsvm-tempest-full) or can i run only our internal functionality
tests? (in this case i don't need devstack-vm-gate-wrap.sh and i can run
custom code directly from jenkins job).

Thanks,

Eduard

On Wed, Jan 14, 2015 at 6:49 PM, Asselin, Ramy  wrote:

>  Double check your ssh public/private key, authorized keys configuration
> in the slave & log server.
>
> They should all match up. No passwords should be requested.
>
> Try doing a manual scp as Jenkins user from the slave to the log server
> (as Jenkins user there too).
>
>
>
> Regarding manually setting up the publisher, I don’t know. Jenkins Job
> Builder configuration I referenced below should work correctly.
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Wednesday, January 14, 2015 6:56 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Ramy,
>
>
>
> I think i managed to setup SCP plugin and updated zuul.conf but it only
> uploads the console.html not the logs
>
> I have an SCP site pointing to the apache server and the root location is
> /srv/static, and in the dsvm job manually added a post-build step, Publish
> Artifacts to SCP Repository, with source: logs/** and destination
> logs/${LOG_PATH} and also checked Copy Console Log.
>
>
>
> The destination path is created, but it only contains console.html.
>
>
>
> I tried to manually scp the directory, but the jenkins user in the
> devstack_slave asks for a password when trying to ssh to apache server.
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Wed, Jan 14, 2015 at 10:40 AM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Thanks Ramy, i'll try to set it up manually.
>
>
>
> Meanwhile i found another problem: jobs are failing because of error or
> are being aborted.
>
> FATAL: java.io.IOException: Unexpected termination of the channel
>
> hudson.remoting.RequestAbortedException 
> <http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
>  java.io.IOException: Unexpected termination of the channel
>
>
>
> Is this related to another warning i got:
>
> WARNING: devstack run took > 15 minutes, this is a very slow node.
>
>
>
> Is there a timeout for how long a job is allowed to run?
>
> Most jobs take between 40 and 60 minutes, some are able to run successfully, 
> some are aborted or get this error.
>
>
>
> Hardware is Xeon E3-1220 Quad core 3.10 Ghz, 32 GB RAM and 3x 1TB sata HDD.
>
> Devstack slaves are configured as m1.large (4 vCPUs, 8 GB vRAM and 80 GB 
> vHDD).
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Tue, Jan 13, 2015 at 5:34 PM, Asselin, Ramy 
> wrote:
>
>  Hi Eduard,
>
>
>
> Apache logs server address is set here (should probably add some
> comment/doc for that)
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10
>
>
>
> Jenkins will get configured here:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml.erb
>
> Note that you need to restart Jenkins for those changes to take effect.
> After it’s set, you can use the Jenkins UI to ‘test’ the connection.
>
>
>
> Jenkins Job Builder publishers are here:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L110
>
>
>
> Use the publishers as

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-14 Thread Asselin, Ramy

Double check your ssh public/private key, authorized keys configuration in the 
slave & log server.
They should all match up. No passwords should be requested.
Try doing a manual scp as Jenkins user from the slave to the log server (as 
Jenkins user there too).

Regarding manually setting up the publisher, I don’t know. Jenkins Job Builder 
configuration I referenced below should work correctly.

Ramy

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Wednesday, January 14, 2015 6:56 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi Ramy,

I think i managed to setup SCP plugin and updated zuul.conf but it only uploads 
the console.html not the logs
I have an SCP site pointing to the apache server and the root location is 
/srv/static, and in the dsvm job manually added a post-build step, Publish 
Artifacts to SCP Repository, with source: logs/** and destination 
logs/${LOG_PATH} and also checked Copy Console Log.

The destination path is created, but it only contains console.html.

I tried to manually scp the directory, but the jenkins user in the 
devstack_slave asks for a password when trying to ssh to apache server.

Thanks,
Eduard

On Wed, Jan 14, 2015 at 10:40 AM, Eduard Matei 
mailto:eduard.ma...@cloudfounders.com>> wrote:
Thanks Ramy, i'll try to set it up manually.

Meanwhile i found another problem: jobs are failing because of error or are 
being aborted.

FATAL: java.io.IOException: Unexpected termination of the channel

hudson.remoting.RequestAbortedException<http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
 java.io.IOException: Unexpected termination of the channel



Is this related to another warning i got:

WARNING: devstack run took > 15 minutes, this is a very slow node.



Is there a timeout for how long a job is allowed to run?

Most jobs take between 40 and 60 minutes, some are able to run successfully, 
some are aborted or get this error.



Hardware is Xeon E3-1220 Quad core 3.10 Ghz, 32 GB RAM and 3x 1TB sata HDD.

Devstack slaves are configured as m1.large (4 vCPUs, 8 GB vRAM and 80 GB vHDD).



Thanks,

Eduard

On Tue, Jan 13, 2015 at 5:34 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
Hi Eduard,

Apache logs server address is set here (should probably add some comment/doc 
for that)
https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10

Jenkins will get configured here: 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml.erb
Note that you need to restart Jenkins for those changes to take effect. After 
it’s set, you can use the Jenkins UI to ‘test’ the connection.

Jenkins Job Builder publishers are here: 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L110

Use the publishers as shown here:
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7

Zuul will then use this url when commenting in gerrit: 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/manifests/master.pp#L18


Ramy

From: Eduard Matei 
[mailto:eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>]
Sent: Tuesday, January 13, 2015 2:31 AM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Thanks Ramy, i got it now working (the NODEPOOL_SSH_KEY was not set before 
starting first time nodepool, so template got incorrect key)
Next question: where do i configure the apache logs server address? I have a 
separate vm with jenkins account and running apache2 exposing /srv/static/logs, 
but where do i enter its ip address ? (in jenkins, nodepool or... )

Thanks,
Eduard

On Mon, Jan 12, 2015 at 6:09 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
You are correct to run nodepoold as nodepool user.
I didn’t see any issues…
Could you double check the public keys listed in .ssh/authorized_keys in the 
template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
Ramy

From: Eduard Matei 
[mailto:eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>]
Sent: Monday, January 12, 2015 5:30 AM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi,
Regarding the last issue, i fixed it by logging in and manually "pip install 
docutils". Image was created successfully.

Now the problem is that nodepool is not able to login into instances created 
from that image.
I have NODEPOOL_SSH_KEY exported in the screen where nodepool is running, and 
also i am able

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-14 Thread Asselin, Ramy

See in-line

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Wednesday, January 14, 2015 12:41 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Thanks Ramy, i'll try to set it up manually.

Meanwhile i found another problem: jobs are failing because of error or are 
being aborted.

FATAL: java.io.IOException: Unexpected termination of the channel

hudson.remoting.RequestAbortedException<http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
 java.io.IOException: Unexpected termination of the channel

RA: This means there’s some communication failure between the Jenkins master 
and Jenkins slave. If it happens every time, then likely some issue on the 
slave changing network settings.

Is this related to another warning i got:

WARNING: devstack run took > 15 minutes, this is a very slow node.

RA:  I get that too…it likely means you have a slow network or didn’t cache 
sufficient packages in the image, or repos server the necessary data are 
overloaded, etc.

Is there a timeout for how long a job is allowed to run?

Most jobs take between 40 and 60 minutes, some are able to run successfully, 
some are aborted or get this error.

Hardware is Xeon E3-1220 Quad core 3.10 Ghz, 32 GB RAM and 3x 1TB sata HDD.

Devstack slaves are configured as m1.large (4 vCPUs, 8 GB vRAM and 80 GB vHDD).

RA: m1.large should be fine.

Thanks,

Eduard

On Tue, Jan 13, 2015 at 5:34 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
Hi Eduard,

Apache logs server address is set here (should probably add some comment/doc 
for that)
https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10

Jenkins will get configured here: 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml.erb
Note that you need to restart Jenkins for those changes to take effect. After 
it’s set, you can use the Jenkins UI to ‘test’ the connection.

Jenkins Job Builder publishers are here: 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L110

Use the publishers as shown here:
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7

Zuul will then use this url when commenting in gerrit: 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/manifests/master.pp#L18

Ramy

From: Eduard Matei 
[mailto:eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>]
Sent: Tuesday, January 13, 2015 2:31 AM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Thanks Ramy, i got it now working (the NODEPOOL_SSH_KEY was not set before 
starting first time nodepool, so template got incorrect key)
Next question: where do i configure the apache logs server address? I have a 
separate vm with jenkins account and running apache2 exposing /srv/static/logs, 
but where do i enter its ip address ? (in jenkins, nodepool or... )

Thanks,
Eduard

On Mon, Jan 12, 2015 at 6:09 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
You are correct to run nodepoold as nodepool user.
I didn’t see any issues…
Could you double check the public keys listed in .ssh/authorized_keys in the 
template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
Ramy

From: Eduard Matei 
[mailto:eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>]
Sent: Monday, January 12, 2015 5:30 AM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi,
Regarding the last issue, i fixed it by logging in and manually "pip install 
docutils". Image was created successfully.

Now the problem is that nodepool is not able to login into instances created 
from that image.
I have NODEPOOL_SSH_KEY exported in the screen where nodepool is running, and 
also i am able to login to the instance from user nodepool, but nodepoold gives 
error:
2015-01-12 14:19:03,095 DEBUG paramiko.transport: Switch to new keys ...
2015-01-12 14:19:03,109 DEBUG paramiko.transport: Trying key 
c03fbf64440cd0c2ecbc07ce4ed59804 from /home/nodepool/.ssh/id_rsa
2015-01-12 14:19:03,135 DEBUG paramiko.transport: userauth is OK
2015-01-12 14:19:03,162 INFO paramiko.transport: Authentication (publickey) 
failed.
2015-01-12 14:19:03,185 DEBUG paramiko.transport: Trying discovered key 
c03fbf64440cd0c2ecbc07ce4ed59804 in /home/nodepool/.ssh/id_rsa
2015-01-12 14:19:03,187 DEBUG paramiko.transport: userauth is OK
^C2015-01-12 14:19:03,210 INFO paramiko.transport: Authentication (publickey) 
failed.
2015-01-

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-14 Thread Eduard Matei

Hi Ramy,

I think i managed to setup SCP plugin and updated zuul.conf but it only
uploads the console.html not the logs
I have an SCP site pointing to the apache server and the root location is
/srv/static, and in the dsvm job manually added a post-build step, Publish
Artifacts to SCP Repository, with source: logs/** and destination
logs/${LOG_PATH} and also checked Copy Console Log.

The destination path is created, but it only contains console.html.

I tried to manually scp the directory, but the jenkins user in the
devstack_slave asks for a password when trying to ssh to apache server.

Thanks,
Eduard

On Wed, Jan 14, 2015 at 10:40 AM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Thanks Ramy, i'll try to set it up manually.
>
> Meanwhile i found another problem: jobs are failing because of error or
> are being aborted.
>
> FATAL: java.io.IOException: Unexpected termination of the 
> channelhudson.remoting.RequestAbortedException 
> <http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
>  java.io.IOException: Unexpected termination of the channel
>
>
> Is this related to another warning i got:
>
> WARNING: devstack run took > 15 minutes, this is a very slow node.
>
>
> Is there a timeout for how long a job is allowed to run?
>
> Most jobs take between 40 and 60 minutes, some are able to run successfully, 
> some are aborted or get this error.
>
>
> Hardware is Xeon E3-1220 Quad core 3.10 Ghz, 32 GB RAM and 3x 1TB sata HDD.
>
> Devstack slaves are configured as m1.large (4 vCPUs, 8 GB vRAM and 80 GB 
> vHDD).
>
>
> Thanks,
>
> Eduard
>
>
> On Tue, Jan 13, 2015 at 5:34 PM, Asselin, Ramy 
> wrote:
>
>>  Hi Eduard,
>>
>>
>>
>> Apache logs server address is set here (should probably add some
>> comment/doc for that)
>>
>>
>> https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10
>>
>>
>>
>> Jenkins will get configured here:
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml.erb
>>
>> Note that you need to restart Jenkins for those changes to take effect.
>> After it’s set, you can use the Jenkins UI to ‘test’ the connection.
>>
>>
>>
>> Jenkins Job Builder publishers are here:
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L110
>>
>>
>>
>> Use the publishers as shown here:
>>
>>
>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
>>
>>
>>
>> Zuul will then use this url when commenting in gerrit:
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/manifests/master.pp#L18
>>
>>
>>
>>
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Tuesday, January 13, 2015 2:31 AM
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Thanks Ramy, i got it now working (the NODEPOOL_SSH_KEY was not set
>> before starting first time nodepool, so template got incorrect key)
>>
>> Next question: where do i configure the apache logs server address? I
>> have a separate vm with jenkins account and running apache2 exposing
>> /srv/static/logs, but where do i enter its ip address ? (in jenkins,
>> nodepool or... )
>>
>>
>>
>> Thanks,
>>
>> Eduard
>>
>>
>>
>> On Mon, Jan 12, 2015 at 6:09 PM, Asselin, Ramy 
>> wrote:
>>
>>  You are correct to run nodepoold as nodepool user.
>>
>> I didn’t see any issues…
>>
>> Could you double check the public keys listed in .ssh/authorized_keys in
>> the template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Monday, January 12, 2015 5:30 AM
>>
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi,
>>
>> Regarding the last issue, i fixed it by logging in and manually "pip
>> install docutils". Image was created successfully.
>>
>

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-14 Thread Eduard Matei

Thanks Ramy, i'll try to set it up manually.

Meanwhile i found another problem: jobs are failing because of error or are
being aborted.

FATAL: java.io.IOException: Unexpected termination of the
channelhudson.remoting.RequestAbortedException
<http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
java.io.IOException: Unexpected termination of the channel


Is this related to another warning i got:

WARNING: devstack run took > 15 minutes, this is a very slow node.


Is there a timeout for how long a job is allowed to run?

Most jobs take between 40 and 60 minutes, some are able to run
successfully, some are aborted or get this error.


Hardware is Xeon E3-1220 Quad core 3.10 Ghz, 32 GB RAM and 3x 1TB sata HDD.

Devstack slaves are configured as m1.large (4 vCPUs, 8 GB vRAM and 80 GB vHDD).


Thanks,

Eduard


On Tue, Jan 13, 2015 at 5:34 PM, Asselin, Ramy  wrote:

>  Hi Eduard,
>
>
>
> Apache logs server address is set here (should probably add some
> comment/doc for that)
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10
>
>
>
> Jenkins will get configured here:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml.erb
>
> Note that you need to restart Jenkins for those changes to take effect.
> After it’s set, you can use the Jenkins UI to ‘test’ the connection.
>
>
>
> Jenkins Job Builder publishers are here:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L110
>
>
>
> Use the publishers as shown here:
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
>
>
>
> Zuul will then use this url when commenting in gerrit:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/manifests/master.pp#L18
>
>
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Tuesday, January 13, 2015 2:31 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Thanks Ramy, i got it now working (the NODEPOOL_SSH_KEY was not set before
> starting first time nodepool, so template got incorrect key)
>
> Next question: where do i configure the apache logs server address? I have
> a separate vm with jenkins account and running apache2 exposing
> /srv/static/logs, but where do i enter its ip address ? (in jenkins,
> nodepool or... )
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Mon, Jan 12, 2015 at 6:09 PM, Asselin, Ramy 
> wrote:
>
>  You are correct to run nodepoold as nodepool user.
>
> I didn’t see any issues…
>
> Could you double check the public keys listed in .ssh/authorized_keys in
> the template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Monday, January 12, 2015 5:30 AM
>
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi,
>
> Regarding the last issue, i fixed it by logging in and manually "pip
> install docutils". Image was created successfully.
>
>
>
> Now the problem is that nodepool is not able to login into instances
> created from that image.
>
> I have NODEPOOL_SSH_KEY exported in the screen where nodepool is running,
> and also i am able to login to the instance from user nodepool, but
> nodepoold gives error:
>
> 2015-01-12 14:19:03,095 DEBUG paramiko.transport: Switch to new keys ...
>
> 2015-01-12 14:19:03,109 DEBUG paramiko.transport: Trying key
> c03fbf64440cd0c2ecbc07ce4ed59804 from /home/nodepool/.ssh/id_rsa
>
> 2015-01-12 14:19:03,135 DEBUG paramiko.transport: userauth is OK
>
> 2015-01-12 14:19:03,162 INFO paramiko.transport: Authentication
> (publickey) failed.
>
> 2015-01-12 14:19:03,185 DEBUG paramiko.transport: Trying discovered key
> c03fbf64440cd0c2ecbc07ce4ed59804 in /home/nodepool/.ssh/id_rsa
>
> 2015-01-12 14:19:03,187 DEBUG paramiko.transport: userauth is OK
>
> ^C2015-01-12 14:19:03,210 INFO paramiko.transport: Authentication
> (publickey) failed.
>
> 2015-01-12 14:19:03,253 DEBUG paramiko.transport: EOF in transport thread
>
> 2015-01-12 14:19:03,254 INFO nodepool.utils: Password auth exception. Try
> number 4...
>
>
>
>
>
> echo $NODEPOOL_SSH_KEY
>

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-13 Thread Asselin, Ramy

Hi Eduard,

Apache logs server address is set here (should probably add some comment/doc 
for that)
https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10

Jenkins will get configured here: 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml.erb
Note that you need to restart Jenkins for those changes to take effect. After 
it’s set, you can use the Jenkins UI to ‘test’ the connection.

Jenkins Job Builder publishers are here: 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L110

Use the publishers as shown here:
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7

Zuul will then use this url when commenting in gerrit: 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/manifests/master.pp#L18


Ramy

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Tuesday, January 13, 2015 2:31 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Thanks Ramy, i got it now working (the NODEPOOL_SSH_KEY was not set before 
starting first time nodepool, so template got incorrect key)
Next question: where do i configure the apache logs server address? I have a 
separate vm with jenkins account and running apache2 exposing /srv/static/logs, 
but where do i enter its ip address ? (in jenkins, nodepool or... )

Thanks,
Eduard

On Mon, Jan 12, 2015 at 6:09 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
You are correct to run nodepoold as nodepool user.
I didn’t see any issues…
Could you double check the public keys listed in .ssh/authorized_keys in the 
template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
Ramy

From: Eduard Matei 
[mailto:eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>]
Sent: Monday, January 12, 2015 5:30 AM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi,
Regarding the last issue, i fixed it by logging in and manually "pip install 
docutils". Image was created successfully.

Now the problem is that nodepool is not able to login into instances created 
from that image.
I have NODEPOOL_SSH_KEY exported in the screen where nodepool is running, and 
also i am able to login to the instance from user nodepool, but nodepoold gives 
error:
2015-01-12 14:19:03,095 DEBUG paramiko.transport: Switch to new keys ...
2015-01-12 14:19:03,109 DEBUG paramiko.transport: Trying key 
c03fbf64440cd0c2ecbc07ce4ed59804 from /home/nodepool/.ssh/id_rsa
2015-01-12 14:19:03,135 DEBUG paramiko.transport: userauth is OK
2015-01-12 14:19:03,162 INFO paramiko.transport: Authentication (publickey) 
failed.
2015-01-12 14:19:03,185 DEBUG paramiko.transport: Trying discovered key 
c03fbf64440cd0c2ecbc07ce4ed59804 in /home/nodepool/.ssh/id_rsa
2015-01-12 14:19:03,187 DEBUG paramiko.transport: userauth is OK
^C2015-01-12 14:19:03,210 INFO paramiko.transport: Authentication (publickey) 
failed.
2015-01-12 14:19:03,253 DEBUG paramiko.transport: EOF in transport thread
2015-01-12 14:19:03,254 INFO nodepool.utils: Password auth exception. Try 
number 4...


echo $NODEPOOL_SSH_KEY
B3NzaC1yc2EDAQABAAABAQC9gP6qui1fmHrj02p6OGvnz7kMTJ2rOC3SBYP/Ij/6yz+SU8rL5rqL6jqT30xzy9t1q0zsdJCNB2jExD4xb+NFbaoGlvjF85m12eFqP4CQenxUOdYAepf5sjV2l8WAO3ylspQ78ipLKec98NeKQwLrHB+xon6QfAHXr6ZJ9NRZbmWw/OdpOgAG9Cab+ELTmkfEYgQz01cZE22xEAMvPXz57KlWPvxtE7YwYWy180Yib97EftylsNkrchbSXCwiqgKUf04qWhTgNrVuRJ9mytil6S82VNDxHzTzeCCxY412CV6dDJNLzJItpf/CXQelj/6wJs1GgFl5GWJnqortMR2v

 cat /home/nodepool/.ssh/id_rsa.pub
ssh-rsa 
B3NzaC1yc2EDAQABAAABAQC9gP6qui1fmHrj02p6OGvnz7kMTJ2rOC3SBYP/Ij/6yz+SU8rL5rqL6jqT30xzy9t1q0zsdJCNB2jExD4xb+NFbaoGlvjF85m12eFqP4CQenxUOdYAepf5sjV2l8WAO3ylspQ78ipLKec98NeKQwLrHB+xon6QfAHXr6ZJ9NRZbmWw/OdpOgAG9Cab+ELTmkfEYgQz01cZE22xEAMvPXz57KlWPvxtE7YwYWy180Yib97EftylsNkrchbSXCwiqgKUf04qWhTgNrVuRJ9mytil6S82VNDxHzTzeCCxY412CV6dDJNLzJItpf/CXQelj/6wJs1GgFl5GWJnqortMR2v
 jenkins@jenkins-cinderci

ssh ubuntu@10.100.128.136<mailto:ubuntu@10.100.128.136> -v
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /home/nodepool/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 10.100.128.136 [10.100.128.136] port 22.
debug1: Connection established.

debug1: Offering RSA public key: /home/nodepool/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: key_parse_private2: missing begin marker
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
Authenticated to 10.100.128.136 ([10.100.128.

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-13 Thread Eduard Matei

Thanks Ramy, i got it now working (the NODEPOOL_SSH_KEY was not set before
starting first time nodepool, so template got incorrect key)
Next question: where do i configure the apache logs server address? I have
a separate vm with jenkins account and running apache2 exposing
/srv/static/logs, but where do i enter its ip address ? (in jenkins,
nodepool or... )

Thanks,
Eduard

On Mon, Jan 12, 2015 at 6:09 PM, Asselin, Ramy  wrote:

>  You are correct to run nodepoold as nodepool user.
>
> I didn’t see any issues…
>
> Could you double check the public keys listed in .ssh/authorized_keys in
> the template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Monday, January 12, 2015 5:30 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi,
>
> Regarding the last issue, i fixed it by logging in and manually "pip
> install docutils". Image was created successfully.
>
>
>
> Now the problem is that nodepool is not able to login into instances
> created from that image.
>
> I have NODEPOOL_SSH_KEY exported in the screen where nodepool is running,
> and also i am able to login to the instance from user nodepool, but
> nodepoold gives error:
>
> 2015-01-12 14:19:03,095 DEBUG paramiko.transport: Switch to new keys ...
>
> 2015-01-12 14:19:03,109 DEBUG paramiko.transport: Trying key
> c03fbf64440cd0c2ecbc07ce4ed59804 from /home/nodepool/.ssh/id_rsa
>
> 2015-01-12 14:19:03,135 DEBUG paramiko.transport: userauth is OK
>
> 2015-01-12 14:19:03,162 INFO paramiko.transport: Authentication
> (publickey) failed.
>
> 2015-01-12 14:19:03,185 DEBUG paramiko.transport: Trying discovered key
> c03fbf64440cd0c2ecbc07ce4ed59804 in /home/nodepool/.ssh/id_rsa
>
> 2015-01-12 14:19:03,187 DEBUG paramiko.transport: userauth is OK
>
> ^C2015-01-12 14:19:03,210 INFO paramiko.transport: Authentication
> (publickey) failed.
>
> 2015-01-12 14:19:03,253 DEBUG paramiko.transport: EOF in transport thread
>
> 2015-01-12 14:19:03,254 INFO nodepool.utils: Password auth exception. Try
> number 4...
>
>
>
>
>
> echo $NODEPOOL_SSH_KEY
>
>
> B3NzaC1yc2EDAQABAAABAQC9gP6qui1fmHrj02p6OGvnz7kMTJ2rOC3SBYP/Ij/6yz+SU8rL5rqL6jqT30xzy9t1q0zsdJCNB2jExD4xb+NFbaoGlvjF85m12eFqP4CQenxUOdYAepf5sjV2l8WAO3ylspQ78ipLKec98NeKQwLrHB+xon6QfAHXr6ZJ9NRZbmWw/OdpOgAG9Cab+ELTmkfEYgQz01cZE22xEAMvPXz57KlWPvxtE7YwYWy180Yib97EftylsNkrchbSXCwiqgKUf04qWhTgNrVuRJ9mytil6S82VNDxHzTzeCCxY412CV6dDJNLzJItpf/CXQelj/6wJs1GgFl5GWJnqortMR2v
>
>
>
>  cat /home/nodepool/.ssh/id_rsa.pub
>
> ssh-rsa
> B3NzaC1yc2EDAQABAAABAQC9gP6qui1fmHrj02p6OGvnz7kMTJ2rOC3SBYP/Ij/6yz+SU8rL5rqL6jqT30xzy9t1q0zsdJCNB2jExD4xb+NFbaoGlvjF85m12eFqP4CQenxUOdYAepf5sjV2l8WAO3ylspQ78ipLKec98NeKQwLrHB+xon6QfAHXr6ZJ9NRZbmWw/OdpOgAG9Cab+ELTmkfEYgQz01cZE22xEAMvPXz57KlWPvxtE7YwYWy180Yib97EftylsNkrchbSXCwiqgKUf04qWhTgNrVuRJ9mytil6S82VNDxHzTzeCCxY412CV6dDJNLzJItpf/CXQelj/6wJs1GgFl5GWJnqortMR2v
> jenkins@jenkins-cinderci
>
>
>
> ssh ubuntu@10.100.128.136 -v
>
> OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
>
> debug1: Reading configuration data /home/nodepool/.ssh/config
>
> debug1: Reading configuration data /etc/ssh/ssh_config
>
> debug1: /etc/ssh/ssh_config line 19: Applying options for *
>
> debug1: Connecting to 10.100.128.136 [10.100.128.136] port 22.
>
> debug1: Connection established.
>
> 
>
> debug1: Offering RSA public key: /home/nodepool/.ssh/id_rsa
>
> debug1: Server accepts key: pkalg ssh-rsa blen 279
>
> debug1: key_parse_private2: missing begin marker
>
> debug1: read PEM private key done: type RSA
>
> debug1: Authentication succeeded (publickey).
>
> Authenticated to 10.100.128.136 ([10.100.128.136]:22).
>
> ...
>
>
>
> I was able to login into the "template" instance and also am able to login
> into the "slave" instances.
>
> Also nodepoold was able to login into "template" instance but now it fails
> loging in into "slave".
>
>
>
> I tried running it as either nodepol or jenkins users, same result.
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Mon, Jan 12, 2015 at 2:09 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi,
>
> Back with another error during image creation with nodepool:
>
> 2015-01-12 13:05:17,775 INFO nodepool.image.build.local_01.d-p-c:
> Downloading python-daemon-2.0.1.tar.gz (62kB)
>
> 2015-01-12 13:05:18,022 INFO nodepool.image.build.local_01.d-p-c:
> Traceback (most recent call last):
>
> 2015-01

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-12 Thread Asselin, Ramy

You are correct to run nodepoold as nodepool user.
I didn’t see any issues…
Could you double check the public keys listed in .ssh/authorized_keys in the 
template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
Ramy

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Monday, January 12, 2015 5:30 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi,
Regarding the last issue, i fixed it by logging in and manually "pip install 
docutils". Image was created successfully.

Now the problem is that nodepool is not able to login into instances created 
from that image.
I have NODEPOOL_SSH_KEY exported in the screen where nodepool is running, and 
also i am able to login to the instance from user nodepool, but nodepoold gives 
error:
2015-01-12 14:19:03,095 DEBUG paramiko.transport: Switch to new keys ...
2015-01-12 14:19:03,109 DEBUG paramiko.transport: Trying key 
c03fbf64440cd0c2ecbc07ce4ed59804 from /home/nodepool/.ssh/id_rsa
2015-01-12 14:19:03,135 DEBUG paramiko.transport: userauth is OK
2015-01-12 14:19:03,162 INFO paramiko.transport: Authentication (publickey) 
failed.
2015-01-12 14:19:03,185 DEBUG paramiko.transport: Trying discovered key 
c03fbf64440cd0c2ecbc07ce4ed59804 in /home/nodepool/.ssh/id_rsa
2015-01-12 14:19:03,187 DEBUG paramiko.transport: userauth is OK
^C2015-01-12 14:19:03,210 INFO paramiko.transport: Authentication (publickey) 
failed.
2015-01-12 14:19:03,253 DEBUG paramiko.transport: EOF in transport thread
2015-01-12 14:19:03,254 INFO nodepool.utils: Password auth exception. Try 
number 4...

echo $NODEPOOL_SSH_KEY
B3NzaC1yc2EDAQABAAABAQC9gP6qui1fmHrj02p6OGvnz7kMTJ2rOC3SBYP/Ij/6yz+SU8rL5rqL6jqT30xzy9t1q0zsdJCNB2jExD4xb+NFbaoGlvjF85m12eFqP4CQenxUOdYAepf5sjV2l8WAO3ylspQ78ipLKec98NeKQwLrHB+xon6QfAHXr6ZJ9NRZbmWw/OdpOgAG9Cab+ELTmkfEYgQz01cZE22xEAMvPXz57KlWPvxtE7YwYWy180Yib97EftylsNkrchbSXCwiqgKUf04qWhTgNrVuRJ9mytil6S82VNDxHzTzeCCxY412CV6dDJNLzJItpf/CXQelj/6wJs1GgFl5GWJnqortMR2v

 cat /home/nodepool/.ssh/id_rsa.pub
ssh-rsa 
B3NzaC1yc2EDAQABAAABAQC9gP6qui1fmHrj02p6OGvnz7kMTJ2rOC3SBYP/Ij/6yz+SU8rL5rqL6jqT30xzy9t1q0zsdJCNB2jExD4xb+NFbaoGlvjF85m12eFqP4CQenxUOdYAepf5sjV2l8WAO3ylspQ78ipLKec98NeKQwLrHB+xon6QfAHXr6ZJ9NRZbmWw/OdpOgAG9Cab+ELTmkfEYgQz01cZE22xEAMvPXz57KlWPvxtE7YwYWy180Yib97EftylsNkrchbSXCwiqgKUf04qWhTgNrVuRJ9mytil6S82VNDxHzTzeCCxY412CV6dDJNLzJItpf/CXQelj/6wJs1GgFl5GWJnqortMR2v
 jenkins@jenkins-cinderci

ssh ubuntu@10.100.128.136<mailto:ubuntu@10.100.128.136> -v
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /home/nodepool/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 10.100.128.136 [10.100.128.136] port 22.
debug1: Connection established.

debug1: Offering RSA public key: /home/nodepool/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: key_parse_private2: missing begin marker
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
Authenticated to 10.100.128.136 ([10.100.128.136]:22).
...

I was able to login into the "template" instance and also am able to login into 
the "slave" instances.
Also nodepoold was able to login into "template" instance but now it fails 
loging in into "slave".

I tried running it as either nodepol or jenkins users, same result.

Thanks,
Eduard

On Mon, Jan 12, 2015 at 2:09 PM, Eduard Matei 
mailto:eduard.ma...@cloudfounders.com>> wrote:
Hi,
Back with another error during image creation with nodepool:
2015-01-12 13:05:17,775 INFO nodepool.image.build.local_01.d-p-c:   Downloading 
python-daemon-2.0.1.tar.gz (62kB)
2015-01-12 13:05:18,022 INFO nodepool.image.build.local_01.d-p-c: Traceback 
(most recent call last):
2015-01-12 13:05:18,023 INFO nodepool.image.build.local_01.d-p-c:   File 
"", line 20, in 
2015-01-12 13:05:18,023 INFO nodepool.image.build.local_01.d-p-c:   File 
"/tmp/pip-build-r6RJKq/python-daemon/setup.py", line 27, in 
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c: 
import version
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:   File 
"version.py", line 51, in 
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c: 
import docutils.core
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c: 
ImportError: No module named docutils.core
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c: Complete 
output from command python setup.py egg_info:
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c: Traceback 
(most recent call last):
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:   File 
"", line

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-12 Thread Eduard Matei

:
> 2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
> File "version.py", line 51, in 
> 2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
> 2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
> import docutils.core
> 2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
> 2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
> ImportError: No module named docutils.core
> 2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
> 2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
> 
> 2015-01-12 13:05:18,054 INFO nodepool.image.build.local_01.d-p-c:
> Command "python setup.py egg_info" failed with error code 1 in
> /tmp/pip-build-r6RJKq/python-daemon
>
> Python-daemon pip package fails to install due to ImportError.
>
> Any ideas how to fix this?
>
> Thanks,
> Eduard
>
> On Fri, Jan 9, 2015 at 10:00 PM, Patrick East <
> patrick.e...@purestorage.com> wrote:
>
>> Thanks for the links!
>>
>> After digging around in my configs I figured out the issue, I had a typo
>> in my JENKINS_SSH_PUBLIC_KEY_NO_WHITESPACE (copy pasta cut off a
>> character...). But I managed to put the right one in the key for nova to
>> use so it was able to log in to set up the instance, but didn't end up with
>> the right thing in the NODEPOOL_SSH_KEY variable.
>>
>> -Patrick
>>
>> On Fri, Jan 9, 2015 at 9:25 AM, Asselin, Ramy 
>> wrote:
>>
>>>
>>>
>>> Regarding SSH Keys and logging into nodes, you need to set the
>>> NODEPOOL_SSH_KEY variable
>>>
>>> 1.   I documented my notes here
>>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/nodepool/nodepool.yaml.erb.sample#L48
>>>
>>> 2.   This is also documented ‘officially’ here:
>>> https://github.com/openstack-infra/nodepool/blob/master/README.rst
>>>
>>> 3.       Also, I had an issue getting puppet to do the right thing with
>>> keys, so it gets forced here:
>>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L197
>>>
>>>
>>>
>>> Ramy
>>>
>>>
>>>
>>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>>> *Sent:* Friday, January 09, 2015 8:58 AM
>>> *To:* OpenStack Development Mailing List (not for usage questions)
>>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>>> help setting up CI
>>>
>>>
>>>
>>> Thanks Patrick,
>>>
>>> Indeed it seems the cloud provider was setting up vms on a bridge whose
>>> eth was DOWN so the vms could not connect to the outside world so the
>>> prepare script was failing.
>>>
>>> Looking into that.
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> Eduard
>>>
>>>
>>>
>>> On Fri, Jan 9, 2015 at 6:44 PM, Patrick East <
>>> patrick.e...@purestorage.com> wrote:
>>>
>>>  Ah yea, sorry, should have specified; I am having it run
>>> the prepare_node_devstack.sh from the infra repo. I see it adding the same
>>> public key to the user specified in my nodepool.yaml. The strange part (and
>>> I need to double check.. feel like it can't be right) is that on my master
>>> node the nodepool users id_rsa changed at some point in the process.
>>>
>>>
>>>
>>>
>>>   -Patrick
>>>
>>>
>>>
>>> On Fri, Jan 9, 2015 at 8:38 AM, Jeremy Stanley 
>>> wrote:
>>>
>>> On 2015-01-09 08:28:39 -0800 (-0800), Patrick East wrote:
>>> [...]
>>> > On a related note, I am having issues with the ssh keys. Nodepool
>>> > is able to log in to the node to set up the template and create an
>>> > image from it, but then fails to log in to a build node. Have you
>>> > run into any issues with that?
>>>
>>> Your image build needs to do _something_ to make SSH into the
>>> resulting nodes possible. We accomplish that by applying a puppet
>>> manifest which sets up an authorized_keys file for the account we
>>> want it to use, but there are countless ways you could go about it
>>> in your environment.
>>> --
>>> Jeremy Stanley
>>>
>>>
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>>

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-12 Thread Eduard Matei

Hi,
Back with another error during image creation with nodepool:
2015-01-12 13:05:17,775 INFO nodepool.image.build.local_01.d-p-c:
Downloading python-daemon-2.0.1.tar.gz (62kB)
2015-01-12 13:05:18,022 INFO nodepool.image.build.local_01.d-p-c:
Traceback (most recent call last):
2015-01-12 13:05:18,023 INFO nodepool.image.build.local_01.d-p-c:
File "", line 20, in 
2015-01-12 13:05:18,023 INFO nodepool.image.build.local_01.d-p-c:
File "/tmp/pip-build-r6RJKq/python-daemon/setup.py", line 27, in 
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
import version
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
File "version.py", line 51, in 
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
import docutils.core
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
ImportError: No module named docutils.core
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
Complete output from command python setup.py egg_info:
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
Traceback (most recent call last):
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
File "", line 20, in 
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
File "/tmp/pip-build-r6RJKq/python-daemon/setup.py", line 27, in 
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
import version
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
File "version.py", line 51, in 
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
import docutils.core
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
ImportError: No module named docutils.core
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:

2015-01-12 13:05:18,054 INFO nodepool.image.build.local_01.d-p-c:
Command "python setup.py egg_info" failed with error code 1 in
/tmp/pip-build-r6RJKq/python-daemon

Python-daemon pip package fails to install due to ImportError.

Any ideas how to fix this?

Thanks,
Eduard

On Fri, Jan 9, 2015 at 10:00 PM, Patrick East 
wrote:

> Thanks for the links!
>
> After digging around in my configs I figured out the issue, I had a typo
> in my JENKINS_SSH_PUBLIC_KEY_NO_WHITESPACE (copy pasta cut off a
> character...). But I managed to put the right one in the key for nova to
> use so it was able to log in to set up the instance, but didn't end up with
> the right thing in the NODEPOOL_SSH_KEY variable.
>
> -Patrick
>
> On Fri, Jan 9, 2015 at 9:25 AM, Asselin, Ramy  wrote:
>
>>
>>
>> Regarding SSH Keys and logging into nodes, you need to set the
>> NODEPOOL_SSH_KEY variable
>>
>> 1.   I documented my notes here
>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/nodepool/nodepool.yaml.erb.sample#L48
>>
>> 2.   This is also documented ‘officially’ here:
>> https://github.com/openstack-infra/nodepool/blob/master/README.rst
>>
>> 3.   Also, I had an issue getting puppet to do the right thing with
>> keys, so it gets forced here:
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L197
>>
>>
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Friday, January 09, 2015 8:58 AM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Thanks Patrick,
>>
>> Indeed it seems the cloud provider was setting up vms on a bridge whose
>> eth was DOWN so the vms could not connect to the outside world so the
>> prepare script was failing.
>>
>> Looking into that.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Eduard
>>
>>
>>
>> On Fri, Jan 9, 2015 at 6:44 PM, Patrick East <
>> patrick.e...@purestorage.com> wrote:
>>
>>  Ah yea, sorry, should have specified; I am having it run
>> the prepare_node_devstack.sh from the infra repo. I see it adding the same
>> public key to the user specified in my nodepool.yaml. The strange part (and
>> I need to double check.. feel like it can't be

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-09 Thread Patrick East

Thanks for the links!

After digging around in my configs I figured out the issue, I had a typo in
my JENKINS_SSH_PUBLIC_KEY_NO_WHITESPACE (copy pasta cut off a
character...). But I managed to put the right one in the key for nova to
use so it was able to log in to set up the instance, but didn't end up with
the right thing in the NODEPOOL_SSH_KEY variable.

-Patrick

On Fri, Jan 9, 2015 at 9:25 AM, Asselin, Ramy  wrote:

>
>
> Regarding SSH Keys and logging into nodes, you need to set the
> NODEPOOL_SSH_KEY variable
>
> 1.   I documented my notes here
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/nodepool/nodepool.yaml.erb.sample#L48
>
> 2.   This is also documented ‘officially’ here:
> https://github.com/openstack-infra/nodepool/blob/master/README.rst
>
> 3.   Also, I had an issue getting puppet to do the right thing with
> keys, so it gets forced here:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L197
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Friday, January 09, 2015 8:58 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Thanks Patrick,
>
> Indeed it seems the cloud provider was setting up vms on a bridge whose
> eth was DOWN so the vms could not connect to the outside world so the
> prepare script was failing.
>
> Looking into that.
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Fri, Jan 9, 2015 at 6:44 PM, Patrick East 
> wrote:
>
>  Ah yea, sorry, should have specified; I am having it run
> the prepare_node_devstack.sh from the infra repo. I see it adding the same
> public key to the user specified in my nodepool.yaml. The strange part (and
> I need to double check.. feel like it can't be right) is that on my master
> node the nodepool users id_rsa changed at some point in the process.
>
>
>
>
>   -Patrick
>
>
>
> On Fri, Jan 9, 2015 at 8:38 AM, Jeremy Stanley  wrote:
>
> On 2015-01-09 08:28:39 -0800 (-0800), Patrick East wrote:
> [...]
> > On a related note, I am having issues with the ssh keys. Nodepool
> > is able to log in to the node to set up the template and create an
> > image from it, but then fails to log in to a build node. Have you
> > run into any issues with that?
>
> Your image build needs to do _something_ to make SSH into the
> resulting nodes possible. We accomplish that by applying a puppet
> manifest which sets up an authorized_keys file for the account we
> want it to use, but there are countless ways you could go about it
> in your environment.
> --
> Jeremy Stanley
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
>
> --
>
> *Eduard Biceri Matei, Senior Software Developer*
>
>  www.cloudfounders.com
>
>  | eduard.ma...@cloudfounders.com
>
>
>
>
>
>
>
>  *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-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-09 Thread Asselin, Ramy

Regarding SSH Keys and logging into nodes, you need to set the NODEPOOL_SSH_KEY 
variable

1.   I documented my notes here 
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/nodepool/nodepool.yaml.erb.sample#L48

2.   This is also documented ‘officially’ here: 
https://github.com/openstack-infra/nodepool/blob/master/README.rst

3.   Also, I had an issue getting puppet to do the right thing with keys, 
so it gets forced here: 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L197

Ramy

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Friday, January 09, 2015 8:58 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Thanks Patrick,
Indeed it seems the cloud provider was setting up vms on a bridge whose eth was 
DOWN so the vms could not connect to the outside world so the prepare script 
was failing.
Looking into that.

Thanks,

Eduard

On Fri, Jan 9, 2015 at 6:44 PM, Patrick East 
mailto:patrick.e...@purestorage.com>> wrote:
Ah yea, sorry, should have specified; I am having it run the 
prepare_node_devstack.sh from the infra repo. I see it adding the same public 
key to the user specified in my nodepool.yaml. The strange part (and I need to 
double check.. feel like it can't be right) is that on my master node the 
nodepool users id_rsa changed at some point in the process.

-Patrick

On Fri, Jan 9, 2015 at 8:38 AM, Jeremy Stanley 
mailto:fu...@yuggoth.org>> wrote:
On 2015-01-09 08:28:39 -0800 (-0800), Patrick East wrote:
[...]
> On a related note, I am having issues with the ssh keys. Nodepool
> is able to log in to the node to set up the template and create an
> image from it, but then fails to log in to a build node. Have you
> run into any issues with that?

Your image build needs to do _something_ to make SSH into the
resulting nodes possible. We accomplish that by applying a puppet
manifest which sets up an authorized_keys file for the account we
want it to use, but there are countless ways you could go about it
in your environment.
--
Jeremy Stanley

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--

Eduard Biceri Matei, Senior Software Developer

www.cloudfounders.com<http://www.cloudfounders.com/>

 | eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>

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-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-09 Thread Eduard Matei

Thanks Patrick,
Indeed it seems the cloud provider was setting up vms on a bridge whose eth
was DOWN so the vms could not connect to the outside world so the prepare
script was failing.
Looking into that.

Thanks,

Eduard

On Fri, Jan 9, 2015 at 6:44 PM, Patrick East 
wrote:

> Ah yea, sorry, should have specified; I am having it run
> the prepare_node_devstack.sh from the infra repo. I see it adding the same
> public key to the user specified in my nodepool.yaml. The strange part (and
> I need to double check.. feel like it can't be right) is that on my master
> node the nodepool users id_rsa changed at some point in the process.
>
>
> -Patrick
>
> On Fri, Jan 9, 2015 at 8:38 AM, Jeremy Stanley  wrote:
>
>> On 2015-01-09 08:28:39 -0800 (-0800), Patrick East wrote:
>> [...]
>> > On a related note, I am having issues with the ssh keys. Nodepool
>> > is able to log in to the node to set up the template and create an
>> > image from it, but then fails to log in to a build node. Have you
>> > run into any issues with that?
>>
>> Your image build needs to do _something_ to make SSH into the
>> resulting nodes possible. We accomplish that by applying a puppet
>> manifest which sets up an authorized_keys file for the account we
>> want it to use, but there are countless ways you could go about it
>> in your environment.
>> --
>> Jeremy Stanley
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com

*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-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-09 Thread Patrick East

Ah yea, sorry, should have specified; I am having it run
the prepare_node_devstack.sh from the infra repo. I see it adding the same
public key to the user specified in my nodepool.yaml. The strange part (and
I need to double check.. feel like it can't be right) is that on my master
node the nodepool users id_rsa changed at some point in the process.

-Patrick

On Fri, Jan 9, 2015 at 8:38 AM, Jeremy Stanley  wrote:

> On 2015-01-09 08:28:39 -0800 (-0800), Patrick East wrote:
> [...]
> > On a related note, I am having issues with the ssh keys. Nodepool
> > is able to log in to the node to set up the template and create an
> > image from it, but then fails to log in to a build node. Have you
> > run into any issues with that?
>
> Your image build needs to do _something_ to make SSH into the
> resulting nodes possible. We accomplish that by applying a puppet
> manifest which sets up an authorized_keys file for the account we
> want it to use, but there are countless ways you could go about it
> in your environment.
> --
> Jeremy Stanley
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-09 Thread Jeremy Stanley

On 2015-01-09 08:28:39 -0800 (-0800), Patrick East wrote:
[...]
> On a related note, I am having issues with the ssh keys. Nodepool
> is able to log in to the node to set up the template and create an
> image from it, but then fails to log in to a build node. Have you
> run into any issues with that?

Your image build needs to do _something_ to make SSH into the
resulting nodes possible. We accomplish that by applying a puppet
manifest which sets up an authorized_keys file for the account we
want it to use, but there are countless ways you could go about it
in your environment.
-- 
Jeremy Stanley

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-09 Thread Patrick East

Hi Eduard,

I am going through the same process of setting up a CI with the same
instructions/tools (migrating from one using jaypipes instructions w/
static slaves). What I learned the other day in IRC is that the gearman
plugin will only register the job if there are build slaves with labels
that can run the jobs. Make sure that your nodepool nodes are being created
and attached to jenkins correctly, if you only see instances with
"template" in the name my understanding is that those are used for snapshot
images and are not the actual build nodes.

On a related note, I am having issues with the ssh keys. Nodepool is able
to log in to the node to set up the template and create an image from it,
but then fails to log in to a build node. Have you run into any issues with
that?

-Patrick

On Fri, Jan 9, 2015 at 5:14 AM, Eduard Matei  wrote:

> Hi all,
> Back with the same error.
> Did a complete (clean) install based on rasselin's tutorial, now i have a
> working jenkins master + a dedicated cloud provider.
> Testing with noop looks ok, but dsvm-tempest-full returns NOT_REGISTERED.
>
> Here is some debug.log:
>
> 2015-01-09 14:08:06,772 DEBUG zuul.IndependentPipelineManager: Found job
> dsvm-tempest-full for change 
> 2015-01-09 14:08:06,773 INFO zuul.Gearman: Launch job dsvm-tempest-full
> for change  with dependent changes []
> 2015-01-09 14:08:06,773 DEBUG zuul.Gearman: Custom parameter function used
> for job dsvm-tempest-full, change: ,
> params: {'BASE_LOG_PATH': '85/139585/15/check', 'ZUUL_PIPELINE': 'check',
> 'OFFLINE_NODE_WHEN_COMPLETE': '1', 'ZUUL_UUID':
> 'fa4ca39e02b14d1d864725441e301eb0', 'LOG_PATH':
> '85/139585/15/check/dsvm-tempest-full/fa4ca39', 'ZUUL_CHANGE_IDS':
> u'139585,15', 'ZUUL_PATCHSET': '15', 'ZUUL_BRANCH': u'master', 'ZUUL_REF':
> u'refs/zuul/master/Z4efb72c817fb4ab39b67eb93fa8177ea', 'ZUUL_COMMIT':
> u'97c142345b12bdf6a48c89b00f0d4d7811ce4a55', 'ZUUL_URL': u'
> http://10.100.128.3/p/', 'ZUUL_CHANGE': '139585', 'ZUUL_CHANGES':
> u'openstack-dev/sandbox:master:refs/changes/85/139585/15', 'ZUUL_PROJECT':
> 'openstack-dev/sandbox'}
> ...
> 2015-01-09 14:08:06,837 DEBUG zuul.Gearman: Function
> build:dsvm-tempest-full is not registered
> 2015-01-09 14:08:06,837 ERROR zuul.Gearman: Job  handle: None name: build:dsvm-tempest-full unique:
> fa4ca39e02b14d1d864725441e301eb0> is not registered with Gearman
> 2015-01-09 14:08:06,837 INFO zuul.Gearman: Build  handle: None name: build:dsvm-tempest-full unique:
> fa4ca39e02b14d1d864725441e301eb0> complete, result NOT_REGISTERED
> 2015-01-09 14:08:06,837 DEBUG zuul.Scheduler: Adding complete event for
> build:  >
> 2015-01-09 14:08:06,837 DEBUG zuul.Scheduler: Done adding complete event
> for build:  >
> 2015-01-09 14:08:06,837 DEBUG zuul.IndependentPipelineManager: Adding
> build  > of job dsvm-tempest-full to item  0x7f8db17ba310 for  in check>
>
> So it seems that Zuul sees the job, but Gearman returns "is not
> registered".
>
> Any idea how to register it? I see it in Jenkins GUI.
> The only warning i see in Jenkins GUI is:
> There’s no slave/cloud that matches this assignment. Did you mean ‘master’
> instead of ‘devstack_slave’?
>
> On the cloud provider gui i see instances with names like (
> d-p-c-TIMESTAMP.template.openstack.org) spawning and running and some
> deleting.
>
> Thanks,
>
> Eduard
>
>
> On Tue, Jan 6, 2015 at 7:29 PM, Asselin, Ramy  wrote:
>
>>  Gearman worker threads is what is needed to actually run the job. You
>> need to type ‘status’ to get the results. It shouldn’t be empty since you
>> stated the job actually ran (and failed tempest)
>>
>> Publishing the result is controlled here in the zuul layout.yaml file
>> [1]. Make sure you’re not using the ‘silent’ pipeline which (obviously)
>> won’t publish the result. Manual is here [2]
>>
>> You’ll need a log server to host the uploaded log files. You can set one
>> up like –infra’s using this [3] or WIP [4]
>>
>>
>>
>> Ramy
>>
>>
>>
>> [1]
>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/zuul/layout.yaml#L22
>>
>> [2] http://ci.openstack.org/zuul/index.html
>>
>> [3]
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_log_server.sh
>>
>> [4] https://review.openstack.org/#/c/138913/
>>
>>
>>
>> *From:* Punith S [mailto:punit...@cloudbyte.com]
>> *Sent:* Monday, Janu

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-09 Thread Eduard Matei

Hi all,
Back with the same error.
Did a complete (clean) install based on rasselin's tutorial, now i have a
working jenkins master + a dedicated cloud provider.
Testing with noop looks ok, but dsvm-tempest-full returns NOT_REGISTERED.

Here is some debug.log:

2015-01-09 14:08:06,772 DEBUG zuul.IndependentPipelineManager: Found job
dsvm-tempest-full for change 
2015-01-09 14:08:06,773 INFO zuul.Gearman: Launch job dsvm-tempest-full for
change  with dependent changes []
2015-01-09 14:08:06,773 DEBUG zuul.Gearman: Custom parameter function used
for job dsvm-tempest-full, change: ,
params: {'BASE_LOG_PATH': '85/139585/15/check', 'ZUUL_PIPELINE': 'check',
'OFFLINE_NODE_WHEN_COMPLETE': '1', 'ZUUL_UUID':
'fa4ca39e02b14d1d864725441e301eb0', 'LOG_PATH':
'85/139585/15/check/dsvm-tempest-full/fa4ca39', 'ZUUL_CHANGE_IDS':
u'139585,15', 'ZUUL_PATCHSET': '15', 'ZUUL_BRANCH': u'master', 'ZUUL_REF':
u'refs/zuul/master/Z4efb72c817fb4ab39b67eb93fa8177ea', 'ZUUL_COMMIT':
u'97c142345b12bdf6a48c89b00f0d4d7811ce4a55', 'ZUUL_URL': u'
http://10.100.128.3/p/', 'ZUUL_CHANGE': '139585', 'ZUUL_CHANGES':
u'openstack-dev/sandbox:master:refs/changes/85/139585/15', 'ZUUL_PROJECT':
'openstack-dev/sandbox'}
...
2015-01-09 14:08:06,837 DEBUG zuul.Gearman: Function
build:dsvm-tempest-full is not registered
2015-01-09 14:08:06,837 ERROR zuul.Gearman: Job  is not registered with Gearman
2015-01-09 14:08:06,837 INFO zuul.Gearman: Build  complete, result NOT_REGISTERED
2015-01-09 14:08:06,837 DEBUG zuul.Scheduler: Adding complete event for
build: >
2015-01-09 14:08:06,837 DEBUG zuul.Scheduler: Done adding complete event
for build: >
2015-01-09 14:08:06,837 DEBUG zuul.IndependentPipelineManager: Adding build
> of job dsvm-tempest-full to item  in check>

So it seems that Zuul sees the job, but Gearman returns "is not registered".

Any idea how to register it? I see it in Jenkins GUI.
The only warning i see in Jenkins GUI is:
There’s no slave/cloud that matches this assignment. Did you mean ‘master’
instead of ‘devstack_slave’?

On the cloud provider gui i see instances with names like (
d-p-c-TIMESTAMP.template.openstack.org) spawning and running and some
deleting.

Thanks,

Eduard


On Tue, Jan 6, 2015 at 7:29 PM, Asselin, Ramy  wrote:

>  Gearman worker threads is what is needed to actually run the job. You
> need to type ‘status’ to get the results. It shouldn’t be empty since you
> stated the job actually ran (and failed tempest)
>
> Publishing the result is controlled here in the zuul layout.yaml file [1].
> Make sure you’re not using the ‘silent’ pipeline which (obviously) won’t
> publish the result. Manual is here [2]
>
> You’ll need a log server to host the uploaded log files. You can set one
> up like –infra’s using this [3] or WIP [4]
>
>
>
> Ramy
>
>
>
> [1]
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/zuul/layout.yaml#L22
>
> [2] http://ci.openstack.org/zuul/index.html
>
> [3]
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_log_server.sh
>
> [4] https://review.openstack.org/#/c/138913/
>
>
>
> *From:* Punith S [mailto:punit...@cloudbyte.com]
> *Sent:* Monday, January 05, 2015 10:22 PM
> *To:* Asselin, Ramy
> *Cc:* Eduard Matei; OpenStack Development Mailing List (not for usage
> questions)
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> thanks ramy :)
>
> i have setup the CI , but our dsvm-tempest-full job is failing due to some
> failures on running tempest.
> but how do we publish these failures to sandbox project.
> my gearman service is not showing any worker threads
>
> root@cimaster:/# telnet 127.0.0.1 4730
>
> Trying 127.0.0.1...
>
> Connected to 127.0.0.1.
>
> Escape character is '^]'.
>
>
>
> thanks
>
>
>
> On Sun, Jan 4, 2015 at 10:23 PM, Asselin, Ramy 
> wrote:
>
>  Did you try asking the friendly folks on IRC freenode #openstack-infra?
>
>
>
> You can also try:
>
> Rebooting.
>
> Delete all the Jenkins jobs and reloading them.
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Friday, December 26, 2014 1:30 AM
> *To:* Punith S
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> Asselin, Ramy
>
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> @Asselin:
>
> Regarding the "few items you can try": i tried eve

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2015-01-05 Thread Punith S

thanks ramy :)

i have setup the CI , but our dsvm-tempest-full job is failing due to some
failures on running tempest.
but how do we publish these failures to sandbox project.
my gearman service is not showing any worker threads

root@cimaster:/# telnet 127.0.0.1 4730
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.

thanks

On Sun, Jan 4, 2015 at 10:23 PM, Asselin, Ramy  wrote:

>  Did you try asking the friendly folks on IRC freenode #openstack-infra?
>
>
>
> You can also try:
>
> Rebooting.
>
> Delete all the Jenkins jobs and reloading them.
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Friday, December 26, 2014 1:30 AM
> *To:* Punith S
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> Asselin, Ramy
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> @Asselin:
>
> Regarding the "few items you can try": i tried everything, the job still
> appears NOT_REGISTERED.
>
> I'll see next week if i can do a clean install on another jenkins master.
>
>
>
> Thanks for your help,
>
> Eduard
>
>
>
> On Fri, Dec 26, 2014 at 11:23 AM, Punith S  wrote:
>
>  hello,
>
>
>
> i have setup the CI environment for our cloudbyte storage, running a
> master jenkins vm and a slave node vm running devstack.
>
>
>
> i have followed the jay's blog using asselin's scripts from github.
>
>
>
> all i need to do is to test our cloudbyte cinder driver against the cinder
> tempest suit.
>
>
>
> currently the noop-check-communication job is coming of successfully on
> openstack-dev/sandbox project
>
>
>
> but the *dvsm full tempest *job is failing due to an error in failing to
> upload the images to the glance service from swift.
>
>
>
> how can i hack the dsvm tempest full job so that it only installs my
> required services like cinder,nova,horizon etc. ?
>
>
>
> does modifying the devstack gate scripts help ?
>
>
>
> i'm attaching the links for the failure of dsvm-tempest-full job
>
>
>
> devstacklog.txt - http://paste.openstack.org/show/154779/
>
> devstack.txt.summary - http://paste.openstack.org/show/154780/
>
>
>
> thanks
>
>
>
>
>
>
>
>
>
> On Tue, Dec 23, 2014 at 8:46 PM, Asselin, Ramy 
> wrote:
>
>  You should use 14.04 for the slave. The limitation for using 12.04 is
> only for the master since zuul’s apache configuration is WIP on 14.04 [1],
> and zuul does not run on the slave.
>
> Ramy
>
> [1] https://review.openstack.org/#/c/141518/
>
> *From:* Punith S [mailto:punit...@cloudbyte.com]
> *Sent:* Monday, December 22, 2014 11:37 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Asselin,
>
>
>
> i'm following your readme https://github.com/rasselin/os-ext-testing
>
> for setting up our cloudbyte CI on two ubuntu 12.04 VM's(master and slave)
>
>
>
> currently the scripts and setup went fine as followed with the document.
>
>
>
> now both master and slave have been connected successfully, but in order
> to run the tempest integration test against our proposed cloudbyte cinder
> driver for kilo, we need to have devstack installed in the slave.(in my
> understanding)
>
>
>
> but on installing the master devstack i'm getting permission issues in
> 12.04 in executing ./stack.sh since master devstack suggests the 14.04 or
> 13.10 ubuntu. and on contrary running install_slave.sh is failing on 13.10
> due to puppet modules on found error.
>
>
>
>  is there a way to get this work ?
>
>
>
> thanks in advance
>
>
>
> On Mon, Dec 22, 2014 at 11:10 PM, Asselin, Ramy 
> wrote:
>
>  Eduard,
>
>
>
> A few items you can try:
>
> 1.   Double-check that the job is in Jenkins
>
> a.   If not, then that’s the issue
>
> 2.   Check that the processes are running correctly
>
> a.   ps -ef | grep zuul
>
>i.  Should
> have 2 zuul-server & 1 zuul-merger
>
> b.  ps -ef | grep Jenkins
>
>i.  Should
> have 1 /usr/bin/daemon --name=jenkins & 1 /usr/bin/java
>
> 3.   In Jenkins, Manage Jenkins, Gearman Plugin Config, “Test
> Connection”
>
> 4.   Stop and Zuul & Jenkins. Start Zuul & Jenkins
>
> a.   service Je

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-26 Thread Eduard Matei

@Asselin:
Regarding the "few items you can try": i tried everything, the job still
appears NOT_REGISTERED.
I'll see next week if i can do a clean install on another jenkins master.

Thanks for your help,
Eduard

On Fri, Dec 26, 2014 at 11:23 AM, Punith S  wrote:

> hello,
>
> i have setup the CI environment for our cloudbyte storage, running a
> master jenkins vm and a slave node vm running devstack.
>
> i have followed the jay's blog using asselin's scripts from github.
>
> all i need to do is to test our cloudbyte cinder driver against the cinder
> tempest suit.
>
> currently the noop-check-communication job is coming of successfully on
> openstack-dev/sandbox project
>
> but the *dvsm full tempest *job is failing due to an error in failing to
> upload the images to the glance service from swift.
>
> how can i hack the dsvm tempest full job so that it only installs my
> required services like cinder,nova,horizon etc. ?
>
> does modifying the devstack gate scripts help ?
>
> i'm attaching the links for the failure of dsvm-tempest-full job
>
> devstacklog.txt - http://paste.openstack.org/show/154779/
> devstack.txt.summary - http://paste.openstack.org/show/154780/
>
> thanks
>
>
>
>
> On Tue, Dec 23, 2014 at 8:46 PM, Asselin, Ramy 
> wrote:
>
>>  You should use 14.04 for the slave. The limitation for using 12.04 is
>> only for the master since zuul’s apache configuration is WIP on 14.04 [1],
>> and zuul does not run on the slave.
>>
>> Ramy
>>
>> [1] https://review.openstack.org/#/c/141518/
>>
>> *From:* Punith S [mailto:punit...@cloudbyte.com]
>> *Sent:* Monday, December 22, 2014 11:37 PM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi Asselin,
>>
>>
>>
>> i'm following your readme https://github.com/rasselin/os-ext-testing
>>
>> for setting up our cloudbyte CI on two ubuntu 12.04 VM's(master and slave)
>>
>>
>>
>> currently the scripts and setup went fine as followed with the document.
>>
>>
>>
>> now both master and slave have been connected successfully, but in order
>> to run the tempest integration test against our proposed cloudbyte cinder
>> driver for kilo, we need to have devstack installed in the slave.(in my
>> understanding)
>>
>>
>>
>> but on installing the master devstack i'm getting permission issues in
>> 12.04 in executing ./stack.sh since master devstack suggests the 14.04 or
>> 13.10 ubuntu. and on contrary running install_slave.sh is failing on 13.10
>> due to puppet modules on found error.
>>
>>
>>
>>  is there a way to get this work ?
>>
>>
>>
>> thanks in advance
>>
>>
>>
>> On Mon, Dec 22, 2014 at 11:10 PM, Asselin, Ramy 
>> wrote:
>>
>>  Eduard,
>>
>>
>>
>> A few items you can try:
>>
>> 1.   Double-check that the job is in Jenkins
>>
>> a.   If not, then that’s the issue
>>
>> 2.   Check that the processes are running correctly
>>
>> a.   ps -ef | grep zuul
>>
>>i.  Should
>> have 2 zuul-server & 1 zuul-merger
>>
>> b.  ps -ef | grep Jenkins
>>
>>i.  Should
>> have 1 /usr/bin/daemon --name=jenkins & 1 /usr/bin/java
>>
>> 3.   In Jenkins, Manage Jenkins, Gearman Plugin Config, “Test
>> Connection”
>>
>> 4.   Stop and Zuul & Jenkins. Start Zuul & Jenkins
>>
>> a.   service Jenkins stop
>>
>> b.  service zuul stop
>>
>> c.   service zuul-merger stop
>>
>> d.  service Jenkins start
>>
>> e.  service zuul start
>>
>> f.service zuul-merger start
>>
>>
>>
>> Otherwise, I suggest you ask in #openstack-infra irc channel.
>>
>>
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Sunday, December 21, 2014 11:01 PM
>>
>>
>> *To:* Asselin, Ramy
>> *Cc:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Thanks Ramy,
>>
>>
>>
>> Unfortunately i don'

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-26 Thread Punith S

hello,

i have setup the CI environment for our cloudbyte storage, running a master
jenkins vm and a slave node vm running devstack.

i have followed the jay's blog using asselin's scripts from github.

all i need to do is to test our cloudbyte cinder driver against the cinder
tempest suit.

currently the noop-check-communication job is coming of successfully on
openstack-dev/sandbox project

but the *dvsm full tempest *job is failing due to an error in failing to
upload the images to the glance service from swift.

how can i hack the dsvm tempest full job so that it only installs my
required services like cinder,nova,horizon etc. ?

does modifying the devstack gate scripts help ?

i'm attaching the links for the failure of dsvm-tempest-full job

devstacklog.txt - http://paste.openstack.org/show/154779/
devstack.txt.summary - http://paste.openstack.org/show/154780/

thanks




On Tue, Dec 23, 2014 at 8:46 PM, Asselin, Ramy  wrote:

>  You should use 14.04 for the slave. The limitation for using 12.04 is
> only for the master since zuul’s apache configuration is WIP on 14.04 [1],
> and zuul does not run on the slave.
>
> Ramy
>
> [1] https://review.openstack.org/#/c/141518/
>
> *From:* Punith S [mailto:punit...@cloudbyte.com]
> *Sent:* Monday, December 22, 2014 11:37 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Asselin,
>
>
>
> i'm following your readme https://github.com/rasselin/os-ext-testing
>
> for setting up our cloudbyte CI on two ubuntu 12.04 VM's(master and slave)
>
>
>
> currently the scripts and setup went fine as followed with the document.
>
>
>
> now both master and slave have been connected successfully, but in order
> to run the tempest integration test against our proposed cloudbyte cinder
> driver for kilo, we need to have devstack installed in the slave.(in my
> understanding)
>
>
>
> but on installing the master devstack i'm getting permission issues in
> 12.04 in executing ./stack.sh since master devstack suggests the 14.04 or
> 13.10 ubuntu. and on contrary running install_slave.sh is failing on 13.10
> due to puppet modules on found error.
>
>
>
>  is there a way to get this work ?
>
>
>
> thanks in advance
>
>
>
> On Mon, Dec 22, 2014 at 11:10 PM, Asselin, Ramy 
> wrote:
>
>  Eduard,
>
>
>
> A few items you can try:
>
> 1.   Double-check that the job is in Jenkins
>
> a.   If not, then that’s the issue
>
> 2.   Check that the processes are running correctly
>
> a.   ps -ef | grep zuul
>
>i.  Should
> have 2 zuul-server & 1 zuul-merger
>
> b.  ps -ef | grep Jenkins
>
>i.  Should
> have 1 /usr/bin/daemon --name=jenkins & 1 /usr/bin/java
>
> 3.   In Jenkins, Manage Jenkins, Gearman Plugin Config, “Test
> Connection”
>
> 4.   Stop and Zuul & Jenkins. Start Zuul & Jenkins
>
> a.   service Jenkins stop
>
> b.  service zuul stop
>
> c.   service zuul-merger stop
>
> d.  service Jenkins start
>
> e.  service zuul start
>
> f.service zuul-merger start
>
>
>
> Otherwise, I suggest you ask in #openstack-infra irc channel.
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Sunday, December 21, 2014 11:01 PM
>
>
> *To:* Asselin, Ramy
> *Cc:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Thanks Ramy,
>
>
>
> Unfortunately i don't see dsvm-tempest-full in the "status" output.
>
> Any idea how i can get it "registered"?
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Fri, Dec 19, 2014 at 9:43 PM, Asselin, Ramy 
> wrote:
>
>  Eduard,
>
>
>
> If you run this command, you can see which jobs are registered:
>
> >telnet localhost 4730
>
>
>
> >status
>
>
>
> There are 3 numbers per job: queued, running and workers that can run job.
> Make sure the job is listed & last ‘workers’ is non-zero.
>
>
>
> To run the job again without submitting a patch set, leave a “recheck”
> comment on the patch & make sure your zuul layout.yaml is configured to
> trigger off that comment. For example [1].
>
> Be sure to use the sandbox repository. [2]
>
> I’m not aware of other ways.
>
>
>
> Ra

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-23 Thread Asselin, Ramy

You should use 14.04 for the slave. The limitation for using 12.04 is only for 
the master since zuul’s apache configuration is WIP on 14.04 [1], and zuul does 
not run on the slave.
Ramy
[1] https://review.openstack.org/#/c/141518/
From: Punith S [mailto:punit...@cloudbyte.com]
Sent: Monday, December 22, 2014 11:37 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi Asselin,

i'm following your readme https://github.com/rasselin/os-ext-testing
for setting up our cloudbyte CI on two ubuntu 12.04 VM's(master and slave)

currently the scripts and setup went fine as followed with the document.

now both master and slave have been connected successfully, but in order to run 
the tempest integration test against our proposed cloudbyte cinder driver for 
kilo, we need to have devstack installed in the slave.(in my understanding)

but on installing the master devstack i'm getting permission issues in 12.04 in 
executing ./stack.sh since master devstack suggests the 14.04 or 13.10 ubuntu. 
and on contrary running install_slave.sh is failing on 13.10 due to puppet 
modules on found error.

 is there a way to get this work ?

thanks in advance

On Mon, Dec 22, 2014 at 11:10 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
Eduard,

A few items you can try:

1.   Double-check that the job is in Jenkins

a.   If not, then that’s the issue

2.   Check that the processes are running correctly

a.   ps -ef | grep zuul

   i.  Should 
have 2 zuul-server & 1 zuul-merger

b.  ps -ef | grep Jenkins

   i.  Should 
have 1 /usr/bin/daemon --name=jenkins & 1 /usr/bin/java

3.   In Jenkins, Manage Jenkins, Gearman Plugin Config, “Test Connection”

4.   Stop and Zuul & Jenkins. Start Zuul & Jenkins

a.   service Jenkins stop

b.  service zuul stop

c.   service zuul-merger stop

d.  service Jenkins start

e.  service zuul start

f.service zuul-merger start

Otherwise, I suggest you ask in #openstack-infra irc channel.

Ramy

From: Eduard Matei 
[mailto:eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>]
Sent: Sunday, December 21, 2014 11:01 PM

To: Asselin, Ramy
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Thanks Ramy,

Unfortunately i don't see dsvm-tempest-full in the "status" output.
Any idea how i can get it "registered"?

Thanks,
Eduard

On Fri, Dec 19, 2014 at 9:43 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
Eduard,

If you run this command, you can see which jobs are registered:
>telnet localhost 4730

>status

There are 3 numbers per job: queued, running and workers that can run job. Make 
sure the job is listed & last ‘workers’ is non-zero.

To run the job again without submitting a patch set, leave a “recheck” comment 
on the patch & make sure your zuul layout.yaml is configured to trigger off 
that comment. For example [1].
Be sure to use the sandbox repository. [2]
I’m not aware of other ways.

Ramy

[1] 
https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml#L20
[2] https://github.com/openstack-dev/sandbox

From: Eduard Matei 
[mailto:eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>]
Sent: Friday, December 19, 2014 3:36 AM
To: Asselin, Ramy
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi all,
After a little struggle with the config scripts i managed to get a working 
setup that is able to process openstack-dev/sandbox and run 
noop-check-comunication.

Then, i tried enabling dsvm-tempest-full job but it keeps returning 
"NOT_REGISTERED"

2014-12-19 12:07:14,683 INFO zuul.IndependentPipelineManager: Change  depends on changes []
2014-12-19 12:07:14,683 INFO zuul.Gearman: Launch job noop-check-communication 
for change  with dependent changes []
2014-12-19 12:07:14,693 INFO zuul.Gearman: Launch job dsvm-tempest-full for 
change  with dependent changes []
2014-12-19 12:07:14,694 ERROR zuul.Gearman: Job  is not registered with Gearman
2014-12-19 12:07:14,694 INFO zuul.Gearman: Build  complete, result NOT_REGISTERED
2014-12-19 12:07:14,765 INFO zuul.Gearman: Build http://127.0.0.1:2> name: build:noop-check-communication 
unique: 333c6ea077324a788e3c37a313d872c5> started
2014-12-19 12:07:14,910 INFO zuul.Gearman: Build http://127.0.0.1:2> name: build:noop-check-communication 
unique: 333c6ea077324a788e3c37a313d872c5> complete, result SUCCESS
2014-12-19 12:07:14,916 INFO zuul.IndependentPipelineManager: Reporting change 
, act

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-22 Thread Punith S

Hi Asselin,

i'm following your readme https://github.com/rasselin/os-ext-testing
for setting up our cloudbyte CI on two ubuntu 12.04 VM's(master and slave)

currently the scripts and setup went fine as followed with the document.

now both master and slave have been connected successfully, but in order to
run the tempest integration test against our proposed cloudbyte cinder
driver for kilo, we need to have devstack installed in the slave.(in my
understanding)

but on installing the master devstack i'm getting permission issues in
12.04 in executing ./stack.sh since master devstack suggests the 14.04 or
13.10 ubuntu. and on contrary running install_slave.sh is failing on 13.10
due to puppet modules on found error.

 is there a way to get this work ?

thanks in advance

On Mon, Dec 22, 2014 at 11:10 PM, Asselin, Ramy  wrote:

>  Eduard,
>
>
>
> A few items you can try:
>
> 1.   Double-check that the job is in Jenkins
>
> a.   If not, then that’s the issue
>
> 2.   Check that the processes are running correctly
>
> a.   ps -ef | grep zuul
>
>i.  Should
> have 2 zuul-server & 1 zuul-merger
>
> b.  ps -ef | grep Jenkins
>
>i.  Should
> have 1 /usr/bin/daemon --name=jenkins & 1 /usr/bin/java
>
> 3.   In Jenkins, Manage Jenkins, Gearman Plugin Config, “Test
> Connection”
>
> 4.   Stop and Zuul & Jenkins. Start Zuul & Jenkins
>
> a.   service Jenkins stop
>
> b.  service zuul stop
>
> c.   service zuul-merger stop
>
> d.  service Jenkins start
>
> e.  service zuul start
>
> f.service zuul-merger start
>
>
>
> Otherwise, I suggest you ask in #openstack-infra irc channel.
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Sunday, December 21, 2014 11:01 PM
>
> *To:* Asselin, Ramy
> *Cc:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Thanks Ramy,
>
>
>
> Unfortunately i don't see dsvm-tempest-full in the "status" output.
>
> Any idea how i can get it "registered"?
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Fri, Dec 19, 2014 at 9:43 PM, Asselin, Ramy 
> wrote:
>
>  Eduard,
>
>
>
> If you run this command, you can see which jobs are registered:
>
> >telnet localhost 4730
>
>
>
> >status
>
>
>
> There are 3 numbers per job: queued, running and workers that can run job.
> Make sure the job is listed & last ‘workers’ is non-zero.
>
>
>
> To run the job again without submitting a patch set, leave a “recheck”
> comment on the patch & make sure your zuul layout.yaml is configured to
> trigger off that comment. For example [1].
>
> Be sure to use the sandbox repository. [2]
>
> I’m not aware of other ways.
>
>
>
> Ramy
>
>
>
> [1]
> https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml#L20
>
> [2] https://github.com/openstack-dev/sandbox
>
>
>
>
>
>
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Friday, December 19, 2014 3:36 AM
> *To:* Asselin, Ramy
> *Cc:* OpenStack Development Mailing List (not for usage questions)
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi all,
>
> After a little struggle with the config scripts i managed to get a working
> setup that is able to process openstack-dev/sandbox and run
> noop-check-comunication.
>
>
>
> Then, i tried enabling dsvm-tempest-full job but it keeps returning
> "NOT_REGISTERED"
>
>
>
> 2014-12-19 12:07:14,683 INFO zuul.IndependentPipelineManager: Change
>  depends on changes []
>
> 2014-12-19 12:07:14,683 INFO zuul.Gearman: Launch job
> noop-check-communication for change  with
> dependent changes []
>
> 2014-12-19 12:07:14,693 INFO zuul.Gearman: Launch job dsvm-tempest-full
> for change  with dependent changes []
>
> 2014-12-19 12:07:14,694 ERROR zuul.Gearman: Job  handle: None name: build:dsvm-tempest-full unique:
> a9199d304d1140a8bf4448dfb1ae42c1> is not registered with Gearman
>
> 2014-12-19 12:07:14,694 INFO zuul.Gearman: Build  handle: None name: build:dsvm-tempest-full unique:
> a9199d304d1140a8bf4448dfb1ae42c1> complete, result NOT_REGISTERED
>
> 2014-12-19 12:07:14,765 INFO zuul.Gearman: Build  handle: H:127.0.0.1:2 name: build:noop-check-communi

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-22 Thread Asselin, Ramy

Eduard,

A few items you can try:

1.   Double-check that the job is in Jenkins

a.   If not, then that’s the issue

2.   Check that the processes are running correctly

a.   ps -ef | grep zuul

   i.  Should 
have 2 zuul-server & 1 zuul-merger

b.  ps -ef | grep Jenkins

   i.  Should 
have 1 /usr/bin/daemon --name=jenkins & 1 /usr/bin/java

3.   In Jenkins, Manage Jenkins, Gearman Plugin Config, “Test Connection”

4.   Stop and Zuul & Jenkins. Start Zuul & Jenkins

a.   service Jenkins stop

b.  service zuul stop

c.   service zuul-merger stop

d.  service Jenkins start

e.  service zuul start

f.service zuul-merger start

Otherwise, I suggest you ask in #openstack-infra irc channel.

Ramy

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Sunday, December 21, 2014 11:01 PM
To: Asselin, Ramy
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Thanks Ramy,

Unfortunately i don't see dsvm-tempest-full in the "status" output.
Any idea how i can get it "registered"?

Thanks,
Eduard

On Fri, Dec 19, 2014 at 9:43 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
Eduard,

If you run this command, you can see which jobs are registered:
>telnet localhost 4730

>status

There are 3 numbers per job: queued, running and workers that can run job. Make 
sure the job is listed & last ‘workers’ is non-zero.

To run the job again without submitting a patch set, leave a “recheck” comment 
on the patch & make sure your zuul layout.yaml is configured to trigger off 
that comment. For example [1].
Be sure to use the sandbox repository. [2]
I’m not aware of other ways.

Ramy

[1] 
https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml#L20
[2] https://github.com/openstack-dev/sandbox

From: Eduard Matei 
[mailto:eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>]
Sent: Friday, December 19, 2014 3:36 AM
To: Asselin, Ramy
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi all,
After a little struggle with the config scripts i managed to get a working 
setup that is able to process openstack-dev/sandbox and run 
noop-check-comunication.

Then, i tried enabling dsvm-tempest-full job but it keeps returning 
"NOT_REGISTERED"

2014-12-19 12:07:14,683 INFO zuul.IndependentPipelineManager: Change  depends on changes []
2014-12-19 12:07:14,683 INFO zuul.Gearman: Launch job noop-check-communication 
for change  with dependent changes []
2014-12-19 12:07:14,693 INFO zuul.Gearman: Launch job dsvm-tempest-full for 
change  with dependent changes []
2014-12-19 12:07:14,694 ERROR zuul.Gearman: Job  is not registered with Gearman
2014-12-19 12:07:14,694 INFO zuul.Gearman: Build  complete, result NOT_REGISTERED
2014-12-19 12:07:14,765 INFO zuul.Gearman: Build http://127.0.0.1:2> name: build:noop-check-communication 
unique: 333c6ea077324a788e3c37a313d872c5> started
2014-12-19 12:07:14,910 INFO zuul.Gearman: Build http://127.0.0.1:2> name: build:noop-check-communication 
unique: 333c6ea077324a788e3c37a313d872c5> complete, result SUCCESS
2014-12-19 12:07:14,916 INFO zuul.IndependentPipelineManager: Reporting change 
, actions: [, {'verified': -1}>]

Nodepoold's log show no reference to dsvm-tempest-full and neither jenkins' 
logs.

Any idea how to enable this job?

Also, i got the "Cloud provider" setup and i can access it from the jenkins 
master.
Any idea how i can manually trigger dsvm-tempest-full job to run and test the 
cloud provider without having to push a review to Gerrit?

Thanks,
Eduard

On Thu, Dec 18, 2014 at 7:52 PM, Eduard Matei 
mailto:eduard.ma...@cloudfounders.com>> wrote:
Thanks for the input.

I managed to get another master working (on Ubuntu 13.10), again with some 
issues since it was already setup.
I'm now working towards setting up the slave.

Will add comments to those reviews.

Thanks,
Eduard

On Thu, Dec 18, 2014 at 7:42 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
Yes, Ubuntu 12.04 is tested as mentioned in the readme [1]. Note that the 
referenced script is just a wrapper that pulls all the latest from various 
locations in openstack-infra, e.g. [2].
Ubuntu 14.04 support is WIP [3]
FYI, there’s a spec to get an in-tree 3rd party ci solution [4]. Please add 
your comments if this interests you.

[1] https://github.com/rasselin/os-ext-testing/blob/master/README.md
[2] 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L29
[3] https://review.openstack.org/#/c/141518/
[4] https://review.openstac

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-21 Thread Eduard Matei

Thanks Ramy,

Unfortunately i don't see dsvm-tempest-full in the "status" output.
Any idea how i can get it "registered"?

Thanks,
Eduard

On Fri, Dec 19, 2014 at 9:43 PM, Asselin, Ramy  wrote:
>
>  Eduard,
>
>
>
> If you run this command, you can see which jobs are registered:
>
> >telnet localhost 4730
>
>
>
> >status
>
>
>
> There are 3 numbers per job: queued, running and workers that can run job.
> Make sure the job is listed & last ‘workers’ is non-zero.
>
>
>
> To run the job again without submitting a patch set, leave a “recheck”
> comment on the patch & make sure your zuul layout.yaml is configured to
> trigger off that comment. For example [1].
>
> Be sure to use the sandbox repository. [2]
>
> I’m not aware of other ways.
>
>
>
> Ramy
>
>
>
> [1]
> https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml#L20
>
> [2] https://github.com/openstack-dev/sandbox
>
>
>
>
>
>
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Friday, December 19, 2014 3:36 AM
> *To:* Asselin, Ramy
> *Cc:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi all,
>
> After a little struggle with the config scripts i managed to get a working
> setup that is able to process openstack-dev/sandbox and run
> noop-check-comunication.
>
>
>
> Then, i tried enabling dsvm-tempest-full job but it keeps returning
> "NOT_REGISTERED"
>
>
>
> 2014-12-19 12:07:14,683 INFO zuul.IndependentPipelineManager: Change
>  depends on changes []
>
> 2014-12-19 12:07:14,683 INFO zuul.Gearman: Launch job
> noop-check-communication for change  with
> dependent changes []
>
> 2014-12-19 12:07:14,693 INFO zuul.Gearman: Launch job dsvm-tempest-full
> for change  with dependent changes []
>
> 2014-12-19 12:07:14,694 ERROR zuul.Gearman: Job  handle: None name: build:dsvm-tempest-full unique:
> a9199d304d1140a8bf4448dfb1ae42c1> is not registered with Gearman
>
> 2014-12-19 12:07:14,694 INFO zuul.Gearman: Build  handle: None name: build:dsvm-tempest-full unique:
> a9199d304d1140a8bf4448dfb1ae42c1> complete, result NOT_REGISTERED
>
> 2014-12-19 12:07:14,765 INFO zuul.Gearman: Build  handle: H:127.0.0.1:2 name: build:noop-check-communication unique:
> 333c6ea077324a788e3c37a313d872c5> started
>
> 2014-12-19 12:07:14,910 INFO zuul.Gearman: Build  handle: H:127.0.0.1:2 name: build:noop-check-communication unique:
> 333c6ea077324a788e3c37a313d872c5> complete, result SUCCESS
>
> 2014-12-19 12:07:14,916 INFO zuul.IndependentPipelineManager: Reporting
> change , actions: [ , {'verified': -1}>]
>
>
>
> Nodepoold's log show no reference to dsvm-tempest-full and neither
> jenkins' logs.
>
>
>
> Any idea how to enable this job?
>
>
>
> Also, i got the "Cloud provider" setup and i can access it from the
> jenkins master.
>
> Any idea how i can manually trigger dsvm-tempest-full job to run and test
> the cloud provider without having to push a review to Gerrit?
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Thu, Dec 18, 2014 at 7:52 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Thanks for the input.
>
>
>
> I managed to get another master working (on Ubuntu 13.10), again with some
> issues since it was already setup.
>
> I'm now working towards setting up the slave.
>
>
>
> Will add comments to those reviews.
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Thu, Dec 18, 2014 at 7:42 PM, Asselin, Ramy 
> wrote:
>
>  Yes, Ubuntu 12.04 is tested as mentioned in the readme [1]. Note that
> the referenced script is just a wrapper that pulls all the latest from
> various locations in openstack-infra, e.g. [2].
>
> Ubuntu 14.04 support is WIP [3]
>
> FYI, there’s a spec to get an in-tree 3rd party ci solution [4]. Please
> add your comments if this interests you.
>
>
>
> [1] https://github.com/rasselin/os-ext-testing/blob/master/README.md
>
> [2]
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L29
>
> [3] https://review.openstack.org/#/c/141518/
>
> [4] https://review.openstack.org/#/c/139745/
>
>
>
>
>
> *From:* Punith S [mailto:punit...@cloudbyte.com]
> *Sent:* Thursday, December 18, 2014 3:12 AM
> *To:* OpenStack Development Mailing List (not for usage questions);
> Eduard Matei
>
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-19 Thread Asselin, Ramy

Eduard,

If you run this command, you can see which jobs are registered:
>telnet localhost 4730

>status

There are 3 numbers per job: queued, running and workers that can run job. Make 
sure the job is listed & last ‘workers’ is non-zero.

To run the job again without submitting a patch set, leave a “recheck” comment 
on the patch & make sure your zuul layout.yaml is configured to trigger off 
that comment. For example [1].
Be sure to use the sandbox repository. [2]
I’m not aware of other ways.

Ramy

[1] 
https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml#L20
[2] https://github.com/openstack-dev/sandbox

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Friday, December 19, 2014 3:36 AM
To: Asselin, Ramy
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi all,
After a little struggle with the config scripts i managed to get a working 
setup that is able to process openstack-dev/sandbox and run 
noop-check-comunication.

Then, i tried enabling dsvm-tempest-full job but it keeps returning 
"NOT_REGISTERED"

2014-12-19 12:07:14,683 INFO zuul.IndependentPipelineManager: Change  depends on changes []
2014-12-19 12:07:14,683 INFO zuul.Gearman: Launch job noop-check-communication 
for change  with dependent changes []
2014-12-19 12:07:14,693 INFO zuul.Gearman: Launch job dsvm-tempest-full for 
change  with dependent changes []
2014-12-19 12:07:14,694 ERROR zuul.Gearman: Job  is not registered with Gearman
2014-12-19 12:07:14,694 INFO zuul.Gearman: Build  complete, result NOT_REGISTERED
2014-12-19 12:07:14,765 INFO zuul.Gearman: Build http://127.0.0.1:2> name: build:noop-check-communication 
unique: 333c6ea077324a788e3c37a313d872c5> started
2014-12-19 12:07:14,910 INFO zuul.Gearman: Build http://127.0.0.1:2> name: build:noop-check-communication 
unique: 333c6ea077324a788e3c37a313d872c5> complete, result SUCCESS
2014-12-19 12:07:14,916 INFO zuul.IndependentPipelineManager: Reporting change 
, actions: [, {'verified': -1}>]

Nodepoold's log show no reference to dsvm-tempest-full and neither jenkins' 
logs.

Any idea how to enable this job?

Also, i got the "Cloud provider" setup and i can access it from the jenkins 
master.
Any idea how i can manually trigger dsvm-tempest-full job to run and test the 
cloud provider without having to push a review to Gerrit?

Thanks,
Eduard

On Thu, Dec 18, 2014 at 7:52 PM, Eduard Matei 
mailto:eduard.ma...@cloudfounders.com>> wrote:
Thanks for the input.

I managed to get another master working (on Ubuntu 13.10), again with some 
issues since it was already setup.
I'm now working towards setting up the slave.

Will add comments to those reviews.

Thanks,
Eduard

On Thu, Dec 18, 2014 at 7:42 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
Yes, Ubuntu 12.04 is tested as mentioned in the readme [1]. Note that the 
referenced script is just a wrapper that pulls all the latest from various 
locations in openstack-infra, e.g. [2].
Ubuntu 14.04 support is WIP [3]
FYI, there’s a spec to get an in-tree 3rd party ci solution [4]. Please add 
your comments if this interests you.

[1] https://github.com/rasselin/os-ext-testing/blob/master/README.md
[2] 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L29
[3] https://review.openstack.org/#/c/141518/
[4] https://review.openstack.org/#/c/139745/

From: Punith S [mailto:punit...@cloudbyte.com<mailto:punit...@cloudbyte.com>]
Sent: Thursday, December 18, 2014 3:12 AM
To: OpenStack Development Mailing List (not for usage questions); Eduard Matei

Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi Eduard

we tried running 
https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
on ubuntu master 12.04, and it appears to be working fine on 12.04.

thanks

On Thu, Dec 18, 2014 at 1:57 PM, Eduard Matei 
mailto:eduard.ma...@cloudfounders.com>> wrote:
Hi,
Seems i can't install using puppet on the jenkins master using 
install_master.sh from 
https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
 because it's running Ubuntu 11.10 and it appears unsupported.
I managed to install puppet manually on master and everything else fails
So i'm trying to manually install zuul and nodepool and jenkins job builder, 
see where i end up.

The slave looks complete, got some errors on running install_slave so i ran 
parts of the script manually, changing some params and it appears installed but 
no way to test it without the master.

Any ideas welcome.

Thanks,

Eduard

On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
Manually running the script requires a few environment settings. Take a look at 
the README here:
ht

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-19 Thread Eduard Matei

Hi all,
After a little struggle with the config scripts i managed to get a working
setup that is able to process openstack-dev/sandbox and run
noop-check-comunication.

Then, i tried enabling dsvm-tempest-full job but it keeps returning
"NOT_REGISTERED"

2014-12-19 12:07:14,683 INFO zuul.IndependentPipelineManager: Change
 depends on changes []
2014-12-19 12:07:14,683 INFO zuul.Gearman: Launch job
noop-check-communication for change  with
dependent changes []
2014-12-19 12:07:14,693 INFO zuul.Gearman: Launch job dsvm-tempest-full for
change  with dependent changes []
2014-12-19 12:07:14,694 ERROR zuul.Gearman: Job  is not registered with Gearman
2014-12-19 12:07:14,694 INFO zuul.Gearman: Build  complete, result NOT_REGISTERED
2014-12-19 12:07:14,765 INFO zuul.Gearman: Build  started
2014-12-19 12:07:14,910 INFO zuul.Gearman: Build  complete, result SUCCESS
2014-12-19 12:07:14,916 INFO zuul.IndependentPipelineManager: Reporting
change , actions: [, {'verified': -1}>]

Nodepoold's log show no reference to dsvm-tempest-full and neither jenkins'
logs.

Any idea how to enable this job?

Also, i got the "Cloud provider" setup and i can access it from the jenkins
master.
Any idea how i can manually trigger dsvm-tempest-full job to run and test
the cloud provider without having to push a review to Gerrit?

Thanks,
Eduard

On Thu, Dec 18, 2014 at 7:52 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:
>
> Thanks for the input.
>
> I managed to get another master working (on Ubuntu 13.10), again with some
> issues since it was already setup.
> I'm now working towards setting up the slave.
>
> Will add comments to those reviews.
>
> Thanks,
> Eduard
>
> On Thu, Dec 18, 2014 at 7:42 PM, Asselin, Ramy 
> wrote:
>
>>  Yes, Ubuntu 12.04 is tested as mentioned in the readme [1]. Note that
>> the referenced script is just a wrapper that pulls all the latest from
>> various locations in openstack-infra, e.g. [2].
>>
>> Ubuntu 14.04 support is WIP [3]
>>
>> FYI, there’s a spec to get an in-tree 3rd party ci solution [4]. Please
>> add your comments if this interests you.
>>
>>
>>
>> [1] https://github.com/rasselin/os-ext-testing/blob/master/README.md
>>
>> [2]
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L29
>>
>> [3] https://review.openstack.org/#/c/141518/
>>
>> [4] https://review.openstack.org/#/c/139745/
>>
>>
>>
>>
>>
>> *From:* Punith S [mailto:punit...@cloudbyte.com]
>> *Sent:* Thursday, December 18, 2014 3:12 AM
>> *To:* OpenStack Development Mailing List (not for usage questions);
>> Eduard Matei
>>
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi Eduard
>>
>>
>>
>> we tried running
>> https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
>>
>> on ubuntu master 12.04, and it appears to be working fine on 12.04.
>>
>>
>>
>> thanks
>>
>>
>>
>> On Thu, Dec 18, 2014 at 1:57 PM, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>  Hi,
>>
>> Seems i can't install using puppet on the jenkins master using
>> install_master.sh from
>> https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
>> because it's running Ubuntu 11.10 and it appears unsupported.
>>
>> I managed to install puppet manually on master and everything else fails
>>
>> So i'm trying to manually install zuul and nodepool and jenkins job
>> builder, see where i end up.
>>
>>
>>
>> The slave looks complete, got some errors on running install_slave so i
>> ran parts of the script manually, changing some params and it appears
>> installed but no way to test it without the master.
>>
>>
>>
>> Any ideas welcome.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Eduard
>>
>>
>>
>> On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy 
>> wrote:
>>
>>   Manually running the script requires a few environment settings. Take
>> a look at the README here:
>>
>> https://github.com/openstack-infra/devstack-gate
>>
>>
>>
>> Regarding cinder, I’m using this repo to run our cinder jobs (fork from
>> jaypipes).
>>
>> https://github.com/rasselin/os-ext-testing
>>
>>
>>
>> Note that this solution doesn’t use the Jenkins gerrit trigger pluggin,
>> but zuul.
>>
>>
>>

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-18 Thread Eduard Matei

Thanks for the input.

I managed to get another master working (on Ubuntu 13.10), again with some
issues since it was already setup.
I'm now working towards setting up the slave.

Will add comments to those reviews.

Thanks,
Eduard

On Thu, Dec 18, 2014 at 7:42 PM, Asselin, Ramy  wrote:

>  Yes, Ubuntu 12.04 is tested as mentioned in the readme [1]. Note that
> the referenced script is just a wrapper that pulls all the latest from
> various locations in openstack-infra, e.g. [2].
>
> Ubuntu 14.04 support is WIP [3]
>
> FYI, there’s a spec to get an in-tree 3rd party ci solution [4]. Please
> add your comments if this interests you.
>
>
>
> [1] https://github.com/rasselin/os-ext-testing/blob/master/README.md
>
> [2]
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L29
>
> [3] https://review.openstack.org/#/c/141518/
>
> [4] https://review.openstack.org/#/c/139745/
>
>
>
>
>
> *From:* Punith S [mailto:punit...@cloudbyte.com]
> *Sent:* Thursday, December 18, 2014 3:12 AM
> *To:* OpenStack Development Mailing List (not for usage questions);
> Eduard Matei
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Eduard
>
>
>
> we tried running
> https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
>
> on ubuntu master 12.04, and it appears to be working fine on 12.04.
>
>
>
> thanks
>
>
>
> On Thu, Dec 18, 2014 at 1:57 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi,
>
> Seems i can't install using puppet on the jenkins master using
> install_master.sh from
> https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
> because it's running Ubuntu 11.10 and it appears unsupported.
>
> I managed to install puppet manually on master and everything else fails
>
> So i'm trying to manually install zuul and nodepool and jenkins job
> builder, see where i end up.
>
>
>
> The slave looks complete, got some errors on running install_slave so i
> ran parts of the script manually, changing some params and it appears
> installed but no way to test it without the master.
>
>
>
> Any ideas welcome.
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy 
> wrote:
>
>   Manually running the script requires a few environment settings. Take a
> look at the README here:
>
> https://github.com/openstack-infra/devstack-gate
>
>
>
> Regarding cinder, I’m using this repo to run our cinder jobs (fork from
> jaypipes).
>
> https://github.com/rasselin/os-ext-testing
>
>
>
> Note that this solution doesn’t use the Jenkins gerrit trigger pluggin,
> but zuul.
>
>
>
> There’s a sample job for cinder here. It’s in Jenkins Job Builder format.
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample
>
>
>
> You can ask more questions in IRC freenode #openstack-cinder. (irc#
> asselin)
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Tuesday, December 16, 2014 12:41 AM
> *To:* Bailey, Darragh
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> OpenStack
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi,
>
>
>
> Can someone point me to some working documentation on how to setup third
> party CI? (joinfu's instructions don't seem to work, and manually running
> devstack-gate scripts fails:
>
> Running gate_hook
>
> Job timeout set to: 163 minutes
>
> timeout: failed to run command 
> ‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory
>
> ERROR: the main setup script run by this job failed - exit code: 127
>
> please look at the relevant log files to determine the root cause
>
> Cleaning up host
>
> ... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)
>
>  Build step 'Execute shell' marked build as failure.
>
>
>
> I have a working Jenkins slave with devstack and our internal libraries, i
> have Gerrit Trigger Plugin working and triggering on patches created, i
> just need the actual job contents so that it can get to comment with the
> test results.
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi Darragh, thanks for your input
>
>
>
> I double

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-18 Thread Asselin, Ramy

Yes, Ubuntu 12.04 is tested as mentioned in the readme [1]. Note that the 
referenced script is just a wrapper that pulls all the latest from various 
locations in openstack-infra, e.g. [2].
Ubuntu 14.04 support is WIP [3]
FYI, there’s a spec to get an in-tree 3rd party ci solution [4]. Please add 
your comments if this interests you.

[1] https://github.com/rasselin/os-ext-testing/blob/master/README.md
[2] 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L29
[3] https://review.openstack.org/#/c/141518/
[4] https://review.openstack.org/#/c/139745/


From: Punith S [mailto:punit...@cloudbyte.com]
Sent: Thursday, December 18, 2014 3:12 AM
To: OpenStack Development Mailing List (not for usage questions); Eduard Matei
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi Eduard

we tried running 
https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
on ubuntu master 12.04, and it appears to be working fine on 12.04.

thanks

On Thu, Dec 18, 2014 at 1:57 PM, Eduard Matei 
mailto:eduard.ma...@cloudfounders.com>> wrote:
Hi,
Seems i can't install using puppet on the jenkins master using 
install_master.sh from 
https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
 because it's running Ubuntu 11.10 and it appears unsupported.
I managed to install puppet manually on master and everything else fails
So i'm trying to manually install zuul and nodepool and jenkins job builder, 
see where i end up.

The slave looks complete, got some errors on running install_slave so i ran 
parts of the script manually, changing some params and it appears installed but 
no way to test it without the master.

Any ideas welcome.

Thanks,

Eduard

On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
Manually running the script requires a few environment settings. Take a look at 
the README here:
https://github.com/openstack-infra/devstack-gate

Regarding cinder, I’m using this repo to run our cinder jobs (fork from 
jaypipes).
https://github.com/rasselin/os-ext-testing

Note that this solution doesn’t use the Jenkins gerrit trigger pluggin, but 
zuul.

There’s a sample job for cinder here. It’s in Jenkins Job Builder format.
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample

You can ask more questions in IRC freenode #openstack-cinder. (irc# asselin)

Ramy

From: Eduard Matei 
[mailto:eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>]
Sent: Tuesday, December 16, 2014 12:41 AM
To: Bailey, Darragh
Cc: OpenStack Development Mailing List (not for usage questions); OpenStack
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi,

Can someone point me to some working documentation on how to setup third party 
CI? (joinfu's instructions don't seem to work, and manually running 
devstack-gate scripts fails:

Running gate_hook

Job timeout set to: 163 minutes

timeout: failed to run command 
‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory

ERROR: the main setup script run by this job failed - exit code: 127

please look at the relevant log files to determine the root cause

Cleaning up host

... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)
Build step 'Execute shell' marked build as failure.

I have a working Jenkins slave with devstack and our internal libraries, i have 
Gerrit Trigger Plugin working and triggering on patches created, i just need 
the actual job contents so that it can get to comment with the test results.

Thanks,

Eduard

On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei 
mailto:eduard.ma...@cloudfounders.com>> wrote:
Hi Darragh, thanks for your input

I double checked the job settings and fixed it:
- build triggers is set to Gerrit event
- Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger Plugin and 
tested separately)
- Trigger on: Patchset Created
- Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches: Type: 
Path, Pattern: ** (was Type Plain on both)
Now the job is triggered by commit on openstack-dev/sandbox :)

Regarding the Query and Trigger Gerrit Patches, i found my patch using query: 
status:open project:openstack-dev/sandbox change:139585 and i can trigger it 
manually and it executes the job.

But i still have the problem: what should the job do? It doesn't actually do 
anything, it doesn't run tests or comment on the patch.
Do you have an example of job?

Thanks,
Eduard

On Tue, Dec 9, 2014 at 1:13 PM, Bailey, Darragh 
mailto:dbai...@hp.com>> wrote:
Hi Eduard,


I would check the trigger settings in the job, particularly which "type"
of pattern matching is being used for the branches. Found it tends to be
the spot that catches most people out

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-18 Thread Punith S

Hi Eduard

we tried running
https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
on ubuntu master 12.04, and it appears to be working fine on 12.04.

thanks

On Thu, Dec 18, 2014 at 1:57 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:
>
> Hi,
> Seems i can't install using puppet on the jenkins master using
> install_master.sh from
> https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
> because it's running Ubuntu 11.10 and it appears unsupported.
> I managed to install puppet manually on master and everything else fails
> So i'm trying to manually install zuul and nodepool and jenkins job
> builder, see where i end up.
>
> The slave looks complete, got some errors on running install_slave so i
> ran parts of the script manually, changing some params and it appears
> installed but no way to test it without the master.
>
> Any ideas welcome.
>
> Thanks,
>
> Eduard
>
> On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy 
> wrote:
>
>>  Manually running the script requires a few environment settings. Take a
>> look at the README here:
>>
>> https://github.com/openstack-infra/devstack-gate
>>
>>
>>
>> Regarding cinder, I’m using this repo to run our cinder jobs (fork from
>> jaypipes).
>>
>> https://github.com/rasselin/os-ext-testing
>>
>>
>>
>> Note that this solution doesn’t use the Jenkins gerrit trigger pluggin,
>> but zuul.
>>
>>
>>
>> There’s a sample job for cinder here. It’s in Jenkins Job Builder format.
>>
>>
>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample
>>
>>
>>
>> You can ask more questions in IRC freenode #openstack-cinder. (irc#
>> asselin)
>>
>>
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Tuesday, December 16, 2014 12:41 AM
>> *To:* Bailey, Darragh
>> *Cc:* OpenStack Development Mailing List (not for usage questions);
>> OpenStack
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi,
>>
>>
>>
>> Can someone point me to some working documentation on how to setup third
>> party CI? (joinfu's instructions don't seem to work, and manually running
>> devstack-gate scripts fails:
>>
>> Running gate_hook
>>
>> Job timeout set to: 163 minutes
>>
>> timeout: failed to run command 
>> ‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory
>>
>> ERROR: the main setup script run by this job failed - exit code: 127
>>
>> please look at the relevant log files to determine the root cause
>>
>> Cleaning up host
>>
>> ... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)
>>
>>  Build step 'Execute shell' marked build as failure.
>>
>>
>>
>> I have a working Jenkins slave with devstack and our internal libraries,
>> i have Gerrit Trigger Plugin working and triggering on patches created, i
>> just need the actual job contents so that it can get to comment with the
>> test results.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Eduard
>>
>>
>>
>> On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>  Hi Darragh, thanks for your input
>>
>>
>>
>> I double checked the job settings and fixed it:
>>
>> - build triggers is set to Gerrit event
>>
>> - Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger
>> Plugin and tested separately)
>>
>> - Trigger on: Patchset Created
>>
>> - Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches:
>> Type: Path, Pattern: ** (was Type Plain on both)
>>
>> Now the job is triggered by commit on openstack-dev/sandbox :)
>>
>>
>>
>> Regarding the Query and Trigger Gerrit Patches, i found my patch using
>> query: status:open project:openstack-dev/sandbox change:139585 and i can
>> trigger it manually and it executes the job.
>>
>>
>>
>> But i still have the problem: what should the job do? It doesn't actually
>> do anything, it doesn't run tests or comment on the patch.
>>
>> Do you have an example of job?
>>
>>
>>
>> Thanks,
>>
>> Eduard
>>
>&g

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-18 Thread Eduard Matei

Hi,
Seems i can't install using puppet on the jenkins master using
install_master.sh from
https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
because it's running Ubuntu 11.10 and it appears unsupported.
I managed to install puppet manually on master and everything else fails
So i'm trying to manually install zuul and nodepool and jenkins job
builder, see where i end up.

The slave looks complete, got some errors on running install_slave so i ran
parts of the script manually, changing some params and it appears installed
but no way to test it without the master.

Any ideas welcome.

Thanks,

Eduard

On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy  wrote:

>  Manually running the script requires a few environment settings. Take a
> look at the README here:
>
> https://github.com/openstack-infra/devstack-gate
>
>
>
> Regarding cinder, I’m using this repo to run our cinder jobs (fork from
> jaypipes).
>
> https://github.com/rasselin/os-ext-testing
>
>
>
> Note that this solution doesn’t use the Jenkins gerrit trigger pluggin,
> but zuul.
>
>
>
> There’s a sample job for cinder here. It’s in Jenkins Job Builder format.
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample
>
>
>
> You can ask more questions in IRC freenode #openstack-cinder. (irc#
> asselin)
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Tuesday, December 16, 2014 12:41 AM
> *To:* Bailey, Darragh
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> OpenStack
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi,
>
>
>
> Can someone point me to some working documentation on how to setup third
> party CI? (joinfu's instructions don't seem to work, and manually running
> devstack-gate scripts fails:
>
> Running gate_hook
>
> Job timeout set to: 163 minutes
>
> timeout: failed to run command 
> ‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory
>
> ERROR: the main setup script run by this job failed - exit code: 127
>
> please look at the relevant log files to determine the root cause
>
> Cleaning up host
>
> ... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)
>
>  Build step 'Execute shell' marked build as failure.
>
>
>
> I have a working Jenkins slave with devstack and our internal libraries, i
> have Gerrit Trigger Plugin working and triggering on patches created, i
> just need the actual job contents so that it can get to comment with the
> test results.
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi Darragh, thanks for your input
>
>
>
> I double checked the job settings and fixed it:
>
> - build triggers is set to Gerrit event
>
> - Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger Plugin
> and tested separately)
>
> - Trigger on: Patchset Created
>
> - Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches:
> Type: Path, Pattern: ** (was Type Plain on both)
>
> Now the job is triggered by commit on openstack-dev/sandbox :)
>
>
>
> Regarding the Query and Trigger Gerrit Patches, i found my patch using
> query: status:open project:openstack-dev/sandbox change:139585 and i can
> trigger it manually and it executes the job.
>
>
>
> But i still have the problem: what should the job do? It doesn't actually
> do anything, it doesn't run tests or comment on the patch.
>
> Do you have an example of job?
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Tue, Dec 9, 2014 at 1:13 PM, Bailey, Darragh  wrote:
>
> Hi Eduard,
>
>
> I would check the trigger settings in the job, particularly which "type"
> of pattern matching is being used for the branches. Found it tends to be
> the spot that catches most people out when configuring jobs with the
> Gerrit Trigger plugin. If you're looking to trigger against all branches
> then you would want "Type: Path" and "Pattern: **" appearing in the UI.
>
> If you have sufficient access using the 'Query and Trigger Gerrit
> Patches' page accessible from the main view will make it easier to
> confirm that your Jenkins instance can actually see changes in gerrit
> for the given project (which should mean that it can see the
> corresponding events as well). Can also use the same page to re-trigger
> for Patchse

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-17 Thread Eduard Matei

Thanks, i'll have a look.

Eduard

On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy  wrote:

>  Manually running the script requires a few environment settings. Take a
> look at the README here:
>
> https://github.com/openstack-infra/devstack-gate
>
>
>
> Regarding cinder, I’m using this repo to run our cinder jobs (fork from
> jaypipes).
>
> https://github.com/rasselin/os-ext-testing
>
>
>
> Note that this solution doesn’t use the Jenkins gerrit trigger pluggin,
> but zuul.
>
>
>
> There’s a sample job for cinder here. It’s in Jenkins Job Builder format.
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample
>
>
>
> You can ask more questions in IRC freenode #openstack-cinder. (irc#
> asselin)
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Tuesday, December 16, 2014 12:41 AM
> *To:* Bailey, Darragh
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> OpenStack
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi,
>
>
>
> Can someone point me to some working documentation on how to setup third
> party CI? (joinfu's instructions don't seem to work, and manually running
> devstack-gate scripts fails:
>
> Running gate_hook
>
> Job timeout set to: 163 minutes
>
> timeout: failed to run command 
> ‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory
>
> ERROR: the main setup script run by this job failed - exit code: 127
>
> please look at the relevant log files to determine the root cause
>
> Cleaning up host
>
> ... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)
>
>  Build step 'Execute shell' marked build as failure.
>
>
>
> I have a working Jenkins slave with devstack and our internal libraries, i
> have Gerrit Trigger Plugin working and triggering on patches created, i
> just need the actual job contents so that it can get to comment with the
> test results.
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi Darragh, thanks for your input
>
>
>
> I double checked the job settings and fixed it:
>
> - build triggers is set to Gerrit event
>
> - Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger Plugin
> and tested separately)
>
> - Trigger on: Patchset Created
>
> - Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches:
> Type: Path, Pattern: ** (was Type Plain on both)
>
> Now the job is triggered by commit on openstack-dev/sandbox :)
>
>
>
> Regarding the Query and Trigger Gerrit Patches, i found my patch using
> query: status:open project:openstack-dev/sandbox change:139585 and i can
> trigger it manually and it executes the job.
>
>
>
> But i still have the problem: what should the job do? It doesn't actually
> do anything, it doesn't run tests or comment on the patch.
>
> Do you have an example of job?
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Tue, Dec 9, 2014 at 1:13 PM, Bailey, Darragh  wrote:
>
> Hi Eduard,
>
>
> I would check the trigger settings in the job, particularly which "type"
> of pattern matching is being used for the branches. Found it tends to be
> the spot that catches most people out when configuring jobs with the
> Gerrit Trigger plugin. If you're looking to trigger against all branches
> then you would want "Type: Path" and "Pattern: **" appearing in the UI.
>
> If you have sufficient access using the 'Query and Trigger Gerrit
> Patches' page accessible from the main view will make it easier to
> confirm that your Jenkins instance can actually see changes in gerrit
> for the given project (which should mean that it can see the
> corresponding events as well). Can also use the same page to re-trigger
> for PatchsetCreated events to see if you've set the patterns on the job
> correctly.
>
> Regards,
> Darragh Bailey
>
> "Nothing is foolproof to a sufficiently talented fool" - Unknown
>
> On 08/12/14 14:33, Eduard Matei wrote:
> > Resending this to dev ML as it seems i get quicker response :)
> >
> > I created a job in Jenkins, added as Build Trigger: "Gerrit Event:
> > Patchset Created", chose as server the configured Gerrit server that
> > was previously tested, then added the project openstack-dev/sandbox
> > and saved.
> >

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-16 Thread Asselin, Ramy

Manually running the script requires a few environment settings. Take a look at 
the README here:
https://github.com/openstack-infra/devstack-gate

Regarding cinder, I’m using this repo to run our cinder jobs (fork from 
jaypipes).
https://github.com/rasselin/os-ext-testing

Note that this solution doesn’t use the Jenkins gerrit trigger pluggin, but 
zuul.

There’s a sample job for cinder here. It’s in Jenkins Job Builder format.
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample

You can ask more questions in IRC freenode #openstack-cinder. (irc# asselin)

Ramy

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Tuesday, December 16, 2014 12:41 AM
To: Bailey, Darragh
Cc: OpenStack Development Mailing List (not for usage questions); OpenStack
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting 
up CI

Hi,

Can someone point me to some working documentation on how to setup third party 
CI? (joinfu's instructions don't seem to work, and manually running 
devstack-gate scripts fails:

Running gate_hook

Job timeout set to: 163 minutes

timeout: failed to run command 
‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory

ERROR: the main setup script run by this job failed - exit code: 127

please look at the relevant log files to determine the root cause

Cleaning up host

... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)
Build step 'Execute shell' marked build as failure.

I have a working Jenkins slave with devstack and our internal libraries, i have 
Gerrit Trigger Plugin working and triggering on patches created, i just need 
the actual job contents so that it can get to comment with the test results.

Thanks,

Eduard

On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei 
mailto:eduard.ma...@cloudfounders.com>> wrote:
Hi Darragh, thanks for your input

I double checked the job settings and fixed it:
- build triggers is set to Gerrit event
- Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger Plugin and 
tested separately)
- Trigger on: Patchset Created
- Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches: Type: 
Path, Pattern: ** (was Type Plain on both)
Now the job is triggered by commit on openstack-dev/sandbox :)

Regarding the Query and Trigger Gerrit Patches, i found my patch using query: 
status:open project:openstack-dev/sandbox change:139585 and i can trigger it 
manually and it executes the job.

But i still have the problem: what should the job do? It doesn't actually do 
anything, it doesn't run tests or comment on the patch.
Do you have an example of job?

Thanks,
Eduard

On Tue, Dec 9, 2014 at 1:13 PM, Bailey, Darragh 
mailto:dbai...@hp.com>> wrote:
Hi Eduard,

I would check the trigger settings in the job, particularly which "type"
of pattern matching is being used for the branches. Found it tends to be
the spot that catches most people out when configuring jobs with the
Gerrit Trigger plugin. If you're looking to trigger against all branches
then you would want "Type: Path" and "Pattern: **" appearing in the UI.

If you have sufficient access using the 'Query and Trigger Gerrit
Patches' page accessible from the main view will make it easier to
confirm that your Jenkins instance can actually see changes in gerrit
for the given project (which should mean that it can see the
corresponding events as well). Can also use the same page to re-trigger
for PatchsetCreated events to see if you've set the patterns on the job
correctly.

Regards,
Darragh Bailey

"Nothing is foolproof to a sufficiently talented fool" - Unknown

On 08/12/14 14:33, Eduard Matei wrote:
> Resending this to dev ML as it seems i get quicker response :)
>
> I created a job in Jenkins, added as Build Trigger: "Gerrit Event:
> Patchset Created", chose as server the configured Gerrit server that
> was previously tested, then added the project openstack-dev/sandbox
> and saved.
> I made a change on dev sandbox repo but couldn't trigger my job.
>
> Any ideas?
>
> Thanks,
> Eduard
>
> On Fri, Dec 5, 2014 at 10:32 AM, Eduard Matei
> mailto:eduard.ma...@cloudfounders.com>
> <mailto:eduard.ma...@cloudfounders.com<mailto:eduard.ma...@cloudfounders.com>>>
>  wrote:
>
> Hello everyone,
>
> Thanks to the latest changes to the creation of service accounts
> process we're one step closer to setting up our own CI platform
> for Cinder.
>
> So far we've got:
> - Jenkins master (with Gerrit plugin) and slave (with DevStack and
> our storage solution)
> - Service account configured and tested (can manually connect to
> review.openstack.org<http://review.openstack.org> 
> <htt

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-16 Thread Eduard Matei

Hi,

Can someone point me to some working documentation on how to setup third
party CI? (joinfu's instructions don't seem to work, and manually running
devstack-gate scripts fails:

Running gate_hook
Job timeout set to: 163 minutes
timeout: failed to run command
‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or
directory
ERROR: the main setup script run by this job failed - exit code: 127
please look at the relevant log files to determine the root cause
Cleaning up host
... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)

Build step 'Execute shell' marked build as failure.

I have a working Jenkins slave with devstack and our internal libraries, i
have Gerrit Trigger Plugin working and triggering on patches created, i
just need the actual job contents so that it can get to comment with the
test results.

Thanks,

Eduard

On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei  wrote:

> Hi Darragh, thanks for your input
>
> I double checked the job settings and fixed it:
> - build triggers is set to Gerrit event
> - Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger Plugin
> and tested separately)
> - Trigger on: Patchset Created
> - Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches:
> Type: Path, Pattern: ** (was Type Plain on both)
> Now the job is triggered by commit on openstack-dev/sandbox :)
>
> Regarding the Query and Trigger Gerrit Patches, i found my patch using
> query: status:open project:openstack-dev/sandbox change:139585 and i can
> trigger it manually and it executes the job.
>
> But i still have the problem: what should the job do? It doesn't actually
> do anything, it doesn't run tests or comment on the patch.
> Do you have an example of job?
>
> Thanks,
> Eduard
>
> On Tue, Dec 9, 2014 at 1:13 PM, Bailey, Darragh  wrote:
>
>> Hi Eduard,
>>
>>
>> I would check the trigger settings in the job, particularly which "type"
>> of pattern matching is being used for the branches. Found it tends to be
>> the spot that catches most people out when configuring jobs with the
>> Gerrit Trigger plugin. If you're looking to trigger against all branches
>> then you would want "Type: Path" and "Pattern: **" appearing in the UI.
>>
>> If you have sufficient access using the 'Query and Trigger Gerrit
>> Patches' page accessible from the main view will make it easier to
>> confirm that your Jenkins instance can actually see changes in gerrit
>> for the given project (which should mean that it can see the
>> corresponding events as well). Can also use the same page to re-trigger
>> for PatchsetCreated events to see if you've set the patterns on the job
>> correctly.
>>
>> Regards,
>> Darragh Bailey
>>
>> "Nothing is foolproof to a sufficiently talented fool" - Unknown
>>
>> On 08/12/14 14:33, Eduard Matei wrote:
>> > Resending this to dev ML as it seems i get quicker response :)
>> >
>> > I created a job in Jenkins, added as Build Trigger: "Gerrit Event:
>> > Patchset Created", chose as server the configured Gerrit server that
>> > was previously tested, then added the project openstack-dev/sandbox
>> > and saved.
>> > I made a change on dev sandbox repo but couldn't trigger my job.
>> >
>> > Any ideas?
>> >
>> > Thanks,
>> > Eduard
>> >
>> > On Fri, Dec 5, 2014 at 10:32 AM, Eduard Matei
>> > > > > wrote:
>> >
>> > Hello everyone,
>> >
>> > Thanks to the latest changes to the creation of service accounts
>> > process we're one step closer to setting up our own CI platform
>> > for Cinder.
>> >
>> > So far we've got:
>> > - Jenkins master (with Gerrit plugin) and slave (with DevStack and
>> > our storage solution)
>> > - Service account configured and tested (can manually connect to
>> > review.openstack.org  and get events
>> > and publish comments)
>> >
>> > Next step would be to set up a job to do the actual testing, this
>> > is where we're stuck.
>> > Can someone please point us to a clear example on how a job should
>> > look like (preferably for testing Cinder on Kilo)? Most links
>> > we've found are broken, or tools/scripts are no longer working.
>> > Also, we cannot change the Jenkins master too much (it's owned by
>> > Ops team and they need a list of tools/scripts to review before
>> > installing/running so we're not allowed to experiment).
>> >
>> > Thanks,
>> > Eduard
>> >
>> > --
>> >
>> > *Eduard Biceri Matei, Senior Software Developer*
>> > www.cloudfounders.com
>> >  | eduard.ma...@cloudfounders.com
>> > 
>> >
>> >
>> >
>> > *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 no

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-09 Thread Eduard Matei

Hi Darragh, thanks for your input

I double checked the job settings and fixed it:
- build triggers is set to Gerrit event
- Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger Plugin
and tested separately)
- Trigger on: Patchset Created
- Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches:
Type: Path, Pattern: ** (was Type Plain on both)
Now the job is triggered by commit on openstack-dev/sandbox :)

Regarding the Query and Trigger Gerrit Patches, i found my patch using
query: status:open project:openstack-dev/sandbox change:139585 and i can
trigger it manually and it executes the job.

But i still have the problem: what should the job do? It doesn't actually
do anything, it doesn't run tests or comment on the patch.
Do you have an example of job?

Thanks,
Eduard

On Tue, Dec 9, 2014 at 1:13 PM, Bailey, Darragh  wrote:

> Hi Eduard,
>
>
> I would check the trigger settings in the job, particularly which "type"
> of pattern matching is being used for the branches. Found it tends to be
> the spot that catches most people out when configuring jobs with the
> Gerrit Trigger plugin. If you're looking to trigger against all branches
> then you would want "Type: Path" and "Pattern: **" appearing in the UI.
>
> If you have sufficient access using the 'Query and Trigger Gerrit
> Patches' page accessible from the main view will make it easier to
> confirm that your Jenkins instance can actually see changes in gerrit
> for the given project (which should mean that it can see the
> corresponding events as well). Can also use the same page to re-trigger
> for PatchsetCreated events to see if you've set the patterns on the job
> correctly.
>
> Regards,
> Darragh Bailey
>
> "Nothing is foolproof to a sufficiently talented fool" - Unknown
>
> On 08/12/14 14:33, Eduard Matei wrote:
> > Resending this to dev ML as it seems i get quicker response :)
> >
> > I created a job in Jenkins, added as Build Trigger: "Gerrit Event:
> > Patchset Created", chose as server the configured Gerrit server that
> > was previously tested, then added the project openstack-dev/sandbox
> > and saved.
> > I made a change on dev sandbox repo but couldn't trigger my job.
> >
> > Any ideas?
> >
> > Thanks,
> > Eduard
> >
> > On Fri, Dec 5, 2014 at 10:32 AM, Eduard Matei
> >  > > wrote:
> >
> > Hello everyone,
> >
> > Thanks to the latest changes to the creation of service accounts
> > process we're one step closer to setting up our own CI platform
> > for Cinder.
> >
> > So far we've got:
> > - Jenkins master (with Gerrit plugin) and slave (with DevStack and
> > our storage solution)
> > - Service account configured and tested (can manually connect to
> > review.openstack.org  and get events
> > and publish comments)
> >
> > Next step would be to set up a job to do the actual testing, this
> > is where we're stuck.
> > Can someone please point us to a clear example on how a job should
> > look like (preferably for testing Cinder on Kilo)? Most links
> > we've found are broken, or tools/scripts are no longer working.
> > Also, we cannot change the Jenkins master too much (it's owned by
> > Ops team and they need a list of tools/scripts to review before
> > installing/running so we're not allowed to experiment).
> >
> > Thanks,
> > Eduard
> >
> > --
> >
> > *Eduard Biceri Matei, Senior Software Developer*
> > www.cloudfounders.com
> >  | eduard.ma...@cloudfounders.com
> > 
> >
> >
> >
> > *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

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

2014-12-09 Thread Bailey, Darragh

Hi Eduard,


I would check the trigger settings in the job, particularly which "type"
of pattern matching is being used for the branches. Found it tends to be
the spot that catches most people out when configuring jobs with the
Gerrit Trigger plugin. If you're looking to trigger against all branches
then you would want "Type: Path" and "Pattern: **" appearing in the UI.

If you have sufficient access using the 'Query and Trigger Gerrit
Patches' page accessible from the main view will make it easier to
confirm that your Jenkins instance can actually see changes in gerrit
for the given project (which should mean that it can see the
corresponding events as well). Can also use the same page to re-trigger
for PatchsetCreated events to see if you've set the patterns on the job
correctly.

Regards,
Darragh Bailey

"Nothing is foolproof to a sufficiently talented fool" - Unknown

On 08/12/14 14:33, Eduard Matei wrote:
> Resending this to dev ML as it seems i get quicker response :)
>
> I created a job in Jenkins, added as Build Trigger: "Gerrit Event:
> Patchset Created", chose as server the configured Gerrit server that
> was previously tested, then added the project openstack-dev/sandbox
> and saved.
> I made a change on dev sandbox repo but couldn't trigger my job.
>
> Any ideas?
>
> Thanks,
> Eduard
>
> On Fri, Dec 5, 2014 at 10:32 AM, Eduard Matei
>  > wrote:
>
> Hello everyone,
>
> Thanks to the latest changes to the creation of service accounts
> process we're one step closer to setting up our own CI platform
> for Cinder.
>
> So far we've got:
> - Jenkins master (with Gerrit plugin) and slave (with DevStack and
> our storage solution)
> - Service account configured and tested (can manually connect to
> review.openstack.org  and get events
> and publish comments)
>
> Next step would be to set up a job to do the actual testing, this
> is where we're stuck.
> Can someone please point us to a clear example on how a job should
> look like (preferably for testing Cinder on Kilo)? Most links
> we've found are broken, or tools/scripts are no longer working.
> Also, we cannot change the Jenkins master too much (it's owned by
> Ops team and they need a list of tools/scripts to review before
> installing/running so we're not allowed to experiment).
>
> Thanks,
> Eduard
>
> -- 
>
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.ma...@cloudfounders.com
> 
>  
>
>  
> *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.
>
>
>
>
> -- 
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.ma...@cloudfounders.com
> 
>  
>
>  
> *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
> informa

Re: [openstack-dev] [OpenStack-Infra][ThirdPartyCI] Need help setting up CI

2014-12-08 Thread Eduard Matei

Resending this to dev ML as it seems i get quicker response :)

I created a job in Jenkins, added as Build Trigger: "Gerrit Event: Patchset
Created", chose as server the configured Gerrit server that was previously
tested, then added the project openstack-dev/sandbox and saved.
I made a change on dev sandbox repo but couldn't trigger my job.

Any ideas?

Thanks,
Eduard

On Fri, Dec 5, 2014 at 10:32 AM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hello everyone,
>
> Thanks to the latest changes to the creation of service accounts process
> we're one step closer to setting up our own CI platform for Cinder.
>
> So far we've got:
> - Jenkins master (with Gerrit plugin) and slave (with DevStack and our
> storage solution)
> - Service account configured and tested (can manually connect to
> review.openstack.org and get events and publish comments)
>
> Next step would be to set up a job to do the actual testing, this is where
> we're stuck.
> Can someone please point us to a clear example on how a job should look
> like (preferably for testing Cinder on Kilo)? Most links we've found are
> broken, or tools/scripts are no longer working.
> Also, we cannot change the Jenkins master too much (it's owned by Ops team
> and they need a list of tools/scripts to review before installing/running
> so we're not allowed to experiment).
>
> Thanks,
> Eduard
>
> --
>
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.ma...@cloudfounders.com
>
>
>
> *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.
>
>

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com

*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-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

44 matches

Mail list logo