Inspector relations tab now shows the units involved in the relation error
Add vagrant for development on other OSes

* Add Vagrantfile for specifying box and networking
* Add vagrant-provision.sh for fleshing out the VM
* Add info on vagrant to HACKING
* Add .vagrant to .gitignore
Remove killing xvfb since it can be shared.
Added unit tests for relation methods in the relation viewlet
Merge pull request #42 from mitechie/test-merge-singularity

- Currently if a test and a merge (landing) job are running on Jenkins they interfere and will not pass due to no fault of the dev.
- This is due to one of them killing the xvfb process running while the other is sharing it.
- After a pre-imp with Benji it was decided there's no harm in leaving it running currently and it's the most expedient way to getting a safer CI process into place. 

Notes:

We may want to revisit this, as noted in the docs in line, if we want to do things like snapshot images in case of a failing test, etc. We can then make the xvfb port configurable as part of that work.

QA
-----

Note that below we have failed test and merge runs. I've updated the branch to remove the failing test and it's ready for review.
Added additional comments for clarity
Merge pull request #43 from hatched/relation-unit-errors

This branch adds the units in error to the relation tab in the inspector. There are only unit tests because the timings are unreliable for a purely js test and would require a settimeout/polling. It would be better tested using selenium.

To QA:
deploy mysql & wordpress
relate them
scale one to 100 units with the simulator on and then switch to the relations tab
once there is a unit in relation error it will show up in the list.
scale it down to 1 unit and switch back to the relations tab quickly you should notice it dissappear.
Update the ci docs with the new process and setup
Merge pull request #44 from mitechie/ci-docs-update

This is a pure docs update with the goal of helping other devs be able to walk into the CI system and find their way around. It provides some debugging tips and descriptions of the moving parts.

I've left the older instructions and noted them as bitrotten per the old Hacking docs. Those notes deal with starting up and dealing with a live Juju environment which CI does not use. Those notes might prove useful in bringing that back up at some point in the future.
Tests now run in vagrant; docs updated per reviews.
Added util for rendering viewlets and added service-relation viewlet tests
Added missing dependency in viewlet relations module
Merge pull request #41 from makyo/vagrant

* Add Vagrantfile for specifying box and networking
* Add vagrant-provision.sh for fleshing out the VM
* Add info on vagrant to HACKING
* Add .vagrant to .gitignore
Merge pull request #45 from hatched/viewlet-test-scaffold
Fix the test port and ENV var usage.
Make all the PORT TEST_PORT
Merge pull request #46 from mitechie/one-test-port

Set the test port to 8888 unless overridden by the TEST_PORT variable. 

- Add a doc on using the override (currently only used by CI)
- Fix the issue I introduced using $(PORT) which tosses cli noise.
Create a new factory.js for test utils.

- Move the existing methods over to it and refactor all the things.
- Drive by to sort and cleanup.
- Remove the circular import between utils/factory and update calls to always
pass the fake backend.
Merge pull request #47 from mitechie/factory-time

- Move the existing methods over to it and refactor all the things.
- Drive by to sort and cleanup.
- Remove the circular import between utils/factory and update calls to always
pass the fake backend.

QA
------
It's a very mechanical change. Tests should pass. No tests were added or removed in the making of this pull request.
Add docs for using Floobits and Vim