Frode Nordahl caed1ceeb3 Use UTC when calculating certificate validity ...

The current usage of ``datetime.today()`` is at the grace of the
locale settings of the test executor and the instances spun up.

The ``cryptography.x509.CertificateBuilder`` ``not_valud_before``
and ``not_valid_after`` attributes do expect [0] a UTC datetime.

0: https://cryptography.io/en/latest/x509/reference/#cryptography.x509.CertificateBuilder

2019-09-10 12:14:52 +02:00

..

__init__.py

Add zaza namespacing, starting with openstack

2019-04-25 17:46:03 +02:00

bundle.py

Add zaza namespacing, starting with openstack

2019-04-25 17:46:03 +02:00

ceph.py

Add zaza namespacing, starting with openstack

2019-04-25 17:46:03 +02:00

cert.py

Use UTC when calculating certificate validity

2019-09-10 12:14:52 +02:00

cli.py

Avoid adding duplicate handler (#4)

2019-05-14 15:31:55 +02:00

exceptions.py

Add zaza namespacing, starting with openstack

2019-04-25 17:46:03 +02:00

file_assertions.py

Add zaza namespacing, starting with openstack

2019-04-25 17:46:03 +02:00

generic.py

Fix issue that it's a unit rather than app

2019-08-05 09:31:05 +01:00

juju.py

Add zaza namespacing, starting with openstack

2019-04-25 17:46:03 +02:00

openstack.py

Consume the http proxy info using the new OS_ env var fmt

2019-08-29 12:43:46 -05:00

os_versions.py

Update versions to include Train

2019-09-02 16:09:42 +02:00