The standalone baremetal cli was introduced in Ussuri as a direct
replacement for "openstack baremetal" commands, which have since been
removed from openstackclient.
This change updates all "openstack baremetal" calls to "baremetal"
calls without regard for the overall correctness of the documentation,
but at least it is calling a command which actually exists.
Change-Id: I85fa3a5dddc5e0815a9650019504336e7feccf81
This change adds resource class matching and reworks profile matching
to make no mention of image flavors or the deprecated profile
commands.
Change-Id: Ie3f820ad5d5449ae7f67aad70e329d986808c5ad
Due to a limitation in metalsmith it is not possible
to specify both a network and a subnet for vif: true
ports in baremetal_deployment.yaml. See:
https://storyboard.openstack.org/#!/story/2009732
Remove the `subnet` key from the doc example.
Change-Id: Ic8680b3e3f57a9421e003d05f083a139e562d748
In change If53577a26edcb2dc67458603286471dfb87f0bda
network_deployment_actions was replaced with
network_config_update in the baremetal YAML definition.
This change updates the documentation page so that it is
in parity.
Closes-Bug: #1951458
Change-Id: I25d6a5b36a822fc447541f7de06aaf44ebab7865
The --skip-nodes-and-networks option will be removed.
Instead the existing --baremtal-deployment option is used to
provide the capability to enable/disable "all-in-one" network+
node provisioning with overcloud deploy command.
This patch removes --skip-nodes-and-networks from docs.
This partially reverts commit 2bae5e3aaad9b7967a56b07a0aa778c5f582156a.
Depends-On: Idaab1f28c4d645279eff0c01b24435bf8571299b
Change-Id: Ie31f38f4c99534b1d425713509757e792869c329
... because the parameter was removed during Rocky[1].
[1] 187f4f8a24affb9a2c6040c53b22fb965e688f88
Change-Id: I23a6527835615c9682cf6ff73c5673ddd25d7116
When not using the *all-in-one* aproach, i.e manually
provisioning networks, virtual IPs and baremetal nodes
using the individual commands. The ``--skip-nodes-and-networks``
argument should be used with the ``overcloud deploy``
command so that the steps are not redundantly repeated
since the ``overcloud deploy`` command defaults to the
*all-in-one* approach.
Change-Id: I488a1285c9616d016aa4a65fa67b333875100b66
Updated documents to show Queens and Steins as past tense and removed where
possible. Proceedure changes may need to done to the following files:
post_deployment/upgrade/major_upgrade.rst
post_deployment/upgrade/fast_forward_upgrade.rst
post_deployment/upgrade/undercloud.rst
post_deployment/tempest/tempest.rst
features/baremetal_overcloud.rst
features/deployed_server.rst
Wallaby repo section added to the repositories.rst file.
Change-Id: I45ca3ccdb69bad2dfa822558d146e81114eaf7d3
Since scaling down controllers was never supported, it might be a better
to use computes as example to prevent people from scaling down
controllers.
Change-Id: Id1508dbfa46292581bd20e15e79370b584183322
Add documentation for the overcloud node provision
ansible_playbook interface. This interface allow
the user to specify playbooks and extra vars that
will be executed against the deployed nodes prior
to network configuration.
Depends-On: https://review.opendev.org/794017
Change-Id: I7f48a84205b199bffdc0f166403fc25c1eb6e07e
It's adding a \n into the password when set. Using |- will trim the last
\n and prevent it from being added to the actual password.
In the user data we see:
{
"ssh_pwauth": true,
"disable_root": false,
"chpasswd": {
"list": "root:password\\n",
"expire": false
},
...SNIP...
}
So the password ends up being set as "password\n" instead of "password"
Change-Id: I1f28b12d8793db33e2653b739318d36a503633f5
Extend the '_baremetal_provision' book to include
details on how to enable management of network ports
and applying network configuration to provisioned nodes
as part of the node provisioning.
Depends-On: https://review.opendev.org/772977
Change-Id: I6d8f6447565779b5892d1b8c5c057c9a81a56df4
Documentation previously referenced mistral.
Which has been deprecated and removed some time ago.
Added references to the VF docs and information about
how validations should be run.
Relinked the docs.
Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: Iea6d1f818dc3a80ff60621575fe27b7c47d5ea77
Following the Depends-On patch, we don't have to pass the
--disable-validations flag anymore when we deploy the OC on pre-deployed
nodes.
The doc still keep the mention of the option for a specific usecase
since it does make sense, for the sake of making Operator's life easier.
Depends-On: https://review.opendev.org/c/openstack/python-tripleoclient/+/771960
Change-Id: I87be5bf25f4ff3f6bfc2ccb311c5f0c9dea5a9bc
This documents the new config_drive property, which allows setting
custom instance metadata and cloud-config tasks to run on first boot.
Change-Id: I291e09068747ffef5d3e3a47b02fd44bce3b4ef3
Depends-On: https://review.opendev.org/761850
Depends-On: https://review.opendev.org/762580
This may be a side effiect of using direct raw images. I
found I was unable to provision unless I deployoed with
5 GB of RAM so we should warn people.
Change-Id: Ifd44599df29c2b0f792043cf3c9620fcdc5fca5f
Support for predictable IP addressing added to the
default port templates in Rocky. The resource
registry overrides are removed the depends-on.
Change-Id: Ib9410e6f6415d3f91a477414930a236f1dc284c8
Related-Bug: #1866215
Depends-On: https://review.opendev.org/711537
This change replaces the scale-down instructions to use the existing
openstack overcloud node delete command, which now supports baremetal
provisioning.
Change-Id: I4420309cdde9a5647bd1ae512690eb410e2e3047
Depends-On: https://review.opendev.org/#/c/695622/
Blueprint: nova-less-deploy
The deployment guide is currently pointed at triplo-docs but it has been
requested that we actually publish a deployment guide. This change
extracts many of the installation doc pages and moves them into the
deploy-guide source tree. Once the deploy-guide is published, we will
follow up to reference the deployment guide from tripleo-docs.
Change-Id: I0ebd26f014180a92c6cf4ab0929d99b2d860796f
