Server Manager & Heat Script Errors

Bug #1438898 reported by azaringh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenContrail
New
Wishlist
Abhay Joshi

Bug Description

It is well-known that Server Manager 2.1 fails to configure heat (1423876 Heat is not supported when provisioning with server manager.) However using the procedure below supplied by Bharat Putta it is possible to configure heat. While using this procedure I ran into two problems that point to Server Manager's initial tenant configuration and the installed heat.conf file.

• In heat-server-setup.sh, the tenant name used in “service”, whereas the installation creates the tenant “services”. This results in authentication failure.

keystone tenant-list
+----------------------------------+----------+---------+
| id | name | enabled |
+----------------------------------+----------+---------+
| 892db8ca1663474a93e81963f694b9d1 | admin | True |
| 577528dec2ea4dc4a1f1bcd26deafa3e | demo | True |
| 8ad48bf59ed543e4869b81c17dd3f86b | services | True |
| b1a60d8df4a942cbaa8493e7ffaa073a | test | True |
+----------------------------------+----------+---------+

• In the installed heat.conf, “rabbit_host” is not configured. This results in heat commands hanging forever.

Fixing these on top of of Bharat's procedure enables heat commands in my setup (a two-node/two-interface system). I found these problems after comparison with the corresponding files in a setup created with testbed files.

====================================================Bharat's Procedure============================

1.keystone user-create --name=heat --pass=contrail123 --<email address hidden>
2.keystone user-role-add --user=heat --tenant=service --role=admin
3. keystone service-create --name=heat --type=orchestration --description=“Orchestration"
4. keystone endpoint-create --service-id=$(keystone service-list | awk '/ orchestration / {print $2}') --publicurl=http://10.204.221.3:8004/v1/%\(tenant_id\)s --internalurl=http://controller:8004/v1/%\(tenant_id\)s --adminurl=http://controller:8004/v1/%\(tenant_id\)s
5. keystone service-create --name=heat-cfn --type=cloudformation --description="Orchestration CloudFormation"
6. keystone endpoint-create --service-id=$(keystone service-list | awk '/ cloudformation / {print $2}') --publicurl=http://10.204.221.3:8000/v1 --internalurl=http://controller:8000/v1 --adminurl=http://controller:8000/v1

7. Run heat-server-setup.sh
8. Need to add apiserver under clients_contrail section in /etc/heat/heat.conf
[clients_contrail]
user = admin
password = contrail123
tenant = admin
api_server = 10.204.221.3 <<<<<<<< Added explicitly
api_base_url = /

9. Re-booted the server.
================================================================================================

Changed in opencontrail:
importance: Undecided → Medium
assignee: nobody → Abhay Joshi (abhayj)
tags: added: server-manager
Revision history for this message
Abhay Joshi (abhayj) wrote :

Will be considered when we implement Heat provisioning using SM.

Changed in opencontrail:
importance: Medium → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.