Post for fixing flavor properties.

SovereignCloudStack / website

Base content for scs.community

https://scs.community/

MIT License

5 stars 18 forks source link

Post for fixing flavor properties. #993

Closed garloff closed 3 months ago

garloff commented 3 months ago

Two things to consider:

I added scs:name-v3 into the tool assuming that this is something that is wanted. Maybe it should be removed again, as this does not seem to be aligned yet.
Merging standards/#645 ahead of posting may leave a better impression -- if we find alignment on doing so.

I'd like this to go out today or in the next few days. Want to push CSPs back to green and give them the input needed.

garloff commented 3 months ago

Thanks for the suggestions, @mbuechse.

I have implemented the markdown improvements. (Please let me know if I overlooked a place where an empty line would be needed.)
I have put the rationale for the properties into a subsubsection, so people can more easily skip it, if they don't want to read it. (I have decided against moving it to the end. It is in my view a rather quick and easy read.) If you are a markdown pro with knowledge how to put it in a special box (Info block), I'm open to it. blockquote does not seem matching that well -- that was the only one I saw right away. [!TIP] Using a TIP was not perfect wither.)
Shell output has been updated both for the compliance tool and the flavor-add-extra-specs.py tool.

garloff commented 3 months ago

To Do:

If we merge the tool (standards/#645 with your changes on top), we could fix the reference to it and don't have to refer to a branch and PR.
Alternatively, we could split out the pieces where we use this tool to a second blog article and reference it.

garloff commented 3 months ago

Preview at https://staging.scs.community/website/tech/2024/08/20/flavor-extra-specs-compliance/ (in a few minutes).

fkr commented 3 months ago

Isn't there any way the PR (https://github.com/SovereignCloudStack/standards/pull/645) can be merged before publishing so that we don't have to point the people to a branch? (seems rather complicated....)

mbuechse commented 3 months ago

Isn't there any way the PR (SovereignCloudStack/standards#645) can be merged before publishing so that we don't have to point the people to a branch? (seems rather complicated....)

Yes, of course. From my POV, it can be merged. It would just be good if Kurt could have a final look and maybe test some less ordinary cases (I have tested on environments that either need no change or still lack all extra_specs).