Re: [openstack-dev] [kolla] Kolla-ansible is available

[Jeffrey Zhang]

On Thu, Dec 1, 2016 at 4:39 AM, Fox, Kevin M  wrote:

> So, longer term, I'd really like to see a set of smaller pieces of
> gate'ness that co-check each other.
>

​yes this is neccessary.​


>
> one gate that periodically checks that kolla:trunk builds (nightly?) sans
> modification. As the containers themselves depend on a lot of
> packages/repositories outside of kolla's control and therefore can break at
> any time. These would be ran against the kolla-ansible/kolla-kubernetes
> trunk gate checks. showing bugs in the potentially changing containers
> against known good deployment tests.
>

​Agree. periodically checks need check the stable branch too, since they
are not update too much.


> A similar periodic check should be done for kolla-ansible/kolla-kubetes
> gates to ensure things like a new version of kubeadm getting released
> doesn't break things, and cause the other gate checks to produce misleading
> failures.
>

​On master branch, we can depend on zuul's cross project test feature. Now
kolla project run kolla-ansible deployment in its gate for every patch set.
Hope ​we can add kolla-k8s too.


>
> The results of the periodic gates, should be cached somewhere and used as
> input to the kolla-ansible and kolla-kubernetes gates used to check
> incoming reviews. You can then rely more on breakages in
> kolla-ansible/kolla-kubernetes gate checks being actually caused by the
> patches incoming, and not some outside influence.
>

inc0 is trying to set up docker registry in openstack infra. when it is
done, we can speed up the deployment gate in kolla-ansible/kolla-kubernetes.
another workaround inc0 proposed is publishing /var/lib/registry to
tarballs.openstack.org, which can be ​download by kolla-ansible/kolla-k8s.


>
> This should make it much quicker to iterate though issues.
>
> Thanks,
> Kevin
>




-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
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] Kolla-ansible is available

[Fox, Kevin M]

So, longer term, I'd really like to see a set of smaller pieces of gate'ness 
that co-check each other.

one gate that periodically checks that kolla:trunk builds (nightly?) sans 
modification. As the containers themselves depend on a lot of 
packages/repositories outside of kolla's control and therefore can break at any 
time. These would be ran against the kolla-ansible/kolla-kubernetes trunk gate 
checks. showing bugs in the potentially changing containers against known good 
deployment tests.

A similar periodic check should be done for kolla-ansible/kolla-kubetes gates 
to ensure things like a new version of kubeadm getting released doesn't break 
things, and cause the other gate checks to produce misleading failures. 

The results of the periodic gates, should be cached somewhere and used as input 
to the kolla-ansible and kolla-kubernetes gates used to check incoming reviews. 
You can then rely more on breakages in kolla-ansible/kolla-kubernetes gate 
checks being actually caused by the patches incoming, and not some outside 
influence.

This should make it much quicker to iterate though issues.

Thanks,
Kevin

From: Steven Dake (stdake) [std...@cisco.com]
Sent: Tuesday, November 29, 2016 6:48 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] Kolla-ansible is available

It’s not really about easy or hard.

We don’t want to make the gating less optimal then it was pre-repo split.  To 
achieve that objective, cross-repo gating is necessary to validate the images 
in the docker repo are correct wrt the orchestration system they were developed 
against originally (which has moved off into the kolla-ansible repository).

Hope that clears it up.

Regards
-steve

-Original Message-
From: Joshua Harlow <harlo...@fastmail.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Tuesday, November 29, 2016 at 11:28 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [kolla] Kolla-ansible is available

I would expect nothing less, things that are worthwhile doing are
usually not just (always) easy :)

