Re: [openstack-dev] [all] Useful tool for easier viewing of IRC logs online

2016-09-19 Thread Asselin, Ramy
Very nice, thanks!
Only change I'll suggest is to allow it to be enabled by default :)
Ramy

From: Bashmakov, Alexander [mailto:alexander.bashma...@intel.com]
Sent: Friday, September 16, 2016 2:26 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] [all] Useful tool for easier viewing of IRC logs online

Hello Stackers,

If you ever find yourself needing to peruse OpenStack IRC logs online 
(http://eavesdrop.openstack.org/irclogs/) and if you use the Chrome browser to 
do it, then the following tool may come in handy:

https://chrome.google.com/webstore/detail/openstack-eavesdrop-irc-f/lcmadadicbflcamibnpplpgdcdahkade

It's a simple extension to filter messages of the type: " has quit" and 
" has joined", which makes the log much more compact and readable.

Source code is here: https://github.com/abashmak/chrome-irc-filter

Comments, suggestions are welcome.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [third-party] [puppet] [infra] puppet-jenkins doesn't allow to pin version

2016-09-07 Thread Asselin, Ramy
Adding [infra]. 

Simon proposed a patch to make it work.
https://review.openstack.org/#/c/366803/1

-Original Message-
From: Evgeny Antyshev [mailto:eantys...@virtuozzo.com] 
Sent: Tuesday, September 06, 2016 2:22 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] [third-party] [puppet] puppet-jenkins doesn't allow to 
pin version

Hello!

Last time I created Third-Party CI in new environment, I faced difficulties 
installing Jenkins by puppet-jenkins:

1) It really doesn't allow to pin Jenkins version, due to bug (or lack of 
functionality) in Jenkins infrastructure:
https://issues.jenkins-ci.org/browse/INFRA-92

Therefore, the change at https://review.openstack.org/354086 don't actually 
work.

There are 2 options to workaround this: install Jenkins package from *.deb by 
given link, which involves some possible issues with dependancies. Or to make 
it without Jenkins, using Zuul launcher in 3rd-party environment, has anybody 
tried that?

2) 3rd-party CI also needs https://review.openstack.org/334400 (to disable 
security policy preventing custom build parameters). But this solution won't be 
accepted, and there's no other yet.

Does anyone have opinion on this?

Thanks in advance!

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [third-party] [ci] Please PIN your 3rd party ci setup to zuul v. 2.5.0

2016-08-09 Thread Asselin, Ramy
All,

In the previous e-mail, [1] was recommending 3rd party ci to pin zuul to v. 
2.1.0, but this has pip dependency conflicts with nodepool 0.3.0 when installed 
on the same VM (common case typical for 3rd party ci) causing zuul service to 
fail to start.
This is fixed by using the newly created zuul v. 2.5.0 tag [2], which has 
compatible pip dependencies along with many bug fixes.

It is strongly recommended to apply this pins to your setup and NOT use master 
branch in order to keep you CI systems stable. The full set of recommended pins 
is being maintained in this file [3].

Ramy

[1] https://review.openstack.org/#/c/348035/4/contrib/single_node_ci_data.yaml
[2] https://review.openstack.org/#/c/352560/1/contrib/single_node_ci_data.yaml
[3] 
http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/single_node_ci_data.yaml

-Original Message-
From: Asselin, Ramy 
Sent: Friday, August 05, 2016 11:29 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [third-party] [ci] Please PIN your 3rd party ci setup 
to JJB 1.6.1

All,

In case you're still using JJB master branch, it is highly recommended that you 
pin to 1.6.1. There are recent/upcoming changes that could break your CI setup.

You can do this by updating your puppet hiera file 
(/etc/puppet/environments/common.yaml [1]) as shown here [2][3]

Re-run puppet (sudo puppet apply --verbose /etc/puppet/manifests/site.pp [1]) 
and that will ensure your JJB & zuul installations are pinned to stable 
versions.

Ramy 

[1] http://docs.openstack.org/infra/openstackci/third_party_ci.html
[2] diff: 
https://review.openstack.org/#/c/348035/4/contrib/single_node_ci_data.yaml
[3] full: 
http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/single_node_ci_data.yaml

-Original Message-----
From: Asselin, Ramy 
Sent: Friday, July 08, 2016 7:30 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [third-party] [ci] Upcoming changes to Nodepool for 
Zuul v3

All,

If you haven't already, it's recommended to pin nodepool to the 0.3.0 tag and 
not use master.
If you're using the puppet-openstackci solution, you can update your puppet 
hiera file as shown here: https://review.openstack.org/293112
Re-run puppet and restart nodepool.

Ramy 

-Original Message-
From: Monty Taylor [mailto:mord...@inaugust.com] 
Sent: Thursday, July 07, 2016 6:21 PM
To: openstack-in...@lists.openstack.org
Subject: [OpenStack-Infra] Upcoming changes to Nodepool for Zuul v3

Hey all!

tl;dr - nodepool 0.3.0 tagged, you should pin

Longer version:

As you are probably aware, we've been working towards Zuul v3 for a while. 
Hopefully you're as excited about that as we are.

We're about to start working in earnest on changes to nodepool in support of 
that. One of our goals with Zuul v3 is to make nodepool supportable in a CD 
manner for people who are not us. In support of that, we may break a few things 
over the next month or two.

So that it's not a steady stream of things you should pay attention to - we've 
cut a tag:

0.3.0

of what's running in production right now. If your tolerance for potentially 
breaking change is low, we strongly recommend pinning your install to it.

We will still be running CD from master the whole time - but we are also paying 
constant attention when we're landing things.

Once this next iteration is ready, we'll send out another announcement that 
master is in shape for consuming CD-style.

Thanks!
Monty

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

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [third-party] [ci] Please PIN your 3rd party ci setup to JJB 1.6.1

2016-08-05 Thread Asselin, Ramy
All,

In case you're still using JJB master branch, it is highly recommended that you 
pin to 1.6.1. There are recent/upcoming changes that could break your CI setup.

You can do this by updating your puppet hiera file 
(/etc/puppet/environments/common.yaml [1]) as shown here [2][3]

Re-run puppet (sudo puppet apply --verbose /etc/puppet/manifests/site.pp [1]) 
and that will ensure your JJB & zuul installations are pinned to stable 
versions.

Ramy 

[1] http://docs.openstack.org/infra/openstackci/third_party_ci.html
[2] diff: 
https://review.openstack.org/#/c/348035/4/contrib/single_node_ci_data.yaml
[3] full: 
http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/single_node_ci_data.yaml

-Original Message-
From: Asselin, Ramy 
Sent: Friday, July 08, 2016 7:30 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [third-party] [ci] Upcoming changes to Nodepool for 
Zuul v3

All,

If you haven't already, it's recommended to pin nodepool to the 0.3.0 tag and 
not use master.
If you're using the puppet-openstackci solution, you can update your puppet 
hiera file as shown here: https://review.openstack.org/293112
Re-run puppet and restart nodepool.

Ramy 

-Original Message-
From: Monty Taylor [mailto:mord...@inaugust.com] 
Sent: Thursday, July 07, 2016 6:21 PM
To: openstack-in...@lists.openstack.org
Subject: [OpenStack-Infra] Upcoming changes to Nodepool for Zuul v3

Hey all!

tl;dr - nodepool 0.3.0 tagged, you should pin

Longer version:

As you are probably aware, we've been working towards Zuul v3 for a while. 
Hopefully you're as excited about that as we are.

We're about to start working in earnest on changes to nodepool in support of 
that. One of our goals with Zuul v3 is to make nodepool supportable in a CD 
manner for people who are not us. In support of that, we may break a few things 
over the next month or two.

So that it's not a steady stream of things you should pay attention to - we've 
cut a tag:

0.3.0

of what's running in production right now. If your tolerance for potentially 
breaking change is low, we strongly recommend pinning your install to it.

We will still be running CD from master the whole time - but we are also paying 
constant attention when we're landing things.

Once this next iteration is ready, we'll send out another announcement that 
master is in shape for consuming CD-style.

Thanks!
Monty

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

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [third-party] [ci] Upcoming changes to Nodepool for Zuul v3

2016-07-08 Thread Asselin, Ramy
All,

If you haven't already, it's recommended to pin nodepool to the 0.3.0 tag and 
not use master.
If you're using the puppet-openstackci solution, you can update your puppet 
hiera file as shown here: https://review.openstack.org/293112
Re-run puppet and restart nodepool.

Ramy 

-Original Message-
From: Monty Taylor [mailto:mord...@inaugust.com] 
Sent: Thursday, July 07, 2016 6:21 PM
To: openstack-in...@lists.openstack.org
Subject: [OpenStack-Infra] Upcoming changes to Nodepool for Zuul v3

Hey all!

tl;dr - nodepool 0.3.0 tagged, you should pin

Longer version:

As you are probably aware, we've been working towards Zuul v3 for a while. 
Hopefully you're as excited about that as we are.

We're about to start working in earnest on changes to nodepool in support of 
that. One of our goals with Zuul v3 is to make nodepool supportable in a CD 
manner for people who are not us. In support of that, we may break a few things 
over the next month or two.

So that it's not a steady stream of things you should pay attention to - we've 
cut a tag:

0.3.0

of what's running in production right now. If your tolerance for potentially 
breaking change is low, we strongly recommend pinning your install to it.

We will still be running CD from master the whole time - but we are also paying 
constant attention when we're landing things.

Once this next iteration is ready, we'll send out another announcement that 
master is in shape for consuming CD-style.

Thanks!
Monty

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

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [openstack-infra][project-config] how project config is updated

2016-06-30 Thread Asselin, Ramy
Puppet would update the repo and trigger changes off of it.

Documented here: 
http://docs.openstack.org/infra/openstackci/third_party_ci.html#updating-your-masterless-puppet-hosts

Ramy

From: 王华 [mailto:wanghua.hum...@gmail.com]
Sent: Thursday, June 30, 2016 9:42 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] [openstack-infra][project-config] how project config 
is updated

Hi all,

After openstack-infra/project-config is updated, for example layout.yaml for 
zuul is changed, how the change is applied to the CI system? Is there a script 
to trigger this change? I don't find some scripts in the pipeline of 
project-config in the layout.yaml to do this work. Do anyone know how it works?

Best Regards,
Wanghua
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [fuel] github can't sync with git because of big uploading

2016-01-11 Thread Asselin, Ramy
I understand this is an issue, but I don’t see why syncing to github is needed 
so urgently? You can still keep working and accessing the repo by 
developers/tools using openstack’s git farm [1]

[1] http://git.openstack.org/cgit/openstack/fuel-plugin-onos/



From: wuwenbin [mailto:wuwenb...@huawei.com]
Sent: Monday, January 11, 2016 5:14 PM
To: Mateusz Matuszkowiak
Cc: openstack-dev@lists.openstack.org
Subject: [openstack-dev] 转发: [fuel] github can't sync with git because of big 
uploading

Hi:
   I have forward the email and can you help me see why no answers.
   Thanks.
Bests
Cathy

发件人: wuwenbin
发送时间: 2015年12月30日 10:35
收件人: 'openstack-dev@lists.openstack.org'
抄送: Jiangrui (Henry, R); Zhaokexue
主题: [fuel] github can't sync with git because of big uploading

Hi all:
 Repo of  has something wrong because of uploading big file. Though 
codes are reverted while history still contains the pack which results in big 
downloading and unsync with github.
 I really want to solve this problem and please forgive my own decision 
for a new commit of new onosfw because I don’t want this impacting the project. 
I have to admit that I am really bad at management of commit and merge. So I 
invite fuel ptl as the manager of new repo to avoid such things.
 Does anyone can help me solve this as soon as possible?
   Thanks
Bests
Cathy

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [third-party] next 3rd party ci working group meeting is 1/12/16 1700 UTC

2016-01-04 Thread Asselin, Ramy
The 3rd party ci working group meeting is on even week Tuesday[1], which means 
the next meeting is next week, and not tomorrow.
The ical definitions are a bit off as referenced below.

Thanks,
Ramy

[1] http://eavesdrop.openstack.org/#Third_Party_Working_Group_Meeting


-Original Message-
From: Thierry Carrez [mailto:thie...@openstack.org] 
Sent: Monday, January 04, 2016 2:00 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] IRC meetings warning: two "odd" weeks coming 
up

Thierry Carrez wrote:
> Bi-weekly meetings are going to be affected by the new year, as two 
> odd ISO week numbers are following each other.
>
> Week 52: Dec 21 - Jan 27
> Week 53: Dec 28 - Jan 3
> Week 1:  Jan 4 - Jan 10
>
> https://en.wikipedia.org/wiki/ISO_week_date
>
> That means on the week of Jan 4th we'll hold "biweekly-odd" meetings, 
> and not "biweekly-even" meetings.
>
> Unfortunately, to add to the confusion, the subtlety of two odd weeks 
> following each other is lost to yaml2ical: it just generates an iCal 
> that puts biweekly meetings every two weeks starting from the 
> generation date. This bug will cause the generated iCal to be off 
> (showing biweekly-odd meetings on that week) until it's regenerated on week 1.

The ICS on eavesdrop.openstack.org was just regenerated, so meetings for this 
week should now appear correctly.

Cheers and happy new year !

--
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [ThirdParty][CI] [patch] Status page at http://ci-watch.tintri.com/project

2015-12-21 Thread Asselin, Ramy
Hi Phillip,

Yes, please offer a patch to that repo Anita suggested. There's a small group 
of us actively working on improving the code and eventually getting ci-watch 
deployed in openstack.org. Your patch and help would be very much appreciated.

We also meet bi-weekly in the 3rd party ci working group: 
https://wiki.openstack.org/wiki/Meetings/ThirdParty
We also discuss some issues in #openstack-third-party-ci

Thanks!
Ramy

-Original Message-
From: Anita Kuno [mailto:ante...@anteaya.info] 
Sent: Monday, December 21, 2015 6:52 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [ThirdParty][CI] [patch] Status page at 
http://ci-watch.tintri.com/project

On 12/21/2015 09:20 AM, Philipp Marek wrote:
> Hi all,
> 
> I quite like the page at http://ci-watch.tintri.com/project - it gives 
> a very quick overview about the failures one should look into, and 
> which to ignore ;)
> 
> 
> Please let me state before anything else that I don't know any of the 
> restrictions that may have led into the current design - it's very 
> likely that I'm just missing a few points, and that some or all of my 
> comments below are invalid anyway. As always, take enough salt!
> 
> 
> One thing about that page that is bothering me is the performance... 
> my
> (current) Firefox asks me several times whether I'd like to stop the 
> JS, or whether it should be allowed to continue.
> 
> With this patch (and a local exported copy of the page) I don't get 
> asked about that any more; it seems to give me a speedup of ~200, as 
> no intermediate lists need to be built and filtered any more:
> 
> $ diff -u verified.js.orig verified.js
> --- verified.js.orig2015-12-21 15:03:45.614529924 +0100
> +++ verified.js 2015-12-21 15:03:36.114432601 +0100
> @@ -33,9 +33,9 @@
>  $(document).ready(function () {
>$("colgroup").each(function (i, elem) {
>  if ($(elem).hasClass("verified-1")) {
> -  $("#results").find("td").filter(":nth-child(" + (i + 1) + 
> ")").addClass("verified-1");
> +  $("#results td:nth-child(" + (i + 1) + 
> + ")").addClass("verified-1");
>  } else if ($(elem).hasClass("verified1")) {
> -  $("#results").find("td").filter(":nth-child(" + (i + 1) + 
> ")").addClass("verified1");
> +  $("#results td:nth-child(" + (i + 1) + 
> + ")").addClass("verified1");
>  }
>});
>$("#verified1-button").on("click", toggle_verified_plus);
> 
> 
> Furthermore, I'm wondering whether
> 
> 
> 
> 
> 
> 
> 
> couldn't be simplified to
> 
> 
> 
> 
> 
> 
> with the rest being done via CSS? Perhaps a  would be needed 
> within the  to get the vertical size right, but everything else 
> should be possible via CSS, I believe.
> 
> This change should reduce the size of the generated HTML big some 50% 
> or so, too.
> 
> 
> 
> Thanks for listening - if you disagree, please ignore and continue 
> working on something else ;)
> 
> 
> Regards,
> 
> Phil
> 
> 
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

The repo is here if you would like to offer your patch via Gerrit.
http://git.openstack.org/cgit/openstack-infra/ciwatch/

Thanks Philipp,
Anita.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [third-party][infra][CI] Common OpenStack 'Third-party' CI Solution - DONE!

2015-11-20 Thread Asselin, Ramy
All,

I’m happy to announce that there is now a working ‘Common’ OpenStack 
‘third-party’ CI Solution available! This is a 3rd party CI solution that uses 
the same tools and scripts as the upstream ‘Jenkins’ CI.

The last few pieces were particularly challenging.
Big thanks to Yolanda Robla for updating Nodepool  & nodepool puppet scripts so 
that is can be reusable by both 3rd party CI’s and upstream infrastructure!

The documentation for setting up a 3rd party ci system on 2 VMs (1 private that 
runs the CI jobs, and 1 public that hosts the log files) is now available here 
[1] or [2]

Big thanks again to everyone that helped submit patches and do the reviews!

A few people have already starting setting up this solution.

Best regards,

Ramy
IRC: asselin

[1] https://github.com/openstack-infra/puppet-openstackci/tree/master/contrib
[2] 
https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/README.md


From: Asselin, Ramy
Sent: Monday, July 20, 2015 3:39 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [third-party][infra] Common OpenStack CI Solution 
- 'Jenkins Job Builder' live

All,

I’m pleased to announce the 4th component merged to puppet-openstackci repo [1].

This means 3rd party ci operators can now use the same scripts that the 
OpenStack Infrastructure team uses in the official ‘Jenkins’ CI system for:


1.   Log Server

2.   Jenkins

3.   Zuul

4.   Jenkins Job Builder

This work is being done as part of the common-ci spec [2]

Big thanks to Juame Devesa for starting the work, Khai Do for fixing all issues 
found in the reviews during the virtual sprint, and to all the reviewers and 
testers.

We’re almost there! Just have nodepool and a sample config to compose all of 
the components together [3]!

Ramy
IRC: asselin

[1] https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101


From: Asselin, Ramy
Sent: Thursday, July 02, 2015 4:59 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [third-party][infra] Common OpenStack CI Solution - 
'Zuul' live

All,

I’m please to say that there are now 3 components merged in the 
puppet-openstackci repo [1]
This means 3rd party ci operators can now use the same scripts that the 
OpenStack Infrastructure team uses in the official ‘Jenkins’ CI system for:


1.   Log Server

2.   Jenkins

3.   Zuul

This work is being done as part of the common-ci spec [2]

Big thanks to Fabien Boucher for completing the Zuul script refactoring, which 
went live today!
Thanks to all the reviewers for careful reviews which led to a smooth migration.

I’ve updated my repo [3] & switched all my CI systems to use it.

As a reminder, there will be a virtual sprint next week July 8-9, 2015 15:00 
UTC to finish the remaining tasks.
If you’re interested in helping out in any of the remaining tasks (Jenkins Job 
Builder, Nodepool, Logstash/Kibana, Documentation, Sample site.pp) Sign up on 
the eitherpad. [4]

Also, we can use the 3rd party meeting time slot next week to discuss plans and 
answer questions [5].
Tuesday 7/7/15 1700 UTC #openstack-meeting

Ramy
IRC: asselin

[1] https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://github.com/rasselin/os-ext-testing (forked from 
jaypipes/os-ext-testing)
[4] https://etherpad.openstack.org/p/common-ci-sprint
[5] https://wiki.openstack.org/wiki/Meetings/ThirdParty


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [third-party][infra][CI] Common OpenStack 'Third-party' CI Solution - DONE!

2015-11-20 Thread Asselin, Ramy
Hi Sid,

Instead of documenting it, was simple enough to automate it. Please try these 
out:

https://review.openstack.org/248223

https://review.openstack.org/248226

Feel free to propose your own fixes or improvements. I think this is one of 
best parts of getting it all in sync upstream.

Best regards,
Ramy



From: Asselin, Ramy
Sent: Friday, November 20, 2015 11:03 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [third-party][infra][CI] Common OpenStack 
'Third-party' CI Solution - DONE!

Hi Sid,

Sorry, you’re right: log server fix is here. [1]
I thought I documented the scp v1.9 plugin issue, but I don’t see it now. I 
will submit a patch to add that.

Thanks for raising these issues!

Ramy

[1] https://review.openstack.org/#/c/242800/


From: Siddharth Bhatt [mailto:siddharth.bh...@falconstor.com]
Sent: Friday, November 20, 2015 10:51 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [third-party][infra][CI] Common OpenStack 
'Third-party' CI Solution - DONE!

Ramy,

I had previously used your os-ext-testing repo to build a 3rd party CI, and 
today I’ve been trying out this new approach. I’ve noticed a piece of the 
puzzle appears to be missing.

In the new instructions [1], there is no mention of having to manually install 
the Jenkins SCP plugin v1.9. Also, your old manifest would create the plugin 
config file [2] and populate it with the appropriate values for the log server, 
but the new approach does not. So when I finished running the puppet apply, the 
job configurations contained a site name “LogServer” but there was no value 
defined anywhere pointing that to the actual IP or hostname of my log server.

I did manually install the v1.9 plugin and then configured it from the Jenkins 
web UI. I guess either the instructions need to be updated to mention this, or 
the puppet manifests need to automate some or all of it.

Regards,
Sid

[1] 
https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/README.md
[2] /var/lib/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml

From: Asselin, Ramy [mailto:ramy.asse...@hpe.com]
Sent: Friday, November 20, 2015 12:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party][infra][CI] Common OpenStack 
'Third-party' CI Solution - DONE!

All,

I’m happy to announce that there is now a working ‘Common’ OpenStack 
‘third-party’ CI Solution available! This is a 3rd party CI solution that uses 
the same tools and scripts as the upstream ‘Jenkins’ CI.

The last few pieces were particularly challenging.
Big thanks to Yolanda Robla for updating Nodepool  & nodepool puppet scripts so 
that is can be reusable by both 3rd party CI’s and upstream infrastructure!

The documentation for setting up a 3rd party ci system on 2 VMs (1 private that 
runs the CI jobs, and 1 public that hosts the log files) is now available here 
[1] or [2]

Big thanks again to everyone that helped submit patches and do the reviews!

A few people have already starting setting up this solution.

Best regards,

Ramy
IRC: asselin

[1] https://github.com/openstack-infra/puppet-openstackci/tree/master/contrib
[2] 
https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/README.md


From: Asselin, Ramy
Sent: Monday, July 20, 2015 3:39 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [third-party][infra] Common OpenStack CI Solution 
- 'Jenkins Job Builder' live

All,

I’m pleased to announce the 4th component merged to puppet-openstackci repo [1].

This means 3rd party ci operators can now use the same scripts that the 
OpenStack Infrastructure team uses in the official ‘Jenkins’ CI system for:


1.   Log Server

2.   Jenkins

3.   Zuul

4.   Jenkins Job Builder

This work is being done as part of the common-ci spec [2]

Big thanks to Juame Devesa for starting the work, Khai Do for fixing all issues 
found in the reviews during the virtual sprint, and to all the reviewers and 
testers.

We’re almost there! Just have nodepool and a sample config to compose all of 
the components together [3]!

Ramy
IRC: asselin

[1] https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101


From: Asselin, Ramy
Sent: Thursday, July 02, 2015 4:59 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [third-party][infra] Common OpenStack CI Solution - 
'Zuul' li

Re: [openstack-dev] [third-party][infra][CI] Common OpenStack 'Third-party' CI Solution - DONE!

2015-11-20 Thread Asselin, Ramy
Hi Sid,

Sorry, you’re right: log server fix is here. [1]
I thought I documented the scp v1.9 plugin issue, but I don’t see it now. I 
will submit a patch to add that.

Thanks for raising these issues!

Ramy

[1] https://review.openstack.org/#/c/242800/


From: Siddharth Bhatt [mailto:siddharth.bh...@falconstor.com]
Sent: Friday, November 20, 2015 10:51 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [third-party][infra][CI] Common OpenStack 
'Third-party' CI Solution - DONE!

Ramy,

I had previously used your os-ext-testing repo to build a 3rd party CI, and 
today I’ve been trying out this new approach. I’ve noticed a piece of the 
puzzle appears to be missing.

In the new instructions [1], there is no mention of having to manually install 
the Jenkins SCP plugin v1.9. Also, your old manifest would create the plugin 
config file [2] and populate it with the appropriate values for the log server, 
but the new approach does not. So when I finished running the puppet apply, the 
job configurations contained a site name “LogServer” but there was no value 
defined anywhere pointing that to the actual IP or hostname of my log server.

I did manually install the v1.9 plugin and then configured it from the Jenkins 
web UI. I guess either the instructions need to be updated to mention this, or 
the puppet manifests need to automate some or all of it.

Regards,
Sid

[1] 
https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/README.md
[2] /var/lib/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml

From: Asselin, Ramy [mailto:ramy.asse...@hpe.com]
Sent: Friday, November 20, 2015 12:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party][infra][CI] Common OpenStack 
'Third-party' CI Solution - DONE!

All,

I’m happy to announce that there is now a working ‘Common’ OpenStack 
‘third-party’ CI Solution available! This is a 3rd party CI solution that uses 
the same tools and scripts as the upstream ‘Jenkins’ CI.

The last few pieces were particularly challenging.
Big thanks to Yolanda Robla for updating Nodepool  & nodepool puppet scripts so 
that is can be reusable by both 3rd party CI’s and upstream infrastructure!

The documentation for setting up a 3rd party ci system on 2 VMs (1 private that 
runs the CI jobs, and 1 public that hosts the log files) is now available here 
[1] or [2]

Big thanks again to everyone that helped submit patches and do the reviews!

A few people have already starting setting up this solution.

Best regards,

Ramy
IRC: asselin

[1] https://github.com/openstack-infra/puppet-openstackci/tree/master/contrib
[2] 
https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/README.md


From: Asselin, Ramy
Sent: Monday, July 20, 2015 3:39 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [third-party][infra] Common OpenStack CI Solution 
- 'Jenkins Job Builder' live

All,

I’m pleased to announce the 4th component merged to puppet-openstackci repo [1].

This means 3rd party ci operators can now use the same scripts that the 
OpenStack Infrastructure team uses in the official ‘Jenkins’ CI system for:


1.   Log Server

2.   Jenkins

3.   Zuul

4.   Jenkins Job Builder

This work is being done as part of the common-ci spec [2]

Big thanks to Juame Devesa for starting the work, Khai Do for fixing all issues 
found in the reviews during the virtual sprint, and to all the reviewers and 
testers.

We’re almost there! Just have nodepool and a sample config to compose all of 
the components together [3]!

Ramy
IRC: asselin

[1] https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101


From: Asselin, Ramy
Sent: Thursday, July 02, 2015 4:59 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [third-party][infra] Common OpenStack CI Solution - 
'Zuul' live

All,

I’m please to say that there are now 3 components merged in the 
puppet-openstackci repo [1]
This means 3rd party ci operators can now use the same scripts that the 
OpenStack Infrastructure team uses in the official ‘Jenkins’ CI system for:


1.   Log Server

2.   Jenkins

3.   Zuul

This work is being done as part of the common-ci spec [2]

Big thanks to Fabien Boucher for completing the Zuul script refactoring, which 
went live today!
Thanks to all the reviewers for careful reviews which led to a smooth migration.

I’ve updated my repo [3] & switched all my CI systems to use it.

As a reminder, there w

Re: [openstack-dev] [third-party] third party ci operators meetup in Tokyo

2015-10-27 Thread Asselin, Ramy
All,

We'll plan to have lunch at the Lunch Buffet/Breakout Sessions area (Hokushin) 
next to where the Keynotes are given.
We'll meet at 1 pm, just after Yolanda's talk "Kubestack CI: dynamic jenkins 
slaves using Kubernetes" in Wakakshiba http://sched.co/4Rle

See you there!
Ramy


-Original Message-
From: Sean McGinnis [mailto:sean.mcgin...@gmx.com] 
Sent: Sunday, October 25, 2015 10:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [third-party] third party ci operators meetup in 
Tokyo

On Fri, Oct 23, 2015 at 07:08:18PM +0000, Asselin, Ramy wrote:
> Would any 3rd party ci operators like to meetup in Tokyo during the summit?
> 
> I would like to propose we have lunch together at one of the summit lunch 
> areas on Wednesday, October 28.
> 
> Please reply to this thread. You can also message me via google hangouts: 
> ramy.asse...@gmail.com<mailto:ramy.asse...@gmail.com>.
> 
> 
> Thanks!
> Ramy

Hey Ramy,

Great idea. I'll try to join up if I can.

Sean

> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [third-party] third party ci operators meetup in Tokyo

