Cyborg has now published their api-ref at the default location[0], drop
the old override.
[0] https://docs.openstack.org/api-ref/accelerator/
Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: I93b0d4c021f710667d4b8e0f8e78f16dc3b7fa67
This prevents setuptools 61.0.0 doing autodiscovery and failing
since this is not a python module.
Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: I52164b745c5fa2182d8116877eec3a314c930373
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_version to not auto-version the documents.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I7f07fc60f45deb2a415af1216ab5b37398cb2929
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove obsolete sections from setup.cfg
- Cleanup doc/source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
- Remove hacking from requirements, it's required in tox.ini already
Change-Id: Ie5d87c62cca191c345bc273e9e43415ec4501df7
Remove now obsolete python 2.7.x support from setup.py,
update pbr version and make dependency explicit via requirements.txt
This change was pushed to test that the dependent change fixes
publishing content to https://service-types.openstack.org/ . So,
please merge once dependency is in and then we can check that publishing
to server works correctly.
Depends-On: https://review.opendev.org/709060
Change-Id: Iac2be67dbef5510679f5cda658b591e52d537051
Switch the job service-types-authority-tox-publish to parent to
opendev-tox-docs so that as a followup we can use a promote job.
This is a step in changing the service-type website to AFS
publishing.
Change-Id: Ibeb60fd5805befc21c9d6d00fa7a615a106393cf
Depends-On: https://review.opendev.org/708517
Task: #37723
Story: #2006598
* Update git URLs to use opendev.org.
* Remove obsolete sphinx instructions from setup.cfg, those are note
used anymore.
* Change homepage to publish page of this repo.
* Remove install_command, the default works just fine.
Change-Id: I9f763b0daa513868e6ce04291cea5f4c1b88a942
Change Iac9054de55728601d839c1feede15c2a5acc45b6 made the
propose-updates job protected, meaning it can only be defined in the
project-config repo. Move it to there
Needed-By: https://review.opendev.org/678135
Change-Id: Id839ac69ed44553a8d2d88547b2c54502af4a913
The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
Change-Id: Iad1424ec96f0f768d5429e6593ff48d425a31a29
Watcher now has an API on developer.o.o, we can use the default.
Update broken links with current version.
Change-Id: Ifa61ffc163e22066b091e2c1874215279ae99d11
Remove oslosphinx, it is deprecated and does not work with Sphinx 2.0.
Instead use openstackdocstheme.
Use newer sphinx-build in tox docs environment following PTI.
Change-Id: Ib19f12e5603b7b5c787cafd77551eb3cf7fbc4cd
Rather than business-logic, because it may not exactly
be used by a business, and avoiding the word 'workflow'.
Story: 2004498
Change-Id: Ie565e06f48980d49a1527949ad55088fc506c48d
It had been nova, but is in the process of becoming placement.
Thus it is also no longer "secondary".
api-ref continues to be in the same place.
Change-Id: I64b579180542342afe71f05afe175d14e10a539d
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Iafd8de12b2955193e2f10d5219d55f30f361ddac
Story: #2002586
Task: #24757
This is a service-type used out in the wild, and was one of the names
for the service back in the day. Add it, otherwise some things break.
Change-Id: Ie8a7cff4b6f83456fbe8ff685b1fd28585fe2473
Yaml.load() return Python object may be dangerous if you receive a YAML
document from an untrusted source such as the Internet. The function
yaml.safe_load() limits this ability to simple Python objects like integers or
lists.
Reference:
https://security.openstack.org/guidelines/dg_avoid-dangerous-input-parsing-libraries.html
Change-Id: Iea14d26e6937472d1ac4b8f441bd59c959d2deb0
The publication job looks in doc/build/html but we're writing it to
publish/. Update the location ... and also add a success-url to the job
so we can verify the content.
Change-Id: I44de36fcac19a754ec107554b7a300dacd62aa3a
Move legacy tox job in-tree and convert to Zuul v3 native syntax.
Use tox as parent, we do not need constraints setup.
Name the job "publish" instead of previously validate since it calls
the publish environment.
Change-Id: Ib676370e4ccf6c6a0c2f9384a0e023b54521a3b7
python-openstacksdk has updated itself to drive the names of the service
objects it presents from the service-types-authority, using the official
service-type in the source code and docs but also registering each on
the Connection object by each of its known aliases. It was already
close, but in four cases it had chosen names that were more consistent
from an English point of view.
Add aliases for each of those.
Change-Id: I973b67043aa0bca305d7b10035567c175ac782b8
The masakari project is an Official OpenStack project.
It has used the 'ha' service-type up until now, but that's a bit broad.
It was agreed that 'instance-ha' would be better. Add it to the registry.
The api-ref documentation is not currently published, but it does exist
in tree:
http://git.openstack.org/cgit/openstack/masakari/tree/api-ref/source
The jobs to publish it have been added:
https://review.openstack.org/#/c/534878
but as the api-ref publication jobs use service-types-authority to
determine the correct place to publish to, the api-ref docs won't exist
until we land this. Once we do and once a publication job runs, they
should be found at the appropriate place.
Change-Id: Icdd0b09060ddd71b2313a90c1d62d84c31cdbb8d
The api_reference for a service_type should usually be
'https://developer.openstack.org/api-ref/{service_type}/'.
With this change set, the source yaml may omit the api_reference field,
whereupon it will be generated according to the above format.
(At this time it is recommended, though not enforced, that the
api_reference field *should* be omitted if it conforms to the above
format.)
Change-Id: I860c1373c72765d4abad1ce8744c8174e5c64de0
This makes comparing changes to the file easy for a human while not violating
the files as computer readable data files. The ordering doesn't have meaning,
it's just for ease of human consumption.
Change-Id: I16f9e4df1acdcc2436cfd413707625a31007a0a2
This reverts commit 492010c2ce.
Restore this once project-config is updated to support secondary services (and maybe aliases).
Change-Id: Id59ebc3aadcd68b4654251962426bc4a0066136e
The breaks project-config, the sanity check in project-config
needs work to handle aliases.
Let's revert this, update project-config - and then readd.
This reverts commit 3f136b6a21.
Change-Id: I49796742d8e23b475c62ee96ed969785749af903
After a few attempts at retrofitting the newly-minted service type
naming rules to established services, we've discovered that's more
hassle than it's worth.
This change updates the guidelines to make it okay for historical
service types to keep their established names, while reinforcing that
new service types should conform to the stated rules.
Change-Id: I1f9d45ae1ccc0a397e2cc83dc8bb61a9b61971fe
Senlin has historically used `clustering` as its service_type. We've
decided [1] to stop trying to retrofit existing historical services'
official service_types to conform to the naming guidelines, because it's
more painful than it's worth.
However, since at this point we've published sta with
`resource-cluster`, we now need to maintain that as an alias :(
[1] https://review.openstack.org/494241
Change-Id: Ic3c04c6d6ce98a56f333f8566d1cba9c65431313
The os-service-types project generates some internal mappings that are
useful. Generate them here on publication so that others can benefit as
well.
Change-Id: Ib761cf9de875e7b80404797d4aa8d294ca56347a
Rather than dump twice, once for each file, dump once to a variable.
Then, while we've got it in memory, strip trailing spaces. It's not
required that json output have no trailing spaces, but gerrit shows them
as does vim when opening files to look at them. It's easy to rememdy,
and we're rolling out some file updates in the next patch anyway.
Change-Id: Id3d04655264480b202a58b93a813360003707508
It's in the nova repo, which is the first time we've done that. Mark it
as secondary so that project-to-service-type can find compute from nova
still.
Closes-Bug: #1709353
Publish placement-api-ref
Depends-On: If5ff9bcc31e2680861e959ef7dc8581210e619e9
Support secondary services
Depends-On: I01ad2934bdcb9346f4af88520f572d9b4f852b5d
Change-Id: Id319fc48e37ccbf68c8086296a1e18b7545e7400
Zuul