Commit Graph

7 Commits

Author SHA1 Message Date
Ghanshyam Mann 7a44dcaf25 Moving IRC network reference to OFTC
Change-Id: I85e4074b867e050f0d36dcec94fb719e3a6c3deb
2021-07-08 18:30:11 -05:00
Aurelien Lourot 6390d21b29 THIS CHARM IS DEPRECATED
See https://review.opendev.org/c/openstack/charm-guide/+/796639

Its functional tests are written with the deprecated
Amulet framework (replaced by Zaza). Our CI system
zOSCI can't run Amulet tests.

Change-Id: Iae83b12199468c18c76a5571eeae9c6a94e83af6
Related-Bug: #1828424
2021-06-16 14:34:45 +02:00
Ryan Beisner 2e2ca0f50a Update readme to clarify charm intent
Change-Id: Iaaf19cee5ba65021049c2cc0460f945852478926
2019-08-16 21:36:39 +00:00
wu.chunyang 73ee650e20 Remove the duplicated word
Change-Id: Ib8ff4a85a0db400c8368d56c19229a9c30c02a1f
2018-08-21 15:06:16 +08:00
Alex Kavanagh 2651c4a038 Add amulet/bundle tests to charm-barbican-softhsm
This adds keystone v2 and v3 tests to the charm.
However, because of bug#1611393 the tests can't execute test 400 which
would check the API to barbican.  Thus, it is disabled and the tests
only check that the relation is set up properly.

Change-Id: Ibfcdd82b070f7688a815fcbb1a089090d9529e2a
2016-08-10 13:57:57 +00:00
Alex Kavanagh a1d134bccd Update the charm to work with renamed barbican-hsm interface
The barbican-hsm-plugin interface was changed to barbican-hsm.
2016-07-13 16:43:08 +00:00
Alex Kavanagh 45e370b142 Charm with unit tests
Working charm with unit tests. Various features:

Change the install ownership for token store

It turns out that the 'user' that creates the token store, is the only one that
can access it, apart from root.  As Barbican uses a 'barbican' user for the
barbican-worker process, we need to create the token store with 1777 perms (see
https://github.com/opendnssec/SoftHSMv2/issues/185) and also create the initial
token using the barbican user.

Add an initial README.md: This describes the charm, where to get help
and how to use it.
2016-07-12 16:53:46 +00:00