2015-10-23 Thread Asselin, Ramy
Would any 3rd party ci operators like to meetup in Tokyo during the summit?

I would like to propose we have lunch together at one of the summit lunch areas 
on Wednesday, October 28.

Please reply to this thread. You can also message me via google hangouts: 
ramy.asse...@gmail.com.


Thanks!
Ramy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Third-Party][CI] Add accouts to CI group

2015-10-16 Thread Asselin, Ramy
Done, you have these 3 now:
Fujitsu C-Fabric CI lsoft-cfabri...@ml.css.fujitsu.com
Fujitsu ETERNUS CI  lsoft-eternu...@ml.css.fujitsu.com
Fujitsu IRMC CI lsoft-irm...@ml.css.fujitsu.com
Ramy
-Original Message-
From: Watanabe, Isao [mailto:watanabe_i...@jp.fujitsu.com] 
Sent: Friday, October 16, 2015 4:52 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Third-Party][CI] Add accouts to CI group

Hello, Third-Party Coordinators
Cc:Ramy

Could you add the following 2 accounts to CI group, please?
Also, we will continually update the wiki.
[1]
Name: Fujitsu C-Fabric CI
Mail: lsoft-cfabri...@ml.css.fujitsu.com
Wiki: https://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_C-Fabric_CI

[2]
Name: Fujitsu IRMC CI
Mail: lsoft-irm...@ml.css.fujitsu.com
Wiki: https://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_IRMC_CI


Best regards,
Watanabe.isao




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [third-party] Reminder of 3rd party ci working group meeting Tuesday at 1700 UTC in #openstack-meeting

2015-09-28 Thread Asselin, Ramy
Hi,

This is a reminder for 3rd party ci operators that there is a working group 
meeting Tuesday at 1700 UTC in #openstack-meeting

The agenda is available here. Please feel free to add additional topics: 
https://wiki.openstack.org/wiki/Meetings/ThirdParty#Agenda_for_next_Working_Group_meeting

Thanks,
Ramy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [third-party] Nodepool: OpenStackCloudException: Image creation failed: 403 Forbidden: Attribute 'is_public' is reserved. (HTTP 403)

2015-09-24 Thread Asselin, Ramy
If anyone is getting the following stack trace in nodepool trying to upload 
images to their providers:

2015-09-24 09:16:53,639 ERROR nodepool.DiskImageUpdater: Exception updating 
image dpc in p222fc:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/nodepool/nodepool.py", line 979, 
in _run
self.updateImage(session)
  File "/usr/local/lib/python2.7/dist-packages/nodepool/nodepool.py", line 
1023, in updateImage
self.image.meta)
  File "/usr/local/lib/python2.7/dist-packages/nodepool/provider_manager.py", 
line 531, in uploadImage
**meta)
  File "/usr/local/lib/python2.7/dist-packages/shade/__init__.py", line 1401, 
in create_image
"Image creation failed: {message}".format(message=str(e)))
OpenStackCloudException: Image creation failed: 403 Forbidden: Attribute 
'is_public' is reserved. (HTTP 403)


This was worked-around / fixed in this patch of shade which merged a few hours 
ago: https://review.openstack.org/#/c/226492/

It will be released to pypi "soon", but I don't know when. In the meantime you 
can pip install it from openstack-infra/shade master.

Ramy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified into gerrit server

2015-09-11 Thread Asselin, Ramy
Follow these instructions to get permission from cinder: [1]
Ramy

[1] 
http://docs.openstack.org/infra/system-config/third_party.html#permissions-on-your-third-party-system

-Original Message-
From: Watanabe, Isao [mailto:watanabe_i...@jp.fujitsu.com] 
Sent: Friday, September 11, 2015 2:26 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified into gerrit 
server

Hello, Ramy

Thank you for your help.
Could you do me another favor, please.
I need to move our CI from sandbox to cinder later.
Do I need to register the CI to anywhere, so that the CI could test new patch 
set in cinder project, please?

Best regards,
Watanabe.isao



> -Original Message-
> From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
> Sent: Friday, September 11, 2015 12:07 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified 
> into gerrit server
> 
> Done. Thank you for adding your CI system to the wiki.
> 
> Ramy
> 
> -Original Message-
> From: Watanabe, Isao [mailto:watanabe_i...@jp.fujitsu.com]
> Sent: Thursday, September 10, 2015 8:00 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified 
> into gerrit server
> 
> Hello, Ramy
> 
> Could you please add the following CI to the third-party ci group, too.
> 
> Fujitsu ETERNUS CI
> 
> We are preparing this CI test system, and going to use this CI system 
> to test Cinder.
> The wiki of this CI:
> <https://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_ETERNUS_CI>
> 
> Thank you very much.
> 
> Best regards,
> Watanabe.isao
> 
> 
> 
> > -Original Message-
> > From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
> > Sent: Thursday, September 10, 2015 8:00 PM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified 
> > into gerrit server
> >
> > I added Fnst OpenStackTest CI
> > <https://review.openstack.org/#/q/owner:openstack_dev%2540163.com+st
> > at us :open,n,z>  to the third-party ci group.
> >
> > Ramy
> >
> >
> >
> > From: Evgeny Antyshev [mailto:eantys...@virtuozzo.com]
> > Sent: Thursday, September 10, 2015 3:51 AM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified 
> > into gerrit server
> >
> >
> >
> >
> >
> > On 10.09.2015 11:30, Xie, Xianshan wrote:
> >
> > Hi, all,
> >
> >In my CI environment, after submitting a patch into 
> > openstack-dev/sandbox,
> >
> > the Jenkins Job can be launched automatically, and the result 
> > message of the job also can be posted into the gerrit server successfully.
> >
> > Everything seems fine.
> >
> >
> >
> > But in the "Verified" column, there is no verified vote, such as +1 
> > or -1.
> >
> > You will be able when your CI account is added to "Third-Party CI"
> > group on review.openstack.org
> > https://review.openstack.org/#/admin/groups/270,members
> > I advice you to ask for such a permission in an IRC meeting for 
> > third-party CI maintainers:
> > https://wiki.openstack.org/wiki/Meetings/ThirdParty
> > But you still won't be able to vote on other projects, except the sandbox.
> >
> >
> >
> >
> > (patch url: https://review.openstack.org/#/c/222049/
> > <https://review.openstack.org/#/c/222049/> ,
> >
> > CI name:  Fnst OpenStackTest CI)
> >
> >
> >
> > Although I have already added the "verified" label into the 
> > layout.yaml , under the check pipeline, it does not work yet.
> >
> >
> >
> > And my configuration info is setted as follows:
> >
> > Layout.yaml
> >
> > ---
> >
> > pipelines:
> >
> >   - name: check
> >
> >trigger:
> >
> >  gerrit:
> >
> >   - event: patchset-created
> >
> >   - event: change-restored
> >
> >   - event: comment-added
> >
> > ...
> >
> >success:
> >
> > gerrit:
> >
> >   verified: 1
> >
> >failure:
> >
> > gerrit:
> >
> >   ve

Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified into gerrit server

2015-09-10 Thread Asselin, Ramy
I added Fnst OpenStackTest 
CI
 to the third-party ci group.
Ramy

From: Evgeny Antyshev [mailto:eantys...@virtuozzo.com]
Sent: Thursday, September 10, 2015 3:51 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified into gerrit 
server


On 10.09.2015 11:30, Xie, Xianshan wrote:
Hi, all,
   In my CI environment, after submitting a patch into openstack-dev/sandbox,
the Jenkins Job can be launched automatically, and the result message of the 
job also can be posted into the gerrit server successfully.
Everything seems fine.

But in the "Verified" column, there is no verified vote, such as +1 or -1.
You will be able when your CI account is added to "Third-Party CI" group on 
review.openstack.org
https://review.openstack.org/#/admin/groups/270,members
I advice you to ask for such a permission in an IRC meeting for third-party CI 
maintainers:
https://wiki.openstack.org/wiki/Meetings/ThirdParty
But you still won't be able to vote on other projects, except the sandbox.


(patch url: https://review.openstack.org/#/c/222049/,
CI name:  Fnst OpenStackTest CI)

Although I have already added the "verified" label into the layout.yaml , under 
the check pipeline, it does not work yet.

And my configuration info is setted as follows:
Layout.yaml
---
pipelines:
  - name: check
   trigger:
 gerrit:
  - event: patchset-created
  - event: change-restored
  - event: comment-added
...
   success:
gerrit:
  verified: 1
   failure:
gerrit:
  verified: -1

jobs:
   - name: noop-check-communication
  parameter-function: reusable_node
projects:
- name: openstack-dev/sandbox
   - noop-check-communication
---


And the projects.yaml of Jenkins job:
---
- project:
name: sandbox
jobs:
  - noop-check-communication:
 node: 'devstack_slave || devstack-precise-check || d-p-c'
...
---

Could anyone help me? Thanks in advance.

Xiexs





__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified into gerrit server

2015-09-10 Thread Asselin, Ramy
Done. Thank you for adding your CI system to the wiki.

Ramy

-Original Message-
From: Watanabe, Isao [mailto:watanabe_i...@jp.fujitsu.com] 
Sent: Thursday, September 10, 2015 8:00 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified into gerrit 
server

Hello, Ramy

Could you please add the following CI to the third-party ci group, too.

Fujitsu ETERNUS CI

We are preparing this CI test system, and going to use this CI system to test 
Cinder.
The wiki of this CI:
<https://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_ETERNUS_CI>

Thank you very much.

Best regards,
Watanabe.isao



> -Original Message-
> From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
> Sent: Thursday, September 10, 2015 8:00 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified 
> into gerrit server
> 
> I added Fnst OpenStackTest CI
> <https://review.openstack.org/#/q/owner:openstack_dev%2540163.com+stat
> us :open,n,z>  to the third-party ci group.
> 
> Ramy
> 
> 
> 
> From: Evgeny Antyshev [mailto:eantys...@virtuozzo.com]
> Sent: Thursday, September 10, 2015 3:51 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [CI] [zuul] Can not vote +/-1 verified 
> into gerrit server
> 
> 
> 
> 
> 
> On 10.09.2015 11:30, Xie, Xianshan wrote:
> 
>   Hi, all,
> 
>  In my CI environment, after submitting a patch into 
> openstack-dev/sandbox,
> 
>   the Jenkins Job can be launched automatically, and the result message 
> of the job also can be posted into the gerrit server successfully.
> 
>   Everything seems fine.
> 
> 
> 
>   But in the "Verified" column, there is no verified vote, such as +1 
> or -1.
> 
> You will be able when your CI account is added to "Third-Party CI" 
> group on review.openstack.org 
> https://review.openstack.org/#/admin/groups/270,members
> I advice you to ask for such a permission in an IRC meeting for 
> third-party CI maintainers:
> https://wiki.openstack.org/wiki/Meetings/ThirdParty
> But you still won't be able to vote on other projects, except the sandbox.
> 
> 
> 
> 
>   (patch url: https://review.openstack.org/#/c/222049/
> <https://review.openstack.org/#/c/222049/> ,
> 
>   CI name:  Fnst OpenStackTest CI)
> 
> 
> 
>   Although I have already added the "verified" label into the 
> layout.yaml , under the check pipeline, it does not work yet.
> 
> 
> 
>   And my configuration info is setted as follows:
> 
>   Layout.yaml
> 
>   ---
> 
>   pipelines:
> 
> - name: check
> 
>  trigger:
> 
>gerrit:
> 
> - event: patchset-created
> 
> - event: change-restored
> 
> - event: comment-added
> 
>   ...
> 
>  success:
> 
>   gerrit:
> 
> verified: 1
> 
>  failure:
> 
>   gerrit:
> 
> verified: -1
> 
> 
> 
>   jobs:
> 
>  - name: noop-check-communication
> 
> parameter-function: reusable_node
> 
>   projects:
> 
>   - name: openstack-dev/sandbox
> 
>  - noop-check-communication
> 
>   ---
> 
> 
> 
> 
> 
>   And the projects.yaml of Jenkins job:
> 
>   ---
> 
>   - project:
> 
>   name: sandbox
> 
>   jobs:
> 
> - noop-check-communication:
> 
>node: 'devstack_slave || devstack-precise-check || d-p-c'
> 
>   ...
> 
>   ---
> 
> 
> 
>   Could anyone help me? Thanks in advance.
> 
> 
> 
>   Xiexs
> 
> 
> 
> 
> 
> 
> 
> 
>   
> __
>   OpenStack Development Mailing List (not for usage questions)
>   Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-de
> v
> 
> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [nova] ProviderFirewallRules still available?

2015-08-31 Thread Asselin, Ramy
I saw this thread, "Undead DB objects: ProviderFirewallRule and 
InstanceGroupPolicy?" [1]

Seems to be in the process of getting removed from the DB, but are provider 
level firewalls still available? I still see a lot of code that indicates it 
does [2]

I traced it to here, but not sure where the nova context is stored [3]

Ramy
Irc:asselin
[1] http://lists.openstack.org/pipermail/openstack-dev/2014-November/050959.html
[2] https://github.com/openstack/nova/search?l=python=provider=%E2%9C%93
[3] 
https://github.com/openstack/nova/blob/b0854ba0c697243aa3d91170d1a22896aed60e02/nova/conductor/rpcapi.py#L215



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [third-party] [CI] The dsvm-tempest-full job failed

2015-08-31 Thread Asselin, Ramy
Hi Xiexs,

After the jobs starts and the nodepool node is marked “used’ use the nodepool 
hold  command.
This will prevent it from being deleted until you do so manually.

Ramy

From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com]
Sent: Monday, August 31, 2015 12:46 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party] [CI] The dsvm-tempest-full job failed

Hi, all,
  I`m trying to run the job "dsvm-tempest-full" in a slave node which built and 
managed by the nodepool.
But I got the following error messages:
--
14:45:48 + timeout -s 9 174m /opt/stack/new/devstack-gate/devstack-vm-gate.sh
14:45:48 timeout: failed to run command 
‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory

...
14:45:48 + echo 'ERROR: the main setup script run by this job failed - exit 
code: 127'
14:45:48 ERROR: the main setup script run by this job failed - exit code: 127
...
14:45:52 No hosts matched
14:45:52 + exit 127
14:45:52 Build step 'Execute shell' marked build as failure
14:45:53 Finished: FAILURE
--
I have no idea what caused this issue.
And furthermore, it seems no more chances to find the detailed information 
about this error,
because the slave node was deleted soon by the nodepool automatically, after 
this job finished.
Is there a setting for the nodepool to prevent the used node being deleted?

I have posted the full console log (which displayed in the Jenkins server) on 
the paste server:
http://paste.openstack.org/show/434487/

Cloud you give me some guidances to work this out?
Thanks in advance.


Xiexs
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [OpenStack-Infra] [openstack-infra][third-party][CI][nodepool] Uploading images to nodepool.

2015-08-27 Thread Asselin, Ramy
[2] is the best option to upload the image.

Yes, the install_master.sh script manually runs puppet to apply your dev 
changes to nodepool.yaml and vars.sh to your production configuration (e.g. 
/etc/nodepool/nodepool.yaml).

Ramy

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Wednesday, August 26, 2015 10:48 PM
To: OpenStack Development Mailing List (not for usage questions); 
openstack-in...@lists.openstack.org
Subject: [OpenStack-Infra] [openstack-infra][third-party][CI][nodepool] 
Uploading images to nodepool.

Hi Folks,

I am following Ramy's new guide for setting up the CI. Till now I have 
installed master and created the slave node image using [1]. Now I want to 
upload the image to nodepool, so can I use [2] to do so, or is there any other 
way also to do so.


  *   Also is there any other changes that need to be done, in vars.sh [3] and 
nodepool.yaml [4]?
  *   And do I need to reinstall the master after setting up the changes in 
nodepool.yaml and vars.sh?

Please enlighten me with your ideas folks.

[1] 
https://github.com/openstack-infra/project-config/tree/master/nodepool/elements#using-diskimage-builder-to-build-devstack-gate-nodes
[2] nodepool image-upload all image-name
[3] 
https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L17
[4] 
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/nodepool/nodepool.yaml.erb.sample

--
[https://docs.google.com/uc?export=downloadid=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [cinder][third-party] StorPool Cinder CI

2015-08-27 Thread Asselin, Ramy
Hi Peter,

Your log files require downloads. Please fix it such that they can be viewed 
directly [1]

Also, it's not clear where in your scripts you actually pull down the cinder 
patch.

Ramy

[1] 
http://docs.openstack.org/infra/system-config/third_party.html#faq-frequently-asked-questions


-Original Message-
From: Peter Penchev [mailto:openstack-...@storpool.com] 
Sent: Thursday, August 27, 2015 1:43 PM
To: OpenStack openstack-dev@lists.openstack.org
Subject: [openstack-dev] [cinder][third-party] StorPool Cinder CI

Hi,

Some time ago I sent
http://lists.openstack.org/pipermail/third-party-announce/2015-August/000261.html
to the third-party-announce list as a reply to a message about the StorPool 
Cinder third-party CI being disabled.  Well, as I wrote in my reply there, I 
think that we have done what Mike Perez asked us to - reconfigured our CI to 
run in silent mode and keep it running for a while, updating our local patches 
to deal with the changes in Cinder, Nova and Brick, and put out the logs so 
that they're available for public perusal.  That message contains links to some 
CI runs as of the time of its sending, but here are some new ones as of today:

http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3129/
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3128/
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3127/
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3126/
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3125/
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3124/
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3123/
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3122/
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3121/
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3120/

So, would that be enough to get our CI system's Gerrit account reenabled, as a 
first step towards putting the StorPool Cinder driver back in?  Of course, if 
there's anyhing else we should do, just let us know.

Once again, thanks to all of you for your work on OpenStack, and thanks to 
Anita Kuno, Mike Perez, and everyone else for keeping an eye on the third-party 
CI systems!

G'luck,
Peter

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [cinder][third-party] StorPool Cinder CI

2015-08-27 Thread Asselin, Ramy
Ok. Can you add a git log -n 1? It would be nice to positively confirm the 
patch under test is being used:

e.g.
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3129/console.log
 

points to:

 Triggered by: https://review.openstack.org/217802 patchset 1: iSCSI fix 
misleading Log warning on connect fail

But your pre-test- hook:

+ cd /opt/stack/new/cinder
2015-08-27 20:18:15.863 | + git remote add osci 
git+ssh://logarchive@osci-jenkins-master/var/lib/osci/git/cinder/
2015-08-27 20:18:15.864 | + git fetch osci
2015-08-27 20:18:16.033 | From 
git+ssh://osci-jenkins-master/var/lib/osci/git/cinder
2015-08-27 20:18:16.034 |  * [new branch]  master - osci/master
2015-08-27 20:18:16.036 |  * [new branch]  storpool-osci - 
osci/storpool-osci
2015-08-27 20:18:16.037 |  * [new branch]  storpool-osci-01 - 
osci/storpool-osci-01
2015-08-27 20:18:16.038 |  * [new branch]  storpool-osci-02 - 
osci/storpool-osci-02
2015-08-27 20:18:16.039 |  * [new branch]  storpool-osci-03 - 
osci/storpool-osci-03
2015-08-27 20:18:16.040 |  * [new branch]  storpool-osci-04 - 
osci/storpool-osci-04
2015-08-27 20:18:16.041 |  * [new branch]  storpool-osci-05 - 
osci/storpool-osci-05
2015-08-27 20:18:16.042 |  * [new branch]  storpool-osci-06 - 
osci/storpool-osci-06
2015-08-27 20:18:16.043 |  * [new branch]  storpool-osci-07 - 
osci/storpool-osci-07
2015-08-27 20:18:16.044 |  * [new branch]  storpool-osci-08 - 
osci/storpool-osci-08
2015-08-27 20:18:16.045 |  * [new branch]  storpool-osci-09 - 
osci/storpool-osci-09
2015-08-27 20:18:16.046 |  * [new tag] bp - bp
2015-08-27 20:18:16.046 | + git rebase osci/storpool-osci
2015-08-27 20:18:16.090 | First, rewinding head to replay your work on top of 
it...
2015-08-27 20:18:16.155 | Applying: Port test_nfs to Python 3
2015-08-27 20:18:16.185 | Applying: Implement function to manage/unmanage 
snapshots

^^ I would expect to see  iSCSI fix misleading Log warning on connect fail 
somewhere here.

Ramy

-Original Message-
From: Peter Penchev [mailto:openstack-...@storpool.com] 
Sent: Thursday, August 27, 2015 3:03 PM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [cinder][third-party] StorPool Cinder CI

On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy ramy.asse...@hp.com wrote:
 Hi Peter,

 Your log files require downloads. Please fix it such that they can be 
 viewed directly [1]

Hi, and thanks for the fast reply!  Yes, I'll try to change the webserver's 
configuration, although the snippet in the FAQ won''t help a lot, since it's a 
lighttpd server, not Apache.  I'll get back to you when I've figured something 
out.

 Also, it's not clear where in your scripts you actually pull down the cinder 
 patch.

It's in the pre_test_hook, the for loop that rebases cinder, nova, os-brick, 
etc. onto the storpool-osci branch of our local repo:

2015-08-27 20:18:15.857 | + echo '=== Fetch the StorPool modifications:'
2015-08-27 20:18:15.858 | === Fetch the StorPool modifications:
2015-08-27 20:18:15.859 | + for i in cinder devstack devstack-gate nova 
os-brick tempest
2015-08-27 20:18:15.860 | + echo '=== - cinder'
2015-08-27 20:18:15.861 | === - cinder
2015-08-27 20:18:15.862 | + cd /opt/stack/new/cinder
2015-08-27 20:18:15.863 | + git remote add osci
git+ssh://logarchive@osci-jenkins-master/var/lib/osci/git/cinder/
2015-08-27 20:18:15.864 | + git fetch osci
2015-08-27 20:18:16.033 | From
git+ssh://osci-jenkins-master/var/lib/osci/git/cinder
2015-08-27 20:18:16.034 |  * [new branch]  master - osci/master
2015-08-27 20:18:16.036 |  * [new branch]  storpool-osci -
osci/storpool-osci
[snip]
2015-08-27 20:18:16.046 | + git rebase osci/storpool-osci
2015-08-27 20:18:16.090 | First, rewinding head to replay your work on top of 
it...
2015-08-27 20:18:16.155 | Applying: Port test_nfs to Python 3
2015-08-27 20:18:16.185 | Applying: Implement function to manage/unmanage 
snapshots

...and then proceeds to do the same for the rest of the OpenStack projects 
listed on the third line.

G'luck,
Peter

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [third-party] Timeout waiting for ssh access

2015-08-26 Thread Asselin, Ramy
Hi Abhi,

First, using DIB is generally easier. However to use the scripts, you configure 
nodepool to do so.

You should already have the scripts directory set [1]
Then you configure the script as the starting point for the image-build via 
setup: prepare_node.sh [2]
Be sure to correctly configure the credentials, ssh keys, etc. as well.

You can use nodepool image-update command to manually invoke it image builds 
using this option.

Ramy

[1] http://docs.openstack.org/infra/nodepool/configuration.html#script-dir
[2] http://docs.openstack.org/infra/nodepool/configuration.html#images




From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Tuesday, August 25, 2015 7:51 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [third-party] Timeout waiting for ssh access

Hi Ramy,

Can you mention the steps for glance  scripts?

On Tue, Aug 25, 2015 at 7:49 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
Hi Tang,

I haven’t seen this issue. Which approach are you using to build the image? DIB 
or via glance  scripts?
Do you get the same result when using both approaches?
If using DIB, what is the OS used to build the image?

Ramy

From: Tang Chen [mailto:tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com]
Sent: Tuesday, August 25, 2015 5:02 AM
To: openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [third-party] Timeout waiting for ssh access

Hi all,

Does anybody have any idea about this problem ?

Since ubuntu does not have /etc/sysconfig/network-scripts/ifcfg-*,
obviously it is a fedora like fs structure, we have tried to use centos,
but we still got the same error.

Thanks.
On 08/24/2015 09:19 PM, Xie, Xianshan wrote:
Hi, All
  I`m still strugling to setup nodepool env, and i got following error messages:
--
ERROR nodepool.NodeLauncher: Exception launching node id: 13 in provider: 
local_01 error:
  Traceback (most recent call last):
File /home/fujitsu/xiexs/nodepool/nodepool/nodepool.py, line 405, in 
_run
  dt = self.launchNode(session)
File /home/fujitsu/xiexs/nodepool/nodepool/nodepool.py, line 503, in 
launchNode
  timeout=self.timeout):
File /home/fujitsu/xiexs/nodepool/nodepool/nodeutils.py, line 50, in 
ssh_connect
  for count in iterate_timeout(timeout, ssh access):
File /home/fujitsu/xiexs/nodepool/nodepool/nodeutils.py, line 42, in 
iterate_timeout
  raise Exception(Timeout waiting for %s % purpose)
  Exception: Timeout waiting for ssh access
 WARNING nodepool.NodePool: Deleting leaked instance d-p-c-local_01-12 
(aa6f58d9-f691-4a72-98db-6add9d0edc1f) in local_01 for node id: 12
--

And meanwhile, in the console.log which records the info for launching this 
instance,
there is also an error as follows:
--
+ sed -i -e s/^\(DNS[0-9]*=[.0-9]\+\)/#\1/g 
/etc/sysconfig/network-scripts/ifcfg-*^M
sed: can't read /etc/sysconfig/network-scripts/ifcfg-*: No such file or 
directory^M
...
cloud-init-nonet[26.16]: waiting 120 seconds for network device
--

I have tried to figure out what`s causing this error:
1. mounted image.qcow2 and then checked the configuration for the network about 
this instance:
$ cat etc/network/interfaces.d/eth0.cfg
   auto eth0
   iface eth0 inet dhcp

$ cat etc/network/interfaces
   auto lo
   iface lo inet loopback
   source /etc/network/interfaces.d/*.cfg

It seems good.

2. But indeed, the directory named /etc/sysconfig/network-scripts/ifcfg-* does 
not exist.
And i dont understand why it attempts to check this configuration file?
Because my instance is specified to ubuntu not rhel.

So,could you give me some tips to work this out?
Thanks in advance.

Xiexs



__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
[https://docs.google.com/uc?export=downloadid=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [third-party] Timeout waiting for ssh access

2015-08-25 Thread Asselin, Ramy
Hi Tang,

I haven't seen this issue. Which approach are you using to build the image? DIB 
or via glance  scripts?
Do you get the same result when using both approaches?
If using DIB, what is the OS used to build the image?

Ramy

From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Tuesday, August 25, 2015 5:02 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [third-party] Timeout waiting for ssh access

Hi all,

Does anybody have any idea about this problem ?

Since ubuntu does not have /etc/sysconfig/network-scripts/ifcfg-*,
obviously it is a fedora like fs structure, we have tried to use centos,
but we still got the same error.

Thanks.

On 08/24/2015 09:19 PM, Xie, Xianshan wrote:
Hi, All
  I`m still strugling to setup nodepool env, and i got following error messages:
--
ERROR nodepool.NodeLauncher: Exception launching node id: 13 in provider: 
local_01 error:
  Traceback (most recent call last):
File /home/fujitsu/xiexs/nodepool/nodepool/nodepool.py, line 405, in 
_run
  dt = self.launchNode(session)
File /home/fujitsu/xiexs/nodepool/nodepool/nodepool.py, line 503, in 
launchNode
  timeout=self.timeout):
File /home/fujitsu/xiexs/nodepool/nodepool/nodeutils.py, line 50, in 
ssh_connect
  for count in iterate_timeout(timeout, ssh access):
File /home/fujitsu/xiexs/nodepool/nodepool/nodeutils.py, line 42, in 
iterate_timeout
  raise Exception(Timeout waiting for %s % purpose)
  Exception: Timeout waiting for ssh access
 WARNING nodepool.NodePool: Deleting leaked instance d-p-c-local_01-12 
(aa6f58d9-f691-4a72-98db-6add9d0edc1f) in local_01 for node id: 12
--

And meanwhile, in the console.log which records the info for launching this 
instance,
there is also an error as follows:
--
+ sed -i -e s/^\(DNS[0-9]*=[.0-9]\+\)/#\1/g 
/etc/sysconfig/network-scripts/ifcfg-*^M
sed: can't read /etc/sysconfig/network-scripts/ifcfg-*: No such file or 
directory^M
...
cloud-init-nonet[26.16]: waiting 120 seconds for network device
--

