Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

2016-08-23 Thread Znoinski, Waldemar
We’ll disable testing on nova stable/liberty till I have a moment to look into 
the problem(s) properly – should happen in next few days.
CI had some trouble on stable/mitaka for a moment couple of weeks back but it’s 
fixed since.

From: Znoinski, Waldemar
Sent: Monday, August 22, 2016 9:17 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: RE: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

I’ll have a look.

From: Timofei Durakov [mailto:tdura...@mirantis.com]
Sent: Monday, August 22, 2016 8:03 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] [nova] [infra] Intel NFV CI voting permission

Hi everyone,

got a question on that Intel NFV CI: has statistics for stable branches been 
checked either?
I have a patch to stable/liberty [1] that failed on all Intel NFV CI jobs 2 
times in a row. Who could help me to figure out the root cause for that?

Thanks in advance,
Timofey.

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

On Mon, Aug 8, 2016 at 6:27 PM, Ptacek, MichalX 
<michalx.pta...@intel.com<mailto:michalx.pta...@intel.com>> wrote:
Change deployed,
Thanks for your comments,

Michal

-Original Message-
From: Markus Zoeller 
[mailto:mzoel...@linux.vnet.ibm.com<mailto:mzoel...@linux.vnet.ibm.com>]
Sent: Monday, August 08, 2016 3:15 PM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

On 03.08.2016 22:02, Znoinski, Waldemar wrote:
> Thanks
> Much appreciated
>
> Making use of the opportunity here... what's the next big thing a CI
> (like one testing NFV) should be doing? (multinode or there's
> something else more important?)

Two tiny nits on the comment the CI is giving a change:

"Build failed (check pipeline). To recheck leave a comment with
intel-nfv-ci recheck. For more info go to
https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-NFV-CI.;

1) Could you put the recheck command in quotation? Like:
   To recheck leave a comment with 'intel-nfv-ci recheck'.
2) The link to the wiki seems to be wrong (hyphen vs. underscore):
   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI

--
Regards, Markus Zoeller (markus_z)

>  >-Original Message-
>  >From: Matt Riedemann 
> [mailto:mrie...@linux.vnet.ibm.com<mailto:mrie...@linux.vnet.ibm.com>]
>  >Sent: Wednesday, August 3, 2016 8:28 PM
>  >To: 
> openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
>  >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting
> permission  >  >On 8/3/2016 8:18 AM, Znoinski, Waldemar wrote:
>  >> [WZ] Hi Matt, do we need, a Gerrit-style, +2 on that from someone?
>  >> Infra Team doesn't keep these settings in their puppet/config
> files on git -  >all the Gerrit changes are done via Gerrit GUI so
> they rely on Cores to add CIs  >to the appropriate ci group, nova-ci in this 
> case.
>  >>
>  >>
>  >
>  >Sorry, I wasn't sure what the next step here was, I guess it was the
> nova-ci  >membership change, which is done now:
>  >
>  >https://review.openstack.org/#/admin/groups/511,members
>  >
>  >--
>  >
>  >Thanks,
>  >
>  >Matt Riedemann
>  >
>  >
>  >__
>  >
>  >OpenStack Development Mailing List (not for usage questions)
>  >Unsubscribe: OpenStack-dev-
>  
> >requ...@lists.openstack.org?subject:unsubscribe<http://requ...@lists.openstack.org?subject:unsubscribe>
>  >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> --
> Intel Research and Development Ireland Limited Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County
> Kildare Registered Number: 308263
>
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

2016-08-22 Thread Znoinski, Waldemar
I’ll have a look.

From: Timofei Durakov [mailto:tdura...@mirantis.com]
Sent: Monday, August 22, 2016 8:03 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

Hi everyone,

got a question on that Intel NFV CI: has statistics for stable branches been 
checked either?
I have a patch to stable/liberty [1] that failed on all Intel NFV CI jobs 2 
times in a row. Who could help me to figure out the root cause for that?

Thanks in advance,
Timofey.

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

On Mon, Aug 8, 2016 at 6:27 PM, Ptacek, MichalX 
<michalx.pta...@intel.com<mailto:michalx.pta...@intel.com>> wrote:
Change deployed,
Thanks for your comments,

Michal

-Original Message-
From: Markus Zoeller 
[mailto:mzoel...@linux.vnet.ibm.com<mailto:mzoel...@linux.vnet.ibm.com>]
Sent: Monday, August 08, 2016 3:15 PM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

On 03.08.2016 22:02, Znoinski, Waldemar wrote:
> Thanks
> Much appreciated
>
> Making use of the opportunity here... what's the next big thing a CI
> (like one testing NFV) should be doing? (multinode or there's
> something else more important?)

