4 Commits

Author SHA1 Message Date
vass
ef2f2eacb1 Remove install-* roles
The install-* roles has been renamed to ensure-* but have been kept
to give users time to update their repositories.

Tuesday the 26th of may is four weeks after we announced the deprecation
of the install-* roles and the date we should remove them completely.

Depends-On: https://review.opendev.org/719323
Depends-On: https://review.opendev.org/719324
Depends-On: https://review.opendev.org/719325
Depends-On: https://review.opendev.org/719326
Depends-On: https://review.opendev.org/719333
Depends-On: https://review.opendev.org/719334
Depends-On: https://review.opendev.org/719401
Depends-On: https://review.opendev.org/719402
Depends-On: https://review.opendev.org/719404

Change-Id: I1bc87cf9ef544c06e2f1daf3177bba9d577e332e
2020-05-26 09:34:25 +02:00
vass
16fe7bbd3f Rename install-pdk-dependencies to ensure-pdk-dependencies for consistency
The old role will be kept and include ensure-pdk-dependencies for backwards-compatability.

Change-Id: Ia269db36655685fe3f4dc54c60ae4bc09a913f52
2020-04-04 15:41:29 -04:00
Andreas Jaeger
0efea94054 Prepare: Use PDK to build puppet module
The puppet module command is deprecated and
is replaced by using the PDK [1] [2].

The difference between the two commands is only
the output in the pkg directory.

The old puppet module command will create a folder and a tarball with the module.

$ls pkg/
openstack-openstacklib-14.1.0/
openstack-openstacklib-14.1.0.tar.gz

While the PDK will only create the tarball in the
pkg folder. This should be no problem since I can't
find anywhere were we are using the generated folder
in the pkg folder.

This is part 1 in a series of two changes, it contains a role to install
the package dependencies (run in pre.yaml before revoke-sudo is called),
the followup change adds the role to actually build. We need those two
steps to not introduce breakage since the users of build-puppet-module
need to be updated before we can change build-puppet-module.

Change-Id: Ief299751c001542b10fcdf44f1b40a169135877a
Needed-By: https://review.opendev.org/667589
Needed-By: https://review.opendev.org/667595
Co-Authored-By: Tobias Urdin <tobias.urdin@binero.se>
2019-06-30 19:42:06 +00:00
James E. Blair
4b3adfeea6 Organize documentation by subject area
This splits all of the current job and role documentation into
files by subject area so that jobs and roles are easier for users to
find.

This will require that any future new jobs or roles add a line to the
appropriate area of the documentation, since that can no longer be
done automatically.  A linter check is added to ensure that every
job and role continue to be documented.

After this refactor, we can begin to enhance the documentation pages
so that they include narrative documentation and subsections.

Change-Id: Ia6f0e89b57e3cb0d7d1745206384c946506d7ea0
2019-03-25 14:21:04 -07:00