I have tried to figure out what`s causing this error:
1. mounted image.qcow2 and then checked the configuration for the network about 
this instance:
$ cat etc/network/interfaces.d/eth0.cfg
   auto eth0
   iface eth0 inet dhcp

$ cat etc/network/interfaces
   auto lo
   iface lo inet loopback
   source /etc/network/interfaces.d/*.cfg

It seems good.

2. But indeed, the directory named /etc/sysconfig/network-scripts/ifcfg-* does 
not exist.
And i dont understand why it attempts to check this configuration file?
Because my instance is specified to ubuntu not rhel.

So,could you give me some tips to work this out?
Thanks in advance.

Xiexs




__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [all][third-party][ci] Announcing CI Watch - Third-party CI monitoring tool

2015-08-25 Thread Asselin, Ramy
HI Skyler,

Very nice tool! When do you plan to open source it? Are you considering adding 
it to the OpenStack big-tent [1]?
There are a few tools being worked on that provide different information 
[2][3][4]. It would be nice to consolidate and invest collective effort into 
one tool.
It would be great to meet and discuss in the third party meeting [5], as Anita 
suggested. Are you available next Monday or Tuesday?

Thanks!
Ramy

[1] http://docs.openstack.org/infra/manual/creators.html 
[2] 
http://git.openstack.org/cgit/stackforge/third-party-ci-tools/tree/monitoring/lastcomment-scoreboard
[3] 
http://git.openstack.org/cgit/stackforge/third-party-ci-tools/tree/monitoring/scoreboard
[4] http://git.openstack.org/cgit/stackforge/radar/tree/
[5] 
https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


-Original Message-
From: Anita Kuno [mailto:ante...@anteaya.info] 
Sent: Monday, August 24, 2015 5:44 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all][third-party][ci] Announcing CI Watch - 
Third-party CI monitoring tool

On 08/24/2015 07:59 PM, Skyler Berg wrote:
 Hi all,
 
 I am pleased to announce CI Watch [1], a CI monitoring tool developed 
 at Tintri. For each OpenStack project with third-party CI's, CI Watch 
 shows the status of all CI systems for all recent patch sets on a 
 single dashboard.
 
 CI maintainers can use this tool to pinpoint when errors began and to 
 find other CI's affected by the similar issues. Core team members can 
 find which vendor CI systems are failing and determine when breaking 
 changes hit their projects. The project dashboards provide access to 
 all relevant logs and reviews, simplifying the process of 
 investigating failures.
 
 CI Watch should also create more transparency within the third-party 
 CI ecosystem. The health of all CI's is now visible to everyone in the 
 community. We hope that by giving everyone this visibility we will 
 make it easier for anyone to find and address issues on CI systems.
 
 Any feedback would be appreciated. We plan to open source this project 
 soon and welcome contributions from anyone interested. For the moment, 
 any bugs, concerns, or ideas can be sent to openstack-...@tintri.com.
 
 [1] ci-watch.tintri.com
 
 Best,
 Skyler Berg
 
 __
  OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: 
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
Hi Skyler:

Thanks for your interest in participating in the third party segment of the 
openstack community.

We have a number of people working on dashboards for ci systems. We are working 
on having infra host one: https://review.openstack.org/#/c/194437/

which is a tool currently hosted by one of our ci operators, Patrick East, 
which is open source.

Can I suggest you attend a third party meeting and perhaps meet some of the 
other operators and collaborate with them?

We don't have any lack of people starting tools what we lack is a tool which 
will be maintained.

Thanks for your interest Skyler,
Anita.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

2015-08-25 Thread Asselin, Ramy
Looks good to me. Thanks!
Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 9:07 PM
To: Asselin, Ramy ramy.asse...@hp.com; 'OpenStack Development Mailing List 
(not for usage questions)' openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Hi Ramy:
I already fixed this important problem. Thanks.
Does our CI system have any missed configuration or problem?
Console log:
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/console.html
CI Review result:
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/logs/
Many thanks.


From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Tuesday, August 25, 2015 10:54 AM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com; 
'OpenStack Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Other than that, everything looks fine to me. But that is important to fix.

Thanks,
Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 6:46 PM
To: Asselin, Ramy; 'OpenStack Development Mailing List (not for usage 
questions)'
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
We use apache proxy pass option to redirect the public link to my 
internal CI server. Maybe I missed some configure? I will try to find solution 
for it. But it should affect the my OpenStack third-party CI system.
Does our CI system ready to re-enable account?


From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Tuesday, August 25, 2015 9:14 AM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com; 
'OpenStack Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Rick,

It's strange, I can navigate using the link you provided, but not via the 
parent Directory link.

This is what it links to, which is missing the prophetstor_ci portion:
http://download.prophetstor.com/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/

Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 5:59 PM
To: Asselin, Ramy ramy.asse...@hp.commailto:ramy.asse...@hp.com; 'OpenStack 
Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
My console file is console.html as below:

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/console.html


http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Monday, August 24, 2015 11:03 PM
To: 'OpenStack Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Cc: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Great.

Somehow you lost your console.log file. Or did I miss it?

Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 2:00 AM
To: Asselin, Ramy; 'OpenStack Development Mailing List (not for usage 
questions)'
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
I competed to change zuul.conf zuul_url to be my zuul server 
zuul.rjenkins.prophetstor.com.

2015-08-24 16:21:48.349 | + git_fetch_at_ref openstack/cinder 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:48.350 | + local project=openstack/cinder
2015-08-24 16:21:48.351 | + local 
ref=refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:48.352 | + '[' 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b '!=' '' ']'
2015-08-24 16:21:48.353 | + git fetch 
http://zuul.rjenkins.prophetstor.com/p/openstack/cinder 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:49.264 | From 
http://zuul.rjenkins.prophetstor.com/p/openstack/cinder
2015-08-24 16:21:49.265 |  * branch
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b - FETCH_HEAD

ProphetStor CI review result:

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/


From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Saturday, August 22, 2015 6:40 AM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com; 
OpenStack Development Mailing List (not for usage questions) 
openstack-dev

Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

2015-08-25 Thread Asselin, Ramy
I suggest you ask Mike Perez on irc: thingee in #openstack-cinder.
I believe it's his decision since he's the cinder PTL.
He'll then notify the infra team to request your account be reenabled.

Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Tuesday, August 25, 2015 6:01 PM
To: Asselin, Ramy; 'OpenStack Development Mailing List (not for usage 
questions)'
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
Now, If all is fine, Can you help me how can I re-enable my CI gerrit 
account?


From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Wednesday, August 26, 2015 12:43 AM
To: 'OpenStack Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Cc: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Looks good to me. Thanks!
Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 9:07 PM
To: Asselin, Ramy ramy.asse...@hp.commailto:ramy.asse...@hp.com; 'OpenStack 
Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Hi Ramy:
I already fixed this important problem. Thanks.
Does our CI system have any missed configuration or problem?
Console log:
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/console.html
CI Review result:
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/logs/
Many thanks.


From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Tuesday, August 25, 2015 10:54 AM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com; 
'OpenStack Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Other than that, everything looks fine to me. But that is important to fix.

Thanks,
Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 6:46 PM
To: Asselin, Ramy; 'OpenStack Development Mailing List (not for usage 
questions)'
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
We use apache proxy pass option to redirect the public link to my 
internal CI server. Maybe I missed some configure? I will try to find solution 
for it. But it should affect the my OpenStack third-party CI system.
Does our CI system ready to re-enable account?


From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Tuesday, August 25, 2015 9:14 AM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com; 
'OpenStack Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Rick,

It's strange, I can navigate using the link you provided, but not via the 
parent Directory link.

This is what it links to, which is missing the prophetstor_ci portion:
http://download.prophetstor.com/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/

Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 5:59 PM
To: Asselin, Ramy ramy.asse...@hp.commailto:ramy.asse...@hp.com; 'OpenStack 
Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
My console file is console.html as below:

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/console.html


http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Monday, August 24, 2015 11:03 PM
To: 'OpenStack Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Cc: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Great.

Somehow you lost your console.log file. Or did I miss it?

Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 2:00 AM
To: Asselin, Ramy; 'OpenStack Development Mailing List (not for usage 
questions)'
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
I competed to change zuul.conf zuul_url to be my zuul server 
zuul.rjenkins.prophetstor.com.

2015-08-24 16:21:48.349 | + git_fetch_at_ref openstack/cinder 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16

Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

2015-08-24 Thread Asselin, Ramy
Great.

Somehow you lost your console.log file. Or did I miss it?

Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 2:00 AM
To: Asselin, Ramy; 'OpenStack Development Mailing List (not for usage 
questions)'
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
I competed to change zuul.conf zuul_url to be my zuul server 
zuul.rjenkins.prophetstor.com.

2015-08-24 16:21:48.349 | + git_fetch_at_ref openstack/cinder 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:48.350 | + local project=openstack/cinder
2015-08-24 16:21:48.351 | + local 
ref=refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:48.352 | + '[' 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b '!=' '' ']'
2015-08-24 16:21:48.353 | + git fetch 
http://zuul.rjenkins.prophetstor.com/p/openstack/cinder 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:49.264 | From 
http://zuul.rjenkins.prophetstor.com/p/openstack/cinder
2015-08-24 16:21:49.265 |  * branch
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b - FETCH_HEAD

ProphetStor CI review result:

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/


From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Saturday, August 22, 2015 6:40 AM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com; 
OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Rick,

Let's keep this on the list so that others can benefit or chip in ideas.
If you cannot subscribe to the list, ask the folks on freenode irc in 
#openstack-infra.

You should set in zuul.conf the [merger] zuul_url to your local zuul's url. [1]
E.g.
[merger]
zuul_url=http://your_ip_or fqdn/p/

Please use export GIT_BASE=https://git.openstack.org. This will reduce the load 
on OpenStack's gerrit server and point you to a more stable GIT farm that can 
better handle the CI load. This will help your CI's success rate (by avoiding 
timeouts and intermittent errors) and reduce your ci test setup time.

Ramy

[1] http://docs.openstack.org/infra/zuul/zuul.html#merger





From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Thursday, August 20, 2015 8:53 PM
To: Asselin, Ramy ramy.asse...@hp.commailto:ramy.asse...@hp.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Hi Ramy:
Can you provide detail information how to solve it?
Yes, I use zuul. My zuul.conf use default zuul_url value.
I thought I use build shell script to pull this patch. I had add 
export GIT_BASE=https://review.openstack.org/p; in the build shell script.
Does it wrong?

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Thursday, August 20, 2015 11:12 PM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Hi Rick,

Thank you for adding this: Triggered by: https://review.openstack.org/203895 
patchset 3
Where do you pull down this patch in the log files?
Normally it gets pulled down during the setup-workspace script, but here you're 
referencing openstack's servers which is not correct. [1]
Are you using zuul? If so, your zuul url should be there.
If not, there should be some other place in your scripts that pull down the 
patch.

Ramy

[1] 
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5117/logs/devstack-gate-setup-workspace-new.txt.gz#_2015-08-20_12_03_24_813

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Thursday, August 20, 2015 6:27 AM
To: Asselin, Ramy
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account


HI Ramy:

Sorry, I did not make sure the mail sent, because I did not receive my 
mail from openstack dev mail list group. So I direct send mail to your 
private mail account.

Thank you for your guidance. I followed your suggestion.

Please reference below link:


http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5117/console.html


my gerrit account:  prophetstor-ci

  gerrit account email:
prophetstor...@prophetstor.commailto:prophetstor...@prophetstor.com



-Original Message-

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]

Sent: Wednesday, August 19, 2015 10:10 PM

To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org; 
'Mike Perez' thin...@gmail.commailto:thin...@gmail.com

Subject: Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account



Hi Rick,



Huge improvement. Log server is looking great! Thanks!



Next question

Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

2015-08-24 Thread Asselin, Ramy
Rick,

It's strange, I can navigate using the link you provided, but not via the 
parent Directory link.

This is what it links to, which is missing the prophetstor_ci portion:
http://download.prophetstor.com/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/

Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 5:59 PM
To: Asselin, Ramy ramy.asse...@hp.com; 'OpenStack Development Mailing List 
(not for usage questions)' openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
My console file is console.html as below:

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/console.html


http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Monday, August 24, 2015 11:03 PM
To: 'OpenStack Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Cc: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Great.

Somehow you lost your console.log file. Or did I miss it?

Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 2:00 AM
To: Asselin, Ramy; 'OpenStack Development Mailing List (not for usage 
questions)'
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
I competed to change zuul.conf zuul_url to be my zuul server 
zuul.rjenkins.prophetstor.com.

2015-08-24 16:21:48.349 | + git_fetch_at_ref openstack/cinder 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:48.350 | + local project=openstack/cinder
2015-08-24 16:21:48.351 | + local 
ref=refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:48.352 | + '[' 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b '!=' '' ']'
2015-08-24 16:21:48.353 | + git fetch 
http://zuul.rjenkins.prophetstor.com/p/openstack/cinder 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:49.264 | From 
http://zuul.rjenkins.prophetstor.com/p/openstack/cinder
2015-08-24 16:21:49.265 |  * branch
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b - FETCH_HEAD

ProphetStor CI review result:

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/


From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Saturday, August 22, 2015 6:40 AM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com; 
OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Rick,

Let's keep this on the list so that others can benefit or chip in ideas.
If you cannot subscribe to the list, ask the folks on freenode irc in 
#openstack-infra.

You should set in zuul.conf the [merger] zuul_url to your local zuul's url. [1]
E.g.
[merger]
zuul_url=http://your_ip_or fqdn/p/

Please use export GIT_BASE=https://git.openstack.org. This will reduce the load 
on OpenStack's gerrit server and point you to a more stable GIT farm that can 
better handle the CI load. This will help your CI's success rate (by avoiding 
timeouts and intermittent errors) and reduce your ci test setup time.

Ramy

[1] http://docs.openstack.org/infra/zuul/zuul.html#merger





From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Thursday, August 20, 2015 8:53 PM
To: Asselin, Ramy ramy.asse...@hp.commailto:ramy.asse...@hp.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Hi Ramy:
Can you provide detail information how to solve it?
Yes, I use zuul. My zuul.conf use default zuul_url value.
I thought I use build shell script to pull this patch. I had add 
export GIT_BASE=https://review.openstack.org/p; in the build shell script.
Does it wrong?

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Thursday, August 20, 2015 11:12 PM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Hi Rick,

Thank you for adding this: Triggered by: https://review.openstack.org/203895 
patchset 3
Where do you pull down this patch in the log files?
Normally it gets pulled down during the setup-workspace script, but here you're 
referencing openstack's servers which is not correct. [1]
Are you using zuul? If so, your zuul url should be there.
If not, there should be some other place in your scripts that pull down the 
patch.

Ramy

[1] 
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5117/logs/devstack-gate-setup-workspace-new.txt.gz#_2015-08-20_12_03_24_813

From

Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

2015-08-24 Thread Asselin, Ramy
Other than that, everything looks fine to me. But that is important to fix.

Thanks,
Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 6:46 PM
To: Asselin, Ramy; 'OpenStack Development Mailing List (not for usage 
questions)'
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
We use apache proxy pass option to redirect the public link to my 
internal CI server. Maybe I missed some configure? I will try to find solution 
for it. But it should affect the my OpenStack third-party CI system.
Does our CI system ready to re-enable account?


From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Tuesday, August 25, 2015 9:14 AM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com; 
'OpenStack Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Rick,

It's strange, I can navigate using the link you provided, but not via the 
parent Directory link.

This is what it links to, which is missing the prophetstor_ci portion:
http://download.prophetstor.com/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/

Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 5:59 PM
To: Asselin, Ramy ramy.asse...@hp.commailto:ramy.asse...@hp.com; 'OpenStack 
Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
My console file is console.html as below:

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/console.html


http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Monday, August 24, 2015 11:03 PM
To: 'OpenStack Development Mailing List (not for usage questions)' 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Cc: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Great.

Somehow you lost your console.log file. Or did I miss it?

Ramy

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 24, 2015 2:00 AM
To: Asselin, Ramy; 'OpenStack Development Mailing List (not for usage 
questions)'
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
I competed to change zuul.conf zuul_url to be my zuul server 
zuul.rjenkins.prophetstor.com.

2015-08-24 16:21:48.349 | + git_fetch_at_ref openstack/cinder 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:48.350 | + local project=openstack/cinder
2015-08-24 16:21:48.351 | + local 
ref=refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:48.352 | + '[' 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b '!=' '' ']'
2015-08-24 16:21:48.353 | + git fetch 
http://zuul.rjenkins.prophetstor.com/p/openstack/cinder 
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b
2015-08-24 16:21:49.264 | From 
http://zuul.rjenkins.prophetstor.com/p/openstack/cinder
2015-08-24 16:21:49.265 |  * branch
refs/zuul/master/Z1a7ecbae61cc4aa090d02620bef4076b - FETCH_HEAD

ProphetStor CI review result:

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5141/


From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Saturday, August 22, 2015 6:40 AM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com; 
OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Rick,

Let's keep this on the list so that others can benefit or chip in ideas.
If you cannot subscribe to the list, ask the folks on freenode irc in 
#openstack-infra.

You should set in zuul.conf the [merger] zuul_url to your local zuul's url. [1]
E.g.
[merger]
zuul_url=http://your_ip_or fqdn/p/

Please use export GIT_BASE=https://git.openstack.org. This will reduce the load 
on OpenStack's gerrit server and point you to a more stable GIT farm that can 
better handle the CI load. This will help your CI's success rate (by avoiding 
timeouts and intermittent errors) and reduce your ci test setup time.

Ramy

[1] http://docs.openstack.org/infra/zuul/zuul.html#merger





From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Thursday, August 20, 2015 8:53 PM
To: Asselin, Ramy ramy.asse...@hp.commailto:ramy.asse...@hp.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Hi Ramy:
Can you provide detail information how to solve it?
Yes, I use zuul. My

Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

2015-08-21 Thread Asselin, Ramy
HI Rick,

Let's keep this on the list so that others can benefit or chip in ideas.
If you cannot subscribe to the list, ask the folks on freenode irc in 
#openstack-infra.

You should set in zuul.conf the [merger] zuul_url to your local zuul's url. [1]
E.g.
[merger]
zuul_url=http://your_ip_or fqdn/p/

Please use export GIT_BASE=https://git.openstack.org. This will reduce the load 
on OpenStack's gerrit server and point you to a more stable GIT farm that can 
better handle the CI load. This will help your CI's success rate (by avoiding 
timeouts and intermittent errors) and reduce your ci test setup time.

Ramy

[1] http://docs.openstack.org/infra/zuul/zuul.html#merger





From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Thursday, August 20, 2015 8:53 PM
To: Asselin, Ramy ramy.asse...@hp.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Hi Ramy:
Can you provide detail information how to solve it?
Yes, I use zuul. My zuul.conf use default zuul_url value.
I thought I use build shell script to pull this patch. I had add 
export GIT_BASE=https://review.openstack.org/p; in the build shell script.
Does it wrong?

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Thursday, August 20, 2015 11:12 PM
To: Rick Chen rick.c...@prophetstor.commailto:rick.c...@prophetstor.com
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Hi Rick,

Thank you for adding this: Triggered by: https://review.openstack.org/203895 
patchset 3
Where do you pull down this patch in the log files?
Normally it gets pulled down during the setup-workspace script, but here you're 
referencing openstack's servers which is not correct. [1]
Are you using zuul? If so, your zuul url should be there.
If not, there should be some other place in your scripts that pull down the 
patch.

Ramy

[1] 
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5117/logs/devstack-gate-setup-workspace-new.txt.gz#_2015-08-20_12_03_24_813

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Thursday, August 20, 2015 6:27 AM
To: Asselin, Ramy
Subject: RE: [openstack-dev] [cinder] [third-party] ProphetStor CI account


HI Ramy:

Sorry, I did not make sure the mail sent, because I did not receive my 
mail from openstack dev mail list group. So I direct send mail to your 
private mail account.

Thank you for your guidance. I followed your suggestion.

Please reference below link:


http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5117/console.html


my gerrit account:  prophetstor-ci

  gerrit account email:
prophetstor...@prophetstor.commailto:prophetstor...@prophetstor.com



-Original Message-

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]

Sent: Wednesday, August 19, 2015 10:10 PM

To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org; 
'Mike Perez' thin...@gmail.commailto:thin...@gmail.com

Subject: Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account



Hi Rick,



Huge improvement. Log server is looking great! Thanks!



Next question is what (cinder) patch set is that job running?

It seems to be cinder master [1].

Is that intended? That's fine to validate general functionality, but eventually 
it needs to run the actual cinder patch set under test.



It's helpful to include a link to the patch that invoked the job at the top of 
the console.log file, e.g. [2].



Ramy



[1] 
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5111/logs/devstack-gate-setup-workspace-new.txt.gz#_2015-08-19_18_27_38_953

[2] 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L93



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [openstack-infra][third-party][CI][nodepool]Using Nodepool for creating slaves.

2015-08-21 Thread Asselin, Ramy
Hi Abhi,

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

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

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

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

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

Ramy

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

Also adding the following:

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

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

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

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

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

--
[https://docs.google.com/uc?export=downloadid=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com



--
[https://docs.google.com/uc?export=downloadid=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [keystone] Can`t find Project ID

2015-08-21 Thread Asselin, Ramy
Hi Steve, Xiexs,

Actually this issue hit us on Tuesday afternoon.
Root cause is not known still, but the workaround was an update to nodepool to 
allow the project-name setting as stated below.
I updated the sample nodepool.yaml.erb as well. See this post I sent for the 
full details of the issue [1]

It would still be nice to know what the root cause is.

Thanks,
Ramy
[1] http://lists.openstack.org/pipermail/openstack-dev/2015-August/072556.html

P.S. Xiexs, in the future, it’s helpful to include the [third-party] and/or 
[infra] tags as well to get better attention since this issue impacts nodepool 
users, which is used by both of these teams.

From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com]
Sent: Thursday, August 20, 2015 11:30 PM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [keystone] Can`t find Project ID

Hi Steve,
   Thanks for your reply.

It`s a stupid mistake.
I have made an invalid configuration for the provider`s project-id in the 
nodepool.yaml as follows:
{ project-id: 'admin' }
But the correct setting should be:
{ Project-name: 'admin'}  or { project-id: '%= id of project admin %' }

To be honest, I was misled by the  sample file 
os-ext-testing-data/etc/nodepool/nodepool.yaml.erb,
in which the project-id is also configured with admin.


Xiexs

From: Steve Martinelli [mailto:steve...@ca.ibm.com]
Sent: Friday, August 21, 2015 1:48 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [keystone] Can`t find Project ID


For the rest of the mailing list, how was it resolved? :)

Thanks,

Steve Martinelli
OpenStack Keystone Core

[Inactive hide details for Xie, Xianshan ---2015/08/21 01:43:35 AM---Hi all,  
  This issue has already been resolved.]Xie, Xianshan ---2015/08/21 01:43:35 
AM---Hi all, This issue has already been resolved.

From: Xie, Xianshan xi...@cn.fujitsu.commailto:xi...@cn.fujitsu.com
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: 2015/08/21 01:43 AM
Subject: Re: [openstack-dev] [keystone] Can`t find Project ID





Hi all,
This issue has already been resolved.
Thanks.


Xiexs

From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com]
Sent: Friday, August 21, 2015 9:51 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [keystone] Can`t find Project ID

Hi, all,

I got following error message while running nodepoold:


2015-08-21 20:18:00,336 ERROR nodepool.NodePool: Exception cleaning up leaked 
nodes
Traceback (most recent call last):
File /home/nodepool/nodepool/nodepool.py, line 2399, in periodicCleanup
self.cleanupLeakedInstances()
File /home/nodepool/nodepool/nodepool.py, line 2410, in cleanupLeakedInstances
servers = manager.listServers()
File /home/nodepool/nodepool/provider_manager.py, line 570, in listServers
self._servers = self.submitTask(ListServersTask())
File /home/nodepool/nodepool/task_manager.py, line 119, in submitTask
return task.wait()
File /home/nodepool/nodepool/task_manager.py, line 57, in run
self.done(self.main(client))
File /home/nodepool/nodepool/provider_manager.py, line 136, in main
servers = client.nova_client.servers.list()
File /usr/local/lib/python2.7/dist-packages/shade/__init__.py, line 318, in 
nova_client
self.get_session_endpoint('compute')
File /usr/local/lib/python2.7/dist-packages/shade/__init__.py, line 811, in 
get_session_endpoint
Error getting %s endpoint: %s % (service_key, str(e)))
OpenStackCloudException: Error getting compute endpoint: Project ID not found: 
admin (Disable debug mode to suppress these details.) (HTTP 401) (Request-ID: 
req-fb986bff-3cad-48e1-9da9-915ac9ef5927)
---

And in my case, the output info with cli listed as follows:
$ openstack service list
| ID | Name | Type |
+--+--++
| 213a7ba8f0564523a3d2769f77621fde | nova | compute |

$ openstack project list
+--++
| ID | Name |
+--++
| 0a765fdfa79a438aae56202bdd5824e2 | admin |

$ keystone endpoint-list
+--+---+-+-+-+--+
| id | region | publicurl | internalurl | adminurl | service_id |
+--+---+-+-+-+--+
| d89b009e81f04a17a26fd07ffbf83efb | regionOne | 
http://controller:8774/v2/%(tenant_id)shttp://controller:8774/v2/%25(tenant_id)s
 | 
http://controller:8774/v2/%(tenant_id)shttp://controller:8774/v2/%25(tenant_id)s
 | 

Re: [openstack-dev] [CI] Cannot get compute endpoint when running nodepool.

2015-08-21 Thread Asselin, Ramy
Hi Tang,

Sorry I did not see this post. I started a thread here to explain the issue: [1]

Ramy

[1] http://lists.openstack.org/pipermail/openstack-dev/2015-August/072556.html

From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Thursday, August 20, 2015 7:13 PM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.org; Asselin, Ramy ramy.asse...@hp.com; 
Abhishek Shrivastava abhis...@cloudbyte.com; Xie, Xianshan/谢 贤山 
xi...@cn.fujitsu.com
Subject: [CI] Cannot get compute endpoint when running nodepool.

Hi, all,

I got following error message while running nodepoold with nodepoold -d  $ 
DAEMON_ARGS


2015-08-21 20:18:00,336 ERROR nodepool.NodePool: Exception cleaning up leaked 
nodes
Traceback (most recent call last):
  File /home/nodepool/nodepool/nodepool.py, line 2399, in periodicCleanup
self.cleanupLeakedInstances()
  File /home/nodepool/nodepool/nodepool.py, line 2410, in 
cleanupLeakedInstances
servers = manager.listServers()
  File /home/nodepool/nodepool/provider_manager.py, line 570, in listServers
self._servers = self.submitTask(ListServersTask())
  File /home/nodepool/nodepool/task_manager.py, line 119, in submitTask
return task.wait()
  File /home/nodepool/nodepool/task_manager.py, line 57, in run
self.done(self.main(client))
  File /home/nodepool/nodepool/provider_manager.py, line 136, in main
servers = client.nova_client.servers.list()
  File /usr/local/lib/python2.7/dist-packages/shade/__init__.py, line 318, in 
nova_client
self.get_session_endpoint('compute')
  File /usr/local/lib/python2.7/dist-packages/shade/__init__.py, line 811, in 
get_session_endpoint
Error getting %s endpoint: %s % (service_key, str(e)))
OpenStackCloudException: Error getting compute endpoint: Project ID not found: 
admin (Disable debug mode to suppress these details.) (HTTP 401) (Request-ID: 
req-fb986bff-3cad-48e1-9da9-915ac9ef5927)
---

And in my case, the output info with cli listed as follows:
$ openstack service list
| ID   | Name | Type   |
+--+--++
| 213a7ba8f0564523a3d2769f77621fde | nova | compute|

$ openstack project list
+--++
| ID   | Name   |
+--++
| 0a765fdfa79a438aae56202bdd5824e2 | admin  |

$ keystone endpoint-list
+--+---+-+-+-+--+
|id|   region  |publicurl   
 |   internalurl   | adminurl   
 |service_id|
+--+---+-+-+-+--+
| d89b009e81f04a17a26fd07ffbf83efb | regionOne | 
http://controller:8774/v2/%(tenant_id)shttp://controller:8774/v2/%25%28tenant_id%29s
 | 
http://controller:8774/v2/%(tenant_id)shttp://controller:8774/v2/%25%28tenant_id%29s
 | 
http://controller:8774/v2/%(tenant_id)shttp://controller:8774/v2/%25%28tenant_id%29s
 | 213a7ba8f0564523a3d2769f77621fde |
+--+---+-+-+-+--+


Have you ever seen this error? And could you give me any advice to solve it?
Thanks in advance.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [infra][third-party] Some unknown updates broke nodepool connection to provider. Read for solution.

2015-08-20 Thread Asselin, Ramy
All,

Recently, some external dependency broke nodepool's ability to launch VMs on an 
openstack provider.
If you haven't run into this yet, it's probably because you haven't restarted 
nodepool.
When you do, you might get an error similar to [1]

