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
In I2ffdd9f615ae6b00428c17249e4f216774991b99 we reworked the logic in
pip-and-virtualenv element to add epel as a dependency. We need to now
exclude epel since is it a dependency.
Change-Id: I43562f960cc100d4ec19b8a5e72c5929e24619ba
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We should use puppet-ironic ironic::pxe class instead
of setting up PXE in ipxe element.
Depends-on: I8b83eff694316755e4dd2dbcde7b569472893bc5
Change-Id: I6c012f7d473c7c2433a6b03d9f8e06a76200458c
Further reduces reliance on elements and moves more logic to puppet.
With this patch, the list of elements being used in the undercloud is
quite small and much easier to reason about logically.
This patch depends on a packaging update for instack-undercloud:
https://review.rdoproject.org/r/#/c/1074/
blueprint undercloud-elements
Change-Id: If6036e9eb68e0af1e1989918d310c8ddf57b9622
Consolidate undercloud-post-config and undercloud-stack-config into
undercloud-install element. All 3 of these elements have to be used
together anyway, so it makes sense to consolidate them all into one as
they're getting smaller. The consolidation will also make easier to
reason about what is remaining in the elements.
blueprint undercloud-elements
Change-Id: I50059a8a58b3082e929d0252d48c4144250c5784
Manage the installation of os-net-config and openvswitch and the
execution of os-net-config via puppet instead of the bash element.
We do still generate the os-net-config configuration via os-apply-config
so, a template is added for that to the undercloud-install element.
As part of this switch, we lose some of the logic from
20-os-net-config[1], namely the configure_safe_defaults fallback
function for when os-net-config failes. However, in almost all cases
(possibly 100%), we never want this fallback on the undercloud anyway
because it will reconfigure the management interface to the undercloud,
which presumably is the interface that is already in use for out of band
management.
This change also requires a 2 step puppet apply, with the first step
running os-net-config.
[1] https://github.com/openstack/tripleo-image-elements/blob/master/elements/os-net-config/os-refresh-config/configure.d/20-os-net-config
blueprint undercloud-elements
Change-Id: Ic19b45e138206ca88ccee5cf261a85c1bfab5e08
This removes usage of the ironic-conductor element in favor of using
puppet instead.
However, puppet-ironic does not yet have full support for configuring
ipxe and tftp, so we still need to make use of 88-setup-ipxe and
69-ironic-tftp-support. Since those bash scripts need to run after
puppet has installed all the needed packages, they are moved to be
os-refresh-config scripts instead. This should be fine since those
scripts are idempotent.
blueprint undercloud-elements
Change-Id: I1a8c97e56309940e0a4394b7ed8c20e8e0c3c9a9
Use the tripleo::selinux module to configure SELinux on the undercloud via
Puppet instead of the bash element.
For CentOS, SELinux is still permissive by defualt.
For RHEL, SELinux is still enforcing by defualt.
An additional hiera (CentOS.yaml/RedHat.yaml) file is added to the hierarchy to
capture this difference.
blueprint undercloud-elements
Change-Id: I0ee6648605fa10a2322edb8ec08514e5e0db1d02
Depends-On: If214005df733d41c2fa4e197df247d8a14baaa14
Moves the os-cloud-config installation to be handled by puppet instead
of the element. Also removes usage of the common-venv element since it
was only ever needed when installing other elements from source.
blueprint undercloud-elements
Change-Id: I9488cebbb479c269901e9b310a1208b6d5ed9e76
Replaces uses of add-rule with using the puppet-tripleo firewall class.
This removes additional dependencies on scripts provided by the elements
(add-rule). There is still one usage of iptables directly in
10-iptables that will be cleaned up in a subsequent patch.
With this change, we can remove the iptables element from the json
files.
blueprint undercloud-elements
Change-Id: I5d496efe22c1a5e17a2b688ba6dfbcfd403349db
Depends-On: I0598007f90018f80a3266193bb24dbf112de49b7
There is already an element from tripleo-image-elements,
enable-packages-install, to switch the default install type to package
instead of source. This patch updates instack-undercloud to use
enable-packages-install and removes the duplicate
undercloud-package-install.
blueprint undercloud-elements
Change-Id: Iadc7940e56be19700977b0cdbd86aa010c105fb6
Depends-On: I8f47b495218a72f5a78d68b7c2610116a5b4984c
Depends-On: I8185aa56ea5225870bab50576023588af37ebedd
This removes the ironic-inspector element from the
undercloud install, and instead uses the puppet module
to setup the ironic-inspector service.
Depends-On: I9b2917a2c3f6afe75dc295c81d09f7a12856007f
Change-Id: Ic3eca27515721000ed1c9d19a2427276e6b1af68
There is currently no liberty tuskar package, so installs using
the latest liberty packages are failing when trying to do
tuskar dbsync. This patch resolves the issue by not installing
tuskar in the undercloud.
An alternative would be to fix the liberty packaging to build
in delorean(https://review.gerrithub.io/#/c/249035), but it
seems like we would not want to do this if we are not going
to support tuskar in liberty.
Change-Id: I06e7d399bc1dab167aae67ad335c758cd8dd5ec6
The name of the the ironic discoverd project has
changed during the Liberty cycle. This change addresses
that name change as well as the config file re-structuring.
It also removes the outdated rdomanager-oscplugin element.
Partial-Bug: 1497004
Change-Id: I319f818deeeafc36968b73b8d249c5bbcaa0d2ea
os-collect-config is not needed on the undercloud. In fact, after a
reboot it starts triggering os-refresh-config, which can cause delays in
system startup with bouncing services.
Change-Id: Ie58e33dd0308523d9e9b06a8e9917d8a42395afe
openstack-clients is actually only being pulled in b/c of the ironic element
which we are already excluding, so we can exclude this one as well.
Change-Id: I85bad0c715f8a9d5d954bab1110b2afe92c12c0a
Now that Puppet is driving a large portion of the Undercloud installation, we
can clean up some previously used elements from the json-files.
We do have to provide some additional bits via the undercloud-install element,
such as simple dib-init-system script. This is much simpler than continuing to
use large elements from tripleo-image-elements that have other unintended
side-effects that we want to avoid.
Change-Id: I0c3626e3b4a2de3d7f1e1bc3274be4150b552a26
Migrate as much as we're initially able to over to be installed via Puppet
instead of elements from tripleo-image-elements. This change is rather large,
but it's all more or less inter-dependent so I wasn't able to break it up any
finer.
The bulk of the change is a new element, puppet-stack-config. That element
installs a puppet manifest at /etc/puppet/manifests/puppet-stack-config.pp that
is applied via puppet during the os-refresh-config phase of the installation.
When the manifest is applied, it uses a hiera data file from
/etc/puppet/hieradata/puppet-stack-config.yaml as input. That file is generated
from a template.
The Puppet modules require a handful of additional inputs for password and
secret items. These inputs are added to the instack.answers.sample file and
instack-install-undercloud.
We're able to remove many items from the static json we're writing out to
/var/lib/heat-cfntools/cfn-init-data, but we still need this for some
configuration as not everything is driven via a Puppet module (os-net-config)
for instance.
Also kemoves some particular hooks scripts that are no longer needed in
instack-undercloud.
This fix-undercloud-package-installs element is no longer needed. It's
addressing bugs that have already been fixed.
Change-Id: I9b93569f193c58d3e98063a1a90c3946a3a886db
Source installs are no longer supported via instack-undercloud. The
default behavior going forward if you want latest code is to use
Delorean. If you want to install something from source instead of a
package, would be to install via Delorean, and then setup the component
you want to run from source manually, stopping any package supplied
services, etc.
This Fedora 20 json file has also bit rotted and no one should be using
it. When we do Fedora again, it would be for Fedora 21. Let's remove this file
to avoid confusion.
Change-Id: I563f01d5b59d2a20493700ead5d1312558633e42
Add support for running instack-install-undercloud on CentOS 7. The
selinux element from tripleo-image-elements fails when applying the
additional rabbitmq policy (depedencies are not met), so we add that
element to exclude_elements, and also inslucde selinux-permissive and
selinux-setenforce-0.
instack-setup-host-rhel7 is symlinked to an updated instack-setup-host and
supports both RHEL 7 and CentOS 7. We may like to consider removing the
rhos-release logic out of that script entirely and just document that
bit since rhos-release is solely for internal consumption.
Change-Id: I89a43f68632d8526b049be2b666c2426a5ccf603
Changes instack-setup-host-rhel7 to setup the needed repositories to use with a
midstream Delorean instance. Also adds a git clone of the needed
tripleo-puppet-elements repository. Although this repository is not initially
needed, the work to install the Undercloud via Puppet and deploy the Overcloud
via Puppet will rely on it, so go ahead and add it. Note that
tripleo-puppet-elements is not yet packaged, which is why need to git clone.
- deletes the previous no longer relevant instack-setup-delorean script.
- Update rhel7rc to set $ELEMENTS_PATH to include tripleo-puppet-elements.
- Also updates $DIB_YUM_REPO_CONF and the cloud image to use RHEL 7.1.
- Remove os-cloud-config element
This element is no longer needed as there one is available in
tripleo-image-elements.
- Updates json file for RHEL 7
- tuskar-ui is removed b/c of it's required role specificity
- we must run the finalise hook b/c use-ephemeral now has a required
hook script that runs in finalise
- exclude pip-and-virtualenv
- The finalise hook for use-ephemeral is not very well idempotent so, also
add some additional steps to 00-cleanup before so we can rerun
installations.
- Set additional install types to package
Change-Id: Ia0e365b15b4b4620c5a392c2a5e3e13d1683b5ef
undercloud install, we can just blacklist the element in the json file. For
image builds, we need to instead use an override element that doesn't install
anything.
By removing rdo-release-icehouse from the undercloud source JSON
we can customize which version of RDO to use exporting RDO_RELEASE.
The cleanup script is also updated to remove any version of the
rdo-release package found.
Alex Schultz