'juju status' difficult to read and provides unneccessary information

Bug #1183129 reported by Jono Bacon
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Low
Unassigned
juju-core (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

From using 'juju status' it provides me with a lot of detail, but most of it I don't care about. I care about the following:

 * Are my machines up.
 * Are my charms connected.
 * Where can access my service online?

To illustrate this I deployed two wordpress charms with mysql. This is what 'juju status' gives me:

jono@forge:~$ juju status
machines:
  "0":
    agent-state: started
    agent-version: 1.10.0
    dns-name: ec2-107-22-102-86.compute-1.amazonaws.com
    instance-id: i-d5db6fbf
    series: precise
  "1":
    agent-state: started
    agent-version: 1.10.0
    dns-name: ec2-54-226-44-116.compute-1.amazonaws.com
    instance-id: i-74500d1c
    series: precise
  "2":
    agent-state: started
    agent-version: 1.10.0
    dns-name: ec2-54-226-45-46.compute-1.amazonaws.com
    instance-id: i-5a500d32
    series: precise
  "3":
    agent-state: started
    agent-version: 1.10.0
    dns-name: ec2-54-226-15-107.compute-1.amazonaws.com
    instance-id: i-13169273
    series: precise
services:
  mysql:
    charm: cs:precise/mysql-19
    exposed: false
    relations:
      db:
      - wordpress
    units:
      mysql/0:
        agent-state: started
        agent-version: 1.10.0
        machine: "2"
        public-address: ec2-54-226-45-46.compute-1.amazonaws.com
  wordpress:
    charm: cs:precise/wordpress-15
    exposed: true
    relations:
      db:
      - mysql
      loadbalancer:
      - wordpress
    units:
      wordpress/0:
        agent-state: started
        agent-version: 1.10.0
        machine: "1"
        public-address: ec2-54-226-44-116.compute-1.amazonaws.com
      wordpress/1:
        agent-state: pending
        agent-version: 1.10.0
        machine: "3"
        public-address: ec2-54-226-15-107.compute-1.amazonaws.com

I just took a few minutes to play with an alternative way of presenting this information based upon the information I really care about (I think all the detail shown above should be accessible with 'juju status -v').

I think this is a better way of displaying it:

jono@forge:~$ juju status

Overview:

   [All services started]

   wordpress/0: ec2-54-226-44-116.compute-1.amazonaws.com
   wordpress/1: ec2-54-226-44-116.compute-1.amazonaws.com
   mysql: ec2-54-226-45-46.compute-1.amazonaws.com

Topology:

   mysql/0 --|-- wordpress/0
             |-- wordpress/1

Machines:

  "0" (i-d5db6fbf) [STARTED]
    Version: 1.10.0
    DNS: ec2-107-22-102-86.compute-1.amazonaws.com
    Series: precise

  "1" (i-74500d1c) [STARTED]
    Version: 1.10.0
    DNS: ec2-54-226-44-116.compute-1.amazonaws.com
    Series: precise

  "2" (i-5a500d32) [STARTED]
    Version: 1.10.0
    DNS: ec2-54-226-45-46.compute-1.amazonaws.com
    Series: precise

  "3" (i-5a500d32) [STARTED]
    Version: 1.10.0
    DNS: ec2-54-226-15-107.compute-1.amazonaws.com
    Series: precise

The 'Overview' section tells me if everything is up and where to access my things. The 'Topology' section makes it clear that everything is connected. The 'Machines' section gives me details about the individual machines, but I re-formatted these to highlight the status (I put all status indications in square brackets in this mock-up).

I would strongly recommend we display this (or another improved) simplified status as the default and show the detail with -v.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: juju-core 1.10.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
Uname: Linux 3.9.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu1
Architecture: i386
Date: Wed May 22 14:35:59 2013
InstallationDate: Installed on 2013-05-05 (17 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130504)
MarkForUpload: True
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jono Bacon (jonobacon) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in juju-core (Ubuntu):
status: New → Confirmed
James Page (james-page)
Changed in juju-core (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Wishlist
William Reade (fwereade)
Changed in juju-core:
status: New → Triaged
importance: Undecided → Wishlist
Curtis Hovey (sinzui)
tags: added: ui
removed: cli-ui
Curtis Hovey (sinzui)
tags: added: improvement
Curtis Hovey (sinzui)
Changed in juju-core:
importance: Wishlist → Low
Revision history for this message
Dimiter Naydenov (dimitern) wrote :

I think we can close this now - juju status --format accepts a number of new output formats (in addition to the default "yaml" and optional "json"). Excerpt from juju status --help:

There are a number of ways to format the status output:

- {short|line|oneline}: List units and their subordinates. For each
           unit, the IP address and agent status are listed.
- summary: Displays the subnet(s) and port(s) the environment utilizes.
           Also displays aggregate information about:
           - MACHINES: total #, and # in each state.
           - UNITS: total #, and # in each state.
           - SERVICES: total #, and # exposed of each service.
- tabular: Displays information in a tabular format in these sections:
           - Machines: ID, STATE, VERSION, DNS, INS-ID, SERIES, HARDWARE
           - Services: NAME, EXPOSED, CHARM
           - Units: ID, STATE, VERSION, MACHINE, PORTS, PUBLIC-ADDRESS
             - Also displays subordinate units.
- yaml (DEFAULT): Displays information on machines, services, and units
                  in the yaml format.

Changed in juju-core:
status: Triaged → Fix Released
Changed in juju-core (Ubuntu):
status: Triaged → 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.