Jeffrey Zhang wrote:
> If we can implement loose coupling, there will be optimal. But
> it is hard to do this.
>
> On Tue, Nov 29, 2016 at 2:50 PM, Joshua Harlow <harlo...@fastmail.com
> <mailto:harlo...@fastmail.com>> wrote:
>
> Jeffrey Zhang wrote:
>
> Because the role and dockerfile are tight couplings.
>
> For example, the container/Dockerfile may need an environment
> variable
> passed by ansible role. without it, the service may not work.
>
>
> Why do they need to be tightly coupled?
>
>
>
> 
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
> --
> Regards,
> Jeffrey Zhang
> Blog: http://xcodest.me <http://xcodest.me/>
>
> __
> 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] Kolla-ansible is available

[Steven Dake (stdake)]

It’s not really about easy or hard.

We don’t want to make the gating less optimal then it was pre-repo split.  To 
achieve that objective, cross-repo gating is necessary to validate the images 
in the docker repo are correct wrt the orchestration system they were developed 
against originally (which has moved off into the kolla-ansible repository).

Hope that clears it up.

Regards
-steve

-Original Message-
From: Joshua Harlow <harlo...@fastmail.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Tuesday, November 29, 2016 at 11:28 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [kolla] Kolla-ansible is available

I would expect nothing less, things that are worthwhile doing are 
usually not just (always) easy :)

Jeffrey Zhang wrote:
> If we can implement loose coupling, there will be optimal. But
> it is hard to do this.
>
> On Tue, Nov 29, 2016 at 2:50 PM, Joshua Harlow <harlo...@fastmail.com
> <mailto:harlo...@fastmail.com>> wrote:
>
> Jeffrey Zhang wrote:
>
> Because the role and dockerfile are tight couplings.
>
> For example, the container/Dockerfile may need an environment
> variable
> passed by ansible role. without it, the service may not work.
>
>
> Why do they need to be tightly coupled?
>
>
>
> 
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
> --
> Regards,
> Jeffrey Zhang
> Blog: http://xcodest.me <http://xcodest.me/>
>
> __
> 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] Kolla-ansible is available

[Joshua Harlow]

I would expect nothing less, things that are worthwhile doing are 
usually not just (always) easy :)


Jeffrey Zhang wrote:

If we can implement loose coupling, there will be optimal. But
it is hard to do this.

On Tue, Nov 29, 2016 at 2:50 PM, Joshua Harlow > wrote:

Jeffrey Zhang wrote:

Because the role and dockerfile are tight couplings.

For example, the container/Dockerfile may need an environment
variable
passed by ansible role. without it, the service may not work.


Why do they need to be tightly coupled?



__
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





--
Regards,
Jeffrey Zhang
Blog: http://xcodest.me 

__
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] Kolla-ansible is available

[Jeffrey Zhang]

If we can implement loose coupling, there will be optimal. But
it is hard to do this.

On Tue, Nov 29, 2016 at 2:50 PM, Joshua Harlow 
wrote:

> Jeffrey Zhang wrote:
>
>> Because the role and dockerfile are tight couplings.
>>
>> For example, the container/Dockerfile may need an environment variable
>> passed by ansible role. without it, the service may not work.
>>
>>
> Why do they need to be tightly coupled?
>
>
>
> __
> 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
>



-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
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] Kolla-ansible is available

[Joshua Harlow]

Jeffrey Zhang wrote:

Because the role and dockerfile are tight couplings.

For example, the container/Dockerfile may need an environment variable
passed by ansible role. without it, the service may not work.



Why do they need to be tightly coupled?


__
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] Kolla-ansible is available

[Jeffrey Zhang]

Because the role and dockerfile are tight couplings.

For example, the container/Dockerfile may need an environment variable
passed by ansible role. without it, the service may not work.



On Tue, Nov 29, 2016 at 1:48 PM, Joshua Harlow 
wrote:

