Paul Bourke wrote:
Hi Joshua,
Thanks for sharing your workflow, interesting to see.
To answer your question, there is a 1:1 relationship between Kolla and
OpenStack releases. As Kevin outlined, you may get lucky, currently in
Oracle we deploy OpenStack Mitaka with Kolla Newton and for the most
Hi Joshua,
Thanks for sharing your workflow, interesting to see.
To answer your question, there is a 1:1 relationship between Kolla and
OpenStack releases. As Kevin outlined, you may get lucky, currently in
Oracle we deploy OpenStack Mitaka with Kolla Newton and for the most
part it works
Fox, Kevin M wrote:
currently one to one on kolla version and openstack release. so 2.0.x is
mitaka. 3.0.x is newton.
I think if we continue forward with the helm idea it will simplify the use case
too. as you can then match up a k8s package (with its templates) for a mitaka
resource with
-dev] [kolla] How tied is kolla to matching 1:1 releases
of openstack?
Fox, Kevin M wrote:
> I think its kind of in the same vein as the rest of the openstack services.
> It might, (and probably will) work with n-1& n services in the same system.
> But it all depends on either:
&g
Fox, Kevin M wrote:
I think its kind of in the same vein as the rest of the openstack services. It
might, (and probably will) work with n-1& n services in the same system. But
it all depends on either:
1. The things that are actually tested
or
2. Luck
I've been testing the kolla-kubernetes
.com]
Sent: Wednesday, November 09, 2016 9:28 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [kolla] How tied is kolla to matching 1:1 releases
of openstack?
Hi kolla folks,
As I am (and others at godaddy) are working through integrating kolla
i
Hi kolla folks,
As I am (and others at godaddy) are working through integrating kolla
image building into our jenkins pipeline(s),
Currently the pipeline is the following (taking an example of glance),
# Checkout stage
1. Checkout kolla at X tag/branch
2. Checkout glance at Y tag/branch
3.
