Re: [openstack-dev] [TripleO][Upgrade Squad syncup]

2016-12-15 Thread Marios Andreou
On 14/12/16 12:34, Marios Andreou wrote:
> On 14/12/16 11:17, Julie Pichon wrote:
>> On 14 December 2016 at 08:56, Dougal Matthews  wrote:
>>> On 13 December 2016 at 16:12, Emilien Macchi  wrote:

 On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou 
 wrote:
> Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1]
> lets schedule a syncup on the Ocata composable upgrades work and how we
> will build on Steve Hardy's base ansible driven implementation.
>
> IMO a call would be the best format (I propose to schedule a bluejeans
> call, though I am open to any other suggestions). For now I've setup a
> doodle poll at http://doodle.com/poll/rp8ck6tstaagftqr - please vote if
> you'd like to participate. Assuming we go with bluejeans (unless I hear
> strong pushback/other suggestions) then I'll try and make a recording
> available to address the concerns expressed at
>
> http://lists.openstack.org/pipermail/openstack-dev/2016-December/108780.html
> (thanks shardy for pointing that out).
>
> Moving forward we should probably switch to an irc based syncup,

 As long as:
 - we have zero pushbash from our community members
 - anyone can join the call
 - our design and discussions stay open (mailing-list, tripleo-specs, IRC)
 - a nice summary is sent to openstack-dev
>>>
>>> or maybe even better, a recording is posted online?
>>
>> Personally, I find summaries easier to parse compared to finding an
>> hour to listen to people talking back and forth about something,
>> though it doesn't need to be an either/or proposition :) One of the
>> issues brought up in the other thread about video calls is that they
>> can be difficult to follow for folks who don't have English as a first
>> language. Having a few written notes about what came up during the
>> meeting and some of the conclusions would help with this I think.
>>
>> Looking forward to seeing how the upgrade work comes along!
>>
>> Julie
>>
 - we keep tripleo meeting on IRC every week

 I don't see any blocker to do video-conference between folks that work
 together on a same topic.

> I'll close the poll at 10UTC tomorrow morning (sorry for short notice :(
> ) and schedule the meeting accordingly with a followup mail here,
> 
> 
> Looks like Thursday works for everybody. I've created an etherpad which
> we can use for the agenda and for notes during the call and with dial-in
> info @ https://etherpad.openstack.org/p/tripleo-upgrades-squad. I've
> added what imo are some reasonable defaults but please fix as
> appropriate - bear in mind we are aiming for a half hour quick call so
> may not get to solve all the things!
> 
> Thanks for the feedback about the video vs irc - lets see how we get on
> having both a recording and the etherpad for this first syncup,
> 
> thanks, marios



o/ OOO - thanks to everyone that participated and for anyone else that
is interested,  we just had this call... the recording is available at
https://bluejeans.com/s/xEi@S/ and there are notes at
https://etherpad.openstack.org/p/tripleo-upgrades-squad


thanks, marios




> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>
> thanks, marios
>
>
> [1]
>
> http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-12-13-14.00.log.html
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


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


Re: [openstack-dev] [TripleO][Upgrade Squad syncup]

2016-12-14 Thread mathieu bultel
On 12/14/2016 10:17 AM, Julie Pichon wrote:
> On 14 December 2016 at 08:56, Dougal Matthews  wrote:
>> On 13 December 2016 at 16:12, Emilien Macchi  wrote:
>>> On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou 
>>> wrote:
 Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1]
 lets schedule a syncup on the Ocata composable upgrades work and how we
 will build on Steve Hardy's base ansible driven implementation.

 IMO a call would be the best format (I propose to schedule a bluejeans
 call, though I am open to any other suggestions). For now I've setup a
 doodle poll at http://doodle.com/poll/rp8ck6tstaagftqr - please vote if
 you'd like to participate. Assuming we go with bluejeans (unless I hear
 strong pushback/other suggestions) then I'll try and make a recording
 available to address the concerns expressed at

 http://lists.openstack.org/pipermail/openstack-dev/2016-December/108780.html
 (thanks shardy for pointing that out).

 Moving forward we should probably switch to an irc based syncup,
>>> As long as:
>>> - we have zero pushbash from our community members
>>> - anyone can join the call
>>> - our design and discussions stay open (mailing-list, tripleo-specs, IRC)
>>> - a nice summary is sent to openstack-dev
>> or maybe even better, a recording is posted online?
> Personally, I find summaries easier to parse compared to finding an
> hour to listen to people talking back and forth about something,
> though it doesn't need to be an either/or proposition :) One of the
> issues brought up in the other thread about video calls is that they
> can be difficult to follow for folks who don't have English as a first
> language. Having a few written notes about what came up during the
Hehe, thanks Julie, I have excatly the same feeling, +1 with you :)

