Pushing passwords into mysql and other fixes.
authorClint Byrum <clint@fewbar.com>
Thu, 16 May 2013 23:10:20 +0000 (16:10 -0700)
committerClint Byrum <clint@fewbar.com>
Thu, 6 Jun 2013 16:36:07 +0000 (09:36 -0700)
Generating and distributing usernames/passwords is just too complicated
with Heat at this stage, so we need to push them into mysql from the
template.

notcompute.yaml

index f63307d..3579760 100644 (file)
@@ -93,6 +93,23 @@ Resources:
         Ref: ServicePassword
       admin-token:
         Ref: AdminToken
+      mysql:
+        create-users:
+          - database: keystone
+            username: keystone
+            password: {Ref: KeystoneDBPassword}
+          - database: heat
+            username: heat
+            password: {Ref: HeatDBPassword}
+          - database: glance
+            username: glance
+            password: {Ref: GlanceDBPassword}
+          - database: nova
+            username: nova
+            password: {Ref: NovaDBPassword}
+          - database: quantum
+            username: quantum
+            password: {Ref: QuantumDBPassword}
       glance:
         db:
           Fn::Join:
@@ -120,12 +137,13 @@ Resources:
             Ref: AWS::StackName
           region:
             Ref: AWS::Region
+        auth_encryption_key: unset
       interfaces:
         control:
           Ref: NovaInterfaces
       keystone:
         host:
-          Fn::GetAtt: [ notocmpute, PrivateIp ]
+          Fn::GetAtt: [ notcompute, PrivateIp ]
         db:
           Fn::Join:
             - ''
@@ -153,6 +171,10 @@ Resources:
           Fn::GetAtt: [ notcompute , PrivateIp ]
         password:
           Ref: RabbitPassword
+        users:
+          username: guest
+          password:
+            Ref: RabbitPassword
       service-password:
         Ref: ServicePassword
     Properties: