| ... | ... | @@ -107,6 +107,17 @@ https://salsa.debian.org/openstack-team/debian/openstack-debian-images/tree/debi |
|
|
|
6. I don't think there's ever going to be anyone providing i386
|
|
|
|
images... :)
|
|
|
|
|
|
|
|
Hi Thomas, in response to your feedback:
|
|
|
|
1. I think that show better details about onde specific image, we will update this on our prototype.
|
|
|
|
|
|
|
|
2. In this case we can remove Release and leave just Code name, but just to clarify the finder will only stores images details about public cloud providers but we still consider the output fields.
|
|
|
|
|
|
|
|
3. This is a thing that we are getting feedback to see witch model will be mode interactive with users, but we note your point of view on this topic.
|
|
|
|
|
|
|
|
4. For images generated on CI/CD the final job will update automatically the finder, for public providers that build their own images when they publish one new image they will need to post the metadata on the finder API that we will provide for each provider.
|
|
|
|
|
|
|
|
|
|
|
|
5
|
|
|
|
|
|
|
|
## From: Bastian Blank <waldi@debian.org>
|
|
|
|
1. I'm not sure where you want to go with that "architecture" knobs on the home page. In most cases (GCE, Azure at least) it will be only amd64, and then it looks silly. AWS just recently added arm64, but that is a detail you only need to know later.
|
| ... | ... | |