Two tiny nits on the comment the CI is giving a change:

"Build failed (check pipeline). To recheck leave a comment with
intel-nfv-ci recheck. For more info go to
https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-NFV-CI.;

1) Could you put the recheck command in quotation? Like:
   To recheck leave a comment with 'intel-nfv-ci recheck'.
2) The link to the wiki seems to be wrong (hyphen vs. underscore):
   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI

--
Regards, Markus Zoeller (markus_z)

>  >-Original Message-
>  >From: Matt Riedemann 
> [mailto:mrie...@linux.vnet.ibm.com<mailto:mrie...@linux.vnet.ibm.com>]
>  >Sent: Wednesday, August 3, 2016 8:28 PM
>  >To: 
> openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
>  >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting
> permission  >  >On 8/3/2016 8:18 AM, Znoinski, Waldemar wrote:
>  >> [WZ] Hi Matt, do we need, a Gerrit-style, +2 on that from someone?
>  >> Infra Team doesn't keep these settings in their puppet/config
> files on git -  >all the Gerrit changes are done via Gerrit GUI so
> they rely on Cores to add CIs  >to the appropriate ci group, nova-ci in this 
> case.
>  >>
>  >>
>  >
>  >Sorry, I wasn't sure what the next step here was, I guess it was the
> nova-ci  >membership change, which is done now:
>  >
>  >https://review.openstack.org/#/admin/groups/511,members
>  >
>  >--
>  >
>  >Thanks,
>  >
>  >Matt Riedemann
>  >
>  >
>  >__
>  >
>  >OpenStack Development Mailing List (not for usage questions)
>  >Unsubscribe: OpenStack-dev-
>  
> >requ...@lists.openstack.org?subject:unsubscribe<http://requ...@lists.openstack.org?subject:unsubscribe>
>  >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> --
> Intel Research and Development Ireland Limited Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County
> Kildare Registered Number: 308263
>
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://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://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

2016-08-22 Thread Timofei Durakov
Hi everyone,

got a question on that Intel NFV CI: has statistics for stable branches
been checked either?
I have a patch to stable/liberty [1] that failed on all Intel NFV CI jobs 2
times in a row. Who could help me to figure out the root cause for that?

Thanks in advance,
Timofey.

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

On Mon, Aug 8, 2016 at 6:27 PM, Ptacek, MichalX <michalx.pta...@intel.com>
wrote:

> Change deployed,
> Thanks for your comments,
>
> Michal
>
> -Original Message-
> From: Markus Zoeller [mailto:mzoel...@linux.vnet.ibm.com]
> Sent: Monday, August 08, 2016 3:15 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
>
> On 03.08.2016 22:02, Znoinski, Waldemar wrote:
> > Thanks
> > Much appreciated
> >
> > Making use of the opportunity here... what's the next big thing a CI
> > (like one testing NFV) should be doing? (multinode or there's
> > something else more important?)
>
> Two tiny nits on the comment the CI is giving a change:
>
> "Build failed (check pipeline). To recheck leave a comment with
> intel-nfv-ci recheck. For more info go to
> https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-NFV-CI.;
>
> 1) Could you put the recheck command in quotation? Like:
>To recheck leave a comment with 'intel-nfv-ci recheck'.
> 2) The link to the wiki seems to be wrong (hyphen vs. underscore):
>https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
>
> --
> Regards, Markus Zoeller (markus_z)
>
> >  >-Original Message-
> >  >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
> >  >Sent: Wednesday, August 3, 2016 8:28 PM
> >  >To: openstack-dev@lists.openstack.org
> >  >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting
> > permission  >  >On 8/3/2016 8:18 AM, Znoinski, Waldemar wrote:
> >  >> [WZ] Hi Matt, do we need, a Gerrit-style, +2 on that from someone?
> >  >> Infra Team doesn't keep these settings in their puppet/config
> > files on git -  >all the Gerrit changes are done via Gerrit GUI so
> > they rely on Cores to add CIs  >to the appropriate ci group, nova-ci in
> this case.
> >  >>
> >  >>
> >  >
> >  >Sorry, I wasn't sure what the next step here was, I guess it was the
> > nova-ci  >membership change, which is done now:
> >  >
> >  >https://review.openstack.org/#/admin/groups/511,members
> >  >
> >  >--
> >  >
> >  >Thanks,
> >  >
> >  >Matt Riedemann
> >  >
> >  >
> >  >__
> >  >
> >  >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
> > --
> > Intel Research and Development Ireland Limited Registered in Ireland
> > Registered Office: Collinstown Industrial Park, Leixlip, County
> > Kildare Registered Number: 308263
> >
> >
> > This e-mail and any attachments may contain confidential material for
> > the sole use of the intended recipient(s). Any review or distribution
> > by others is strictly prohibited. If you are not the intended
> > recipient, please contact the sender and delete all copies.
> >
> >
> > __
> >  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
> --
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
>
>
> This e-mail and any attachments may contain confidential material for the
> sole
> use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact
&

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

2016-08-08 Thread Ptacek, MichalX
Change deployed,
Thanks for your comments,

Michal

-Original Message-
From: Markus Zoeller [mailto:mzoel...@linux.vnet.ibm.com] 
Sent: Monday, August 08, 2016 3:15 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

On 03.08.2016 22:02, Znoinski, Waldemar wrote:
> Thanks
> Much appreciated
> 
> Making use of the opportunity here... what's the next big thing a CI 
> (like one testing NFV) should be doing? (multinode or there's 
> something else more important?)

Two tiny nits on the comment the CI is giving a change:

"Build failed (check pipeline). To recheck leave a comment with
intel-nfv-ci recheck. For more info go to
https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-NFV-CI.;

1) Could you put the recheck command in quotation? Like:
   To recheck leave a comment with 'intel-nfv-ci recheck'.
2) The link to the wiki seems to be wrong (hyphen vs. underscore):
   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI

--
Regards, Markus Zoeller (markus_z)

>  >-Original Message-
>  >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
>  >Sent: Wednesday, August 3, 2016 8:28 PM
>  >To: openstack-dev@lists.openstack.org
>  >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting 
> permission  >  >On 8/3/2016 8:18 AM, Znoinski, Waldemar wrote:
>  >> [WZ] Hi Matt, do we need, a Gerrit-style, +2 on that from someone?
>  >> Infra Team doesn't keep these settings in their puppet/config 
> files on git -  >all the Gerrit changes are done via Gerrit GUI so 
> they rely on Cores to add CIs  >to the appropriate ci group, nova-ci in this 
> case.
>  >>
>  >>
>  >
>  >Sorry, I wasn't sure what the next step here was, I guess it was the 
> nova-ci  >membership change, which is done now:
>  >
>  >https://review.openstack.org/#/admin/groups/511,members
>  >
>  >--
>  >
>  >Thanks,
>  >
>  >Matt Riedemann
>  >
>  >
>  >__
>  >
>  >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
> --
> Intel Research and Development Ireland Limited Registered in Ireland 
> Registered Office: Collinstown Industrial Park, Leixlip, County 
> Kildare Registered Number: 308263
> 
> 
> This e-mail and any attachments may contain confidential material for 
> the sole use of the intended recipient(s). Any review or distribution 
> by others is strictly prohibited. If you are not the intended 
> recipient, please contact the sender and delete all copies.
> 
> 
> __
>  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
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.


__
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] [nova] [infra] Intel NFV CI voting permission

2016-08-08 Thread Markus Zoeller
On 03.08.2016 22:02, Znoinski, Waldemar wrote:
> Thanks
> Much appreciated
> 
> Making use of the opportunity here... what's the next big thing a CI (like 
> one testing NFV) should be doing? (multinode or there's something else more 
> important?)

Two tiny nits on the comment the CI is giving a change:

"Build failed (check pipeline). To recheck leave a comment with
intel-nfv-ci recheck. For more info go to
https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-NFV-CI.;

1) Could you put the recheck command in quotation? Like:
   To recheck leave a comment with 'intel-nfv-ci recheck'.
2) The link to the wiki seems to be wrong (hyphen vs. underscore):
   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI

-- 
Regards, Markus Zoeller (markus_z)

>  >-Original Message-
>  >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
>  >Sent: Wednesday, August 3, 2016 8:28 PM
>  >To: openstack-dev@lists.openstack.org
>  >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
>  >
>  >On 8/3/2016 8:18 AM, Znoinski, Waldemar wrote:
>  >> [WZ] Hi Matt, do we need, a Gerrit-style, +2 on that from someone?
>  >> Infra Team doesn't keep these settings in their puppet/config files on 
> git -
>  >all the Gerrit changes are done via Gerrit GUI so they rely on Cores to add 
> CIs
>  >to the appropriate ci group, nova-ci in this case.
>  >>
>  >>
>  >
>  >Sorry, I wasn't sure what the next step here was, I guess it was the nova-ci
>  >membership change, which is done now:
>  >
>  >https://review.openstack.org/#/admin/groups/511,members
>  >
>  >--
>  >
>  >Thanks,
>  >
>  >Matt Riedemann
>  >
>  >
>  >__
>  >
>  >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
> --
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
> 
> 
> This e-mail and any attachments may contain confidential material for the sole
> use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact the
> sender and delete all copies.
> 
> 
> __
> 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] [nova] [infra] Intel NFV CI voting permission

2016-08-03 Thread Matt Riedemann

On 8/3/2016 3:02 PM, Znoinski, Waldemar wrote:

Thanks
Much appreciated

Making use of the opportunity here... what's the next big thing a CI (like one 
testing NFV) should be doing? (multinode or there's something else more 
important?)



Moshe Levi might have more input here, but I think multinode is the 
biggest one so that we can test resize/migrate of servers with NFV features.


--

Thanks,

Matt Riedemann


__
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] [nova] [infra] Intel NFV CI voting permission

2016-08-03 Thread Znoinski, Waldemar
Thanks
Much appreciated

Making use of the opportunity here... what's the next big thing a CI (like one 
testing NFV) should be doing? (multinode or there's something else more 
important?)

 >-Original Message-
 >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 >Sent: Wednesday, August 3, 2016 8:28 PM
 >To: openstack-dev@lists.openstack.org
 >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
 >
 >On 8/3/2016 8:18 AM, Znoinski, Waldemar wrote:
 >> [WZ] Hi Matt, do we need, a Gerrit-style, +2 on that from someone?
 >> Infra Team doesn't keep these settings in their puppet/config files on git -
 >all the Gerrit changes are done via Gerrit GUI so they rely on Cores to add 
 >CIs
 >to the appropriate ci group, nova-ci in this case.
 >>
 >>
 >
 >Sorry, I wasn't sure what the next step here was, I guess it was the nova-ci
 >membership change, which is done now:
 >
 >https://review.openstack.org/#/admin/groups/511,members
 >
 >--
 >
 >Thanks,
 >
 >Matt Riedemann
 >
 >
 >__
 >
 >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
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.


__
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] [nova] [infra] Intel NFV CI voting permission

2016-08-03 Thread Matt Riedemann

On 8/3/2016 8:18 AM, Znoinski, Waldemar wrote:

[WZ] Hi Matt, do we need, a Gerrit-style, +2 on that from someone?
Infra Team doesn't keep these settings in their puppet/config files on git - 
all the Gerrit changes are done via Gerrit GUI so they rely on Cores to add CIs 
to the appropriate ci group, nova-ci in this case.




Sorry, I wasn't sure what the next step here was, I guess it was the 
nova-ci membership change, which is done now:


https://review.openstack.org/#/admin/groups/511,members

--

Thanks,

Matt Riedemann


__
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] [nova] [infra] Intel NFV CI voting permission

2016-08-03 Thread Znoinski, Waldemar


 >-Original Message-
 >From: Znoinski, Waldemar [mailto:waldemar.znoin...@intel.com]
 >Sent: Monday, August 1, 2016 6:52 PM
 >To: OpenStack Development Mailing List (not for usage questions)
 ><openstack-dev@lists.openstack.org>
 >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
 >
 >
 > >-Original Message-
 > >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 > >Sent: Friday, July 29, 2016 6:37 PM
 > >To: openstack-dev@lists.openstack.org
 > >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
 >>  >On 7/29/2016 10:47 AM, Znoinski, Waldemar wrote:
 > >> Hi Matt et al,
 > >> Thanks for taking the time to have a chat about it in Nova meeting
 >>yesterday.
 > >> In relation to your two points below...
 > >>
 > >> 1. tempest-dsvm-ovsdpdk-nfv-networking job in our Intel NFV CI was
 >>broken for about a day till we troubleshooted the issue, to find out merge
 >of  >this [1] change started to cause our troubles.
 > >> We set Q_USE_PROVIDERNET_FOR_PUBLIC back to False to let the job
 >get  >green again and test what it should be testing - nova/neutron changes
 >and  >not giving false negatives because of that devstack change.
 > >> We saw a REVERT [2] of the above change shortly after as it was breaking
 >>Jenkins neutron's linuxbridge tempest too [3].
 > >>
 > >> 2. Our aim is to have two things tested when new change is proposed to
 > >devstack: NFV and OVS+DPDK. For better clarity we'll run two separate
 >jobs  >instead of having NFV+OVSDPDK together.
 > >> Currently we run OVSDPDK+ODL on devstack changes to discover
 >potential  >issues with configuring these two together with each devstack
 >change  >proposed. We've discussed this internally and we can add/(replace
 >>OVSDPDK+ODL job) with a 'tempest-dsvm-full-nfv' one (currently running
 >on  >Nova changes) that does devstack + runs full tempest test suite (1100+
 >tests)  >on NFV enabled flavors. It should test properly proposed devstack
 >changes  >with NFV features (as per wiki [4]) we have enabled in Openstack.
 > >>
 > >> Let me know if there are other questions, concerns, asks or suggestions.
 > >>
 > >> Thanks
 > >> Waldek
 > >>
 > >>
 > >> [1] https://review.openstack.org/#/c/343072/
 > >> [2] https://review.openstack.org/#/c/345820/
 > >> [3] https://bugs.launchpad.net/devstack/+bug/1605423
 > >> [4] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
 > >>
 > >>
 > >>  >-Original Message-
 > >>  >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 > >>  >Sent: Thursday, July 28, 2016 4:14 PM  >>  >To: openstack-
 >d...@lists.openstack.org  >>  >Subject: Re: [openstack-dev] [nova] [infra]
 >Intel NFV CI voting  >> permission  >  >On 7/21/2016 5:38 AM, Znoinski,
 >Waldemar wrote:
 > >>  >> Hi Nova cores et al,
 > >>  >>
 > >>  >>
 > >>  >>
 > >>  >> I would like to acquire voting (+/-1 Verified) permission for our  >> 
 > >> >>
 >Intel NFV CI.
 > >>  >>
 > >>  >>
 > >>  >>
 > >>  >> 1.   It's running since Q1'2015.
 > >>  >>
 > >>  >> 2.   Wiki [1].
 > >>  >>
 > >>  >> 3.   It's using openstack-infra/puppet-openstackci
 > >>  >> <https://github.com/openstack-infra/puppet-openstackci> with Zuul
 >>> >> 2.1.1 for last 4 months: zuul, gearman, Jenkins, nodepool, local  >>
 >Openstack  >cloud.
 > >>  >>
 > >>  >> 4.   We have a team of 2 people + me + Nagios looking after it. 
 > >> Its
 > >>  >> problems are fixed promptly and rechecks triggered after non-code
 >>> >> related issues. It's being reconciled against ci-watch [2].
 > >>  >>
 > >>  >> 5.   Reviews [3].
 > >>  >>
 > >>  >>
 > >>  >>
 > >>  >> Let me know if further questions.
 > >>  >>
 > >>  >>
 > >>  >>
 > >>  >> 1.
 >https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
 > >>  >>
 > >>  >> 2.   http://ci-watch.tintri.com/project?project=nova
 > >>  >>
 > >>  >> 3.
 > >>  >> https://review.openstack.org/#/q/reviewer:%22Intel+NFV-
 > >>  >CI+%253Copensta
 > >

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

2016-08-01 Thread Znoinski, Waldemar

 >-Original Message-
 >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 >Sent: Friday, July 29, 2016 6:37 PM
 >To: openstack-dev@lists.openstack.org
 >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
 >
 >On 7/29/2016 10:47 AM, Znoinski, Waldemar wrote:
 >> Hi Matt et al,
 >> Thanks for taking the time to have a chat about it in Nova meeting
 >yesterday.
 >> In relation to your two points below...
 >>
 >> 1. tempest-dsvm-ovsdpdk-nfv-networking job in our Intel NFV CI was
 >broken for about a day till we troubleshooted the issue, to find out merge of
 >this [1] change started to cause our troubles.
 >> We set Q_USE_PROVIDERNET_FOR_PUBLIC back to False to let the job get
 >green again and test what it should be testing - nova/neutron changes and
 >not giving false negatives because of that devstack change.
 >> We saw a REVERT [2] of the above change shortly after as it was breaking
 >Jenkins neutron's linuxbridge tempest too [3].
 >>
 >> 2. Our aim is to have two things tested when new change is proposed to
 >devstack: NFV and OVS+DPDK. For better clarity we'll run two separate jobs
 >instead of having NFV+OVSDPDK together.
 >> Currently we run OVSDPDK+ODL on devstack changes to discover potential
 >issues with configuring these two together with each devstack change
 >proposed. We've discussed this internally and we can add/(replace
 >OVSDPDK+ODL job) with a 'tempest-dsvm-full-nfv' one (currently running on
 >Nova changes) that does devstack + runs full tempest test suite (1100+ tests)
 >on NFV enabled flavors. It should test properly proposed devstack changes
 >with NFV features (as per wiki [4]) we have enabled in Openstack.
 >>
 >> Let me know if there are other questions, concerns, asks or suggestions.
 >>
 >> Thanks
 >> Waldek
 >>
 >>
 >> [1] https://review.openstack.org/#/c/343072/
 >> [2] https://review.openstack.org/#/c/345820/
 >> [3] https://bugs.launchpad.net/devstack/+bug/1605423
 >> [4] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
 >>
 >>
 >>  >-----Original Message-----
 >>  >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 >>  >Sent: Thursday, July 28, 2016 4:14 PM
 >>  >To: openstack-dev@lists.openstack.org
 >>  >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting
 >> permission  >  >On 7/21/2016 5:38 AM, Znoinski, Waldemar wrote:
 >>  >> Hi Nova cores et al,
 >>  >>
 >>  >>
 >>  >>
 >>  >> I would like to acquire voting (+/-1 Verified) permission for our
 >> >> Intel NFV CI.
 >>  >>
 >>  >>
 >>  >>
 >>  >> 1.   It's running since Q1'2015.
 >>  >>
 >>  >> 2.   Wiki [1].
 >>  >>
 >>  >> 3.   It's using openstack-infra/puppet-openstackci
 >>  >> <https://github.com/openstack-infra/puppet-openstackci> with Zuul
 >> >> 2.1.1 for last 4 months: zuul, gearman, Jenkins, nodepool, local
 >> Openstack  >cloud.
 >>  >>
 >>  >> 4.   We have a team of 2 people + me + Nagios looking after it. Its
 >>  >> problems are fixed promptly and rechecks triggered after non-code
 >> >> related issues. It's being reconciled against ci-watch [2].
 >>  >>
 >>  >> 5.   Reviews [3].
 >>  >>
 >>  >>
 >>  >>
 >>  >> Let me know if further questions.
 >>  >>
 >>  >>
 >>  >>
 >>  >> 1.   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
 >>  >>
 >>  >> 2.   http://ci-watch.tintri.com/project?project=nova
 >>  >>
 >>  >> 3.
 >>  >> https://review.openstack.org/#/q/reviewer:%22Intel+NFV-
 >>  >CI+%253Copensta
 >>  >> ck-nfv-ci%2540intel.com%253E%22
 >>  >>
 >>  >>
 >>  >>
 >>  >>
 >>  >>
 >>  >>
 >>  >> *Waldek*
 >>  >>
 >>  >>
 >>  >>
 >>  >> --
 >>  >> Intel Research and Development Ireland Limited Registered in
 >> Ireland  >> Registered Office: Collinstown Industrial Park, Leixlip,
 >> County  >> Kildare Registered Number: 308263  >>  >> This e-mail and
 >> any attachments may contain confidential material for  >> the sole use
 >> of the intended recipient(s). Any review or distribution  >> by others
 >> is strictly prohibite

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

