The TripleO team is putting together tools to reproduce
CI results outside of the upstream CI system. This
tag can be used to organize those issues and bugs.
Change-Id: I572aaa02b35792b32bd0572046a899c51bf3d94a
The "transformation" squad has been added to the squands documentation.
This squad will bring together a group of folks working on the
tripleo-ansible effort, which will initially focus on converting our
heat template and puppet tasks into ansible; the results of this effort
will be put into playbooks and roles housed within the tripleo-ansible[0]
respository.
Per the initial mailing list post[1] this squad will also begin working
with various upstreams and collaborating across project teams within the
OpenStack ecosystem.
[0] - https://opendev.org/openstack/tripleo-ansible
[1] - http://lists.openstack.org/pipermail/openstack-dev/2018-August/133295.html
Change-Id: I07056e774658f2f7952dbf3a6a79ff3929e670ef
Signed-off-by: Kevin Carter <kecarter@redhat.com>
During the Train PTG, we identified that scaling the heat-engine and
ironic-conductor may be beneficial to improving scale. This spec
proposes to create a new undercloud minion node so that an operator
can provide additional systems for heat and ironic usages.
Change-Id: Ic5a5a785b4102383d7369b3a825fe5d615d381c0
Related-Blueprint: undercloud-minion
With all the jobs running tempest now, it's good to have a way to track
down all the tempest issues easily on Launchpad.
Change-Id: I885df34d5768f65776df7d6c722eebbb92718a0e
Oslosphinxs is bosolete and will be EOL after pike, this replace it with
openstackdocstheme with is the official replacement.
Also upgrade sphinx to make it compatible with newer version of yasfb.
Unit test are run with python3 so we can upgrade sphinx to >= 2.0.0
Closes-Bug: #1824074
Change-Id: Ifb28b4e656b60dc1b2dcb6da08b0e717439586ee
This is an alternative pattern which can be used to launch
side containers in a safe manner within our current architecture.
A specific focus here is Neutron which requires its side container
processes to run in network namespaces.
Change-Id: I352b0fbad444f8f340e53da0b758287f55e1c752
Following discussions and meetings, the following change has to be
done in order to get a clean code:
- validations should be presented as roles, not playbooks
- current existing playbooks should be migrated to roles
- in order to keep the mistral compatibility, playbooks will be
created and just include the roles
Change-Id: Ifa36b59c81e6757f1bdb258c477723e883a4f30b
Spec: triple-routed-networks-templates Refactor THT for routed nets.
This spec describes the problem set and work items to implement support
for routed network deployment with TripleO Heat templates. For routed
networks, we will need to support an additional layer of abstraction
for isolated networks, where there are multiple broadcast domains, each
with their own VLANs. Separate VLANs with routers connecting them
allows for horizontal scalability and reduced broadcast, multicast and
unknown unicast traffic within each VLAN.
This is a dependency of blueprint tripleo-routed-networks-deployment
Change-Id: I50dab467fde8a1e62ab0b24ce12d639d72dd692b
Provide a common, unified validation framework inside tripleoclient.
This resubmits Iffaa3c99ac401626c70211437dd98f214b4973e4 previously
merged too fast.
This reverts commit 20fc7a387af043809ec96a6ac1c3bac29f60516b.
Blueprint: validation-framework
Change-Id: Ib99f82227d045c07d1e8b602627c8bcd6a88114c
Utilizing the standalone installer to better test the upgrade
tasks within existing ci wall-time and nodes.
As part of Stein PTG discussion [1] it was decided that the
approach outlined here will be one of two main streams for
upgrades CI in S. This for testing service upgrade_tasks
and another stream for testing the workflow. That latter
workflow stream is not considered here.
[1] https://etherpad.openstack.org/p/ptg_denver_2018_tripleo_ci
Co-Authored-By: Jiri Stransky <jistr@redhat.com>, Athlan-Guyot sofer <sathlang@redhat.com>
Change-Id: Ic8a8867018c6fb866856a45a2bf472a0ed65d99b
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I052f587922176126e25bced35d3108425a70e798
Story: #2002586
Task: #24341
I mistakenly merged this spec and it needs further discussion.
This reverts commit 05b5288b286a52386d4f1fff1665355265167404.
Change-Id: I173bb6242070f280b2b4c88c8c1afe44f14aa62c
It happens that we overlook the upgrade impact of some new
features. Add Upgrade impact section to the spec template to make us
think about how do we upgrade to some feature when proposing that
feature.
Change-Id: I137a4353ce73ae961e83ecd656df77d6bd45a4e4
