Feature Configurations¶
Documentation on additional features for TripleO.
- Configuring API access policies
- Backend Configuration
- Deploying Manila in the Overcloud
- Configuring Cinder with a Custom Unmanaged Backend
- Configuring Cinder with a NetApp Backend
- 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
- Network Options
- SSH User Options
- Container Options
- 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
- Domain-specific LDAP Backends
- Use an external Swift Proxy with the Overcloud
- Bare Metal Instances in Overcloud
- Deploying with Composable Services
- Deploying with Custom Networks
- Deploying with Custom Roles
- Manage Virtual Persistent Memory (vPMEM)
- Deploy an additional nova cell v2
- Example 1. - Basic Cell Architecture in Train release
- Example 2. - Split Cell controller/compute Architecture in Train release
- 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 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
- Additional cell considerations and features
- Managing the cell
- Deploy and Scale Swift in the Overcloud
- Using Already Deployed Servers
- Deploying DNSaaS (Designate)
- Disable Telemetry
- Distributed Compute Node deployment
- Introduction
- Supported failure modes and High Availability recommendations
- Deploying DCN
- Updating DCN
- Running Ansible across multiple DCN stacks
- Distributed Multibackend Storage
- Features
- Architecture
- Stacks
- Ceph Deployment Types
- 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
- Tolerate deployment failures
- Configuring High Availability
- Configuring Instance High Availability
- Deploying with IPSec
- Keystone Security Compliance
- Enable LVM2 filtering on overcloud nodes
- Multiple Overclouds from a Single Undercloud
- 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
- Modifying default node configuration
- Provisioning of node-specific Hieradata
- Deploying Octavia in the Overcloud
- Deploying Operational Tools
- Configuring Messaging RPC and Notifications
- Deploying with OVS DPDK Support
- Deploying with SR-IOV Support
- Deploying with RHSM
- 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
- 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
- Security Hardening
- Splitting the Overcloud stack into multiple independent Heat stacks
- Deploying with SSL
- TLS Introduction
- Deploying TLS-everywhere
- Deploying custom tuned profiles
- (DEPRECATED) Installing a Undercloud Minion
- Deploying with vDPA Support
- Configure node before Network Config