Use upstream Music link

Updates references to upstream Music repo

.gitreview

@@ -0,0 +1,4 @@
+[gerrit]
+host=review.openstack.org
+port=29418
+project=openstack/valet.git

CONTRIBUTING.rst

@@ -0,0 +1,17 @@
+If you would like to contribute to the development of OpenStack, you must
+follow the steps in this page:
+
+   http://docs.openstack.org/infra/manual/developers.html
+
+If you already have a good understanding of how the system works and your
+OpenStack accounts are set up, you can skip to the development workflow
+section of this documentation to learn how changes to OpenStack should be
+submitted for review via the Gerrit tool:
+
+   http://docs.openstack.org/infra/manual/developers.html#development-workflow
+
+Pull requests submitted through GitHub will be ignored.
+
+Bugs should be filed on Launchpad, not GitHub:
+
+   https://bugs.launchpad.net/valet

HACKING.rst

@@ -0,0 +1,4 @@
+Valet Style Commandments
+========================
+
+Read the OpenStack Commandments http://docs.openstack.org/developer/hacking/

babel.cfg

@@ -0,0 +1 @@
+[python: **.py]

valet_plugins/README.md

@@ -14,9 +14,8 @@ Valet consists of the following components:
 * [valet-openstack](https://github.com/att-comdev/valet/blob/master/doc/valet_os.md): a set of OpenStack plugins used to interact with Valet
 * [valet-api](https://github.com/att-comdev/valet/blob/master/doc/valet_api.md): an API engine used to interact with Valet
 * [Ostro](https://github.com/att-comdev/valet/blob/master/doc/ostro.md): a placement optimization engine
-* Music: a data storage and persistence service
+* [Music](https://github.com/att/music): a data storage and persistence service
 * [ostro-listener](https://github.com/att-comdev/valet/blob/master/doc/ostro_listener.md): a message bus listener used in conjunction with Ostro and Music
-* [havalet](https://github.com/att-comdev/valet/blob/master/doc/ha.md): a service that assists in providing high availability for Valet
 
 Additional documents:
 

valet_plugins/RELEASE

@@ -12,9 +12,6 @@ Valet1.0/Ostro features
 - Resource standby
     When allocating resources (CPU, memory, disk, and later network bandwidth), Ostro intentionally leaves a certain percentage of resources as unused. This is because of the concern of load spikes of tenant applications. Later, we will deploy more dynamic mechanism in the future version of Ostro.
 
-- High availability
-    Ostro replicas run as active-passive way. When active Ostro fails, automatically the passive one is activated via HAValet. All data is updated in MUSIC database at runtime whenever it is changed. When the passive Ostro is activated, it gets data from MUSIC to initialize its status rather than from OpenStack. Ostro also takes ping messages to show if it is alive or not.
-
 - Runtime update via the Oslo message bus or RO
     Working on this.