Greetings OpenStack community,
Today's meeting was mostly devoted to two topics: Which of Monty's several
patches were ready for freeze and some naming issues with raising the minimum
microversion.
We decided three of Monty's patches are ready, they are listed below in the
"Freeze" section.
The naming issue related to an optional field we want to add to the microversion discovery
document. Some projects wish to be able to signal that they are intending to raise the minimum
microversion at a point in the future. The name for the next minimum version is fairly clear:
"next_min_version". What's less clear is the name which can be used for the field that
states the earliest date at which this will happen. This cannot be a definitive date because
different deployments will release the new code at different times. We can only say "it will
be no earlier than this time".
Naming this field has proven difficult. The original was "not_before", but that has no
association with "min_version" so is potentially confusing. However, people who know how
to parse the doc will know what it means so it may not matter. As always, naming is hard, so we
seek input from the community to help us find a suitable name. This is something we don't want to
ever have to change, so it needs to be correct from the start. Candidates include:
* not_before
* not_raise_min_before
* min_raise_not_before
* earliest_min_raise_date
* min_version_eol_date
* next_min_version_effective_date
If you have an opinion on any of these, or a better suggestion please let us know,
either on the review at <https://review.openstack.org/#/c/446138/>, or in
response to this message.
# Newly Published Guidelines
Nothing new at this time.
# API Guidelines Proposed for Freeze
Guidelines that are ready for wider review by the whole community.
* Add guideline about consuming endpoints from catalog
https://review.openstack.org/#/c/462814/
* Add support for historical service type aliases
https://review.openstack.org/#/c/460654/
* Describe the publication of service-types-authority data
https://review.openstack.org/#/c/462815/
# Guidelines Currently Under Review [3]
* Microversions: add next_min_version field in version body
https://review.openstack.org/#/c/446138/
* A suite of several documents about doing version discovery
Start at https://review.openstack.org/#/c/459405/
* WIP: microversion architecture archival doc (very early; not yet ready for
review)
https://review.openstack.org/444892
# Highlighting your API impacting issues
If you seek further review and insight from the API WG, please address your concerns in
an email to the OpenStack developer mailing list[1] with the tag "[api]" in the
subject. In your email, you should include any relevant reviews, links, and comments to
help guide the discussion of the specific challenge you are facing.
To learn more about the API WG mission and the work we do, see OpenStack API
Working Group [2].
Thanks for reading and see you next week!
# References
[1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[2] http://specs.openstack.org/openstack/api-wg/
[3] https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
[4] Start at https://review.openstack.org/#/c/462814/
[5] https://review.openstack.org/#/c/446138/
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent tw: @anticdent
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
