This is the frontend for discover_and_enroll_nodes workflow.
Change-Id: I822ec89add3742020262c091e79ff94f92ef92e7
Depends-On: I158f0b8f5251d9d94e7e57b3fe24362316d26599
Implements: blueprint node-discovery-by-range
This command is to be used by an operator to run sosreport on
specific set of servers (or all) and retrieve log bundles that can
be used to debug the status of the cluster or troubleshoot issues.
Depends-On: I47c486d14c46a653c61cfd92d9f484efe0407217
Change-Id: I45699dfa6eb3e83d419c7041dbb72cc5d5e4f0ea
Implements-Blueprint: capture-environment-status-and-logs
With pbr 2.0 and Sphinx 1.5, the setting for treat sphinx warnings as
errors is setting warning-is-error in build_sphinx section. Enable this.
Change-Id: I981b05275e1a75e3c42ea3ef24812cded0cefc0d
An upcoming release of pbr will require explicitly stating which
builders are requested, rather than defaulting to html and man. Head off
any potential impact this may cause by explicitly setting this
configuration now.
Change-Id: I06850630c9e85811a09f8464060728679c093dbf
The update abort is not reliable, and could mess up a TripleO stack
beyond repair. Since this has a potential for data loss, I would
suggest this be removed without a deprecation period.
Change-Id: Ieec4f01e38768eafb3df1f06340bdd3e220d30bd
This command receives the same --config-file argument as "overcloud
container image upload" and invokes kolla-build to build the images
specified in that file.
It is also possible to specify --kolla-config-file multiple times to
control the behaviour of kolla-build.
Change-Id: If06a941eaf8d92c29ed84387c4f040866cf07cfa
Depends-On: I061f626fdb3d71613aa23436bf6c53cf4de62213
If a user deploys via the GUI, then this file wont automatically be
created. We can now create it via a Mistral action - this command
provides CLI users a way to call that action and save the file.
While adding tests a typo was spotted in utils.py, this is also resolved
by this patch and covered by the tests.
Change-Id: I7808cd2c43a95bbb154ec6c6f77896b97551e354
This patch adds a new 'undercloud deploy' option which:
-installs and configures os-collect-config, and hooks using instack
-forks an all-in-one heat-api/engine process using noauth
-spawn our own fake keystone thread for noauth Heat
-creates a Heat stack for the undercloud using t-h-t
-starts os-collect-config to drive the deployment of Heat
metadata
Partially-implements: blueprint heat-undercloud
Depends-On: I50a8cc46b4c3c235d438a711760fba94bf8e9715
Depends-On: I36df7fa86c2ff40026d59f02248af529a4a81861
Co-Authored-By: Ian Main <imain@redhat.com>
Co-Authored-by: Flavio Percoco <flaper87@gmail.com>
Change-Id: Ib05062e3710aeec922988d5f1308be44b5468473
We can now generate parameters to enable HA fencing, by re-consuming the
instackenv.json file and introspecting the deployed stack.
Closes-Bug: #1649695
Depends-On: I0ff173b6daf770329b25f61b76fcba0e28b2550a
Change-Id: I8b717b069f95cac20fe2d8c7fdaaacc46214957b
This moves the package update to using a mistral workflow.
Change-Id: I5176746ca4843202a385206289be66f7e6450f48
Depends-On: I8a1f2dbffa19c2d8c93684562d2fb16aef6667db
Closes-Bug: #1614928
This change introduces a new command to build RAID:
$ openstack overcloud raid create --node UUID1 [--node UUID2] configuraiton
More variants of this command will come later.
Part of blueprint raid-workflow
Change-Id: Ic4a547939213e5305cb7ca4f4458ef9eb577437b
This change adds an overcloud delete that will delete the stack and
issue a plan delete for the overcloud in a single command.
Change-Id: I97a2b5606f47deb929972c06c869cd1eda0dc9a6
Closes-Bug: #1632271
It has been in conflict with "baremetal show" command provided by Ironic
since Mitaka, and due to that has been completely broken. The only
reason we haven't noticed that is because nobody uses this command.
Let's just remove it.
Change-Id: I645536f0ae0af3bd318db26543a662de659a27a5
This command will start an overcloud deploy of the plan with
Mistral and wait for it to finish.
Closes-Bug: #1616015
Change-Id: Ie990bfb29dd245a1c83891495aa3f4ec7a0051e8
This uses the new Mistral actions and workflows to create a
plan with the tripleo heat templates. Templates can either
be provided by the user or the default templates on the
undercloud can be used.
Closes-Bug: #1616014
Change-Id: I4f82fda01215b9a45669862ef26c69421fdaad59
Calls to the Mistral workflows to configure boot options and the root
device.
Change-Id: Ifd868fcdd6ed2d54b40c2e1861558d0233731be5
Depends-On: I5ba0a3710012c44822dd3b8e69662bbef04d3787
Closes-Bug: #1595205
The new commands aim to simplify the node management workflow
[1]. Additional configuration will be possible via 'openstack overcloud
node configure.'
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-May/095456.html
Change-Id: I704438da31a31a90f882ddd01ba02e3ca62549ac
Depends-On: Iea9b7f3b49f99f810ce759f65b45b88c1c40f010
Partial-Bug: #1595205
Add a new overcloud_execute module that can be used to run
ad-hoc scripts via the CLI. This implementation uses Mistral
to start a workflow which is then monitored via a Zaqar websocket
for status updates and completion.
Depends-On: I418e8d26db953bc032a7da66f725dcecf7f6f66a
Change-Id: Ia8f9ed38dd5000da02c6cc9572fc87b8e9434a4b
Partially-implements: blueprint remote-execution
Adds a command to upgrade a stack. Takes similar parameters to
'deploy' command. The StackUpgradeManager from tripleo-common is
called to perform the actual upgrade. The command is
'openstack overcloud upgrade'.
Change-Id: Ifda39765704e7d98d1fb70882a4d31ee0c9de21d
Depends-On: Ib7fc5d544755d9b1ffbf46170602ec390e735c11
The undercloud upgrade process entails updating the installed packages,
then running the installer again. However, after updating packages, a
number of services may no longer be able to run, as upon restart the
new code is not compatible with older settings. Therefore, this makes
the upgrade more 'atomic' by bundling the package update and the
undercloud install into a single command. An error (non-zero RC) in the
package update will halt the process.
Change-Id: I269ba919f1648f0e4b30ab710c386dafdad2a68d
This change will allow users (or ironic-inspector) to provide
several possible profiles for a node by setting capabilities like
XXX_profile (where XXX = compute, controller...).
Two new commands are added:
openstack overcloud profiles match
When no enough nodes with a given profile are found, this command
will inspect nodes with such capabilities and choose missing nodes
from them.
openstack overcloud profiles list
Lists all available and active nodes with their profiles and possible
profiles.
See the following thread for the full background:
http://lists.openstack.org/pipermail/openstack-dev/2015-November/078884.html
This changes refactores profile validation code in the deploy command to use
the same logic as commands above. It's worth noting that this change also
removes an incorrect assumption that a node can have multiple values
for the same capability. It also makes sure we only take active and available
nodes into account for all calculations.
Change-Id: I398cf2052b280eaf67e5755412c35fe9551c341f
"Python 3.3 support is being dropped since OpenStack Liberty."
written in following URL.
https://wiki.openstack.org/wiki/Python3
And already the infra team and the oslo team are dropping py33
support from their projects.
Since we rely on oslo for a lot of our work, and depend on infra
for our CI, we should drop py33 support too.
Change-Id: I5db42f479849ed7be05ae0a2aa70af04844ef159
Closes-Bug: #1526170
* changes:
Add a show capabilities command to view the capabilities of nodes
Add passenv to the venv to allow passing of environment variables from stackrc
There are more general ways to scale stacks and thus this isn't needed. After
removing this approach there are still two other methods:
1. Scale a Tuskar plan and then deploy it
openstack management plan set $PLAN_UUID -S Compute-1=2
openstack overcloud deploy --plan-uuid $PLAN_UUID
2. Scale during a deploy
openstack overcloud deploy --plan-uuid $PLAN_UUID --compute-scale 2
The first only works with Tuskar, but the second will also work when
deploying the tripleo-heat-templates.
See: https://bugzilla.redhat.com/show_bug.cgi?id=1233201
Change-Id: I924f6b16102783c0a1a81f5244493ffa1703e458
Dmitry Tantsur