charm deprecation needs a user-visible warning

Bug #1474093 reported by Mike McCracken
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
quantum-gateway (Juju Charms Collection)
Fix Released
High
Corey Bryant

Bug Description

As the next release switches to neutron-gateway, a user who does a 'juju deploy quantum-gateway' needs to have some way of knowing that it's deprecated code.

I wouldn't necessarily expect that the user has read the most recent README for the charm (especially if they're using a bundle or the openstack-installer package)

I'm not sure what all the options available are, but perhaps using the juju workload-status API would be a good start?

Alternatively, if the plan is to just redirect quantum-gateway to neutron-gateway at the charm store level so it's impossible to freshly deploy stale code, that'd be great.

Related branches

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

Right, not everyone reads the release notes. We sent a ~1mo. reminder to the juju mailing list, and should probably send another @ freeze.

One of the options discussed was to have the quantum-gateway name space contain a dummy charm >= 15.07, with juju status and debug log deprecation messages, and otherwise no charm functionality (ie. deploy would just fail).

Revision history for this message
Mike McCracken (mikemc) wrote : Re: [Bug 1474093] Re: charm deprecation needs a user-visible warning

As discussed on irc, the dummy charm sounds like a good idea to me.

On Mon, Jul 13, 2015 at 12:00 PM, Ryan Beisner <email address hidden>
wrote:

> Right, not everyone reads the release notes. We sent a ~1mo. reminder
> to the juju mailing list, and should probably send another @ freeze.
>
> One of the options discussed was to have the quantum-gateway name space
> contain a dummy charm >= 15.07, with juju status and debug log
> deprecation messages, and otherwise no charm functionality (ie. deploy
> would just fail).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1474093
>
> Title:
> charm deprecation needs a user-visible warning
>
> Status in quantum-gateway package in Juju Charms Collection:
> New
>
> Bug description:
> As the next release switches to neutron-gateway, a user who does a
> 'juju deploy quantum-gateway' needs to have some way of knowing that
> it's deprecated code.
>
> I wouldn't necessarily expect that the user has read the most recent
> README for the charm (especially if they're using a bundle or the
> openstack-installer package)
>
> I'm not sure what all the options available are, but perhaps using the
> juju workload-status API would be a good start?
>
> Alternatively, if the plan is to just redirect quantum-gateway to
> neutron-gateway at the charm store level so it's impossible to freshly
> deploy stale code, that'd be great.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/charms/+source/quantum-gateway/+bug/1474093/+subscriptions
>

Changed in quantum-gateway (Juju Charms Collection):
status: New → Fix Committed
assignee: nobody → Corey Bryant (corey.bryant)
status: Fix Committed → Confirmed
Changed in quantum-gateway (Juju Charms Collection):
status: Confirmed → Fix Committed
Liam Young (gnuoy)
Changed in quantum-gateway (Juju Charms Collection):
importance: Undecided → High
milestone: none → 15.10
James Page (james-page)
Changed in quantum-gateway (Juju Charms Collection):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.