The hiera function is deprecated and does not work with the latest
hieradata version 5. It should be replaced by the new lookup
function[1].
[1] https://puppet.com/docs/puppet/7/hiera_automatic.html
With the lookup function, we can define value type and merge behavior,
but these are kept default at this moment to limit scope of this change
to just simple replacement. Adding value type might be useful to make
sure the value is in expected type (especially when a boolean value is
expected), but we will revisit that later.
example:
lookup(<NAME>, [<VALUE TYPE>], [<MERGE BEHAVIOR>], [<DEFAULT VALUE>])
This also replaces the hiera_array function which is also deprecated,
according to the guideline[2].
[2] https://puppet.com/docs/puppet/7/hiera_migrate.html#updated_classic_hiera_function_calls
Change-Id: Ic9930107fbc68cba3432f4424f113071325efcb7
Since Puppet 4 all class names are handled as absolute class names
and we don't neet to explicitly use $::{name}.
Change-Id: Icf925c479a9fc05fe71d8315306cb390fd7a57d9
FWaaS is being retired upstream during Victoria release, so we need to
remove it from packstack options.
[1] https://review.opendev.org/#/c/735829/
Change-Id: I9808793db64f9e4ad6d2af818d52378f04d03456
We needed to update the Rake version required by the Gemfile inside
the Packstack Puppet module directory. After that, a rake lint
execution showed many linter errors, so fixing them.
Change-Id: Ib58e62768f5b71e68b79002e01f0d779d1c6138b
Firewall v1 driver was deprecated long ago and
is now removed in [1], let's switch to firewall v2
driver.
[1] https://review.openstack.org/#/c/616410/
Change-Id: Ic995a392075133dd1fba9e417e07149dc1cb4863
In previous releases neutron L3 agent was configured statically
to manage only br-ex as provider network. This way of configuring
neutron is being deprecated in neutron and it has been removed
from puppet-neutron in https://review.openstack.org/#/c/423625/.
This patch changes neutron configuration to a new mode where a
single L3 agent is able to manage multiple provider networks.
To implement it, a new parameter CONFIG_NEUTRON_OVS_EXTERNAL_PHYSNET
has been introduced. Default configuration has been modify to preserve the
existing behavior, creating a public network attached to br-ex bridge.
Change-Id: I71677a5d456ec8748e36f2191f247c96fa578d7d
In the last cycle, some changes have been done in the fwaas project
that requires changes in packstack.
- FIREWALL service_provider is required
- Now l3 agent loads fwaas via extension mechanism.
- A new version fwaasv2 exist whis is not used yet, so version 1 is specified.
Change-Id: I0c826333fb695e0fffc340f2fca806a29e2fde6e
Previously, Packstack created many individual manifest files from
smaller snippets (templates), and executed them following a certain
order. This is sub-optimal, since it forces code duplication and goes
against the Puppet design of running a single manifest.
This patch refactors the manifest execution, following these principles:
- Only 3 templates used, so max 3 Puppet executions on a host: controller
manifest, network node manifest, compute node manifest.
- The previous snippets are now part of the Packstack Puppet module, and
included as needed by the controller/network/compute manifests. This
concept is similar to the one used by the puppet-openstack-integration
project [1].
- The remaining Python code is left untouched, so we can keep complete
compatibility with previous answer files.
- Redis HA support has been removed, as this was the only service with
HA enabled and didn't fit the general purpose of Packstack.
[1] - https://github.com/openstack/puppet-openstack-integration
Change-Id: I87591be0fce98079c85c5c12ad76ea7115fb9c75
Takashi Kajinami
yatin