Feature Configurations

Documentation on additional features for TripleO.

• Configuring API access policies
• Backend Configuration
  • Deploying Manila in the Overcloud
    • Deploying the Overcloud with the Internal Ceph Backend
      • Network Isolation
    • Deploying Manila in the overcloud with CephFS through NFS and a composable network
      • CephFS with NFS-Ganesha deployment
      • Configure the StorageNFS network
    • Deploying the Overcloud with an External Backend
    • Creating the Share
    • Accessing the Share
  • Configuring Cinder with a Custom Unmanaged Backend
    • Adding a custom backend to Cinder
  • Configuring Cinder with a NetApp Backend
    • Deploying the Overcloud
    • Creating a NetApp Volume
  • Deploying Ceph with TripleO
    • Deployed Ceph Workflow
    • Deployed Ceph Scope
    • Multiple Ceph clusters per deployment
    • Prerequisite: Ensure the Ceph container is available
    • Prerequisite: Ensure the cephadm package is installed
    • Prerequisite: Ensure Disks are Clean
    • Deployed Ceph Command Line Interface
    • Ceph Configuration Options
    • Placement Groups (PGs)
    • Ceph Name Options
    • Ceph Spec Options
    • Overriding which disks should be OSDs
    • Service Placement Options
    • Ceph VIP Options
    • Deploy additional daemons
    • Example: deploy HA Ceph NFS daemon
    • Crush Hierarchy Options
      • Example: Apply a custom crush hierarchy to the deployed OSDs
    • TLD option
    • Network Options
      • Example: Multiple subnets with custom network names
      • Example: IPv6
      • Example: Directly setting network and ms_bind options
    • SSH User Options
    • Container Options
    • NTP configuration
    • Creating Pools and CephX keys before overcloud deployment (Optional)
    • Environment files to configure Ceph during Overcloud deployment
    • Applying Ceph server configuration during overcloud deployment
    • Applying Ceph client configuration during overcloud deployment
    • Ceph Pool Options
    • Overriding CRUSH rules
    • Overriding CephX Keys
    • Add the Ceph Dashboard to a Overcloud deployment
    • Scenario: Deploy Ceph with TripleO and Metalsmith and then Scale Up
    • Scenario: Scale Down Ceph with TripleO and Metalsmith
    • Scenario: Deploy Hyperconverged Ceph
  • Use an external Ceph cluster with the Overcloud
    • Deploying Cinder, Glance, Nova, Gnocchi with an external Ceph RBD service
    • Configuring Ceph Clients for Multiple External Ceph RBD Services
    • Deploying Manila with an External CephFS Service
    • Compatibility Options
    • Deployment of an Overcloud with External Ceph
    • Standalone Ansible Roles for External Ceph
      • Single Ceph Cluster
      • Multiple Ceph Clusters
  • Domain-specific LDAP Backends
    • Setup
    • Post-deployment setup
    • FreeIPA as an LDAP backend
  • Use an external Swift Proxy with the Overcloud
• Bare Metal Instances in Overcloud
  • Architecture and requirements
  • Preparing undercloud
  • Configuring and deploying ironic
    • Essential configuration
    • Additional configuration
    • Using a Custom Network for Overcloud Provisioning
    • Deployment
    • Validation
  • Post-deployment configuration
    • Resource classes
    • Preparing networking
    • Networking using a custom network
    • Configuring networks
      • Configuring networks on deployment
      • Configuring networks per node
    • Adding deployment images
    • Creating flavors
    • Creating host aggregates
    • Creating instance images
  • Enrolling nodes
    • Preparing inventory
    • Enrolling nodes
    • Populating host aggregates
    • Checking available resources
  • Booting a bare metal instance
  • Booting a bare metal instance from a cinder volume
  • Configuring ml2-ansible for multi-tenant networking
    • ml2-ansible configuration
    • ml2-ansible example
• Deploying with Composable Services
  • Deploying with custom service lists
