[openstack-dev] [kolla] repo split
Britt Houser (bhouser)
bhouser at cisco.com
Wed Jul 20 23:41:30 UTC 2016
-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" <inc007 at gmail.com> 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 <rhallise at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
More information about the OpenStack-dev
mailing list