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

Indexing of use locks #370

Open
6 tasks
erikh opened this issue Jul 28, 2016 · 0 comments
Open
6 tasks

Indexing of use locks #370

erikh opened this issue Jul 28, 2016 · 0 comments

Comments

@erikh
Copy link
Contributor

erikh commented Jul 28, 2016

Use locks are very useful for controlling mount flow but the UX sucks.

We have watch tools and listing tools, but we really don't have a way of expressing this statement (which I feel to be a pretty important one):

"What hosts are using what volumes?"

Another one that I would like is:

"What volumes are in what states?"

This could be accomplished with a set of indexes which were taken as locks alongside the primary lock. lock.ExecuteWithMultiUseLock can accomplish this atomically.

What I think needs to happen is that this method needs to be extended to do two things:

  • Canned method for acquiring use locks in config/use.go in a way that also populates indexes
  • Multi-Acquire with TTL refresh, which would wrap ExecuteWithMultiUseLock similar to lock.AcquireWithTTLRefresh's behavior with acquire.

The feature also needs a few volcli functions (I think switches would be better than commands here, but up to the implementer):

  • List uses by host
  • Watch uses by host
  • All uses by state (Reason in the use struct)
  • All uses by state, by host.
@yuva29 yuva29 self-assigned this Jul 28, 2016
@erikh erikh added this to the 0.3 milestone Jul 30, 2016
@erikh erikh removed this from the 0.3 milestone Aug 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants