Public bug reported:
>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)
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: apport-bug cli-ui i386 saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1183129
Title:
'juju status' difficult to read and provides unneccessary information
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183129/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
