Credenciais ausentes para funções na orquestração de calor no OpenStack?

1

Estou experimentando a orquestração de calor no OpenStack. Ao configurar uma única pilha de instâncias usando a configuração abaixo, estou recebendo este erro:

Error: ERROR: Missing required credential: roles [u'_member_']

Qual poderia ser o problema aqui?

Obrigado!

heat_template_version: 2013-05-23

description: Simple template to deploy a single compute instance

resources:
  my_instance:
    type: OS::Nova::Server
    properties:
      image: CentOS-6-x86_64-GenericCloud-2016-04-05
      flavor: c1-tiny
      key_name: mine
      networks:
        - network: private_network
    
por madtowneast 14.04.2016 / 23:03

1 resposta

0

o atributo membro denota um papel em projetos OpenStack, então este é um erro lançado por keystone, posso pensar em Duas possibilidades - o usuário que está invocando a pilha não tem um member role (Se você pode logar no horizonte você tem essa função) ou o usuário do domínio de calor e pilha não foi configurado, a partir dos pré-requisitos de instalação:

Orchestration requires additional information in the Identity service to manage stacks. To add this information, complete these steps:

Create the heat domain that contains projects and users for stacks:

$ openstack domain create --description "Stack projects and users" heat
+-------------+----------------------------------+
| Field       | Value                            |
+-------------+----------------------------------+
| description | Stack projects and users         |
| enabled     | True                             |
| id          | 0f4d1bd326f2454dacc72157ba328a47 |
| name        | heat                             |
+-------------+----------------------------------+
Create the heat_domain_admin user to manage projects and users in the heat domain:

$ openstack user create --domain heat --password-prompt heat_domain_admin
User Password:
Repeat User Password:
+-----------+----------------------------------+
| Field     | Value                            |
+-----------+----------------------------------+
| domain_id | 0f4d1bd326f2454dacc72157ba328a47 |
| enabled   | True                             |
| id        | b7bd1abfbcf64478b47a0f13cd4d970a |
| name      | heat_domain_admin                |
+-----------+----------------------------------+
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:

$ openstack role add --domain heat --user heat_domain_admin admin
 Note
This command provides no output.

Create the heat_stack_owner role:

$ openstack role create heat_stack_owner
+-------+----------------------------------+
| Field | Value                            |
+-------+----------------------------------+
| id    | 15e34f0c4fed4e68b3246275883c8630 |
| name  | heat_stack_owner                 |
+-------+----------------------------------+
Add the heat_stack_owner role to the demo project and user to enable stack management by the demo user:

$ openstack role add --project demo --user demo heat_stack_owner
 Note
This command provides no output.

 Note
You must add the heat_stack_owner role to each user that manages stacks.

Create the heat_stack_user role:

$ openstack role create heat_stack_user
+-------+----------------------------------+
| Field | Value                            |
+-------+----------------------------------+
| id    | 88849d41a55d4d1d91e4f11bffd8fc5c |
| name  | heat_stack_user                  |
+-------+----------------------------------+
 Note
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. 
    
por 15.04.2016 / 18:08

Tags