[OpenStack-Infra] devstack failed './stack.sh:1224:start_nova_api'

[Wan, Sam]

Dear all,

Our CI failed at devstack setup.
The error messages in devstacklog is as below:
2014-12-07 22:33:47.959 | ./stack.sh:1224:start_nova_api
2014-12-07 22:33:47.959 | /opt/stack/new/devstack/lib/nova:701:die
2014-12-07 22:33:47.965 | [ERROR] /opt/stack/new/devstack/lib/nova:701 nova-api 
did not start
2014-12-07 22:33:48.970 | exit_trap: cleaning up child processes
2014-12-07 22:33:48.970 | ./stack.sh: line 441: kill: (5161) - No such process
2014-12-07 22:33:48.971 | Error on exit
2014-12-07 22:33:49.019 | World dumping... see 
/opt/stack/new/worlddump-2014-12-07-223349.txt for details
2014-12-07 22:33:49.086 | ./stack.sh: line 434:   428 Terminated  
_old_run_process "$service" "$command"


Seems there's something wrong with nova-api.
Has someone met this too?
Any suggestion or clue will be appreciated.

Thanks and regards
~
| Wan Shan  (Sam)
| Openstack Certification | EMC E-Lab
| Tel: +86-28-82966713
| Addr: 7F, C12, Tianfu Software Park, Chengdu, Sichuan, P. R. of China
~

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

Re: [OpenStack-Infra] devstack failed './stack.sh:1224:start_nova_api'

[Wan, Sam]

Hi there,

The problem turns out to be that we have a lower version of 'retrying' package.
After upgrading  'retrying' to latest 1.3.2 by 'pip install -U retrying' ,  
devstack can run.


Thanks and regards
~
| Wan Shan  (Sam)
| Openstack Certification | EMC E-Lab
| Tel: +86-28-82966713
| Addr: 7F, C12, Tianfu Software Park, Chengdu, Sichuan, P. R. of China
~

From: Wan, Sam [mailto:sam@emc.com]
Sent: Monday, December 08, 2014 4:14 PM
To: openstack-infra@lists.openstack.org
Subject: [OpenStack-Infra] devstack failed './stack.sh:1224:start_nova_api'

Dear all,

Our CI failed at devstack setup.
The error messages in devstacklog is as below:
2014-12-07 22:33:47.959 | ./stack.sh:1224:start_nova_api
2014-12-07 22:33:47.959 | /opt/stack/new/devstack/lib/nova:701:die
2014-12-07 22:33:47.965 | [ERROR] /opt/stack/new/devstack/lib/nova:701 nova-api 
did not start
2014-12-07 22:33:48.970 | exit_trap: cleaning up child processes
2014-12-07 22:33:48.970 | ./stack.sh: line 441: kill: (5161) - No such process
2014-12-07 22:33:48.971 | Error on exit
2014-12-07 22:33:49.019 | World dumping... see 
/opt/stack/new/worlddump-2014-12-07-223349.txt for details
2014-12-07 22:33:49.086 | ./stack.sh: line 434:   428 Terminated  
_old_run_process "$service" "$command"


Seems there's something wrong with nova-api.
Has someone met this too?
Any suggestion or clue will be appreciated.

Thanks and regards
~
| Wan Shan  (Sam)
| Openstack Certification | EMC E-Lab
| Tel: +86-28-82966713
| Addr: 7F, C12, Tianfu Software Park, Chengdu, Sichuan, P. R. of China
~

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

Re: [OpenStack-Infra] devstack failed './stack.sh:1224:start_nova_api'

[Rick Chen]

HI Sam:

I happed same issue. In the some log has trace-back in the oslo
package, but I forgot which one.

I try to update all oslo.XXX that can solve this problem.

Ex:

pip install oslo.concurrency --upgrade

 

From: Wan, Sam [mailto:sam@emc.com] 
Sent: Monday, December 08, 2014 4:14 PM
To: openstack-infra@lists.openstack.org
Subject: [OpenStack-Infra] devstack failed './stack.sh:1224:start_nova_api'

 

Dear all,

 

Our CI failed at devstack setup.

The error messages in devstacklog is as below:


2014-12-07 22:33:47.959 | ./stack.sh:1224:start_nova_api

2014-12-07 22:33:47.959 | /opt/stack/new/devstack/lib/nova:701:die

2014-12-07 22:33:47.965 | [ERROR] /opt/stack/new/devstack/lib/nova:701
nova-api did not start

2014-12-07 22:33:48.970 | exit_trap: cleaning up child processes

2014-12-07 22:33:48.970 | ./stack.sh: line 441: kill: (5161) - No such
process

2014-12-07 22:33:48.971 | Error on exit

2014-12-07 22:33:49.019 | World dumping... see
/opt/stack/new/worlddump-2014-12-07-223349.txt for details

2014-12-07 22:33:49.086 | ./stack.sh: line 434:   428 Terminated
_old_run_process "$service" "$command"

 

Seems there's something wrong with nova-api.

Has someone met this too? 

