The description param is optional and add unit test for device profile
create.

Related-Bug: #1940810
Change-Id: I93d99d0edcfe8c417e3cd5c4aa3990f31322c6cb

Change-Id: I63527d222a6be6794334346f2dc4bbac6cc9b5c3

Closes-Bug: #1940509
Change-Id: I382d9691301c74c6426668de39c4f05f4b2619fd

inspect.getargspec was deprecated since Python 3.0 and
inspect.getfullargspec is its replacement with correct handling of
function annotations and keyword-only parameters[1].

[1] https://docs.python.org/3/library/inspect.html#inspect.getargspec

Change-Id: I2d3591e41ae35479b613487a81c43548c7cd3f9c

This patch catches the 'ResourceNotFound' exception and adds
 some unittests.

Closes-Bug: #1937251
Change-Id: I1e07528e9b551ff192ee707d1988a8c07bf349a0

This patch adds checking input arg. If not uuid, raise CommandError with
 output like 'Only UUID of device_profile allowed'.

Closes-Bug: #1936877
Change-Id: I24999d0f39cbd027ef5c797ed2e9bf0bbfe8a793

This patch updates/adds the contributor documentation to follow
the guidelines of the Ussuri cycle community goal[1].

[1] https://governance.openstack.org/tc/goals/selected/ussuri/project-ptl-and-contrib-docs.html

Story: #2007236
Task: #38519
Change-Id: Ia738b3f37d1b0a477838c37a91afca14108f85e3

Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:

  UserWarning: Usage of dash-separated 'description-file' will not be
  supported in future versions. Please use the underscore name
  'description_file' instead

[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb

Change-Id: I83d80999568b7236044ac257b19c984fd5e788bb

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for xena.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: Ib2bb3b6f27f29ef7268e4411b669c9a094e3cd48

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: Idf92f17f515f8a7da4b3edebf0fbb710a843dae2

This will cause version conflict:

Obtaining file:///opt/stack/python-cyborgclient
ERROR: Could not satisfy constraints for 'python-cyborgclient': installation from path or url cannot be constrained to a version

or

ERROR: Could not find a version that satisfies the requirement python-cyborgclient 1.3.1.dev1
ERROR: No matching distribution found for python-cyborgclient 1.3.1.dev1

Change-Id: I521f880606fa1aab25cd85875153275c5dd2e125

We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].
Removing specific doc requirements from test-requirements.txt.

The problem here is that this repos haven't doc/requirements.txt file
and by default in this case zuul will use the test-requirements.txt file
to pull requirements [4].

This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new pip
resolver fails to install these requirements and the job exits in error.

This project meet the conditions leading to the bug.

[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36

Change-Id: Ie4cc84c7159f4b59be52439ef6e4c5e60474866d

Change-Id: I51e852a81e0337842f14296dda7613d85209c936

Reason for revert: Python 3.7 *is* supported because it falls
in the range of supported Python versions (3.6-3.8).

Change-Id: I7365634864f09eb04a68d901ca4ca962fa4d7bb2

Change-Id: I4c7a02bfff3cfd314c71f2a22a1684897fda152c

Remove python3.7 from setup.cfg, since Wallaby's python
supported runtimes are python 3.6 and python 3.8[1]:

[1]: https://governance.openstack.org/tc/reference/runtimes/wallaby.html

Change-Id: Iaa89b4d36e9c391a2bd294e9b5e39d817d843559

Change-Id: If10f63674f2f7a4c0a38b7f76a2ba8ea86bab3ae

Change-Id: I7f278088722a3e0e0fd502be45337c485d9f282b

Change-Id: I1674693c06ea21210ceed002154c0cf70b2ec22b

Change-Id: Ie43342e156e32aceae5af8630ea91830273923db

As per victoria cycle testing runtime and community goal[1],
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).

Bump lower constraints to make testing work for Focal.

[1]https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal

Change-Id: I2eeaa3fdec4841eae6fe706ef5f4ef120b21a30f
Story: 2007865
Task: 40181

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for wallaby.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I0d82ace6f9745b02868ac7b627218e625546f0b1

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: Ibc047731bf08644197c462a66b4e3fe061c4746e
Sem-Ver: feature

It is difficult to create device profile with command because of
the groups parameter is hard to pass, so add e.g. for the command
``openstack help accelerator device profile create``, that we
can get the example for the `group` parameter.

Change-Id: I6afa3ec4c3cc0d14d0632ff821fdf200c736da0e