neutron

Commit Graph

Author	SHA1	Message	Date
Ihar Hrachyshka	5e0878f476	Added API extensions to detect sorting/pagination features Those features are available only when allow_sorting and allow_pagination options are enabled (the current default is False). They don't depend on plugin support, because when plugins don't implement them natively, emulated mode is applied by API router itself. So to make it plugin agnostic, we introduce a way to register custom per-extension checks to override support detection for cases like that one. Now that we have a way to detect support for those features via API, there is little reason to keep tempest configuration options to enable those features. Instead, just inspect [network-feature-enabled] api_extensions option in tempest.conf. Now that DEFAULT_ALLOW_SORTING/DEFAULT_ALLOW_PAGINATION constants are used in a single place only (in allow_sorting/allow_pagination definitions), removed them and replaced with a literal. Added first in-tree API tests for /extensions entry point. DocImpact Update API documentation to cover new extensions. APIImpact Document the new extensions. Related-Bug: #1566514 Change-Id: I0aaaa037a8ad52060a68dd75c0a1accc6add238e	7 years ago
Ihar Hrachyshka	0cf4ddc6ee	tests: validate sorting and pagination for networks These are the very first API tests in the tree to cover those features. The test is implemented in a generic way that will hopefully ease its adoption for other resources. Sadly, those tests cannot pass on every neutron cloud, at least until we enable those API features by default and remove options to disable the features. There is no way to determine, via neutron API, whether cloud supports those features. To work around that, we introduce two new tempest options that determine whether tests that rely on sorting or pagination should be executed. Those options are set in post-extra phase because configure_tempest resets any configuration made during post-config. Also bump resource quotas x10 times since default quotas are now not enough, at least for network resource that is now under sorting and pagination testing. Related-Bug: #1566514 Change-Id: I5e68f471a641a34100aba31cb2c4a815c7220014	7 years ago
Mark McClain	ee3fe4e836	Rename Quantum to Neutron This change renames everything to Neutron while providing backwards compatible adjustments for Grizzly configuration files. implements blueprint: remove-use-of-quantum Change-Id: Ie7d07ba7c89857e13d4ddc8f0e9b68de020a3d19	10 years ago

Author

SHA1

Message

Date

Ihar Hrachyshka

5e0878f476

Added API extensions to detect sorting/pagination features

Those features are available only when allow_sorting and
allow_pagination options are enabled (the current default is False).

They don't depend on plugin support, because when plugins don't
implement them natively, emulated mode is applied by API router itself.
So to make it plugin agnostic, we introduce a way to register custom
per-extension checks to override support detection for cases like that
one.

Now that we have a way to detect support for those features via API,
there is little reason to keep tempest configuration options to enable
those features. Instead, just inspect [network-feature-enabled]
api_extensions option in tempest.conf.

Now that DEFAULT_ALLOW_SORTING/DEFAULT_ALLOW_PAGINATION constants are
used in a single place only (in allow_sorting/allow_pagination
definitions), removed them and replaced with a literal.

Added first in-tree API tests for /extensions entry point.

DocImpact Update API documentation to cover new extensions.
APIImpact Document the new extensions.
Related-Bug: #1566514
Change-Id: I0aaaa037a8ad52060a68dd75c0a1accc6add238e

Ihar Hrachyshka

0cf4ddc6ee

tests: validate sorting and pagination for networks

These are the very first API tests in the tree to cover those features.
The test is implemented in a generic way that will hopefully ease its
adoption for other resources.

Sadly, those tests cannot pass on every neutron cloud, at least until we
enable those API features by default and remove options to disable the
features.

There is no way to determine, via neutron API, whether cloud supports
those features. To work around that, we introduce two new tempest
options that determine whether tests that rely on sorting or pagination
should be executed. Those options are set in post-extra phase because
configure_tempest resets any configuration made during post-config.

Also bump resource quotas x10 times since default quotas are now not
enough, at least for network resource that is now under sorting and
pagination testing.

Related-Bug: #1566514
Change-Id: I5e68f471a641a34100aba31cb2c4a815c7220014

Mark McClain

ee3fe4e836

Rename Quantum to Neutron

This change renames everything to Neutron while providing backwards
compatible adjustments for Grizzly configuration files.

implements blueprint: remove-use-of-quantum

Change-Id: Ie7d07ba7c89857e13d4ddc8f0e9b68de020a3d19

3 Commits (99f4495c940011293e3cabbb590770dc1e7b6900)