| 2015-06-03 13:00:38 |
Ryan Beisner |
bug |
|
|
added bug |
| 2015-06-03 13:01:03 |
Ryan Beisner |
branch linked |
|
lp:~1chb1n/charm-helpers/heat-amulet |
|
| 2015-06-03 13:01:24 |
Ryan Beisner |
branch linked |
|
lp:~1chb1n/charms/trusty/heat/next-amulet-init |
|
| 2015-06-03 13:02:37 |
Ryan Beisner |
description |
Amulet/openstack service check methods need series and init system awareness for testing Vivid and later.
I'm using the heat amulet test writing effort to also update charm-helpers to resolve this Vivid issue, and other general Wily prep.
[1] validate_services()
http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/amulet/utils.py
[2] _get_openstack_release_string()
http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/openstack/amulet/deployment.py
This affects all openstack charm amulet tests, keystone as an example:
Previous approach presumes presence of upstart:
http://paste.ubuntu.com/11542366/
http://bazaar.launchpad.net/~openstack-charmers/charms/trusty/keystone/next/view/head:/tests/basic_deployment.py |
Amulet/openstack service check methods need series and init system awareness for testing Vivid and later.
I'm using the heat amulet test writing effort to also update charm-helpers to resolve this Vivid issue, and other general Wily prep.
[1] validate_services()
http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/amulet/utils.py
[2] _get_openstack_release_string()
http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/openstack/amulet/deployment.py
This affects all openstack charm amulet tests, keystone as an example:
Previous approach presumes presence of upstart:
http://paste.ubuntu.com/11542366/
http://bazaar.launchpad.net/~openstack-charmers/charms/trusty/keystone/next/view/head:/tests/basic_deployment.py
Once resolved and landed, other openstack charms can also have vivid/wily++ amulet tests. |
|
| 2015-06-03 13:12:39 |
Ryan Beisner |
description |
Amulet/openstack service check methods need series and init system awareness for testing Vivid and later.
I'm using the heat amulet test writing effort to also update charm-helpers to resolve this Vivid issue, and other general Wily prep.
[1] validate_services()
http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/amulet/utils.py
[2] _get_openstack_release_string()
http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/openstack/amulet/deployment.py
This affects all openstack charm amulet tests, keystone as an example:
Previous approach presumes presence of upstart:
http://paste.ubuntu.com/11542366/
http://bazaar.launchpad.net/~openstack-charmers/charms/trusty/keystone/next/view/head:/tests/basic_deployment.py
Once resolved and landed, other openstack charms can also have vivid/wily++ amulet tests. |
Amulet/openstack service check methods need series and init system awareness for testing Vivid and later.
I'm using the heat amulet test writing effort to also update charm-helpers to resolve this Vivid issue, and other general Wily prep.
Affected charm-helper pieces are:
[1] validate_services()
http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/amulet/utils.py
[2] _get_openstack_release_string()
http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/openstack/amulet/deployment.py
This affects all openstack charm amulet tests, keystone as an example:
Previous approach presumes presence of upstart:
http://paste.ubuntu.com/11542366/
http://bazaar.launchpad.net/~openstack-charmers/charms/trusty/keystone/next/view/head:/tests/basic_deployment.py
Once resolved and landed, other openstack charms can also have vivid/wily++ amulet tests. |
|
| 2015-06-12 13:51:28 |
Launchpad Janitor |
branch linked |
|
lp:~openstack-charmers/charms/trusty/heat/next |
|
