Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add TripleO requirements playbook #637

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

fmount
Copy link
Contributor

@fmount fmount commented Oct 1, 2024

This playbook represents a requirement for some storage services (e.g. Manila, but it can be extended to Glance NFS in the future) to prepare a TripleO based environment to perform the adoption. Manila, when a ceph-nfs backend is used, requires a cephadm based NFS cluster, and the goal of this patch is:

  1. Propagate the StorageNFS network to the Ceph target nodes
  2. Deploy a CephNFS cluster to the specified VIP

This is in line with the documentation and by executing this preliminary playbook we're able to simplify the Manila adoption process.

This playbook represents a requirement for some storage services (e.g.
Manila, but it can be extended to Glance NFS in the future) to prepare
a TripleO based environment to perform the adoption. Manila, when a
ceph-nfs backend is used, requires a cephadm based NFS cluster, and the
goal of these tasks are:
1. Propagate the StorageNFS network to the Ceph target nodes
2. Deploy a CephNFS cluster to the specified VIP

This is in line with the documentation and by executing this preliminary
playbook we're able to simplify the Manila adoption process.

Signed-off-by: Francesco Pantano <[email protected]>
@fmount
Copy link
Contributor Author

fmount commented Oct 1, 2024

This is required by #620

gather_facts: true
tasks:
# Propagate StorageNFS network
- name: Propagate Storage NFS network
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe I can put a condition to skip this in case we want to execute against a standalone environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant