Re: [OpenStack-Infra] New Neutron Infra Liasons

2015-08-17 Thread Kyle Mestery
On Mon, Aug 17, 2015 at 5:19 PM, Clark Boylan cboy...@sapwetik.org wrote:

 Just letting everyone know that Neutron have asked that changes to their
 job configs (think project-config, devstack-gate, etc) be ACKed by one
 of their Infra liasons (mestery, dougwig, and armax) before we merge it.
 Basically look for a +1 from at least one of them before pushing Neutron
 related changes through Infra.

 Note that in the case of an emergency we can go ahead and push things
 without their input then beg for forgiveness later, but this should be
 an uncommon occurrence and provide much more stability to Neutron's CI
 in general.


Thanks for sending this out Clark, and thanks for dropping by our meeting
this week! With the onslaught of new repos and plethora of changes in
infra, we're hoping this will help provide some much needed sanity checking
and relieve a bit of the load we've put on infra.

Thanks for all the support that you and the rest of the infra team provide
us and everyone else in OpenStack!

Kyle


 Thank you,
 Clark

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

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


Re: [OpenStack-Infra] Gerrit under high load

2015-08-17 Thread Joshua Hesketh
Hi all,

Gerrit (review.openstack.org) has been restarted and the systems are back
up and functioning.

We have an idea of the cause of the problem and will investigate more
permanent fixes.

Cheers,
Josh

On Mon, Aug 17, 2015 at 5:06 PM, Joshua Hesketh joshua.hesk...@gmail.com
wrote:

 Hi all,

 Gerrit is currently under very high load and may be unresponsive. We are
 looking into the issue and will keep you updated here.

 Cheers,
 Josh

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


Re: [OpenStack-Infra] Migrating existing projects in the stackforge namespace

2015-08-17 Thread Thierry Carrez
James E. Blair wrote:
 As mentioned previously[1], we are retiring the stackforge/ namespace
 for git repositories and creating new projects in openstack/.  This is
 largely a cosmetic change and does not change the governance model for
 new projects.
 
 As part of this we want to move all of the projects that are currently
 in the stackforge/ namespace into openstack/ to make it easier for them
 to become official OpenStack projects in the future while reducing the
 impact to the community that the current practice of sporadic renaming
 causes.
 
 To that end, I propose the following process:
 
 1) We choose a date upon which to perform a mass migration of all
 stackforge/ projects into openstack/.
 
 I suggest either October 17 or November 7 (both Saturdays), as least
 likely to interfere with the release or summit.
 
 2) We create a wiki page for all such projects to either sign up for
 that migration or indicate that they are no longer maintained.
 
 3) Any stackforge projects that do not sign up for the migration within
 a certain time are placed on the list of projects that are no longer
 maintained.
 
 4) We attempt to contact, by way of posts to the openstack-dev mailing
 list, announcements at the cross project meeting, and direct emails to
 the individuals who initially requested repository creation, people who
 might be responsible for projects which have not responded and ensure
 that they have a chance to respond.  We will freeze the list of projects
 and portions of the project-config repository several days before the
 migration, to facilitate creating and reviewing the necessary change.
 
 5) On the migration date, the Infrastructure team will move all of the
 projects at once.  We will generate the changes needed to do so
 automatically, individual projects will not need to do anything except
 approve .gitreview changes and possibly help fix any CI jobs that break
 as a result of the moves.
 
 6) For the projects that are no longer maintained, we will merge changes
 to them that indicate that and make them read-only.
 
 We will schedule a move in early September for the projects that have
 already requested moves as part of becoming official OpenStack projects.
 Please don't propose any more changes to move projects before the mass
 migration.
 
 While most new projects are being created directly in the openstack/
 namespace, we will continue to create additional git repositories
 associated with existing projects in the stackforge/ namespace so that
 the constituent repositories associated with those projects are not
 split across namespaces.  We will happily move those projects along with
 the rest as part of the mass migration.
 
 Please reply with any feedback or suggested improvements to this plan.
 If we can achieve consensus on the approach, we will make further
 announcements as to specifics soon.

Sounds good. I like that we take the opportunity to clean up abandoned
projects: since there is no project team owner for those projects,
it's easy to create one and abandon it.

-- 
Thierry Carrez (ttx)

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


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

2015-08-17 Thread Abhishek Shrivastava
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.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?

 --


 *Thanks  Regards,*
 *Abhishek*
 *Cloudbyte Inc. http://www.cloudbyte.com*




-- 


*Thanks  Regards,*
*Abhishek*
*Cloudbyte Inc. http://www.cloudbyte.com*
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


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

2015-08-17 Thread Abhishek Shrivastava
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?

-- 


*Thanks  Regards,*
*Abhishek*
*Cloudbyte Inc. http://www.cloudbyte.com*
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


[OpenStack-Infra] Gerrit under high load

2015-08-17 Thread Joshua Hesketh
Hi all,

Gerrit is currently under very high load and may be unresponsive. We are
looking into the issue and will keep you updated here.

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


[OpenStack-Infra] [Infra] Meeting Tuesday August 18th at 19:00 UTC

2015-08-17 Thread Elizabeth K. Joseph
Hi everyone,

The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday August 18th, at 19:00 UTC in #openstack-meeting

Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)

Everyone interested in infrastructure and process surrounding
automated testing and deployment is encouraged to attend.

In case you missed them or would like a refresher, the meeting minutes
and full logs from our last two meetings are available.

August 4th:

Minutes: 
http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-04-19.03.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-04-19.03.txt
Log: 
http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-04-19.03.log.html

August 11th:

Minutes: 
http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-11-19.02.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-11-19.02.txt
Log: 
http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-11-19.02.log.html

-- 
Elizabeth Krumbach Joseph || Lyz || pleia2

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