Short-term need informing long-term design: Landscape integration
Gary Poster
gary.poster at canonical.com
Fri Jan 25 17:39:11 UTC 2013
Hi Nick. Great, thank you. I commented on the doc.
Gary
On 01/25/2013 11:14 AM, Nick Boettcher wrote:
> Hi all
>
> I've mocked-up a potential solution to the stories and requirements
> mentioned below. This is specific to the current interface for the JuJu GUI.
>
> https://docs.google.com/a/canonical.com/file/d/0B1IM--9A1RkTUURlRU1raFNoM1k/edit
>
> It's a discussion piece so please let me know your thoughts. Add
> comments to the document or feel free to respond via email.
>
> Cheers,
> Nick.
>
>
>
> On 23/01/2013 23:32, Gary Poster wrote:
>> Hi Alejandra, Nick and everyone.
>>
>> The GUI devs should be starting work on Landscape integration very soon.
>> I currently suspect it will be the week after next.
>>
>> Short-term, that will involve adding some links and visual indicators to
>> the current interface, and we'd like your advice and guidance with that.
>> Longer term, you'll want to incorporate these stories into the revised
>> UX that you are working on now.
>>
>> I currently have a list of the technical changes we've been requested to
>> make. I'd like to reverse engineer those into user stories we want to
>> tell, and then plan the GUI changes from those stories.
>>
>> So, to put the cart before the horse, here are the technical changes we
>> have. To be clear, a "Landscape link" means a link to the Landscape
>> application.
>>
>> * We have a Landscape link to view/manage the machines that represent
>> the current environment.
>>
>> * We have a Landscape link to view/manage the set of machines that
>> represent a given service.
>>
>> * We have a Landscape link to view/manage a single machine that is
>> running a given service unit.
>>
>> * We have information about whether a unit is on a machine that needs
>> security updates from Landscape.
>>
>> * We have information about whether a unit is on a machine that needs a
>> reboot from Landscape.
>>
>> Example user stories (Emmanuel is our SA persona):
>>
>> Emmanuel wants to use the GUI to monitor the health of his juju
>> environment. He goes to the GUI environment and looks at his services.
>> He sees that there are no markers indicating a problem, and so he goes
>> off and does something else. He comes back later and sees an indication
>> that the mediawiki service has some machines that need a security
>> update. He gets an option to go to Landscape and resolve the problem,
>> which he takes. The browser opens Landscape, replacing the GUI. He
>> does not need to login, because he was using it recently. He sees a
>> list of all the machines that need a security update in the environment,
>> and confirms that he wants the update to happen. He then sees an option
>> to return to the GUI, which he takes. He does not need to log in (devs:
>> Kapil wants to use http://code.google.com/p/sessionstorage/), and
>> returns to approximately the same view he was on before.
>>
>> Emmanuel is looking at the GUI, and wants to check the more detailed
>> status of the environment's machines in Landscape. He takes an option
>> to go to Landscape. This moves the browser from the GUI to Landscape.
>> He logs in. He investigates a bit, makes some changes, and then is
>> finished. He then decides to return to the GUI. He does not need to
>> log in again to the GUI.
>>
>> Emmanuel is looking at the GUI and sees there is a Juju error in the
>> mediawiki service. Investigating, he sees that only one of the units
>> has a problem. He decides to look at the unit's machine in Landscape to
>> see if he can get more information to diagnose or fix the problem. He
>> takes an option to go to Landscape. This moves the browser from the GUI
>> to Landscape to look at that machine. Emmanuel investigates and
>> resolves the issue. He returns to the GUI from Landscape and marks the
>> unit as resolved.
>>
>> Thanks
>>
>> Gary
>
More information about the Juju-GUI
mailing list