I couldn't find the issue, but regardless, there's a fix to nodepool that's 
been merged  [2].
However, you do need to update your nodepool.yaml configurations to use 
'project-name' instead of 'project-id'.
Here's an example [3]
I don't know the solution if you're using cloud.yaml, but it should be similar.

Ramy
irc: asselin


[1] 
http://logs.openstack.org/54/211754/4/check/gate-dsvm-nodepool-nv/958471b/logs/screen-nodepool.txt.gz#_2015-08-18_22_59_57_227
[2] https://review.openstack.org/#/c/214399/2
[3] 
https://github.com/rasselin/os-ext-testing-data/commit/00dcce696c7fb8d3b5e55e1984ebb2bff9edfcb2

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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

2015-08-19 Thread Asselin, Ramy
Hi Xies, Abhi,

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

Ramy


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

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

Hope this might help you.


Xiexs


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

Also adding the following:

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

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

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

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

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

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



--
[Image removed by sender.]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

2015-08-19 Thread Asselin, Ramy
Hi Rick,

Huge improvement. Log server is looking great! Thanks!

Next question is what (cinder) patch set is that job running?
It seems to be cinder master [1]. 
Is that intended? That's fine to validate general functionality, but eventually 
it needs to run the actual cinder patch set under test.

It's helpful to include a link to the patch that invoked the job at the top of 
the console.log file, e.g. [2].

Ramy

[1] 
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5111/logs/devstack-gate-setup-workspace-new.txt.gz#_2015-08-19_18_27_38_953
[2] 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L93


-Original Message-
From: Rick Chen [mailto:rick.c...@prophetstor.com] 
Sent: Wednesday, August 19, 2015 5:23 AM
To: 'OpenStack Development Mailing List (not for usage questions)'; 'Mike Perez'
Subject: Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy:
Many thanks, I completed to install log-server.

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds
vm-tempest-cinder-ci/5111/logs/

So, can you help me to re-enable my gerrit account?


-Original Message-
From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Tuesday, August 18, 2015 11:28 PM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.org; 'Mike Perez' thin...@gmail.com
Subject: Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Rick,

These files are missing newlines i.e. unreadable for me: [1] [2] [3]

Out of curiosity, any particular reason you don't set up a log server like 
OpenStack Infra?
I have a script to do that [4], which uses the upstream common solution [5]

Ramy

[1]
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds
vm-tempest-cinder-ci/5100/logs/devstacklog.txt.gz
[2]
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds
vm-tempest-cinder-ci/5100/logs/etc/cinder/cinder.conf.txt.gz
[3]
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds
vm-tempest-cinder-ci/5100/logs/screen-c-vol.txt.gz
[4]
https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_log_se
rver.sh
]5]
http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/manife
sts/logserver.pp



-Original Message-
From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, August 17, 2015 8:22 AM
To: 'Mike Perez'
Cc: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Mike:
I completed to refine our CI configuration to follow Ramy's comments. 
Does any missed or other attention I need respect?

[1] Add export DEVSTACK_GATE_TEMPEST_REGEX=volume to verify all 
cinder volume testing.
[2] Add each service configuration in the log.

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds
vm-tempest-cinder-ci/5100/logs/etc/
[3] Add email alert when the devstack build failed to instead of you 
notify to me.
[4] Integrate VMware snapshot revert feature in the Jenkins master to 
clean CI slave machine OS environment that avoid the devstack building failed 
due to previous devstack garbage configuration.
[5] Latest CI result for you reference.

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds
vm-tempest-cinder-ci/5100/logs/
http://download.prophetstor.com/prophetstor_ci/

[6] Logs need to be browsable online.
Add Rewrite module and rule in the apache configuration.

my gerrit account:  prophetstor-ci
   gerrit account email:prophetstor...@prophetstor.com

Many thanks.

-Original Message-
From: Mike Perez [mailto:thin...@gmail.com]
Sent: Friday, August 14, 2015 11:41 PM
To: Rick Chen rick.c...@prophetstor.com
Cc: openstack-dev@lists.openstack.org
Subject: Re: [cinder] [third-party]RE: [OpenStack-Infra] ProphetStor CI account

On 09:44 Aug 14, Rick Chen wrote:
 HI Mike:
   Sorry again, I already add email alert agent in our CI Jenkins
server 
 to capture each failed build result.
   [1] -
 http://lists.openstack.org/pipermail/third-party-announce/2015-June/00
 0192.h
 tml
   [2] -
 http://lists.openstack.org/pipermail/third-party-announce/2015-June/00
 0193.h
 tml
   Solution 1: Our Jenkins client machine is vmware machine, I already 
 add snapshot revert script in the Jenkins Job script. Each git review job
 trigger the client will revert to  clean environment
 to solve this problem.
   Solution 2: I don't know whiched changed to make keystone unable to

 import pastedeploy. So I try to uninstall python-pastedeploy package 
 in the local to solve some
issue about unable

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

2015-08-18 Thread Asselin, Ramy
HI Abhi,

There are two ways to build images. The preferred way is to use Disk Image 
Builder (DIB).
These images are built on the same VM that nodepool is run.
When you start nodepool, it will automatically do this for you.
The instructions explain how to do it ‘manually’ which is helpful for debugging 
issues, especially the first time you setup.

Ramy

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Monday, August 17, 2015 11:32 PM
To: Remo Mattei
Cc: OpenStack Development Mailing List (not for usage questions); 
openstack-in...@lists.openstack.org
Subject: Re: [OpenStack-Infra] [openstack-infra][third-paty][CI][nodepool]Using 
Nodepool for creating slaves.

Hi Remo,

I got the solution for creating images, but my question is do we need to create 
the images in CI master VM or some other VM?

On Tue, Aug 18, 2015 at 11:32 AM, Remo Mattei 
r...@italy1.commailto:r...@italy1.com wrote:
There is a webex scheduled for this topic you want to check it out go to 
Solinea.comhttp://solinea.com

Remo

Inviato da iPhone

Il giorno 18 ago 2015, alle ore 07:41, Abhishek Shrivastava 
abhis...@cloudbyte.commailto:abhis...@cloudbyte.com ha scritto:
Hi Folks,

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

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

--
[Image removed by sender.]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com
!DSPAM:1,55d2c5ef145828302144768!
___
OpenStack-Infra mailing list
openstack-in...@lists.openstack.orgmailto:openstack-in...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


!DSPAM:1,55d2c5ef145828302144768!



--
[Image removed by sender.]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

2015-08-18 Thread Asselin, Ramy
Rick,

These files are missing newlines i.e. unreadable for me: [1] [2] [3]

Out of curiosity, any particular reason you don't set up a log server like 
OpenStack Infra?
I have a script to do that [4], which uses the upstream common solution [5]

Ramy

[1] 
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5100/logs/devstacklog.txt.gz
[2] 
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5100/logs/etc/cinder/cinder.conf.txt.gz
[3] 
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-dsvm-tempest-cinder-ci/5100/logs/screen-c-vol.txt.gz
[4] 
https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_log_server.sh
]5] 
http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/manifests/logserver.pp



-Original Message-
From: Rick Chen [mailto:rick.c...@prophetstor.com] 
Sent: Monday, August 17, 2015 8:22 AM
To: 'Mike Perez'
Cc: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Mike:
I completed to refine our CI configuration to follow Ramy's comments. 
Does any missed or other attention I need respect?

[1] Add export DEVSTACK_GATE_TEMPEST_REGEX=volume to verify all 
cinder volume testing.
[2] Add each service configuration in the log.

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds
vm-tempest-cinder-ci/5100/logs/etc/
[3] Add email alert when the devstack build failed to instead of you 
notify to me.
[4] Integrate VMware snapshot revert feature in the Jenkins master to 
clean CI slave machine OS environment that avoid the devstack building failed 
due to previous devstack garbage configuration.
[5] Latest CI result for you reference.

http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds
vm-tempest-cinder-ci/5100/logs/
http://download.prophetstor.com/prophetstor_ci/

[6] Logs need to be browsable online.
Add Rewrite module and rule in the apache configuration.

my gerrit account:  prophetstor-ci
   gerrit account email:prophetstor...@prophetstor.com

Many thanks.

-Original Message-
From: Mike Perez [mailto:thin...@gmail.com]
Sent: Friday, August 14, 2015 11:41 PM
To: Rick Chen rick.c...@prophetstor.com
Cc: openstack-dev@lists.openstack.org
Subject: Re: [cinder] [third-party]RE: [OpenStack-Infra] ProphetStor CI account

On 09:44 Aug 14, Rick Chen wrote:
 HI Mike:
   Sorry again, I already add email alert agent in our CI Jenkins
server 
 to capture each failed build result.
   [1] -
 http://lists.openstack.org/pipermail/third-party-announce/2015-June/00
 0192.h
 tml
   [2] -
 http://lists.openstack.org/pipermail/third-party-announce/2015-June/00
 0193.h
 tml
   Solution 1: Our Jenkins client machine is vmware machine, I already 
 add snapshot revert script in the Jenkins Job script. Each git review job
 trigger the client will revert to  clean environment
 to solve this problem.
   Solution 2: I don't know whiched changed to make keystone unable to

 import pastedeploy. So I try to uninstall python-pastedeploy package 
 in the local to solve some
issue about unable to build devstack issue.
   Sorry again to disturb you.

Rick,

I looked at your CI results directory [1], but it looks like the last time this 
ran was on July 28th according to the last modified dates. This should be 
actively running even if you account is disabled from leaving comments, so I 
can verify from the logs things are running fine again.

In addition, see Ramy's comments with issues with the CI [2].

[1] - http://download.prophetstor.com/prophetstor_ci/?C=M;O=A
[2] -
http://lists.openstack.org/pipermail/openstack-infra/2015-August/003057.html

--
Mike Perez


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] ][third-party-ci]Running custom code before tests

2015-08-13 Thread Asselin, Ramy
This is what we do:
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L23

Ramy

From: Andrey Pavlov [mailto:andrey...@gmail.com]
Sent: Thursday, August 13, 2015 12:11 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] ][third-party-ci]Running custom code before tests

HI,
this file has changed since yesterday,
New link is 
https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/devstack-gate.yaml#L2146
or you can find these lines by yourself -
  export DEVSTACK_LOCAL_CONFIG=CINDER_ISCSI_HELPER=lioadm
  export DEVSTACK_LOCAL_CONFIG+=$'\n'CINDER_LVM_TYPE=thin
I mean that you can try to change CINDER_ISCSI_HELPER in devstack.

On Thu, Aug 13, 2015 at 9:47 AM, Eduard Matei 
eduard.ma...@cloudfounders.commailto:eduard.ma...@cloudfounders.com wrote:
Hi,

I think you pointed me to the wrong file, the devstack-gate yaml (and line 2201 
contains timestamps).
I need an example of how to configure tempest to use my driver.

I tried EXPORT in the jenkins job (before executing dsvm shell script) but 
looking at the tempest.txt (log) it shows that it still uses the defaults. How 
do i overwrite those defaults?

Thanks,

Eduard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Kind regards,
Andrey Pavlov.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [cinder] Brocade CI

2015-08-13 Thread Asselin, Ramy
Hi Nagendra,

Seems one of the issues is the format of the posted comments. The correct 
format is documented here [1]

Notice the format is not correct:
Incorrect: Brocade Openstack CI (non-voting) build SUCCESS logs at: 
http://144.49.208.28:8000/build_logs/2015-08-13_18-19-19/
Correct: * test-name-no-spaces http://link.to/result : [SUCCESS|FAILURE] some 
comment about the test

Ramy

[1] 
http://docs.openstack.org/infra/system-config/third_party.html#posting-result-to-gerrit

From: Nagendra Jaladanki [mailto:nagendra.jalada...@gmail.com]
Sent: Wednesday, August 12, 2015 4:37 PM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.org
Cc: brocade-openstack...@brocade.com
Subject: Re: [openstack-dev] [cinder] Brocade CI

Mike,

Thanks for your feedback and suggestions. I had send my response yesterday but 
looks like didn't get posted on the 
lists.openstack.orghttp://lists.openstack.org. Hence posting it here again.

We reviewed your comments and following issues were identified and some of them 
are fixed and some fix plans in progress:

1) Not posting success or failure
 The Brocade CI is a non-voting CI. The CI is posting the comment for build 
sucucess or failures. The report tool is not seeing these. We are working on 
correcting this.
2) Not posting a result link to view logs.
   We could not find any cases where CI is failed to post the link to logs from 
the generated report.  If you have any specific uses where it failed to post 
logs link, please share with us. But we did see that CI not posted the comment 
at all for some review patch sets. Root causing the issue why CI not posted the 
comment at all.
3) Not consistently doing runs.
   There were planned down times and CI not posted during those periods. We 
also observed that CI was not posting the failures in some cases where CI 
failed due non openstack issues. We corrected this. Now the CI should be 
posting the results for all patch sets either success or failure.
We are also doing the following:
- Enhance the message format to be inline with other CIs.
- Closely monitoring the incoming Jenkin's request vs out going builds and 
correcting if there are any issues.

Once again thanks for your feedback and suggestions. We will continue to post 
this list on the updates.

Thanks  Regards,

Nagendra Rao Jaladanki

Manager, Software Engineering Manageability Brocade

130 Holger Way, San Jose, CA 95134

On Sun, Aug 9, 2015 at 5:34 PM, Mike Perez 
thin...@gmail.commailto:thin...@gmail.com wrote:
People have asked me at the Cinder midcycle sprint to look at the Brocade CI
to:

1) Keep the zone manager driver in Liberty.
2) Consider approving additional specs that we're submitted before the
   deadline.

Here are the current problems with the last 100 runs [1]:

1) Not posting success or failure.
2) Not posting a result link to view logs.
3) Not consistently doing runs. If you compare with other CI's there are plenty
   missing in a day.

This CI does not follow the guidelines [2]. Please get help [3].

[1] - http://paste.openstack.org/show/412316/
[2] - 
http://docs.openstack.org/infra/system-config/third_party.html#requirements
[3] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Questions

--
Mike Perez

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [third-party-ci]Issue with running noop-check-communication

2015-08-06 Thread Asselin, Ramy
I added it very recently.

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Thursday, August 06, 2015 2:08 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [third-party-ci]Issue with running 
noop-check-communication


Thanks,
Indeed running on a slave did the trick.

Strange how i missed that part in the README.

--

Eduard Biceri Matei, Senior Software Developer

www.cloudfounders.comhttp://www.cloudfounders.com/

 | eduard.ma...@cloudfounders.commailto:eduard.ma...@cloudfounders.com






__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] How to use the log server in CI ?

2015-08-06 Thread Asselin, Ramy
Hi Tang,

First, I recommend you use os-loganalyze because it significantly increases the 
value of the log files by making them easier to consume.
I'm not sure what the issue you encountered is. The link you provide is to use 
swift, but that is the newer alternative to the old-fashion files on disk 
approach, and not a requirement.

That said, you'll find the rules in one of the files located here: 
/etc/apache2/sites-enabled/
It is created by this template [1]. As you see, there's not htmlify directory 
because it's an alias that invokes os-loganalyze.

Ramy

[1] 
http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/templates/logs.vhost.erb#n85



From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Thursday, August 06, 2015 5:07 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] How to use the log server in CI ?

Hi Joshua,

Thanks to reply.
On 08/06/2015 07:45 PM, Joshua Hesketh wrote:
Hi Tang,
For OpenStack's set up, os-loganalyze sits at /htmlify/ and is used to add 
markup and filter log lines when viewing in a browser.

On my box, I don't have a /htmlify/ directory, and I don't think I installed 
os-loganalyze at all.
But when I accessed to the log site, the URL was just modified, added /htmlify/.



For your own set up you don't need to use this and could simply serve anything 
straight off your disk. It should be safe to remove the apache matching rules 
in order to do so.

I'm sorry, how to remove the apache matching rules ? From where ?

Thanks. :)




Hope that helps.
Cheers,
Josh

On Thu, Aug 6, 2015 at 6:50 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:
Hi Abhishek,

After I setup a log server, if the request ends in .txt.gz, console.html or 
console.html.gz rewrite the url to prepend /htmlify/ .
But actually the log file is on my local machine.

Is this done by os-loganalyze ?  Is this included in install_log_server.sh ? (I 
don't think so.)
Could I disable it and access my log file locally ?

I found this URL for reference.
http://josh.people.rcbops.com/2014/10/openstack-infrastructure-swift-logs-and-performance/

Thanks. :)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [third-party-ci]Issue with running noop-check-communication

2015-08-05 Thread Asselin, Ramy
Hi Eduard,

There seems to be a bug regarding running jobs on master [1]. Try running it on 
a slave instead.

Ramy

[1] 
https://github.com/rasselin/os-ext-testing/blob/master/README.md#running-jobs-on-jenkins-master

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Wednesday, August 05, 2015 5:03 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party-ci]Issue with running 
noop-check-communication

Hi,

We're in the process of rebuilding the Jenkins CI for Cinder and i'm stuck at 
testing the noop job.
I've setup using the latest changes from os-ext-testing and os-ext-testing-data 
using project-config, jjb and dib and i have a jenkins running which has the 2 
jobs defined and i have 3 slaves attached (from a devstack - cloud provider).

Now when i make changes to sandbox (to test it) i see jobs being triggered but 
they hang in Jenkins:
pending—There are no nodes with the label ‘’http://10.100.128.3:8080/label/

I checked the job config and it shows Restrict where this project can be 
run/Label expression master / Slaves in label: 1 and i can trigger it 
manually and it shows Waiting for next available executor on master  - 
although there are 4 executors in Idle.

Any ideas?

Thanks,
--

Eduard Biceri Matei, Senior Software Developer

www.cloudfounders.comhttp://www.cloudfounders.com/

 | eduard.ma...@cloudfounders.commailto:eduard.ma...@cloudfounders.com







CloudFounders, The Private Cloud Software Company


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [CI]How to set proxy for nodepool

2015-08-05 Thread Asselin, Ramy
HI Xiexs,

“Also, I’ve found some of the infra project-config elements don’t work in my 
environment and aren’t needed as they’re specific to infra. For those, simply 
comment out the portions that don’t work. I didn’t notice any negative 
side-effects.”
This one you need to skip because you don’t have access to that server.

In fact, here are the ones that I skip in my setup:

etc/nodepool/elements/nodepool-base/install.d/90-venv-swift-logs:# skipped
etc/nodepool/elements/nodepool-base/install.d/99-install-zuul:# Skipped
etc/nodepool/elements/nodepool-base/finalise.d/99-unbound:# Skipped
etc/nodepool/elements/cache-devstack/install.d/99-cache-testrepository-db:# 
Skipped

The ’99-unbound’ may work in your setup. If not, you need to disable it here 
too:
etc/nodepool/elements/puppet/bin/prepare-node:  enable_unbound = false,

Ramy

From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com]
Sent: Wednesday, August 05, 2015 3:40 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI]How to set proxy for nodepool

Hi Ramy,
Thanks for your patience.
I have tried your suggestion, but it did not work for me.
According to the log, this element has already ran in the chroot before the pip 
commands are executed.
So, in theory, the pip command  would run behind this proxy, but the connection 
errors are still raised.
It`s weird.

Then  I tried to hard code the proxy with --proxy option into the pip command, 
it works.
Anyway, this is a merely temporary solution for this issue until I figure it 
out.

But, after that, I got a new error:
-
nodepool.image.build.dpc: + sudo env 
'PATH=/opt/git/subunit2sql-env/bin:/usr/lib64/ccache:/usr/lib/ccache:$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'
 /opt/git/subunit2sql-env/bin/python2 
/opt/nodepool-scripts/prepare_tempest_testrepository.py 
/opt/git/openstack/tempest
nodepool.image.build.dpc: sudo: unable to resolve host fnst01
nodepool.image.build.dpc: No handlers could be found for logger 
oslo_db.sqlalchemy.session
nodepool.image.build.dpc: Traceback (most recent call last):
nodepool.image.build.dpc: File 
/opt/nodepool-scripts/prepare_tempest_testrepository.py, line 50, in module
nodepool.image.build.dpc: main()
nodepool.image.build.dpc: File 
/opt/nodepool-scripts/prepare_tempest_testrepository.py, line 39, in main
nodepool.image.build.dpc: session = api.get_session()
nodepool.image.build.dpc: File 
/opt/git/subunit2sql-env/local/lib/python2.7/site-packages/subunit2sql/db/api.py,
 line 47, in get_session
nodepool.image.build.dpc: facade = _create_facade_lazily()
nodepool.image.build.dpc: File 
/opt/git/subunit2sql-env/local/lib/python2.7/site-packages/subunit2sql/db/api.py,
 line 37, in _create_facade_lazily
nodepool.image.build.dpc: **dict(CONF.database.iteritems()))
nodepool.image.build.dpc: File 
/opt/git/subunit2sql-env/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/session.py,
 line 822, in __init__
nodepool.image.build.dpc: **engine_kwargs)
nodepool.image.build.dpc: File 
/opt/git/subunit2sql-env/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/session.py,
 line 417, in create_engine
nodepool.image.build.dpc: test_conn = _test_connection(engine, max_retries, 
retry_interval)
nodepool.image.build.dpc: File 
/opt/git/subunit2sql-env/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/session.py,
 line 596, in _test_connection
nodepool.image.build.dpc: six.reraise(type(de_ref), de_ref)
nodepool.image.build.dpc: File string, line 2, in reraise
nodepool.image.build.dpc: oslo_db.exception.DBConnectionError: 
(pymysql.err.OperationalError) (2003, Can't connect to MySQL server on 
'logstash.openstack.org' ([Errno -5] No address associated with hostname))
-
I think it is also a proxy problem about remote access to the subunit2sql 
database.
And it should work with simpleproxy I think.
But I couldn`t find how to use simpleproxy to forward data for the subunit2sql 
db.
Could you please give me more hints?

Thanks again.

Xiexs

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Wednesday, August 05, 2015 6:00 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI]How to set proxy for nodepool

Hi Xiexs,

You might need to configure pip to use your proxy.

I added my own element here:

cache-devstack/install.d/98-setup-pip

Basically:

set -eux

mkdir -p /root/.pip/

cat EOF  /root/.pip/pip.conf
[global]
proxy = your proxy
EOF

cp -f /root/.pip/pip.conf /etc/

Ramy

From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com]
Sent: Tuesday, August 04, 2015 12:05 AM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [CI]How to set proxy for nodepool

Hi Ramy,
Thanks for your help.

I have already confirmed proxy setting again, and it works fine(no matter 
whether the NODEPOOL_ variables are declared

Re: [openstack-dev] [CI]How to set proxy for nodepool

2015-08-04 Thread Asselin, Ramy
Hi Xiexs,

You might need to configure pip to use your proxy.

I added my own element here:

cache-devstack/install.d/98-setup-pip

Basically:

set -eux

mkdir -p /root/.pip/

cat EOF  /root/.pip/pip.conf
[global]
proxy = your proxy
EOF

cp -f /root/.pip/pip.conf /etc/

Ramy

From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com]
Sent: Tuesday, August 04, 2015 12:05 AM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [CI]How to set proxy for nodepool

Hi Ramy,
Thanks for your help.

I have already confirmed proxy setting again, and it works fine(no matter 
whether the NODEPOOL_ variables are declared or not):

1)   not only in the host machine on which DIB run,

2)   but also in the first half part of DIB(before the DIB running chroot).

3)   furthmore, I ran the commands manually in the host env, they also 
works fine.

$ sudo -H virtualenv /usr/zuul-swift-logs-env

$ sudo -H /usr/zuul-swift-logs-env/bin/pip install python-magic argparse 
requests glob2

So, if I understood correctly, it seems obvious, that the proxy setting is 
missed when DIB goes into chroot env.
Thus, when DIB attempts to connect internet to download/install/update some 
materials to prepare the image within the chroot env, the error will be 
encountered.
In this case, DIB will run “pip install” in the chroot env zuul-swift-logs-env 
to install python-magic, argparse and so forth.

