Guest User

Untitled

a guest
Jan 30th, 2018
344
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.02 KB | None | 0 0
  1. heat_template_version: 2013-05-23
  2.  
  3. description: Simple template to deploy a single compute instance
  4.  
  5. resources:
  6. my_instance:
  7. type: OS::Nova::Server
  8. properties:
  9. image: CentOS-6-x86_64-GenericCloud-2016-04-05
  10. flavor: c1-tiny
  11. key_name: mine
  12. networks:
  13. - network: private_network
  14.  
  15. Orchestration requires additional information in the Identity service to manage stacks. To add this information, complete these steps:
  16.  
  17. Create the heat domain that contains projects and users for stacks:
  18.  
  19. $ openstack domain create --description "Stack projects and users" heat
  20. +-------------+----------------------------------+
  21. | Field | Value |
  22. +-------------+----------------------------------+
  23. | description | Stack projects and users |
  24. | enabled | True |
  25. | id | 0f4d1bd326f2454dacc72157ba328a47 |
  26. | name | heat |
  27. +-------------+----------------------------------+
  28. Create the heat_domain_admin user to manage projects and users in the heat domain:
  29.  
  30. $ openstack user create --domain heat --password-prompt heat_domain_admin
  31. User Password:
  32. Repeat User Password:
  33. +-----------+----------------------------------+
  34. | Field | Value |
  35. +-----------+----------------------------------+
  36. | domain_id | 0f4d1bd326f2454dacc72157ba328a47 |
  37. | enabled | True |
  38. | id | b7bd1abfbcf64478b47a0f13cd4d970a |
  39. | name | heat_domain_admin |
  40. +-----------+----------------------------------+
  41. Add the admin role to the heat_domain_admin user in the heat domain to enable administrative stack management privileges by the heat_domain_admin user:
  42.  
  43. $ openstack role add --domain heat --user heat_domain_admin admin
  44. Note
  45. This command provides no output.
  46.  
  47. Create the heat_stack_owner role:
  48.  
  49. $ openstack role create heat_stack_owner
  50. +-------+----------------------------------+
  51. | Field | Value |
  52. +-------+----------------------------------+
  53. | id | 15e34f0c4fed4e68b3246275883c8630 |
  54. | name | heat_stack_owner |
  55. +-------+----------------------------------+
  56. Add the heat_stack_owner role to the demo project and user to enable stack management by the demo user:
  57.  
  58. $ openstack role add --project demo --user demo heat_stack_owner
  59. Note
  60. This command provides no output.
  61.  
  62. Note
  63. You must add the heat_stack_owner role to each user that manages stacks.
  64.  
  65. Create the heat_stack_user role:
  66.  
  67. $ openstack role create heat_stack_user
  68. +-------+----------------------------------+
  69. | Field | Value |
  70. +-------+----------------------------------+
  71. | id | 88849d41a55d4d1d91e4f11bffd8fc5c |
  72. | name | heat_stack_user |
  73. +-------+----------------------------------+
  74. Note
  75. The Orchestration service automatically assigns the heat_stack_user role to users that it creates during stack deployment. By default, this role restricts API operations. To avoid conflicts, do not add this role to users with the heat_stack_owner role.
Add Comment
Please, Sign In to add comment