> Jeffrey Zhang wrote:
>
>> ​​
>> ​​
>> does
>> ​
>> anyone
>> ​ ​
>> has
>> an idea to leverage zuul's cross project testing[0] for kolla and
>> kolla-ansibe
>> gate?
>> ​
>>
>>
>> Here is a use case:
>>
>> when implementing A service, we need
>>
>> * add dockerfile in kolla project
>> * add ansible role in kolla-ansible project
>>
>
> Just curious, but why is it required to have the above?
>
> If I want to use just the dockerfiles and docker image building and not
> the ansible roles why should it be required to have both at the same time
> for a new service A?
>
> Why not just allow both the ansible 'code' and the docker files + code to
> be created and maintained independently? Of course if people want to use
> ansible to manage the docker images, more power to them.
>
> -Josh
>
>
> __
> 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
>



-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
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] Kolla-ansible is available

[Joshua Harlow]

Jeffrey Zhang wrote:

​​
​​
does
​
anyone
​ ​
has
an idea to leverage zuul's cross project testing[0] for kolla and
kolla-ansibe
gate?
​


Here is a use case:

when implementing A service, we need

* add dockerfile in kolla project
* add ansible role in kolla-ansible project


Just curious, but why is it required to have the above?

If I want to use just the dockerfiles and docker image building and not 
the ansible roles why should it be required to have both at the same 
time for a new service A?


Why not just allow both the ansible 'code' and the docker files + code 
to be created and maintained independently? Of course if people want to 
use ansible to manage the docker images, more power to them.


-Josh

__
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] Kolla-ansible is available

[Jeffrey Zhang]

​​
​​
does
​
anyone
​ ​
has
an idea to leverage zuul's cross project testing[0] for kolla and
kolla-ansibe
gate?
​


Here is a use case:

when implementing A service, we need

* add dockerfile in kolla project
* add ansible role in kolla-ansible project

there are in the different project. assume that gate can test service A in
kolla and
kolla-ansible
​
*
how could we archive this before the dockerfile part is not merged?
*
and do not merge all these two patches until
the
patch
es
are both green?

I think cross project testing should be helpful. But after reading it more
times,
I am still confused with the second table.

>
> Change Project Zuul Ref. Description
> 1 acme master/Z1 acme master + change 1
> 2 acme master/Z2 acme master + change 1
> 2 plugin stable/Z2 plugin stable + change 2
> 3 acme master/Z3 acme master + change 1
> 3 plugin stable/Z3 plugin stable + change 2
> 3 plugin master/Z3 plugin master + change 3


How above is generated? Will it generate 6 jobs to run? and how kolla can
leverage it?

[0] http://docs.openstack.org/infra/zuul/gating.html#cross-project-testing

On Thu, Nov 17, 2016 at 2:53 AM, Michał Jastrzębski <inc...@gmail.com>
wrote:

> So I can see value of moving configs to kolla itself, but that would
> require significant ansible-fu to get it properly separated, I'd
> suggest separating this discussion from general announcement. If
> someone is willing to make effort of clean separation of configs from
> ansible, let's discuss how to do it technically.
>
> On 16 November 2016 at 12:39, Fox, Kevin M <kevin@pnnl.gov> wrote:
> > I think some kolla-kubernetes folks will still want to use kolla
> genconfig.
> >
> > Not sure it really does need the ansible dependency though. if the dep is
> > removed, it may be better to put it in the kolla repo then the
> kolla-ansible
> > repo.
> >
> > Thanks,
> > Kevin
> > 
> > From: Jeffrey Zhang [zhang.lei@gmail.com]
> > Sent: Tuesday, November 15, 2016 11:55 PM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [kolla] Kolla-ansible is available
> >
> >
> > On Wed, Nov 16, 2016 at 9:10 AM, Fox, Kevin M <kevin@pnnl.gov>
> wrote:
> >>
> >> whats the plan for genconfig? its based on ansible right now, but may
> fit
> >> better as a non ansible specific tool?
> >
> >
> > the core issue is: k8s depends on the ansible configuration file.
> > now Kolla is split. how the kolla-k8s generate the configuration file?
> if it
> > still re-use the ansible configuration file. we do not need any change.
> >
> >
> >
> > --
> > Regards,
> > Jeffrey Zhang
> > Blog: http://xcodest.me
> >
> > 
> __
> > 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
>