Any suggestion or clue will be appreciated.

 

Thanks and regards

~

| Wan Shan  (Sam)

| Openstack Certification | EMC E-Lab

| Tel: +86-28-82966713

| Addr: 7F, C12, Tianfu Software Park, Chengdu, Sichuan, P. R. of China

~

 

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

Re: [OpenStack-Infra] devstack failed './stack.sh:1224:start_nova_api'

[Wan, Sam]

Hi Rick,

Thanks.
Actually I only upgraded 'retrying' and that works

Thanks and regards
~
| Wan Shan  (Sam)
| Openstack Certification | EMC E-Lab
| Tel: +86-28-82966713
| Addr: 7F, C12, Tianfu Software Park, Chengdu, Sichuan, P. R. of China
~

From: Rick Chen [mailto:rick.c...@prophetstor.com]
Sent: Monday, December 08, 2014 6:07 PM
To: Wan, Sam; openstack-infra@lists.openstack.org
Subject: RE: [OpenStack-Infra] devstack failed './stack.sh:1224:start_nova_api'

HI Sam:
I happed same issue. In the some log has trace-back in the oslo 
package, but I forgot which one.
I try to update all oslo.XXX that can solve this problem.
Ex:
pip install oslo.concurrency --upgrade

From: Wan, Sam [mailto:sam@emc.com]
Sent: Monday, December 08, 2014 4:14 PM
To: 
openstack-infra@lists.openstack.org
Subject: [OpenStack-Infra] devstack failed './stack.sh:1224:start_nova_api'

Dear all,

Our CI failed at devstack setup.
The error messages in devstacklog is as below:
2014-12-07 22:33:47.959 | ./stack.sh:1224:start_nova_api
2014-12-07 22:33:47.959 | /opt/stack/new/devstack/lib/nova:701:die
2014-12-07 22:33:47.965 | [ERROR] /opt/stack/new/devstack/lib/nova:701 nova-api 
did not start
2014-12-07 22:33:48.970 | exit_trap: cleaning up child processes
2014-12-07 22:33:48.970 | ./stack.sh: line 441: kill: (5161) - No such process
2014-12-07 22:33:48.971 | Error on exit
2014-12-07 22:33:49.019 | World dumping... see 
/opt/stack/new/worlddump-2014-12-07-223349.txt for details
2014-12-07 22:33:49.086 | ./stack.sh: line 434:   428 Terminated  
_old_run_process "$service" "$command"


Seems there's something wrong with nova-api.
Has someone met this too?
Any suggestion or clue will be appreciated.

Thanks and regards
~
| Wan Shan  (Sam)
| Openstack Certification | EMC E-Lab
| Tel: +86-28-82966713
| Addr: 7F, C12, Tianfu Software Park, Chengdu, Sichuan, P. R. of China
~

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

Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for Additional Meeting for third-party

[Erlon Cruz]

I agree that 2 meetings per week will mess things up. 1+ for alternating
meetings.

On Fri, Dec 5, 2014 at 1:08 PM, Kurt Taylor  wrote:

