[openstack-dev] [kolla] repo split underway

2016-11-14 Thread Steven Dake (stdake)
Hey folks,

Thanks to the efforts of the openstyack-infra and release teams in coaching me 
through how to do the job properly, the repo split is ready to go (requires a 
couple +1’s from inc0 as he is the PTL of our merry band).

What this means is some patches that are merging now may have to be remerged if 
they touch ansible/* )since I had to take a snapshot of the kolla repository 
Saturday morning to remove all the tags/branches.  Boy that was somewhat 
painful ;(  Anyway, apologies for the remerge requirements.  I suspect inc0 
will send out an announcement when the repository split is finished.

Regards
-steve

__
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] [kolla] repo split

2016-07-27 Thread Ryan Hallisey
Agreed, it's been a week. The vote can be brought up again when
the conclusion of N is closer.

-Ryan

- Original Message -
From: "Steven Dake (stdake)" <std...@cisco.com>
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Sent: Wednesday, July 27, 2016 11:46:44 AM
Subject: Re: [openstack-dev] [kolla] repo split

Martin,

Thanks for your feedback.  This vote has expired without a consensus.  I
think we need to try a new vote once the core team gets comfortable with
the backporting process I spoke about earlier in a different thread this
vote would likely pass.

Regards
-steve

On 7/27/16, 3:09 AM, "Martin André" <m.an...@redhat.com> wrote:

>On Thu, Jul 21, 2016 at 5:21 PM, Steven Dake (stdake) <std...@cisco.com>
>wrote:
>> I am voting -1 for now, but would likely change my vote after we branch
>> Newton.  I'm not a super big fan of votes way ahead of major events
>>(such
>> as branching) because a bunch of things could change between now and
>>then
>> and the vote would be binding.
>>
>> Still community called the vote - so vote stands :)
>
>IIUC, if split there is, it's scheduled for when we branch out Newton
>which is only 1 month ahead.
>
>I'm +1 on splitting ansible deployment code into kolla-ansible.
>
>Martin
>
>> Regards
>> -steve
>>
>>
>> On 7/20/16, 1:48 PM, "Ryan Hallisey" <rhall...@redhat.com> wrote:
>>
>>>Hello.
>>>
>>>The repo split discussion that started at summit was brought up again at
>>>the midcycle.
>>>The discussion was focused around splitting the Docker containers and
>>>Ansible code into
>>>two separate repos [1].
>>>
>>>One of the main opponents to the split is backports.  Backports will
>>>need
>>>to be done
>>>by hand for a few releases.  So far, there hasn't been a ton of
>>>backports, but that could
>>>always change.
>>>
>>>As for splitting, it provides a much clearer view of what pieces of the
>>>project are where.
>>>Kolla-ansible with its own repo will sit along side kolla-kubernetes as
>>>consumers of the
>>>kolla repo.
>>>
>>>The target for the split will be for day 1 of Occata. The core team will
>>>vote on
>>>the change of splitting kolla into kolla-ansible and kolla.
>>>
>>>Cores please respond with a +1/-1 to approve or disapprove the repo
>>>split. Any community
>>>member feel free to weigh in with your opinion.
>>>
>>>+1
>>>-Ryan
>>>
>>>[1] - https://etherpad.openstack.org/p/kolla-N-midcycle-repo-split
>>>
>>>
>>>__
>>>OpenStack Development Mailing List (not for usage questions)
>>>Unsubscribe: 
>>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> 
>>_
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack 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] [kolla] repo split

2016-07-27 Thread Steven Dake (stdake)
Martin,

Thanks for your feedback.  This vote has expired without a consensus.  I
think we need to try a new vote once the core team gets comfortable with
the backporting process I spoke about earlier in a different thread this
vote would likely pass.

Regards
-steve

On 7/27/16, 3:09 AM, "Martin André"  wrote:

>On Thu, Jul 21, 2016 at 5:21 PM, Steven Dake (stdake) 
>wrote:
>> I am voting -1 for now, but would likely change my vote after we branch
>> Newton.  I'm not a super big fan of votes way ahead of major events
>>(such
>> as branching) because a bunch of things could change between now and
>>then
>> and the vote would be binding.
>>
>> Still community called the vote - so vote stands :)
>
>IIUC, if split there is, it's scheduled for when we branch out Newton
>which is only 1 month ahead.
>
>I'm +1 on splitting ansible deployment code into kolla-ansible.
>
>Martin
>
>> Regards
>> -steve
>>
>>
>> On 7/20/16, 1:48 PM, "Ryan Hallisey"  wrote:
>>
>>>Hello.
>>>
>>>The repo split discussion that started at summit was brought up again at
>>>the midcycle.
>>>The discussion was focused around splitting the Docker containers and
>>>Ansible code into
>>>two separate repos [1].
>>>
>>>One of the main opponents to the split is backports.  Backports will
>>>need
>>>to be done
>>>by hand for a few releases.  So far, there hasn't been a ton of
>>>backports, but that could
>>>always change.
>>>
>>>As for splitting, it provides a much clearer view of what pieces of the
>>>project are where.
>>>Kolla-ansible with its own repo will sit along side kolla-kubernetes as
>>>consumers of the
>>>kolla repo.
>>>
>>>The target for the split will be for day 1 of Occata. The core team will
>>>vote on
>>>the change of splitting kolla into kolla-ansible and kolla.
>>>
>>>Cores please respond with a +1/-1 to approve or disapprove the repo
>>>split. Any community
>>>member feel free to weigh in with your opinion.
>>>
>>>+1
>>>-Ryan
>>>
>>>[1] - https://etherpad.openstack.org/p/kolla-N-midcycle-repo-split
>>>
>>>
>>>__
>>>OpenStack Development Mailing List (not for usage questions)
>>>Unsubscribe: 
>>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> 
>>_
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack 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] [kolla] repo split

2016-07-27 Thread Martin André
On Thu, Jul 21, 2016 at 5:21 PM, Steven Dake (stdake)  wrote:
> I am voting -1 for now, but would likely change my vote after we branch
> Newton.  I'm not a super big fan of votes way ahead of major events (such
> as branching) because a bunch of things could change between now and then
> and the vote would be binding.
>
> Still community called the vote - so vote stands :)

IIUC, if split there is, it's scheduled for when we branch out Newton
which is only 1 month ahead.

I'm +1 on splitting ansible deployment code into kolla-ansible.

Martin

> Regards
> -steve
>
>
> On 7/20/16, 1:48 PM, "Ryan Hallisey"  wrote:
>
>>Hello.
>>
>>The repo split discussion that started at summit was brought up again at
>>the midcycle.
>>The discussion was focused around splitting the Docker containers and
>>Ansible code into
>>two separate repos [1].
>>
>>One of the main opponents to the split is backports.  Backports will need
>>to be done
>>by hand for a few releases.  So far, there hasn't been a ton of
>>backports, but that could
>>always change.
>>
>>As for splitting, it provides a much clearer view of what pieces of the
>>project are where.
>>Kolla-ansible with its own repo will sit along side kolla-kubernetes as
>>consumers of the
>>kolla repo.
>>
>>The target for the split will be for day 1 of Occata. The core team will
>>vote on
>>the change of splitting kolla into kolla-ansible and kolla.
>>
>>Cores please respond with a +1/-1 to approve or disapprove the repo
>>split. Any community
>>member feel free to weigh in with your opinion.
>>
>>+1
>>-Ryan
>>
>>[1] - https://etherpad.openstack.org/p/kolla-N-midcycle-repo-split
>>
>>__
>>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] [kolla] repo split

2016-07-21 Thread Steven Dake (stdake)
I am voting -1 for now, but would likely change my vote after we branch
Newton.  I'm not a super big fan of votes way ahead of major events (such
as branching) because a bunch of things could change between now and then
and the vote would be binding.

Still community called the vote - so vote stands :)

Regards
-steve


On 7/20/16, 1:48 PM, "Ryan Hallisey"  wrote:

>Hello.
>
>The repo split discussion that started at summit was brought up again at
>the midcycle.
>The discussion was focused around splitting the Docker containers and
>Ansible code into
>two separate repos [1].
>
>One of the main opponents to the split is backports.  Backports will need
>to be done
>by hand for a few releases.  So far, there hasn't been a ton of
>backports, but that could
>always change.
>
>As for splitting, it provides a much clearer view of what pieces of the
>project are where.
>Kolla-ansible with its own repo will sit along side kolla-kubernetes as
>consumers of the
>kolla repo.
>
>The target for the split will be for day 1 of Occata. The core team will
>vote on
>the change of splitting kolla into kolla-ansible and kolla.
>
>Cores please respond with a +1/-1 to approve or disapprove the repo
>split. Any community
>member feel free to weigh in with your opinion.
>
>+1
>-Ryan
>
>[1] - https://etherpad.openstack.org/p/kolla-N-midcycle-repo-split
>
>__
>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] [kolla] repo split

2016-07-20 Thread Britt Houser (bhouser)
-0 (My vote doesn't count).  We had endless problems keeping containers and 
orchestration in sync when we had two repos.  I am really impressed that Mitaka 
ansible can orchestrate Liberty containers.  That really speaks volumes.  And  
I understand there is a stable ABI now, but surely at some point in the future 
the ABI will need some unforeseen change?  Will we have ABI v1 and v2?  Seems 
like that will bring headaches, at least based on my past experience.


Thx,
britt

On 7/20/16, 6:32 PM, "Michał Jastrzębski"  wrote:

>+1 I was reluctant to repo split by Newton timeframe as it was crucial
>time to our project, people will start using it, and I didn't want to
>cause needless confusion. Now time is right imho.
>
>On 20 July 2016 at 15:48, Ryan Hallisey  wrote:
>> Hello.
>>
>> The repo split discussion that started at summit was brought up again at the 
>> midcycle.
>> The discussion was focused around splitting the Docker containers and 
>> Ansible code into
>> two separate repos [1].
>>
>> One of the main opponents to the split is backports.  Backports will need to 
>> be done
>> by hand for a few releases.  So far, there hasn't been a ton of backports, 
>> but that could
>> always change.
>>
>> As for splitting, it provides a much clearer view of what pieces of the 
>> project are where.
>> Kolla-ansible with its own repo will sit along side kolla-kubernetes as 
>> consumers of the
>> kolla repo.
>>
>> The target for the split will be for day 1 of Occata. The core team will 
>> vote on
>> the change of splitting kolla into kolla-ansible and kolla.
>>
>> Cores please respond with a +1/-1 to approve or disapprove the repo split. 
>> Any community
>> member feel free to weigh in with your opinion.
>>
>> +1
>> -Ryan
>>
>> [1] - https://etherpad.openstack.org/p/kolla-N-midcycle-repo-split
>>
>> __
>> 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] [kolla] repo split

2016-07-20 Thread Michał Jastrzębski
+1 I was reluctant to repo split by Newton timeframe as it was crucial
time to our project, people will start using it, and I didn't want to
cause needless confusion. Now time is right imho.

On 20 July 2016 at 15:48, Ryan Hallisey  wrote:
> Hello.
>
> The repo split discussion that started at summit was brought up again at the 
> midcycle.
> The discussion was focused around splitting the Docker containers and Ansible 
> code into
> two separate repos [1].
>
> One of the main opponents to the split is backports.  Backports will need to 
> be done
> by hand for a few releases.  So far, there hasn't been a ton of backports, 
> but that could
> always change.
>
> As for splitting, it provides a much clearer view of what pieces of the 
> project are where.
> Kolla-ansible with its own repo will sit along side kolla-kubernetes as 
> consumers of the
> kolla repo.
>
> The target for the split will be for day 1 of Occata. The core team will vote 
> on
> the change of splitting kolla into kolla-ansible and kolla.
>
> Cores please respond with a +1/-1 to approve or disapprove the repo split. 
> Any community
> member feel free to weigh in with your opinion.
>
> +1
> -Ryan
>
> [1] - https://etherpad.openstack.org/p/kolla-N-midcycle-repo-split
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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


[openstack-dev] [kolla] repo split

2016-07-20 Thread Ryan Hallisey
Hello.

The repo split discussion that started at summit was brought up again at the 
midcycle.
The discussion was focused around splitting the Docker containers and Ansible 
code into
two separate repos [1].

One of the main opponents to the split is backports.  Backports will need to be 
done
by hand for a few releases.  So far, there hasn't been a ton of backports, but 
that could
always change.

As for splitting, it provides a much clearer view of what pieces of the project 
are where.
Kolla-ansible with its own repo will sit along side kolla-kubernetes as 
consumers of the
kolla repo.

The target for the split will be for day 1 of Occata. The core team will vote on
the change of splitting kolla into kolla-ansible and kolla.

Cores please respond with a +1/-1 to approve or disapprove the repo split. Any 
community
member feel free to weigh in with your opinion.

+1
-Ryan

[1] - https://etherpad.openstack.org/p/kolla-N-midcycle-repo-split

__
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