This file has been used for the containerized undercloud so we can
deploy a simple bridge with os-net-config.
We're moving the environments used for CI into THT, so we can branch
them. This is part of this effort.
Change-Id: I4255120e12123568a388c75956e6e8d32dec66aa
Murano dashboard has a dependency on heat-dashboard which is not yet in
the horizon image. The heat-dashboard was recently packaged in RDO [1]
but hasn't yet made it's way into current-tripleo or current-passed-ci.
We need to add the package into the kolla image once there is a RDO
promotion and re-enable the plugin.
[1] https://github.com/rdo-packages/heat-dashboard-distgit
Change-Id: I7c0ccd915d8429bb348c09ab621163aef275c669
Related-Bug: #1752132
This patch replaces use of ipaddr python module with
ipaddress module. The ipaddr has been superseded by the
ipaddress module.
Also install python-ipaddress instead of python-ipaddr in
deployed-server bootstrap scripts.
Closes-Bug: #1751934
Change-Id: I63ae89869c8994e17b3460f9ae94e5fa922f6237
This reverts commit a1ec856e61532daa49f38683857918fd2cc561aa.
This change didn't actually solve the problem so it's best
not to continue to carry it. The correct fix is for the issue
is https://review.openstack.org/547281.
Change-Id: I4e6c5f8a1189d7a134c99b45505e7d33df5c6d89
Via Ic08468854ce92e81cd84bd6c86a6b672b5a9d49b we fixed the problem of
docker being restarted when puppet triggers a change while pacemaker is
up and running. That approach, while more correct than what existed
previously, is still suboptimal because we are stopping all docker
containers even though we don't have to.
Let's detect if applying the profile::base::docker manifest would
introduce any changes and also detect if the docker rpm is going to be
updated. If one of the two conditions is true we need to stop
containers.
This way rerunning the update workflow on a node should be much less
disruptive. Tested this and correctly observed that the first run did
correctly stopped the docker containers whereas subsequent runs did not
stop containers.
Change-Id: I9176da730b0156d06e2a1ef5f2fcc061e2a6abf6
Related-Bug: #1747851
Zaqar's websocket endpoint is binding to the proxied hostname instead of
the actual IP that the service should be listening on. This is not
correct as that interface is used by HAProxy.
Change-Id: I3e528ef072a8d21984e4d4b05b41de99be5b1d0d
Closes-Bug: #1751779
This patch enables health check execution for mistral api docker container.
Change-Id: I5e2c689c152a21aa12476789d4c64fb71b32d34f
Depends-On: Id10f0d52b1732003533aba6b5c89a5079baba852
This patch enables health check execution for mistral-event-engine
docker container.
Change-Id: I804da516d5fe335a0a050ce3aa3c6a44c2be9f59
Depends-On: I074f7911e8a41d45249dbbf277138bc80ee3a774
When enabling network isolation, openshift-ansible picks the wrong ip
address as the default IP for the services. Set the IP to the ctrlplane
network by default, which works with and without network isolation.
Change-Id: I0deef6c2a71c1f2a34e6efed9586bbaa052b49c9
* wait_backoff wrapper retries the command several time increasing backoff
timeout exponentially. Its log is added to to stderr.
* Under some circumstances (race condition), stack may be created but it's
resources are not. fail_if_empty wrapper fails if no output received.
* Some openstack commands were wrapped as there is a delay between stack and
resource creations. Usually it's not visible on speedy environments. However,
when undercloud is located on small VM or cloud flavour is m1.medium then a
race condition may occur as heat creates stack and its resources
sequentially. This means there may be cases when stack is created but its
resources are not. Wrapping openstack calls with wait_backoff and
fail_if_empty guarantees output with proper exit code
Change-Id: If10f4d58f3689bc7d817c8ac2c31e48501e937ce
fast_forward_upgrade_tasks for keystone covering Ocata and Pike.
- Service status check
- Stop service when updating from Ocata to Pike
- Update keystone package
- Db sync
bp fast-forward-upgrades
Change-Id: I65b0c562c6e2545e99e9511d7b148c2130cc6b25
In change 'Render NIC config templates with jinja2' there was also
change of IP ranges for networks. This change is backwards
incompatible and it's better to revert the ranges instead of making
compatibility workaround.
Change-Id: Ifd9f4abaf8b9ac18c251ab8cfba326f2fa92f796
The roles would get generated with deprecated parameter group, but no
parameter in that group. Heat would then refuse that template.
Change-Id: I526c8177d1a759ae9e48cdb8b94fc2aa7fe3c6fb
Closes-Bug: #1750828
We add a ComputeInstanceHA so that using -e
environments/compute-instanceha.yaml does not require customizing roles
by hand and we can rely on the 'openstack overcloud role generate'
command.
Change-Id: I613b7653c9cb6f8e6f368066c4d881e682d62308
A nit was introduced during the refactor of the repo selection. This
should fix it.
Closes-Bug: #1750643
Change-Id: If8a0feed236d7f4d7eaf679c93461816efd7b628