> meeting and some of the conclusions would help with this I think.
>
> Looking forward to seeing how the upgrade work comes along!
>
> Julie
>
>>> - we keep tripleo meeting on IRC every week
>>>
>>> I don't see any blocker to do video-conference between folks that work
>>> together on a same topic.
>>>
 I'll close the poll at 10UTC tomorrow morning (sorry for short notice :(
 ) and schedule the meeting accordingly with a followup mail here,


 thanks, marios


 [1]

 http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-12-13-14.00.log.html
> __
> 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] [TripleO][Upgrade Squad syncup]

2016-12-14 Thread Marios Andreou
On 14/12/16 11:17, Julie Pichon wrote:
> On 14 December 2016 at 08:56, Dougal Matthews  wrote:
>> On 13 December 2016 at 16:12, Emilien Macchi  wrote:
>>>
>>> On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou 
>>> wrote:
 Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1]
 lets schedule a syncup on the Ocata composable upgrades work and how we
 will build on Steve Hardy's base ansible driven implementation.

 IMO a call would be the best format (I propose to schedule a bluejeans
 call, though I am open to any other suggestions). For now I've setup a
 doodle poll at http://doodle.com/poll/rp8ck6tstaagftqr - please vote if
 you'd like to participate. Assuming we go with bluejeans (unless I hear
 strong pushback/other suggestions) then I'll try and make a recording
 available to address the concerns expressed at

 http://lists.openstack.org/pipermail/openstack-dev/2016-December/108780.html
 (thanks shardy for pointing that out).

 Moving forward we should probably switch to an irc based syncup,
>>>
>>> As long as:
>>> - we have zero pushbash from our community members
>>> - anyone can join the call
>>> - our design and discussions stay open (mailing-list, tripleo-specs, IRC)
>>> - a nice summary is sent to openstack-dev
>>
>> or maybe even better, a recording is posted online?
> 
> Personally, I find summaries easier to parse compared to finding an
> hour to listen to people talking back and forth about something,
> though it doesn't need to be an either/or proposition :) One of the
> issues brought up in the other thread about video calls is that they
> can be difficult to follow for folks who don't have English as a first
> language. Having a few written notes about what came up during the
> meeting and some of the conclusions would help with this I think.
> 
> Looking forward to seeing how the upgrade work comes along!
> 
> Julie
> 
>>> - we keep tripleo meeting on IRC every week
>>>
>>> I don't see any blocker to do video-conference between folks that work
>>> together on a same topic.
>>>
 I'll close the poll at 10UTC tomorrow morning (sorry for short notice :(
 ) and schedule the meeting accordingly with a followup mail here,


Looks like Thursday works for everybody. I've created an etherpad which
we can use for the agenda and for notes during the call and with dial-in
info @ https://etherpad.openstack.org/p/tripleo-upgrades-squad. I've
added what imo are some reasonable defaults but please fix as
appropriate - bear in mind we are aiming for a half hour quick call so
may not get to solve all the things!

Thanks for the feedback about the video vs irc - lets see how we get on
having both a recording and the etherpad for this first syncup,

thanks, marios











 thanks, marios


 [1]

 http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-12-13-14.00.log.html
> 
> __
> 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] [TripleO][Upgrade Squad syncup]

2016-12-14 Thread Julie Pichon
On 14 December 2016 at 08:56, Dougal Matthews  wrote:
> On 13 December 2016 at 16:12, Emilien Macchi  wrote:
>>
>> On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou 
>> wrote:
>> > Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1]
>> > lets schedule a syncup on the Ocata composable upgrades work and how we
>> > will build on Steve Hardy's base ansible driven implementation.
>> >
>> > IMO a call would be the best format (I propose to schedule a bluejeans
>> > call, though I am open to any other suggestions). For now I've setup a
>> > doodle poll at http://doodle.com/poll/rp8ck6tstaagftqr - please vote if
>> > you'd like to participate. Assuming we go with bluejeans (unless I hear
>> > strong pushback/other suggestions) then I'll try and make a recording
>> > available to address the concerns expressed at
>> >
>> > http://lists.openstack.org/pipermail/openstack-dev/2016-December/108780.html
>> > (thanks shardy for pointing that out).
>> >
>> > Moving forward we should probably switch to an irc based syncup,
>>
>> As long as:
>> - we have zero pushbash from our community members
>> - anyone can join the call
>> - our design and discussions stay open (mailing-list, tripleo-specs, IRC)
>> - a nice summary is sent to openstack-dev
>
> or maybe even better, a recording is posted online?

Personally, I find summaries easier to parse compared to finding an
hour to listen to people talking back and forth about something,
though it doesn't need to be an either/or proposition :) One of the
issues brought up in the other thread about video calls is that they
can be difficult to follow for folks who don't have English as a first
language. Having a few written notes about what came up during the
meeting and some of the conclusions would help with this I think.

