Six is in use to help us to keep support for python 2.7.
Since the ussuri cycle we decide to remove the python 2.7
support so we can go ahead and also remove six usage from
the python code.
Review process and help
-----------------------
Removing six introduce a lot of changes and an huge amount of modified files
To simplify reviews we decided to split changes into several patches to avoid
painful reviews and avoid mistakes.
To review this patch you can use the six documentation [1] to obtain help and
understand choices.
Additional informations
-----------------------
Changes related to 'six.b(data)' [2]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
six.b [2] encode the given datas in latin-1 in python3 so I did the same
things in this patch.
Latin-1 is equal to iso-8859-1 [3].
This encoding is the default encoding [4] of certain descriptive HTTP
headers.
I suggest to keep latin-1 for the moment and to move to another encoding
in a follow-up patch if needed to move to most powerful encoding (utf8).
HTML4 support utf8 charset and utf8 is the default charset for HTML5 [5].
Note that this commit message is autogenerated and not necesserly contains
changes related to 'six.b'
[1] https://six.readthedocs.io/
[2] https://six.readthedocs.io/#six.b
[3] https://docs.python.org/3/library/codecs.html#standard-encodings
[4] https://www.w3schools.com/charsets/ref_html_8859.asp
[5] https://www.w3schools.com/html/html_charset.asp
Patch 28 of a serie of 28 patches
six fully removed now!
Thank you six for the rendered services!
Change-Id: If44ee4b565cc9390fa0422fba4dda080b4f90b98
Let's skip integration tests using Swift when the service is not
available. It will help turn the py3 gate green.
Change-Id: Ib3536583dbb3bbf50d9c64976e909fd352391d05
The swift key used in aws tests is generated in a fashion that doesn't
work in python3. This fixes it.
Change-Id: I31d7046f343987ca3803cfc95c189e5c9f6dcc8e
yaml.load() provides the ability to construct an arbitrary python object
that may be dangerous. yaml.safe_load() limits this ability to simple
python objects like integers or lists.
ref: https://en.wikipedia.org/wiki/YAML#Security
Change-Id: I9c28c25f4265fb691d39e72e20ef9c99f5538bf5
devstack has moved default Keystone API version to v3[1].
[1] f4ce44bf3f
Though the above patch has been reverted, this would help
if devstack removes v2 support in the future.
Change-Id: I393750d00b3712a015e48a3cf38ab5f95bb61dae
Closes-Bug: #1539692
In integration we publish templates in Swift using temporary URLs.
Unfortunately there is a race condition in the way we setup the key, as
we use the key global to the account. This switches to a container per
test and a key per container to work around that.
Change-Id: Ia19967696811847e5b3ba07df68848a1708c2316
Closes-Bug: #1491773
This adds options to skip scenario and functional tests.
You can either skip the complete set of tests or list of specific
tests.
Following new config options are added:
`skip_scenario_tests` - Skip all scenario tests
`skip_functional_tests` - Skip all functional tests
`skip_functional_test_list` - List of functional tests to skip
`skip_scenario_test_list` - List of scenario tests to skip
`skip_test_stack_action_list` - List of actions in tests to skip
Change-Id: I7a5233f5db1f065ccee5a97408c72203c108a656
Depends-On: I25c5e853f0499b88f2803b077d19e132140908f1
These wait for the stack state to get to complete,
this wasn't done consistently. In test_autoscaling we were
only waiting for the resource state to get to SUSPEND_COMPLETE
and this lead to a time sensitive bug.
Change-Id: Id985d833dc0b4cab1e3cb9d8f67d5d8cc94b5863
Closes-bug: #1438717
Later the integration jobs can be tuned to have their own
logging settings.
This change also raises _log_console_output to info, so it is displayed
by default.
Change-Id: Ifcaa6faf76c655e0c8cfd7d76775b80de70062c4
- use swift to post templates to.
- move limit tests to test_stack_resource
Part of blueprint decouple-nested
Change-Id: Id11e86835addc21301b3534a559d1754a802425e
