[Feature Request] Make it possible to mark deprecation of flavors

[berendt]

As seen in the PCO documentation (plusserver/docs@aab7f70#diff-9ba625b8251e88c93f9bbf32736650e6a5e6cb65e60fe30600a3e77c99658fe4R58-R61)

The 'os:deprecation' property is used to indicate when a particular Compute Flavor is set for deprecation, signalling that it may be removed or phased out in the future. You can also find a note in the description field.

I think it makes sense to discuss and add such a deprecation property to the SCS flavor standard.

[garloff]

I'm in favor of using machine readable and well-defined flags to communicate from operators to users.
We'd need to think about the precise semantics of it.
So we can add an optional (yet well-defined) setting in our scs: namespace.

• A flavor property (extra_spec) scs:deprecated[=YYYY-MM-DD] is a setting that operators can use to communicate to their users that this flavor is deprecated and won't be supported for much longer. The optional date (recommended!) =YYYY-MM-DD communicates the date until which the user is safe to rely on the flavor. (As usual, operators may overdeliver and keep the flavor longer. It is recommended that operators check which flavors are in use and contact remaining users prior to removal.) scs:deprecated will break standards compliance if applied to a flavor that is mandatory in the respective standard (and if that standard is still in effect on the optionally specified removal date).

Thoughts?

[mbuechse]

I agree. I will bring this before Team IaaS. The name os:deprecation is not defined in the official docs, so an scs: prefix should be preferable, I suppose. (Compared to os, which seems rather generic, or I don't understand it properly.)