Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: Ib1857448c2cb7e455d5002c27c6f0d83c999539e
Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: I28e9cc11f79f8ae506b98f2cfc7bc6e68eef5a32
Add file to the reno documentation build to show release notes for
stable/2023.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.1.
Sem-Ver: feature
Change-Id: I61bf3f0fa2cff8c80affabff9d78a6fab91ba815
Add file to the reno documentation build to show release notes for
stable/zed.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/zed.
Sem-Ver: feature
Change-Id: I381fb75fc354af99751917d95f30bbfca7adfc8b
The CLI now support the following syntax both for openstack resource
providers list and allocation candidate list commands:
--required T1,T2 --required T3
and it means (T1 or T2) and T3.
In the allocation candidate list command the above can be used both
outside and in a --group context.
Story: 2005345
Story: 2005346
Depends-On: https://review.opendev.org/c/openstack/placement/+/826719
Change-Id: I38ff55bdd072f3a9c1ed03e28192d045cb4096cf
Add file to the reno documentation build to show release notes for
stable/xena.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/xena.
Sem-Ver: feature
Change-Id: Ida17fdbe9fce1971106bba7f84318b9a191a5589
Add file to the reno documentation build to show release notes for
stable/yoga.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/yoga.
Sem-Ver: feature
Change-Id: Ib9f97090a45e7e633c4f4667603c02c406447067
The ``openstack resource provider allocation unset`` command now
supports ``--resource-class`` option, which accepts string of a
resource class. This will remove allocations for the given resource
class from all the providers. If ``--provider`` option is also
specified, allocations to remove will be limited to the given resource
class of the given resource provider.
example1::
# remove VGPU allocation from provider P for this consumer.
allocation unset <consumer_uuid> --provider P --resource-class VGPU
example2::
# remove VGPU allocations from all providers for this consumer.
allocation unset <consumer_uuid> --resource-class VGPU
Change-Id: I91baf9de5205ec15023706a1646556850302d3d9
Story: #2006779
Task: #37304
Add file to the reno documentation build to show release notes for
stable/wallaby.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/wallaby.
Sem-Ver: feature
Change-Id: Ie3d8cff403c70dda6aa9232bcc0adcaf3139ed74
Add file to the reno documentation build to show release notes for
stable/victoria.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/victoria.
Change-Id: I63f598a8bf484a6c44d489649075894e92e688cd
Sem-Ver: feature
The ``openstack allocation candidate list`` command now supports
``--group`` and ``--group-policy`` option. The ``--group`` option is
accepts integer to group granular requests. If specified, following
given options of resources, required/forbidden traits, and aggregates
are associated to that group and will be satisfied by the same resource
provider in the response. Can be repeated to get candidates from
multiple resource providers in the same resource provider tree.
If multiple groups are supplied, the separate groups may or may not
be satisfied by the same provider. If you want the groups to be
satisfied by different providers, set ``--group_policy`` to
``isolate``.
For example:
``openstack allocation candidate list \
--group 1 --resource VCPU=3 --required HW_CPU_X86_SSE \
--group 2 --resource VCPU=4 \
--group_policy isolate``
The granular request is supported in 1.25, but this is tested via
microversion 1.29 since the API is unaware of nested provider
before that version. Note that 1.26-1.29 has no impact to client:
1.25 - Adds support for granular resource requests via numbered
querystring groups in GET /allocation_candidates.
1.26 - Add ability to specify inventory with reserved value equal
to total.
1.27 - Include all resource class inventories in `provider_summaries`
field in response of `GET /allocation_candidates` API even if
the resource class is not in the requested resources.
1.28 - Add support for consumer generation
1.29 - Support nested providers in `GET /allocation_candidates` API.
Change-Id: Ib32181abd12db0c2983065ea9846e911033d53f1
The ``openstack allocation candidate list`` and the ``openstack
allocation candidate list`` command now supports ``--member-of``
option, which accepts a list of comma-separated UUIDs of the
resource provider aggregates. If this is specified, the returned
resource providers must be associated with at least one of the
aggregates identified by uuid. This option can be repeated to
add(restrict) the condition with ``--os-placement-api-version 1.24``
or greater.
This deprecates the ``--aggregate-uuid`` option because it is
difficult to keep using this option to support multiple ``member_of``
feature added in microversion 1.24.
Change-Id: I0f3068c411c504380918f27f994734528fe55c77
Co-Autored-By: Tetsuro Nakamura <tetsuro.nakamura.bc@hco.ntt.co.jp>
Story: #2006940
Task: #37613
The 'resource provider inventory list' and 'resource provider inventory
show' commands describe everything about some given inventory *except*
their usage, which is a pretty important metric in quickly assessing
availability of a given resource. Instead, usage is hidden behind the
'resource provider usage show' command. There doesn't appear to be any
reason for this to the case, aside from wanting to directly map to the
placement API which shouldn't be a goal. Make these commands more
friendly by including usage information. We may want to consider
deprecating the 'resource provider usage show' command in the future,
but that's left for another day.
Change-Id: Iafedac3ff7a5ae60e6027741c44904babf64d3f1
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
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: Iedbe8c96c57403d5ee7208cc89bddd9809b70eb2
Add file to the reno documentation build to show release notes for
stable/ussuri.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/ussuri.
Change-Id: I4c44fffbb953a255e5a556c113abaa85444ce27a
Sem-Ver: feature
This adds support to the resource provider allocation set command
for microversion 1.28 which uses consumer generations to ensure
atomic updates of consumer allocations.
Change-Id: I8f85ee4ff4c39fba69a78bbe642f79a706504df8
Story: #2006912
Task: #37557
Adds the "openstack resource provider allocation unset" command which
allows removing resource provider(s) from the set of allocations for
the given consumer. This can be useful when a consumer has allocations
against more than one resource provider and
"openstack resource provider allocation delete" is undesirable as it
removes all allocations for the consumer. The new unset command requires
"--os-placement-api-version 1.12" or greater.
Note that the --provider option can be specified multiple times.
If the resulting allocations are all gone and 1.28 or greater is not
being used, a DELETE is called rather than PUT since
PUT /allocations/{consumer_id} before 1.28 does not allow an empty
"allocations" dict in the request body. In this case nothing is output
similar to the "openstack resource provider allocation delete" command.
Change-Id: I627bfd1ff699d075028da6afafbe7fb9b2f13058
Story: #2006779
Task: #37304
Add file to the reno documentation build to show release notes for
stable/train.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.
Change-Id: Ib344994b447ad7fd98658f54c316812cbf0eec14
Sem-Ver: feature
This adds a new '--dry-run' option which gives the ability to preview
changes before effecting them.
Story: 2006318
Task: 36190
Change-Id: I24bbe9657c0b83a93f0d4c762992c16e91b4ec47
This adds a new '--amend' option which can update resource provider
inventory without requiring the user to pass a full replacement for
inventory. It does a GET for existing inventory, applies user provided
updates, and does a PUT of the updated inventory.
Story: 2006318
Task: 36049
Change-Id: I4ed1016852144377485959e65077803f5f2c672c
This adds a new '--aggregate' option which can set resource provider
inventory for all resource providers that are members of the specified
aggregate.
The main motivation for this option is to give operators a tool to
make setting overcommit allocation ratios on a per-aggregate basis
easier, after the functionality from the old
Aggregate[Core|Ram|Disk]Filter scheduler filters was removed back in
Ocata [1].
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-January/126283.html
Story: 2006318
Task: 36189
Change-Id: Ib0cbb58d0adbbcfe83ee48d2ff6c9af1a516a7ae
The 1.22 microversion of placement adds support for
excluding resource providers and allocation candidates
with specified traits. A forbidden trait may be specified
with --forbidden option.
Change-Id: I4760fe6119e29d80f63ec7bd6c4a5f2395a9291e
The latter does not work well with Sphinx 2.0.
Switching brings us up to date with modern norms. The
changes made here are to get it working:
* Changing tox jobs to the modern style, with a separate
requirements.txt in the doc directory.
* Updating doc and releasenotes conf.py to use the new
theme and correctly point at storyboard for bugs
* Remove docs related requirements from test-requirements.txt
Change-Id: I9770f375b0fd7a6cacdd02e3d0381a28879f18b5
Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: I23590c9f780018d550c50470649fb2d20b2e3978
Sem-Ver: feature
Add support for member_of/aggregate-uuid when listing allocation
candidates. The choice of arguments intentionally mirrors those
used when listing resource providers, which means that the term
'member of' is not used.
Note that microversion 1.24 [1] is going to make argument parsing
in this area considerably more complex. Not for the computer, but
the humans using the tool. For now we probably want to do what's
here, to do the aforementioned mirroring, but when we get to 1.24
we'll need some brains.
[1] https://docs.openstack.org/placement/latest/placement-api-microversion-history.html#support-multiple-member-of-queryparams
Change-Id: Iba3e31fec29e8e85aa2f6a4248f0a27d7373ba6d
The 1.19 microversion of placement adds support for the
generation parameter when setting aggregates on a resource
provider. The value is an integer generation, available
when listing or showing resource providers.
If an earlier version is chosen, but a --generation arg
provided, an error is reported. Similarly, if not generation
is provided and the version is 1.19 or later, an error
is reported.
The new TestAggregate119 inherits from TestAggregate to
repeat the general validation it does, overrides those
methods which require a generation when using version
1.19, and adds two failure tests. One test in the super
class is adjusted so that it works as desired in both
classes and in both versions of Python (Python3 has
different behavor of a *args before kw args). I considered
changing the signature of base.resource_provider_aggregate_set
but that would have meant changes is several places.
Change-Id: I74157998dd19d8a8d2b68d12ed3726aac11eb013
The 1.18 microversion of placement adds support for the
required parameter when requesting a list of resource
providers. The values are traits which limit the results
to only those providers that have those traits. The
--required argument may be specified multiple times.
Note the NOTE in the added test about raciness. There's
not a ton we can do about that since the functional
tests aren't actually functional tests, they are
integration.
Change-Id: If79b4d12c712fdeeafa5ea77ae3411d31c8cfe9b
Zuul
OpenStack Release Bot