instack-undercloud is no longer in use by the TripleO project. Removing
the code to avoid confusion. Stable branches will continue to be
maintained for their life however no new features should be added.
Change-Id: I63a813c7c1ffd30ca30017133d31a497b77a9a4d
Blueprint: remove-instack-undercloud
As part of the docs migration work[0] for Pike we need to switch to use the
openstackdocstheme.
[0] https://review.openstack.org/#/c/472275/
Change-Id: I6eca43c3e52a9e7faa5ee9045daf0591d54f9395
This is a manual sync of our requirements from g-r. I believe the
bot is not proposing updates because we had an entry in
requirements.txt that was not in g-r, so the update script was
failing. Once this merges we should get automated updates again.
Change-Id: I7daf819ccc965d10b80929ae80f6606ed3511661
These are required to satisfy the gate-instack-undercloud-docs job.
Content will need to be added over time.
Change-Id: Id3057d7ee17f9e06afde382fea33b08dada3cb39
As part of https://bugzilla.redhat.com/show_bug.cgi?id=1255058
at least initially the user will have to collect the mac address
list and feed into the heat stack create. This just adds an
enhanced example on how to achieve that using the downloaded
node swift data.
Change-Id: I6ccc6c2aac794214d69c7bb33046a74b80455ff1
More specifically:
* fixed typos
* use ASCII chars for quotes and double quotes
* properly capitalize OpenStack
* fixed list formatting
Change-Id: Iaf94a98c3ab4df2da2f972ac3cee07e0f0b6bd60
This doc shows show to deploy an overcloud with Manila installed
and configured. This guides the user through deploying the overcloud,
creating a share and accessing that share from a VM.
Change-Id: Idd35cf5eb06f0f9ae5eaf768ce228e0bb156a75d
As documented @ BZ 1245226 clarify that you must include the custom
environment files to the node delete cli.
Also squashes 2 nits in the quiesce procedure we document and point
to from the node delete docs.
Change-Id: Ie785939cbb999adb0fa87c726d13f94c8ad39bf4
Related-Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1245226
Some docs were added in I099dde62909f576b32039d594a397a59d2b11b4f
(https://review.gerrithub.io/#/c/241459/5) that show how the tuskar
roles and plan can be removed and recreated. At the same time
another commit was merged that has some related content explaining
roles and plans at Ieaf500ea2fda79a196d1d7e88ed30d986248718f
(https://review.gerrithub.io/#/c/239980/).
This change moves the tuskar reload docs into a section of the
general roles and plans docs (and deletes the stand-alone file).
Change-Id: I53dcd6754857b5039947c683d8752f6d45712df1
This change documents properly how to use VLAN mode with OSP-Director.
The VLAN mode configuration was not documented before.
This change also corrects documentation for the External bridge.
The parameter for NeutronExternalNetworkBridge needed to be defined
differently in order to work on both Tuskar and Heat.
Change-Id: I657d47d787618f3ca5b43812f944f78e0fd57241
Adds a section in Advanced Deployment to document how to delete and
recreate the deployment plan and roles from scratch. This includes
a way to specify an alternative tripleo heat templates directory
from which roles are created.
A related bug is at
https://bugzilla.redhat.com/show_bug.cgi?id=1229493
In time we can change the procedure documented here to use the
--all flags to tuskar load/delete roles as tracked in that BZ
and avoid using the tripleo image element scripts directly.
Change-Id: I099dde62909f576b32039d594a397a59d2b11b4f
Previously the docs did not mention usage of network_type flat param
when creating the external network, which resulted in neutron
creating one of vxlan or gre type, depending on tenant network
type.
Change-Id: I9ba27d80b9f943964ed6da6000108ba59687cec5