> In my opinion, further discussion is needed. The proposal on the table is
> to have 2 weekly meetings, one at the existing time of 1800UTC on Monday
> and, also in the same week, to have another meeting at 0800 UTC on Tuesday.
>
> Here are some of the problems that I see with this approach:
>
> 1. Meeting content: Having 2 meetings per week is more than is needed at
> this stage of the working group. There just isn't enough meeting content to
> justify having two meetings every week.
>
> 2. Decisions: Any decision made at one meeting will potentially be undone
> at the next, or at least not fully explained. It will be difficult to keep
> consistent direction with the overall work group.
>
> 3. Meeting chair(s): Currently we do not have a commitment for a long-term
> chair of this new second weekly meeting. I will not be able to attend this
> new meeting at the proposed time.
>
> 4. Current meeting time: I am not aware of anyone that likes the current
> time of 1800 UTC on Monday. The current time is the main reason it is hard
> for EU and APAC CI Operators to attend.
>
> My proposal was to have only 1 meeting per week at alternating times, just
> as other work groups have done to solve this problem. (See examples at:
> https://wiki.openstack.org/wiki/Meetings)  I volunteered to chair, then
> ask other CI Operators to chair as the meetings evolved. The meeting times
> could be any between 1300-0300 UTC. That way, one week we are good for US
> and Europe, the next week for APAC.
>
> Kurt Taylor (krtaylor)
>
>
> On Wed, Dec 3, 2014 at 11:10 PM, trinath.soman...@freescale.com <
> trinath.soman...@freescale.com> wrote:
>
>> +1.
>>
>> --
>> Trinath Somanchi - B39208
>> trinath.soman...@freescale.com | extn: 4048
>>
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info]
>> Sent: Thursday, December 04, 2014 3:55 AM
>> To: openstack-infra@lists.openstack.org
>> Subject: Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for
>> Additional Meeting for third-party
>>
>> On 12/03/2014 03:15 AM, Omri Marcovitch wrote:
>> > Hello Anteaya,
>> >
>> > A meeting between 8:00 - 16:00 UTC time will be great (Israel).
>> >
>> >
>> > Thanks
>> > Omri
>> >
>> > -Original Message-
>> > From: Joshua Hesketh [mailto:joshua.hesk...@rackspace.com]
>> > Sent: Wednesday, December 03, 2014 9:04 AM
>> > To: He, Yongli; OpenStack Development Mailing List (not for usage
>> > questions); openstack-infra@lists.openstack.org
>> > Subject: Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for
>> > Additional Meeting for third-party
>> >
>> > Hey,
>> >
>> > 0700 -> 1000 UTC would work for me most weeks fwiw.
>> >
>> > Cheers,
>> > Josh
>> >
>> > Rackspace Australia
>> >
>> > On 12/3/14 11:17 AM, He, Yongli wrote:
>> >> anteaya,
>> >>
>> >> UTC 7:00 AM to UTC9:00, or UTC11:30 to UTC13:00 is ideal time for
>> china.
>> >>
>> >> if there is no time slot there, just pick up any time between UTC
>> >> 7:00 AM to UCT 13:00. ( UTC9:00 to UTC 11:30 is on road to home and
>> >> dinner.)
>> >>
>> >> Yongi He
>> >> -Original Message-
>> >> From: Anita Kuno [mailto:ante...@anteaya.info]
>> >> Sent: Tuesday, December 02, 2014 4:07 AM
>> >> To: openstack Development Mailing List;
>> >> openstack-infra@lists.openstack.org
>> >> Subject: [openstack-dev] [third-party]Time for Additional Meeting for
>> >> third-party
>> >>
>> >> One of the actions from the Kilo Third-Party CI summit session was to
>> start up an additional meeting for CI operators to participate from
>> non-North American time zones.
>> >>
>> >> Please reply to this email with times/days that would work for you.
>> The current third party meeting is on Mondays at 1800 utc which works well
>> since Infra meetings are on Tuesdays. If we could find a time that works
>> for Europe and APAC that is also on Monday that would be ideal.
>> >>
>> >> Josh Hesketh has said he will try to be available for these meetings,
>> he is in Australia.
>> >>
>> >> Let's get a sense of what days and timeframes work for those
>> interested and then we can narrow it down and pick a channel.
>> >>
>> >> Thanks everyone,
>> >> Anita.
>> >>
>>
>> Okay first of all thanks to everyone who replied.
>>
>> Again, to clarify, the purpose of this thread has been to find a suitable
>> additional third-party meeting time geared towards folks in EU and APAC. We
>> live on a sphere, there is no time that will suit everyone.
>>
>> It looks like we are converging on 0800 UTC as a time and I am going to
>> suggest Tuesdays. We have very little competition for space at that date
>> + time combination so we can use #openstack-meeting (I have already
>> booked the space on the wikipage).
>>
>> So barring further discussion, see you then!
>>
>> Thanks everyone,
>> Anita.
>>
>> ___
>> OpenStack-Infra mailing li

Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for Additional Meeting for third-party

[trinath.soman...@freescale.com]

With Kurt Taylor. +1

Very nice idea to start with.

--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048

From: Kurt Taylor [mailto:kurt.r.tay...@gmail.com]
Sent: Friday, December 05, 2014 8:39 PM
To: OpenStack Development Mailing List (not for usage questions); 
openstack-infra@lists.openstack.org
Subject: Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for Additional 
Meeting for third-party

In my opinion, further discussion is needed. The proposal on the table is to 
have 2 weekly meetings, one at the existing time of 1800UTC on Monday and, also 
in the same week, to have another meeting at 0800 UTC on Tuesday.

Here are some of the problems that I see with this approach:

1. Meeting content: Having 2 meetings per week is more than is needed at this 
stage of the working group. There just isn't enough meeting content to justify 
having two meetings every week.

2. Decisions: Any decision made at one meeting will potentially be undone at 
the next, or at least not fully explained. It will be difficult to keep 
consistent direction with the overall work group.

3. Meeting chair(s): Currently we do not have a commitment for a long-term 
chair of this new second weekly meeting. I will not be able to attend this new 
meeting at the proposed time.

4. Current meeting time: I am not aware of anyone that likes the current time 
of 1800 UTC on Monday. The current time is the main reason it is hard for EU 
and APAC CI Operators to attend.

