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.

Sign up for GitHub

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

Jump to bottom

Implement a clean-up option #63

Open
brainfunked opened this issue Nov 27, 2017 · 8 comments
Open

Implement a clean-up option #63

brainfunked opened this issue Nov 27, 2017 · 8 comments
Labels
enhancement question

Comments

@brainfunked
Copy link
Contributor

The following steps need to be executed:

  • Stop all tendrl components.
  • Stop etcd.
  • Empty the etcd data directory on all etcd nodes.
  • Start etcd and verify that it has started with no keys present.
  • Start the tendrl node agents on all nodes.
  • Start all the other tendrl components.
@mbukatov
Copy link
Collaborator

mbukatov commented Nov 28, 2017 •
edited
Loading

Is this the same feature as described in #50 ? Could i use details you provided here to implement #50 as well?

@mbukatov
Copy link
Collaborator

How would we cope with etcd authentication?

@mbukatov mbukatov added this to the changes_for_v1.5.5 milestone Nov 28, 2017
@mbukatov mbukatov removed this from the changes_for_v1.5.5 milestone Feb 16, 2018
@mbukatov
Copy link
Collaborator

mbukatov commented Mar 8, 2018

Is this still relevant when we have unmanage feature specification?

@mbukatov
Copy link
Collaborator

mbukatov commented Mar 9, 2018

See also: https://github.com/shtripat/tendrl-cleanup

@nthomas-redhat
Copy link
Contributor

@mbukatov , I think we still need to support this as part of tendrl-ansible

@mbukatov
Copy link
Collaborator

Ack.

@mbukatov
Copy link
Collaborator

@nthomas-redhat I have few additional questions:

  • the main use case for this is to remove all tendrl data in etcd, right?
  • what about other data, such as graphite?
  • why would someone wanted to run such playbook? what is the motivation behind this?

@shtripat
Copy link
Member

Sending a PR to tackle this and the code would take care of below things

  • Stop collectd and tendrl services on storage nodes
  • Stop all tendrl specific services in server node
  • Stop grafana-server, carbon-cache and etcd on server node
  • Clean etcd, grafana and carbon data files from server node

After this cleanup, user can run tendrl-ansible again to setup again.

shtripat pushed a commit to shtripat/tendrl-ansible that referenced this issue Nov 14, 2018
Added cleanup meachnism for tendrl setup
267a1b9 
The cleanup playbook performs the below steps
- Stops collectd, tendrl-node-agent and tendrl-gluster-integration
on storage nodes
- Stops tendrl-node-agent, tendrl-monitoring-integration, tendrl-notifier,
tendrl-api on tendrl server node
- Stops grafana-server, carbon-cache and etcd services on storage nodes
- Cleans up etcd, grafana and carbon data files

tendrl-bug-id: Tendrl/issues/63
Signed-off-by: Shubhendu <[email protected]>
@shtripat shtripat mentioned this issue Nov 14, 2018
Open
shtripat pushed a commit to shtripat/tendrl-ansible that referenced this issue Nov 14, 2018
Added cleanup meachnism for tendrl setup
82778a6 
The cleanup playbook performs the below steps
- Stops collectd, tendrl-node-agent and tendrl-gluster-integration
on storage nodes
- Stops tendrl-node-agent, tendrl-monitoring-integration, tendrl-notifier,
tendrl-api on tendrl server node
- Stops grafana-server, carbon-cache and etcd services on storage nodes
- Cleans up etcd, grafana and carbon data files

tendrl-bug-id: Tendrl/issues/63
Signed-off-by: Shubhendu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@brainfunked @mbukatov @nthomas-redhat @shtripat