-
Notifications
You must be signed in to change notification settings - Fork 112
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
Move again NFS server after EDPM deploy #1407
Move again NFS server after EDPM deploy #1407
Conversation
Skipping CI for Draft Pull Request. |
Temporarily integrated #1409 to check whether zuul is really able to combine two changes on the same github repository. |
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/90615520f08d46f7921eb2c23de27435 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 31m 05s |
@tosky hello! Is this still relevant? If so, care to mark it "ready for review" and advertise it? Thanks! |
It is still relevant but several unrelated issues prevented me from testing it, and now I have troubles understanding what is failing. But it is still definitely relevant, and I don't think I can mark it as ready yet. |
82e28d6
to
6667d21
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/44a86407652a4388bc47eded7a1debfe ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 51m 40s |
Otherwise the target EDPM node has no full networking setup, which means the choosen VLAN where to expose This means that any usage of NFS should be moved to the post_deploy phase, possibly reconfiguring an existing control plane. This mirror the similar mechanism used to configure and use Ceph on EDPM nodes.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pablintino The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
b14d023
into
openstack-k8s-operators:main
Otherwise the target EDPM node has no full networking setup, which means the choosen VLAN where to expose
This means that any usage of NFS should be moved to the post_deploy phase, possibly reconfiguring an existing control plane.
This mirror the similar mechanism used to configure and use Ceph on EDPM nodes.
As a pull request owner and reviewers, I checked that: