Hi,

in today’s publiccloud-sig meeting we’ve continued the topic of “flavor discoverability”,
a topic that has been part of our discussion for a while. Before I dive into that, a quick heads-up:

So far we’ve been meeting in the odd weeks. We’ll be switching that to the even weeks.
This means, we’ll be meeting again next week (Nov. 29th).

For today’s meeting:

The minutes for the meeting are here:
https://etherpad.opendev.org/p/publiccloud-sig-meeting

Since this was a videocall (and as such no meetingbot logs), here a quick summary (thanks @joek-office).

=======
0. Discussion on flavor/image/volume "search engine" aka flavor-discovery

idea 1:
extend the services with the appropriate features to meet the requirements
cons:

pros:

idea 2:
build up a new service with required metadata based on the .wellknown concept supported by sdk right now (or discoverable via service catalogue - that's not in scope of the service catalog, but the new "discovery" service may be added into the catalog)
cons:

pros:

=========

For people interested in this subject, we (at least gtema and me) are going to continue this discussion tomorrow
at 1400 CET here: https://conf.scs.koeln:8443/OIF-public-cloud-sig

felix

--
Felix Kronlage-Dammers
Product Owner IaaS & Operations Sovereign Cloud Stack

Sovereign Cloud Stack — standardized, built and operated by many
Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V.

Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr@osb-alliance.com