Add procedure for converting external Swift storage nodes - #1342
Conversation
8e5a2d1 to
0bdade4
Compare
|
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
8716ee6 to
0bdade4
Compare
|
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
0bdade4 to
45137bb
Compare
84c7b1b to
2437811
Compare
Thanks @klgill for your review! I applied your changes and squashed them into the first commit. I added a second commit with a few additions/fixes, can you have a look at that one too please? I'll squash the commit as well once you reviewed these changes. |
2437811 to
b7818a8
Compare
59c7186 to
df52575
Compare
Thanks @klgill, applied all suggestions and squashed them into the main commit. Changes from yesterdays commit: https://github.com/openstack-k8s-operators/data-plane-adoption/compare/b7818a8d98e0dfe8232b6b869f2201ab455c4117..df52575eed95d484bfcf6bf22e861e6085303a82 |
klgill
left a comment
There was a problem hiding this comment.
I have one minor formatting change. One of the notes is not rendering properly in the preview.
98f987d to
dedf9bb
Compare
Thanks, I just committed & squashed the change. |
|
@cschwede My latest suggestion didn't work either. I'll need to look at it on my own after this is merged. |
@klgill Yes, FR6 - this is the feature: OSPRH-23099 |
Adds documentation for converting existing TripleO-managed Swift storage nodes post-adoption without data migration. There are two ways to adopt existing Swift storage nodes: 1. Migrate data to PVs (or dataplane nodes), which is required if Swift storage was deployed on previous controller nodes 2. Convert existing TripleO/Director-managed nodes to dataplane nodes, which should be used for any former external ObjectStorage node to avoid moving huge amounts of data. This commit adds documentation for the second option; the first one already exists. JIRA: OSPRH-23099 Signed-off-by: Christian Schwede <cschwede@redhat.com> Co-authored-by: Katie Gilligan <kgilliga@redhat.com>
dedf9bb to
9fdeaab
Compare
@klgill I think the issue was the intendation: https://github.com/openstack-k8s-operators/data-plane-adoption/compare/dedf9bbcc91a531915e172da698cd74a6cb12886..9fdeaabd9ca139bddd841985e7ee29534551ecfa |
Yes, that looks better! |
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
bf6e42f
into
openstack-k8s-operators:main
Adds documentation for converting existing TripleO-managed Swift storage nodes post-adoption without data migration.
There are two ways to adopt existing Swift storage nodes:
This commit adds documentation for the second option; the first one already exists.