Merge lp://staging/~corey.bryant/openstack-charm-testing/add-new-svcs-to-sparse into lp://staging/openstack-charm-testing

Proposed by Corey Bryant
Status: Merged
Approved by: Ryan Beisner
Approved revision: 263
Merged at revision: 265
Proposed branch: lp://staging/~corey.bryant/openstack-charm-testing/add-new-svcs-to-sparse
Merge into: lp://staging/openstack-charm-testing
Diff against target: 214 lines (+115/-10)
2 files modified
bundles/sparse/default.yaml (+73/-3)
bundles/sparse/next.yaml (+42/-7)
To merge this branch: bzr merge lp://staging/~corey.bryant/openstack-charm-testing/add-new-svcs-to-sparse
Reviewer Review Type Date Requested Status
Ryan Beisner Needs Information
OpenStack Charm Testing Maintainers Pending
Review via email: mp+313156@code.staging.launchpad.net

Commit message

Add aodh, barbican, and designate to sparse default/next bundles.

To post a comment you must log in.
Revision history for this message
Ryan Beisner (1chb1n) wrote :

I'm pretty sure one or more of these have Trusty support. Can you check into that before we proceed? Thanks!

review: Needs Information
Revision history for this message
Corey Bryant (corey.bryant) wrote :

aodh and designate do have trusty charm versions. I started working on these updates, but I'm not sure if it's worth adding them to the bundle for trusty, since the charm/packages were new in yakkety.

Revision history for this message
Corey Bryant (corey.bryant) wrote :

clarification: the charms were new in yakkety

Revision history for this message
Ryan Beisner (1chb1n) wrote :

If the charms support Trusty (and some do), we need the bundles to define those targets imho. Otherwise we're releasing charm to a series that isn't tested.

If the practicality measure says why-bother @ trusty on those new charms, then we should confer, discuss and decide to remove that series from the charm metadata - and if so, then my reservations here evaporate. :-)

review: Needs Information
Revision history for this message
James Page (james-page) wrote :

I think we agreed that trusty-mitaka would be support for deployment on
trusty as that's the last series supported for 14.04.
On Tue, 10 Jan 2017 at 18:02, Ryan Beisner <email address hidden>
wrote:

> Review: Needs Information
>
> If the charms support Trusty (and some do), we need the bundles to define
> those targets imho. Otherwise we're releasing charm to a series that isn't
> tested.
>
> If the practicality measure says why-bother @ trusty on those new charms,
> then we should confer, discuss and decide to remove that series from the
> charm metadata - and if so, then my reservations here evaporate. :-)
> --
>
> https://code.launchpad.net/~corey.bryant/openstack-charm-testing/add-new-svcs-to-sparse/+merge/313156
> Your team OpenStack Charmers is subscribed to branch
> lp:openstack-charm-testing.
>

263. By Corey Bryant

Enable aodh and designate for trusty-mitaka

Revision history for this message
Corey Bryant (corey.bryant) wrote :

Ok finally got back to this! aodh and designate are now deployed if trusty-mitaka or greater is chosen. And if xenial or greater is chosen barbican is added to the deployment.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches

to status/vote changes: