New and Changed Features

Product Components

• Contrail Networking Release 21.4.L2
  • Contrail Networking R21.4.L2 Release Notes.
• Contrail Insights Release 3.3.10 (formerly AppFormix)
  • Contrail Insights Release Notes are available as part of the software download package.
• Red Hat OpenStack 16.2.5 – OpenStack Train (Red Hat CDN sync 10-May-2023)
  • RHOSP 16.2.5 Release Notes.
• RHEL 8.4–Linux kernel 4.18.0-305.88.1.el8_4.x86_64 (Red Hat CDN sync 10-May-2023)
  • RHEL 8.4 Release Notes.
• Red Hat Ceph Storage 4.3.1 (Red Hat CDN sync 10-May-2023)
  • Ceph Storage 4 Release Notes.
• Red Hat Virtualization Release 4.4 (Red Hat CDN sync 10-May-2023)
  • Red Hat Virtualization 4.4 Release Notes.

• RHEL 8.6–Linux kernel 4.18.0-372.52.1.el8_6.x86_64 for the RHV hosts (Red Hat CDN sync 10-May-2023)

  • RHEL 8.6 Release Notes

• Kubernetes Release 1.23.7
  • Kubernetes 1.23 Release Notes
  • Kubernetes 1.23 Documentation

Contrail Cloud Tuning

All feature and extra configuration samples can be found in your /var/lib/contrail_cloud/samples/features directory on the jump host.

• Optional overcloud tuning in your config/site.yml configuration file with the controller_extra_config parameter. This new parameter is used to provide additional configuration under the ControllerExtraConfig THT section. You can also configure the extra_config: to modify any TripleO parameter documented by Red Hat.

  For a sample of the overcloud controller_extra_config and overcloud extra_config, see the /var/lib/contrail_cloud/samples/features/extra_config/site.yml sample file on your jump host.

  The controller_extra_config supports for additional Nova tuning of the overcloud to match specific settings and requirements. See below for a tuning example:

  content_copy zoom_out_map

  overcloud:
    controller_extra_config:
      nova::config::nova_config:
        filter_scheduler/build_failure_weight_multiplier:
          value: 10000.0
    extra_config:
  

Secured Registries

Secured registry is used as of Contrail Cloud Release 16.3. You must provide your container image registry credentials in your vault-data.yml file.

Always update your vault-data.yml file with your most recent credentials before performing any deployment, or update activities.

From the jump host, see /var/lib/contrail_cloud/samples/vault-data.yml for more information and vault data example. To access the file from the CLI, use ansible-vault view /var/lib/contrail_cloud/samples/vault-data.yml with the default password of c0ntrail123.

Cloud-init Network Configuration Syntax

Cloud-init network configuration Syntax replaces the previous os-net-config syntax in the following locations:

• When configuring control_host_nodes_network_config in your control-host-nodes.yml configuration file. For more information, see /var/lib/contrail_cloud/samples/control-host-nodes.yml.

  content_copy zoom_out_map

  control_host_nodes_network_config:
    version: 1
    config:
    - type: physical
      name: eno1
      subnets:
      - type: dhcp
      mtu: "{{ host.max_mtu }}"
      nm_controlled: true
    - type: physical
      name: eno2
      mtu: "{{ host.max_mtu }}"
      nm_controlled: true
    - type: physical
      name: ens7f0
      mtu: "{{ host.max_mtu }}"
      nm_controlled: true
    - type: physical
      name: ens7f1
      mtu: "{{ host.max_mtu }}"
      nm_controlled: true
    - type: bond
      name: bond0
      mtu: "{{ host.max_mtu }}"
      nm_controlled: true
      bond_interfaces:
        - ens7f0
        - ens7f1
      params:
        bond-mode: "802.3ad"
        xmit_hash_policy: layer3+4
        lacp_rate: fast
        miimon: "100"
  

• When configuring k8s_host_nodes_network_config in your k8s-host-nodes.yml configuration file. For more information, see /var/lib/contrail_cloud/samples/k8s-host-nodes.yml.

  content_copy zoom_out_map

  k8s_host_nodes_network_config:
    version: 1
    config:
    - type: physical
      name: enp1s0
      subnets:
      - type: static
        address: "{{ host.control_ip_netmask }}"
    - type: vlan
      name: "enp1s0.{{ overcloud.network.internal_api.vlan }}"
      vlan_link: enp1s0
      vlan_id: "{{ overcloud.network.internal_api.vlan }}"
      subnets:
      - type: static
        address: "{{ host.internalapi_ip_netmask }}"
        routes:
        - gateway: "{{ overcloud.network.internal_api.gateway }}"
          network: "{{ overcloud.network.internal_api.supernet | ipaddr('network') }}"
          netmask: "{{ overcloud.network.internal_api.supernet | ipaddr('netmask') }}"
    - type: physical
      name: enp2s0
      subnets:
      - type: static
        address: "{{ host.external_ip_netmask }}"
        gateway: "{{ host.gw }}"
        dns_nameservers:
          - "{{ host.dns_server1 }}"
          - "{{ host.dns_server2 }}"
    - type: physical
      name: enp3s0
    - type: vlan
      name: "enp3s0.{{ overcloud.network.tenant.vlan }}"
      vlan_link: enp3s0
      vlan_id: "{{ overcloud.network.tenant.vlan }}"
      subnets:
      - type: static
        address: "{{ host.tenant_ip_netmask }}"
        routes:
        - gateway: "{{ overcloud.network.tenant.gateway }}"
          network: "{{ overcloud.network.tenant.supernet | ipaddr('network') }}"
          netmask: "{{ overcloud.network.tenant.supernet | ipaddr('netmask') }}"
  

Contrail Cloud supports both networking configuration version 1 format, and networking configuration version 2 format. For more information on Cloud-init's network configuration syntax, see:

• Networking Config Version 1

• Networking Config Version 2

Storage Configuration - Mount Point

Contrail Cloud 16 storage configuration has been changed to include the mount point of the storage drive. You can view this change in your /var/lib/contrail_cloud/samples/site.yml configuration file.

storage:
    # Define a set of disk groups that can be referenced for VM virtual disk allocations
    # These become virsh storage pools on the control host
    # Each pool has:
    #   mountpoint: "/absolute/path/where/lvm/will/get/mounted"
    #   type: Either "dir" or "logical".
    #       "dir" does not create any new volumes
    #         it is useful if one large hardware raid is used as /
    #       "logical" is a LVM volume placed on the list of "disk".
    #   disk: List of disk devices to use for the pool
    hdd_storage:
      mountpoint: "/srv/hdd_storage"
      type: logical
      disk:
        - "/dev/disk/by-alias/spinning-0"
        - "/dev/disk/by-alias/spinning-1"
        - "/dev/disk/by-alias/spinning-2"
        - "/dev/disk/by-alias/spinning-3"
    ssd_storage:
      mountpoint: "/srv/ssd_storage"
      type: logical
      disk:
        - "/dev/disk/by-alias/ssd-0"
    #srv:
    #  mountpoint: "/srv"
    #  type: dir