Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

fleetctl list-units does not expose necessary data #663

Closed
bcwaldon opened this issue Jul 14, 2014 · 0 comments
Closed

fleetctl list-units does not expose necessary data #663

bcwaldon opened this issue Jul 14, 2014 · 0 comments
Assignees
@bcwaldon
Labels
priority/P1
Milestone
v0.6.0

Comments

@bcwaldon
Copy link
Contributor

I've deployed a single unit foo.service on v0.5.3:

$ fleetctl list-units
UNIT        STATE       LOAD    ACTIVE  SUB DESC    MACHINE
foo.service launched    loaded  active  running -   5849e100.../172.17.8.101

This does not expose two necessary pieces of information: the target machine and the desired state. This is important to expose for debuggability and management of the system:

  1. The desired state vs the last known state is used to drive changes in the cluster
  2. Given Scope unit state by machine #638, the exposed state might actually be incorrect.
@bcwaldon bcwaldon added feature and removed feature labels Jul 14, 2014
@bcwaldon bcwaldon added this to the v0.6.0 milestone Jul 14, 2014
@bcwaldon bcwaldon self-assigned this Jul 14, 2014
bcwaldon added a commit to bcwaldon/fleet that referenced this issue Jul 14, 2014
@bcwaldon
fleetctl: add tstate and tmachine list-units fields
c646703 
Fix coreos#663
bcwaldon added a commit to bcwaldon/fleet that referenced this issue Jul 14, 2014
@bcwaldon
fleetctl: add dstate and tmachine list-units fields
c2394fa 
Fix coreos#663
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bcwaldon bcwaldon

Labels
priority/P1
Projects
None yet
Milestone
v0.6.0
Development

No branches or pull requests
1 participant
@bcwaldon