Actually, all NODEPOOL_ variables were already declared by the 
install_master.sh previously, and the proxy setting also derived from the host 
machine`s proxy setting.

Xiexs
From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Tuesday, August 04, 2015 12:54 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI]How to set proxy for nodepool

Hi Xiexs,

You are using disk image builder (DIB), so make sure your proxy is set 
correctly also without the NODEPOOL_ prefix.
Those NODEPOOL_ prefixed variables are what would be used when DIB is not used 
/ when the script approach is used with nova/glance (nodepool image-update). I 
don’t recommend using that if you can use DIB.

Also, I’ve found some of the infra project-config elements don’t work in my 
environment and aren’t needed as they’re specific to infra. For those, simply 
comment out the portions that don’t work. I didn’t notice any negative 
side-effects.

Ramy

From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com]
Sent: Monday, August 03, 2015 9:37 PM
To: openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [CI]How to set proxy for nodepool

Hi All,
When I ran “nodepool image-build image-name” to create a new image, I got 
this error message:
…
INFO nodepool.image.build.dpc: + sudo -H virtualenv /usr/zuul-swift-logs-env
INFO nodepool.image.build.dpc: sudo: unable to resolve host fnst01
INFO nodepool.image.build.dpc: + sudo -H /usr/zuul-swift-logs-env/bin/pip 
install python-magic argparse requests glob2
INFO nodepool.image.build.dpc: sudo: unable to resolve host fnst01
INFO nodepool.image.build.dpc: Collecting python-magic
INFO nodepool.image.build.dpc: Retrying (Retry(total=4, connect=None, 
read=None, redirect=None)) after connection broken by 
'ProtocolError('Connection aborted.', gaierror(-5, 'No address associated with 
hostname'))': /simple/python-magic/
INFO nodepool.image.build.dpc: Retrying (Retry(total=3, connect=None, 
read=None, redirect=None)) after connection broken by 
'ProtocolError('Connection aborted.', gaierror(-5, 'No address associated with 
hostname'))': /simple/python-magic/
…

And I exported the bash env when the script 
elements/nodepool-base/install.d/90-venv-swift-logs ran,
it seems that the nodepool proxy and dns has already been set:

declare -x NODEPOOL_HTTPS_PROXY=http://xx.xx.xx.xx:8080/  --valid proxy
declare -x NODEPOOL_HTTP_PROXY=http://xx.xx.xx.xx:8080/;
declare -x NODEPOOL_NO_PROXY=localhost,127.0.0.1
declare -x NODEPOOL_SCRIPTDIR=/etc/nodepool/scripts
declare -x NODEPOOL_STATIC_NAMESERVER=xx.xx.xx.xx
declare -x PS1=(zuul-swift-logs-env)
INFO nodepool.image.build.dpc: + cat /etc/resolv.conf
INFO nodepool.image.build.dpc: nameserver xx.xx.xx.xx   --valid dns

And I have tried to add element “local-config” into nodepool.yaml, but it does 
not work.

So, my questions are:

1)  These bash env will be passed into the virtualenv zuul-swift-logs-env 
after chroot, is it right?

2)  If not, how to configure the proxy for nodepool?

Many thanks to any suggestion.

Xiexs
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] How to use the log server in CI ?

2015-08-03 Thread Asselin, Ramy
BTW, I did update the documentation a bit to cover recent questions [1]. Let me 
know if I missed anything.

Thanks,
Ramy

[1] 
https://github.com/rasselin/os-ext-testing/commit/0d8e4234c226273392391df3693292af43b1d2be


From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Monday, August 03, 2015 6:14 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] How to use the log server in CI ?


On 08/04/2015 06:44 AM, Asselin, Ramy wrote:
Hi Tang,

Sorry the documentation on github is limited. I’ve been focusing on getting an 
upstream solution working, and that’s where it belongs and should be 
maintained. I will take a quick look and add some tips as discussed in this 
thread.
Of course if you have pull requests, I’m happy to merge them.

I did include publishers in the sample: 
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L73

Greate.

Thanks a lot. :)



Ramy
From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Friday, July 31, 2015 12:04 AM
To: Abhishek Shrivastava abhis...@cloudbyte.commailto:abhis...@cloudbyte.com
Cc: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] How to use the log server in CI ?

Hi Abhishek,

I found out what was wrong.

I didn't configure publisher in my jobs..
Sorry for the trouble.

But I do think the document on github is not suitable for any beginner.
So I think I will post some patches to provide more info for those who use this 
tool for the very first time
when I finish the work on my hand.

And about the nodepool you asked last time, I'm working on it.
But due to the proxy in my company, I  have to solve lots of trivial problems 
first.

Thanks.


On 07/31/2015 09:57 AM, Tang Chen wrote:
Hi Abhishek,


On 07/30/2015 04:54 PM, Abhishek Shrivastava wrote:
Hi Tang,

After completing the logServer installation the logs will go to your machine 
automatically after each build run.

I don't quite understand here. I didn't configure anything about jenkins in 
install_log_server.sh except the public SSH key.
How could jenkins find and connect to the log server ? Or how could the log 
server find the jenkins ?

Now, I can access to my log server index page. But when I run a build, no new 
log is put into /srv/static/logs/.

Thanks.






On Thu, Jul 30, 2015 at 2:19 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:
Hi Asselin, Abhishek,

Sorry, it is about the CI again.

I run install_log_server.sh to setup a log server.

I setup the log server on the same machine with my Jenkins Master, and 
configured it like this:
$DOMAIN=localhost
$JENKINS_SSH_PUBLIC_KEY = path to my ssh key

The script completed. But I don't know how to use the log server.

Here are my questions:

1. Is the log server able to be on the same machine with Jenkins Master ?
I think maybe the apache in the log server conflicts with the jenkins 
server.

​ The answer to your question is no, as the logs generated​

​ each time will become large in size so it is recommended to use logServer on 
a separate machine having a public IP.

2. Is the log server able to upload the logs to Gerrit automatically ?
Or it is just a server for you to view the logs ?

​ The logs is not uploaded to Gerrit, only success or failure is reported to 
Gerrit. Also, when you click on the job in the gerrit with either of the 
message, you will be redirected to the logServer page.​


I raised an issue on github.  You can also discuss this on github if you like.
(https://github.com/rasselin/os-ext-testing/issues/19)

I also asked about this in IRC #openstack-infra, but it seems that very few 
people are using os-ext-testing.

Thanks.



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






__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] How to use the log server in CI ?

2015-08-03 Thread Asselin, Ramy
Hi Tang,

Sorry the documentation on github is limited. I’ve been focusing on getting an 
upstream solution working, and that’s where it belongs and should be 
maintained. I will take a quick look and add some tips as discussed in this 
thread.
Of course if you have pull requests, I’m happy to merge them.

I did include publishers in the sample: 
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L73

Ramy
From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Friday, July 31, 2015 12:04 AM
To: Abhishek Shrivastava abhis...@cloudbyte.com
Cc: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] How to use the log server in CI ?

Hi Abhishek,

I found out what was wrong.

I didn't configure publisher in my jobs..
Sorry for the trouble.

But I do think the document on github is not suitable for any beginner.
So I think I will post some patches to provide more info for those who use this 
tool for the very first time
when I finish the work on my hand.

And about the nodepool you asked last time, I'm working on it.
But due to the proxy in my company, I  have to solve lots of trivial problems 
first.

Thanks.

On 07/31/2015 09:57 AM, Tang Chen wrote:
Hi Abhishek,

On 07/30/2015 04:54 PM, Abhishek Shrivastava wrote:
Hi Tang,

After completing the logServer installation the logs will go to your machine 
automatically after each build run.

I don't quite understand here. I didn't configure anything about jenkins in 
install_log_server.sh except the public SSH key.
How could jenkins find and connect to the log server ? Or how could the log 
server find the jenkins ?

Now, I can access to my log server index page. But when I run a build, no new 
log is put into /srv/static/logs/.

Thanks.





On Thu, Jul 30, 2015 at 2:19 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:
Hi Asselin, Abhishek,

Sorry, it is about the CI again.

I run install_log_server.sh to setup a log server.

I setup the log server on the same machine with my Jenkins Master, and 
configured it like this:
$DOMAIN=localhost
$JENKINS_SSH_PUBLIC_KEY = path to my ssh key

The script completed. But I don't know how to use the log server.

Here are my questions:

1. Is the log server able to be on the same machine with Jenkins Master ?
I think maybe the apache in the log server conflicts with the jenkins 
server.

​ The answer to your question is no, as the logs generated​

​ each time will become large in size so it is recommended to use logServer on 
a separate machine having a public IP.

2. Is the log server able to upload the logs to Gerrit automatically ?
Or it is just a server for you to view the logs ?

​ The logs is not uploaded to Gerrit, only success or failure is reported to 
Gerrit. Also, when you click on the job in the gerrit with either of the 
message, you will be redirected to the logServer page.​


I raised an issue on github.  You can also discuss this on github if you like.
(https://github.com/rasselin/os-ext-testing/issues/19)

I also asked about this in IRC #openstack-infra, but it seems that very few 
people are using os-ext-testing.

Thanks.



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





__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.

2015-08-03 Thread Asselin, Ramy
Hi Tang,

I thought I replied about this earlier. There seems to be a regression running 
jobs directly on master, at least for newer versions of Jenkins. Running on a 
slave does work.

Ramy

From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Monday, July 27, 2015 6:30 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up 
a new CI system.

Hi Zaro,
On 07/24/2015 11:44 PM, Zaro wrote:
Tang, Have you tried to look at the function registrations and gearman queue on 
the gearman server as i suggested?  The instructions are in the wiki i 
referenced (in 'Starting the gearman workers' section).  What you are seeing 
from the gear_client could also be from passing in a function name that does 
not exist.  Unfortunately the simple gear_client does not check whether the 
passed in functions are valid so what you want to do is verify that the gearman 
functions have been registered by using the 'workers' command.


Thank you for your suggestion. I have not seen the inside of Gearman.

But I set up a slave node, and the job can run on the slave node.

This is also acceptable for me. So I think I have to go on with my work first.
And I'll check what you said later.

Thanks very much. :)




On Fri, Jul 24, 2015 at 1:09 AM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:

On 07/24/2015 03:36 PM, Tang Chen wrote:
Hi Zaro,

Thanks to reply.
On 07/24/2015 03:06 PM, Zaro wrote:
That is correctly, the Jenkins UI will not show any info about the gearman 
queue.  If job is pending in Jenkins that means it's been added to the gearman 
queue and has been moved to the jenkins build queue.  The jenkins UI will only 
show the job once it's in the jenkins queue.

Hmm.  What happens when you manually start a build by click on the build icon 
in the jenkins UI?

If I click the build icon in the jenkins UI, the job can run. Wired, isn't it ?

Thanks.



I'm wondering if maybe your labels are configured correctly for your jobs and 
slaves.  Are there any labels on the job or the nodes (master or slaves)? I 
think the jobs would be in a pending state if there are labels on nodes and 
jobs but they do not match.  I would check to see if there are any labels on 
the jobs and if there are then I would remove all of the labels and try again.  
There are step by step directions on how to setup the gearman-plugin in the 
jenkins wiki[1] which also shows you how to debug by viewing the gearman server 
queue and function registrations.  Try to make sure the functions are 
registered correctly and that the job is in the queue after you run the 
gear-client command.

A couple of questions:
What version of Jenkins are you running?  I think openstack runs on 1.565.3
Also I don't think we've ever tested Jenkins and the gearman server running on 
the same machine or VM.  Maybe one thing you can try is to run them on separate 
VMs?

I don't have any label, and only a master, no slave.

My jenkins is 1.609.1.

The whole problem is described here:

http://paste.openstack.org/show/405051/

Please help to check and see.


BTW, I post the problem to #openstack-infra IRC channel. You can join into that 
meeting if you'd like to.


Thanks.



[1] https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin







__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] 答复: [CI] No image was created after running nodepoold -d $DAEMON_ARGS

2015-08-03 Thread Asselin, Ramy
Hi Xiexs,

Definitely make sure you run nodepool commands as nodepool and not root:
sudo su - nodepool

Before starting nodepool on a fresh install, I usually manually build the image 
first as it is easier to debug issues:

sudo su - nodepool
nodepool image-build image-name 

Ramy

-Original Message-
From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com] 
Sent: Wednesday, July 29, 2015 10:44 PM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.org
Subject: [openstack-dev] 答复: [CI] No image was created after running nodepoold 
-d $DAEMON_ARGS

Hi Wienand,
  Thanks for your reply.

So, nothing after this?
Yes, there is nothing anymore since that line in the nodepool.log.
But, the the polling thread still goes on , according to the log message in the 
debug.log.

 Nothing jumps out; first thought was to check if disk-image-create is running 
 and go from there.  If it's stuck, pointing strace() at it might give a clue.
The disk-image-create is still running(with ps command).
I don’t know how to debug disk-image-create while it spawned by nodepoold.
(I had tried to add set -x into disk-image-create, but it did not work) Could 
you give me some tips?

Something I just thought of that has caused problems is check your users; I 
think running things by hand as root and then switching back to a unprivileged 
user can cause problems as the second run hits things it can't modify.
Yes, you are definitely right, I really once met this problem.
But right now, I checked the disk-image-create by hand with user nodepool 
which also used by nodepoold -d $DAEMON_ARGS. 

Thanks again.

Xiexs



-邮件原件-
发件人: Ian Wienand [mailto:iwien...@redhat.com]
发送时间: 2015年7月30日 11:51
收件人: OpenStack Development Mailing List (not for usage questions)
主题: Re: [openstack-dev] [CI] No image was created after running nodepoold -d 
$DAEMON_ARGS

On 07/30/2015 12:34 PM, Xie, Xianshan wrote:
 DEBUG nodepool.NodePool: Finished node launch calculation INFO
 nodepool.DiskImageBuilderThread: Running disk-image-create ...

So, nothing after this?

Nothing jumps out; first thought was to check if disk-image-create is running 
and go from there.  If it's stuck, pointing strace() at it might give a clue.

Full logs and config help, but my best suggestion is to jump on irc in 
#openstack-infra; during USA awake hours you'll get the best response.

-i

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [CI]How to set proxy for nodepool

2015-08-03 Thread Asselin, Ramy
Hi Xiexs,

You are using disk image builder (DIB), so make sure your proxy is set 
correctly also without the NODEPOOL_ prefix.
Those NODEPOOL_ prefixed variables are what would be used when DIB is not used 
/ when the script approach is used with nova/glance (nodepool image-update). I 
don’t recommend using that if you can use DIB.

Also, I’ve found some of the infra project-config elements don’t work in my 
environment and aren’t needed as they’re specific to infra. For those, simply 
comment out the portions that don’t work. I didn’t notice any negative 
side-effects.

Ramy

From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com]
Sent: Monday, August 03, 2015 9:37 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [CI]How to set proxy for nodepool

Hi All,
When I ran “nodepool image-build image-name” to create a new image, I got 
this error message:
…
INFO nodepool.image.build.dpc: + sudo -H virtualenv /usr/zuul-swift-logs-env
INFO nodepool.image.build.dpc: sudo: unable to resolve host fnst01
INFO nodepool.image.build.dpc: + sudo -H /usr/zuul-swift-logs-env/bin/pip 
install python-magic argparse requests glob2
INFO nodepool.image.build.dpc: sudo: unable to resolve host fnst01
INFO nodepool.image.build.dpc: Collecting python-magic
INFO nodepool.image.build.dpc: Retrying (Retry(total=4, connect=None, 
read=None, redirect=None)) after connection broken by 
'ProtocolError('Connection aborted.', gaierror(-5, 'No address associated with 
hostname'))': /simple/python-magic/
INFO nodepool.image.build.dpc: Retrying (Retry(total=3, connect=None, 
read=None, redirect=None)) after connection broken by 
'ProtocolError('Connection aborted.', gaierror(-5, 'No address associated with 
hostname'))': /simple/python-magic/
…

And I exported the bash env when the script 
elements/nodepool-base/install.d/90-venv-swift-logs ran,
it seems that the nodepool proxy and dns has already been set:

declare -x NODEPOOL_HTTPS_PROXY=http://xx.xx.xx.xx:8080/  --valid proxy
declare -x NODEPOOL_HTTP_PROXY=http://xx.xx.xx.xx:8080/;
declare -x NODEPOOL_NO_PROXY=localhost,127.0.0.1
declare -x NODEPOOL_SCRIPTDIR=/etc/nodepool/scripts
declare -x NODEPOOL_STATIC_NAMESERVER=xx.xx.xx.xx
declare -x PS1=(zuul-swift-logs-env)
INFO nodepool.image.build.dpc: + cat /etc/resolv.conf
INFO nodepool.image.build.dpc: nameserver xx.xx.xx.xx   --valid dns

And I have tried to add element “local-config” into nodepool.yaml, but it does 
not work.

So, my questions are:

1)  These bash env will be passed into the virtualenv zuul-swift-logs-env 
after chroot, is it right?

2)  If not, how to configure the proxy for nodepool?

Many thanks to any suggestion.

Xiexs
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.

2015-07-23 Thread Asselin, Ramy
Are you running on 'master' nodes? I remember seeing an issue where with a 
recent version of Jenkins or a plugin where it doesn't execute jobs on the 
master node.
But when run on non-master jenkins slaves, it works fine.

-Original Message-
From: Tang Chen [mailto:tangc...@cn.fujitsu.com] 
Sent: Thursday, July 23, 2015 12:38 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up 
a new CI system.

Hi, all

The Jenkins jobs submitted by zuul are always pending-Waiting for next 
available executor .

And Jenkins log shows the following:

Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl
submitFunction
WARNING:  Worker _exec-0 exception while executing function 
hudson.plugins.gearman.StartJobWorker
java.lang.RuntimeException: java.lang.RuntimeException: 
java.util.concurrent.CancellationException
at
org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:136)
at
org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:22)
at
hudson.plugins.gearman.MyGearmanWorkerImpl.submitFunction(MyGearmanWorkerImpl.java:590)
at
hudson.plugins.gearman.MyGearmanWorkerImpl.work(MyGearmanWorkerImpl.java:374)
at
hudson.plugins.gearman.AbstractWorkerThread.run(AbstractWorkerThread.java:166)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.RuntimeException: 
java.util.concurrent.CancellationException
at
hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:116)
at
org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:125)
... 5 more
Caused by: java.util.concurrent.CancellationException
at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:77)
at
hudson.plugins.gearman.StartJobWorker.safeExecuteFunction(StartJobWorker.java:196)
at
hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:114)
... 6 more

Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work
INFO:  Worker _exec-0 sending initial grab job Jul 24, 2015 11:09:04 AM 
hudson.plugins.gearman.MyGearmanWorkerImpl
handleSessionEvent
INFO:  Worker _exec-1 received unique job assignment Jul 24, 2015 11:09:04 
AM hudson.plugins.gearman.MyGearmanWorkerImpl work
INFO:  Worker _exec-1 executing function Jul 24, 2015 11:09:04 AM 
hudson.plugins.gearman.StartJobWorker
safeExecuteFunction
INFO:  Worker _exec-1 scheduling devstack-vm-test build #14 on with UUID 
83d4fd10c1ad4f1ead51beb2adf23ccd and build params
[(StringParameterValue) BASE_LOG_PATH='03/204803/1',
(StringParameterValue) ZUUL_PIPELINE='check', (StringParameterValue) 
ZUUL_UUID='83d4fd10c1ad4f1ead51beb2adf23ccd', (StringParameterValue) 
LOG_PATH='03/204803/1/check/devstack-vm-test/83d4fd1',
(StringParameterValue) ZUUL_CHANGE_IDS='204803,1',
(StringParameterValue) ZUUL_PATCHSET='1', (StringParameterValue) 
ZUUL_BRANCH='master', (StringParameterValue) 
ZUUL_REF='refs/zuul/master/Z07d022076a68448d842bd1a47dd42e19',
(StringParameterValue)
ZUUL_COMMIT='174cac545549f086e07f32edbe34b70c4155a7fc',
(StringParameterValue) ZUUL_URL='http://10.124.196.205/p/',
(StringParameterValue) ZUUL_CHANGE='204803', (StringParameterValue) 
ZUUL_CHANGES='openstack-dev/sandbox:master:refs/changes/03/204803/1',
(StringParameterValue) ZUUL_PROJECT='openstack-dev/sandbox']


It seems that Gearman doesn't work properly.

Do you guys have any idea of this ?

Thanks.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [CI] How to set a proxy for zuul.

2015-07-21 Thread Asselin, Ramy
Hi Tang,

Please use a new thread for this new question.  I'd like to keep the current 
thread focused on How to set a proxy for zuul.

Ramy

From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Tuesday, July 21, 2015 12:23 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [CI] How to set a proxy for zuul.

Hi Asselin, Abhishek,

I got some problems when I was trying to write a jenkins job.

I found that when zuul received the notification from gerrit, jenkins didn't 
run the test.

I added something to noop-check-communication in /etc/jenkins_jobs/config/ 
examples.yaml,
just touched a file under /tmp.

- job-template:
name: 'noop-check-communication'
node: '{node}'

builders:
  - shell: |
  #!/bin/bash -xe
  touch /tmp/noop-check-communication   
 # I added something here.
  echo Hello world, this is the {vendor} Testing System
  - link-logs  # In macros.yaml from os-ext-testing

And I flushed the jobs, using jenkins-jobs --flush-cache update 
/etc/jenkins_jobs/config/.
I can build the job in jenkins web UI, and the file was touched.


But when I send a patch, the file was not touched. But CI really works.
I can see it on the web site. ( https://review.openstack.org/#/c/203941/)

How do you think of this ?


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-21 Thread Asselin, Ramy
Why do you want to stop those downloads? The purpose is to setup your VM so 
that it has the latest code in the git repos and that each project has any 
custom refs, such as the patch under test.

Also, this is a different problem than the subject, so should be a new thread.

Ramy

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Tuesday, July 21, 2015 2:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: openstack-in...@lists.openstack.org
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

Also, can't we stop downloading all those projects and let them include them in 
the DevStack using the ENABLED_SERVICES parameter, like we usually do while 
installing devstack.

On Tue, Jul 21, 2015 at 11:18 AM, Abhishek Shrivastava 
abhis...@cloudbyte.commailto:abhis...@cloudbyte.com wrote:
Hi Ramy,


  *   The project list is mentioned in the devstack-vm-gate-wrap script[1].
  *   Downloaded using functions.sh script using setup workspace function[2]
[1] 
https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate-wrap.sh#L35
[2] 
https://github.com/openstack-infra/devstack-gate/blob/master/functions.sh#L416

On Mon, Jul 20, 2015 at 7:14 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
Is this to optimize the performance of the job? Can you provide a link to where 
the downloading is occurring that you’d like to restrict?

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.commailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 10:53 PM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

This is ok for the services it will install, but how can we also restrict the 
downloading of all the projects(i.e; downloading only required projects) ?

On Sun, Jul 19, 2015 at 11:39 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
There are two ways that I know of to customize what services are run:

1.  Setup your own feature matrix [1]

2.  Override enabled services [2]

Option 2 is probably what you’re looking for.

[1] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n152
[2] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate.sh#n76

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.commailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 10:37 AM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

Hi Ramy,

Thanks for the suggestion. One more thing I need to ask, as I have have setup 
one more CI so is there any way that we can decide that only required projects 
should get downloaded and installed during devstack installation dynamically. 
As I see no such things that can be done to devstack-gate scripts so the 
following scenario can be achieved.

On Sun, Jul 19, 2015 at 8:38 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
Just the export I mentioned:
export DEVSTACK_GATE_NEUTRON=1
Devstack-gate scripts will do the right thing when it sees that set. You can 
see plenty of examples here [1].

Ramy

[1] 
http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/devstack-gate.yaml#n467

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.commailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 2:24 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

Hi Ramy,

Thanks for the suggestion but since I am not including the neutron project, so 
downloading and including it will require any additional configuration in 
devstack-gate or not?

On Sat, Jul 18, 2015 at 11:41 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
We ran into this issue as well. I never found the root cause, but I found a 
work-around: Use neutron-networking instead of the default nova-networking.

If you’re using devstack-gate, it’s as  simple as:
export DEVSTACK_GATE_NEUTRON=1

Then run the job as usual.

Ramy

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.commailto:abhis...@cloudbyte.com]
Sent: Friday, July 17, 2015 9:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing 
with SSH timeout.

Hi Folks,

In my CI I see the following tempest tests failure for a past couple of days.

•
tempest.scenario.test_minimum_basic.TestMinimumBasicScenario.test_minimum_basic_scenario
 [361.274316s] ... FAILED

•
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
 [320.122458s] ... FAILED

Re: [openstack-dev] [CI] How to set a proxy for zuul.

2015-07-21 Thread Asselin, Ramy
Tang,

#openstack-meeting is for people to come together for officially scheduled 
meetings [1]
Did you try to join the 3rd party meeting on Monday[2]? I was chairing the 
meeting but did not see you. That would be a great forum to ask these questions.

Otherwise, you can ask in #openstack-infra. If you do ask, remember to stay 
logged in, otherwise you'll miss any responses  people are not likely to 
respond to your question if they see you're not logged in (because you'll miss 
the response).

Ramy

[1] https://wiki.openstack.org/wiki/Meetings
[2] http://eavesdrop.openstack.org/#Third_Party_Meeting



From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Tuesday, July 21, 2015 12:50 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [CI] How to set a proxy for zuul.


On 07/21/2015 03:35 PM, Abhishek Shrivastava wrote:
Hi Tang,

Can you please send me the whole job snippet you wrote.

In /etc/jenkins_jobs/config/ examples.yaml, that's all.

- job-template:
name: 'noop-check-communication'
node: '{node}'

builders:
  - shell: |
  #!/bin/bash -xe
  touch /tmp/noop-check-communication
  echo Hello world, this is the {vendor} Testing System
  - link-logs  # In macros.yaml from os-ext-testing

#publishers:
#  - devstack-logs  # In macros.yaml from os-ext-testing
#  - console-log  # In macros.yaml from os-ext-testing



noop-check-communication was setup by default. I didn't change anything else.


BTW, I tried to ask this in #openstack-meeting IRC.
But no one seems to be active. :)

Thanks.




On Tue, Jul 21, 2015 at 12:52 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:
Hi Asselin, Abhishek,

I got some problems when I was trying to write a jenkins job.

I found that when zuul received the notification from gerrit, jenkins didn't 
run the test.

I added something to noop-check-communication in /etc/jenkins_jobs/config/ 
examples.yaml,
just touched a file under /tmp.

- job-template:
name: 'noop-check-communication'
node: '{node}'

builders:
  - shell: |
  #!/bin/bash -xe
  touch /tmp/noop-check-communication   
 # I added something here.
  echo Hello world, this is the {vendor} Testing System
  - link-logs  # In macros.yaml from os-ext-testing

And I flushed the jobs, using jenkins-jobs --flush-cache update 
/etc/jenkins_jobs/config/.
I can build the job in jenkins web UI, and the file was touched.


But when I send a patch, the file was not touched. But CI really works.
I can see it on the web site. ( https://review.openstack.org/#/c/203941/)

How do you think of this ?



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
[https://docs.google.com/uc?export=downloadid=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com




__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [CI] How to set a proxy for zuul.

2015-07-20 Thread Asselin, Ramy
I found that paramiko does support proxies [1].

I remember looking at this a long time ago and you should be able to update 
zuul code to use it [2].

Ramy


[1] http://blog.adimian.com/2014/10/paramiko-and-corporate-proxies/
[2] 
http://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/lib/gerrit.py#n61


From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Sunday, July 19, 2015 10:48 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI] How to set a proxy for zuul.

Hi Asselin, Abhishek,

Thanks for the reply. :)

On 07/19/2015 02:41 AM, Asselin, Ramy wrote:
HI Abhi  Tang,

Sorry I missed this thread. Let me know if you’ve resolved your issues.

My repo is undergoing migrations to reuse components in 
openstack-infra/puppet-openstackci.

For single-use-nodes, the file you need has been removed here [1]: But I see 
now that it is still needed, or a different function is needed based on this 
version used by infra: [2]. I will explore a solution.

A couple other notes, please use ci-sandbox  [3] instead of sandbox.

OK.



Zuul use behind a proxy: seems you got past this? Could you share your solution?

The root cause is that zuul uses a library named paramiko to create connection
with low level socket APIs. And it doesn't provide proxy functionary.

I tried to use tools like proxychain, to redirect the zuul connection to go 
through
my proxy. But it doesn't work. If I use proxychain to run zuul service, it 
doesn't
output anything to the log file, and the service will die soon.

I think, there are two solutions:
1. Add proxy functionality to paramiko.
2. Add proxy functionality to zuul. That means, maybe,
zuul does not use paramiko to create connection, but by itself.

Solution 1 is much simpler, so for now, I just modified the source code of 
paramiko.

I'm using python-socksipy package, and modified
/usr/local/lib/python2.7/dist-packages/paramiko/client.py like this:

diff --git a/client.py b/client.py
index 15ff696..d7225ed 100644
--- a/client.py
+++ b/client.py
@@ -24,6 +24,7 @@ from binascii import hexlify
 import getpass
 import os
 import socket
+import socks
 import warnings
 import pdb

@@ -235,6 +236,7 @@ class SSHClient (ClosingContextManager):
 ``gss_deleg_creds`` and ``gss_host`` arguments.
 

+   
 if not sock:
 for (family, socktype, proto, canonname, sockaddr) in 
socket.getaddrinfo(hostname, port, socket.AF_UNSPEC, socket.SOCK_STREAM):
 if socktype == socket.SOCK_STREAM:
@@ -251,6 +253,13 @@ class SSHClient (ClosingContextManager):
 except:
 pass
 retry_on_signal(lambda: sock.connect(addr))
+   
+
+   if not sock:
+   sock = socks.socksocket()
+   sock.setproxy(socks.PROXY_TYPE_SOCKS5, MY_PROXY_IP, 
MY_PROXY_PORT, username=XXX, password=XXX)

  # This is review.openstack.org
+   addr = ('104.130.159.134', 29418)
+   retry_on_signal(lambda: sock.connect(addr))

 t = self._transport = Transport(sock, gss_kex=gss_kex, 
gss_deleg_creds=gss_deleg_creds)
 t.use_compression(compress=compress)


Of course, this is just a draft. It is only for my case, not for all.


BTW, I'm now working on Fujitsu CI System, and really want to join into the 
development of openstack-infra.
I think the proxy functionality is necessary for many companies. So if you are 
planing to add the proxy support,
I think I can help.

Thanks. :)



Also, feel free to join 3rd party ci IRC  meetings on freenode [4]. It’s a 
great place to ask questions and meet others setting up or maintaining these 
systems.

Thanks,
Ramy
IRC: asselin

[1] 
https://github.com/rasselin/os-ext-testing/commit/dafe822be7813522a6c7361993169da20b37ffb7
[2] 
https://github.com/openstack-infra/project-config/blob/master/zuul/openstack_functions.py
[3] http://git.openstack.org/cgit/openstack-dev/ci-sandbox/
[4] http://eavesdrop.openstack.org/#Third_Party_Meeting



From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Monday, July 13, 2015 11:51 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI] How to set a proxy for zuul.

Also if you want to change it you will need to talk with Asselin Ramy who is 
the owner of the repo you followed.

On Tue, Jul 14, 2015 at 12:18 PM, Abhishek Shrivastava 
abhis...@cloudbyte.commailto:abhis...@cloudbyte.com wrote:
​Basically it is not required, and if you see /etc/jenkins_jobs/config folder 
you will find one dsvm-cinder-tempest.yaml which is to be used basically not 
examples.yaml. So its not an issue.​

On Tue, Jul 14, 2015 at 12:07 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:

On 07/14/2015 01:46 PM, Abhishek Shrivastava wrote:
Instead of it use reusable_node option.

Thanks. Problem resolved. :)

BTW, single_use_node is written in layout.yaml by default.
If it doesn't

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-20 Thread Asselin, Ramy
Is this to optimize the performance of the job? Can you provide a link to where 
the downloading is occurring that you’d like to restrict?

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 10:53 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

This is ok for the services it will install, but how can we also restrict the 
downloading of all the projects(i.e; downloading only required projects) ?

On Sun, Jul 19, 2015 at 11:39 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
There are two ways that I know of to customize what services are run:

1.  Setup your own feature matrix [1]

2.  Override enabled services [2]

Option 2 is probably what you’re looking for.

[1] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n152
[2] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate.sh#n76

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.commailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 10:37 AM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

Hi Ramy,

Thanks for the suggestion. One more thing I need to ask, as I have have setup 
one more CI so is there any way that we can decide that only required projects 
should get downloaded and installed during devstack installation dynamically. 
As I see no such things that can be done to devstack-gate scripts so the 
following scenario can be achieved.

On Sun, Jul 19, 2015 at 8:38 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
Just the export I mentioned:
export DEVSTACK_GATE_NEUTRON=1
Devstack-gate scripts will do the right thing when it sees that set. You can 
see plenty of examples here [1].

Ramy

[1] 
http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/devstack-gate.yaml#n467

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.commailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 2:24 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

Hi Ramy,

Thanks for the suggestion but since I am not including the neutron project, so 
downloading and including it will require any additional configuration in 
devstack-gate or not?

On Sat, Jul 18, 2015 at 11:41 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
We ran into this issue as well. I never found the root cause, but I found a 
work-around: Use neutron-networking instead of the default nova-networking.

If you’re using devstack-gate, it’s as  simple as:
export DEVSTACK_GATE_NEUTRON=1

Then run the job as usual.

Ramy

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.commailto:abhis...@cloudbyte.com]
Sent: Friday, July 17, 2015 9:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing 
with SSH timeout.

Hi Folks,

In my CI I see the following tempest tests failure for a past couple of days.

•
tempest.scenario.test_minimum_basic.TestMinimumBasicScenario.test_minimum_basic_scenario
 [361.274316s] ... FAILED

•
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
 [320.122458s] ... FAILED

•
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern
 [317.399342s] ... FAILED

•
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_compute_with_volumes
 [257.858272s] ... FAILED

The failure logs are always the same every time, i.e;



03:34:09 2015-07-17 03:21:13,256 9505 ERROR[tempest.scenario.manager] 
(TestVolumeBootPattern:test_volume_boot_pattern) Initializing SSH connection to 
172.24.5.1 failed. Error: Connection to the 172.24.5.1 via SSH timed out.

03:34:09 User: cirros, Password: None

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
Traceback (most recent call last):

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
tempest/scenario/manager.py, line 312, in get_remote_client

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
linux_client.validate_authentication()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
tempest/common/utils/linux/remote_client.py, line 62, in 
validate_authentication

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
self.ssh_client.test_connection_auth()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common

Re: [openstack-dev] [CI] How to set a proxy for zuul.

2015-07-20 Thread Asselin, Ramy
Pull Requests are welcomed.
I think you’re referring to [1], but it shouldn’t make a functional difference 
since ‘name’ is not being referenced anywhere.


[1] 
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/projects.yaml#L2


From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Sunday, July 19, 2015 11:06 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI] How to set a proxy for zuul.


On 07/19/2015 02:41 AM, Asselin, Ramy wrote:
HI Abhi  Tang,

Sorry I missed this thread. Let me know if you’ve resolved your issues.

My repo is undergoing migrations to reuse components in 
openstack-infra/puppet-openstackci.

For single-use-nodes, the file you need has been removed here [1]: But I see 
now that it is still needed, or a different function is needed based on this 
version used by infra: [2]. I will explore a solution.

A couple other notes, please use ci-sandbox  [3] instead of sandbox.

BTW, in /etc/zuul/layout.yaml, it is ci-sandbox.

But in /etc/jenkins_jobs/config/projects.yaml, it is configured to sandbox.

Not a big deal, but for someone who uses CI for the first time, it costs some 
time to solve it.

Thanks. :)



Zuul use behind a proxy: seems you got past this? Could you share your solution?

Also, feel free to join 3rd party ci IRC  meetings on freenode [4]. It’s a 
great place to ask questions and meet others setting up or maintaining these 
systems.

Thanks,
Ramy
IRC: asselin

[1] 
https://github.com/rasselin/os-ext-testing/commit/dafe822be7813522a6c7361993169da20b37ffb7
[2] 
https://github.com/openstack-infra/project-config/blob/master/zuul/openstack_functions.py
[3] http://git.openstack.org/cgit/openstack-dev/ci-sandbox/
[4] http://eavesdrop.openstack.org/#Third_Party_Meeting



From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Monday, July 13, 2015 11:51 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI] How to set a proxy for zuul.

Also if you want to change it you will need to talk with Asselin Ramy who is 
the owner of the repo you followed.

On Tue, Jul 14, 2015 at 12:18 PM, Abhishek Shrivastava 
abhis...@cloudbyte.commailto:abhis...@cloudbyte.com wrote:
​Basically it is not required, and if you see /etc/jenkins_jobs/config folder 
you will find one dsvm-cinder-tempest.yaml which is to be used basically not 
examples.yaml. So its not an issue.​

On Tue, Jul 14, 2015 at 12:07 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:

On 07/14/2015 01:46 PM, Abhishek Shrivastava wrote:
Instead of it use reusable_node option.

Thanks. Problem resolved. :)

BTW, single_use_node is written in layout.yaml by default.
If it doesn't exist anymore, do we need a patch to fix it ?

For someone who uses CI for the first time, it is really a problem..

And also, if I want to post patch for zuul, where should I post the patch ?

Thanks.





On Tue, Jul 14, 2015 at 9:12 AM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:
Hi Abhishek, All,

I found the problem.

My /etc/zuul/layout/layout.yaml has the following config:

jobs:
  - name: ^dsvm-tempest.*$
parameter-function: single_use_node

But in _parseConfig() in zuul/scheduler.py, it failed to find single_use_node().

fname = config_job.get('parameter-function', None)
if fname:
func = config_env.get(fname, None)
if not func:
raise Exception(Unable to find function %s % fname)

So projects section was not parsed.

Does anyone know why ?

Thanks.




On 07/14/2015 10:54 AM, Tang Chen wrote:
Hi Abhishek,

I printed the self.layout.projects in zuul/scheduler.py, it is empty.
So the project was not found.

But I did do the jenkins-jobs --flush-cache update /etc/jenkins_jobs/config/
And I did configure openstack-dev/sandbox in layout.yaml.

Do you have any idea what's wrong here ?

Thanks.


On 07/13/2015 05:58 PM, Tang Chen wrote:

On 07/13/2015 04:35 PM, Abhishek Shrivastava wrote:
Updating jobs using sudo jenkins-jobs --flush-cache update 
/etc/jenkins_jobs/config/. Also update the myvendor in examples.yaml


Sorry, I updated the jobs, restart the whole machine. But it still doesn't work.

By the way, there is no vendor in examples.yaml.

It is still this error: Project openstack-dev/sandbox not found

Anything else should I pay attention to?

Thanks.




On Mon, Jul 13, 2015 at 1:45 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:

On 07/13/2015 03:50 PM, Abhishek Shrivastava wrote:
​ Use tester or something, also are you updating the jobs or not?​

I used tester as my vendor. It doesn't work.

And what do you mean by updating the jobs ? I built the 
noop-check-cimmunitication
job once in Jenkins UI. Does it matter ? All the others are not touched.

And referring to the error, Project openstack-dev/sandbox not found, it seems 
like
somewhere

Re: [openstack-dev] [third-party][infra] Common OpenStack CI Solution - 'Jenkins Job Builder' live

2015-07-20 Thread Asselin, Ramy
All,

I’m pleased to announce the 4th component merged to puppet-openstackci repo [1].

This means 3rd party ci operators can now use the same scripts that the 
OpenStack Infrastructure team uses in the official ‘Jenkins’ CI system for:


1.   Log Server

2.   Jenkins

3.   Zuul

4.   Jenkins Job Builder

This work is being done as part of the common-ci spec [2]

Big thanks to Juame Devesa for starting the work, Khai Do for fixing all issues 
found in the reviews during the virtual sprint, and to all the reviewers and 
testers.

We’re almost there! Just have nodepool and a sample config to compose all of 
the components together [3]!

Ramy
IRC: asselin

[1] https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101


From: Asselin, Ramy
Sent: Thursday, July 02, 2015 4:59 PM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.org
Subject: [openstack-dev] [third-party][infra] Common OpenStack CI Solution - 
'Zuul' live

All,

I’m please to say that there are now 3 components merged in the 
puppet-openstackci repo [1]
This means 3rd party ci operators can now use the same scripts that the 
OpenStack Infrastructure team uses in the official ‘Jenkins’ CI system for:


1.   Log Server

2.   Jenkins

3.   Zuul

This work is being done as part of the common-ci spec [2]

Big thanks to Fabien Boucher for completing the Zuul script refactoring, which 
went live today!
Thanks to all the reviewers for careful reviews which led to a smooth migration.

I’ve updated my repo [3]  switched all my CI systems to use it.

As a reminder, there will be a virtual sprint next week July 8-9, 2015 15:00 
UTC to finish the remaining tasks.
If you’re interested in helping out in any of the remaining tasks (Jenkins Job 
Builder, Nodepool, Logstash/Kibana, Documentation, Sample site.pp) Sign up on 
the eitherpad. [4]

Also, we can use the 3rd party meeting time slot next week to discuss plans and 
answer questions [5].
Tuesday 7/7/15 1700 UTC #openstack-meeting

Ramy
IRC: asselin

[1] https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://github.com/rasselin/os-ext-testing (forked from 
jaypipes/os-ext-testing)
[4] https://etherpad.openstack.org/p/common-ci-sprint
[5] https://wiki.openstack.org/wiki/Meetings/ThirdParty


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-19 Thread Asselin, Ramy
There are two ways that I know of to customize what services are run:

1.  Setup your own feature matrix [1]

2.  Override enabled services [2]

Option 2 is probably what you’re looking for.

[1] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n152
[2] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate.sh#n76

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 10:37 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

Hi Ramy,

Thanks for the suggestion. One more thing I need to ask, as I have have setup 
one more CI so is there any way that we can decide that only required projects 
should get downloaded and installed during devstack installation dynamically. 
As I see no such things that can be done to devstack-gate scripts so the 
following scenario can be achieved.

On Sun, Jul 19, 2015 at 8:38 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
Just the export I mentioned:
export DEVSTACK_GATE_NEUTRON=1
Devstack-gate scripts will do the right thing when it sees that set. You can 
see plenty of examples here [1].

Ramy

[1] 
http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/devstack-gate.yaml#n467

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.commailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 2:24 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

Hi Ramy,

Thanks for the suggestion but since I am not including the neutron project, so 
downloading and including it will require any additional configuration in 
devstack-gate or not?

On Sat, Jul 18, 2015 at 11:41 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
We ran into this issue as well. I never found the root cause, but I found a 
work-around: Use neutron-networking instead of the default nova-networking.

If you’re using devstack-gate, it’s as  simple as:
export DEVSTACK_GATE_NEUTRON=1

Then run the job as usual.

Ramy

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.commailto:abhis...@cloudbyte.com]
Sent: Friday, July 17, 2015 9:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing 
with SSH timeout.

Hi Folks,

In my CI I see the following tempest tests failure for a past couple of days.

•
tempest.scenario.test_minimum_basic.TestMinimumBasicScenario.test_minimum_basic_scenario
 [361.274316s] ... FAILED

•
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
 [320.122458s] ... FAILED

•
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern
 [317.399342s] ... FAILED

•
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_compute_with_volumes
 [257.858272s] ... FAILED

The failure logs are always the same every time, i.e;



03:34:09 2015-07-17 03:21:13,256 9505 ERROR[tempest.scenario.manager] 
(TestVolumeBootPattern:test_volume_boot_pattern) Initializing SSH connection to 
172.24.5.1 failed. Error: Connection to the 172.24.5.1 via SSH timed out.

03:34:09 User: cirros, Password: None

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
Traceback (most recent call last):

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
tempest/scenario/manager.py, line 312, in get_remote_client

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
linux_client.validate_authentication()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
tempest/common/utils/linux/remote_client.py, line 62, in 
validate_authentication

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
self.ssh_client.test_connection_auth()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py,
 line 151, in test_connection_auth

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
connection = self._get_ssh_connection()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py,
 line 87, in _get_ssh_connection

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
password=self.password)

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
SSHTimeout: Connection to the 172.24.5.1 via SSH timed out.

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager User: 
cirros

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-19 Thread Asselin, Ramy
Just the export I mentioned:
export DEVSTACK_GATE_NEUTRON=1
Devstack-gate scripts will do the right thing when it sees that set. You can 
see plenty of examples here [1].

Ramy

[1] 
http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/devstack-gate.yaml#n467

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 2:24 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

Hi Ramy,

Thanks for the suggestion but since I am not including the neutron project, so 
downloading and including it will require any additional configuration in 
devstack-gate or not?

On Sat, Jul 18, 2015 at 11:41 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
We ran into this issue as well. I never found the root cause, but I found a 
work-around: Use neutron-networking instead of the default nova-networking.

If you’re using devstack-gate, it’s as  simple as:
export DEVSTACK_GATE_NEUTRON=1

Then run the job as usual.

Ramy

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.commailto:abhis...@cloudbyte.com]
Sent: Friday, July 17, 2015 9:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing 
with SSH timeout.

Hi Folks,

In my CI I see the following tempest tests failure for a past couple of days.

•
tempest.scenario.test_minimum_basic.TestMinimumBasicScenario.test_minimum_basic_scenario
 [361.274316s] ... FAILED

•
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
 [320.122458s] ... FAILED

•
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern
 [317.399342s] ... FAILED

•
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_compute_with_volumes
 [257.858272s] ... FAILED

The failure logs are always the same every time, i.e;



03:34:09 2015-07-17 03:21:13,256 9505 ERROR[tempest.scenario.manager] 
(TestVolumeBootPattern:test_volume_boot_pattern) Initializing SSH connection to 
172.24.5.1 failed. Error: Connection to the 172.24.5.1 via SSH timed out.

03:34:09 User: cirros, Password: None

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
Traceback (most recent call last):

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
tempest/scenario/manager.py, line 312, in get_remote_client

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
linux_client.validate_authentication()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
tempest/common/utils/linux/remote_client.py, line 62, in 
validate_authentication

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
self.ssh_client.test_connection_auth()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py,
 line 151, in test_connection_auth

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
connection = self._get_ssh_connection()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py,
 line 87, in _get_ssh_connection

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
password=self.password)

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
SSHTimeout: Connection to the 172.24.5.1 via SSH timed out.

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager User: 
cirros, Password: None

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager

03:34:09 2015-07-17 03:21:14,377 9505 INFO 
[tempest_lib.common.rehttp://tempest_lib.common.re



Because of these every job is failing, so if someone can help me regarding this 
please do reply.

--
[https://docs.google.com/uc?export=downloadid=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
[https://docs.google.com/uc?export=downloadid=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com
__
OpenStack Development Mailing

Re: [openstack-dev] [CI] How to set a proxy for zuul.

2015-07-18 Thread Asselin, Ramy
HI Tang,

I just pushed the file [1]. Please read the migration instructions in the 
README.md.

Let me know of any issues [2].

[1] 
https://github.com/rasselin/os-ext-testing/commit/9b39bb3c9a3532e753763d5e65241eeff2a20a06
[2] https://github.com/rasselin/os-ext-testing/issues/new

Thanks,
Ramy


From: Asselin, Ramy
Sent: Saturday, July 18, 2015 11:41 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: RE: [openstack-dev] [CI] How to set a proxy for zuul.

HI Abhi  Tang,

Sorry I missed this thread. Let me know if you’ve resolved your issues.

My repo is undergoing migrations to reuse components in 
openstack-infra/puppet-openstackci.

For single-use-nodes, the file you need has been removed here [1]: But I see 
now that it is still needed, or a different function is needed based on this 
version used by infra: [2]. I will explore a solution.

A couple other notes, please use ci-sandbox  [3] instead of sandbox.

Zuul use behind a proxy: seems you got past this? Could you share your solution?

Also, feel free to join 3rd party ci IRC  meetings on freenode [4]. It’s a 
great place to ask questions and meet others setting up or maintaining these 
systems.

Thanks,
Ramy
IRC: asselin

[1] 
https://github.com/rasselin/os-ext-testing/commit/dafe822be7813522a6c7361993169da20b37ffb7
[2] 
https://github.com/openstack-infra/project-config/blob/master/zuul/openstack_functions.py
[3] http://git.openstack.org/cgit/openstack-dev/ci-sandbox/
[4] http://eavesdrop.openstack.org/#Third_Party_Meeting



From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Monday, July 13, 2015 11:51 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI] How to set a proxy for zuul.

Also if you want to change it you will need to talk with Asselin Ramy who is 
the owner of the repo you followed.

On Tue, Jul 14, 2015 at 12:18 PM, Abhishek Shrivastava 
abhis...@cloudbyte.commailto:abhis...@cloudbyte.com wrote:
​Basically it is not required, and if you see /etc/jenkins_jobs/config folder 
you will find one dsvm-cinder-tempest.yaml which is to be used basically not 
examples.yaml. So its not an issue.​

On Tue, Jul 14, 2015 at 12:07 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:

On 07/14/2015 01:46 PM, Abhishek Shrivastava wrote:
Instead of it use reusable_node option.

Thanks. Problem resolved. :)

BTW, single_use_node is written in layout.yaml by default.
If it doesn't exist anymore, do we need a patch to fix it ?

For someone who uses CI for the first time, it is really a problem..

And also, if I want to post patch for zuul, where should I post the patch ?

Thanks.



On Tue, Jul 14, 2015 at 9:12 AM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:
Hi Abhishek, All,

I found the problem.

My /etc/zuul/layout/layout.yaml has the following config:

jobs:
  - name: ^dsvm-tempest.*$
parameter-function: single_use_node

But in _parseConfig() in zuul/scheduler.py, it failed to find single_use_node().

fname = config_job.get('parameter-function', None)
if fname:
func = config_env.get(fname, None)
if not func:
raise Exception(Unable to find function %s % fname)

So projects section was not parsed.

Does anyone know why ?

Thanks.


On 07/14/2015 10:54 AM, Tang Chen wrote:
Hi Abhishek,

I printed the self.layout.projects in zuul/scheduler.py, it is empty.
So the project was not found.

But I did do the jenkins-jobs --flush-cache update /etc/jenkins_jobs/config/
And I did configure openstack-dev/sandbox in layout.yaml.

Do you have any idea what's wrong here ?

Thanks.
On 07/13/2015 05:58 PM, Tang Chen wrote:

On 07/13/2015 04:35 PM, Abhishek Shrivastava wrote:
Updating jobs using sudo jenkins-jobs --flush-cache update 
/etc/jenkins_jobs/config/. Also update the myvendor in examples.yaml


Sorry, I updated the jobs, restart the whole machine. But it still doesn't work.

By the way, there is no vendor in examples.yaml.

It is still this error: Project openstack-dev/sandbox not found

Anything else should I pay attention to?

Thanks.


On Mon, Jul 13, 2015 at 1:45 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:

On 07/13/2015 03:50 PM, Abhishek Shrivastava wrote:
​ Use tester or something, also are you updating the jobs or not?​

I used tester as my vendor. It doesn't work.

And what do you mean by updating the jobs ? I built the 
noop-check-cimmunitication
job once in Jenkins UI. Does it matter ? All the others are not touched.

And referring to the error, Project openstack-dev/sandbox not found, it seems 
like
somewhere the project name was wrong.

right ?


Thanks.


On Mon, Jul 13, 2015 at 1:16 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:
Hi Abhishek,

Thanks for the quick reply.
On 07/13/2015 03:16 PM, Abhishek Shrivastava wrote:
Also check that Gearman is connecting

Re: [openstack-dev] [CI] How to set a proxy for zuul.

2015-07-18 Thread Asselin, Ramy
HI Abhi  Tang,

Sorry I missed this thread. Let me know if you’ve resolved your issues.

My repo is undergoing migrations to reuse components in 
openstack-infra/puppet-openstackci.

For single-use-nodes, the file you need has been removed here [1]: But I see 
now that it is still needed, or a different function is needed based on this 
version used by infra: [2]. I will explore a solution.

A couple other notes, please use ci-sandbox  [3] instead of sandbox.

Zuul use behind a proxy: seems you got past this? Could you share your solution?

Also, feel free to join 3rd party ci IRC  meetings on freenode [4]. It’s a 
great place to ask questions and meet others setting up or maintaining these 
systems.

Thanks,
Ramy
IRC: asselin

[1] 
https://github.com/rasselin/os-ext-testing/commit/dafe822be7813522a6c7361993169da20b37ffb7
[2] 
https://github.com/openstack-infra/project-config/blob/master/zuul/openstack_functions.py
[3] http://git.openstack.org/cgit/openstack-dev/ci-sandbox/
[4] http://eavesdrop.openstack.org/#Third_Party_Meeting



From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Monday, July 13, 2015 11:51 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [CI] How to set a proxy for zuul.

Also if you want to change it you will need to talk with Asselin Ramy who is 
the owner of the repo you followed.

On Tue, Jul 14, 2015 at 12:18 PM, Abhishek Shrivastava 
abhis...@cloudbyte.commailto:abhis...@cloudbyte.com wrote:
​Basically it is not required, and if you see /etc/jenkins_jobs/config folder 
you will find one dsvm-cinder-tempest.yaml which is to be used basically not 
examples.yaml. So its not an issue.​

On Tue, Jul 14, 2015 at 12:07 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:

On 07/14/2015 01:46 PM, Abhishek Shrivastava wrote:
Instead of it use reusable_node option.

Thanks. Problem resolved. :)

BTW, single_use_node is written in layout.yaml by default.
If it doesn't exist anymore, do we need a patch to fix it ?

For someone who uses CI for the first time, it is really a problem..

And also, if I want to post patch for zuul, where should I post the patch ?

Thanks.




On Tue, Jul 14, 2015 at 9:12 AM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:
Hi Abhishek, All,

I found the problem.

My /etc/zuul/layout/layout.yaml has the following config:

jobs:
  - name: ^dsvm-tempest.*$
parameter-function: single_use_node

But in _parseConfig() in zuul/scheduler.py, it failed to find single_use_node().

fname = config_job.get('parameter-function', None)
if fname:
func = config_env.get(fname, None)
if not func:
raise Exception(Unable to find function %s % fname)

So projects section was not parsed.

Does anyone know why ?

Thanks.



On 07/14/2015 10:54 AM, Tang Chen wrote:
Hi Abhishek,

I printed the self.layout.projects in zuul/scheduler.py, it is empty.
So the project was not found.

But I did do the jenkins-jobs --flush-cache update /etc/jenkins_jobs/config/
And I did configure openstack-dev/sandbox in layout.yaml.

Do you have any idea what's wrong here ?

Thanks.

On 07/13/2015 05:58 PM, Tang Chen wrote:

On 07/13/2015 04:35 PM, Abhishek Shrivastava wrote:
Updating jobs using sudo jenkins-jobs --flush-cache update 
/etc/jenkins_jobs/config/. Also update the myvendor in examples.yaml


Sorry, I updated the jobs, restart the whole machine. But it still doesn't work.

By the way, there is no vendor in examples.yaml.

It is still this error: Project openstack-dev/sandbox not found

Anything else should I pay attention to?

Thanks.



On Mon, Jul 13, 2015 at 1:45 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:

On 07/13/2015 03:50 PM, Abhishek Shrivastava wrote:
​ Use tester or something, also are you updating the jobs or not?​

I used tester as my vendor. It doesn't work.

And what do you mean by updating the jobs ? I built the 
noop-check-cimmunitication
job once in Jenkins UI. Does it matter ? All the others are not touched.

And referring to the error, Project openstack-dev/sandbox not found, it seems 
like
somewhere the project name was wrong.

right ?


Thanks.



On Mon, Jul 13, 2015 at 1:16 PM, Tang Chen 
tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote:
Hi Abhishek,

Thanks for the quick reply.
On 07/13/2015 03:16 PM, Abhishek Shrivastava wrote:
Also check that Gearman is connecting or not through Jenkins UI.

On Mon, Jul 13, 2015 at 12:45 PM, Abhishek Shrivastava 
abhis...@cloudbyte.commailto:abhis...@cloudbyte.com wrote:
First of all, change the vendor to your vendor name in 
/etc/jenkins_jobs/config/projects.yaml file. Also, restart the zuul and zuul 
merger.

I did the check. Gearman plugin works find. In Jenkins UI, I tested the 
connection, and it succeeded.

And also, I restarted zuul and zuul merger every time I modified the yaml files.

But it doesn't

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-18 Thread Asselin, Ramy
We ran into this issue as well. I never found the root cause, but I found a 
work-around: Use neutron-networking instead of the default nova-networking.

If you’re using devstack-gate, it’s as  simple as:
export DEVSTACK_GATE_NEUTRON=1

Then run the job as usual.

Ramy

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Friday, July 17, 2015 9:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing 
with SSH timeout.

Hi Folks,

In my CI I see the following tempest tests failure for a past couple of days.

·
tempest.scenario.test_minimum_basic.TestMinimumBasicScenario.test_minimum_basic_scenario
 [361.274316s] ... FAILED

·
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
 [320.122458s] ... FAILED

·
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern
 [317.399342s] ... FAILED

·
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_compute_with_volumes
 [257.858272s] ... FAILED

The failure logs are always the same every time, i.e;



03:34:09 2015-07-17 03:21:13,256 9505 ERROR[tempest.scenario.manager] 
(TestVolumeBootPattern:test_volume_boot_pattern) Initializing SSH connection to 
172.24.5.1 failed. Error: Connection to the 172.24.5.1 via SSH timed out.

03:34:09 User: cirros, Password: None

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
Traceback (most recent call last):

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
tempest/scenario/manager.py, line 312, in get_remote_client

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
linux_client.validate_authentication()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
tempest/common/utils/linux/remote_client.py, line 62, in 
validate_authentication

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
self.ssh_client.test_connection_auth()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py,
 line 151, in test_connection_auth

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
connection = self._get_ssh_connection()

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager   File 
/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py,
 line 87, in _get_ssh_connection

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
password=self.password)

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager 
SSHTimeout: Connection to the 172.24.5.1 via SSH timed out.

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager User: 
cirros, Password: None

03:34:09 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager

03:34:09 2015-07-17 03:21:14,377 9505 INFO 
[tempest_lib.common.rehttp://tempest_lib.common.re



Because of these every job is failing, so if someone can help me regarding this 
please do reply.

--
[https://docs.google.com/uc?export=downloadid=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks  Regards,
Abhishek
Cloudbyte Inc.http://www.cloudbyte.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Cinder] Quobyte Cinder Driver revert?

2015-07-06 Thread Asselin, Ramy
HI Silvan,

A great resource to resolve such issues is the third-party ci meetings [1]. 
It’s a dedicated time slot to ask questions and get help from other community 
members such as yourself. Oftentimes, someone else has run into the same issue 
and already as an answer.

Ramy

[1] https://wiki.openstack.org/wiki/Meetings/ThirdParty


From: Silvan Kaiser [mailto:sil...@quobyte.com]
Sent: Friday, July 03, 2015 9:06 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] Quobyte Cinder Driver revert?

Hello again!
Ok, now i did find the review [1], sorry i did not earlier.

We will solve the CI issues asap in order to provide the requirements to 
recommit the Quobyte driver.
We've been trying to solve the CIs networking issue i wrote about since then 
but were unable to nail it down completely as we're only a small company and 
restricted in resources.
After the mail from Mike Perez regarding missing reports [2] i had brief 
contact with him directly via email [3] and once more on the third party 
mailing list [4].
As i did not receive a message after the replies i did not expect there to be a 
defined deadline and I did not see information about the impending revert on 
gerrit, and thus was unable to comment on that.
My apologies for that.
We're focusing on this with all the team now.

Silvan Kaiser


[1] https://review.openstack.org/#/c/191192/
[2] 
http://lists.openstack.org/pipermail/third-party-announce/2015-June/000200.html
[3] 
http://lists.openstack.org/pipermail/third-party-announce/2015-June/000213.html
[4] 
http://lists.openstack.org/pipermail/third-party-announce/2015-June/000214.html


2015-07-03 16:31 GMT+02:00 Silvan Kaiser 
sil...@quobyte.commailto:sil...@quobyte.com:
Hello!
I just found the following commit in the cinder log:

commit a3f4eed52efce50c2eb1176725bc578272949d7b
Merge: 6939b4a e896ae2
Author: Jenkins 
jenk...@review.openstack.orgmailto:jenk...@review.openstack.org
Date:   Thu Jul 2 23:14:39 2015 +

Merge Revert First version of Cinder driver for Quobyte


Is this part of some restructuring work, etc. that i did miss?
I could not find a gerrit review for this and had no prior information? I did 
not see any related information when i did my weekly checks of the cinder 
weekly meeting logs and am confused to find this commit.

We're still working on the CI issues discussed on the CI mailing list and am 
fully aware that we've to get this stably reporting. This is not a removal 
because of the CI issues?
Best regards
Silvan Kaiser


--
Dr. Silvan Kaiser
Quobyte GmbH
Boyenstr. 41 - 10115 Berlin-Mitte - Germany
+49-30-814 591 800tel:%2B49-30-814%20591%20800 - 
www.quobyte.comhttp://www.quobyte.com/http://www.quobyte.com/
Amtsgericht Berlin-Charlottenburg, HRB 149012B
Management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender



--
Dr. Silvan Kaiser
Quobyte GmbH
Boyenstr. 41 - 10115 Berlin-Mitte - Germany
+49-30-814 591 800 - 
www.quobyte.comhttp://www.quobyte.com/http://www.quobyte.com/
Amtsgericht Berlin-Charlottenburg, HRB 149012B
Management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender


--
Quobyte GmbH
Hardenbergplatz 2 - 10623 Berlin - Germany
+49-30-814 591 800 - www.quobyte.comhttp://www.quobyte.com/
Amtsgericht Berlin-Charlottenburg, HRB 149012B
management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [third-party][infra] Common OpenStack CI Solution - 'Zuul' live

2015-07-02 Thread Asselin, Ramy
All,

I’m please to say that there are now 3 components merged in the 
puppet-openstackci repo [1]
This means 3rd party ci operators can now use the same scripts that the 
OpenStack Infrastructure team uses in the official ‘Jenkins’ CI system for:


1.   Log Server

2.   Jenkins

3.   Zuul

This work is being done as part of the common-ci spec [2]

Big thanks to Fabien Boucher for completing the Zuul script refactoring, which 
went live today!
Thanks to all the reviewers for careful reviews which led to a smooth migration.

I’ve updated my repo [3]  switched all my CI systems to use it.

As a reminder, there will be a virtual sprint next week July 8-9, 2015 15:00 
UTC to finish the remaining tasks.
If you’re interested in helping out in any of the remaining tasks (Jenkins Job 
Builder, Nodepool, Logstash/Kibana, Documentation, Sample site.pp) Sign up on 
the eitherpad. [4]

Also, we can use the 3rd party meeting time slot next week to discuss plans and 
answer questions [5].
Tuesday 7/7/15 1700 UTC #openstack-meeting

Ramy
IRC: asselin

[1] https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://github.com/rasselin/os-ext-testing (forked from 
jaypipes/os-ext-testing)
[4] https://etherpad.openstack.org/p/common-ci-sprint
[5] https://wiki.openstack.org/wiki/Meetings/ThirdParty


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Manila] State of 3rd party CI

2015-06-26 Thread Asselin, Ramy
Friendly reminder that there are 3rd party CI weekly meetings [1] for us to 
come together and work out issues and find ways to make it easier to setup and 
maintain a 3rd party ci system. 

[1] 
https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings

Ramy

-Original Message-
From: Ben Swartzlander [mailto:b...@swartzlander.org] 
Sent: Friday, June 26, 2015 1:17 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Manila] State of 3rd party CI

Liberty-1 has passed and many exciting things are going on in Manila, and lots 
of exciting new features have merged or are being worked on but we cannot 
forget the slightly less-exciting topic of CI systems. Just before the summit I 
proposed a plan for CI and we agreed to it. The original thread is here:

http://lists.openstack.org/pipermail/openstack-dev/2015-May/064086.html

Most drivers are on track regarding the CI deadlines. As requested, the 
maintainers for all of the existing drivers (except one) have signed up and 
committed to implementing a CI system for Manila according to the plan on this 
etherpad:

https://etherpad.openstack.org/p/manila-driver-maintainers

The one driver without a maintainer is IBM GPFS. I know that IBM is going to 
make a decision soon about the maintainer.

Also, I would like to thank NetApp and HP for not waiting until the last minute 
and getting their CI systems reporting already!

The next deadline is liberty-2 (July 30), and by then I expect that all of the 
needed accounts in the gerrit system should exist and drivers maintainers 
should at least be able to demonstrate passing tempest tests on their drivers 
if not reporting upstream. Any failing tests should have bugs by the next 
deadline too.

Now that we have a list of maintainers I'm going to check status with each of 
you to make sure everything is on track. As I have told many people privately, 
don't be afraid to ask for help! The point of having the staged deadlines is 
not only to make sure everyone gets started early but also to identify who 
needs help and to connect them with people who can help. We have several 
resources in the community who understand CI and have helped others. I want 
everyone to be successful setting up their CI system because I don't want to 
submit a single driver removal patch in September.

-Ben Swartzlander



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Looking for help getting git-review to work over https

2015-06-11 Thread Asselin, Ramy
Try creating/updated ~/.pip/pip.conf

With contents:

[global]
proxy = http://your_proxy:port/

From: KARR, DAVID [mailto:dk0...@att.com]
Sent: Thursday, June 11, 2015 4:16 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Looking for help getting git-review to work over 
https

This is just going swimmingly.
% sudo python setup.py install
Download error on https://pypi.python.org/simple/pbr/: [Errno 110] Connection 
timed out -- Some packages may not be found!
Couldn't find index page for 'pbr' (maybe misspelled?)
Download error on https://pypi.python.org/simple/: [Errno 110] Connection timed 
out -- Some packages may not be found!
No local packages or download links found for pbr

Do I have to do something special to set the proxy for this?  I have 
“http_proxy” and “https_proxy” already set.

From: ZZelle [mailto:zze...@gmail.com]
Sent: Thursday, June 11, 2015 3:50 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Looking for help getting git-review to work over 
https

Indeed, the doc[1] is unclear
git-review can be installed using: python setup.py install or pip install .


[1]http://docs.openstack.org/infra/manual/developers.html#accessing-gerrit-over-https

On Thu, Jun 11, 2015 at 11:16 PM, KARR, DAVID 
dk0...@att.commailto:dk0...@att.com wrote:
I see.  I would guess a footnote on the instructions about this would be 
useful. Is https://github.com/openstack-infra/git-review the proper location to 
get the buildable source?  I don’t see any obvious build instructions there.

From: ZZelle [mailto:zze...@gmail.commailto:zze...@gmail.com]
Sent: Thursday, June 11, 2015 2:01 PM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Looking for help getting git-review to work over 
https

Hi David,


Following git config options are supported by git-review 
(https://review.openstack.org/116035)
   git config --global gitreview.scheme https
   git config --global gitreview.port 443
BUT the feature was merged after 1.24 (it's highlighted by your git review -vs)
so the feature is currently only available on the git-review master branch 
(which
is quite stable, i use it every day).


Cedric/ZZelle@irc


On Thu, Jun 11, 2015 at 10:14 PM, KARR, DAVID 
dk0...@att.commailto:dk0...@att.com wrote:
I followed the instructions for installing and configuring corkscrew, similar 
to what you provided here.  The result seems to indicate it did something, but 
the overall result is the same:
2015-06-11 13:07:25.866568 Running: git log --color=never --oneline HEAD^1..HEAD
2015-06-11 13:07:25.869309 Running: git remote
2015-06-11 13:07:25.872742 Running: git config --get gitreview.username
No remote set, testing 
ssh://dk0...@review.openstack.org:29418/openstack/horizon.githttp://dk0...@review.openstack.org:29418/openstack/horizon.git
2015-06-11 13:07:25.874869 Running: git push --dry-run 
ssh://dk0...@review.openstack.org:29418/openstack/horizon.githttp://dk0...@review.openstack.org:29418/openstack/horizon.git
 --all
The authenticity of host 
'[review.openstack.orghttp://review.openstack.org]:29418 (no hostip for 
proxy command)' can't be established.
RSA key fingerprint is 28:c6:42:b7:44:d2:48:64:c1:3f:31:d8:1b:6e:3b:63.
Are you sure you want to continue connecting (yes/no)? yes
ssh://dk0...@review.openstack.org:29418/openstack/horizon.githttp://dk0...@review.openstack.org:29418/openstack/horizon.git
 did not work.
Could not connect to gerrit.
Enter your gerrit username:
---

From: Paul Michali [mailto:p...@michali.netmailto:p...@michali.net]
Sent: Thursday, June 11, 2015 11:09 AM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Looking for help getting git-review to work over 
https

Do you know if you have SSH access to the outside world through the firewall?

Did you setup a proxy? I setup 'corkscrew' under Ubuntu. After installing, 
created a .ssh/config file with:

Host review.openstack.orghttp://review.openstack.org
ProxyCommand corkscrew proxy-host 80 %h %p

The proxy host is one that allows HTTP/HTTPS to outside world and corkscrew 
tunnels the SSH through to port 80.

HTHs,

PCM

On Thu, Jun 11, 2015 at 12:44 PM KARR, DAVID 
dk0...@att.commailto:dk0...@att.com wrote:
Thanks for replying.

% git review -vs
2015-06-11 09:30:38.396076 Running: git log --color=never --oneline HEAD^1..HEAD
2015-06-11 09:30:38.399021 Running: git remote
2015-06-11 09:30:38.401033 Running: git config --get gitreview.username
No remote set, testing 
ssh://dk0...@review.openstack.org:29418/openstack/horizon.githttp://dk0...@review.openstack.org:29418/openstack/horizon.git
2015-06-11 09:30:38.402988 Running: git push --dry-run 
ssh://dk0...@review.openstack.org:29418/openstack/horizon.githttp://dk0...@review.openstack.org:29418/openstack/horizon.git
 --all

[openstack-dev] [third-party][infra] Common OpenStack CI Solution - 'Jenkins' live

2015-06-10 Thread Asselin, Ramy
All,

I’m please to say that there are now 2 components merged in the 
puppet-openstackci repo [1]
This means 3rd party ci operators to use the same scripts that the OpenStack 
Infrastructure team uses in the official ‘Jenkins’ CI system for:


1.   Log Server

2.   Jenkins

Big thanks to Tristan Cacqueray for completing the Jenkins script refactoring, 
which went live today!
He did a great job, especially with managing all the reviews and patch churn, 
and now we’re all one step closer to having a reusable “OpenStack” CI system 
[2].

I’ve switched my repo [3]  CI system to use it.

Ramy

[1] https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://github.com/rasselin/os-ext-testing (forked from 
jaypipes/os-ext-testing)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra][third-party] Common-CI Virtual Sprint

2015-06-08 Thread Asselin, Ramy
I didn’t hear any objections, so I’ll plan on scheduling this sprint as 
proposed on July 8  9.

Thanks!
Ramy Asselin

From: Ricardo Carrillo Cruz [mailto:ricardo.carrillo.c...@gmail.com]
Sent: Thursday, June 04, 2015 12:14 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [infra][third-party] Common-CI Virtual Sprint

Whenever is, I'll participate.

Regards

2015-06-04 21:09 GMT+02:00 Spencer Krum 
n...@spencerkrum.commailto:n...@spencerkrum.com:
I'm in!

--
  Spencer Krum
  n...@spencerkrum.commailto:n...@spencerkrum.com

On Thu, Jun 4, 2015, at 09:22 AM, Asselin, Ramy wrote:
 Hi,

 It was nice to meet many of you at the Vancouver Infra Working Session.
 Quite a bit of progress was made finding owners for some of the common-ci
 refactoring work [1] and puppet testing work. A few patches were
 proposed, reviewed, and some merged!

 As we continue the effort over the coming weeks, I thought it would be
 helpful to schedule a  virtual sprint to complete the remaining tasks.

 GOAL: By the end of the sprint, we should be able to set up a 3rd party
 CI system using the same puppet components that the OpenStack
 infrastructure team is using in its production CI system.

 I proposed this in Tuesday's Infra meeting [1] there was general
 consensus that this would be valuable (if clear goals are documented) and
 that July 8  9 are good dates. (After the US  Canada July 1st and 4th
 holidays, not on Tuesday, and not near a Liberty Milestone)

 I would like to get comments from a broader audience on the goals and
 dates.

 You can show interest by adding your name to the etherpad [3].

 Thank you,
 Ramy
 irc: asselin



 [1]
 http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
 [2]
 http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-06-02-19.01.html
 [3] https://etherpad.openstack.org/p/common-ci-sprint



 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [infra][third-party] Common-CI Virtual Sprint

2015-06-04 Thread Asselin, Ramy
Hi,

It was nice to meet many of you at the Vancouver Infra Working Session. Quite a 
bit of progress was made finding owners for some of the common-ci refactoring 
work [1] and puppet testing work. A few patches were proposed, reviewed, and 
some merged!

As we continue the effort over the coming weeks, I thought it would be helpful 
to schedule a  virtual sprint to complete the remaining tasks.

GOAL: By the end of the sprint, we should be able to set up a 3rd party CI 
system using the same puppet components that the OpenStack infrastructure team 
is using in its production CI system.

I proposed this in Tuesday's Infra meeting [1] there was general consensus that 
this would be valuable (if clear goals are documented) and that July 8  9 are 
good dates. (After the US  Canada July 1st and 4th holidays, not on Tuesday, 
and not near a Liberty Milestone)

I would like to get comments from a broader audience on the goals and dates. 

You can show interest by adding your name to the etherpad [3].

Thank you,
Ramy
irc: asselin



[1] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[2] 
http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-06-02-19.01.html
[3] https://etherpad.openstack.org/p/common-ci-sprint



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [cinder][third-party] CI FC passthrough scripts now available on stackforge

2015-06-03 Thread Asselin, Ramy
For anyone working on 3rd party CI FC drivers:

Patrick East and I have been working on making “FC pass-through” scripts.
The main use case of these scripts is to present the FC HBAs directly inside a 
VM in order to test your FC cinder driver.

Now available in stackforge [1]
Link available in cinder FAQ [2]

It’s a working solution (3 drivers using these scripts, more using its 
precursors), but not the ‘best’ solution.  It’s open source:  so any 
improvements/bug fixes are welcome ☺

Ramy

[1] 
https://git.openstack.org/cgit/stackforge/third-party-ci-tools/tree/provisioning_scripts/fibre_channel

[2] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#FAQ

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Nodepool: puppet puts wrong key in authorized_keys in slave

2015-05-30 Thread Asselin, Ramy
Hi Eduard,

While not immediately related to your issue, if you haven’t tried using 
disk-image-builder, I strongly recommend it. Overall it’s much simpler, faster, 
and superior in every regard to create, debug, and maintain nodepool images.

I just updated my sample to use it: 
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/nodepool/nodepool.yaml.erb.sample

And very likely it will also solve your authorized_keys issue. If you look at 
the diff, you’ll see how many comments were deleted regarding getting keys and 
auth to work because it just works. Can’t recommend it enough.

Best,
Ramy

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Saturday, May 30, 2015 12:26 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] Nodepool: puppet puts wrong key in authorized_keys in 
slave

Hi,

Recently i updated nodepool and the devstack where it's supposed to create 
slaves.
After some minor issues i managed to get it running, and it is able to create 
an image and i can login to an instance created from that image using user 
ubuntu (image is trusty).

While trying to add the slave to jenkins it fails with ssh error.
After a little debugging i found that in the authorized_keys of user ubuntu is 
the correct key (so i can ssh as user ubuntu) - the one i put in the Key-pair, 
but for user jenkins there is another key which i can't find for any user in 
the jenkins master.

The authorized_keys for user jenkins contains:
# HEADER: This file was autogenerated at 2015-05-29 12:35:49 +
# HEADER: by puppet.  While it can still be managed manually, it
# HEADER: is definitely not recommended.
... then the key... and at the end: jenkins-master-2014-04-24

While for user ubuntu:
... the key from user jenkins on the master... and at the end: 
jenkins@jenkins-cinderci

I didn't make any changes to nodepool.yaml or the keys themselves.

I've been looking inside nodepool's scripts, but this looks like a puppet 
script and i don't know how to debug those.

Thanks,

Eduard
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Pip 7 released

2015-05-22 Thread Asselin, Ramy
Rob, thanks for your help. We're all set. We moved our trusted-hosts to 
definitions to the pip.conf [global] section.
Ramy
 

-Original Message-
From: Robert Collins [mailto:robe...@robertcollins.net] 
Sent: Friday, May 22, 2015 7:26 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] Pip 7 released

This is just a heads up, Donald has released pip 7, which includes wheel 
caching that should help reduce developer pain around new tox venvs, amongst 
other things. CI seems happy and green with it (yay), except for 3par, which 
I'm going to see if I can help when they get back on IRC :)

Cheers,
Rob

--
Robert Collins rbtcoll...@hp.com
Distinguished Technologist
HP Converged Cloud

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!

2015-04-21 Thread Asselin, Ramy
HI Sukhdev,

I also wonder how many folks are in that camp.
Regardless, if we can go from 85 -- 2 (or any other much smaller number), then 
that is a good thing.
Also, from an open source point of view, I’d like to see new 
contributors/vendors contributing effort on value-add innovation, and less on 
recreating/maintaining the ‘common’ portions of 3rd party ci.

Ramy

From: Sukhdev Kapur [mailto:sukhdevka...@gmail.com]
Sent: Monday, April 20, 2015 1:39 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [third-party][infra] Third-Party CI Operators: 
Let's use a common CI Solution!

Hi Ramy,

While I agree, in principal, with this line of thinking and goal, my concern 
will be how much extra work is it going to create for existing CI owners?
Our Ci system has been stable for a long time, and we put in a good amount of 
effort to get it to that point. Our CI is not based upon zuul framework. Zuul 
was still under discussion at the time when we put together our CI. We use 
Jenkins as front end, along with Gerrit triggers, and AWS for 
posting/preserving results/log.  We have dedicated back-end servers for  
testing.

My paranoia at this point will be to learn a new framework, risk breaking 
things and taking a huge effort to get things stabilized - without much 
additional ROI.
Am I overreacting here or does my argument makes sense?

I wonder how many folks will be in that camp?

Sukhdev




On Sun, Apr 19, 2015 at 10:17 PM, Asselin, Ramy 
ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote:
All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them 
running a variety of closed  open-source solutions.
Instead of individually maintaining all those similar solutions, let’s join 
together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2] to 
refactor much of what the Infrastructure team uses for the upstream “Jenkins” 
CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using the 
gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”, which 
creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or ping 
me IRC (asselin) on Freenode #openstack-infra, or join some of the third party 
ci meetings [5].

Thanks!
Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101
[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z
[5] 
https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!

2015-04-19 Thread Asselin, Ramy
All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them 
running a variety of closed  open-source solutions.
Instead of individually maintaining all those similar solutions, let’s join 
together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2] to 
refactor much of what the Infrastructure team uses for the upstream “Jenkins” 
CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using the 
gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”, which 
creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or ping 
me IRC (asselin) on Freenode #openstack-infra, or join some of the third party 
ci meetings [5].

Thanks!
Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101
[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z
[5] 
https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [cinder] Report status of Huawei Volume CI from April 1

2015-04-04 Thread Asselin, Ramy
Please update your Apache configuration to not require downloads.
Instructions to do this are here: 
http://ci.openstack.org/third_party.html#faq-frequently-asked-questions
Ramy

From: liuxinguo [mailto:liuxin...@huawei.com]
Sent: Saturday, April 04, 2015 5:47 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Fanyaohong
Subject: [openstack-dev] [cinder] Report status of Huawei Volume CI from April 1

Hello Cinder team,

·Huawei Volume CI has posted to about forty cinder reviews from April 1 
to now and will keep reporting stably.
·
·It now runs 304 tests, passed 293 and skipped 11.

The following are links to the cinder reviews our CI has posted results to, 
please check it:
https://review.openstack.org/12‍
https://review.openstack.org/163641‍
https://review.openstack.org/169430‍
https://review.openstack.org/168177‍
https://review.openstack.org/168179‍
https://review.openstack.org/169153 ‍
https://review.openstack.org/165798‍
https://review.openstack.org/167134‍
https://review.openstack.org/169653‍
https://review.openstack.org/159704‍
https://review.openstack.org/154350‍
https://review.openstack.org/169707‍
https://review.openstack.org/164527‍
https://review.openstack.org/165688‍
https://review.openstack.org/163706‍
https://review.openstack.org/144409‍
https://review.openstack.org/169781 ‍
https://review.openstack.org/169812  ‍
https://review.openstack.org/169831  ‍
https://review.openstack.org/165655‍
https://review.openstack.org/16‍
https://review.openstack.org/17‍
https://review.openstack.org/169915‍
https://review.openstack.org/170156‍
https://review.openstack.org/170157‍
https://review.openstack.org/151567‍
https://review.openstack.org/170199‍
https://review.openstack.org/170178‍
https://review.openstack.org/163232‍
https://review.openstack.org/170588‍
https://review.openstack.org/152284 ‍
https://review.openstack.org/156904‍
https://review.openstack.org/160682‍
https://review.openstack.org/170346‍
https://review.openstack.org/170616‍
https://review.openstack.org/164692‍
https://review.openstack.org/161363‍
https://review.openstack.org/170310‍
https://review.openstack.org/169858‍
https://review.openstack.org/152475‍
https://review.openstack.org/161209‍
https://review.openstack.org/155607‍
https://review.openstack.org/168901‍
https://review.openstack.org/169060‍
https://review.openstack.org/160209‍
https://review.openstack.org/163910‍
https://review.openstack.org/159856‍
https://review.openstack.org/147476‍

·Or you can just check it at here:
·https://review.openstack.org/#/q/project:openstack/cinder,n,z
·
I will pay very close attention to the status of our CI and keep it running 
stably.
If there is any requirement our CI has not satisfied, please let us know.

Thanks and regards,
Liu

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFS/SA Cinder drivers (iSCSI and NFS)

2015-03-31 Thread Asselin, Ramy
Hi Diem,

Looking at: https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z

I don't see any issues, other than missing testr_results.html (nit).
You can get that using John's latest code: 
https://github.com/j-griffith/sos-ci/commit/1aa63782b1745a87c72562edcce19358f9ba79d5

Also, as explained here: http://ci.openstack.org/third_party.html#requirements, 
please add your CI contact info here: 
https://wiki.openstack.org/wiki/ThirdPartySystems

+1
Ramy

-Original Message-
From: Diem Tran [mailto:diem.t...@oracle.com] 
Sent: Tuesday, March 31, 2015 2:23 PM
To: Mike Perez
Cc: openstack-dev@lists.openstack.org; openstack-in...@lists.openstack.org; 
Alka Deshpande
Subject: Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please 
re-consider Oracle ZFS/SA Cinder drivers (iSCSI and NFS)

Hi Mike,

This is just a gentle status check from our team:

We are aware of the requirements where the CI needs to report in a stable 
fashion for at least 5 days prior to 4/6/2015. Hence we'd like to know if you 
and the Cinder team have any issue with the current state of Oracle ZFSSA CI. 
We want to handle it immediately and stay complied with the requirements.

Thank you,
Diem.


On 03/26/2015 01:28 PM, Diem Tran wrote:
 Hi Mike, The CI has been adjusted to run 304 tests since 3/24/2015
 evening: 
 https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z

 Here are examples of recent success runs:
 https://review.openstack.org/#/c/167080/
 https://review.openstack.org/#/c/165763/
 https://review.openstack.org/#/c/166823/
 https://review.openstack.org/#/c/166689/
 https://review.openstack.org/#/c/167366/
 https://review.openstack.org/#/c/166164/

 We delayed our response until now because we want to get proofs of 
 success runs and make sure our CI complies with the requirements. We 
 believe it does now.

 Thank you for your contribution and effort in keeping us updated on 
 this matter.

 Diem.
 On 03/24/2015 05:28 PM, Mike Perez wrote:
 On 18:20 Mon 23 Mar , Diem Tran wrote:
 Hello Cinder team,

 Oracle ZFSSA CI has been reporting since March 20th. Below is a link 
 to the list of results the CI already posted:

 https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z

 Our CI system will be running and reporting results from now on, 
 hence I kindly request that you accept our CI results and consider 
 re-integrating our drivers back in Kilo RC.

 If there is any concern, please let us know.
 Diem,

 I appreciate your team getting back to us on the CI. It appears your 
 CI is running 247 tests, when it should be running 304. Please verify 
 you're running tempest as followed in the instructions here:

 https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_t
 ests_do_I_use.3F


 Once this issue is resolved, I'll continue to monitor the stability, 
 and based on that make a decision for readding the driver.




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [OpenStack-Infra] [cinder] Status of Huawei Volume CI

2015-03-25 Thread Asselin, Ramy
I checked 3 random ones and I couldn't see any log files.

Ramy

https://review.openstack.org/#/c/144409/
Patch Set 6: Build succeeded. - huawei-iscsi-dsvm-tempest-full ...

Mar 1 11:54 PM


http://125.70.13.170:8088/huawei-iscsi-dsvm-tempest-full/357  Not found
http://125.70.13.170:8088/huawei-fc-dsvm-tempest-full/26 Not found
Both links fail to show any logs

https://review.openstack.org/#/c/164692/
Huawei Volume CI check

Mar 22, 2015 1:37 PM

huawei-iscsi-dsvm-tempest-fullhttp://125.70.13.170:8088/huawei-iscsi-dsvm-tempest-full/414

FAILURE in 12m 54s

huawei-fc-dsvm-tempest-fullhttp://125.70.13.170:8088/huawei-fc-dsvm-tempest-full/99

FAILURE in 11m 03s


Both links fail to show any logs

https://review.openstack.org/#/c/167080/
Huawei Volume CI check

Mar 24, 2015 6:47 AM

huawei-iscsi-dsvm-tempest-fullhttp://125.70.13.170:8088/huawei-iscsi-dsvm-tempest-full/432

UNSTABLE in 15m 32s

huawei-fc-dsvm-tempest-fullhttp://125.70.13.170:8088/huawei-fc-dsvm-tempest-full/122

SUCCESS in 17m 09s


Both links fail to show any logs

From: liuxinguo [mailto:liuxin...@huawei.com]
Sent: Wednesday, March 25, 2015 5:45 AM
To: OpenStack Development Mailing List (not for usage questions); 
openstack-in...@lists.openstack.org
Cc: Fanyaohong
Subject: [openstack-dev] [OpenStack-Infra] [cinder] Status of Huawei Volume CI

Hello Cinder team,

*Huawei Volume CI has been reporting since Decemberapp:ds:December 20 
th 2014. Now it runs
*two tempest jobs for Huawei 18000 iSCSI driver and Huawei 18000 FC 
driver.
*Considering that our drivers have been moved for the upstream, I have 
added some
*code to ensureapp:ds:ensure the jobs run against the real storage 
backend when building devstack.
*
*And now the CI is reporting much more stably and will keep running and 
reporting from now on.
*Below is a link shows the recentlyapp:ds:recently posted results 
from the CI:

https://review.openstack.org/#/q/reviewer:%22Huawei+Volume+CI%22,n,z

I kindly request that you accept our CI result and consider re-integrating
our 18000 iSCSI and 18000 FC drivers back in Kilo RC.

If there is any concern, please let us know.

Thanks and regards,
Liu


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [cinder]Driver broken

2015-03-25 Thread Asselin, Ramy
Hi Eduard,

Your third party ci reported success on that patch. The tempest volume tests 
include attached  detaches. Seems your CI is not running them?
http://packages.cloudfounders.com/ci_logs/47/85847/47/check/openvstorage-cinder-functionality/b073fb9/console.html

CloudFounders OpenvStorage CI check

Mar 10, 2015 9:14 AM

openvstorage-cinder-functionalityhttp://packages.cloudfounders.com/ci_logs/47/85847/47/check/openvstorage-cinder-functionality/b073fb9

SUCCESS in 37m 16s


Ramy

From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Wednesday, March 25, 2015 8:05 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [cinder]Driver broken

Hi,

Just reported an issue: https://bugs.launchpad.net/cinder/+bug/1436367
Seems to be related to https://review.openstack.org/#/c/85847/ which introduced 
another parameter to be passed to the driver, but our driver didn't get updated 
so detach_volume fails for us.

How can we get this fixed asap?

Thanks,
Eduard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] Cinder Review Inbox Was RE: Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

2015-03-24 Thread Asselin, Ramy
Changing the topic.

Mike Perez did include a Cinder Review Inbox link on the main Cinder Wiki page.
https://wiki.openstack.org/wiki/Cinder#Resources

Not sure how many people/cores use that link but that could be a step towards 
what you’re asking for.
The query should probably be proposed to 
http://git.openstack.org/cgit/stackforge/gerrit-dash-creator/tree/dashboards

Ramy


From: Rochelle Grober [mailto:rochelle.gro...@huawei.com]
Sent: Tuesday, March 24, 2015 12:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: 
[cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

One other item I’d like to bring up.

While Nova and Neutron are well distributed around the globe and have Core 
Reviewers on IRC in the Asia daytime, some other projects are not so well 
distributed as yet.  A problem I noticed a number of times is that an Asia 
based developer will post to the mailing list to get some attention for  
his/her patch.  This is frowned upon in the community, but when there are few 
to no Core Reviewers in IRC, getting that first core review can be difficult.  
Emailing the PTL is something I’m sure the PTLs would like to limit as they are 
already swamped.  So, how do we get timely first core review of patches in 
areas of the world where Core presence in IRC is slim to none?

I can think of a few options but they don’t seem great:

· A filter for dashboards that flags reviews with multiple +1s and no 
core along with a commitment of the Core team to perform a review within x 
number of days

· A separate mailing list for project review requests

· Somehow queueing requests in the IRC channel so that offline 
developers can easily find review requests when looking at channel logs

· ???

Solving this issue could help not just Third Party developers, but all of 
OpenStack and make the community more inviting to Asian and Australian (and 
maybe European and African) developers.

--Rocky

From: Rochelle Grober [mailto:rochelle.gro...@huawei.com]
Sent: Monday, March 23, 2015 14:51
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: 
[cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

I’d like to suggest that the myriad wiki pages and spreadsheets for Third Party 
CI also be consolidated to a more manageable count.  Just looking for 
maintainers contact, you can find information (often conflicting) in 
Stackalytics, on the ThirdPartyDrivers page, on the Cinder PTL’s google doc and 
who knows where else for the Neutron maintainers.  Even finding which tests to 
run takes linking through a number of Cinder wiki pages.

The teams have done a great job documenting a process that started out as lore, 
but I think the beginning of L would be a great time to revisit and reorganize 
the documentation for clarity, conciseness and single locations (version 
controlled) of critical information.

--Rocky

From: Patrick East [mailto:patrick.e...@purestorage.com]
Sent: Monday, March 23, 2015 14:38
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: 
[cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

On Mon, Mar 23, 2015 at 12:59 PM, Stefano Maffulli 
stef...@openstack.orgmailto:stef...@openstack.org wrote:
On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote:
 We've been talking about CI's for a year. We started talking about CI 
 deadlines
 in August. If you post a driver for Kilo, it was communicated that you're
 required to have a CI by the end of Kilo [1][2][3][4][5][6][7][8]. This
 should've been known by your engineers regardless of when you submitted your
 driver.

Let's work to fix the CI bits for Liberty and beyond. I have the feeling
that despite your best effort to communicate deadlines, some quite
visible failure has happened.

I think the only failure is on the side of any driver maintainers who did not 
make the deadlines. From my perspective (as one of the driver maintainers who 
did setup a CI system and a developer working on Cinder) this whole process has 
been a success. The test coverage has sky rocketed for Cinder, driver 
maintainers are forced to be a bit more active in the community, and the code 
base (in theory) no longer has volume drivers in tree that we don't know if 
they actually work or not. This is, in my opinion, a huge win for the project.

You've been clear about Cinder's deadlines, I've been trying to add them
also to the weekly newsletter, too.

To the people whose drivers don't have their CI completed in time: what
do you suggest should change so that you won't miss the deadlines in the
future? How should the processes and tool be different so you'll be
successful with your OpenStack-based products?

For anyone who struggled 

Re: [openstack-dev] [cinder] Third Party CI

2015-03-23 Thread Asselin, Ramy
All vendors working on cinder third party ci are encouraged to attend the 3rd 
party ci meetings.

https://wiki.openstack.org/wiki/Meetings/ThirdParty

This is a great place to ask questions, report issues, and share solutions.

Ramy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] openstack storage configaration file(cinder-service)

2015-03-20 Thread Asselin, Ramy
You can follow the basic instructions here in FAQ:
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers

Ramy


From: Kamsali, RaghavendraChari (Artesyn) 
[mailto:raghavendrachari.kams...@artesyn.com]
Sent: Friday, March 20, 2015 4:20 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] openstack storage configaration file(cinder-service)

Hi,

Anyone can help how to configure local.conf file for storage node via cinder 
service in devstack.



Thanks and Regards,
Raghavendrachari kamsali | Software Engineer II  | Embedded Computing
Artesyn Embedded Technologies | 5th Floor, Capella Block, The V, Madhapur| 
Hyderabad, AP 500081 India
T +91-40-66747059 | M +919705762153

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [cinder] [Third-party-announce] Cinder Merged patch broke HDS driver

2015-03-05 Thread Asselin, Ramy
Marcus,

Don’t turn off ci, because then you could miss another regression.

Instead, simply exclude that test case:
e.g.
export 
DEVSTACK_GATE_TEMPEST_REGEX=^(?=.*tempest.api.volume)(?!.*test_snapshots_actions).*

Ramy


From: Marcus Vinícius Ramires do Nascimento [mailto:marcus...@gmail.com]
Sent: Wednesday, March 04, 2015 1:29 PM
To: openstack-dev@lists.openstack.org; Announcements for third party CI 
operators.
Subject: [openstack-dev] [cinder] [Third-party-announce] Cinder Merged patch 
broke HDS driver

Hi folks,

This weekend, the patch Snapshot and volume objects 
(https://review.openstack.org/#/c/133566) was merged and this one broke our HDS 
HBSD driver and the respective CI.

When CI tries to run tempest.api.volume.admin.test_snapshots_actions the 
following error is shown:

2015-03-04 14:00:34.368 ERROR oslo_messaging.rpc.dispatcher 
[req-c941792b-963f-4a7d-a6ac-9f1d9f823fd1 915289d113dd4f9db2f2a792c18b3564 
984bc8d228c8497689dde60dc2b8f300] Exception during messag
e handling: 'class 'cinder.objects.snapshot.Snapshot'' object has no 
attribute 'snapshot_metadata'
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher Traceback (most 
recent call last):
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
142, in _dispatch_and_reply
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
186, in _dispatch
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
130, in _do_dispatch
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/osprofiler/profiler.py, line 105, in 
wrapper
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher return f(*args, 
**kwargs)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/opt/stack/cinder/cinder/volume/manager.py, line 156, in lso_inner1
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher return 
lso_inner2(inst, context, snapshot, **kwargs)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py, line 
431, in inner
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher return f(*args, 
**kwargs)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/opt/stack/cinder/cinder/volume/manager.py, line 155, in lso_inner2
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher return 
f(*_args, **_kwargs)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/opt/stack/cinder/cinder/volume/manager.py, line 635, in delete_snapshot
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher snapshot.save()
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, line 82, in 
__exit__
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/opt/stack/cinder/cinder/volume/manager.py, line 625, in delete_snapshot
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher 
self.driver.delete_snapshot(snapshot)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/osprofiler/profiler.py, line 105, in 
wrapper
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher return f(*args, 
**kwargs)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/opt/stack/cinder/cinder/volume/drivers/hitachi/hbsd_iscsi.py, line 314, in 
delete_snapshot
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher 
self.common.delete_snapshot(snapshot)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/opt/stack/cinder/cinder/volume/drivers/hitachi/hbsd_common.py, line 635, in 
delete_snapshot
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher is_vvol = 
self.get_snapshot_is_vvol(snapshot)
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/opt/stack/cinder/cinder/volume/drivers/hitachi/hbsd_common.py, line 189, in 
get_snapshot_is_vvol
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher return 
self.get_is_vvol(snapshot, 'snapshot_metadata')
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher   File 
/opt/stack/cinder/cinder/volume/drivers/hitachi/hbsd_common.py, line 183, in 
get_is_vvol
2015-03-04 14:00:34.368 TRACE oslo_messaging.rpc.dispatcher return 
self.get_value(obj, name, 'type') 

Re: [openstack-dev] [infra] Infra cloud: infra running a cloud for nodepool

2015-02-24 Thread Asselin, Ramy
I think this is really neat. As a 3rd party ci operator managing a small 
nodepool cloud, leveraging #3 would be really great!

Ramy

-Original Message-
From: James E. Blair [mailto:cor...@inaugust.com] 
Sent: Tuesday, February 24, 2015 1:19 PM
To: openstack-in...@lists.openstack.org
Cc: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [infra] Infra cloud: infra running a cloud for nodepool

A group of folks from HP is interested in starting an effort to run a cloud as 
part of the Infrastructure program with the purpose of providing resources to 
nodepool for OpenStack testing.  HP is supplying two racks of machines, and we 
will operate each as an independent cloud.
I think this is a really good idea, and will do a lot for OpenStack.

Here's what we would get out of it:

1) More test resources.  The primary goal of this cloud will be to provide more 
instances to nodepool.  This would extend our pool to include a third provider 
meaning that we are more resilient to service disruptions, and increase our 
aggregate capacity meaning we can perform more testing more quickly.  It's hard 
to say for certain until we have something spun up that we can benchmark, but 
we are hoping for somewhere between an additional 50% to 100% of our current 
capacity.

2) Closing the loop between OpenStack developers and ops.  This cloud will be 
deployed as often as we are able (perhaps daily, perhaps less often, depending 
on technology) meaning that if it is not behaving in a way developers like, 
they can fix it fairly quickly.

3) A fully open deployment.  The infra team already runs a large logstash and 
elasticsearch system for finding issues in devstack runs.
We will deploy the same technology (and perhaps more) to make sure that anyone 
who wants to inspect the operational logs from the running production cloud is 
able to do so.  We can even run the same elastic-recheck queries to see if 
known bugs are visible in production.
The cloud will be deployed using the same tools and processes as the rest of 
the project infrastructure, meaning anyone can edit the modules that deploy the 
cloud to make changes.

How is this different from the TripleO cloud?

The primary goal of the TripleO cloud is to provide test infrastructure so that 
the TripleO project can run tests that require real hardware and complex 
environments.  The primary purpose of the infra cloud will be to run a 
production service that will stand alongside other cloud providers to supply 
virtual machines to nodepool.

What about the infra team's aversion to real hardware?

It's true that all of our current resources are virtual, and this would be 
adding the first real, bare-metal, machines to the infra project.
However, there are a number of reasons I feel we're ready to take that step now:

* This cloud will stand alongside two others to provide resources to
  nodepool.  If it completely fails, infra will continue to operate; so
  we don't need to be overly concerned with uptime and being on-call,
  etc.

* The deployment and operation of the cloud will use the same technology
  and processes as the infra project currently uses, so there should be
  minimal barriers for existing team members.

* A bunch of new people will be joining the team to help with this.  We
  expect them to become fully integrated with the rest of infra, so that
  they are able to help out in other areas and the whole team expands
  its collective capacity and expertise.

If this works well, it may become a template for incorporating other hardware 
contributions into the system.

Next steps:

We've started the process of identifying the steps to make this happen, as well 
as answering some deployment questions (specifics about technology, topology, 
etc).  There is a StoryBoard story for the effort:

  https://storyboard.openstack.org/#!/story/2000175

And some notes that we took at a recent meeting to bootstrap the effort:

  https://etherpad.openstack.org/p/InfraCloudBootcamp

I think one of the next steps is to actually write all that up and push it up 
as a change to the system-config documentation.  Once we're certain we agree on 
all of that, it should be safe to divide up many of the remaining tasks.

-Jim

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Openstack][dev][Zuul] Merge Failed Error in CI - GitPython Error

2015-01-27 Thread Asselin, Ramy
Punith,

I think it’s because when you installed fresh again on 14.04, the zuul 
GitPython dependency was updated to the latest.

I proposed this zuul patch to fix it: https://review.openstack.org/#/c/149336/

Ramy

From: Punith S [mailto:punit...@cloudbyte.com]
Sent: Tuesday, January 27, 2015 4:33 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Openstack Team
Subject: Re: [openstack-dev] [Openstack][dev][Zuul] Merge Failed Error in CI - 
GitPython Error

Hi the merge fail error that we reported in ubuntu 12.04 has been solved in the 
new ubuntu 14.04 CI master setup.

many thanks to ramy on the update of the repo :) 
https://github.com/rasselin/os-ext-testing

cheers!

On Fri, Jan 16, 2015 at 4:58 PM, Punith S 
punit...@cloudbyte.commailto:punit...@cloudbyte.com wrote:

Hi stackers,

i'm running CI for openstack cinder patches, when zuul reads a new patch from 
gerrit, it tries to merge the patch to it's own cinder repo 
@/var/lib/zuul/git/openstack/cinder

and returns the comment to gerrit saying

[cid:image001.jpg@01D03A03.67046AC0]

hence it is failing to issue the tempest-job in jenkins via gearman !!!

on checking the trace the error seems to come from GitPython 0.3.2.1
​
the zuul/merger-debug log snapshot ref - http://paste.openstack.org/show/158218/


raise ValueError(Failed to parse line: %r % line)
ValueError: Failed to parse line: 'Total 9 (delta 7), reused 9 (delta 7)''


is this a problem of python git ?

i'm using ubuntu 12.04 and git 1.7


thanks

regards,

punith s
cloudbyte.comhttp://cloudbyte.com



--
regards,

punith s
cloudbyte.comhttp://cloudbyte.com



--
regards,

punith s
cloudbyte.comhttp://cloudbyte.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Openstack][infra] Zuul-Merger Error in CI

2015-01-27 Thread Asselin, Ramy
FYI, it wasn’t a change to my repo, but to openstack upstream that solved the 
12.04 -- 14.04 issue: https://review.openstack.org/#/c/141518/
So this will help anyone using the Openstack-Infra zuul puppet modules!
Ramy

From: Punith S [mailto:punit...@cloudbyte.com]
Sent: Tuesday, January 27, 2015 4:32 AM
To: openstack-in...@lists.openstack.org; OpenStack Development Mailing List 
(not for usage questions)
Cc: Asselin, Ramy
Subject: Re: [Openstack][infra] Zuul-Merger Error in CI

Hi the merge fail error that we reported in ubuntu 12.04 has been solved in the 
new ubuntu 14.04 CI master setup.

many thanks to ramy on the update of the repo :) 
https://github.com/rasselin/os-ext-testing

cheers!

On Thu, Jan 8, 2015 at 7:16 PM, Punith S 
punit...@cloudbyte.commailto:punit...@cloudbyte.com wrote:
hi,

i'm running CI for openstack cinder patches, when zuul reads a new patch from 
gerrit, it tries to merge the patch to it's own cinder repo 
@/var/lib/zuul/git/openstack/cinder

and returns the comment to gerrit saying

[cid:image001.jpg@01D03A03.B7884B60]

hence it is failing to issue the dsvm-tempest-job in jenkins via gearman !!!
​
the zuul/merger-debug log sanpshot

2015-01-08 19:03:43,320 DEBUG zuul.MergeServer: Got merge job.
2015-01-08 19:03:43,321 DEBUG zuul.Merger: Merging for change 145778,1.
2015-01-08 19:03:43,321 DEBUG zuul.Merger: Processing refspec 
refs/changes/78/145778/1 for project openstack/cinder / master ref 
Zbd4a4ad6ff3741c68ce382afa6d8df84
2015-01-08 19:03:43,383 DEBUG zuul.Merger: Unable to find commit for ref 
master/Zbd4a4ad6ff3741c68ce382afa6d8df84
2015-01-08 19:03:43,384 DEBUG zuul.Merger: No base commit found for 
(u'openstack/cinder', u'master')
2015-01-08 19:03:43,384 DEBUG zuul.Repo: Resetting repository 
/var/lib/zuul/git/openstack/cinder
2015-01-08 19:03:43,385 DEBUG zuul.Repo: Updating repository 
/var/lib/zuul/git/openstack/cinder
2015-01-08 19:03:54,507 DEBUG zuul.Repo: Checking out 
5993660498f44e96b0f35ccc0f4d4a4c7b430363
2015-01-08 19:04:02,685 ERROR zuul.Merger: Exception while merging a change:
Traceback (most recent call last):
  File /usr/local/lib/python2.7/dist-packages/zuul/merger/merger.py, line 
234, in _mergeChange
commit = repo.merge(item['refspec'], 'resolve')
  File /usr/local/lib/python2.7/dist-packages/zuul/merger/merger.py, line 
132, in merge
self.fetch(ref)
  File /usr/local/lib/python2.7/dist-packages/zuul/merger/merger.py, line 
145, in fetch
origin.fetch(ref)
  File /usr/local/lib/python2.7/dist-packages/git/remote.py, line 598, in 
fetch
return self._get_fetch_info_from_stderr(proc, progress or RemoteProgress())
  File /usr/local/lib/python2.7/dist-packages/git/remote.py, line 540, in 
_get_fetch_info_from_stderr
for err_line, fetch_line in zip(fetch_info_lines, fetch_head_info))
  File /usr/local/lib/python2.7/dist-packages/git/remote.py, line 540, in 
genexpr
for err_line, fetch_line in zip(fetch_info_lines, fetch_head_info))
  File /usr/local/lib/python2.7/dist-packages/git/remote.py, line 252, in 
_from_line
raise ValueError(Failed to parse line: %r % line)
ValueError: Failed to parse line: 'Total 7 (delta 5), reused 7 (delta 5)'


is this a problem of python git ?

i'm using ubuntu 12.04 and git 1.7


thanks in advance
--
regards,

punith s
cloudbyte.comhttp://cloudbyte.com



--
regards,

punith s
cloudbyte.comhttp://cloudbyte.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Cinder][3rd CI] Confused about “*real* storage backend”requirement for 3rd CI.

2015-01-23 Thread Asselin, Ramy
Another ‘sample’ you can use is here: 
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L2

Ramy

From: Bharat Kumar [mailto:bharat.kobag...@redhat.com]
Sent: Thursday, January 22, 2015 10:01 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Cinder][3rd CI] Confused about “*real* storage 
backend”requirement for 3rd CI.


On 01/22/2015 05:39 PM, Duncan Thomas wrote:
Please take a look at 
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers to learn how to 
configure devstack to use your driver rather than LVM.

On 22 January 2015 at 13:28, liuxinguo 
liuxin...@huawei.commailto:liuxin...@huawei.com wrote:

Hi Mike,



I received a email named “All Cinder Drivers Must Have a Third Party CI By 
March 19th 2015” and I feel confused about the “*real* storage backend”.



One of the requirements is: Run Tempest [5][6] volume tests against the 
devstack environment that's hooked up to your *real* storage backend.


• And my confusion is:
• Every time the CI is triggered by a newly came patch, the 3rd CI will 
build a new devstack environment and create a default cinder.conf file whick 
will set the backend to “lvmdriver-1” automatically. And the tempest will run 
against “lvmdriver-1”. So what’s the meaning for a *real* storage backend since 
the cinder.conf will be set to use “lvmdriver-1” automatically for every newly 
came patch ? And how should I configure the cinder.conf file to run the tempest 
for the newly came driver patch came from different venders since different 
venders need different configuration for cinder.conf file and need different 
storage backend. I mean, does our CI should run tempest against our *real* 
storage backend for every newly came driver patch in cinder?

Liu,

Yes, by default DevStack configures cinder with LVM. But we can customize 
DevStack to configure cinder with our own backend (real storage backend).

Below is the link to the path, enables Automatic Configuration of GlusterFS for 
Cinder using devstack:
https://review.openstack.org/#/c/133102/

And also below it the link to Configure CEPH with Cinder using devstack:
https://review.openstack.org/#/c/65113/

Above two are old way of real storage plugin implementation. Sean Dague 
proposed a new way of devstack plugin implementation. Have a look at below two 
links:
https://review.openstack.org/#/c/142805/
https://review.openstack.org/#/c/142805/7/doc/source/plugins.rst

Thanks and regards,
Liu

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Duncan Thomas




__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--

Warm Regards,

Bharat Kumar Kobagana

Software Engineer

OpenStack Storage – RedHat India

Mobile - +91 9949278005
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] sos-ci for cinder scst

2015-01-18 Thread Asselin, Ramy
Hi Nikesh,

Not familiar with sos-ci, but in general, for drivers that are not yet in-tree, 
you’ll want to use the gerrit event patch referenced, then apply (e.g. cherry 
pick) the patch that contains the out-of-tree driver on top.

Ramy

From: Nikesh Kumar Mahalka [mailto:nikeshmaha...@vedams.com]
Sent: Friday, January 16, 2015 11:56 PM
To: OpenStack Development Mailing List (not for usage questions); John Griffith
Cc: Sreedhar Varma
Subject: [openstack-dev] sos-ci for cinder scst

Hi,
localconf.base file in sos-ci/sos-ci/tempates have

CINDER_BRANCH = master
volume_driver=cinder.volume.drivers.solidfire.SolidFireDriver
similarly in our localconf.base file,we have

CINDER_BRANCH = master
[[post-config|$CINDER_CONF]]
[lvmdriver-1]
iscsi_helper=scstadmin
volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver

when sos-ci launch instance and try to install
devstack with CINDER_BRANCH=gerrit event patch reference,cinder-volume service 
is unable to start.
Because our code is not in master for this local.conf to be run by 
LVMISCSIDriver.

As far we know,we should not give CINDER_BRANCH=refs/changes/78/145778/1
in our localconf.base,because sos-ci is setting CINDER_BRANCH with gerrit
event stream events patch reference.


Regards
Nikesh
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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.RequestAbortedExceptionhttp://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 
ramy.asse...@hp.commailto: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.commailto: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 
ramy.asse...@hp.commailto: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.commailto: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

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 
eduard.ma...@cloudfounders.commailto: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.RequestAbortedExceptionhttp://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 
ramy.asse...@hp.commailto: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.commailto: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 
ramy.asse...@hp.commailto: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.commailto: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

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 
ramy.asse...@hp.commailto: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.commailto: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.136mailto: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

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

2015-01-12 Thread Asselin, Ramy
-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 module
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 module
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.commailto: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 
ramy.asse...@hp.commailto:ramy.asse...@hp.com 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.commailto: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.commailto: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 
fu...@yuggoth.orgmailto: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.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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



--

Eduard Biceri Matei, Senior Software Developer

www.cloudfounders.comhttp://www.cloudfounders.com/

 | eduard.ma...@cloudfounders.commailto: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

Re: [openstack-dev] [Cinder] Cutoff deadlines for cinder drivers

2015-01-11 Thread Asselin, Ramy
Feel free to join any of the 3rd party 'mentoring' meetings on IRC Freenode 
#openstack-meeting to help get started, work through issues, etc. 

Third Party meeting for all aspects of Third Party needs: Mondays at 1500 UTC 
and Tuesdays at 0800 UTC. Everyone interested in any aspect Third Party process 
is encouraged to attend. [1]

[1] https://wiki.openstack.org/wiki/Meetings/ThirdParty

Ramy

-Original Message-
From: Mike Perez [mailto:thin...@gmail.com] 
Sent: Sunday, January 11, 2015 6:53 PM
To: jsbry...@electronicjungle.net; OpenStack Development Mailing List (not for 
usage questions)
Subject: Re: [openstack-dev] [Cinder] Cutoff deadlines for cinder drivers

On 21:00 Sat 10 Jan , Jay S. Bryant wrote:
 I think what we discussed was that existing drivers were supposed to 
 have something working by the end of k-2, or at least have something 
 close to working.
 
 For new drivers they had to have 3rd party CI working by the end of Kilo.
 
 Duncan, correct me if I am wrong.
 
 Jay
 On 01/10/2015 04:52 PM, Mike Perez wrote:
 On 14:42 Fri 09 Jan , Ivan Kolodyazhny wrote:
 Hi Erlon,
 
 We've got a thread mailing-list [1] for it and some details in wiki [2].
 Anyway, need to get confirmation from our core devs and/or Mike.
 
 [1]
 http://lists.openstack.org/pipermail/openstack-dev/2014-October/0495
 12.html
 [2]
 https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testi
 ng_requirements_for_Kilo_release_and_beyond
 
 Regards,
 Ivan Kolodyazhny
 
 On Fri, Jan 9, 2015 at 2:26 PM, Erlon Cruz sombra...@gmail.com wrote:
 
 Hi all, hi cinder core devs,
 
 I have read on IRC discussions about a deadline for drivers vendors 
 to have their CI running and voting until kilo-2, but I didn't find 
 any post on this list to confirm this. Can anyone confirm this?
 
 Thanks,
 Erlon
 We did discuss and agree in the Cinder meeting that the deadline 
 would be k-2, but I don't think anyone reached out to the driver 
 maintainers about the deadline. Duncan had this action item [1], perhaps he 
 can speak more about it.
 
 [1] - 
 http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19
 -16.00.html
 

That is correct [1]. However, I don't think there was any warning given to 
existing drivers [2]. If Duncan can confirm this is the case, I would recommend 
fair warning go out for the end of Kilo for existing drivers as well.

[1] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
[2] - 
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html

--
Mike Perez

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
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 
patrick.e...@purestorage.commailto: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 
fu...@yuggoth.orgmailto: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.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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



--

Eduard Biceri Matei, Senior Software Developer

www.cloudfounders.comhttp://www.cloudfounders.com/

 | eduard.ma...@cloudfounders.commailto: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] [Cinder] how to delete a volume which is in error_deleting state

2015-01-05 Thread Asselin, Ramy
HI Eli,

In the UI, got to Admin -- Volumes  select desired volume.

[cid:image001.png@01D028F0.E93AA0A0]

Then click the drop down for the volume and pick “Update Volume Status”.

[cid:image002.png@01D028F0.E93AA0A0]

You can then change the stats to anything you like.

[cid:image003.png@01D028F0.E93AA0A0]

Ramy

From: Eli Qiao [mailto:ta...@linux.vnet.ibm.com]
Sent: Sunday, January 04, 2015 9:32 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] how to delete a volume which is in 
error_deleting state


在 2015年01月05日 13:10, Asselin, Ramy 写道:
Before getting into the database, try the cinder reset-state command. It’s 
available in the horizon ui starting in Juno.
Otherwise use the command line [1].

Ramy
[1] http://docs.openstack.org/cli-reference/content/cinderclient_commands.html

 Hi Punith, the command line is really help , thanks.
but I am not sure I found it in horizon ui(latest upstream version), is there a 
button , or menu to call cinder reset-state in ui ?


From: Punith S [mailto:punit...@cloudbyte.com]
Sent: Sunday, January 04, 2015 9:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] how to delete a volume which is in 
error_deleting state

Hi Eli,

you have to log-in to MySQL cinder database , and try deleting the required 
volume from the volumes table using the id.
if it fails due to foreign key constraints in volume metadata table, try 
deleting the corresponding volume metadata and then try to delete the required 
volume row.

thanks

On Mon, Jan 5, 2015 at 7:22 AM, Eli Qiao 
ta...@linux.vnet.ibm.commailto:ta...@linux.vnet.ibm.com wrote:

hi all,
how to delete a cinder volume which is in error_deleting status ?
I don't find force delete options in 'cinder delete',  then how we fix it if we 
got such situation ?
[tagett@stack-01 devstack]$ cinder list
+--++-+--+-+--+--+
|  ID  | Status | Name| Size | 
Volume Type | Bootable | Attached to  |
+--++-+--+-+--+--+
| 3e0acd0a-f28f-4fe3-b6e9-e65d5c40740b | in-use | with_cirros |  4   | 
lvmdriver-1 |   true   | 428f0235-be54-462f-8916-f32965d42e63 |
| 7039c683-2341-4dd7-a947-e35941245ec4 | error_deleting | None|  4   | 
lvmdriver-1 |  false   |  |
| d576773f-6865-4959-ba26-13602ed32e89 | error_deleting | None|  4   | 
lvmdriver-1 |  false   |  |
+--++-+--+-+--+--+
[tagett@stack-01 devstack]$ cinder delete  7039c683-2341-4dd7-a947-e35941245ec4
Delete for volume 7039c683-2341-4dd7-a947-e35941245ec4 failed: Bad Request 
(HTTP 400) (Request-ID: req-e4d8cdd9-6ed5-4a7f-81de-7f38f2163d33)
ERROR: Unable to delete any of specified volumes.




--

Thanks,

Eli (Li Yong) Qiao

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



--
regards,

punith s
cloudbyte.comhttp://cloudbyte.com




___

OpenStack-dev mailing list

OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--

Thanks,

Eli (Li Yong) Qiao
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Cinder] how to delete a volume which is in error_deleting state

2015-01-04 Thread Asselin, Ramy
Before getting into the database, try the cinder reset-state command. It’s 
available in the horizon ui starting in Juno.
Otherwise use the command line [1].

Ramy
[1] http://docs.openstack.org/cli-reference/content/cinderclient_commands.html


From: Punith S [mailto:punit...@cloudbyte.com]
Sent: Sunday, January 04, 2015 9:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] how to delete a volume which is in 
error_deleting state

Hi Eli,

you have to log-in to MySQL cinder database , and try deleting the required 
volume from the volumes table using the id.
if it fails due to foreign key constraints in volume metadata table, try 
deleting the corresponding volume metadata and then try to delete the required 
volume row.

thanks

On Mon, Jan 5, 2015 at 7:22 AM, Eli Qiao 
ta...@linux.vnet.ibm.commailto:ta...@linux.vnet.ibm.com wrote:

hi all,
how to delete a cinder volume which is in error_deleting status ?
I don't find force delete options in 'cinder delete',  then how we fix it if we 
got such situation ?
[tagett@stack-01 devstack]$ cinder list
+--++-+--+-+--+--+
|  ID  | Status | Name| Size | 
Volume Type | Bootable | Attached to  |
+--++-+--+-+--+--+
| 3e0acd0a-f28f-4fe3-b6e9-e65d5c40740b | in-use | with_cirros |  4   | 
lvmdriver-1 |   true   | 428f0235-be54-462f-8916-f32965d42e63 |
| 7039c683-2341-4dd7-a947-e35941245ec4 | error_deleting | None|  4   | 
lvmdriver-1 |  false   |  |
| d576773f-6865-4959-ba26-13602ed32e89 | error_deleting | None|  4   | 
lvmdriver-1 |  false   |  |
+--++-+--+-+--+--+
[tagett@stack-01 devstack]$ cinder delete  7039c683-2341-4dd7-a947-e35941245ec4
Delete for volume 7039c683-2341-4dd7-a947-e35941245ec4 failed: Bad Request 
(HTTP 400) (Request-ID: req-e4d8cdd9-6ed5-4a7f-81de-7f38f2163d33)
ERROR: Unable to delete any of specified volumes.



--

Thanks,

Eli (Li Yong) Qiao

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



--
regards,

punith s
cloudbyte.comhttp://cloudbyte.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


  1   2   >