4b01172be2
During the overcloud deployment phase, some operations should still be performed on the provisioned Ceph cluster. When Ceph is TripleO deployed, cephadm doesn't provide any firewall configuration (–-skip-firewalld is provided), as well as any HA configuration for the Ceph Dashboard. This change introduces a new cephadm/ branch containing all the services that should be configured in the TripleO context. Co-Authored-By: Giulio Fidente <gfidente@redhat.com> Co-Authored-By: John Fulton <fulton@redhat.com> Depends-On: I35e57abddc64310a6422174fe191bd328588d7cd Change-Id: Ie9537471924d1d60f7642699e58e734511b91a2b
18 lines
902 B
YAML
18 lines
902 B
YAML
---
|
|
features:
|
|
- It is now possible to deploy Ceph with TripleO using cephadm.
|
|
deprecations:
|
|
- Ceph Deployment using Ceph versions older than Octopus is deprecated.
|
|
- |
|
|
The CephOsdPercentageMin parameter has been deprecated and has a new default
|
|
of 0 so that the validation is not run. There is no need to fail the deployment
|
|
early if a percentage of the OSDs are not running because the Ceph pools created
|
|
for OpenStack can now be created even if there are 0 OSDs as the PG number is no
|
|
longer required on pool creation. TripleO no longer waits for OSD creation and
|
|
instead only queues the request for OSD creation with the ceph orchestrator.
|
|
other:
|
|
- |
|
|
The CephPoolDefaultPgNum paramter default is now 16. The Ceph pg_autoscaler
|
|
is enabled by default in the supported versions of Ceph though the parameter
|
|
CephPoolDefaultPgNum may still be used as desired.
|