OpenStack Cinder Pure Storage Charm

charm-cinder-purestorage:stable/20.10

  1. Git
  2. lp:charm-cinder-purestorage
  3. stable/20.10
Last commit made on 2020-11-02
Get this branch:
git clone -b stable/20.10 https://git.launchpad.net/charm-cinder-purestorage

Branch merges

Branch information

Name:
stable/20.10
Repository:
lp:charm-cinder-purestorage

Recent commits

2a27dd0... by Aurelien Lourot

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch tests to stable.

Switch to using stable charm-helpers branch.

Switch to using stable charm.openstack branch.

Change-Id: Iec1f88d868c3a081031b43946d85be62fdc69dbb

0f1bba2... by Alex Kavanagh

Rebuild reactive charms to pick up latest charm-helpers release.

v0.20.18 has been released and needs incorporating into the reactive charms.

Change-Id: I5494aa2a8c42015eac587037074123f758649f83

116628d... by Alex Kavanagh

Sync libraries & common files prior to freeze

* charm-helpers sync for classic charms
* charms.ceph sync for ceph charms
* rebuild for reactive charms
* sync tox.ini files as needed
* sync requirements.txt files to sync to standard

Change-Id: Ib6dd363b65b962b6ee2626ee824c1b27769b2cbf

b95d09f... by Aurelien Lourot

Add focal-victoria to the test gate

Change-Id: I239e6129dcc970753c4a4fb074a3d744933e7d7a

b7c34b9... by Alex Kavanagh

Release sync for 20.08

- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
- sync tox.ini
- sync requirements.txt and test-requirements.txt

Change-Id: I53c6ce3f08eebbca22caab0c8a8b81c46116a139

fc1d422... by Zuul <email address hidden>

Merge "Remove inherited configuration options invalid for charm"

e273d83... by Aurelien Lourot

Add Victoria test bundles

Change-Id: I65d31b439c83ef6dea0f1b0f333101918b228592

ec02c2c... by Liam Young

Add focal and ussuri bundles to the charm

Change-Id: I839e720ccdea1440069ea98b84b1621a47824325

a6c109e... by Zuul <email address hidden>

Merge "Stop to use the __future__ module."

4b17e45... by Herve Beraud

Stop to use the __future__ module.

The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.

We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.

Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]

[1] https://docs.python.org/3/library/__future__.html
[2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[3] https://www.python.org/dev/peps/pep-0238
[4] https://www.python.org/dev/peps/pep-3105
[5] https://www.python.org/dev/peps/pep-3112
[6] https://www.python.org/dev/peps/pep-0343
[7] https://www.python.org/dev/peps/pep-0328

Change-Id: I4b49b03729d67d0b442686a06a569243988c0ce2