My proposal was to have only 1 meeting per week at alternating times, just as 
other work groups have done to solve this problem. (See examples at: 
https://wiki.openstack.org/wiki/Meetings)  I volunteered to chair, then ask 
other CI Operators to chair as the meetings evolved. The meeting times could be 
any between 1300-0300 UTC. That way, one week we are good for US and Europe, 
the next week for APAC.

Kurt Taylor (krtaylor)


On Wed, Dec 3, 2014 at 11:10 PM, 
trinath.soman...@freescale.com 
mailto:trinath.soman...@freescale.com>> wrote:
+1.

--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 
4048

-Original Message-
From: Anita Kuno [mailto:ante...@anteaya.info]
Sent: Thursday, December 04, 2014 3:55 AM
To: 
openstack-infra@lists.openstack.org
Subject: Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for Additional 
Meeting for third-party

On 12/03/2014 03:15 AM, Omri Marcovitch wrote:
> Hello Anteaya,
>
> A meeting between 8:00 - 16:00 UTC time will be great (Israel).
>
>
> Thanks
> Omri
>
> -Original Message-
> From: Joshua Hesketh 
> [mailto:joshua.hesk...@rackspace.com]
> Sent: Wednesday, December 03, 2014 9:04 AM
> To: He, Yongli; OpenStack Development Mailing List (not for usage
> questions); 
> openstack-infra@lists.openstack.org
> Subject: Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for
> Additional Meeting for third-party
>
> Hey,
>
> 0700 -> 1000 UTC would work for me most weeks fwiw.
>
> Cheers,
> Josh
>
> Rackspace Australia
>
> On 12/3/14 11:17 AM, He, Yongli wrote:
>> anteaya,
>>
>> UTC 7:00 AM to UTC9:00, or UTC11:30 to UTC13:00 is ideal time for china.
>>
>> if there is no time slot there, just pick up any time between UTC
>> 7:00 AM to UCT 13:00. ( UTC9:00 to UTC 11:30 is on road to home and
>> dinner.)
>>
>> Yongi He
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info]
>> Sent: Tuesday, December 02, 2014 4:07 AM
>> To: openstack Development Mailing List;
>> openstack-infra@lists.openstack.org
>> Subject: [openstack-dev] [third-party]Time for Additional Meeting for
>> third-party
>>
>> One of the actions from the Kilo Third-Party CI summit session was to start 
>> up an additional meeting for CI operators to participate from non-North 
>> American time zones.
>>
>> Please reply to this email with times/days that would work for you. The 
>> current third party meeting is on Mondays at 1800 utc which works well since 
>> Infra meetings are on Tuesdays. If we could find a time that works for 
>> Europe and APAC that is also on Monday that would be ideal.
>>
>> Josh Hesketh has said he will try to be available for these meetings, he is 
>> in Australia.
>>
>> Let's get a sense of what days and timeframes work for those interested and 
>> then we can narrow it down and pick a channel.
>>
>> Thanks everyone,
>> Anita.
>>

Okay first of all thanks to everyone who replied.

Again, to clarify, the purpose of this thread has been to find a suitable 
additional third-party meeting time geared towards folks in EU and APAC. We 
live on a sphere, there is no time that will suit everyone.

It looks like we are converging on 0800 UTC as a time and I am going to su

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

[Eduard Matei]

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

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

Any ideas?

Thanks,
Eduard

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

> Hello everyone,
>
> Thanks to the latest changes to the creation of service accounts process
> we're one step closer to setting up our own CI platform for Cinder.
>
> So far we've got:
> - Jenkins master (with Gerrit plugin) and slave (with DevStack and our
> storage solution)
> - Service account configured and tested (can manually connect to
> review.openstack.org and get events and publish comments)
>
> Next step would be to set up a job to do the actual testing, this is where
> we're stuck.
> Can someone please point us to a clear example on how a job should look
> like (preferably for testing Cinder on Kilo)? Most links we've found are
> broken, or tools/scripts are no longer working.
> Also, we cannot change the Jenkins master too much (it's owned by Ops team
> and they need a list of tools/scripts to review before installing/running
> so we're not allowed to experiment).
>
> Thanks,
> Eduard
>
> --
>
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.ma...@cloudfounders.com
>
>
>
> *CloudFounders, The Private Cloud Software Company*
>
> Disclaimer:
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to whom they are addressed.
> If you are not the named addressee or an employee or agent responsible for 
> delivering this message to the named addressee, you are hereby notified that 
> you are not authorized to read, print, retain, copy or disseminate this 
> message or any part of it. If you have received this email in error we 
> request you to notify us by reply e-mail and to delete all electronic files 
> of the message. If you are not the intended recipient you are notified that 
> disclosing, copying, distributing or taking any action in reliance on the 
> contents of this information is strictly prohibited.
> E-mail transmission cannot be guaranteed to be secure or error free as 
> information could be intercepted, corrupted, lost, destroyed, arrive late or 
> incomplete, or contain viruses. The sender therefore does not accept 
> liability for any errors or omissions in the content of this message, and 
> shall have no liability for any loss or damage suffered by the user, which 
> arise as a result of e-mail transmission.
>
>


-- 

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



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] [Infra] Meeting Tuesday December 9th at 19:00 UTC

[Elizabeth K. Joseph]

Hi everyone,

The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting on Tuesday December 9th, 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.

And in case you missed it, meeting log and minutes from the last
meeting are available here:

Minutes: 
http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-12-02-19.01.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-12-02-19.01.txt
Log: 
http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-12-02-19.01.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

Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for Additional Meeting for third-party

[Steve Weston]

Hi Everyone,

I have summarized the responses so far in a Google spreadsheet document [1].

Looks like the consensus has converged on alternating meetings, in UTC:

Week 1 - Mondays 1800 or 1300
Week 2 - Tuesdays 0800

I would be agreeable to moving the Monday meeting to Wednesday, and 
alternating as Kurt suggested.  I have set up a Google moderator page 
[2] so that all interested parties can provide their input for a final 
tally.


[1] 
https://docs.google.com/spreadsheets/d/1glmZirKpp1wGvcJ0Zx35IkmJ23CSpfq2NoAK3_vW6b8/pubhtml

[2] https://www.google.com/moderator/#16/e=21b93c

Thanks,
Steve Weston
Triniplex

On 12/8/14 5:48 AM, trinath.soman...@freescale.com wrote:


With Kurt Taylor. +1

Very nice idea to start with.

--

Trinath Somanchi - B39208

trinath.soman...@freescale.com| extn: 4048

*From:*Kurt Taylor [mailto:kurt.r.tay...@gmail.com]
*Sent:* Friday, December 05, 2014 8:39 PM
*To:* OpenStack Development Mailing List (not for usage questions); 
openstack-infra@lists.openstack.org
*Subject:* Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for 
Additional Meeting for third-party


In my opinion, further discussion is needed. The proposal on the table 
is to have 2 weekly meetings, one at the existing time of 1800UTC on 
Monday and, also in the same week, to have another meeting at 0800 UTC 
on Tuesday.


Here are some of the problems that I see with this approach:

1. Meeting content: Having 2 meetings per week is more than is needed 
at this stage of the working group. There just isn't enough meeting 
content to justify having two meetings every week.


2. Decisions: Any decision made at one meeting will potentially be 
undone at the next, or at least not fully explained. It will be 
difficult to keep consistent direction with the overall work group.


3. Meeting chair(s): Currently we do not have a commitment for a 
long-term chair of this new second weekly meeting. I will not be able 
to attend this new meeting at the proposed time.


4. Current meeting time: I am not aware of anyone that likes the 
current time of 1800 UTC on Monday. The current time is the main 
reason it is hard for EU and APAC CI Operators to attend.


My proposal was to have only 1 meeting per week at alternating times, 
just as other work groups have done to solve this problem. (See 
examples at: https://wiki.openstack.org/wiki/Meetings)  I volunteered 
to chair, then ask other CI Operators to chair as the meetings 
evolved. The meeting times could be any between 1300-0300 UTC. That 
way, one week we are good for US and Europe, the next week for APAC.


Kurt Taylor (krtaylor)

On Wed, Dec 3, 2014 at 11:10 PM, trinath.soman...@freescale.com 
 
> wrote:


+1.

--
Trinath Somanchi - B39208
trinath.soman...@freescale.com
 | extn: 4048

-Original Message-
From: Anita Kuno [mailto:ante...@anteaya.info
]
Sent: Thursday, December 04, 2014 3:55 AM
To: openstack-infra@lists.openstack.org


Subject: Re: [OpenStack-Infra] [openstack-dev] [third-party]Time
for Additional Meeting for third-party

On 12/03/2014 03:15 AM, Omri Marcovitch wrote:
> Hello Anteaya,
>
> A meeting between 8:00 - 16:00 UTC time will be great (Israel).
>
>
> Thanks
> Omri
>
> -Original Message-
> From: Joshua Hesketh [mailto:joshua.hesk...@rackspace.com
]
> Sent: Wednesday, December 03, 2014 9:04 AM
> To: He, Yongli; OpenStack Development Mailing List (not for usage
> questions); openstack-infra@lists.openstack.org

> Subject: Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for
> Additional Meeting for third-party
>
> Hey,
>
> 0700 -> 1000 UTC would work for me most weeks fwiw.
>
> Cheers,
> Josh
>
> Rackspace Australia
>
> On 12/3/14 11:17 AM, He, Yongli wrote:
>> anteaya,
>>
>> UTC 7:00 AM to UTC9:00, or UTC11:30 to UTC13:00 is ideal time
for china.
>>
>> if there is no time slot there, just pick up any time between UTC
>> 7:00 AM to UCT 13:00. ( UTC9:00 to UTC 11:30 is on road to home and
>> dinner.)
>>
>> Yongi He
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info
]
>> Sent: Tuesday, December 02, 2014 4:07 AM
>> To: openstack Development Mailing List;
>> openstack-infra@lists.openstack.org

>> Subject: [openstack-dev] [third-party]Time for Additional
Meeting for
>> third-party
>>
>> One of the actions from the Kilo Third-Party CI summit session
was to start up an additional meeting for CI operators to
  

Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for Additional Meeting for third-party

[Kurt Taylor]

Thanks Steve, you beat me to it by just a few minutes.  :)  Can you load up
these times?

I was going to propose the following (all UTC and on Wednesday, alternating
weeks):
A) 12:00 and 22:00
B) 13:00 and 02:00
C) 14:00 and 03:00
D) 15:00 and 04:00

These times would alternate weeks, for instance one week the first time,
the next week the second time.

