| ... | ... | @@ -16,7 +16,9 @@ |
|
|
|
|
|
|
|
|
|
|
|
# Feedback
|
|
|
|
|
|
|
|
## From: Noah Meyerhans <noahm@debian.org>
|
|
|
|
|
|
|
|
1. It'd be good to use a static (bookmarkable) URL for the provider
|
|
|
|
details pages. If, for example, I'm an openstack user, I don't want to
|
|
|
|
have to click through several pages of general purpose information
|
| ... | ... | @@ -34,6 +36,21 @@ services on a daily basis. That will likely differ somewhat based on the |
|
|
|
cloud provider.
|
|
|
|
|
|
|
|
|
|
|
|
### Answer to Noah Meyerhans <noahm@debian.org>
|
|
|
|
|
|
|
|
Hi Noah, in response to your feedback:
|
|
|
|
|
|
|
|
1. "on using a static (bookmarkable) URL for the provider", this was already
|
|
|
|
planned in our backlog. So for example given the URL=finder.debian.org the path for open stack it will be finder.debian.org/open-stack.
|
|
|
|
|
|
|
|
2. The ideia for this problem it that we will provide one API route that OpenStack will use to update the generated image to finder application. The only thing that is important to us is this data from Open Stack for example when a new image is uploaded returns some ID to be placed in the metadata file?
|
|
|
|
|
|
|
|
|
|
|
|
Thanks for your feedback!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## From: Thomas Goirand <zigo@debian.org>
|
|
|
|
|
|
|
|
1. In your "provider details", I can see name, zone, version, etc., though
|
| ... | ... | |
