此内容没有您所选择的语言版本。
Appendix A. Sample environment file: creating a Ceph Storage cluster
The following custom environment file uses many of the options described throughout Chapter 2, Preparing overcloud nodes. This sample does not include any commented-out options. For an overview on environment files, see Environment Files (from the Advanced Overcloud Customization guide).
/home/stack/templates/storage-config.yaml
- 1
- The
parameter_defaults
section modifies the default values for parameters in all templates. Most of the entries listed here are described in Chapter 4, Customizing the Storage service. - 2
- If you are deploying the Ceph Object Gateway, you can use Ceph Object Storage (
ceph-rgw
) as a backup target. To configure this, setCinderBackupBackend
toswift
. See Section 4.2, “Enabling the Ceph Object Gateway” for details. - 3
- The
CephAnsibleDisksConfig
section defines a custom disk layout for deployments using BlueStore. - 4
- For each role, the
*Count
parameters assign a number of nodes while theOvercloud*Flavor
parameters assign a flavor. For example,ControllerCount: 3
assigns 3 nodes to the Controller role, andOvercloudControlFlavor: control
sets each of those roles to use thecontrol
flavor. See Section 7.1, “Assigning nodes and flavors to roles” for details.NoteThe
CephMonCount
,CephMdsCount
,OvercloudCephMonFlavor
, andOvercloudCephMdsFlavor
parameters (along with theceph-mon
andceph-mds
flavors) will only be valid if you created a customCephMON
andCephMds
role, as described in Chapter 3, Deploying Ceph services on dedicated nodes. - 5
NeutronNetworkType:
sets the network type that theneutron
service should use (in this case,vxlan
).