Don't create machines that don't exist.
Lint cleanup.
Remove testing cruft.
Restrict the result set of the search autocomplete results to:
Precise and above charms. Oneiric is well past EOL and many Oneiric charms do not meet our current standards.
Only a single most relevant charm to the user per name ex) only one mysql charm, closest matching series and recommended status.
Any others up to 5, including bundles appended to the end after the above filters.
Fixed test to match new autocomplete result lists
            ECS reflects changes to the ghost service name.

            When changing the name of a ghost service, the ECS
            records are properly updated, so that when changes
            are committed the resulting service is given the desired
            name.

            This also includes ghost unit names.

            QA:
            Use the mv flag.
            Drag a service and click commit: the service and its
            unit should be deployed as usual.
            Now drag a new service, and use the inspector to rename it.
            Open and close the service inspectore multiple times to ensure
            the inspectore reflects the new service name.
            Open the deployer panel to show the changes: both the service and
            the unit have the correct customized name.
            Switch to the machine view and check the service units is also
            renamed.
            Commit the changes: the deployment summary shows the proper names.
            When the ghost is deployed, the resulting service should
            have the desired name.
Merge pull request #469 from frankban/rename-ghost-service

ECS reflects changes to the ghost service name.

       When changing the name of a ghost service, the ECS
        records are properly updated, so that when changes
        are committed the resulting service is given the desired
        name.

        This also includes ghost unit names.

        QA:
        Use the mv flag.
        Drag a service and click commit: the service and its
        unit should be deployed as usual.
        Now drag a new service, and use the inspector to rename it.
        Open and close the service inspectore multiple times to ensure
        the inspectore reflects the new service name.
        Open the deployer panel to show the changes: both the service and
        the unit have the correct customized name.
        Switch to the machine view and check the service units is also
        renamed.
        Commit the changes: the deployment summary shows the proper names.
        When the ghost is deployed, the resulting service should
        have the desired name.
Merge pull request #472 from hatched/ac-result-filter-1348290

Fixes the search autocomplete result list - Fixes 1348290

Restrict the result set of the search autocomplete results to:
- Precise and above charms. Oneiric is well past EOL and many Oneiric charms do not meet our current standards.
- Only a single most relevant charm to the user per name ex) only one mysql charm, closest matching series and recommended status.
- Any others up to 5, including bundles appended to the end after the above filters.

The real search results are untouched.
Make it clear when a machine is a state server.
Merge pull request #471 from kadams54/services-without-machines

Don't create machines that don't exist.

**QA:**

This must be done in a real environment, in machine view.

1. Create a new machine by clicking on the "Add machine" link in the header.
2. Select a charm in the charmbrowser and click on the "Add to canvas" button. You should see a unit show up in the unplaced units column.
3. Select the newly created machine (still undeployed) so that the bare metal container is visible.
4. Drag and drop the unplaced unit on the bare metal container.
5. Deploy everything and wait a few seconds. You should get an error message (due to another bug).
6. The machine view should re-render with the unit back as an unplaced unit. The newly-created machine should now be deployed, but with nothing on it. There should *only* be one machine created. Before fixing this bug, two machines would show up in the column, one with no ID and showing the unit as being deployed, like so: http://cl.ly/image/0y2o032x2v1Z
Merge pull request #473 from frankban/state-server-machine

Make it clear when a machine is a state server.

Also simplified the machine token tests.

QA:
In sandbox mode, no change should be observed.
Using a real environment, the bootstrap node should
be displayed as "0 - State service".