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

Destroy the bootstrap node in an attempt to test backup and restoration. #1806

Closed
Ebaneck opened this issue Sep 30, 2019 · 1 comment
Closed
Assignees
Labels
complexity:medium Something that requires one or few days to fix topic:ci Continuous integration and build orchestration

Comments

@Ebaneck
Copy link
Contributor

Ebaneck commented Sep 30, 2019

Component:

'tests', 'backup', 'restore' 'ci'

Why this is needed:

While performing a bootstrap node recovery, we do not have any real need for the old bootstrap node and as such we should destroy it completely.

What should be done:

Add a CI step to destroy the old bootstrap node.

Implementation proposal (strongly recommended):

Seems to me that there is no real need to destroy the entire open stack multi-node infrastructure. We could destroy the bootstrap node with a kubectl delete node bootstrap

It looks like some extra cleanup is needed such as

  • Maybe cleaning up Persistent Data if any exist on the host (prometheus data for example)
  • For any hosts that had ran an etcd service, there could be a couple of items that may need to be cleaned up (e.g Remove the etcd backups by running rm -r /var/lib/etcd/member/*.)

Test plan:

@Ebaneck Ebaneck added moonshot topic:ci Continuous integration and build orchestration topic:build Anything related to building steps complexity:medium Something that requires one or few days to fix labels Sep 30, 2019
@slaperche-scality slaperche-scality removed the topic:build Anything related to building steps label Oct 4, 2019
@alexandre-allard alexandre-allard self-assigned this Nov 14, 2019
@alexandre-allard
Copy link
Contributor

Closing this issue as it has already been done in #2061 (#1687)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity:medium Something that requires one or few days to fix topic:ci Continuous integration and build orchestration
Projects
None yet
Development

No branches or pull requests

4 participants