-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
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] Kolla-ansible is available

[Fox, Kevin M]

I think some kolla-kubernetes folks will still want to use kolla genconfig.

Not sure it really does need the ansible dependency though. if the dep is 
removed, it may be better to put it in the kolla repo then the kolla-ansible 
repo.

Thanks,
Kevin

From: Jeffrey Zhang [zhang.lei@gmail.com]
Sent: Tuesday, November 15, 2016 11:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] Kolla-ansible is available


On Wed, Nov 16, 2016 at 9:10 AM, Fox, Kevin M 
<kevin@pnnl.gov<mailto:kevin@pnnl.gov>> wrote:
whats the plan for genconfig? its based on ansible right now, but may fit 
better as a non ansible specific tool?

the core issue is: k8s depends on the ansible configuration file.
now Kolla is split. how the kolla-k8s generate the configuration file? if it 
still re-use the ansible configuration file. we do not need any change.



--
Regards,
Jeffrey Zhang
Blog: http://xcodest.me<http://xcodest.me/>
__
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] Kolla-ansible is available

[Jeffrey Zhang]

On Wed, Nov 16, 2016 at 9:10 AM, Fox, Kevin M  wrote:

> whats the plan for genconfig? its based on ansible right now, but may fit
> better as a non ansible specific tool?


the core issue is: k8s depends on the ansible configuration file.
now Kolla is split. how the kolla-k8s generate the configuration file? if
it still re-use the ansible configuration file. we do not need any change.



-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
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] Kolla-ansible is available

[Jeffrey Zhang]

On Wed, Nov 16, 2016 at 1:53 AM, Michał Jastrzębski 
wrote:

> Hello,
>
> I wanted to thank Steve for doing the work, but kolla-ansible is now
> open for business:)
>
> Couple of clarifications how it's going to work:
>
> 1. Currently Kolla-ansible is copy from kolla repo. We will need to
> propose patches to remove docker from it. Also remove ansible bits
> from kolla.
> 2. Any outstanding ansible change should be closed and re-posted to
> kolla-ansible repo.
> 3. Build gates should be dropped from kolla-ansible, deploy gates
> should be removed from kolla
>
​How about do not remove the deploy gates from kolla.
​

​Imaging that, when made some change for certain Dockerfile, ​it is hard
for kolla-ansible and kolla-k8s to notice such change until new patch
trigger deploy gate. this is especially common in stable branch.

4. Core team for kolla-ansible is copy of kolla core team, but teams
> are separate and at some point might diverge from each other.
> 5. Kolla-ansible has it's own launchpad and we should migrate all
> relevant bugs and blueprints out there.
> 6. Kolla-ansibe will use same version number as Kolla (so first tag
> will be 4.0.0b1)
>
> Questions?
>
> Regards,
> Michal
>
> __
> 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
>



-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
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] Kolla-ansible is available

[Fox, Kevin M]

whats the plan for genconfig? its based on ansible right now, but may fit 
better as a non ansible specific tool?

Thanks,
Kevin

From: Michał Jastrzębski [inc...@gmail.com]
Sent: Tuesday, November 15, 2016 9:53 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [kolla] Kolla-ansible is available

Hello,

I wanted to thank Steve for doing the work, but kolla-ansible is now
open for business:)

Couple of clarifications how it's going to work:

1. Currently Kolla-ansible is copy from kolla repo. We will need to
propose patches to remove docker from it. Also remove ansible bits
from kolla.
2. Any outstanding ansible change should be closed and re-posted to
kolla-ansible repo.
3. Build gates should be dropped from kolla-ansible, deploy gates
should be removed from kolla
4. Core team for kolla-ansible is copy of kolla core team, but teams
are separate and at some point might diverge from each other.
5. Kolla-ansible has it's own launchpad and we should migrate all
relevant bugs and blueprints out there.
6. Kolla-ansibe will use same version number as Kolla (so first tag
will be 4.0.0b1)

Questions?

Regards,
Michal

__
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] Kolla-ansible is available

[Michał Jastrzębski]

I think we could use git submodule in kolla-ansible to download kolla.
That would help us deal with gates in kolla-ansible short term.
Thoughts?

On 15 November 2016 at 12:07, Paul Bourke  wrote:
> Seems good so far, thanks Michal / Steve. Cores don't forget to add
> openstack/kolla-ansible to your watched projects in Gerrit :)
>
> I assume we just -2 any Ansible related patches currently open against the
> openstack/kolla project with instructions on how to resubmit.
>
> Also has it been discussed yet if we have a recommended mechanism for
> integration of the two projects, e.g. git submodules, pip or something else?
>
> -Paul
>
>
> On 15/11/16 17:53, Michał Jastrzębski wrote:
>>
>> Hello,
>>
>> I wanted to thank Steve for doing the work, but kolla-ansible is now
>> open for business:)
>>
>> Couple of clarifications how it's going to work:
>>
>> 1. Currently Kolla-ansible is copy from kolla repo. We will need to
>> propose patches to remove docker from it. Also remove ansible bits
>> from kolla.
>> 2. Any outstanding ansible change should be closed and re-posted to
>> kolla-ansible repo.
>> 3. Build gates should be dropped from kolla-ansible, deploy gates
>> should be removed from kolla
>> 4. Core team for kolla-ansible is copy of kolla core team, but teams
>> are separate and at some point might diverge from each other.
>> 5. Kolla-ansible has it's own launchpad and we should migrate all
>> relevant bugs and blueprints out there.
>> 6. Kolla-ansibe will use same version number as Kolla (so first tag
>> will be 4.0.0b1)
>>
>> Questions?
>>
>> Regards,
>> Michal
>>
>> __
>> 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] Kolla-ansible is available

[Paul Bourke]

Seems good so far, thanks Michal / Steve. Cores don't forget to add 
openstack/kolla-ansible to your watched projects in Gerrit :)


I assume we just -2 any Ansible related patches currently open against 
the openstack/kolla project with instructions on how to resubmit.


Also has it been discussed yet if we have a recommended mechanism for 
integration of the two projects, e.g. git submodules, pip or something else?


-Paul

On 15/11/16 17:53, Michał Jastrzębski wrote:

Hello,

I wanted to thank Steve for doing the work, but kolla-ansible is now
open for business:)

Couple of clarifications how it's going to work:

1. Currently Kolla-ansible is copy from kolla repo. We will need to
propose patches to remove docker from it. Also remove ansible bits
from kolla.
2. Any outstanding ansible change should be closed and re-posted to
kolla-ansible repo.
3. Build gates should be dropped from kolla-ansible, deploy gates
should be removed from kolla
4. Core team for kolla-ansible is copy of kolla core team, but teams
are separate and at some point might diverge from each other.
5. Kolla-ansible has it's own launchpad and we should migrate all
relevant bugs and blueprints out there.
6. Kolla-ansibe will use same version number as Kolla (so first tag
will be 4.0.0b1)

Questions?

Regards,
Michal

__
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] Kolla-ansible is available

[Michał Jastrzębski]

Hello,

I wanted to thank Steve for doing the work, but kolla-ansible is now
open for business:)

Couple of clarifications how it's going to work:

1. Currently Kolla-ansible is copy from kolla repo. We will need to
propose patches to remove docker from it. Also remove ansible bits
from kolla.
2. Any outstanding ansible change should be closed and re-posted to
kolla-ansible repo.
3. Build gates should be dropped from kolla-ansible, deploy gates
should be removed from kolla
4. Core team for kolla-ansible is copy of kolla core team, but teams
are separate and at some point might diverge from each other.
5. Kolla-ansible has it's own launchpad and we should migrate all
relevant bugs and blueprints out there.
6. Kolla-ansibe will use same version number as Kolla (so first tag
will be 4.0.0b1)

Questions?

Regards,
Michal

__
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