Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Change-Id: Icadcb1b27852d729608195f4890f914c8350ac8c
|
|
|
|
|
|
|
|
Add ReNo support to manage release notes.
http://docs.openstack.org/developer/reno/
Change-Id: Ie5154d909e616e4e7e813052f9c121d6ac5b0875
|
|
|
|
This reverts commit 4e3b085a59e7af49d1025986fd80796be338f5fd.
Change-Id: Id9b3610af7167572b292ba330c3f0aad660fedc4
Related-Bug: #1656276
|
|
|
|
|
|
This is needed to fetch the tripleo repo; since it's not available
because we're using the generic cloud image on CI.
Change-Id: I22ebe028c7b23cb5fba7d03ce89e967bca5951f8
|
|
Change-Id: I9c6116ddb4475b798876635cbb701214759fa33b
Partially-Implements: blueprint overcloud-upgrades-per-service
|
|
|
|
Change-Id: I730abee756598c0a23209a53e52cc83e0b815a50
Partially-Implements: blueprint overcloud-upgrades-per-service
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We needed to set the 'ws' protocol so we would get the correct endpoint
map generated when using build_endpoint_map.py
Change-Id: I6f2cfce058a803f1925c4e22f9791d0117a6c0e3
|
|
the version it was using was 2015-04-30, but we should be using ocata
instead.
Change-Id: I3eca2f235b3623f08e9cd6b7c2eafe0959b2fb3c
|
|
|
|
|
|
|
|
The error path for this fails because we don't import six
or install it in the templates tox venv
Change-Id: Ie9f46332f2b03d48a1b0a4a432e9721757833569
|
|
Relying on home can be tricky if run on CI, since we would need to
hard-code the user. So for this case, we can use /tmp to source that
environment file from.
bp tls-via-certmonger
Change-Id: Ie6234a15af7aa493257c13bd40cbf51ab36085be
|
|
|
|
Deploying ODL without L3 DVR is no longer supported. This patch moves
the opendaylight-l3 env settings to be the new default for opendaylight
env file, while also removing any option to disable L3.
Closes-Bug: 1654586
Change-Id: Ia2488cb0b752fb4b33f03caa7a1d2469d20395f0
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
|
|
This change adds a CephMds service, disabled by default, on the
Controller role and an environment file to enable it.
Change-Id: If7cb46319038a80ed52f753a623989885e1b7da4
Depends-On: Iaecc3ff7acb851776c5057c42a5a513a70425d2c
Partial-Bug: #1644784
|
|
Introduce THT for networking-fujitsu. networking-fujitsu is a neutron ML2 plugin
which enables FUJITSU C-Fabric switch in OpenStack environment. This templates
deploy overcloud with C-Fabric switch.
Change-Id: Iee75a1a30552d8dc9f55f52d10b0dc2b623992ef
Implements: blueprint integration-networking-fujitsu
Depends-On: I37a502b43eb7d91bfe20625248ed117eae3ca535
Depends-On: I5eb2c2a9c50b5991d62f4b6d74b83351c86b02de
|
|
Occasionally we can see transient network outages when attempting
to register with the Redhat Portal or Satellite server. This causes
deployment or scaleout operations to fail. These outages are minimal
and retrying often resolves the issue. This becomes more prevelant
during testing as we deploy infrastructure far more frequently.
Change-Id: If23785fbe2eea4643918b2e68915bbc13c1b1112
|
|
Change-Id: I9ae60dfb2ef5e8fb5aae482ddb08206fc1980ca5
|
|
|
|
|
|
Mistral is tested by scenario003. Let's document it.
Change-Id: If715a2071b7e421b63033fd00f49d3a3f1948af1
|
|
Change-Id: Icd23553e94fd573a8032c52e18857e722eb2ea49
|
|
|
|
|
|
|
|
The current environment files for OpenDaylight use
the opendaylight mechanism driver - changing it to
opendaylight_v2.
Also using the l3_odl_v2 as a service plugin
Depends-On: I2a1c5097614e47cc09e43bbc77305a0548d54baa
Change-Id: Iba6f52663ce4a5e4c070f58f079465fdd24ecc7c
|
|
|
|
There are change of ServiceNetMapDefaults in service_net_map.j2.yaml but
were not reproduce in update-from-keystone-admin-internal-api.yaml
environment. Tested in newton.
Closes-Bug: #1646862
Change-Id: I307dcaabbc6d583896090bf3f046b442007fbc42
Signed-off-by: Cyril Lopez <cylopez@redhat.com>
Co-Authored-By: Gregory Charot <gcharot@redhat.com>
|
|
Some deployments of the undercloud would like to use
net-config-noop (to disable all network configuration).
This patch changes this noop software deployment to use
'apply-config' instead of 'os-apply-config' which allows it
to work with the undercloud installer which only supports the
newer (apply-config) style due to heat signalling requirements.
Change-Id: If7b579b759477afd81ad64a4847169e59ddcbd77
|
|
The commands specified by UpgradeInitCommand need to be run before
InstanceIdDeployment in deployed-server.yaml, otherwise the upgrades
hang with the resource in progress. This is because the new
python-heat-agent-apply-config has not yet been installed on the
deployed server.
Adding the UpgradeInitCommand (and corresponding
SoftwareConfig/SoftwareDeployment to apply it) will cause the new repos
and python-heat-agent-* rpm's to be installed before
InstanceIdDeployment.
An open question is whether or not Heat should even be triggering the
InstanceIdDepoyment to IN_PROGRESS on upgrade when only the group is
changing from os-apply-config to apply-config. If that turns out to be a
Heat bug, then this patch wouldn't be necessary.
Change-Id: I9d87f995744415b110a7d0bca8d2309d7167148c
|
|
Add a new roles data YAML file and environment to help
create the undercloud via t-h-t.
Partially-implements: blueprint heat-undercloud
Change-Id: I36df7fa86c2ff40026d59f02248af529a4a81861
|
|
This patch adds several new heat engine setting that are required
in order to configure a fully working Heat engine in the undercloud.
New parameters have been added for the max resources and convergence
settings. I've hard coded the max stack depth at 6 which matches our
undercloud and should be fine as a default setting I think (would
rarely need overridden).
Change-Id: I335476f46b4bea4b9f3ac70a6312a7e906f43ba6
|