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

RFC: Handling resources shared with me #113

Open
ryran opened this issue Feb 1, 2017 · 2 comments
Open

RFC: Handling resources shared with me #113

ryran opened this issue Feb 1, 2017 · 2 comments

Comments

@ryran
Copy link
Owner

ryran commented Feb 1, 2017

Currently, the only resources ravshello manages that are shareable are blueprints. (For future reference, VM images & disk images are also shareable.)

In managing resources that have been "shared with me", we have a few options:

  1. ignore them completely; assume that people will manage them from the Web UI and that no one wants to see them in ravshello
  2. show them in a separate per-resource subfolder (e.g., /blueprints/Shared_with_me and in the future, /images/Shared_with_me)
  3. show them in a top-level /shared-with-me folder (e.g., /shared-with-me/bps/SOMEBP) -- I don't like this
  4. Do 2 or 3 only if ravshello is run with a particular cmdline arg (e.g., --showshared)
  5. Do 2 or 3 only after running some command, e.g., /blueprints show_shared, or something like that
@ryran ryran self-assigned this Feb 1, 2017
@ryran
Copy link
Owner Author

ryran commented Feb 1, 2017

For right now, shared bps automatically show up in /blueprints/Shared_with_me but I'm leaning towards hiding them by default and implementing an option. Feedback welcome.

@ajblum
Copy link
Contributor

ajblum commented Feb 3, 2017

My preference would be for #5

Do 2 or 3 only after running some command, e.g., /blueprints show_shared, or something like that

I like the idea that you might be working within ravshello and then get the idea that you want to see "all" blueprints even those that were shared with you. Rather than exiting and re-running, you can just issue a new command in the configshell.

Between #2 and #3, I prefer #2 since I'd probably be looking for some blueprint whether its shared or not. I wouldn't want to first do /blueprints ls and then /shared_with_me/bps ls.

I wouldn't like #1 ... because ravshello uses the API directly, I would like for it to always exceed whats possible with the WebUI :)

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

2 participants