Add notes on removing novajoin

Added note about permission needed when migrating from novajoin to
tripleo-ipa.  Also added notes indicating that novajoin is no longer
available in Victoria.

Change-Id: I614ab9eb39d3b46fa1f854bae4656c35fd48da48
This commit is contained in:
Ade Lee 2020-09-18 15:21:24 -04:00
parent bf90c44ccd
commit 2f12c90538
2 changed files with 27 additions and 14 deletions

View File

@ -162,7 +162,8 @@ TLS-everywhere with Novajoin
.. warning:: This deployment strategy is only supported up to the Train release. We
recommend using tripleo-ipa to accomplish *TLS-everywhere* in newer
releases. Steps for using tripleo-ipa are documented above.
releases. Steps for using tripleo-ipa are documented above. This deployment
strategy has been removed in Victoria.
Do the following steps before deploying your undercloud.
@ -313,25 +314,23 @@ are described below.
Novajoin Composable Service
~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is the default option but we will update TripleO in the future to use
tripleo-ipa by default. At that point, you may need to add the following
composable service to the ``resource_registry`` in ``tls-parameters.yaml``::
This was the default option until Ussuri. As of Victoria, this option has
been removed, and deployers upgrading to Victoria will be migrated to tripleo-ipa.
resource_registry:
OS::TripleO::Services::IpaClient: /usr/share/openstack-tripleo-heat-templates/deployment/ipa/ipaclient-baremetal-ansible.yaml
For reference, the Novajoin based composable service is located at
/usr/share/openstack-tripleo-heat-templates/deployment/ipa/ipaclient-baremetal-ansible.yaml
tripleo-ipa Composable Service
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you're deploying *TLS-everwhere* with tripleo-ipa, you need to override the
default Novajoin composable service. Add the following composable service to
If you're deploying *TLS-everwhere* with tripleo-ipa prior to Victoria, you need to
override the default Novajoin composable service. Add the following composable service to
the ``resource_registry`` in ``tls-parameters.yaml``::
resource_registry:
OS::TripleO::Services::IpaClient: /usr/share/openstack-tripleo-heat-templates/deployment/ipa/ipaservices-baremetal-ansible.yaml
Remember, this is going to be the default method of deploying *TLS-everywhere*
as of the Victoria release.
As of Victoria, this is the only method for deploying *TLS-everywhere*.
Specify Templates
~~~~~~~~~~~~~~~~~

View File

@ -94,7 +94,7 @@ FreeIPA.::
/etc/pki/pki-tomcat/ca/CS.cfg
systemctl restart ipa
Finally, if your IPA server is not at 4.8.5 or higher, you will need to add an
If your IPA server is not at 4.8.5 or higher, you will need to add an
ACL to allow for the proper generation of certificates with a IP SAN.::
cat << EOF | ldapmodify -x -D "cn=Directory Manager" -w $DIRECTORY_MANAGER_PASSWORD
@ -104,6 +104,13 @@ ACL to allow for the proper generation of certificates with a IP SAN.::
aci: (targetattr = "aaaarecord || arecord || cnamerecord || idnsname || objectclass || ptrrecord")(targetfilter = "(&(objectclass=idnsrecord)(|(aaaarecord=*)(arecord=*)(cnamerecord=*)(ptrrecord=*)(idnsZoneActive=TRUE)))")(version 3.0; acl "Allow hosts to read DNS A/AAA/CNAME/PTR records"; allow (read,search,compare) userdn = "ldap:///fqdn=*,cn=computers,cn=accounts,dc=example,dc=com";)
EOF
If you are upgrading to Victoria and you have been using novajoin, an additional permission
must be added to the Nova Host Manager role to allow the creation of DNS zone entries.
As an admin user::
ipa privilege-add-permission 'Nova Host Management' --permission \
'System: Modify Realm Domains'
Please refer to ``ipa-server-install --help`` for specifics on each argument or
reference the `FreeIPA documentation`_. The directions above are only a guide.
You may need to adjust certain values and configuration options to use FreeIPA,
@ -126,6 +133,14 @@ Novajoin was introduced in the Queens release and is supported through Train.
The `tripleo-ipa`_ project, described below, effectively replaced novajoin in
the Train release.
As of Victoria, novajoin is not longer supported. If you are updating
from Ussuri, tripleo will automatically migrate your deployment from novajoin
to tripleo-ipa. Tripleo will stop and remove the novajoin containers from
the undercloud. If in-flight validations are enabled, tripleo will run a
pre-upgrade validation to verify that the needed ACI and permissions have been
added to the FreeIPA server. See the previous section on "Installing FreeIPA"
for more details.
.. _Novajoin: https://opendev.org/x/novajoin
tripleo-ipa
@ -138,8 +153,7 @@ well as :doc:`deployed_server`. This project was introduced in Train and
effectively replaces the novajoin metadata service.
We recommend using tripleo-ipa for all *TLS-everywhere* deployments as of the
Train release. In a future release, we will update TripleO to only support
tripleo-ipa as the default method for configuring and deploying
*TLS-everywhere*.
Train release. As of Victoria, tripleo-ipa is the only supported method to
configure and deploy *TLS-everywhere*.
.. _tripleo-ipa: https://opendev.org/x/tripleo-ipa