2016-07-29 Thread Matt Riedemann

On 7/29/2016 10:47 AM, Znoinski, Waldemar wrote:

Hi Matt et al,
Thanks for taking the time to have a chat about it in Nova meeting yesterday.
In relation to your two points below...

1. tempest-dsvm-ovsdpdk-nfv-networking job in our Intel NFV CI was broken for 
about a day till we troubleshooted the issue, to find out merge of this [1] 
change started to cause our troubles.
We set Q_USE_PROVIDERNET_FOR_PUBLIC back to False to let the job get green 
again and test what it should be testing - nova/neutron changes and not giving 
false negatives because of that devstack change.
We saw a REVERT [2] of the above change shortly after as it was breaking 
Jenkins neutron's linuxbridge tempest too [3].

2. Our aim is to have two things tested when new change is proposed to 
devstack: NFV and OVS+DPDK. For better clarity we'll run two separate jobs 
instead of having NFV+OVSDPDK together.
Currently we run OVSDPDK+ODL on devstack changes to discover potential issues 
with configuring these two together with each devstack change proposed. We've 
discussed this internally and we can add/(replace OVSDPDK+ODL job) with a 
'tempest-dsvm-full-nfv' one (currently running on Nova changes) that does 
devstack + runs full tempest test suite (1100+ tests) on NFV enabled flavors. 
It should test properly proposed devstack changes with NFV features (as per 
wiki [4]) we have enabled in Openstack.

Let me know if there are other questions, concerns, asks or suggestions.

Thanks
Waldek


