Fabiano Correa Mercer 29a86fe563 Use FQDN for MGMT network
The management network is used extensively for all internal
communication.
Since the original use of the network was a private network before
it was exposed for external communication in a distributed cloud
configuration, it was never designed to be reconfigured.

To support MGMT network reconfiguration the idea is to configure the
applications to use the hostname/FQDN instead of a static MGMT IP
address.

In this way the MGMT network can be changed and the services and
applications will still work since they are using the hostname/FQDN
and the DNS will be responsible to translate to the current MGMT
IP address.

The use of FQDN will be applied for all installation modes: AIO-SX,
AIO-DX, Standard, AIO-PLUS and DC subclouds. But given the
complexities of supporting the multi-host reconfiguration,
the MGMT network reconfiguration will focus on support for AIO-SX
only.

The DNSMASQ service must start as soon as possible to translate
the FQDN to IP address.

Test plan ( Debian only )
 - AIO-SX and AIO-DX virtualbox installation IPv4/IPv6
 - Standard virtualbox installation IPv6
 - DC virtualbox installation IPv4 ( AIO-SX/DX subclouds )
 - AIO-SX and AIO-DX installation IPv4/IPv6
 - AIO-DX plus installation IPv6
 - DC IPv6 and subcloud AIO-SX
 - AIO-DX host-swact
 - DC IPv4 virtualbox with subcloud AIO-DX and AIO-DX
 - AIO-SX to AIO-DX migration
 - netstat -tupl ( no services are using the MGMT IP address )
 - Ran sanity/regression tests
 - Backup and Restore for AIO-SX/AIO-DX

Story: 2010722
Task: 48447
Depends-On: https://review.opendev.org/c/starlingx/config/+/886208
Depends-On: https://review.opendev.org/c/starlingx/integ/+/887534

Change-Id: I3e24f275cf4cbdeb022742853324540e48adaac4
Signed-off-by: Fabiano Correa Mercer <fabiano.correamercer@windriver.com>
2023-10-26 16:00:51 +00:00

57 lines
1.6 KiB
Plaintext

Source: puppet-manifests
Section: admin
Priority: optional
Maintainer: StarlingX Developers <starlingx-discuss@lists.starlingx.io>
Build-Depends: debhelper-compat (= 13)
Standards-Version: 4.4.1
Homepage: https://www.starlingx.io
Package: puppet-manifests
Architecture: any
Depends: ${misc:Depends}, puppet,
puppet-dcorch,
puppet-dcmanager,
puppet-mtce,
puppet-nfv,
puppet-patching,
puppet-sysinv,
puppet-sshd,
puppet-smapi,
puppet-fm,
puppet-dcdbsync,
puppet-usm,
puppet-module-barbican,
puppet-module-ceph,
puppet-module-horizon,
puppet-module-keystone,
puppet-module-openstacklib,
puppet-module-vswitch,
puppet-module-puppetlabs-concat,
puppet-module-puppetlabs-haproxy,
puppet-module-puppetlabs-inifile,
puppet-lvm,
puppet-module-puppetlabs-postgresql,
puppet-module-puppetlabs-rabbitmq,
puppet-module-puppetlabs-stdlib,
puppet-module-duritong-sysctl,
puppet-module-cristifalcas-etcd,
puppet-drbd,
puppet-boolean,
puppet-dnsmasq,
puppet-puppi,
puppet-module-puppetlabs-firewall,
puppet-module-adrienthebo-filemapper,
puppet-module-camptocamp-kmod,
puppet-ldap,
puppet-memcached,
puppet-network,
puppet-module-voxpupuli-collectd,
python3-ruamel.yaml
Description: Puppet configuration and manifests
Puppet lets you centrally manage every important aspect of your system using a
cross-platform specification language that manages all the separate elements
normally aggregated in different files, like users, cron jobs, and hosts,
along with obviously discrete elements like packages, services, and files.
.
Puppet configuration and manifests.