Open Stack

(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) <stdake at cisco.com> 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" <jpeeler at redhat.com> wrote:
>
>>On Fri, May 13, 2016 at 2:57 AM, Britt Houser (bhouser)
>><bhouser at cisco.com> 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.