Re: [openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

[Michal Rostecki]

OK, looks like we have consensus on implementing that in the main kolla 
repo.


Thanks,
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

Re: [openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

[Jeff Peeler]

(continuing to top post)

I wasn't arguing otherwise for the record. My comment was merely to
remind that coupling between the two repos should be kept at a
minimum. But I'm fully in favor of any coupling that eliminates code
duplication.

On Fri, May 13, 2016 at 2:51 PM, Steven Dake (stdake)  wrote:
> Jeff,
>
> I'd like to see Kolla defaults for k8s come from one place rather then
> two, so I suggested to Dims in a previous review to depend on the kolla
> repo for those files rather then copy them and maintain them in two places.
>
> Therefore, I don¹t see a viable path forward without the Kolla package
> installed that doesn't create a maintenance nightmare for the core
> reviewers.
>
> Regards
> -steve
>
> On 5/13/16, 11:10 AM, "Jeff Peeler"  wrote:
>
>>On Fri, May 13, 2016 at 2:57 AM, Britt Houser (bhouser)
>> wrote:
>>> Would we ever run AIO-k8s vagrant w/o Kolla repo?  If not, then it
>>>makes sense to me just to extend Vagrant kolla repo.
>>>
>>> Thx,
>>> britt
>>
>>As Kolla developers we may not, but somebody else may want to. Either
>>way, having the Vagrant configuration in the place with the least
>>amount of burden makes sense.

__
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] Vagrant environment for kolla-kubernetes

[Steven Dake (stdake)]

Jeff,

I'd like to see Kolla defaults for k8s come from one place rather then
two, so I suggested to Dims in a previous review to depend on the kolla
repo for those files rather then copy them and maintain them in two places.

Therefore, I don¹t see a viable path forward without the Kolla package
installed that doesn't create a maintenance nightmare for the core
reviewers.

Regards
-steve

On 5/13/16, 11:10 AM, "Jeff Peeler"  wrote:

>On Fri, May 13, 2016 at 2:57 AM, Britt Houser (bhouser)
> wrote:
>> Would we ever run AIO-k8s vagrant w/o Kolla repo?  If not, then it
>>makes sense to me just to extend Vagrant kolla repo.
>>
>> Thx,
>> britt
>
>As Kolla developers we may not, but somebody else may want to. Either
>way, having the Vagrant configuration in the place with the least
>amount of burden makes sense.
>
>__
>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] Vagrant environment for kolla-kubernetes

[Jeff Peeler]

On Fri, May 13, 2016 at 2:57 AM, Britt Houser (bhouser)
 wrote:
> Would we ever run AIO-k8s vagrant w/o Kolla repo?  If not, then it makes 
> sense to me just to extend Vagrant kolla repo.
>
> Thx,
> britt

As Kolla developers we may not, but somebody else may want to. Either
way, having the Vagrant configuration in the place with the least
amount of burden makes sense.

__
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] Vagrant environment for kolla-kubernetes

[Eric LEMOINE]

On Fri, May 13, 2016 at 10:36 AM, Martin André  wrote:
> On Fri, May 13, 2016 at 8:57 AM, Britt Houser (bhouser)
>  wrote:
>> Would we ever run AIO-k8s vagrant w/o Kolla repo?  If not, then it makes 
>> sense to me just to extend Vagrant kolla repo.
>
> Agreed. Vagrant is for developers and developers will want the kolla
> repo for building the container images.
> Having a config options to setup the Vagrant environment for the
> different deployment methods seems appropriate here.

Agree. Duplicating the Vagrantfile would cause maintenance issues.

__
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] Vagrant environment for kolla-kubernetes

[Martin André]

On Fri, May 13, 2016 at 8:57 AM, Britt Houser (bhouser)
 wrote:
> Would we ever run AIO-k8s vagrant w/o Kolla repo?  If not, then it makes 
> sense to me just to extend Vagrant kolla repo.