Looking forward to seeing how the upgrade work comes along!

Julie

>> - we keep tripleo meeting on IRC every week
>>
>> I don't see any blocker to do video-conference between folks that work
>> together on a same topic.
>>
>> > I'll close the poll at 10UTC tomorrow morning (sorry for short notice :(
>> > ) and schedule the meeting accordingly with a followup mail here,
>> >
>> >
>> > thanks, marios
>> >
>> >
>> > [1]
>> >
>> > http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-12-13-14.00.log.html

__
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] [TripleO][Upgrade Squad syncup]

2016-12-14 Thread Dougal Matthews
On 13 December 2016 at 16:12, Emilien Macchi  wrote:

> On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou 
> wrote:
> > Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1]
> > lets schedule a syncup on the Ocata composable upgrades work and how we
> > will build on Steve Hardy's base ansible driven implementation.
> >
> > IMO a call would be the best format (I propose to schedule a bluejeans
> > call, though I am open to any other suggestions). For now I've setup a
> > doodle poll at http://doodle.com/poll/rp8ck6tstaagftqr - please vote if
> > you'd like to participate. Assuming we go with bluejeans (unless I hear
> > strong pushback/other suggestions) then I'll try and make a recording
> > available to address the concerns expressed at
> > http://lists.openstack.org/pipermail/openstack-dev/2016-
> December/108780.html
> > (thanks shardy for pointing that out).
> >
> > Moving forward we should probably switch to an irc based syncup,
>
> As long as:
> - we have zero pushbash from our community members
> - anyone can join the call
> - our design and discussions stay open (mailing-list, tripleo-specs, IRC)
> - a nice summary is sent to openstack-dev
>

or maybe even better, a recording is posted online?


> - we keep tripleo meeting on IRC every week
>
> I don't see any blocker to do video-conference between folks that work
> together on a same topic.
>
> > I'll close the poll at 10UTC tomorrow morning (sorry for short notice :(
> > ) and schedule the meeting accordingly with a followup mail here,
> >
> >
> > thanks, marios
> >
> >
> > [1]
> > http://eavesdrop.openstack.org/meetings/tripleo/2016/
> tripleo.2016-12-13-14.00.log.html
> >
> > 
> __
> > 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
>
>
>
> --
> Emilien Macchi
>
> __
> 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] [TripleO][Upgrade Squad syncup]

2016-12-13 Thread Emilien Macchi
On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou  wrote:
> Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1]
> lets schedule a syncup on the Ocata composable upgrades work and how we
> will build on Steve Hardy's base ansible driven implementation.
>
> IMO a call would be the best format (I propose to schedule a bluejeans
> call, though I am open to any other suggestions). For now I've setup a
> doodle poll at http://doodle.com/poll/rp8ck6tstaagftqr - please vote if
> you'd like to participate. Assuming we go with bluejeans (unless I hear
> strong pushback/other suggestions) then I'll try and make a recording
> available to address the concerns expressed at
> http://lists.openstack.org/pipermail/openstack-dev/2016-December/108780.html
> (thanks shardy for pointing that out).
>
> Moving forward we should probably switch to an irc based syncup,

As long as:
- we have zero pushbash from our community members
- anyone can join the call
- our design and discussions stay open (mailing-list, tripleo-specs, IRC)
- a nice summary is sent to openstack-dev
- we keep tripleo meeting on IRC every week

I don't see any blocker to do video-conference between folks that work
together on a same topic.

> I'll close the poll at 10UTC tomorrow morning (sorry for short notice :(
> ) and schedule the meeting accordingly with a followup mail here,
>
>
> thanks, marios
>
>
> [1]
> http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-12-13-14.00.log.html
>
> __
> 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



-- 
Emilien Macchi

__
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] [TripleO][Upgrade Squad syncup]

2016-12-13 Thread Marios Andreou
Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1]
lets schedule a syncup on the Ocata composable upgrades work and how we
will build on Steve Hardy's base ansible driven implementation.

IMO a call would be the best format (I propose to schedule a bluejeans
call, though I am open to any other suggestions). For now I've setup a
doodle poll at http://doodle.com/poll/rp8ck6tstaagftqr - please vote if
you'd like to participate. Assuming we go with bluejeans (unless I hear
strong pushback/other suggestions) then I'll try and make a recording
available to address the concerns expressed at
http://lists.openstack.org/pipermail/openstack-dev/2016-December/108780.html
(thanks shardy for pointing that out).

Moving forward we should probably switch to an irc based syncup,

I'll close the poll at 10UTC tomorrow morning (sorry for short notice :(
) and schedule the meeting accordingly with a followup mail here,


thanks, marios


[1]
http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-12-13-14.00.log.html

__
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