Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I3a84cf52cc46f0c338319a046d77edb2a9b29c45
|
|
|
|
This makes more sense than calling it 'ubuntu'.
Note: This will require an associated incubator change which
I will push momentarily.
Change-Id: I166b45a6ceb34635ed5ef7e29dd028f8c6a4cbe3
|
|
This is used to control the dhcp_options_enabled flag in nova.conf,
needed to enable PXE orchestration (until Nova assumes all Neutron
libraries and servers support it).
Change-Id: I035a2341d829a9987eeeebdd9c22f039e69489db
|
|
This prevents secret values being returned for stack-show.
Change-Id: I82eff26fda31511b66c6371f6ded2a5fb559f3fb
Fixes-Bug: #1226730
|
|
The OpenStack native OS::Nova::Server gives us the full list of
networks rather than AWS::EC2::Instance's contrived view of 'private'
and 'public'. We know we want ctlplane, and use Fn::Select to choose
that network directly. The outer Fn::Select is meant to choose the
first network every time, which may not always be correct, but is at
this point.
Change-Id: Iae54ab8d9ac8d84f4f6e2f86ac1b66aacb687473
|
|
Nova BM can only run one architecture at a time, and the incubator
currently documents running sed against undercloud-vm.yaml!
Change-Id: Ib157cf405a40fa983f1df3fb3ed62d04262e3e81
|
|
Update the PrivateIp attribute to first_private_address as a result of
the change to the OS::Nova::Server type.
Change-Id: Id90f8c7c4e0217e1f94d3e5134744a810390e7b7
|
|
So that it can be a snowflake! (unique).
Change-Id: Ic823620ace7df5636cd9ff16dcd7476654692e6c
|
|
The undercloud doesn't contain swift.
Change-Id: I1372ed28d7ee5bec2b0e03941bd8d50a0b749825
|
|
No longer needed, less globals == win.
Change-Id: I2872e5a8775a09b2e857ef082f3b86109785a126
|
|
Another service converted to match the keystone model of unique
accounts per service.
Change-Id: I62fce289a7032138be3aca8c74df499c2b1fde28
|
|
The in-instance scripts are about to require this.
Change-Id: I0260da5502639acc60b2791e9f957952f7ab5956
|
|
Change-Id: Ifde42d405e22c32f4edc2fdd4f5aed5a0c8bff20
|
|
Change-Id: I34c294c62bf5da4c01d72931173c055c6a13706c
|
|
Change-Id: Iec40d309f3099998fbeb85de7538ed5e0d2e9c42
|
|
The in-instance scripts are being fixed to not confuse the admin
password with the neutron service password.
Change-Id: I341574bb838a9563120791b9ac014d75274a96aa
|
|
We use the admin password in in-instance scripts that configure e.g.
nagios from the cloud metadata, but production clouds will all have
unique passwords - it has to be a parameter.
Change-Id: I1f6c697ce27580fd669c7623e7fcea4c96ec62d0
|
|
Because unique is good for auth secrets.
Change-Id: Iaadc102d11d68d7fc059e62bd992de7ee6f2c818
|
|
Previously we could not feed the IP of an instance into its own
Metadata because of circular dependency problems. 0.0.0.0 was used
with the heat-localip element to work around this problem. This
caused problems though, as heat-localip would edit the source local
heat metadata, which would make cfn-hup and/or os-collect-config think
that the Metadata had changed, causing it to restart everything every
time we query the Metadata, which was about every five minutes.
Now we can just query this inert LaunchConfiguration resource to get
its' Metadata once it is ready. This resource will only change when
legitimate things are changed in the stack, and so we won't restart
everything every five minutes anymore. Note that when the native Heat
DSL lands, the OS::Heat::SoftwareConfig resource is meant for exactly
this purpose.
After this is merged we no longer need the heat-localip element.
Fixes bug #1202322
Change-Id: Id06323ba43203570eeebfa5b3d03fa56c16c0c10
|
|
Os-collect-config is meant to replace cfn-hup from heat-cfntools. It
allows pulling from multiple metadata sources and runs continuously.
Fixes bug #1211289
Change-Id: Ia4e9127fb79048bd1022b32a37272f8463a774ae
|
|
This is supplied to neutron etc via API calls - having it in Heat
leads to having redundancy, confusion and tricky scripts. Incubator
now has scripts to configure this and instances won't consult these
keys.
Change-Id: Ia45d9bf5bb326ec88f9f4a48c5520570cf5b6d72
|
|
Several users with slightly older hardware report the PXE deploy
process aborting deploys that were progressing fine. By increasing the
default PXE deploy timeout we should cater for this. A separate bug
has been filed in Nova/Ironic about the timeout being too simple.
Change-Id: I9e340fc7f928b32b1146ce758cda7180888d6cc9
|
|
Per bug 1201656 (which this doesn't fix) nova-compute can only run one
bm arch from a single compute host.
Change-Id: I0eabe6e85ed388af111ef503882dfdf7959d8d97
|
|
The undercloud (and boot-stack in general) no longer create baremetal
flavors or register baremetal ramdisks, so passing in keys for that
isn't needed.
Change-Id: I8c20e95f3a57418d7ae160a296a092cd71254e3d
|
|
Almost all references to quantum have been changed
neutron in tripleo-image-elements.
Change-Id: Ib17353d5834dd95d0348f62111074180c6e47181
|
|
It is currently broken due to mismatched config keys.
Change-Id: If3ce934730cb974af7bcd7c6b3134e499f4e2a0d
|
|
Change-Id: Ibf59b34341129712c0e3187aa87ac90c092a74a7
|