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

Maintenance agent for global backend in case of remote backends not being deployed #200

Open
openvstorage-ci opened this issue Sep 8, 2016 · 3 comments

Comments

@openvstorage-ci
Copy link
Contributor

openvstorage-ci commented Sep 8, 2016

From @wimpers on September 8, 2016 12:7

Ticket as extension of #177 (comment) . The approach taken in that case has an issue in case a global backend has only remote backends. In that case there are no nodes known to put the maintenance agents on. In this special case the maintenance agent should run on the same nodes as the proxy or nodes that can be configured with that role.

To be decided which implementation to be taken.

Copied from original issue: openvstorage/framework#887

@wimpers wimpers changed the title Maintenance agent for global backens in case of remote backends Maintenance agent for global backend in case of remote backends not being deployed Sep 9, 2016
@wimpers wimpers added this to the Roadmap milestone Sep 15, 2016
@wimpers
Copy link

wimpers commented Sep 15, 2016

To be discussed how to tackle

@wimpers
Copy link

wimpers commented Mar 9, 2017

@khenderick is this ticket still relevant now that we have #379 .

@khenderick
Copy link
Contributor

@wimpers, it is still relevant and is not changed by #379

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

No branches or pull requests

4 participants