Vote for your favorite from the above, A, B, C, D.

Thanks everyone!
Kurt Taylor (krtaylor)


On Mon, Dec 8, 2014 at 8:50 PM, Steve Weston 
wrote:

>  Hi Everyone,
>
> I have summarized the responses so far in a Google spreadsheet document
> [1].
>
> Looks like the consensus has converged on alternating meetings, in UTC:
>
> Week 1 - Mondays 1800 or 1300
> Week 2 - Tuesdays 0800
>
> I would be agreeable to moving the Monday meeting to Wednesday, and
> alternating as Kurt suggested.  I have set up a Google moderator page [2]
> so that all interested parties can provide their input for a final tally.
>
> [1]
> https://docs.google.com/spreadsheets/d/1glmZirKpp1wGvcJ0Zx35IkmJ23CSpfq2NoAK3_vW6b8/pubhtml
> [2] https://www.google.com/moderator/#16/e=21b93c
>
> Thanks,
> Steve Weston
> Triniplex
>
> On 12/8/14 5:48 AM, trinath.soman...@freescale.com wrote:
>
>  With Kurt Taylor. +1
>
>
>
> Very nice idea to start with.
>
>
>
> --
>
> Trinath Somanchi - B39208
>
> trinath.soman...@freescale.com | extn: 4048
>
>
>
> *From:* Kurt Taylor [mailto:kurt.r.tay...@gmail.com
> ]
> *Sent:* Friday, December 05, 2014 8:39 PM
> *To:* OpenStack Development Mailing List (not for usage questions);
> openstack-infra@lists.openstack.org
> *Subject:* Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for
> Additional Meeting for third-party
>
>
>
> In my opinion, further discussion is needed. The proposal on the table is
> to have 2 weekly meetings, one at the existing time of 1800UTC on Monday
> and, also in the same week, to have another meeting at 0800 UTC on Tuesday.
>
>
>
> Here are some of the problems that I see with this approach:
>
>
>
> 1. Meeting content: Having 2 meetings per week is more than is needed at
> this stage of the working group. There just isn't enough meeting content to
> justify having two meetings every week.
>
>
>
> 2. Decisions: Any decision made at one meeting will potentially be undone
> at the next, or at least not fully explained. It will be difficult to keep
> consistent direction with the overall work group.
>
>
>
> 3. Meeting chair(s): Currently we do not have a commitment for a long-term
> chair of this new second weekly meeting. I will not be able to attend this
> new meeting at the proposed time.
>
>
>
> 4. Current meeting time: I am not aware of anyone that likes the current
> time of 1800 UTC on Monday. The current time is the main reason it is hard
> for EU and APAC CI Operators to attend.
>
>
>
> My proposal was to have only 1 meeting per week at alternating times, just
> as other work groups have done to solve this problem. (See examples at:
> https://wiki.openstack.org/wiki/Meetings)  I volunteered to chair, then
> ask other CI Operators to chair as the meetings evolved. The meeting times
> could be any between 1300-0300 UTC. That way, one week we are good for US
> and Europe, the next week for APAC.
>
>
>
> Kurt Taylor (krtaylor)
>
>
>
>
>
> On Wed, Dec 3, 2014 at 11:10 PM, trinath.soman...@freescale.com <
> trinath.soman...@freescale.com> wrote:
>
> +1.
>
> --
> Trinath Somanchi - B39208
> trinath.soman...@freescale.com | extn: 4048
>
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info]
> Sent: Thursday, December 04, 2014 3:55 AM
> To: openstack-infra@lists.openstack.org
>
> Subject: Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for
> Additional Meeting for third-party
>
> On 12/03/2014 03:15 AM, Omri Marcovitch wrote:
> > Hello Anteaya,
> >
> > A meeting between 8:00 - 16:00 UTC time will be great (Israel).
> >
> >
> > Thanks
> > Omri
> >
> > -Original Message-
> > From: Joshua Hesketh [mailto:joshua.hesk...@rackspace.com]
> > Sent: Wednesday, December 03, 2014 9:04 AM
> > To: He, Yongli; OpenStack Development Mailing List (not for usage
> > questions); openstack-infra@lists.openstack.org
> > Subject: Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for
> > Additional Meeting for third-party
> >
> > Hey,
> >
> > 0700 -> 1000 UTC would work for me most weeks fwiw.
> >
> > Cheers,
> > Josh
> >
> > Rackspace Australia
> >
> > On 12/3/14 11:17 AM, He, Yongli wrote:
> >> anteaya,
> >>
> >> UTC 7:00 AM to UTC9:00, or UTC11:30 to UTC13:00 is ideal time for china.
> >>
> >> if there is no time slot there, just pick up any time between UTC
> >> 7:00 AM to UCT 13:00. ( UTC9:00 to UTC 11:30 is on road to home and
> >> dinner.)
> >>
> >> Yongi He
> >> -Original Message-
> >> From: Anita Kuno [mailto:ante...@anteaya.info]
> >> Sent: Tuesday, December 02, 2014 4:07 AM
> >> To: openstack Development Mailing List;
> >> openstack-infra@lists.openstack.org
> >> Subject: [openstack-dev] [third-

Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for Additional Meeting for third-party

[Steve Weston]

Times are entered.  Let the voting begin!!

On 12/8/14 7:29 PM, Kurt Taylor wrote:
Thanks Steve, you beat me to it by just a few minutes.  :)  Can you 
load up these times?


I was going to propose the following (all UTC and on Wednesday, 
alternating weeks):

A) 12:00 and 22:00
B) 13:00 and 02:00
C) 14:00 and 03:00
D) 15:00 and 04:00

These times would alternate weeks, for instance one week the first 
time, the next week the second time.


Vote for your favorite from the above, A, B, C, D.

Thanks everyone!
Kurt Taylor (krtaylor)


On Mon, Dec 8, 2014 at 8:50 PM, Steve Weston 
mailto:steve.wes...@triniplex.com>> wrote:


Hi Everyone,

I have summarized the responses so far in a Google spreadsheet
document [1].

Looks like the consensus has converged on alternating meetings, in
UTC:

Week 1 - Mondays 1800 or 1300
Week 2 - Tuesdays 0800

I would be agreeable to moving the Monday meeting to Wednesday,
and alternating as Kurt suggested.  I have set up a Google
moderator page [2] so that all interested parties can provide
their input for a final tally.

[1]

https://docs.google.com/spreadsheets/d/1glmZirKpp1wGvcJ0Zx35IkmJ23CSpfq2NoAK3_vW6b8/pubhtml
[2] https://www.google.com/moderator/#16/e=21b93c

Thanks,
Steve Weston
Triniplex

On 12/8/14 5:48 AM, trinath.soman...@freescale.com
 wrote:


With Kurt Taylor. +1

Very nice idea to start with.

--

Trinath Somanchi - B39208

trinath.soman...@freescale.com| extn: 4048

*From:*Kurt Taylor [mailto:kurt.r.tay...@gmail.com]
*Sent:* Friday, December 05, 2014 8:39 PM
*To:* OpenStack Development Mailing List (not for usage
questions); openstack-infra@lists.openstack.org

*Subject:* Re: [OpenStack-Infra] [openstack-dev]
[third-party]Time for Additional Meeting for third-party

In my opinion, further discussion is needed. The proposal on the
table is to have 2 weekly meetings, one at the existing time of
1800UTC on Monday and, also in the same week, to have another
meeting at 0800 UTC on Tuesday.

Here are some of the problems that I see with this approach:

1. Meeting content: Having 2 meetings per week is more than is
needed at this stage of the working group. There just isn't
enough meeting content to justify having two meetings every week.

2. Decisions: Any decision made at one meeting will potentially
be undone at the next, or at least not fully explained. It will
be difficult to keep consistent direction with the overall work
group.

3. Meeting chair(s): Currently we do not have a commitment for a
long-term chair of this new second weekly meeting. I will not be
able to attend this new meeting at the proposed time.

4. Current meeting time: I am not aware of anyone that likes the
current time of 1800 UTC on Monday. The current time is the main
reason it is hard for EU and APAC CI Operators to attend.

