Age | Commit message (Collapse) | Author | Files | Lines |
|
This is complete as far as it goes but it isn't enough to make running
a scaled out control plane actually work. Specifically, the constructs
to point at API hosts based on looking up a network address aren't
suirtable for scaled out - we need to be using the virtual IP or DNS
round robin or other such resilient configurations, but that is
largely / entirely orthogonal to making the template be ready for
scaling.
Change-Id: Ib9e6db5e7d5db84e4746afdabea046d2b8702bbb
|
|
Using of Heat wait conditions allows us to reliably reason when a
stack creation is complete (as the completion handle is triggered
when os-refresh-config completes).
Change-Id: I89725143532177a0b4aea23c1c31bc7737da0896
|
|
|
|
merge.py seems to look for OpenStack::ImageBuilder::Elements
But we use Openstack::ImageBuilder::Elements in our templates.
Change-Id: I94ee367cf77c3f2929ee23d2dcdd28622849c89e
|
|
Using notcompute for the undercloud resources is a bit confusing
so lets rename them accordingly. This change shouldn't effect
the devtest scripts or toci because we don't pass a parameter
in for the undercloud.
Change-Id: I33c28a3554fe117c5a0a6e641ea277f7a95f2b35
|
|
This will require some changes to our devtest scripts
and TOCI to ensure we build the overcloud-vm template
before attempting to use it.
Change-Id: I14b5e4a0ccf5f18429bfc33e527bdb4760b8d1a3
|