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
|
|
InstanceType and ImageId properties belong to an
AWS::AutoScaling::LaunchConfiguration, for example as used for
NovaCompute0Config in nova-compute-instance.yaml. However this
template doesn't use a LaunchConfig but params instead. AFAICT
we don't need these here (and they cause HEAT template validation
to fail)
Change-Id: If444e4449e3d62cb954de48bc3b55b16dcc8886f
|
|
Mergeable block storage yaml template. Makefile updated to create a
overcloud-with-block-storage template to deploy an additional machine
as a block storage node.
Change-Id: I37c06cde114592507a4583f7ec53ffac123d66e3
|