• Deploying with Custom Networks
  • Default networks
  • Deploying with custom networks
  • Network data YAML options
    • Options for network data YAML subnet definitions
  • Network Virtual IPs data YAML options
• Deploying with Custom Roles
  • Provided example roles
  • Deploying with custom roles
• Manage Virtual Persistent Memory (vPMEM)
  • Prerequisite
  • TripleO vPMEM parameters
  • Examples
• Deploy an additional nova cell v2
  • Example 1. - Basic Cell Architecture in Train release
    • Extract deployment information from the overcloud stack
      • Export EndpointMap, HostsEntry, AllNodesConfig, GlobalConfig and passwords information
      • Create roles file for the cell stack
      • Create cell parameter file for additional customization (e.g. cell1/cell1.yaml)
      • Create the network configuration for cellcontroller and add to environment file
    • Deploy the cell
      • Create new flavor used to tag the cell controller
      • Run cell deployment
    • Create the cell and discover compute nodes (ansible playbook)
    • Create the cell and discover compute nodes (manual way)
      • Add cell information to overcloud controllers
      • Extract transport_url and database connection
      • Create the cell
      • Perform cell host discovery
      • Create and add the node to an Availability Zone
  • Example 2. - Split Cell controller/compute Architecture in Train release
    • Extract deployment information from the overcloud stack
      • Create roles file for the cell stack
      • Create cell parameter file for additional customization (e.g. cell1/cell1.yaml)
      • Create the network configuration for cellcontroller and add to environment file
    • Deploy the cell
      • Create new flavor used to tag the cell controller
      • Run cell deployment
    • Create the cell
    • Extract deployment information from the cell controller stack
      • Export EndpointMap, HostsEntry, AllNodesConfig, GlobalConfig and passwords information
      • Create cell compute parameter file for additional customization
    • Deploy the cell computes
      • Run cell deployment
      • Perform cell host discovery
      • Create and add the node to an Availability Zone
  • Example 3. - Advanced example using split cell controller/compute architecture and routed networks in Train release
    • Used networks
    • Prepare control plane for cell network routing
    • Reuse networks and adding cell subnets
    • Export EndpointMap, HostsEntry, AllNodesConfig, GlobalConfig and passwords information
    • Cell roles
    • Create the cell parameter file
    • Virtual IP addresses
    • Create the network configuration for cellcontroller and add to environment file
    • Deploy the cell controllers
      • Create new flavor used to tag the cell controller
      • Run cell deployment
    • Create the cell
    • Extract deployment information from the cell controller stack
    • Create cell compute parameter file for additional customization
    • Reusing networks from control plane and cell controller stack
    • Deploy the cell computes
      • Run cell deployment
      • Perform cell host discovery
      • Create and add the node to an Availability Zone
  • Additional cell considerations and features
    • Availability Zones (AZ)
      • Configuring AZs for Nova (compute)
    • Routed networks
    • Reusing networks from an already deployed stack
    • Configuring nova-metadata API per-cell
  • Managing the cell
    • Add a compute to a cell
    • Delete a compute from a cell
    • Delete a cell
    • Updating a cell
• Deploy and Scale Swift in the Overcloud
  • Initial Deploy
  • Scaling Swift
  • Viewing the Ring
• Using Already Deployed Servers
  • Deployed Server Requirements
    • Networking
      • Network interfaces
      • Undercloud
      • Overcloud
      • Testing Connectivity
    • Package repositories
  • Deploying the Overcloud
    • Provision networks and ports if using Neutron
    • Deployment Command
      • With generated baremetal and network environments
      • Without generated environments (no Neutron)
  • Scaling the Overcloud
    • Scaling Up
    • Scaling Down
  • Deleting the Overcloud
• Deploying DNSaaS (Designate)
• Disable Telemetry
  • Deploy your overcloud without Telemetry services
    • Disabling Notifications
• Distributed Compute Node deployment
  • Introduction
  • Supported failure modes and High Availability recommendations
    • Loss of control plane connectivity
    • Loss of an edge site
    • Improving resiliency for N/S and E/W traffic
    • Network recommendations
    • Config-drive/cloud-init details
    • IPv6 details
    • Storage recommendations
  • Deploying DCN
    • Undercloud configuration
      • Using direct deploy instead of iSCSI
      • Configure the Swift temporary URL key
      • Configure nodes to use the deploy interface
    • Deploying the control plane
    • Deploying a DCN site
      • Saving configuration from the overcloud
      • Network resource configuration
      • DCN related roles
      • Configuring Availability Zones (AZ)
        • Configuring AZs for Nova (compute)
        • Configuring AZs for Cinder (storage)
        • Deploying Ceph with HCI
        • Sample environments
    • Example: DCN deployment with pre-provisioned nodes, shared networks, and multiple stacks
      • Undercloud
      • Deploy the control-plane stack
      • Exported configuration from the control-plane stack
      • Deploy the central stack
      • Deploy the edge-0 and edge-1 stacks
  • Updating DCN
  • Running Ansible across multiple DCN stacks
• Distributed Multibackend Storage
  • Features
  • Architecture
  • Stacks
  • Ceph Deployment Types
    • Decide which cephx key will be used to access remote Ceph clusters
  • Deployment Steps
    • Create a separate external Cephx key (optional)
    • Create control-plane roles
    • Deploy the central Ceph cluster
    • Deploy the control-plane stack
    • Extract overcloud control-plane and Ceph configuration
    • Create extra Ceph key for dcn0 (optional)
    • Override Glance defaults for dcn0
    • Create DCN roles for dcn0
    • Deploy the dcn0 Ceph cluster
    • Deploy the dcn0 stack
    • Deploy additional DCN sites
    • Update central site to use additional Ceph clusters as Glance stores
  • DCN using only External Ceph Clusters (optional)
  • Confirm images may be copied between sites
  • Confirm image-based volumes may be booted as DCN instances
  • Confirm image snapshots may be created and copied between sites
• Node customization and Third-Party Integration
  • Firstboot extra configuration
  • Per-node extra configuration
  • Post-Deploy extra configuration
• Tolerate deployment failures
• Configuring High Availability
• Configuring Instance High Availability
• Deploying with IPSec
  • Solution Overview
  • Deployment
  • Verification
• Keystone Security Compliance
• Enable LVM2 filtering on overcloud nodes
• Multiple Overclouds from a Single Undercloud
  • Requirements
  • Undercloud Deployment
  • First Overcloud
  • Deploying Additional Overclouds
  • Managing Heat Templates
  • Using Pre-Provisioned Nodes
• Configuring Network Isolation
  • Introduction
  • Architecture
  • Workflow
  • Create and Edit network data YAML definition file
  • Create the networks, segments and subnet resources on the Undercloud
  • Create and Edit network Virtual IPs YAML definition file
  • Create the overcloud network Virtual IPs on the Undercloud
  • Generate Templates from Jinja2
  • Create Network Environment Overrides File
  • Configure IP Subnets
  • Configure Bonding Options
  • Creating Custom Interface Templates
  • Customizing the Interface Templates
  • Migrating existing Network Interface Configuration Templates
  • Updating Existing Network Interface Configuration Templates
  • Configuring Interfaces
  • Configuring Routes and Default Routes
  • Using a Dedicated Interface For Tenant VLANs
  • Using the Native VLAN for Floating IPs
  • Using the Native VLAN on a Trunked Interface
  • Configuring Jumbo Frames
  • Assigning OpenStack Services to Isolated Networks
  • Deploying the Overcloud With Network Isolation
  • Creating Floating IP Networks
  • Creating Provider Networks
• Configuring Network Isolation in Virtualized Environments
  • Introduction
  • Create an External VLAN on Your Undercloud
  • Create a Custom Environment File
  • Modify Your Overcloud Deploy to Enable Network Isolation
• Modifying default node configuration
  • Making ansible variable changes
  • Making puppet configuration changes
• Provisioning of node-specific Hieradata
  • Collecting the node UUID
  • Creating the Heat environment file
  • Generating the Heat environment file for Ceph devices
  • Deploying with NodeDataLookup
• Deploying Octavia in the Overcloud
  • Preparing to deploy
  • Configuring the amphora image
  • Deploying the overcloud with the octavia services
  • Uploading/Updating the amphora image after deployment
• Deploying Operational Tools
  • Architecture
  • Deploying the Operational Tool Server
  • Deploying the Undercloud
  • Before deploying the Overcloud
• Configuring Messaging RPC and Notifications
  • Standard Deployment of RabbitMQ Server Backend
  • Deployment of Separate RPC and Notify Messaging Backends
• Deploying with OVS DPDK Support
  • Deploy Command
  • Parameters
  • Network Config
• Deploying with SR-IOV Support
  • Deploy Command
  • Parameters
  • Network Config
• Deploying with RHSM
  • Summary
  • Using RHSM
  • Scale-down the Overcloud
  • Transition from previous method
  • More about the Ansible role
• Role-Specific Parameters
• Deploying Overcloud with L3 routed networking
  • Layer 3 routed Requirements
  • Layer 3 routed Limitations
  • Create undercloud configuration
  • Install the undercloud
  • DHCP relay configuration
    • Broadcast DHCP relay
    • Unicast DHCP relay
    • DHCP relay configuration (Example)
  • Map bare metal node ports to control plane network segments
  • Create network data with multi-subnet networks
  • Create roles specific to each leaf (layer 2 segment)
  • Configure node placement
  • Add role specific configuration to parameter_defaults
  • Network configuration templates
  • Virtual IP addresses (VIPs)
  • Deploy the overcloud
• Disabling updates to certain nodes
  • Server blacklist
    • Setting the blacklist
    • Clearing the blacklist
  • Skip deploy identifier
• Security Hardening
  • Horizon Password Validation
  • Default Security Values in Horizon
    • Enforce Password Check
    • Disallow Iframe Embed
    • Disable Password Reveal
  • SSH Banner Text
  • Audit
  • Firewall Management
    • VXLAN and nftables
  • AIDE - Intrusion Detection
    • Further AIDE values
    • Cron configuration
    • AIDE and Upgrades
  • SecureTTY
  • Keystone CADF auditing
  • login.defs values
• Splitting the Overcloud stack into multiple independent Heat stacks
  • split-stack Requirements
  • Default split-stack deployment
    • Baremetal Deployment Command
    • Services Deployment Command
• Deploying with SSL
  • Undercloud SSL
  • Overcloud SSL
    • Certificate and Public VIP Configuration
    • Certificate Details
    • DNS Endpoint Configuration
    • Deploying an SSL Environment
    • Getting the overcloud to trust CAs
• TLS Introduction
  • Certmonger
  • FreeIPA
    • Installing FreeIPA
  • Novajoin
  • tripleo-ipa
• Deploying TLS-everywhere
  • TLS-everywhere with tripleo-ipa
    • Configure DNS
    • Configure FreeIPA
      • Create a FreeIPA role
      • Register the undercloud
      • Create a principal
    • Configure the Undercloud
    • Undercloud Install
    • Undercloud Verification
  • TLS-everywhere with Novajoin
    • Configure DNS
    • Add Undercloud as a FreeIPA host
    • Configure the Undercloud
    • Undercloud Install
    • Undercloud Verification
  • Configuring the Overcloud
    • Set Parameters
    • Composable Services
    • Novajoin Composable Service
    • tripleo-ipa Composable Service
    • Specify Templates
  • Overcloud Verification
  • Deleting Overclouds
• Deploying custom tuned profiles
  • Deploying with existing tuned profiles
  • Deploying with custom tuned profiles
• (DEPRECATED) Installing a Undercloud Minion
  • Installation Steps
• Deploying with vDPA Support
  • Deploy Command
  • Parameters
  • Network Config
  • Network and Port Creation
  • Scheduling instances
  • Validations
• Configure node before Network Config
  • Custom Service