[1] https://review.openstack.org/#/c/343072/
[2] https://review.openstack.org/#/c/345820/
[3] https://bugs.launchpad.net/devstack/+bug/1605423
[4] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI


 >-Original Message-
 >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 >Sent: Thursday, July 28, 2016 4:14 PM
 >To: openstack-dev@lists.openstack.org
 >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
 >
 >On 7/21/2016 5:38 AM, Znoinski, Waldemar wrote:
 >> Hi Nova cores et al,
 >>
 >>
 >>
 >> I would like to acquire voting (+/-1 Verified) permission for our
 >> Intel NFV CI.
 >>
 >>
 >>
 >> 1.   It's running since Q1'2015.
 >>
 >> 2.   Wiki [1].
 >>
 >> 3.   It's using openstack-infra/puppet-openstackci
 >> <https://github.com/openstack-infra/puppet-openstackci> with Zuul
 >> 2.1.1 for last 4 months: zuul, gearman, Jenkins, nodepool, local Openstack
 >cloud.
 >>
 >> 4.   We have a team of 2 people + me + Nagios looking after it. Its
 >> problems are fixed promptly and rechecks triggered after non-code
 >> related issues. It's being reconciled against ci-watch [2].
 >>
 >> 5.   Reviews [3].
 >>
 >>
 >>
 >> Let me know if further questions.
 >>
 >>
 >>
 >> 1.   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
 >>
 >> 2.   http://ci-watch.tintri.com/project?project=nova
 >>
 >> 3.
 >> https://review.openstack.org/#/q/reviewer:%22Intel+NFV-
 >CI+%253Copensta
 >> ck-nfv-ci%2540intel.com%253E%22
 >>
 >>
 >>
 >>
 >>
 >>
 >> *Waldek*
 >>
 >>
 >>
 >> --
 >> Intel Research and Development Ireland Limited Registered in Ireland
 >> Registered Office: Collinstown Industrial Park, Leixlip, County
 >> Kildare Registered Number: 308263
 >>
 >> This e-mail and any attachments may contain confidential material for
 >> the sole use of the intended recipient(s). Any review or distribution
 >> by others is strictly prohibited. If you are not the intended
 >> recipient, please contact the sender and delete all copies.
 >>
 >>
 >>
 >>
 >__
 >
 >>  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
 >>
 >
 >We talked about this in the nova meeting today. I don't have a great grasp on
 >how the Intel NFV CI has been performing, but making it voting will help with
 >that. Looking at the 7 day results:
 >
 >http://ci-watch.tintri.com/project?project=nova=7+days
 >
 >Everything looks pretty good except for tempest-dsvm-ovsdpdk-nfv-
 >networking but Waldemar pointed out there was a change in devstack that
 >broke the CI for a day or so:
 >
 >https://github.com/openstack-
 >dev/devstack/commit/130a11f8aaf08ea529b6ce60dd9052451cb7bb5c
 >
 >I would like to

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

2016-07-29 Thread Znoinski, Waldemar
Hi Matt et al, 
Thanks for taking the time to have a chat about it in Nova meeting yesterday.
In relation to your two points below...

1. tempest-dsvm-ovsdpdk-nfv-networking job in our Intel NFV CI was broken for 
about a day till we troubleshooted the issue, to find out merge of this [1] 
change started to cause our troubles.
We set Q_USE_PROVIDERNET_FOR_PUBLIC back to False to let the job get green 
again and test what it should be testing - nova/neutron changes and not giving 
false negatives because of that devstack change.
We saw a REVERT [2] of the above change shortly after as it was breaking 
Jenkins neutron's linuxbridge tempest too [3].

2. Our aim is to have two things tested when new change is proposed to 
devstack: NFV and OVS+DPDK. For better clarity we'll run two separate jobs 
instead of having NFV+OVSDPDK together.
Currently we run OVSDPDK+ODL on devstack changes to discover potential issues 
with configuring these two together with each devstack change proposed. We've 
discussed this internally and we can add/(replace OVSDPDK+ODL job) with a 
'tempest-dsvm-full-nfv' one (currently running on Nova changes) that does 
devstack + runs full tempest test suite (1100+ tests) on NFV enabled flavors. 
It should test properly proposed devstack changes with NFV features (as per 
wiki [4]) we have enabled in Openstack.

Let me know if there are other questions, concerns, asks or suggestions.

Thanks
Waldek


