gistfile1.txt

I've been working on adding the container creation workflows to machine
view and came across several UX questions. Without further ado:

* The "submit" button for the machine/container creation form has
several labels in the visuals: "Move", "Create", and "Add" are all used,
depending on the context. "Move" is used when clicking on the icon in
the unplaced unit token. "Create" is used when creating a machine. "Add"
when creating a container. Would it be better to have that label change
depending on context, or remain consistent?

  + Use "create" except for moving unplaced tokens, which get "move"

* Also in that same form… in certain contexts (creating a machine)
there's a "Define constraints" label above the constraints inputs. In
other contexts (creating a KVM container) the label is missing. Should
we be consistent with including/excluding that label?

  + Be consistent - try using the label unless it causes problems somewhere

* Another consistency issue: in some places, the container type dropdown
is shown with "lxc" and "kvm", in other places it's "New LXC" and "New
KVM".

  + Go with 'lxc' and 'kvm'

* How do we want to handle the "Add container" link in the container
column? Right now it doesn't work unless there's a machine selected. I'd
recommend hiding it unless a machine is selected, though we could also
display a machine dropdown similar to the move unplaced token workflow.

  + Take up with design, but we're thinking show a 'Select machine' prompt
    in the column
  
* When you drop a unit on a machine, we display the create container form 
  and let them put it on a new KVM/LXC, but not on any existing containers 
  like bare metal.

  + On deployed machines, we can display existing containers + bare metal IF 
    there's already something on bare metal
  + On uncommitted machines, we can display bare metal always

#31 Change header to "Select a machine for details" or something in a kind of greyed out way like a placeholder text on an input field.

for the select options

1. machine is already deployed, we can only add containers
2. Machine is not yet deployed, but there's already a bare metal service, we can only create containers
3. Machine is not yet deployed and nothing is on bare metal, we can default the select box to the bare metal options for deployment.