Agreed. Vagrant is for developers and developers will want the kolla
repo for building the container images.
Having a config options to setup the Vagrant environment for the
different deployment methods seems appropriate here.

Martin

> Thx,
> britt
>
>
>
>
> On 5/13/16, 2:37 AM, "Michal Rostecki"  wrote:
>
>>Hi,
>>
>>Currently we have nice guide about setting up AIO k8s environment in
>>review. But at the same time I'm thinking also about automating this by
>>Vagrant, like we did in kolla-mesos.
>>
>>Here comes the question - what repo is good for keeping the Vagrant
>>stuff for kolla-k8s? I see two options.
>>
>>1) Create a Vagrantfile in kolla-k8s repo
>>
>>That's what we've done in kolla-mesos. And that was a huge problem, because:
>>- we had to copy dhcp-leases script for vagrant-libvirt
>>- we almost copied all the logic of overriding the resources via
>>Vagrantfile.custom
>>
>>While we can do something with the first con - by trying to drop the
>>dhcp-leases script and use eth0 for keepalived/haproxy and endpoints,
>>getting rif of the second con may be hard.
>>
>>2) Extend Vagrantfile in kolla repo
>>
>>That would be easy - it requires just adding some boolean to the
>>Vagrantfile and additional provisioning script.
>>
>>But it sounds odd, to have separate repo for kolla-k8s and at the same
>>time centralize only some compoments in the one repo.
>>
>>What are your thoughts?
>>
>>Cheers,
>>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] Vagrant environment for kolla-kubernetes

[Britt Houser (bhouser)]

Would we ever run AIO-k8s vagrant w/o Kolla repo?  If not, then it makes sense 
to me just to extend Vagrant kolla repo.

Thx,
britt




On 5/13/16, 2:37 AM, "Michal Rostecki"  wrote:

>Hi,
>
>Currently we have nice guide about setting up AIO k8s environment in 
>review. But at the same time I'm thinking also about automating this by 
>Vagrant, like we did in kolla-mesos.
>
>Here comes the question - what repo is good for keeping the Vagrant 
>stuff for kolla-k8s? I see two options.
>
>1) Create a Vagrantfile in kolla-k8s repo
>
>That's what we've done in kolla-mesos. And that was a huge problem, because:
>- we had to copy dhcp-leases script for vagrant-libvirt
>- we almost copied all the logic of overriding the resources via 
>Vagrantfile.custom
>
>While we can do something with the first con - by trying to drop the 
>dhcp-leases script and use eth0 for keepalived/haproxy and endpoints, 
>getting rif of the second con may be hard.
>
>2) Extend Vagrantfile in kolla repo
>
>That would be easy - it requires just adding some boolean to the 
>Vagrantfile and additional provisioning script.
>
>But it sounds odd, to have separate repo for kolla-k8s and at the same 
>time centralize only some compoments in the one repo.
>
>What are your thoughts?
>
>Cheers,
>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] Vagrant environment for kolla-kubernetes

[Michal Rostecki]

Hi,

Currently we have nice guide about setting up AIO k8s environment in 
review. But at the same time I'm thinking also about automating this by 
Vagrant, like we did in kolla-mesos.


Here comes the question - what repo is good for keeping the Vagrant 
stuff for kolla-k8s? I see two options.


1) Create a Vagrantfile in kolla-k8s repo

That's what we've done in kolla-mesos. And that was a huge problem, because:
- we had to copy dhcp-leases script for vagrant-libvirt
- we almost copied all the logic of overriding the resources via 
Vagrantfile.custom


While we can do something with the first con - by trying to drop the 
dhcp-leases script and use eth0 for keepalived/haproxy and endpoints, 
getting rif of the second con may be hard.


2) Extend Vagrantfile in kolla repo

That would be easy - it requires just adding some boolean to the 
Vagrantfile and additional provisioning script.


But it sounds odd, to have separate repo for kolla-k8s and at the same 
time centralize only some compoments in the one repo.


What are your thoughts?

Cheers,
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