[1] https://review.openstack.org/#/c/343072/
[2] https://review.openstack.org/#/c/345820/ 
[3] https://bugs.launchpad.net/devstack/+bug/1605423 
[4] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI 


 >-Original Message-
 >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 >Sent: Thursday, July 28, 2016 4:14 PM
 >To: openstack-dev@lists.openstack.org
 >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
 >
 >On 7/21/2016 5:38 AM, Znoinski, Waldemar wrote:
 >> Hi Nova cores et al,
 >>
 >>
 >>
 >> I would like to acquire voting (+/-1 Verified) permission for our
 >> Intel NFV CI.
 >>
 >>
 >>
 >> 1.   It's running since Q1'2015.
 >>
 >> 2.   Wiki [1].
 >>
 >> 3.   It's using openstack-infra/puppet-openstackci
 >> <https://github.com/openstack-infra/puppet-openstackci> with Zuul
 >> 2.1.1 for last 4 months: zuul, gearman, Jenkins, nodepool, local Openstack
 >cloud.
 >>
 >> 4.   We have a team of 2 people + me + Nagios looking after it. Its
 >> problems are fixed promptly and rechecks triggered after non-code
 >> related issues. It's being reconciled against ci-watch [2].
 >>
 >> 5.   Reviews [3].
 >>
 >>
 >>
 >> Let me know if further questions.
 >>
 >>
 >>
 >> 1.   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
 >>
 >> 2.   http://ci-watch.tintri.com/project?project=nova
 >>
 >> 3.
 >> https://review.openstack.org/#/q/reviewer:%22Intel+NFV-
 >CI+%253Copensta
 >> ck-nfv-ci%2540intel.com%253E%22
 >>
 >>
 >>
 >>
 >>
 >>
 >> *Waldek*
 >>
 >>
 >>
 >> --
 >> Intel Research and Development Ireland Limited Registered in Ireland
 >> Registered Office: Collinstown Industrial Park, Leixlip, County
 >> Kildare Registered Number: 308263
 >>
 >> This e-mail and any attachments may contain confidential material for
 >> the sole use of the intended recipient(s). Any review or distribution
 >> by others is strictly prohibited. If you are not the intended
 >> recipient, please contact the sender and delete all copies.
 >>
 >>
 >>
 >>
 >__
 >
 >>  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
 >>
 >
 >We talked about this in the nova meeting today. I don't have a great grasp on
 >how the Intel NFV CI has been performing, but making it voting will help with
 >that. Looking at the 7 day results:
 >
 >http://ci-watch.tintri.com/project?project=nova=7+days
 >
 >Everything looks pretty good except for tempest-dsvm-ovsdpdk-nfv-
 >networking but Waldemar pointed out there was a change in devstack that
 >broke the CI for a day or so:
 >
 >https://github.com/openstack-
 >dev/devstack/commit/130a11f8aaf08ea529b6ce60dd9052451cb7bb5c
 >
 >I would like to know a little more about why we don't run the Intel NFV CI on
 >devstack changes to catch stuff like this before it bec

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

2016-07-28 Thread Matt Riedemann

On 7/21/2016 5:38 AM, Znoinski, Waldemar wrote:

Hi Nova cores et al,



I would like to acquire voting (+/-1 Verified) permission for our Intel
NFV CI.



1.   It’s running since Q1’2015.

2.   Wiki [1].

3.   It’s using openstack-infra/puppet-openstackci
 with Zuul 2.1.1
for last 4 months: zuul, gearman, Jenkins, nodepool, local Openstack cloud.

4.   We have a team of 2 people + me + Nagios looking after it. Its
problems are fixed promptly and rechecks triggered after non-code
related issues. It’s being reconciled against ci-watch [2].

5.   Reviews [3].



Let me know if further questions.



1.   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI

2.   http://ci-watch.tintri.com/project?project=nova

3.
https://review.openstack.org/#/q/reviewer:%22Intel+NFV-CI+%253Copenstack-nfv-ci%2540intel.com%253E%22






*Waldek*



--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution by
others is strictly prohibited. If you are not the intended recipient,
please contact the sender and delete all copies.



__
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



We talked about this in the nova meeting today. I don't have a great 
grasp on how the Intel NFV CI has been performing, but making it voting 
will help with that. Looking at the 7 day results:


http://ci-watch.tintri.com/project?project=nova=7+days

Everything looks pretty good except for 
tempest-dsvm-ovsdpdk-nfv-networking but Waldemar pointed out there was a 
change in devstack that broke the CI for a day or so:


https://github.com/openstack-dev/devstack/commit/130a11f8aaf08ea529b6ce60dd9052451cb7bb5c

I would like to know a little more about why we don't run the Intel NFV 
CI on devstack changes to catch stuff like this before it becomes a 
breaking problem? The team worked around it for now, but it is a concern 
of mine. I think at least the Xen and PowerKVM CIs also run on devstack 
changes to avoid problems like this.


So please give me some details on running against devstack changes and 
then I'll ack or nack the request.


--

Thanks,

Matt Riedemann


__
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] [infra] Intel NFV CI voting permission

2016-07-21 Thread Znoinski, Waldemar
Hi Nova cores et al,

I would like to acquire voting (+/-1 Verified) permission for our Intel NFV CI.


1.   It's running since Q1'2015.

2.   Wiki [1].

3.   It's using 
openstack-infra/puppet-openstackci
 with Zuul 2.1.1 for last 4 months: zuul, gearman, Jenkins, nodepool, local 
Openstack cloud.

4.   We have a team of 2 people + me + Nagios looking after it. Its 
problems are fixed promptly and rechecks triggered after non-code related 
issues. It's being reconciled against ci-watch [2].

5.   Reviews [3].


Let me know if further questions.


1.   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI

2.   http://ci-watch.tintri.com/project?project=nova

3.   
https://review.openstack.org/#/q/reviewer:%22Intel+NFV-CI+%253Copenstack-nfv-ci%2540intel.com%253E%22


Waldek

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
__
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