My proposal was to have only 1 meeting per week at alternating
times, just as other work groups have done to solve this problem.
(See examples at: https://wiki.openstack.org/wiki/Meetings)  I
volunteered to chair, then ask other CI Operators to chair as the
meetings evolved. The meeting times could be any between
1300-0300 UTC. That way, one week we are good for US and Europe,
the next week for APAC.

Kurt Taylor (krtaylor)

On Wed, Dec 3, 2014 at 11:10 PM, trinath.soman...@freescale.com

mailto:trinath.soman...@freescale.com>> wrote:

+1.

--
Trinath Somanchi - B39208
trinath.soman...@freescale.com
 | extn: 4048

-Original Message-
From: Anita Kuno [mailto:ante...@anteaya.info
]
Sent: Thursday, December 04, 2014 3:55 AM
To: openstack-infra@lists.openstack.org


Subject: Re: [OpenStack-Infra] [openstack-dev]
[third-party]Time for Additional Meeting for third-party

On 12/03/2014 03:15 AM, Omri Marcovitch wrote:
> Hello Anteaya,
>
> A meeting between 8:00 - 16:00 UTC time will be great (Israel).
>
>
> Thanks
> Omri
>
> -Original Message-
> From: Joshua Hesketh [mailto:joshua.hesk...@rackspace.com
]
> Sent: Wednesday, December 03, 2014 9:04 AM
> To: He, Yongli; OpenStack Development Mailing List (not for
usage
> questions); openstack-infra@lists.openstack.org

> Subject: Re: [openstack-dev] [OpenStack-Infra]
[third-party]Time for
> Additional Meeting f

Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for Additional Meeting for third-party

[Anita Kuno]

I'm not doing alternating meetings. I am doing additional meetings as I
always said I would.

I will be in channel at 0800 utc in #openstack-meeting on Tuesday.

All are welcome to attend.

Thank you,
Anita.

On 12/08/2014 09:48 PM, Steve Weston wrote:
> Times are entered.  Let the voting begin!!
> 
> On 12/8/14 7:29 PM, Kurt Taylor wrote:
>> Thanks Steve, you beat me to it by just a few minutes.  :)  Can you
>> load up these times?
>>
>> I was going to propose the following (all UTC and on Wednesday,
>> alternating weeks):
>> A) 12:00 and 22:00
>> B) 13:00 and 02:00
>> C) 14:00 and 03:00
>> D) 15:00 and 04:00
>>
>> These times would alternate weeks, for instance one week the first
>> time, the next week the second time.
>>
>> Vote for your favorite from the above, A, B, C, D.
>>
>> Thanks everyone!
>> Kurt Taylor (krtaylor)
>>
>>
>> On Mon, Dec 8, 2014 at 8:50 PM, Steve Weston
>> mailto:steve.wes...@triniplex.com>> wrote:
>>
>> Hi Everyone,
>>
>> I have summarized the responses so far in a Google spreadsheet
>> document [1].
>>
>> Looks like the consensus has converged on alternating meetings, in
>> UTC:
>>
>> Week 1 - Mondays 1800 or 1300
>> Week 2 - Tuesdays 0800
>>
>> I would be agreeable to moving the Monday meeting to Wednesday,
>> and alternating as Kurt suggested.  I have set up a Google
>> moderator page [2] so that all interested parties can provide
>> their input for a final tally.
>>
>> [1]
>>
>> https://docs.google.com/spreadsheets/d/1glmZirKpp1wGvcJ0Zx35IkmJ23CSpfq2NoAK3_vW6b8/pubhtml
>>
>> [2] https://www.google.com/moderator/#16/e=21b93c
>>
>> Thanks,
>> Steve Weston
>> Triniplex
>>
>> On 12/8/14 5:48 AM, trinath.soman...@freescale.com
>>  wrote:
>>>
>>> With Kurt Taylor. +1
>>>
>>> Very nice idea to start with.
>>>
>>> --
>>>
>>> Trinath Somanchi - B39208
>>>
>>> trinath.soman...@freescale.com| extn: 4048
>>>
>>> *From:*Kurt Taylor [mailto:kurt.r.tay...@gmail.com]
>>> *Sent:* Friday, December 05, 2014 8:39 PM
>>> *To:* OpenStack Development Mailing List (not for usage
>>> questions); openstack-infra@lists.openstack.org
>>> 
>>> *Subject:* Re: [OpenStack-Infra] [openstack-dev]
>>> [third-party]Time for Additional Meeting for third-party
>>>
>>> In my opinion, further discussion is needed. The proposal on the
>>> table is to have 2 weekly meetings, one at the existing time of
>>> 1800UTC on Monday and, also in the same week, to have another
>>> meeting at 0800 UTC on Tuesday.
>>>
>>> Here are some of the problems that I see with this approach:
>>>
>>> 1. Meeting content: Having 2 meetings per week is more than is
>>> needed at this stage of the working group. There just isn't
>>> enough meeting content to justify having two meetings every week.
>>>
>>> 2. Decisions: Any decision made at one meeting will potentially
>>> be undone at the next, or at least not fully explained. It will
>>> be difficult to keep consistent direction with the overall work
>>> group.
>>>
>>> 3. Meeting chair(s): Currently we do not have a commitment for a
>>> long-term chair of this new second weekly meeting. I will not be
>>> able to attend this new meeting at the proposed time.
>>>
>>> 4. Current meeting time: I am not aware of anyone that likes the
>>> current time of 1800 UTC on Monday. The current time is the main
>>> reason it is hard for EU and APAC CI Operators to attend.
>>>
>>> My proposal was to have only 1 meeting per week at alternating
>>> times, just as other work groups have done to solve this problem.
>>> (See examples at: https://wiki.openstack.org/wiki/Meetings)  I
>>> volunteered to chair, then ask other CI Operators to chair as the
>>> meetings evolved. The meeting times could be any between
>>> 1300-0300 UTC. That way, one week we are good for US and Europe,
>>> the next week for APAC.
>>>
>>> Kurt Taylor (krtaylor)
>>>
>>> On Wed, Dec 3, 2014 at 11:10 PM, trinath.soman...@freescale.com
>>> 
>>> >> > wrote:
>>>
>>> +1.
>>>
>>> --
>>> Trinath Somanchi - B39208
>>> trinath.soman...@freescale.com
>>>  | extn: 4048
>>>
>>> -Original Message-
>>> From: Anita Kuno [mailto:ante...@anteaya.info
>>> ]
>>> Sent: Thursday, December 04, 2014 3:55 AM
>>> To: openstack-infra@lists.openstack.org
>>> 
>>>
>>> Subject: Re: [OpenStack-Infra] [openstack-dev]
>>> [third-party]Time for Additional Meeting for third-party
>>>
>>> On 12/03/2014 03:15 AM, Omri Marcovitch wrote:
>>> > He