tripleo-heat-templates/sample-env-generator/dcn.yaml
Harald Jensås 23cdf4dd17 Refactor Service VIPs redis and ovn_dbs
With this change a Heat resource is no longer used to
create an undercloud neutron API port resource for the
redis and ovn_dbs service virtual IPs. Instead an
external deploy task at step 0 in the individual service
template uses the "tripleo_service_vip" ansible module
to mange a neutron API port resource for each service.

The interfaces to control the IP address and service
network (RedisVirtualFixedIPs, OVNDBsVirtualFixedIPs
and ServiceNetMap) remains the same.

It is also possible to include the 'use_neutron' boolean
in the FixedIPs parameter to instruct the ansible module
not to create a neutron API resource, and simply "echo"
the ip_address given in the FixedIPs parameter. For
example:
  RedisVirtualFixedIPs:
    - ip_address: 1.0.0.5
      use_neutron: false

Alternatively the fixed-ips can be set using the
'ServiceVips' parameter, like this:

 ServiceVips:
   redis: 1.0.0.5
   ovs_dbs: 1.0.0.6

NOTE: If the neutron service is not available the
      tripleo_service_vip ansible module will "echo"
      the IP provided in %service%VirtualFixedIPs.

Related: blueprint network-data-v2-ports
Depends-On: https://review.opendev.org/777307
Depends-On: https://review.opendev.org/779883
Change-Id: I4794418546363888e7a555a16b45b7a4417f1ef8
2021-04-14 10:22:59 +02:00

58 lines
2.4 KiB
YAML

environments:
- name: dcn
title: Distributed Compute Node
description: |-
Environment file for deploying a remote site of distributed compute nodes
(DCN) in a separate stack (multi-stack) deployment.
files: &dcn_files
deployment/nova/nova-az-config.yaml:
parameters:
- NovaComputeAvailabilityZone
network/external.yaml:
parameters:
- ManageNetworks
deployment/nova/nova-base-puppet.yaml:
parameters:
- NovaCrossAZAttach
deployment/nova/nova-compute-container-puppet.yaml:
parameters:
- NovaDisableImageDownloadToRbd
sample_values: &sample_values
ManageNetworks: false
NovaCrossAZAttach: false
NovaDisableImageDownloadToRbd: true
resource_registry: &dcn_resource_registry
OS::TripleO::Services::GlanceApiEdge: ../deployment/glance/glance-api-edge-container-puppet.yaml
OS::TripleO::Services::HAproxyEdge: ../deployment/haproxy/haproxy-edge-container-puppet.yaml
OS::TripleO::Services::NovaAZConfig: ../deployment/nova/nova-az-config.yaml
children:
- name: dcn-storage
title: Distributed Compute Node with storage
description: |-
Environment file for deploying a remote site of distributed compute
nodes (DCN) in a separate stack (multi-stack) deployment with storage;
either HCI or with separate storage nodes. It should be used in
combination with environments/ceph-ansible/ceph-ansible.yaml.
files:
<<: *dcn_files
deployment/cinder/cinder-base.yaml:
parameters:
- CinderStorageAvailabilityZone
deployment/cinder/cinder-volume-container-puppet.yaml:
parameters:
- CinderVolumeCluster
- CinderEtcdLocalConnect
deployment/glance/glance-api-container-puppet.yaml:
parameters:
- GlanceEnabledImportMethods
sample_values:
<<: *sample_values
CinderStorageAvailabilityZone: dcn
CinderVolumeCluster: dcn
CinderEtcdLocalConnect: True
GlanceEnabledImportMethods: web-download,copy-image
resource_registry:
<<: *dcn_resource_registry
OS::TripleO::Services::Etcd: ../deployment/etcd/etcd-container-puppet.yaml
OS::TripleO::Services::CinderVolumeEdge: ../deployment/cinder/cinder-volume-container-puppet.yaml