It was deprecated during the previous cycle[1] because pool-manager was
already removed from Designate.
Ideally we should maintain this until 2024.1 release because of SLURP.
However the implementation has not been functioning for several cycles
so I propose removing it early,
[1] 8f4986cea4
Change-Id: I919883c7ee3dc2364378a2926ed12b378046128b
the validate_legacy function is marked for deprecation in
v9.0.0 from puppetlabs-stdlib.
Note that this change looses validation about pool ids. Alternatively
we can define a new data type to keep the validation, but these defined
types for pool-manager were already deprecated and useless and will be
removed in a near future release so we avoid that redundant step.
Change-Id: I85d7058bf379c6aa0e787b2f806f14aebf0693d3
... because the pool-manager feature was already removed during Train
cycle by [1].
[1] 52ad1c4c13d1fead646435634e4b07bb32c68d28
Change-Id: Ia64a6c489889391feb6706ed9b72dca0c3206f6d
This changes all the puppet 3 validate_* functions
to use the validate_legacy function.
The validate_legacy function has been available since
about three years but require Puppet >= 4.4.0 and since
there is Puppet 4.10.12 as latest we should assume people
are running a fairly new Puppet 4 version.
This is the first step to then remove all validate function
calls and use proper types for parameter as described in spec [1].
[1] https://review.openstack.org/#/c/568929/
Change-Id: If8c450da479eca3167d93a1ef29ac8b1bc4312ca
This adds defined anchor points for external modules to hook into the
software install, config and service dependency chain. This allows
external modules to manage software installation (virtualenv,
containers, etc) and service management (pacemaker) without needing rely
on resources that may change or be renamed.
Change-Id: If9fa188b7dca47e6724a737d66e34c0c85668c36
Takashi Kajinami