Re: [Openstack] [HEAT] order in attributes list

[Pavlo Shchelokovskyy]

Hi,

AFAIU the get_attr function does not use the values you've passed to Heat
in the resource definition, instead it fetches their actual values from
Neutron (basically making a 'port show' API call), and Heat does nothing
wrt to ordering afterwards.

Btw AFAIR this is exactly why heat requires a separate network with single
IPv4 subnet during tempest tests - the default network created by devstack
at some point started to have both IPv4 and IPv6 subnets, and there's no
way I know of to get specifically the IPv4 address using get_attr.

OTOH may be some newer Heat template features like map filters,
conditionals and yaql expressions could possibly be utilized for that..
need to investigate :-)

Cheers,

On Tue, Apr 3, 2018 at 6:10 PM, Volodymyr Litovka  wrote:

> Hi colleagues,
>
> I have the following HOT configuration of a port:
>
>   n1-wan:
> type: OS::Neutron::Port
> properties:
>   fixed_ips:
> - { subnet: e-subnet1, ip_address: 51.x.x.x }
> - { subnet: e-subnet2, ip_address: 25.x.x.x }
>
> when I try to extract these values in template using {get_attr}, then,
> regardless of fixed_ips' order in port definition (either "subnet1,
> subnet2" or "subnet2, subnet1"), the value of { get_attr: [n1-wan,
> fixed_ips] } always give the following result:
>
> output_value:
>- ip_address: 25.x.x.x
>   subnet_id: ...
>- ip_address: 51.x.x.x
>  subnet_id: ...
>
> and, thus, { get_attr: [n1-wan, fixed_ips, 1, ip_address ] } gives me
> 51.x.x.x value.
>
> So, the question is - how the list of fixed_ips is ordered? Is there way
> to know for sure index of entry I'm interested in?
>
> Thank you.
>
> --
> Volodymyr Litovka
>   "Vision without Execution is Hallucination." -- Thomas Edison
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>



-- 
Dr. Pavlo Shchelokovskyy
Senior Software Engineer
Mirantis Inc
www.mirantis.com
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [HEAT] order in attributes list

[Volodymyr Litovka]

Hi colleagues,

I have the following HOT configuration of a port:

  n1-wan:
    type: OS::Neutron::Port
    properties:
  fixed_ips:
    - { subnet: e-subnet1, ip_address: 51.x.x.x }
    - { subnet: e-subnet2, ip_address: 25.x.x.x }

when I try to extract these values in template using {get_attr}, then, 
regardless of fixed_ips' order in port definition (either "subnet1, 
subnet2" or "subnet2, subnet1"), the value of { get_attr: [n1-wan, 
fixed_ips] } always give the following result:


output_value:
   - ip_address: 25.x.x.x
      subnet_id: ...
   - ip_address: 51.x.x.x
 subnet_id: ...

and, thus, { get_attr: [n1-wan, fixed_ips, 1, ip_address ] } gives me 
51.x.x.x value.


So, the question is - how the list of fixed_ips is ordered? Is there way 
to know for sure index of entry I'm interested in?


Thank you.

--
Volodymyr Litovka
  "Vision without Execution is Hallucination." -- Thomas Edison


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat] AutoScalingGroup and dependents

[Zane Bitter]

On 19/11/17 11:27, Lars-Erik Helander wrote:

I am using OS::Heat::AutoScalingGroup in the following type of scenario

resources:

    my_vm:

   type: SOME_TEMPLATE_WITH_A_VM_CONNECTED_TO_MULTIPLE_NETWORKS

   properties:

 networks: { get_attr: [my_networks, outputs_list, my_network] }

    my_networks:

  type: OS::Heat::AutoScalingGroup

      properties:

     resource:

    type: 
SOME_TEMPLATE_WITH_A_NETWORK_ATTRIBUTE_my_network_HOLDS_NETWORK_ID


When I deploy my stack everything works as expected. When I trigger 
(using a ScalingPolicy and its alarm_url) the my_networks group scales 
as expected.


Now I want the my_vm resource to adjust to the new state (re-evaluation 
of { get_attr: [my_networks, outputs_list, my_network] } ).


Can this be done ?


It won't be updated until the parent stack is updated. (You can update 
it using the --existing option to not change the 
template/environment/parameters.)


The old AWS Autoscaling resource has a hard-coded hack for updating a 
loadbalancer after each scaling operation. We never did think of a tidy 
mechanism for exposing something similar to the template author in a 
flexible way.


cheers,
Zane.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [heat] AutoScalingGroup and dependents

[Lars-Erik Helander]

I am using OS::Heat::AutoScalingGroup in the following type of scenario

resources:
   my_vm:
  type: SOME_TEMPLATE_WITH_A_VM_CONNECTED_TO_MULTIPLE_NETWORKS
  properties:
networks: { get_attr: [my_networks, outputs_list, my_network] }

   my_networks:
 type: OS::Heat::AutoScalingGroup
 properties:
resource:
   type: 
SOME_TEMPLATE_WITH_A_NETWORK_ATTRIBUTE_my_network_HOLDS_NETWORK_ID

When I deploy my stack everything works as expected. When I trigger (using a 
ScalingPolicy and its alarm_url) the my_networks group scales as expected.
Now I want the my_vm resource to adjust to the new state (re-evaluation of { 
get_attr: [my_networks, outputs_list, my_network] } ).

Can this be done ?

/Lars
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] heat resume Vms and run from SNAPSHOT

[Charls D. Chap]

heat resume Vms and run from SNAPSHOT:
I have a stack of VMs (nova servers). The commands i execute are the following:
 openstack stack create
 openstack stack suspend
 openstack stack snapshot create

At this point stack_state is in status SNAPSHOT_COMPLETED
and vms_state is in status SUSPENDED
How can i resume stack, with VMs be active and in Running state,
LAUNCING the SNAPSHOTTED image.

I can't resume the stack, because the VMs are in SNAPSHOTTED state.
How Heat deals with it?
How can you resume a stack with status SNAPSHOT_COMPLETED and VMs suspended
to vm_state = unning for all the VMs of the stack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack-hpc] openstack heat multi tenant scenario

[Charls D. Chap]

I could't have a stack with the SAME name "mystack" for different tenants,
and i did specify OS_PROJECT_NAME.

It prompts error message, that stack with the same name already exists...


On Tue, Oct 10, 2017 at 6:51 PM, Fox, Kevin M  wrote:
> A heat stack belongs to one tenant. It works as you describe below.
>
> You just have to specify which tenant to run which command under. like:
> OS_PROJECT_NAME=TenantA openstack stack create "mystack"
> OS_PROJECT_NAME=TenantB openstack stack create "mystack"
>
> Thanks,
> Kevin
> 
> From: Charls D. Chap [chapcha...@gmail.com]
> Sent: Tuesday, October 10, 2017 5:17 AM
> To: openstack-...@lists.openstack.org; openstack@lists.openstack.org
> Subject: [openstack-hpc] openstack heat multi tenant scenario
>
> Scenario:
> -DomainA (TenantA, TenantB)
> -TenantA(userA)
> -TenantB(userB)
> - A template which start OS:NOVA:SERVERS
>
> 1. Is it possible two run simultaneously the same openstack stack
> create command?
> 2.
> a. how can i specify that i want, in the first case, the VMs of the
> stack, beloging to TenantA
> and in the second case to TenantB
> b. for the OS::NOVA::SERVER as fas as i can see there is no such
> property to Distinguish project names
>
> c. I want to achieve something like this
> openstack stack create "mystack" for TenantA
> openstack stack create "mystack" for TenantB
>  openstack server list for TenantA
> VM1 RUNNING
> VM2 RUNNING
> 
> openstack server list for TenantB
> VM1 RUNNING
> VM2 RUNNING
> 
>
> So THE SAME VMs for both Tenants!
>
> 3. In the end, how is multi-tenancy achieved?
> So far, I have achieved it, by having two different stack names,
> tenantA and tenantB correspondingly, which take as input the same template,
> with the same parameters.
>
> ___
> OpenStack-HPC mailing list
> openstack-...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-hpc

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] openstack heat multi tenant scenario

[Charls D. Chap]

Scenario:
-DomainA (TenantA, TenantB)
-TenantA(userA)
-TenantB(userB)
- A template which start OS:NOVA:SERVERS

1. Is it possible two run simultaneously the same openstack stack
create command?
2.
a. how can i specify that i want, in the first case, the VMs of the
stack, beloging to TenantA
and in the second case to TenantB
b. for the OS::NOVA::SERVER as fas as i can see there is no such
property to Distinguish project names

c. I want to achieve something like this
openstack stack create "mystack" for TenantA
openstack stack create "mystack" for TenantB
 openstack server list for TenantA
VM1 RUNNING
VM2 RUNNING

openstack server list for TenantB
VM1 RUNNING
VM2 RUNNING


So THE SAME VMs for both Tenants!

3. In the end, how is multi-tenancy achieved?
So far, I have achieved it, by having two different stack names,
tenantA and tenantB correspondingly, which take as input the same template,
with the same parameters.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat] Using value_specs

[Zane Bitter]

On 08/09/17 04:48, Lars-Erik Helander wrote:
A number of resource types supports a ”value_specs” property. I have 
problem finding out valid vales for this property. I have tried various 
map values but whatever I try I get the message that the value is not 
allowed.


How to find out the possible value sets?


AFAIK they're just passed directly to the underlying clients, so the way 
to find out would be to look at the documentation of the relevant client 
library.


cheers,
Zane.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [heat] default collectors

[Volodymyr Litovka]

Hi colleagues,

when deploying VMs using Heat, os-collect-config automatically 
configured for three collectors: heat, ec2 and local.


While I don't need for sure ec2, there is corresponding bug 
https://bugs.launchpad.net/tripleo/+bug/1669842 which suggests to remove 
unconditional adding of this collector to the list.


What is 'local' collector needed for? There are lot of error messages 
every 30 seconds in syslog:


Sep 13 11:39:12 vm os-collect-config[1570]: No local metadata found 
(['/var/lib/os-collect-config/local-data'])
Sep 13 11:39:42 vm os-collect-config[1570]: 
/var/lib/os-collect-config/local-data not found. Skipping


which impacts nothing except I understand that every 30 seconds process 
tries to access this data. According to source code, it also added 
unconditionally to the end of the list like this code:


collectors = ['ec2']
if heat then collectors.append('heat')
if zaqar then collectors.append('zaqar')
if cfn then collectors.append('cfn')
[ ... ]
collectors.append('local')

Is it safe to remove it from code as well as proposed in bug above?

Thank you.

--
Volodymyr Litovka
  "Vision without Execution is Hallucination." -- Thomas Edison

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [heat]

[Lars-Erik Helander]

I am trying to create a deployment scenario with the following characteristics:

-  Controllable via the Horizon Heat UI

-  Uses nested resource types


The only way I have been able to do this is to create an external server where 
all nested templates are stored and either reference the nested templates via 
explicit URLs in the nesting template or in an environment file.

Could this be done without the need for an external server ?

/Lars
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [heat] Using value_specs

[Lars-Erik Helander]

A number of resource types supports a ”value_specs” property. I have problem 
finding out valid vales for this property. I have tried various map values but 
whatever I try I get the message that the value is not allowed.
How to find out the possible value sets?

/Lars
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat][Designate] Struggling to create DNS records for created instances

[Kaz Shinohara]

Hi Lance,


Good to hear, you could find the cause :)

Regards,
Kaz


2017-07-24 16:12 GMT+09:00 Lance Haig :
> Hi Kaz,
>
> Thanks for responding.
>
> I found my mistake the Designate Resource requires that the name provided be
> a FQDN
>
> I was just passing in the name.
>
> I should look like this
>
> instance_record:
> type: OS::Designate::Record
> properties:
>   data: { get_attr: [ instance, first_address ] }
>   description: { get_attr: [instance, name] }
>   domain: { get_param: dns_zone }
>   name: { list_join: ['.', [{ get_attr: [instance, name] }, { get_param:
> dns_zone }]] }
>   type: "A"
>
> Thanks
>
> Lance
>
>
> On 22.07.17 07:46, Kaz Shinohara wrote:
>
> Hi Lance,
>
> Just a quick question, have you tried "depends_on" ?
> Also looks the error what you got indicates your posted properties for
> "instance_record" includes not supported one.
>
> Regards,
> Kaz
>
>
> On Jul 22, 2017 1:19 AM, "Lance Haig"  wrote:
>
> Hi,
>
>
> I have the following instance code
>
> server1:
>   type: OS::Nova::Server
>   properties:
> name: Server1
> image: { get_param: image }
> flavor: { get_param: flavor }
> key_name: { get_param: key_name }
> networks:
>   - port: { get_resource: server1_port }
>
>
> and I am trying to create a DNS record from the output of the Instance.
>
>   instance_record:
> type: OS::Designate::Record
> properties:
>   data: { get_attr: [ instance, first_address ] }
>   description: { get_attr: [instance, name] }
>   domain: { get_param: dns_zone }
>   name: { get_attr: [instance, name] }
>   type: "A"
>
> For some reason it is giving me an error
>
> resources.instance_stack: Went to status CREATE_FAILED due to "BadRequest:
> resources.instance_record: Provided object does not match schema"
>
> Is it possible to use the output from Nova Server to populate the DNS
> record?
>
>
> Regards
>
> Lance
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat][Designate] Struggling to create DNS records for created instances

[Lance Haig]

Hi Kaz,

Thanks for responding.

I found my mistake the Designate Resource requires that the name 
provided be a FQDN


I was just passing in the name.

I should look like this

instance_record:
type: OS::Designate::Record
properties:
  data: { get_attr: [ instance, first_address ] }
  description: { get_attr: [instance, name] }
  domain: { get_param: dns_zone }
  name: { list_join: ['.', [{ get_attr: [instance, name] }, { 
get_param: dns_zone }]] }

  type: "A"

Thanks

Lance

On 22.07.17 07:46, Kaz Shinohara wrote:

Hi Lance,

Just a quick question, have you tried "depends_on" ?
Also looks the error what you got indicates your posted properties for 
"instance_record" includes not supported one.


Regards,
Kaz


On Jul 22, 2017 1:19 AM, "Lance Haig" > wrote:


Hi,


I have the following instance code

server1:
  type: OS::Nova::Server
  properties:
name: Server1
image: { get_param: image }
flavor: { get_param: flavor }
key_name: { get_param: key_name }
networks:
  - port: { get_resource: server1_port }


and I am trying to create a DNS record from the output of the
Instance.

  instance_record:
type: OS::Designate::Record
properties:
  data: { get_attr: [ instance, first_address ] }
  description: { get_attr: [instance, name] }
  domain: { get_param: dns_zone }
  name: { get_attr: [instance, name] }
  type: "A"

For some reason it is giving me an error

resources.instance_stack: Went to status CREATE_FAILED due to
"BadRequest: resources.instance_record: Provided object does not
match schema"

Is it possible to use the output from Nova Server to populate the
DNS record?


Regards

Lance


___
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Post to : openstack@lists.openstack.org

Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack





___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat][Designate] Struggling to create DNS records for created instances

[Kaz Shinohara]

Hi Lance,

Just a quick question, have you tried "depends_on" ?
Also looks the error what you got indicates your posted properties for
"instance_record" includes not supported one.

Regards,
Kaz


On Jul 22, 2017 1:19 AM, "Lance Haig"  wrote:

Hi,


I have the following instance code

server1:
  type: OS::Nova::Server
  properties:
name: Server1
image: { get_param: image }
flavor: { get_param: flavor }
key_name: { get_param: key_name }
networks:
  - port: { get_resource: server1_port }


and I am trying to create a DNS record from the output of the Instance.

  instance_record:
type: OS::Designate::Record
properties:
  data: { get_attr: [ instance, first_address ] }
  description: { get_attr: [instance, name] }
  domain: { get_param: dns_zone }
  name: { get_attr: [instance, name] }
  type: "A"

For some reason it is giving me an error

resources.instance_stack: Went to status CREATE_FAILED due to "BadRequest:
resources.instance_record: Provided object does not match schema"

Is it possible to use the output from Nova Server to populate the DNS
record?


Regards

Lance


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [heat][Designate] Struggling to create DNS records for created instances

[Lance Haig]

Hi,


I have the following instance code

server1:
  type: OS::Nova::Server
  properties:
name: Server1
image: { get_param: image }
flavor: { get_param: flavor }
key_name: { get_param: key_name }
networks:
  - port: { get_resource: server1_port }


and I am trying to create a DNS record from the output of the Instance.

  instance_record:
type: OS::Designate::Record
properties:
  data: { get_attr: [ instance, first_address ] }
  description: { get_attr: [instance, name] }
  domain: { get_param: dns_zone }
  name: { get_attr: [instance, name] }
  type: "A"

For some reason it is giving me an error

resources.instance_stack: Went to status CREATE_FAILED due to 
"BadRequest: resources.instance_record: Provided object does not match 
schema"


Is it possible to use the output from Nova Server to populate the DNS 
record?



Regards

Lance


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack Heat/Orchestration Service - 500 Internal Server Error

[Mohit Taneja]

Not sure that whether I have resolved the problem completely or not, but
now its working with the following changes in heat.conf file:

#[profiler]
#profiler_enabled = True
#trace_sqlalchemy = True

Just commented the above and restarted the service and now its working. If
there is any suggestion or any other input/advice in general then please
drop me an email.

Thanks & Regards,
Mohit

On 27 June 2017 at 14:16, Mohit Taneja  wrote:

>
>
> -- Forwarded message --
> From: MOHIT TANEJA 
> Date: Tue, Jun 27, 2017 at 11:34 AM
> Subject: Openstack Heat/Orchestration Service - 500 Internal Server Error
> To: ochupry...@mirantis.com, skray...@mirantis.com, mkr1...@gmail.com
>
>
> Hi,
>
> When I try to orchestrate (create stack) using heat template I get the
> following error:
>
> *Commands:*
>
> *To Create Stack:*
>
> $> openstack stack create -t  -e  STACKNAME
>
>
>
>
> *To Check Stack list:*
> $>openstack stack list
>
> /*Both command after sourcing the shell file*/
>
> *Error that I receive:*
>
> ubuntu@mohitfogcloud:~$ openstack stack list
> ERROR: 
> 
> 500 Internal Server Error
> 
> Internal Server Error
> The server encountered an internal error or
> misconfiguration and was unable to complete
> your request.
> Please contact the server administrator at
>  [no address given] to inform them of the time this error occurred,
>  and the actions you performed just before this error.
> More information about this error may be available
> in the server error log.
> 
> Apache/2.4.18 (Ubuntu) Server at 192.168.1.126 Port 8004
> 
>
> ​
> *heat_api.log shows the following:*
>
> 2017-06-27 12:37:58.884717 mod_wsgi (pid=2139): Target WSGI script
> '/usr/local/bin/heat-wsgi-api' cannot be loaded as Python module.
> 2017-06-27 12:37:58.884737 mod_wsgi (pid=2139): Exception occurred
> processing WSGI script '/usr/local/bin/heat-wsgi-api'.
> 2017-06-27 12:37:58.884754 Traceback (most recent call last):
> 2017-06-27 12:37:58.884770   File "/usr/local/bin/heat-wsgi-api", line
> 54, in 
> 2017-06-27 12:37:58.884814 application = init_application()
> 2017-06-27 12:37:58.884825   File "/opt/stack/heat/heat/httpd/heat_api.py",
> line 36, in init_application
> 2017-06-27 12:37:58.884852 logging.register_options(cfg.CONF)
> 2017-06-27 12:37:58.884861   File 
> "/usr/local/lib/python2.7/dist-packages/oslo_log/log.py",
> line 250, in register_options
> 2017-06-27 12:37:58.884874 conf.register_cli_opts(_option
> s.common_cli_opts)
> 2017-06-27 12:37:58.884882   File 
> "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py",
> line 2329, in __inner
> 2017-06-27 12:37:58.884895 result = f(self, *args, **kwargs)
> 2017-06-27 12:37:58.884902   File 
> "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py",
> line 2551, in register_cli_opts
> 2017-06-27 12:37:58.884913 self.register_cli_opt(opt, group,
> clear_cache=False)
> 2017-06-27 12:37:58.884932   File 
> "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py",
> line 2333, in __inner
> 2017-06-27 12:37:58.884943 return f(self, *args, **kwargs)
> 2017-06-27 12:37:58.884949   File 
> "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py",
> line 2543, in register_cli_opt
> 2017-06-27 12:37:58.884960 raise ArgsAlreadyParsedError("cannot
> register CLI option")
> 2017-06-27 12:37:58.884977 ArgsAlreadyParsedError: arguments already
> parsed: cannot register CLI option
>
>
> I checked that it was a bug initially which was fixed in openstac/heat
> 6.0.0.0b1. I referred to the following links:
>
> https://bugs.launchpad.net/heat/+bug/1500807
>
> https://review.openstack.org/gitweb?p=openstack/heat.git;a=c
> ommitdiff;h=a1b3c23ff856ed2574a1ab50ba854f6a79b3213e#patch1
>
> https://git.openstack.org/cgit/openstack/heat/diff/?id=a1b3c
> 23ff856ed2574a1ab50ba854f6a79b3213e
>
>
> I am using latest version of heat and everything seems to be as desired as
> per the links above, but I am still getting the error as mentioned.
>
> I please request you to help me out here to fix this issue.
>
> Eagerly waiting for your response!
>
> Thanking you in anticipation!
>
> Best Regards,
> Mohit
>
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Fwd: Openstack Heat/Orchestration Service - 500 Internal Server Error

[Mohit Taneja]

-- Forwarded message --
From: MOHIT TANEJA 
Date: Tue, Jun 27, 2017 at 11:34 AM
Subject: Openstack Heat/Orchestration Service - 500 Internal Server Error
To: ochupry...@mirantis.com, skray...@mirantis.com, mkr1...@gmail.com


Hi,

When I try to orchestrate (create stack) using heat template I get the
following error:

*Commands:*

*To Create Stack:*

$> openstack stack create -t  -e  STACKNAME




*To Check Stack list:*
$>openstack stack list

/*Both command after sourcing the shell file*/

*Error that I receive:*

ubuntu@mohitfogcloud:~$ openstack stack list
ERROR: 

500 Internal Server Error

Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator at
 [no address given] to inform them of the time this error occurred,
 and the actions you performed just before this error.
More information about this error may be available
in the server error log.

Apache/2.4.18 (Ubuntu) Server at 192.168.1.126 Port 8004


​
*heat_api.log shows the following:*

2017-06-27 12:37:58.884717 mod_wsgi (pid=2139): Target WSGI script
'/usr/local/bin/heat-wsgi-api' cannot be loaded as Python module.
2017-06-27 12:37:58.884737 mod_wsgi (pid=2139): Exception occurred
processing WSGI script '/usr/local/bin/heat-wsgi-api'.
2017-06-27 12:37:58.884754 Traceback (most recent call last):
2017-06-27 12:37:58.884770   File "/usr/local/bin/heat-wsgi-api", line 54,
in 
2017-06-27 12:37:58.884814 application = init_application()
2017-06-27 12:37:58.884825   File "/opt/stack/heat/heat/httpd/heat_api.py",
line 36, in init_application
2017-06-27 12:37:58.884852 logging.register_options(cfg.CONF)
2017-06-27 12:37:58.884861   File
"/usr/local/lib/python2.7/dist-packages/oslo_log/log.py",
line 250, in register_options
2017-06-27 12:37:58.884874 conf.register_cli_opts(_option
s.common_cli_opts)
2017-06-27 12:37:58.884882   File
"/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py",
line 2329, in __inner
2017-06-27 12:37:58.884895 result = f(self, *args, **kwargs)
2017-06-27 12:37:58.884902   File
"/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py",
line 2551, in register_cli_opts
2017-06-27 12:37:58.884913 self.register_cli_opt(opt, group,
clear_cache=False)
2017-06-27 12:37:58.884932   File
"/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py",
line 2333, in __inner
2017-06-27 12:37:58.884943 return f(self, *args, **kwargs)
2017-06-27 12:37:58.884949   File
"/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py",
line 2543, in register_cli_opt
2017-06-27 12:37:58.884960 raise ArgsAlreadyParsedError("cannot
register CLI option")
2017-06-27 12:37:58.884977 ArgsAlreadyParsedError: arguments already
parsed: cannot register CLI option


I checked that it was a bug initially which was fixed in openstac/heat
6.0.0.0b1. I referred to the following links:

https://bugs.launchpad.net/heat/+bug/1500807

https://review.openstack.org/gitweb?p=openstack/heat.git;a=c
ommitdiff;h=a1b3c23ff856ed2574a1ab50ba854f6a79b3213e#patch1

https://git.openstack.org/cgit/openstack/heat/diff/?id=a1b3c
23ff856ed2574a1ab50ba854f6a79b3213e


I am using latest version of heat and everything seems to be as desired as
per the links above, but I am still getting the error as mentioned.

I please request you to help me out here to fix this issue.

Eagerly waiting for your response!

Thanking you in anticipation!

Best Regards,
Mohit
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat] Heat::SoftwareDeployment not working

[Volodymyr Litovka]

Please, check whether this can be an issue -

https://bugs.launchpad.net/openstack-manuals/+bug/1661759

you should use 'v2.0' path in both es2authtoken and keystone_authtoken 
sections of heat.conf.


On 6/23/17 3:47 PM, Amit Kumar wrote:

Hi All,

I have installed OpenStack Mitaka using OpenStack-Ansible 13.3.13. 
Trying to use Heat::SoftwareDeployment resource similar to as 
described in:
https://github.com/openstack/heat-templates/blob/master/hot/software-config/example-templates/example-script-template.yaml ; 
but is not working as expected. SoftwareDeployment resource is always 
in progress state once heat stack is created from command line.


Here are the /var/log/cloud-init-output.log: 
http://paste.openstack.org/show/613502/
/var/log/os-collect-config.log shows these logs: 
http://paste.openstack.org/show/613503/. Can they cause any harm?
/var/run/heat-config/heat-config is showing the script and the input 
parameters which I want to run on VM. Here are the logs: 
http://paste.openstack.org/show/613504/ but in-spite of script and its 
input being here, 
//var/lib/cloud/instances/i-003a/scripts/userdata/ file is empty.
Here is the /var/lib/cloud/instances/i-003a/user-data.txt: 
http://paste.openstack.org/show/613505/


With the help of above logs, please see if you can point out if I am 
missing anything here.


Thanks.

Regards,
Amit




___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


--
Volodymyr Litovka
  "Vision without Execution is Hallucination." -- Thomas Edison

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat] Heat::SoftwareDeployment not working

[Eugen Block]

Hi,

since heat is not really my strong suit I won't be able to help you  
there. Hopefully, someone else with more experience will help you.


Regards,
Eugen


Zitat von Amit Kumar :


Thanks Eugene and Ignazio for your replies.

Please take note that Heat::SoftwareConfiguration is working perfectly at
my end. Shell script provided with Software configuration works fine.
Problem is occurring only when I am trying to use Heat::SoftwareDeployment
instead of using SoftwareConfig directly. Only motive behind using
SoftwareDeployment is to be able to pass input parameters to shell script.

Adding more to the above, VM is accessible from external new using SSH.
Flat NW is being used to put VM's eth0 on external NW. IP assigned is fixed
using NW port. If Nw is provider Nw then does it make any difference for
SoftwareConfig and SoftwareDeployment? curl -v http://169.254.169.254
<http://169.254.169.254/latest> works fine.

Regards,
Amit

On Jun 23, 2017 6:51 PM, "Eugen Block"  wrote:

Hi,

it seems like your VM fails to connect to the metadata server, so any
configuration provided by user-data will have failed. Is the VM's network
configured properly? Does it get its IP by DHCP? Is it a provider network
or a self-service network?
If it's a provider network (external router), you'll have to provide the
user-data and network config by config-drive, this way you won't need a
metadata-server. If it's a self-service network, is DHCP enabled? Check
your ip config within your vm. If the ip config is as expected, try to
execute "curl -v http://169.254.169.254/latest";, does it timeout?

Are dhcp-server and metadata-server up and running? What's the output of
neutron agent-list

If you launch an instance in the same network without heat, just with the
user-data, does that work? If it does it's probably a heat issue. Have you
checked the heat logs for any hints?

Regards
Eugen


Zitat von Amit Kumar :

Hi All,


I have installed OpenStack Mitaka using OpenStack-Ansible 13.3.13. Trying
to use Heat::SoftwareDeployment resource similar to as described in:
https://github.com/openstack/heat-templates/blob/master/hot/
software-config/example-templates/example-script-template.yaml
;
but is not working as expected. SoftwareDeployment resource is always in
progress state once heat stack is created from command line.

Here are the /var/log/cloud-init-output.log:
http://paste.openstack.org/show/613502/
/var/log/os-collect-config.log shows these logs:
http://paste.openstack.org/show/613503/. Can they cause any harm?
/var/run/heat-config/heat-config is showing the script and the input
parameters which I want to run on VM. Here are the logs:
http://paste.openstack.org/show/613504/ but in-spite of script and its
input being here, */var/lib/cloud/instances/i-003a/scripts/userdata*

file is empty.
Here is the /var/lib/cloud/instances/i-003a/user-data.txt:
http://paste.openstack.org/show/613505/

With the help of above logs, please see if you can point out if I am
missing anything here.

Thanks.

Regards,
Amit





--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat] Heat::SoftwareDeployment not working

[Amit Kumar]

Thanks Eugene and Ignazio for your replies.

Please take note that Heat::SoftwareConfiguration is working perfectly at
my end. Shell script provided with Software configuration works fine.
Problem is occurring only when I am trying to use Heat::SoftwareDeployment
instead of using SoftwareConfig directly. Only motive behind using
SoftwareDeployment is to be able to pass input parameters to shell script.

Adding more to the above, VM is accessible from external new using SSH.
Flat NW is being used to put VM's eth0 on external NW. IP assigned is fixed
using NW port. If Nw is provider Nw then does it make any difference for
SoftwareConfig and SoftwareDeployment? curl -v http://169.254.169.254
<http://169.254.169.254/latest> works fine.

Regards,
Amit

On Jun 23, 2017 6:51 PM, "Eugen Block"  wrote:

Hi,

it seems like your VM fails to connect to the metadata server, so any
configuration provided by user-data will have failed. Is the VM's network
configured properly? Does it get its IP by DHCP? Is it a provider network
or a self-service network?
If it's a provider network (external router), you'll have to provide the
user-data and network config by config-drive, this way you won't need a
metadata-server. If it's a self-service network, is DHCP enabled? Check
your ip config within your vm. If the ip config is as expected, try to
execute "curl -v http://169.254.169.254/latest";, does it timeout?

Are dhcp-server and metadata-server up and running? What's the output of
neutron agent-list

If you launch an instance in the same network without heat, just with the
user-data, does that work? If it does it's probably a heat issue. Have you
checked the heat logs for any hints?

Regards
Eugen


Zitat von Amit Kumar :

Hi All,
>
> I have installed OpenStack Mitaka using OpenStack-Ansible 13.3.13. Trying
> to use Heat::SoftwareDeployment resource similar to as described in:
> https://github.com/openstack/heat-templates/blob/master/hot/
> software-config/example-templates/example-script-template.yaml
> ;
> but is not working as expected. SoftwareDeployment resource is always in
> progress state once heat stack is created from command line.
>
> Here are the /var/log/cloud-init-output.log:
> http://paste.openstack.org/show/613502/
> /var/log/os-collect-config.log shows these logs:
> http://paste.openstack.org/show/613503/. Can they cause any harm?
> /var/run/heat-config/heat-config is showing the script and the input
> parameters which I want to run on VM. Here are the logs:
> http://paste.openstack.org/show/613504/ but in-spite of script and its
> input being here, */var/lib/cloud/instances/i-003a/scripts/userdata*
>
> file is empty.
> Here is the /var/lib/cloud/instances/i-003a/user-data.txt:
> http://paste.openstack.org/show/613505/
>
> With the help of above logs, please see if you can point out if I am
> missing anything here.
>
> Thanks.
>
> Regards,
> Amit
>



-- 
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat] Heat::SoftwareDeployment not working

[Eugen Block]

Hi,

it seems like your VM fails to connect to the metadata server, so any  
configuration provided by user-data will have failed. Is the VM's  
network configured properly? Does it get its IP by DHCP? Is it a  
provider network or a self-service network?
If it's a provider network (external router), you'll have to provide  
the user-data and network config by config-drive, this way you won't  
need a metadata-server. If it's a self-service network, is DHCP  
enabled? Check your ip config within your vm. If the ip config is as  
expected, try to execute "curl -v http://169.254.169.254/latest";, does  
it timeout?


Are dhcp-server and metadata-server up and running? What's the output of
neutron agent-list

If you launch an instance in the same network without heat, just with  
the user-data, does that work? If it does it's probably a heat issue.  
Have you checked the heat logs for any hints?


Regards
Eugen


Zitat von Amit Kumar :


Hi All,

I have installed OpenStack Mitaka using OpenStack-Ansible 13.3.13. Trying
to use Heat::SoftwareDeployment resource similar to as described in:
https://github.com/openstack/heat-templates/blob/master/hot/software-config/example-templates/example-script-template.yaml
;
but is not working as expected. SoftwareDeployment resource is always in
progress state once heat stack is created from command line.

Here are the /var/log/cloud-init-output.log:
http://paste.openstack.org/show/613502/
/var/log/os-collect-config.log shows these logs:
http://paste.openstack.org/show/613503/. Can they cause any harm?
/var/run/heat-config/heat-config is showing the script and the input
parameters which I want to run on VM. Here are the logs:
http://paste.openstack.org/show/613504/ but in-spite of script and its
input being here, */var/lib/cloud/instances/i-003a/scripts/userdata*
file is empty.
Here is the /var/lib/cloud/instances/i-003a/user-data.txt:
http://paste.openstack.org/show/613505/

With the help of above logs, please see if you can point out if I am
missing anything here.

Thanks.

Regards,
Amit




--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat] Heat::SoftwareDeployment not working

[Ignazio Cassano]

Hi Amit,
when I got issues with software config  the reason was the communication
between instance and heat_waitcondition_server_url specified in
/etc/heat/heat.conf.
I am not sure if it could help you.
Ignazio


2017-06-23 14:47 GMT+02:00 Amit Kumar :

> Hi All,
>
> I have installed OpenStack Mitaka using OpenStack-Ansible 13.3.13. Trying
> to use Heat::SoftwareDeployment resource similar to as described in:
> https://github.com/openstack/heat-templates/blob/master/
> hot/software-config/example-templates/example-script-template.yaml ; but
> is not working as expected. SoftwareDeployment resource is always in
> progress state once heat stack is created from command line.
>
> Here are the /var/log/cloud-init-output.log: http://paste.
> openstack.org/show/613502/
> /var/log/os-collect-config.log shows these logs: http://paste.openstack.
> org/show/613503/. Can they cause any harm?
> /var/run/heat-config/heat-config is showing the script and the input
> parameters which I want to run on VM. Here are the logs:
> http://paste.openstack.org/show/613504/ but in-spite of script and its
> input being here, */var/lib/cloud/instances/i-003a/scripts/userdata*
> file is empty.
> Here is the /var/lib/cloud/instances/i-003a/user-data.txt: http
> ://paste.openstack.org/show/613505/
>
> With the help of above logs, please see if you can point out if I am
> missing anything here.
>
> Thanks.
>
> Regards,
> Amit
>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [heat] Heat::SoftwareDeployment not working

[Amit Kumar]

Hi All,

I have installed OpenStack Mitaka using OpenStack-Ansible 13.3.13. Trying
to use Heat::SoftwareDeployment resource similar to as described in:
https://github.com/openstack/heat-templates/blob/master/hot/software-config/example-templates/example-script-template.yaml
;
but is not working as expected. SoftwareDeployment resource is always in
progress state once heat stack is created from command line.

Here are the /var/log/cloud-init-output.log:
http://paste.openstack.org/show/613502/
/var/log/os-collect-config.log shows these logs:
http://paste.openstack.org/show/613503/. Can they cause any harm?
/var/run/heat-config/heat-config is showing the script and the input
parameters which I want to run on VM. Here are the logs:
http://paste.openstack.org/show/613504/ but in-spite of script and its
input being here, */var/lib/cloud/instances/i-003a/scripts/userdata*
file is empty.
Here is the /var/lib/cloud/instances/i-003a/user-data.txt:
http://paste.openstack.org/show/613505/

With the help of above logs, please see if you can point out if I am
missing anything here.

Thanks.

Regards,
Amit
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Heat][Openstack-Ansible] Heat Engine not able to connect to Aodh Service

[Amit Kumar]

Hi All,

I have installed OpenStack Newton release using Ansible. I am trying
Orchestration with HEAT template. Here is the HEAT template I am using:
http://paste.openstack.org/show/610960/.

OS::Ceilometer:Alarm resource creation is failing while HEAT stack creation
is in progress. Here are the HEAT engine logs: http://paste.openstack.
org/show/610972/. They are showing error in connecting to
http://172.29.236.11:8042/v2/alarms but when I am trying to "wget
http://172.29.236.11:8042/v2/alarms"; from the HEAT engine, it shows
connected but then "401 Unauthorized" response code.

Has anybody faced such problem, please respond?

Regards,
Amit
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [openstack][heat][openstack-telemetry][openstack-ansible] Heat engine unable to connect to Aodh service

[Amit Kumar]

Hi All,

I have installed OpenStack Newton release using Ansible. I am trying
Orchestration with HEAT template. Here is the HEAT template I am using:
http://paste.openstack.org/show/610960/.

OS::Ceilometer:Alarm resource creation is failing while HEAT stack creation
is in progress. Here are the HEAT engine logs:
http://paste.openstack.org/show/610972/. They are showing error in
connecting to http://172.29.236.11:8042/v2/alarms but when I am trying to
"wget http://172.29.236.11:8042/v2/alarms"; from the HEAT engine, it shows
connected but then "401 Unauthorized" response code.

Has anybody faced such problem, please respond?

Regards,
Amit
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [heat][cinder] How to manage my volumes ?

[Lars-Erik Helander]

I am struggling to find a solution given the following:


-  A cluster of two or more servers

-  Each server has a storage volume attached

-  If a server goes down (disappears) it should attach to the same 
(identical content) volume when it is re-created

-  Minimal manual intervention for all life-cycle use cases

-  Fully managed vi Heat


If it would be possible to define the following logic, it would be great, but I 
have not found any way to do this:


-  For each server, pre-declare the name of the volume to attach

-  When server is created and a volume with the pre-declared name 
exists, that volume is attached

-  When a server is created and a volume with the pre-declared name 
does not exist, such a volume is automatically created

-  When a server is deleted, its attached volume is deattached but not 
deleted (could do this using “deletion_policy: ‘Retain’” )

I would be happy to receive feedback on any idea that will take me closer to a 
solution.

I have tried to use “external_id:” in conjunction with OS::Cinder::Volume in 
order to get a pre-declared name for each volume, but that did not work as I 
expected it to. I ma currently on “Newton”.

Thanks
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Heat] Customize server names in AutoScalingGroup

[Phil Clay]

Hi,
I want to customize the names of the OS::Nova::Server resources that are part 
of a OS::Heat::AutoScalingGroup resource.
Ideally, I want to use something like:
    -

If I do not specify the name, then the name will default to this pattern:
    --
I could, in theory, get close to what I want by just customizing the stackName. 
 However, in reality, the stackname to which the server belongs will be super 
long, because the AutoScalingGroup creates nested stacks.  So for example, if 
my top level stack name is myawesomestack, the server will belong to a nested 
stack whose name is something like:
    myawesomestack-asg-lcu5abqafob2-q2lhhye4iux5-kezgqb5ub5k4
Then, the servers will be created with a name that looks like this  (note the 
stackname is shortened by using the first two characters, and the last X digits 
to keep it under a certain length):
    my-fob2-bods7udv2y6o-mowdcx2ewaiz-server-f4quplsegdiw



Therefore, the default naming pattern does not meet my needs.

In order to get the pattern I want, I must figure out what to specify for the 
name value.  I tried a few things...
A) First, I just tried a static name, hoping that Heat would auto-append 
something.  Unfortunately, Heat doesn't do that, and all the servers end up 
with the same name.  This does not work for me.
B) Then, I tried using a OS::Heat::RandomString to generate a unique suffix 
like this:
  server_name_suffix:    type: OS::Heat::RandomString    properties:      
character_classes:        - class: lowercase        - class: digits        
server:    type: OS::Nova::Server    properties:      name:        str_replace: 
         template: $prefix-$suffix          params:            $prefix: 
{get_param: name_prefix}            $suffix: {get_resource: server_name_suffix}
This results in the servers having unique names that follow the pattern I want. 
 However, when I perform a rolling update by changing something on the server 
(e.g. user_data or something), the RandomString resources do NOT change.  
Therefore the "new" servers will end up with the same name as the "old" 
servers.  This doesn't work for me either.  New servers should have a new name. 
 This is not just a preference thing, since the LBaaS provider I'm using 
complained about servers with the same name, so it really just doesn't work for 
me.
C) Then, I tried to incorporate the server's resource id into the name like 
this:
  server:    type: OS::Nova::Server    properties:      name:        
str_replace:          template: $prefix-$suffix          params:            
$prefix: {get_param: name_prefix}            $suffix: {get_resource: server}
I didn't expect this to work, but I tried it anyway.  I was right, Heat 
complains about a circular reference.

I haven't found any other way to get the naming pattern that I would like.
So here are my questions:
1) Has anybody figured out how to get server names to use a simple pattern  
(-) ?
2) Is it possible to get a RandomString to update when the server updates 
within an AutoScalingGroup?  This would allow #B to work.
3) Is it possible to get/use the id of the resource from within itself?  This 
would allow #C to work.  The shortId 
(https://github.com/openstack/heat/blob/master/heat/common/short_id.py#L41-L58) 
would be even better.___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat] Fwd: newton heat stack glance error

[Brian Rosmaita]

Adding "heat" to the subject line.  Heat people, I've responded to
Ignazio on the operators' list [0], but you may have some helpful info.

[0] (would link here, but can't find the April 2017 page in pipermail)

Thread starts here:
http://lists.openstack.org/pipermail/openstack-operators/2017-March/013078.html

thanks,
brian

On 4/1/17 2:42 AM, Ignazio Cassano wrote:
> Hi all,
> Please, could anyone help me about the problem showed in the follwing
> email?
> Regards
> Ignazio
> 
> 
> 
> -- Messaggio inoltrato --
> Da: "Ignazio Cassano" 
> Data: 31/Mar/2017 16:52
> Oggetto: newton heat stack glance error
> A: "OpenStack Operators" 
> Cc:
> 
> Hi all,
>> I just installed openstack newton on centos 7 and enabled glance with v2
>> api.
>> When I execute a simple heat stack, it returns the following error:
>>
>> ERROR: Property error: : resources.my_instance.properties.image: :
>> HTTPMultipleChoices (HTTP 300) Requested version of OpenStack Images API is
>> not available.
>>
>>
>> the following is my very simple stack:
>>
>> heat_template_version: 2015-10-15
>> description: simple test
>> resources:
>>   my_instance:
>> type: OS::Nova::Server
>> properties:
>>   key_name: opstkcsi
>>   image: cirros
>>   flavor: m1.small
>>   networks:
>>   - network: "0bfd37f8-779f-4b51-bb79-b03745409c15"
>>
>>
>> I am able to create instances from image using the dashboard and creating
>> volume from images but it does not work.
>> Please, help me !!!
>> Thanks
>> Ignazio
>>
> 
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Conditions on resource properties

[Lars-Erik Helander]

Thanks, found the example in the documentation but I could not make my case to 
work. What if the values are more complex than strings, e.g. a list of maps, do 
anyone have an example of that?


On 2017-03-22, 20:11, "Zane Bitter"  wrote:

On 22/03/17 07:45, Lars-Erik Helander wrote:
> The Heat documentation states that conditions could be applied to
> resources, resource properties and output values. I have failed to set
> conditions on resource properties and I have found no examples. Anyone
> that has a working example?

You'll want to use the 'if' intrinsic function to specify different 
property values based on conditions.

cheers,
Zane.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Conditions on resource properties

[Zane Bitter]

On 22/03/17 07:45, Lars-Erik Helander wrote:

The Heat documentation states that conditions could be applied to
resources, resource properties and output values. I have failed to set
conditions on resource properties and I have found no examples. Anyone
that has a working example?


You'll want to use the 'if' intrinsic function to specify different 
property values based on conditions.


cheers,
Zane.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Heat] Conditions on resource properties

[Lars-Erik Helander]

The Heat documentation states that conditions could be applied to resources, 
resource properties and output values. I have failed to set conditions on 
resource properties and I have found no examples. Anyone that has a working 
example?
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Heat] Dynamically create OS::Nova:Server "networks" property

[Lars-Erik Helander]

I have tried in numerous ways to compose a proper value for the “networks” 
property of OS::Nova::Server but with no success.

Basically I have two “inputs” that together shall result in the complete 
networks lists, e.g.

List1 : “[{port: foo1}, {port: foo2}]”
List2 : “[{network: foo3}, {port: foo4}, network: foo5}]”

Should be combined into a networks specification that is similar to this:

   type: OS::Nova::Server
   properties:
  networks:

-  port: foo1

-  port: foo2

-  network: foo3

-  port: foo4

-  network: foo5

I have tried the repeat intrinsic function but have not found any working 
syntax.

List input should be both from an input parameter and/or from an output 
attribute of some resource.


Any help is highly appreciated.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[Davide Panarese]

If you’re using v2 authentication Domains are not enabled. Did you try to use 
v3 authentication?! I’m using keystone v3 (i follow mitaka install too)

Let me know.

Davide
> On 02 Feb 2017, at 20:15, NareshA kumar  wrote:
> 
> Davide,
> I have other services like cinder and tacker configured (tacker is not 
> working as it needs heat). Memcached server is working still authentication 
> error is there.
> I followed 
> http://docs.openstack.org/mitaka/install-guide-ubuntu/heat-install.html 
>  In 
> keystone v2 we cant create domains as mentioned in this document. Is there 
> any suitable document for keystone v2 that I can follow? Please let me know 
> how can I check if keystone store the token properly?
> 
> Regards,
> NareshA.
> 
> On Thu, Feb 2, 2017 at 9:29 PM, Davide Panarese  > wrote:
> Hi,
> do you have other services or only heat configured?! 
> Did you check if keystone store token properly? I had the same problem when 
> my memcache token backend didn’t work.
> 
> If not, it seems all correct. Did you follow openstack install official guide?
> 
> Davide
> 
>> On 02 Feb 2017, at 10:19, NareshA kumar > > wrote:
>> 
>> Dear Davide,
>> Below are the steps I have followed to configure heat in kilo. Please let me 
>> know if I am missing something here.
>> 
>> mysql -u root -p
>> 
>> CREATE DATABASE heat;
>> 
>> GRANT ALL PRIVILEGES ON heat.* TO 'heat'@'localhost' \
>>   IDENTIFIED BY 'heat';
>> GRANT ALL PRIVILEGES ON heat.* TO 'heat'@'%' \
>>   IDENTIFIED BY 'heat';
>> 
>> export OS_TENANT_NAME='openstack'
>> export OS_USERNAME='admin'
>> export OS_PASSWORD='Chang3M3'
>> export OS_AUTH_URL='https://identity.cncloud.com:5000/v2.0 
>> '
>> export OS_AUTH_STRATEGY='keystone'
>> export OS_REGION_NAME='RegionOne'
>> 
>> 
>> keystone user-create --name heat --pass heat
>> keystone user-role-add --user heat --role admin --tenant services
>> keystone service-create --name heat --description "Orchestration" --type 
>> orchestration
>> keystone service-create --name heat-cfn --description "Orchestration" --type 
>> cloudformation
>> keystone endpoint-create --service heat --publicurl "MailScanner ha rilevato 
>> un possibile tentativo di frode proveniente da "54.174.88.227:8004" 
>> MailScanner warning: numerical links are often malicious: 
>> http://54.174.88.227:8004/v1/%(tenant_id)s 
>> " --adminurl "MailScanner ha 
>> rilevato un possibile tentativo di frode proveniente da "54.174.88.227:8004" 
>> MailScanner warning: numerical links are often 
>> malicious:http://54.174.88.227:8004/v1/%(tenant_id)s 
>> " --internalurl "MailScanner ha 
>> rilevato un possibile tentativo di frode proveniente da "54.174.88.227:8004" 
>> MailScanner warning: numerical links are often malicious: 
>> http://54.174.88.227:8004/v1/%(tenant_id)s 
>> "
>> keystone endpoint-create --service heat-cfn --publicurl "MailScanner ha 
>> rilevato un possibile tentativo di frode proveniente da "54.174.88.227:8000" 
>> MailScanner warning: numerical links are often malicious: 
>> http://54.174.88.227:8000/v1/%(tenant_id)s 
>> " --adminurl "MailScanner ha 
>> rilevato un possibile tentativo di frode proveniente da "54.174.88.227:8000" 
>> MailScanner warning: numerical links are often malicious: 
>> http://54.174.88.227:8000/v1/%(tenant_id)s 
>> " --internalurl "MailScanner ha 
>> rilevato un possibile tentativo di frode proveniente da "54.174.88.227:8000" 
>> MailScanner warning: numerical links are often malicious: 
>> http://54.174.88.227:8000/v1/%(tenant_id)s 
>> "
>> keystone role-create --name heat_stack_owner
>> keystone user-role-add --user admin --tenant openstack --role 
>> heat_stack_owner
>> keystone role-create --name heat_stack_user
>> 
>> heat-keystone-setup-domain \
>> –stack-user-domain-name heat_user_domain \
>> –stack-domain-admin heat_domain_admin \
>> –stack-domain-admin-password $HeatPass | tee heat-keystone-setup-domain.out
>> 
>> heact.conf:
>> [DEFAULT]
>> debug = true
>> verbose = true
>> rpc_backend = zmq
>> heat_metadata_server_url = MailScanner ha rilevato un possibile tentativo di 
>> frode proveniente da "54.174.88.227:8000" MailScanner warning: numerical 
>> links are often malicious: http://54.174.88.227:8000 
>> 
>> heat_waitcondition_server_url = MailScanner ha rilevato un possibile 
>> tentativo di frode proveniente da "54.174.88.227:8000" MailScanner warning: 
>> numerical links are often malicious: 
>> http://54.174.88.227:8000/v1/waitcondition 
>> 
>> stack_domain_admin  = heat_domain_admin
>> stack_d

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[NareshA kumar]

Davide,
I have other services like cinder and tacker configured (tacker is not
working as it needs heat). Memcached server is working still authentication
error is there.
I followed
http://docs.openstack.org/mitaka/install-guide-ubuntu/heat-install.html In
keystone v2 we cant create domains as mentioned in this document. Is there
any suitable document for keystone v2 that I can follow? Please let me know
how can I check if keystone store the token properly?

Regards,
NareshA.

On Thu, Feb 2, 2017 at 9:29 PM, Davide Panarese  wrote:

> Hi,
> do you have other services or only heat configured?!
> Did you check if keystone store token properly? I had the same problem
> when my memcache token backend didn’t work.
>
> If not, it seems all correct. Did you follow openstack install official
> guide?
>
> Davide
>
> On 02 Feb 2017, at 10:19, NareshA kumar  wrote:
>
> Dear Davide,
> Below are the steps I have followed to configure heat in kilo. Please let
> me know if I am missing something here.
>
> mysql -u root -p
>
> CREATE DATABASE heat;
>
> GRANT ALL PRIVILEGES ON heat.* TO 'heat'@'localhost' \
>   IDENTIFIED BY 'heat';
> GRANT ALL PRIVILEGES ON heat.* TO 'heat'@'%' \
>   IDENTIFIED BY 'heat';
>
> export OS_TENANT_NAME='openstack'
> export OS_USERNAME='admin'
> export OS_PASSWORD='Chang3M3'
> export OS_AUTH_URL='https://identity.cncloud.com:5000/v2.0'
> export OS_AUTH_STRATEGY='keystone'
> export OS_REGION_NAME='RegionOne'
>
>
> keystone user-create --name heat --pass heat
> keystone user-role-add --user heat --role admin --tenant services
> keystone service-create --name heat --description "Orchestration" --type
> orchestration
> keystone service-create --name heat-cfn --description "Orchestration"
> --type cloudformation
> keystone endpoint-create --service heat --publicurl "*MailScanner
> warning: numerical links are often malicious:*
> http://54.174.88.227:8004/v1/%(tenant_id)s" --adminurl "*MailScanner
> warning: numerical links are often malicious:*
> http://54.174.88.227:8004/v1/%(tenant_id)s" --internalurl "*MailScanner
> warning: numerical links are often malicious:*
> http://54.174.88.227:8004/v1/%(tenant_id)s"
> keystone endpoint-create --service heat-cfn --publicurl "*MailScanner
> warning: numerical links are often malicious:*
> http://54.174.88.227:8000/v1/%(tenant_id)s" --adminurl "*MailScanner
> warning: numerical links are often malicious:*
> http://54.174.88.227:8000/v1/%(tenant_id)s" --internalurl "*MailScanner
> warning: numerical links are often malicious:*
> http://54.174.88.227:8000/v1/%(tenant_id)s"
> keystone role-create --name heat_stack_owner
> keystone user-role-add --user admin --tenant openstack --role
> heat_stack_owner
> keystone role-create --name heat_stack_user
>
> heat-keystone-setup-domain \
> –stack-user-domain-name heat_user_domain \
> –stack-domain-admin heat_domain_admin \
> –stack-domain-admin-password $HeatPass | tee heat-keystone-setup-domain.out
>
> heact.conf:
> [DEFAULT]
> debug = true
> verbose = true
> rpc_backend = zmq
> heat_metadata_server_url = *MailScanner warning: numerical links are
> often malicious:* http://54.174.88.227:8000 
> heat_waitcondition_server_url = *MailScanner warning: numerical links are
> often malicious:* http://54.174.88.227:8000/v1/waitcondition
> 
> stack_domain_admin  = heat_domain_admin
> stack_domain_admin_password  = Chang3M3
> stack_user_domain_name = heat_user_domain
> stack_user_domain_id=f798141e117a417996a736ba8f57f368
> rpc_zmq_host = 54.174.88.227
> [database]
> connection = mysql://heat:heat@54.174.88.227/heat
> [keystone_authtoken]
> auth_uri = https://identity.cncloud.com:5000/v2.0
> identity_url = https://identity.cncloud.com:35357
> #memcached_servers = controller:11211
> project_name = services
> auth_type = password
> admin_tenant_name = services
> admin_user = heat
> admin_password = heat
> [ec2authtoken]
> auth_uri =  https://identity.cncloud.com:5000/v2.0
>
> heat-manage db_sync
>
> service heat-api restart
> service heat-api-cfn restart
> service heat-engine restart
>
> export OS_TENANT_NAME='services'
> export OS_USERNAME='heat'
> export OS_PASSWORD='heat'
> export OS_AUTH_URL='https://identity.cncloud.com:5000/v2.0'
> export OS_AUTH_STRATEGY='keystone'
> export OS_REGION_NAME='RegionOne'
>
> heat stack-list
>
> ERROR : Authentication Required.
>
>
>
> Regards,
> NareshA.
>
> On Wed, Feb 1, 2017 at 4:07 PM, NareshA kumar 
> wrote:
>
>> Davide,
>> Yes I am using the heat credentials as you have mentioned. But still I am
>> getting Authentication required error.
>>
>> Regards,
>> NareshA.
>>
>> On Wed, Feb 1, 2017 at 4:01 PM, NareshA kumar 
>> wrote:
>>
>>> Davide,
>>> Yes I am using the heat credentials as you have mentioned. But still I
>>> am getting Authentication required error.
>>>
>>> I am attaching heat-api.log here for your reference. I am guessing that
>>> I would have missed something while creating heat domains.
>>>
>>> Regards,
>>

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[Davide Panarese]

Hi,
do you have other services or only heat configured?! 
Did you check if keystone store token properly? I had the same problem when my 
memcache token backend didn’t work.

If not, it seems all correct. Did you follow openstack install official guide?

Davide

> On 02 Feb 2017, at 10:19, NareshA kumar  wrote:
> 
> Dear Davide,
> Below are the steps I have followed to configure heat in kilo. Please let me 
> know if I am missing something here.
> 
> mysql -u root -p
> 
> CREATE DATABASE heat;
> 
> GRANT ALL PRIVILEGES ON heat.* TO 'heat'@'localhost' \
>   IDENTIFIED BY 'heat';
> GRANT ALL PRIVILEGES ON heat.* TO 'heat'@'%' \
>   IDENTIFIED BY 'heat';
> 
> export OS_TENANT_NAME='openstack'
> export OS_USERNAME='admin'
> export OS_PASSWORD='Chang3M3'
> export OS_AUTH_URL='https://identity.cncloud.com:5000/v2.0 
> '
> export OS_AUTH_STRATEGY='keystone'
> export OS_REGION_NAME='RegionOne'
> 
> 
> keystone user-create --name heat --pass heat
> keystone user-role-add --user heat --role admin --tenant services
> keystone service-create --name heat --description "Orchestration" --type 
> orchestration
> keystone service-create --name heat-cfn --description "Orchestration" --type 
> cloudformation
> keystone endpoint-create --service heat --publicurl "MailScanner warning: 
> numerical links are often malicious: 
> http://54.174.88.227:8004/v1/%(tenant_id)s 
> " --adminurl "MailScanner 
> warning: numerical links are often malicious: 
> http://54.174.88.227:8004/v1/%(tenant_id)s 
> " --internalurl "MailScanner 
> warning: numerical links are often malicious: 
> http://54.174.88.227:8004/v1/%(tenant_id)s 
> "
> keystone endpoint-create --service heat-cfn --publicurl "MailScanner warning: 
> numerical links are often malicious: 
> http://54.174.88.227:8000/v1/%(tenant_id)s 
> " --adminurl "MailScanner 
> warning: numerical links are often malicious: 
> http://54.174.88.227:8000/v1/%(tenant_id)s 
> " --internalurl "MailScanner 
> warning: numerical links are often malicious: 
> http://54.174.88.227:8000/v1/%(tenant_id)s 
> "
> keystone role-create --name heat_stack_owner
> keystone user-role-add --user admin --tenant openstack --role heat_stack_owner
> keystone role-create --name heat_stack_user
> 
> heat-keystone-setup-domain \
> –stack-user-domain-name heat_user_domain \
> –stack-domain-admin heat_domain_admin \
> –stack-domain-admin-password $HeatPass | tee heat-keystone-setup-domain.out
> 
> heact.conf:
> [DEFAULT]
> debug = true
> verbose = true
> rpc_backend = zmq
> heat_metadata_server_url = MailScanner warning: numerical links are often 
> malicious: http://54.174.88.227:8000 
> heat_waitcondition_server_url = MailScanner warning: numerical links are 
> often malicious: http://54.174.88.227:8000/v1/waitcondition 
> 
> stack_domain_admin  = heat_domain_admin
> stack_domain_admin_password  = Chang3M3
> stack_user_domain_name = heat_user_domain
> stack_user_domain_id=f798141e117a417996a736ba8f57f368
> rpc_zmq_host = 54.174.88.227
> [database]
> connection = mysql://heat:heat@54.174.88.227/heat 
> 
> [keystone_authtoken]
> auth_uri = https://identity.cncloud.com:5000/v2.0 
> 
> identity_url = https://identity.cncloud.com:35357 
> 
> #memcached_servers = controller:11211
> project_name = services
> auth_type = password
> admin_tenant_name = services
> admin_user = heat
> admin_password = heat
> [ec2authtoken]
> auth_uri =  https://identity.cncloud.com:5000/v2.0 
> 
> 
> heat-manage db_sync
> 
> service heat-api restart
> service heat-api-cfn restart
> service heat-engine restart
> 
> export OS_TENANT_NAME='services'
> export OS_USERNAME='heat'
> export OS_PASSWORD='heat'
> export OS_AUTH_URL='https://identity.cncloud.com:5000/v2.0 
> '
> export OS_AUTH_STRATEGY='keystone'
> export OS_REGION_NAME='RegionOne'
> 
> heat stack-list
> 
> ERROR : Authentication Required.
> 
>  
> 
> Regards,
> NareshA.
> 
> On Wed, Feb 1, 2017 at 4:07 PM, NareshA kumar  > wrote:
> Davide,
> Yes I am using the heat credentials as you have mentioned. But still I am 
> getting Authentication required error.
> 
> Regards,
> NareshA.
> 
> On Wed, Feb 1, 2017 at 4:01 PM, NareshA kumar  > wrote:
> Davide,
> Yes I am using the heat credentials as you have mentioned. But still I am 
> getting Authentication required error.
> 
> I am attaching heat-api.log here for your reference. I am guessing that I 
> would have miss

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[NareshA kumar]

Dear Davide,
Below are the steps I have followed to configure heat in kilo. Please let
me know if I am missing something here.

mysql -u root -p

CREATE DATABASE heat;

GRANT ALL PRIVILEGES ON heat.* TO 'heat'@'localhost' \
  IDENTIFIED BY 'heat';
GRANT ALL PRIVILEGES ON heat.* TO 'heat'@'%' \
  IDENTIFIED BY 'heat';

export OS_TENANT_NAME='openstack'
export OS_USERNAME='admin'
export OS_PASSWORD='Chang3M3'
export OS_AUTH_URL='https://identity.cncloud.com:5000/v2.0'
export OS_AUTH_STRATEGY='keystone'
export OS_REGION_NAME='RegionOne'


keystone user-create --name heat --pass heat
keystone user-role-add --user heat --role admin --tenant services
keystone service-create --name heat --description "Orchestration" --type
orchestration
keystone service-create --name heat-cfn --description "Orchestration"
--type cloudformation
keystone endpoint-create --service heat --publicurl "
http://54.174.88.227:8004/v1/%(tenant_id)s" --adminurl "
http://54.174.88.227:8004/v1/%(tenant_id)s" --internalurl "
http://54.174.88.227:8004/v1/%(tenant_id)s"
keystone endpoint-create --service heat-cfn --publicurl "
http://54.174.88.227:8000/v1/%(tenant_id)s" --adminurl "
http://54.174.88.227:8000/v1/%(tenant_id)s" --internalurl "
http://54.174.88.227:8000/v1/%(tenant_id)s"
keystone role-create --name heat_stack_owner
keystone user-role-add --user admin --tenant openstack --role
heat_stack_owner
keystone role-create --name heat_stack_user

heat-keystone-setup-domain \
–stack-user-domain-name heat_user_domain \
–stack-domain-admin heat_domain_admin \
–stack-domain-admin-password $HeatPass | tee heat-keystone-setup-domain.out

heact.conf:
[DEFAULT]
debug = true
verbose = true
rpc_backend = zmq
heat_metadata_server_url = http://54.174.88.227:8000
heat_waitcondition_server_url = http://54.174.88.227:8000/v1/waitcondition
stack_domain_admin  = heat_domain_admin
stack_domain_admin_password  = Chang3M3
stack_user_domain_name = heat_user_domain
stack_user_domain_id=f798141e117a417996a736ba8f57f368
rpc_zmq_host = 54.174.88.227
[database]
connection = mysql://heat:heat@54.174.88.227/heat
[keystone_authtoken]
auth_uri = https://identity.cncloud.com:5000/v2.0
identity_url = https://identity.cncloud.com:35357
#memcached_servers = controller:11211
project_name = services
auth_type = password
admin_tenant_name = services
admin_user = heat
admin_password = heat
[ec2authtoken]
auth_uri =  https://identity.cncloud.com:5000/v2.0

heat-manage db_sync

service heat-api restart
service heat-api-cfn restart
service heat-engine restart

export OS_TENANT_NAME='services'
export OS_USERNAME='heat'
export OS_PASSWORD='heat'
export OS_AUTH_URL='https://identity.cncloud.com:5000/v2.0'
export OS_AUTH_STRATEGY='keystone'
export OS_REGION_NAME='RegionOne'

heat stack-list

ERROR : Authentication Required.



Regards,
NareshA.

On Wed, Feb 1, 2017 at 4:07 PM, NareshA kumar 
wrote:

> Davide,
> Yes I am using the heat credentials as you have mentioned. But still I am
> getting Authentication required error.
>
> Regards,
> NareshA.
>
> On Wed, Feb 1, 2017 at 4:01 PM, NareshA kumar 
> wrote:
>
>> Davide,
>> Yes I am using the heat credentials as you have mentioned. But still I am
>> getting Authentication required error.
>>
>> I am attaching heat-api.log here for your reference. I am guessing that I
>> would have missed something while creating heat domains.
>>
>> Regards,
>> NareshA.
>>
>> On Wed, Feb 1, 2017 at 3:14 PM, Davide Panarese 
>> wrote:
>>
>>> If you use heat creadential for token request it works?
>>>
>>> export OS_AUTH_URL=https://identity.cncloud.com:5000/v2.0
>>> export OS_REGION_NAME=RegionOne
>>> export OS_USERNAME=heat
>>> export OS_TENANT_NAME=services
>>> export OS_PASSWORD=heat
>>>
>>> keystone token-get
>>>
>>> Davide
>>>
>>> On 01 Feb 2017, at 10:10, NareshA kumar 
>>> wrote:
>>>
>>> I have associated heat user to services tenant and gave it a admin role.
>>>
>>> keystone user-role-list --user heat --tenant services
>>> +--+---+
>>> --+--+
>>> |id|  name | user_id
>>>  |tenant_id |
>>> +--+---+
>>> --+--+
>>> | 2b995253c23e4c1db8cd374346a4ecd4 | admin |
>>> 645eb7e9f04f4a2b8df65272a23c1394 | 024890084b7642e9b8535b52a86584ea |
>>> +--+---+
>>> --+--+
>>>
>>> heat --debug stack-list
>>>
>>> DEBUG (session) REQ: curl -g -i -X GET https://identity.cncloud.com:5
>>> 000/v2.0 -H "Accept: application/json" -H "User-Agent:
>>> python-keystoneclient"
>>> DEBUG (session) RESP: [200] x-openstack-request-id:
>>> req-2515497e-671b-475e-b48c-0cb6f2ccfe2f content-length: 347 via: 1.1
>>> identity.cncloud.com:5000 access-control-expose-headers: Accept,
>>> Content-Type, X-Auth-Token, X-Subject-Toke

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[NareshA kumar]

Davide,
Yes I am using the heat credentials as you have mentioned. But still I am
getting Authentication required error.

Regards,
NareshA.

On Wed, Feb 1, 2017 at 4:01 PM, NareshA kumar 
wrote:

> Davide,
> Yes I am using the heat credentials as you have mentioned. But still I am
> getting Authentication required error.
>
> I am attaching heat-api.log here for your reference. I am guessing that I
> would have missed something while creating heat domains.
>
> Regards,
> NareshA.
>
> On Wed, Feb 1, 2017 at 3:14 PM, Davide Panarese 
> wrote:
>
>> If you use heat creadential for token request it works?
>>
>> export OS_AUTH_URL=https://identity.cncloud.com:5000/v2.0
>> export OS_REGION_NAME=RegionOne
>> export OS_USERNAME=heat
>> export OS_TENANT_NAME=services
>> export OS_PASSWORD=heat
>>
>> keystone token-get
>>
>> Davide
>>
>> On 01 Feb 2017, at 10:10, NareshA kumar 
>> wrote:
>>
>> I have associated heat user to services tenant and gave it a admin role.
>>
>> keystone user-role-list --user heat --tenant services
>> +--+---+
>> --+--+
>> |id|  name | user_id
>>  |tenant_id |
>> +--+---+
>> --+--+
>> | 2b995253c23e4c1db8cd374346a4ecd4 | admin |
>> 645eb7e9f04f4a2b8df65272a23c1394 | 024890084b7642e9b8535b52a86584ea |
>> +--+---+
>> --+--+
>>
>> heat --debug stack-list
>>
>> DEBUG (session) REQ: curl -g -i -X GET https://identity.cncloud.com:5
>> 000/v2.0 -H "Accept: application/json" -H "User-Agent:
>> python-keystoneclient"
>> DEBUG (session) RESP: [200] x-openstack-request-id:
>> req-2515497e-671b-475e-b48c-0cb6f2ccfe2f content-length: 347 via: 1.1
>> identity.cncloud.com:5000 access-control-expose-headers: Accept,
>> Content-Type, X-Auth-Token, X-Subject-Token vary: X-Auth-Token server:
>> Apache/2.4.7 (Ubuntu) connection: close access-control-allow-methods: GET
>> POST OPTIONS PUT DELETE PATCH date: Wed, 01 Feb 2017 09:07:01 GMT
>> access-control-allow-origin: * access-control-allow-headers: Accept,
>> Content-Type, X-Auth-Token, X-Subject-Token content-type: application/json
>> x-distribution: Ubuntu
>> RESP BODY: {"version": {"status": "stable", "updated":
>> "2014-04-17T00:00:00Z", "media-types": [{"base": "application/json",
>> "type": "application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0",
>> "links": [{"href": "https://identity.cncloud.com:5000/v2.0/";, "rel":
>> "self"}, {"href": "http://docs.openstack.org/";, "type": "text/html",
>> "rel": "describedby"}]}}
>>
>> DEBUG (v2) Making authentication request to
>> https://identity.cncloud.com:5000/v2.0/tokens
>> DEBUG (session) REQ: curl -g -i -X GET *MailScanner warning: numerical
>> links are often malicious:* http://54.174.88.227:8004/v1/0
>> c28d40bdcf0472d8dfb214a5c0286c4/stacks
>> ?
>> -H "Accept: application/json" -H "User-Agent: python-heatclient" -H
>> "X-Region-Name: RegionOne" -H "X-Auth-Token: 
>> {SHA1}9cc75daaff59cdb14a75bfb74ca6d77ebb8d8ac6"
>> -H "Content-Type: application/json" -H "X-Auth-Url:
>> https://identity.cncloud.com:5000/v2.0";
>> DEBUG (session) RESP:
>> DEBUG (v2) Making authentication request to
>> https://identity.cncloud.com:5000/v2.0/tokens
>> DEBUG (session) RESP:
>> Traceback (most recent call last):
>>   File "/usr/bin/heat", line 10, in 
>> sys.exit(main())
>>   File "/usr/lib/python2.7/dist-packages/heatclient/shell.py", line 706,
>> in main
>> HeatShell().main(args)
>>   File "/usr/lib/python2.7/dist-packages/heatclient/shell.py", line 656,
>> in main
>> args.func(client, args)
>>   File "/usr/lib/python2.7/dist-packages/heatclient/v1/shell.py", line
>> 581, in do_stack_list
>> utils.print_list(stacks, fields, sortby_index=3)
>>   File 
>> "/usr/lib/python2.7/dist-packages/heatclient/openstack/common/cliutils.py",
>> line 169, in print_list
>> for o in objs:
>>   File "/usr/lib/python2.7/dist-packages/heatclient/v1/stacks.py", line
>> 100, in paginate
>> stacks = self._list(url, 'stacks')
>>   File 
>> "/usr/lib/python2.7/dist-packages/heatclient/openstack/common/apiclient/base.py",
>> line 117, in _list
>> body = self.client.get(url).json()
>>   File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py",
>> line 292, in get
>> return self.client_request("GET", url, **kwargs)
>>   File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py",
>> line 285, in client_request
>> resp, body = self.json_request(method, url, **kwargs)
>>   File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py",
>> line 266, in json_request
>> resp = self._http_request(url, method, **kwargs)
>>   File "/usr/lib/python2.7/dist-packages/h

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[Davide Panarese]

If you use heat creadential for token request it works?

export OS_AUTH_URL=https://identity.cncloud.com:5000/v2.0 

export OS_REGION_NAME=RegionOne
export OS_USERNAME=heat
export OS_TENANT_NAME=services
export OS_PASSWORD=heat

keystone token-get 

Davide
> On 01 Feb 2017, at 10:10, NareshA kumar  wrote:
> 
> I have associated heat user to services tenant and gave it a admin role.
> 
> keystone user-role-list --user heat --tenant services
> +--+---+--+--+
> |id|  name | user_id  
> |tenant_id |
> +--+---+--+--+
> | 2b995253c23e4c1db8cd374346a4ecd4 | admin | 645eb7e9f04f4a2b8df65272a23c1394 
> | 024890084b7642e9b8535b52a86584ea |
> +--+---+--+--+
> 
> heat --debug stack-list
> 
> DEBUG (session) REQ: curl -g -i -X GET https://identity.cncloud.com:5000/v2.0 
>  -H "Accept: application/json" -H 
> "User-Agent: python-keystoneclient"
> DEBUG (session) RESP: [200] x-openstack-request-id: 
> req-2515497e-671b-475e-b48c-0cb6f2ccfe2f content-length: 347 via: 1.1 
> identity.cncloud.com:5000  
> access-control-expose-headers: Accept, Content-Type, X-Auth-Token, 
> X-Subject-Token vary: X-Auth-Token server: Apache/2.4.7 (Ubuntu) connection: 
> close access-control-allow-methods: GET POST OPTIONS PUT DELETE PATCH date: 
> Wed, 01 Feb 2017 09:07:01 GMT access-control-allow-origin: * 
> access-control-allow-headers: Accept, Content-Type, X-Auth-Token, 
> X-Subject-Token content-type: application/json x-distribution: Ubuntu 
> RESP BODY: {"version": {"status": "stable", "updated": 
> "2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type": 
> "application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links": 
> [{"href": "https://identity.cncloud.com:5000/v2.0/ 
> ", "rel": "self"}, {"href": 
> "http://docs.openstack.org/ ", "type": 
> "text/html", "rel": "describedby"}]}}
> 
> DEBUG (v2) Making authentication request to 
> https://identity.cncloud.com:5000/v2.0/tokens 
> 
> DEBUG (session) REQ: curl -g -i -X GET MailScanner warning: numerical links 
> are often malicious: 
> http://54.174.88.227:8004/v1/0c28d40bdcf0472d8dfb214a5c0286c4/stacks 
> ? -H 
> "Accept: application/json" -H "User-Agent: python-heatclient" -H 
> "X-Region-Name: RegionOne" -H "X-Auth-Token: 
> {SHA1}9cc75daaff59cdb14a75bfb74ca6d77ebb8d8ac6" -H "Content-Type: 
> application/json" -H "X-Auth-Url: https://identity.cncloud.com:5000/v2.0 
> "
> DEBUG (session) RESP:
> DEBUG (v2) Making authentication request to 
> https://identity.cncloud.com:5000/v2.0/tokens 
> 
> DEBUG (session) RESP:
> Traceback (most recent call last):
>   File "/usr/bin/heat", line 10, in 
> sys.exit(main())
>   File "/usr/lib/python2.7/dist-packages/heatclient/shell.py", line 706, in 
> main
> HeatShell().main(args)
>   File "/usr/lib/python2.7/dist-packages/heatclient/shell.py", line 656, in 
> main
> args.func(client, args)
>   File "/usr/lib/python2.7/dist-packages/heatclient/v1/shell.py", line 581, 
> in do_stack_list
> utils.print_list(stacks, fields, sortby_index=3)
>   File 
> "/usr/lib/python2.7/dist-packages/heatclient/openstack/common/cliutils.py", 
> line 169, in print_list
> for o in objs:
>   File "/usr/lib/python2.7/dist-packages/heatclient/v1/stacks.py", line 100, 
> in paginate
> stacks = self._list(url, 'stacks')
>   File 
> "/usr/lib/python2.7/dist-packages/heatclient/openstack/common/apiclient/base.py",
>  line 117, in _list
> body = self.client.get(url).json()
>   File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line 
> 292, in get
> return self.client_request("GET", url, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line 
> 285, in client_request
> resp, body = self.json_request(method, url, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line 
> 266, in json_request
> resp = self._http_request(url, method, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line 
> 361, in _http_request
> raise exc.from_response(resp)
> heatclient.exc.HTTPUnauthorized: ERROR: Authentication required
> 
> 
> Regards,
> NareshA.
> 
> On Wed, Feb 1, 2017 at 2:16 PM, Davide Panarese  > wrote:
> Could you debug heat

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[NareshA kumar]

I have associated heat user to services tenant and gave it a admin role.

keystone user-role-list --user heat --tenant services
+--+---+--+--+
|id|  name | user_id
   |tenant_id |
+--+---+--+--+
| 2b995253c23e4c1db8cd374346a4ecd4 | admin |
645eb7e9f04f4a2b8df65272a23c1394 | 024890084b7642e9b8535b52a86584ea |
+--+---+--+--+

heat --debug stack-list

DEBUG (session) REQ: curl -g -i -X GET
https://identity.cncloud.com:5000/v2.0 -H "Accept: application/json" -H
"User-Agent: python-keystoneclient"
DEBUG (session) RESP: [200] x-openstack-request-id:
req-2515497e-671b-475e-b48c-0cb6f2ccfe2f content-length: 347 via: 1.1
identity.cncloud.com:5000 access-control-expose-headers: Accept,
Content-Type, X-Auth-Token, X-Subject-Token vary: X-Auth-Token server:
Apache/2.4.7 (Ubuntu) connection: close access-control-allow-methods: GET
POST OPTIONS PUT DELETE PATCH date: Wed, 01 Feb 2017 09:07:01 GMT
access-control-allow-origin: * access-control-allow-headers: Accept,
Content-Type, X-Auth-Token, X-Subject-Token content-type: application/json
x-distribution: Ubuntu
RESP BODY: {"version": {"status": "stable", "updated":
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json",
"type": "application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0",
"links": [{"href": "https://identity.cncloud.com:5000/v2.0/";, "rel":
"self"}, {"href": "http://docs.openstack.org/";, "type": "text/html", "rel":
"describedby"}]}}

DEBUG (v2) Making authentication request to
https://identity.cncloud.com:5000/v2.0/tokens
DEBUG (session) REQ: curl -g -i -X GET
http://54.174.88.227:8004/v1/0c28d40bdcf0472d8dfb214a5c0286c4/stacks? -H
"Accept: application/json" -H "User-Agent: python-heatclient" -H
"X-Region-Name: RegionOne" -H "X-Auth-Token:
{SHA1}9cc75daaff59cdb14a75bfb74ca6d77ebb8d8ac6" -H "Content-Type:
application/json" -H "X-Auth-Url: https://identity.cncloud.com:5000/v2.0";
DEBUG (session) RESP:
DEBUG (v2) Making authentication request to
https://identity.cncloud.com:5000/v2.0/tokens
DEBUG (session) RESP:
Traceback (most recent call last):
  File "/usr/bin/heat", line 10, in 
sys.exit(main())
  File "/usr/lib/python2.7/dist-packages/heatclient/shell.py", line 706, in
main
HeatShell().main(args)
  File "/usr/lib/python2.7/dist-packages/heatclient/shell.py", line 656, in
main
args.func(client, args)
  File "/usr/lib/python2.7/dist-packages/heatclient/v1/shell.py", line 581,
in do_stack_list
utils.print_list(stacks, fields, sortby_index=3)
  File
"/usr/lib/python2.7/dist-packages/heatclient/openstack/common/cliutils.py",
line 169, in print_list
for o in objs:
  File "/usr/lib/python2.7/dist-packages/heatclient/v1/stacks.py", line
100, in paginate
stacks = self._list(url, 'stacks')
  File
"/usr/lib/python2.7/dist-packages/heatclient/openstack/common/apiclient/base.py",
line 117, in _list
body = self.client.get(url).json()
  File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line
292, in get
return self.client_request("GET", url, **kwargs)
  File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line
285, in client_request
resp, body = self.json_request(method, url, **kwargs)
  File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line
266, in json_request
resp = self._http_request(url, method, **kwargs)
  File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line
361, in _http_request
raise exc.from_response(resp)
heatclient.exc.HTTPUnauthorized: ERROR: Authentication required


Regards,
NareshA.

On Wed, Feb 1, 2017 at 2:16 PM, Davide Panarese  wrote:

> Could you debug heat api call with heat —debug stack-list?
> Did you associate heat user to service tenant and give it admin role?
>
> Davide
>
> On 31 Jan 2017, at 19:54, NareshA kumar  wrote:
>
> Hi,
> I am installing heat in kilo with keystone v2 APIs. As per document I have
> configured the endpoints and heat.conf. "heat stack-list" gives me
> Authentication required error. In heat-api.log I am seeing "Authorization
> failed for token" message.
> Can anyone help me solve this issue?
>
> Regards,
> NareshA.
>
> --
> Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non
> infetto.
> Clicca qui per segnalarlo come spam.
> 
> Clicca qui per metterlo in blacklist
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstac

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[Davide Panarese]

Could you debug heat api call with heat —debug stack-list?
Did you associate heat user to service tenant and give it admin role?

Davide
> On 31 Jan 2017, at 19:54, NareshA kumar  wrote:
> 
> Hi,
> I am installing heat in kilo with keystone v2 APIs. As per document I have 
> configured the endpoints and heat.conf. "heat stack-list" gives me 
> Authentication required error. In heat-api.log I am seeing "Authorization 
> failed for token" message. 
> Can anyone help me solve this issue?
> 
> Regards,
> NareshA.
> 
> -- 
> Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non 
> infetto. 
> Clicca qui per segnalarlo come spam. 
>  
> Clicca qui per metterlo in blacklist 
>  
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[NareshA kumar]

George,
Do you mean credentials used for heat? How to identify heat in keystone.
Can you please explain this part?

Regards,
NareshA


On 01-Feb-2017 2:16 AM, "George Shuklin"  wrote:

Try to identify youself against keystone with those credentials to if you
can get token. Use OS_* variables for this.

On 01/31/2017 09:48 PM, NareshA kumar wrote:

George,
I have created heat user and [keystoneauth] section looks like,

[keystone_authtoken]

# Complete public Identity API endpoint. (string value)
auth_uri = https://identity.cncloud.com:5000/v2.0
identity_url = https://identity.cncloud.com:35357
#memcached_servers = controller:11211
auth_type = password
admin_tenant_name = services
admin_user = heat
admin_password = heat

keystone user-list
| 3d15004f86e04424a9b5fb81935eac42 | glance|   True  |
glance@localhost|
| 645eb7e9f04f4a2b8df65272a23c1394 |  heat |   True  |
|
| d5cc6fa4d07d4198b6a2c580082d4169 |neutron|   True  |
 neutron@localhost|
| adfda15b5ec64accac2b92516a62d455 |  nova |   True  |
 nova@localhost |



Regards,
NareshA.

On Wed, Feb 1, 2017 at 12:56 AM, George Shuklin 
wrote:

> On 01/31/2017 08:54 PM, NareshA kumar wrote:
>
> Hi,
> I am installing heat in kilo with keystone v2 APIs. As per document I have
> configured the endpoints and heat.conf. "heat stack-list" gives me
> Authentication required error. In heat-api.log I am seeing "Authorization
> failed for token" message.
> Can anyone help me solve this issue?
>
> It may be that you didn't add heat user to keystone or didn't put it's
> credentials into [keystoneauth] section of config.
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[George Shuklin]

Try to identify youself against keystone with those credentials to if 
you can get token. Use OS_* variables for this.



On 01/31/2017 09:48 PM, NareshA kumar wrote:

George,
I have created heat user and [keystoneauth] section looks like,

[keystone_authtoken]

# Complete public Identity API endpoint. (string value)
auth_uri = https://identity.cncloud.com:5000/v2.0
identity_url = https://identity.cncloud.com:35357
#memcached_servers = controller:11211
auth_type = password
admin_tenant_name = services
admin_user = heat
admin_password = heat

keystone user-list
| 3d15004f86e04424a9b5fb81935eac42 | glance| True  | 
glance@localhost|
| 645eb7e9f04f4a2b8df65272a23c1394 |  heat | True  |   
  |
| d5cc6fa4d07d4198b6a2c580082d4169 |neutron| True  |   
 neutron@localhost|
| adfda15b5ec64accac2b92516a62d455 |  nova | True  | 
 nova@localhost |




Regards,
NareshA.

On Wed, Feb 1, 2017 at 12:56 AM, George Shuklin 
mailto:george.shuk...@gmail.com>> wrote:


On 01/31/2017 08:54 PM, NareshA kumar wrote:

Hi,
I am installing heat in kilo with keystone v2 APIs. As per
document I have configured the endpoints and heat.conf. "heat
stack-list" gives me Authentication required error. In
heat-api.log I am seeing "Authorization failed for token" message.
Can anyone help me solve this issue?


It may be that you didn't add heat user to keystone or didn't put
it's credentials into [keystoneauth] section of config.

___
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Post to : openstack@lists.openstack.org

Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack





___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[NareshA kumar]

George,
I have created heat user and [keystoneauth] section looks like,

[keystone_authtoken]

# Complete public Identity API endpoint. (string value)
auth_uri = https://identity.cncloud.com:5000/v2.0
identity_url = https://identity.cncloud.com:35357
#memcached_servers = controller:11211
auth_type = password
admin_tenant_name = services
admin_user = heat
admin_password = heat

keystone user-list
| 3d15004f86e04424a9b5fb81935eac42 | glance|   True  |
glance@localhost|
| 645eb7e9f04f4a2b8df65272a23c1394 |  heat |   True  |
|
| d5cc6fa4d07d4198b6a2c580082d4169 |neutron|   True  |
 neutron@localhost|
| adfda15b5ec64accac2b92516a62d455 |  nova |   True  |
 nova@localhost |



Regards,
NareshA.

On Wed, Feb 1, 2017 at 12:56 AM, George Shuklin 
wrote:

> On 01/31/2017 08:54 PM, NareshA kumar wrote:
>
> Hi,
> I am installing heat in kilo with keystone v2 APIs. As per document I have
> configured the endpoints and heat.conf. "heat stack-list" gives me
> Authentication required error. In heat-api.log I am seeing "Authorization
> failed for token" message.
> Can anyone help me solve this issue?
>
> It may be that you didn't add heat user to keystone or didn't put it's
> credentials into [keystoneauth] section of config.
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[George Shuklin]

On 01/31/2017 08:54 PM, NareshA kumar wrote:

Hi,
I am installing heat in kilo with keystone v2 APIs. As per document I 
have configured the endpoints and heat.conf. "heat stack-list" gives 
me Authentication required error. In heat-api.log I am seeing 
"Authorization failed for token" message.

Can anyone help me solve this issue?

It may be that you didn't add heat user to keystone or didn't put it's 
credentials into [keystoneauth] section of config.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Heat] Authentication required error in kilo with keystone v2 APIs

[NareshA kumar]

Hi,
I am installing heat in kilo with keystone v2 APIs. As per document I have
configured the endpoints and heat.conf. "heat stack-list" gives me
Authentication required error. In heat-api.log I am seeing "Authorization
failed for token" message.
Can anyone help me solve this issue?

Regards,
NareshA.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Seeing the execution log of a HOT deployment

[Nasir Mahmood]

Did you try to use  heat -d . option for debug?

On Dec 1, 2016 11:14 PM, "N Vivekanandan" 
wrote:

> Hi Heat Team,
>
>
>
> Can you please let us know if there is a way to see the
>
> execution log of a HOT execution that is done via stack-create?
>
>
>
> We would like to know which REST APIs were executed on openstack services
>
> as part of that HOT deployment (and which REST APIs failed with what
> status code) etc..
>
>
>
> --
>
> Thanks,
>
>
>
> Vivek
>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Heat] Seeing the execution log of a HOT deployment

[N Vivekanandan]

Hi Heat Team,

Can you please let us know if there is a way to see the
execution log of a HOT execution that is done via stack-create?

We would like to know which REST APIs were executed on openstack services
as part of that HOT deployment (and which REST APIs failed with what status 
code) etc..

--
Thanks,

Vivek

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Heat Index Number

[Turbo Fredriksson]

On Aug 21, 2016, at 1:14 AM, Brent Troge wrote:

> i was hoping there was an index tracker for the heat stack as well.

"the heat stack"?

What do you mean? You can create EVERYTHING from Heat. A set
of rules that creates this is called the "stack"..

Such as a Designate domain with records, Nova ports, Cinder
volumes, Neutron FWaaS with rules, Ceilometer alerts, etc, etc..


What do you mean with/by "index tracker for the heat stack"??
-- 
Med ett schysst järnrör slår man hela världen med häpnad
- Sockerconny


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Heat Index Number

[Brent Troge]

yeah the resource group %index% i am aware of.

i was hoping there was an index tracker for the heat stack as well.

On Sat, Aug 20, 2016 at 1:02 PM, Turbo Fredriksson  wrote:

> On Aug 20, 2016, at 6:30 PM, Brent Troge wrote:
>
> > Is there an internal variable that I can poll to expose the current
> > index/interation of a heat stack ?
>
> %index%
>
> But only for ResourceGroups. AutoScalingGroups don't have one :(.
>
> Example:
>
>   name: { list_join: ['-', [ { get_param: 'OS::stack_name' }, 'ldap',
> "%index%" ] ] }
> --
> If something's hard to do, then it's not worth doing.
> - Homer Simpson
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Heat Index Number

[Turbo Fredriksson]

On Aug 20, 2016, at 6:30 PM, Brent Troge wrote:

> Is there an internal variable that I can poll to expose the current
> index/interation of a heat stack ?

%index%

But only for ResourceGroups. AutoScalingGroups don't have one :(.

Example:

  name: { list_join: ['-', [ { get_param: 'OS::stack_name' }, 'ldap', "%index%" 
] ] }
--
If something's hard to do, then it's not worth doing.
- Homer Simpson


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Heat] Heat Index Number

[Brent Troge]

Is there an internal variable that I can poll to expose the current
index/interation of a heat stack ?

I know resource group has an internal variable to track the current group
index/iteration, but wondering if heat has something simlar.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [heat] Errors to be propagated as ReST http response

[Soumik Samanta]

In case of any heat error due to either bad template or error from the
nova/neutron, the heat client returns a description indicating the cause of
the error.
However, if ReST API is used, only 500 Internal Server Error response is
returned and the consumer has no clue of the cause of the error.

Though the error is logged in the heat-api.log, it would be extremely
helpful to the API consumers if a proper error message is returned in the
HTTP response.

I am using Kilo version of Heat
-- 
Regds
Soumik Samanta
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat template - retrieving a ports ID?

[Turbo Fredriksson]

On Aug 2, 2016, at 11:28 AM, Turbo Fredriksson wrote:

>  outputs:
>port:
>  value: { get_attr: [port, port_id] }
>  description: The port ID


If I try to use (the more obvious)

  value: { get_resource: port }

I get:

  Value must be a string

which I assume is because it's empty (i.e., wrong)?
-- 
Med ett schysst järnrör slår man hela världen med häpnad
- Sockerconny


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Heat template - retrieving a ports ID?

[Turbo Fredriksson]

Looking at

  
http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::FloatingIP

I see that one of the attributes ('exports'?) is:

  port_id
  ID of the port associated with this IP.

However, when trying to use that in an output:

  outputs:
port:
  value: { get_attr: [port, port_id] }
  description: The port ID

I get

  The Referenced Attribute (port port_id) is incorrect.

What did I miss?
--
You know, boys, a nuclear reactor is a lot like a woman.
You just have to read the manual and press the right buttons
- Homer Simpson


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat template - get port ID of 'external' instance

[Turbo Fredriksson]

Dang! Never mind. I was sure I've tried a 'string' type as the
input to volume, but apparently not..

Changing that, now it works.
--
Choose a job you love, and you will never have
to work a day in your life.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat template - get port ID of 'external' instance

[Turbo Fredriksson]

On Aug 1, 2016, at 4:41 PM, Turbo Fredriksson wrote:

>> You actually need to explicitly export the attributes you want as outputs 
>> from the instance.yaml template, just as you defined parameters to accept 
>> the property values.


This seems to mostly working, but i'm not sure how to 'export' the
instance UUID from "instance.yaml" to "volume.yaml" via "development.yaml"
(which is the 'primary' template):

  
https://github.com/FransUrbo/Openstack-Bayour.COM/blob/master/development.yaml#L41
  
https://github.com/FransUrbo/Openstack-Bayour.COM/blob/master/instance.yaml#L83
  https://github.com/FransUrbo/Openstack-Bayour.COM/blob/master/volume.yaml#L40

This give me

  Resource CREATE failed: ValueError: resources.volume: Value must be valid 
JSON: No JSON object could be decoded

I've also tried

  value: { get_attr: [instance, instance_uuid] }

=> The Referenced Attribute (instance instance_uuid) is incorrect.
--
God gave man both a penis and a brain,
but unfortunately not enough blood supply
to run both at the same time.
- R. Williams


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat template - get port ID of 'external' instance

[Turbo Fredriksson]

On Aug 1, 2016, at 3:53 PM, Zane Bitter wrote:

> BTW I really wouldn't recommend using the OS:: namespace for your own custom 
> types.

Thanx. I'll change that 'eventually' :).

>>  floating_network_id: physical
>> #  port_id: { get_attr: [admin, networks, { get_param: network }, 0, 
>> port]}
>> #  port_id: { get_attr: [admin, networks, 0, port]}
> 
> You want the second one.

It didn't work, that's why it's commented out. I got something like
'networks isn't available' or something to that affect.

> You actually need to explicitly export the attributes you want as outputs 
> from the instance.yaml template, just as you defined parameters to accept the 
> property values.

Ok, thanx!

>  heat resource-type-template -t hot -F yaml OS::Nova::Server


Cool! Wish I knew that this weekend :). Thanx, will come in handy
in the future..
--
Geologists recently discovered that "earthquakes" are
nothing more than Bruce Schneier and Chuck Norris
communicating via a roundhouse kick-based cryptosystem.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat template - get port ID of 'external' instance

[Zane Bitter]

On 31/07/16 10:39, Turbo Fredriksson wrote:

I've created a environment file:

  resource_registry:
"OS::Nova::Server::Instance": 
"https://raw.githubusercontent.com/FransUrbo/Openstack-Bayour.COM/master/instance.yaml";


BTW I really wouldn't recommend using the OS:: namespace for your own 
custom types.



I then create an instance from the template:

  admin_floating:
type: OS::Neutron::FloatingIP
description: LDAP/KRB5 Admin Floating IP
properties:
  floating_network_id: physical
#  port_id: { get_attr: [admin, networks, { get_param: network }, 0, port]}
#  port_id: { get_attr: [admin, networks, 0, port]}


You want the second one.


  admin:
type: OS::Nova::Server::Instance
properties:
  name: instance
  image: { get_param: image }
  size: 5
  flavor: m1.2tiny
  network: { get_param: network }


You're assuming here that doing get_attr on your provider resource will 
automatically reach into the nested stack and pull out the attributes of 
the resource you're thinking of - which of course would require Heat to 
be clairvoyant ;)


You actually need to explicitly export the attributes you want as 
outputs from the instance.yaml template, just as you defined parameters 
to accept the property values. To make this a bit easier, you can get 
the API to generate a template that you can modify with the command:


  heat resource-type-template -t hot -F yaml OS::Nova::Server

cheers,
Zane.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Heat template - get port ID of 'external' instance

[Turbo Fredriksson]

I've created a environment file:

  resource_registry:
"OS::Nova::Server::Instance": 
"https://raw.githubusercontent.com/FransUrbo/Openstack-Bayour.COM/master/instance.yaml";

I then create an instance from the template:

  admin_floating:
type: OS::Neutron::FloatingIP
description: LDAP/KRB5 Admin Floating IP
properties:
  floating_network_id: physical
#  port_id: { get_attr: [admin, networks, { get_param: network }, 0, port]}
#  port_id: { get_attr: [admin, networks, 0, port]}

  admin:
type: OS::Nova::Server::Instance
properties:
  name: instance
  image: { get_param: image }
  size: 5
  flavor: m1.2tiny
  network: { get_param: network }

The problem here is the 'port_id' of "admin_floating". I can't
seem to be able to get the port ID of the instance created..

If I don't rollback my stack, I can investigate the instance
using "openstack server show " and there's no network
or port in there..
--
If something's hard to do, then it's not worth doing.
- Homer Simpson


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat stack create

[Turbo Fredriksson]

On Jul 21, 2016, at 4:01 PM, Cavalcante, Franciraldo X wrote:

> You need to create the cloudformation endpoint.


Thanx.
--
There are no dumb questions,
unless a customer is asking them.
- Unknown


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat stack create

[Cavalcante, Franciraldo X]

Hey Turbo,

You need to create the cloudformation endpoint.

Here is a link that shows how to do it:
 


Regards,
\Franza


On 7/21/16, 7:21 AM, "Turbo Fredriksson"  wrote:

>I'm trying to setup Trove, to get DBaaS working. That uses
>Heat to do the orchestration.
>
>However, when trying to create a test stack in Heat
>
>  
>http://docs.openstack.org/icehouse/install-guide/install/yum/content/heat-
>verify.html
>
>I get:
>
>- s n i p -
>==> /var/log/heat/heat-engine.log <==
>2016-07-21 14:17:08.124 9011 INFO heat.engine.resource [-] CREATE: Server
>"server1" Stack "test-stack" [832fb9d6-3871-44be-8a3a-1745223d6cce]
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource Traceback (most
>recent call last):
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/heat/engine/resource.py", line 704, in
>_action_recorder
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource yield
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/heat/engine/resource.py", line 775, in
>_do_action
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource yield
>self.action_handler_task(action, args=handler_args)
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/heat/engine/scheduler.py", line 297, in
>wrapper
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource step =
>next(subtask)
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/heat/engine/resource.py", line 746, in
>action_handler_task
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource handler_data
>= handler(*args)
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/heat/engine/resources/openstack/nova/ser
>ver.py", line 818, in handle_create
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource
>user_data_format=user_data_format)
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/heat/engine/clients/os/nova.py", line
>378, in build_userdata
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource watch_url =
>heat_client_plugin.get_watch_server_url()
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/heat/engine/clients/os/heat_plugin.py",
>line 102, in get_watch_server_url
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource cfn_url =
>self.get_heat_cfn_url()
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/heat/engine/clients/os/heat_plugin.py",
>line 80, in get_heat_cfn_url
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource
>endpoint_type=endpoint_type)
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/heat/engine/clients/client_plugin.py",
>line 182, in url_for
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource url =
>get_endpoint()
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/heat/engine/clients/client_plugin.py",
>line 168, in get_endpoint
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource return
>auth_plugin.get_endpoint(self._keystone_session, **kwargs)
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/keystoneclient/auth/identity/base.py",
>line 341, in get_endpoint
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource
>service_name=service_name)
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/positional/__init__.py", line 94, in
>inner
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource return
>func(*args, **kwargs)
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File
>"/usr/lib/python2.7/dist-packages/keystoneclient/service_catalog.py",
>line 297, in url_for
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource raise
>exceptions.EndpointNotFound(msg)
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource EndpointNotFound:
>publicURL endpoint for cloudformation service not found
>2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource
>2016-07-21 14:17:08.191 9011 INFO heat.engine.service [-] Stack create
>failed, status FAILED
>2016-07-21 14:17:08.239 9011 INFO heat.engine.stack [-] Stack CREATE
>FAILED (test-stack): Resource CREATE failed: EndpointNotFound:
>resources.server1: publicURL endpoint for cloudformation service not found
>- s n i p -
>
>What is that 'publicURL endpoint for cloudformation service not found'
>part, and how/where do I configure it?
>-- 
>Try not. Do. Or do not. There is no try!
>- Yoda
>
>
>___
>Mailing list: 
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>Post to : openstack@lists.openstack.org
>Unsubscribe : 

[Openstack] Heat stack create

[Turbo Fredriksson]

I'm trying to setup Trove, to get DBaaS working. That uses
Heat to do the orchestration.

However, when trying to create a test stack in Heat

  
http://docs.openstack.org/icehouse/install-guide/install/yum/content/heat-verify.html

I get:

- s n i p -
==> /var/log/heat/heat-engine.log <==
2016-07-21 14:17:08.124 9011 INFO heat.engine.resource [-] CREATE: Server 
"server1" Stack "test-stack" [832fb9d6-3871-44be-8a3a-1745223d6cce]
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource Traceback (most recent 
call last):
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/resource.py", line 704, in 
_action_recorder
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource yield
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/resource.py", line 775, in 
_do_action
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource yield 
self.action_handler_task(action, args=handler_args)
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/scheduler.py", line 297, in 
wrapper
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource step = next(subtask)
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/resource.py", line 746, in 
action_handler_task
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource handler_data = 
handler(*args)
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/resources/openstack/nova/server.py",
 line 818, in handle_create
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource 
user_data_format=user_data_format)
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/clients/os/nova.py", line 378, in 
build_userdata
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource watch_url = 
heat_client_plugin.get_watch_server_url()
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/clients/os/heat_plugin.py", line 
102, in get_watch_server_url
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource cfn_url = 
self.get_heat_cfn_url()
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/clients/os/heat_plugin.py", line 
80, in get_heat_cfn_url
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource 
endpoint_type=endpoint_type)
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/clients/client_plugin.py", line 
182, in url_for
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource url = get_endpoint()
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/clients/client_plugin.py", line 
168, in get_endpoint
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource return 
auth_plugin.get_endpoint(self._keystone_session, **kwargs)
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/auth/identity/base.py", line 
341, in get_endpoint
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource 
service_name=service_name)
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/positional/__init__.py", line 94, in inner
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource return func(*args, 
**kwargs)
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/service_catalog.py", line 297, 
in url_for
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource raise 
exceptions.EndpointNotFound(msg)
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource EndpointNotFound: 
publicURL endpoint for cloudformation service not found
2016-07-21 14:17:08.124 9011 ERROR heat.engine.resource
2016-07-21 14:17:08.191 9011 INFO heat.engine.service [-] Stack create failed, 
status FAILED
2016-07-21 14:17:08.239 9011 INFO heat.engine.stack [-] Stack CREATE FAILED 
(test-stack): Resource CREATE failed: EndpointNotFound: resources.server1: 
publicURL endpoint for cloudformation service not found
- s n i p -

What is that 'publicURL endpoint for cloudformation service not found'
part, and how/where do I configure it?
-- 
Try not. Do. Or do not. There is no try!
- Yoda


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat] Heat-stack deletion and re-creation

[ESWAR RAO]

Hi All,

Below are some observations:

(1) Delete existing stack
(2) Re-create heat stack again with same stack-name and with same template
as part of some kind of healing

But , when heat-engine is trying to create stack, there's again DELETE
operation on same stack-name and creation is getting FAILED.

If I keep some delay between (1) and (2) then stack re-creation is going
fine.


 stack-delete operation 

2016-07-15 15:32:31.910 3069 DEBUG root [-] JSON response : {"stack":
{"disable_rollback": true, "description": "HOT template to create  network
service\n", "parameters": {"right-net-id":
"5756a23c-e28f-4b99-a48c-bb5b9d2774fd", "OS::stack_id":
"8a8bb460-761c-4151-b4cb-bdf992b09c41", "OS::stack_name":
"TEST-4ed70f4e-c4fd-49db-a6cd-30133a1daa17", "nsid":
"4ed70f4e-c4fd-49db-a6cd-30133a1daa17", "mgmt-net-id":
"25e0c2b9-c99a-4c9c-9ee5-e2d89b703358", "left-subnet-cidr": "80.0.0.0/24"},
"stack_status_reason": "Stack DELETE started", "stack_name":
"NSO-4ed70f4e-c4fd-49db-a6cd-30133a1daa17", "creation_time":
"2016-07-15T09:57:46Z", "links": [{"href": "
http://10.210.6.32:8004/v1/5c193081803c48c3a02f4f6986ba979f/stacks/
TEST-4ed70f4e-c4fd-49db-a6cd-30133a1daa17/8a8bb460-761c-4151-b4cb-bdf992b09c41",
"rel": "self"}], "capabilities": [], "notification_topics": [],
"timeout_mins": null, "stack_status": "DELETE_IN_PROGRESS", "updated_time":
"2016-07-15T10:01:59Z", "id": "8a8bb460-761c-4151-b4cb-bdf992b09c41",
"template_description": "HOT template to create  network service\n"}}
to_json /usr/lib/python2.7/dist-packages/heat/common/wsgi.py:577


 stack-get returned NotFound 

2016-07-15 15:32:46.918 3069 DEBUG heat.api.middleware.version_negotiation
[-] Processing request: GET
/v1/5c193081803c48c3a02f4f6986ba979f/stacks/TEST-4ed70f4e-c4fd-49db-a6cd-30133a1daa17
Accept:
application/json process_request
/usr/lib/python2.7/dist-packages/heat/api/middleware/version_negotiation.py:53

2016-07-15 15:32:46.978 3069 DEBUG root [-] JSON response : {"explanation":
"The resource could not be found.", "code": 404, "error": {"message": "The
Stack (TEST-4ed70f4e-c4fd-49db-a6cd-30133a1daa17) could not be found.",
"traceback": "Traceback (most recent call last):\n\n  File
\"/usr/lib/python2.7/dist-packages/heat/engine/service.py\", line 63, in
wrapped\nreturn func(self, ctx, *args, **kwargs)\n\n  File
\"/usr/lib/python2.7/dist-packages/heat/engine/service.py\", line 336, in
identify_stack\nraise
exception.StackNotFound(stack_name=stack_name)\n\nStackNotFound: The Stack
(TEST-4ed70f4e-c4fd-49db-a6cd-30133a1daa17) could not be found.\n", "type":
"StackNotFound"}, "title": "Not Found"} to_json
/usr/lib/python2.7/dist-packages/heat/common/wsgi.py:577

 CREATION request 

2016-07-15 15:33:05.974 3069 DEBUG root [-] JSON response : {"stack":
{"disable_rollback": true, "description": "HOT template to create  network
service\n", "parameters": {"right-net-id":
"5756a23c-e28f-4b99-a48c-bb5b9d2774fd", "OS::stack_id":
"e97f118a-7e1a-46be-a680-10fa98c65abf", "OS::stack_name":
"TEST-4ed70f4e-c4fd-49db-a6cd-30133a1daa17", "nsid":
"4ed70f4e-c4fd-49db-a6cd-30133a1daa17", "mgmt-net-id":
"25e0c2b9-c99a-4c9c-9ee5-e2d89b703358", "left-subnet-cidr": "80.0.0.0/24"},
"stack_status_reason": "Stack CREATE started", "stack_name":
"NSO-4ed70f4e-c4fd-49db-a6cd-30133a1daa17", "creation_time":
"2016-07-15T10:03:05Z", "links": [{"href": "
http://10.210.6.32:8004/v1/5c193081803c48c3a02f4f6986ba979f/stacks/
TEST-4ed70f4e-c4fd-49db-a6cd-30133a1daa17/e97f118a-7e1a-46be-a680-10fa98c65abf",
"rel": "self"}], "capabilities": [], "notification_topics": [],
"timeout_mins": null, "stack_status": "CREATE_IN_PROGRESS", "updated_time":
null, "id": "e97f118a-7e1a-46be-a680-10fa98c65abf", "template_description":
"HOT template to create  network service\n"}} to_json
/usr/lib/python2.7/dist-packages/heat/common/wsgi.py:577

 BUT again DELETE 

2016-07-15 15:33:06.132 3069 DEBUG heat.api.middleware.version_negotiation
[-] Processing request: DELETE
/v1/5c193081803c48c3a02f4f6986ba979f/stacks/TEST-4ed70f4e-c4fd-49db-a6cd-30133a1daa17/e97f118a-7e1a-46be-a680-10fa98c65abf
Accept: */* process_request
/usr/lib/python2.7/dist-packages/heat/api/middleware/version_negotiation.py:53


Thanks



On Fri, Jul 15, 2016 at 9:15 PM, ESWAR RAO  wrote:

> Hi All,
>
>
> After deleting the heat-stack , I am polling until the stack is DELETED.
>
> I am following below way of polling until stack-get fails with
> HTTPNotFound Exception.
>
> Is there any other better way of checking whether stack is DELETED instead
> of catching exception.
>
> >>> from heatclient.client import Client
>
> heat_client = Client('1', endpoint=heat_url, token=auth_token)
>
> heat_client.stacks.

[Openstack] [Heat] Heat-stack deletion and status

[ESWAR RAO]

Hi All,


After deleting the heat-stack , I am polling until the stack is DELETED.

I am following below way of polling until stack-get fails with HTTPNotFound
Exception.

Is there any other better way of checking whether stack is DELETED instead
of catching exception.

>>> from heatclient.client import Client

heat_client = Client('1', endpoint=heat_url, token=auth_token)

heat_client.stacks.delete(stack_name)


**poll loop**

try:

stack_get = heat_client.stacks.get(stack_name)

except (heatexception.HTTPNotFound):

# stack is deleted

if 'IN_PROGRESS' in stack_get.status:

   # sleep and again loop

*


Thanks

Eswar
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] heat stack failed , ConnectionError: Unable to establish connection: ('Connection aborted.', BadStatusLine("''", ))

[Kamsali, Raghavendrachari]

Hi Thanks for the reply,

Not only cinder issue , also getting same error some time with neutron port 
creation time and some time it is with nova;
+--+---+--+-+---++-+
|  Binary  |  Host | Zone |  Status | State | Updated_at
 | Disabled Reason |
+--+---+--+-+---++-+
| cinder-scheduler | host3 | nova | enabled |   up  | 
2016-07-15T00:30:08.00 |-|
| cinder-scheduler | host4 | nova | enabled |   up  | 
2016-07-15T00:30:18.00 |-|
| cinder-scheduler | host5 | nova | enabled |   up  | 
2016-07-15T00:30:08.00 |-|
|  cinder-volume   | host1 | nova | enabled |   up  | 
2016-07-15T00:30:08.00 |-|
|  cinder-volume   | host2 | nova | enabled |   up  | 
2016-07-15T00:30:08.00 |-|








From: Brent Troge [mailto:brenttroge2...@gmail.com]
Sent: Thursday, July 14, 2016 8:36 PM
To: Kamsali, Raghavendrachari 
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] heat stack failed , ConnectionError: Unable to 
establish connection: ('Connection aborted.', BadStatusLine("''", ))

Does this only occur when creating a cinder volume ?
If you just create a VM without creating volumes, what is the outcome ?
At face value it looks like the cinder services are not available.
cinder service-list



On Thu, Jul 14, 2016 at 7:17 AM, Kamsali, Raghavendrachari 
mailto:raghavendrachari.kams...@hpe.com>> 
wrote:
Hi,

Am trying to launch heat stack , in the middle of the creating am getting error 
and stack failed .


2016-07-14 00:27:27.301 40107 INFO heat.engine.stack [-] Stack CREATE 
IN_PROGRESS (opnfv_cw): Stack CREATE started
2016-07-14 00:27:27.557 40107 INFO heat.engine.resource [-] creating 
CinderVolume "volume5" Stack "opnfv_cw" [54d10ecc-e9d7-49fe-b0ca-dae26449bccb]
2016-07-14 00:27:28.240 40107 INFO heat.engine.clients.os.cinder [-] Creating 
Cinder client with volume API version 2.
2016-07-14 00:27:30.324 40107 INFO heat.engine.resource [-] creating 
CinderVolume "volume2" Stack "opnfv_cw" [54d10ecc-e9d7-49fe-b0ca-dae26449bccb]
2016-07-14 00:27:32.144 40098 INFO heat.engine.service 
[req-ccbc7bf8-e5e6-443d-aa11-61df9be533a3 - -] Service 
c1adfa2d-cc66-44d2-a0f6-240b00805169 is updated
2016-07-14 00:27:32.257 40104 INFO heat.engine.service 
[req-e0606cb0-29a8-4262-9e33-58467c3d6c18 - -] Service 
6169f661-9972-491e-a315-61a158797357 is updated
2016-07-14 00:27:32.349 40099 INFO heat.engine.service 
[req-306f847e-9562-4916-b61f-5d25c97c16fb - -] Service 
80fff45e-6c4e-493c-8c95-2d1aea09e9a8 is updated
2016-07-14 00:27:32.491 40101 INFO heat.engine.service 
[req-8fddf522-14a6-4296-b560-b7e8cbce49a0 - -] Service 
9bf6cff0-5656-48e5-b2ad-55fd71e7610e is updated
2016-07-14 00:27:34.567 40102 INFO heat.engine.service 
[req-efeb68c4-88d2-47fb-967f-e85691c4d4be - -] Service 
2bfbe1de-63dc-4db6-9367-a95e3f3cc611 is updated
2016-07-14 00:27:34.935 40105 INFO heat.engine.service 
[req-51890740-6f33-44d8-ac58-9443d1d55bb6 - -] Service 
89586269-3183-4288-a7b1-d724d15ba2c5 is updated
2016-07-14 00:27:35.046 40106 INFO heat.engine.service 
[req-702870f5-8720-46e0-9310-d390e7eacf23 - -] Service 
5c58c90c-0d90-4800-81cc-4649a822d98a is updated
2016-07-14 00:27:35.127 40103 INFO heat.engine.service 
[req-9ae5fcee-86c6-4305-a052-ee919725c3fa - -] Service 
7cebe82b-42ee-40bb-9e7d-8344f2793203 is updated
2016-07-14 00:27:35.277 40107 INFO heat.engine.service 
[req-d8f2aaf3-69bd-4674-94e3-be0146cad307 - -] Service 
1c19833e-4d3d-48d4-b6e5-d84c61fd5663 is updated
2016-07-14 00:27:38.678 40135 INFO heat.engine.service 
[req-3e4ee334-d09b-44d0-a3f5-02845d2ce756 - -] Service 
e3adaeb9-e68c-444a-b021-4a922c7cf21c is updated
2016-07-14 00:27:38.778 40110 INFO heat.engine.service 
[req-0b77a507-ebb2-48da-b803-616368793119 - -] Service 
70b1433c-4d73-42a8-b5d7-75dc9ef896d0 is updated
2016-07-14 00:27:38.922 40114 INFO heat.engine.service 
[req-aeac47e3-85d6-42ee-934d-64421ddfe6ee - -] Service 
c4cee34a-ccd3-4864-8407-0eee574543f1 is updated
2016-07-14 00:27:39.078 40129 INFO heat.engine.service 
[req-1c804362-5996-49c2-bfe5-a9f1a650aa57 - -] Service 
3484a3b7-6381-4c8b-babd-4190e07f4fb6 is updated
2016-07-14 00:27:39.155 40113 INFO heat.engine.service 
[req-08915cf1-0bb0-46e6-a611-ccf02cebc4a1 - -] Service 
43049010-97e8-49c7-b16d-da4b690aa983 is updated
2016-07-14 00:27:39.262 40112 INFO heat.engine.service 
[req-9a9f3531-bbaf-4e98-ad68-9b7643b1a4e7 - -] Service 
71468276-5928-4786-a610-2fffddfc4cbd is updated
2016-07-14 00:27:39.363 40115 INFO heat.engine.service 
[req-7d07e9de-210c-416a-9fb1-45e97e304676 - -] Service 
5e0fdf17-bb5f-434c-8457-34d9da915b80 is updated
2016-07-14 00:27:39.455 40134 INFO heat.engine.service 
[req-63745b8d-26cf-4825-b7a3-1d8b0722d183 - -] Service 
a0838b

Re: [Openstack] heat stack failed , ConnectionError: Unable to establish connection: ('Connection aborted.', BadStatusLine("''", ))

[Brent Troge]

Does this only occur when creating a cinder volume ?

If you just create a VM without creating volumes, what is the outcome ?

At face value it looks like the cinder services are not available.

cinder service-list




On Thu, Jul 14, 2016 at 7:17 AM, Kamsali, Raghavendrachari <
raghavendrachari.kams...@hpe.com> wrote:

> Hi,
>
>
>
> Am trying to launch heat stack , in the middle of the creating am getting
> error and stack failed .
>
>
>
>
>
> 2016-07-14 00:27:27.301 40107 INFO heat.engine.stack [-] Stack CREATE
> IN_PROGRESS (opnfv_cw): Stack CREATE started
>
> 2016-07-14 00:27:27.557 40107 INFO heat.engine.resource [-] creating
> CinderVolume "volume5" Stack "opnfv_cw"
> [54d10ecc-e9d7-49fe-b0ca-dae26449bccb]
>
> 2016-07-14 00:27:28.240 40107 INFO heat.engine.clients.os.cinder [-]
> Creating Cinder client with volume API version 2.
>
> 2016-07-14 00:27:30.324 40107 INFO heat.engine.resource [-] creating
> CinderVolume "volume2" Stack "opnfv_cw"
> [54d10ecc-e9d7-49fe-b0ca-dae26449bccb]
>
> 2016-07-14 00:27:32.144 40098 INFO heat.engine.service
> [req-ccbc7bf8-e5e6-443d-aa11-61df9be533a3 - -] Service
> c1adfa2d-cc66-44d2-a0f6-240b00805169 is updated
>
> 2016-07-14 00:27:32.257 40104 INFO heat.engine.service
> [req-e0606cb0-29a8-4262-9e33-58467c3d6c18 - -] Service
> 6169f661-9972-491e-a315-61a158797357 is updated
>
> 2016-07-14 00:27:32.349 40099 INFO heat.engine.service
> [req-306f847e-9562-4916-b61f-5d25c97c16fb - -] Service
> 80fff45e-6c4e-493c-8c95-2d1aea09e9a8 is updated
>
> 2016-07-14 00:27:32.491 40101 INFO heat.engine.service
> [req-8fddf522-14a6-4296-b560-b7e8cbce49a0 - -] Service
> 9bf6cff0-5656-48e5-b2ad-55fd71e7610e is updated
>
> 2016-07-14 00:27:34.567 40102 INFO heat.engine.service
> [req-efeb68c4-88d2-47fb-967f-e85691c4d4be - -] Service
> 2bfbe1de-63dc-4db6-9367-a95e3f3cc611 is updated
>
> 2016-07-14 00:27:34.935 40105 INFO heat.engine.service
> [req-51890740-6f33-44d8-ac58-9443d1d55bb6 - -] Service
> 89586269-3183-4288-a7b1-d724d15ba2c5 is updated
>
> 2016-07-14 00:27:35.046 40106 INFO heat.engine.service
> [req-702870f5-8720-46e0-9310-d390e7eacf23 - -] Service
> 5c58c90c-0d90-4800-81cc-4649a822d98a is updated
>
> 2016-07-14 00:27:35.127 40103 INFO heat.engine.service
> [req-9ae5fcee-86c6-4305-a052-ee919725c3fa - -] Service
> 7cebe82b-42ee-40bb-9e7d-8344f2793203 is updated
>
> 2016-07-14 00:27:35.277 40107 INFO heat.engine.service
> [req-d8f2aaf3-69bd-4674-94e3-be0146cad307 - -] Service
> 1c19833e-4d3d-48d4-b6e5-d84c61fd5663 is updated
>
> 2016-07-14 00:27:38.678 40135 INFO heat.engine.service
> [req-3e4ee334-d09b-44d0-a3f5-02845d2ce756 - -] Service
> e3adaeb9-e68c-444a-b021-4a922c7cf21c is updated
>
> 2016-07-14 00:27:38.778 40110 INFO heat.engine.service
> [req-0b77a507-ebb2-48da-b803-616368793119 - -] Service
> 70b1433c-4d73-42a8-b5d7-75dc9ef896d0 is updated
>
> 2016-07-14 00:27:38.922 40114 INFO heat.engine.service
> [req-aeac47e3-85d6-42ee-934d-64421ddfe6ee - -] Service
> c4cee34a-ccd3-4864-8407-0eee574543f1 is updated
>
> 2016-07-14 00:27:39.078 40129 INFO heat.engine.service
> [req-1c804362-5996-49c2-bfe5-a9f1a650aa57 - -] Service
> 3484a3b7-6381-4c8b-babd-4190e07f4fb6 is updated
>
> 2016-07-14 00:27:39.155 40113 INFO heat.engine.service
> [req-08915cf1-0bb0-46e6-a611-ccf02cebc4a1 - -] Service
> 43049010-97e8-49c7-b16d-da4b690aa983 is updated
>
> 2016-07-14 00:27:39.262 40112 INFO heat.engine.service
> [req-9a9f3531-bbaf-4e98-ad68-9b7643b1a4e7 - -] Service
> 71468276-5928-4786-a610-2fffddfc4cbd is updated
>
> 2016-07-14 00:27:39.363 40115 INFO heat.engine.service
> [req-7d07e9de-210c-416a-9fb1-45e97e304676 - -] Service
> 5e0fdf17-bb5f-434c-8457-34d9da915b80 is updated
>
> 2016-07-14 00:27:39.455 40134 INFO heat.engine.service
> [req-63745b8d-26cf-4825-b7a3-1d8b0722d183 - -] Service
> a0838b11-fcdc-4803-99a4-c083046e9cc9 is updated
>
> 2016-07-14 00:27:39.521 40121 INFO heat.engine.service
> [req-7905a259-17d0-4b0c-9017-ce7f93b0e46f - -] Service
> 9cd09edb-364b-4e00-bb09-aeee13afe805 is updated
>
> 2016-07-14 00:27:39.621 40133 INFO heat.engine.service
> [req-5a02e254-c3b6-4a7f-8c23-9aa49de7ec3d - -] Service
> 756bdce5-3c04-4018-905c-5cf5b22a6cd0 is updated
>
> 2016-07-14 00:27:39.713 40117 INFO heat.engine.service
> [req-8abce8de-82c9-42e4-8ab3-3cc8228ba28d - -] Service
> 10960c1a-5c82-49a9-974d-06e3159a2f6b is updated
>
> 2016-07-14 00:27:39.789 40131 INFO heat.engine.service
> [req-f1590f18-e352-4375-92d5-530c11db6e5b - -] Service
> 0b790835-ae32-4fa5-a7f0-2ef09e6e687f is updated
>
> 2016-07-14 00:27:39.864 40111 INFO heat.engine.service
> [req-6972ece7-b3e3-4e5d-8e92-7111f21ca0cb - -] Service
> 8e251462-707d-4130-8eb0-6b18dc655cdf is updated
>
> 2016-07-14 00:27:40.006 40108 INFO heat.engine.service
> [req-fe701c68-8909-45fb-a098-9832bf7bf53f - -] Service
> 1093bddb-b67f-42b6-849f-ef54ca80a56c is updated
>
> 2016-07-14 00:27:40.098 40124 INFO heat.engine.service
> [req-c4783dae-72e6-405a-b691-3dce116e4ece - -] Service
> b7b2eaea-4b50-4b08-9730-300e565340f8 is updated
>
> 2016-07-

[Openstack] [openstack][heat] heat stack failed , ConnectionError: Unable to establish connection: ('Connection aborted.', BadStatusLine("''", ))

[Kamsali, Raghavendrachari]

Hi,

Am trying to launch heat stack , in the middle of the creating am getting error 
and stack failed .


2016-07-14 00:27:27.301 40107 INFO heat.engine.stack [-] Stack CREATE 
IN_PROGRESS (opnfv_cw): Stack CREATE started
2016-07-14 00:27:27.557 40107 INFO heat.engine.resource [-] creating 
CinderVolume "volume5" Stack "opnfv_cw" [54d10ecc-e9d7-49fe-b0ca-dae26449bccb]
2016-07-14 00:27:28.240 40107 INFO heat.engine.clients.os.cinder [-] Creating 
Cinder client with volume API version 2.
2016-07-14 00:27:30.324 40107 INFO heat.engine.resource [-] creating 
CinderVolume "volume2" Stack "opnfv_cw" [54d10ecc-e9d7-49fe-b0ca-dae26449bccb]
2016-07-14 00:27:32.144 40098 INFO heat.engine.service 
[req-ccbc7bf8-e5e6-443d-aa11-61df9be533a3 - -] Service 
c1adfa2d-cc66-44d2-a0f6-240b00805169 is updated
2016-07-14 00:27:32.257 40104 INFO heat.engine.service 
[req-e0606cb0-29a8-4262-9e33-58467c3d6c18 - -] Service 
6169f661-9972-491e-a315-61a158797357 is updated
2016-07-14 00:27:32.349 40099 INFO heat.engine.service 
[req-306f847e-9562-4916-b61f-5d25c97c16fb - -] Service 
80fff45e-6c4e-493c-8c95-2d1aea09e9a8 is updated
2016-07-14 00:27:32.491 40101 INFO heat.engine.service 
[req-8fddf522-14a6-4296-b560-b7e8cbce49a0 - -] Service 
9bf6cff0-5656-48e5-b2ad-55fd71e7610e is updated
2016-07-14 00:27:34.567 40102 INFO heat.engine.service 
[req-efeb68c4-88d2-47fb-967f-e85691c4d4be - -] Service 
2bfbe1de-63dc-4db6-9367-a95e3f3cc611 is updated
2016-07-14 00:27:34.935 40105 INFO heat.engine.service 
[req-51890740-6f33-44d8-ac58-9443d1d55bb6 - -] Service 
89586269-3183-4288-a7b1-d724d15ba2c5 is updated
2016-07-14 00:27:35.046 40106 INFO heat.engine.service 
[req-702870f5-8720-46e0-9310-d390e7eacf23 - -] Service 
5c58c90c-0d90-4800-81cc-4649a822d98a is updated
2016-07-14 00:27:35.127 40103 INFO heat.engine.service 
[req-9ae5fcee-86c6-4305-a052-ee919725c3fa - -] Service 
7cebe82b-42ee-40bb-9e7d-8344f2793203 is updated
2016-07-14 00:27:35.277 40107 INFO heat.engine.service 
[req-d8f2aaf3-69bd-4674-94e3-be0146cad307 - -] Service 
1c19833e-4d3d-48d4-b6e5-d84c61fd5663 is updated
2016-07-14 00:27:38.678 40135 INFO heat.engine.service 
[req-3e4ee334-d09b-44d0-a3f5-02845d2ce756 - -] Service 
e3adaeb9-e68c-444a-b021-4a922c7cf21c is updated
2016-07-14 00:27:38.778 40110 INFO heat.engine.service 
[req-0b77a507-ebb2-48da-b803-616368793119 - -] Service 
70b1433c-4d73-42a8-b5d7-75dc9ef896d0 is updated
2016-07-14 00:27:38.922 40114 INFO heat.engine.service 
[req-aeac47e3-85d6-42ee-934d-64421ddfe6ee - -] Service 
c4cee34a-ccd3-4864-8407-0eee574543f1 is updated
2016-07-14 00:27:39.078 40129 INFO heat.engine.service 
[req-1c804362-5996-49c2-bfe5-a9f1a650aa57 - -] Service 
3484a3b7-6381-4c8b-babd-4190e07f4fb6 is updated
2016-07-14 00:27:39.155 40113 INFO heat.engine.service 
[req-08915cf1-0bb0-46e6-a611-ccf02cebc4a1 - -] Service 
43049010-97e8-49c7-b16d-da4b690aa983 is updated
2016-07-14 00:27:39.262 40112 INFO heat.engine.service 
[req-9a9f3531-bbaf-4e98-ad68-9b7643b1a4e7 - -] Service 
71468276-5928-4786-a610-2fffddfc4cbd is updated
2016-07-14 00:27:39.363 40115 INFO heat.engine.service 
[req-7d07e9de-210c-416a-9fb1-45e97e304676 - -] Service 
5e0fdf17-bb5f-434c-8457-34d9da915b80 is updated
2016-07-14 00:27:39.455 40134 INFO heat.engine.service 
[req-63745b8d-26cf-4825-b7a3-1d8b0722d183 - -] Service 
a0838b11-fcdc-4803-99a4-c083046e9cc9 is updated
2016-07-14 00:27:39.521 40121 INFO heat.engine.service 
[req-7905a259-17d0-4b0c-9017-ce7f93b0e46f - -] Service 
9cd09edb-364b-4e00-bb09-aeee13afe805 is updated
2016-07-14 00:27:39.621 40133 INFO heat.engine.service 
[req-5a02e254-c3b6-4a7f-8c23-9aa49de7ec3d - -] Service 
756bdce5-3c04-4018-905c-5cf5b22a6cd0 is updated
2016-07-14 00:27:39.713 40117 INFO heat.engine.service 
[req-8abce8de-82c9-42e4-8ab3-3cc8228ba28d - -] Service 
10960c1a-5c82-49a9-974d-06e3159a2f6b is updated
2016-07-14 00:27:39.789 40131 INFO heat.engine.service 
[req-f1590f18-e352-4375-92d5-530c11db6e5b - -] Service 
0b790835-ae32-4fa5-a7f0-2ef09e6e687f is updated
2016-07-14 00:27:39.864 40111 INFO heat.engine.service 
[req-6972ece7-b3e3-4e5d-8e92-7111f21ca0cb - -] Service 
8e251462-707d-4130-8eb0-6b18dc655cdf is updated
2016-07-14 00:27:40.006 40108 INFO heat.engine.service 
[req-fe701c68-8909-45fb-a098-9832bf7bf53f - -] Service 
1093bddb-b67f-42b6-849f-ef54ca80a56c is updated
2016-07-14 00:27:40.098 40124 INFO heat.engine.service 
[req-c4783dae-72e6-405a-b691-3dce116e4ece - -] Service 
b7b2eaea-4b50-4b08-9730-300e565340f8 is updated
2016-07-14 00:28:22.146 40107 INFO heat.engine.resource [-] CREATE: 
CinderVolume "volume2" Stack "opnfv_cw" [54d10ecc-e9d7-49fe-b0ca-dae26449bccb]
2016-07-14 00:28:22.146 40107 ERROR heat.engine.resource Traceback (most recent 
call last):
2016-07-14 00:28:22.146 40107 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/resource.py", line 612, in 
_action_recorder
2016-07-14 00:28:22.146 40107 ERROR heat.engine.resource yield
2016-07-14 00:28:22.146 40107 ERROR heat.engine.resou

[Openstack] heat stack failed , ConnectionError: Unable to establish connection: ('Connection aborted.', BadStatusLine("''", ))

[Kamsali, Raghavendrachari]

Hi,

Am trying to launch heat stack , in the middle of the creating am getting error 
and stack failed .


2016-07-14 00:27:27.301 40107 INFO heat.engine.stack [-] Stack CREATE 
IN_PROGRESS (opnfv_cw): Stack CREATE started
2016-07-14 00:27:27.557 40107 INFO heat.engine.resource [-] creating 
CinderVolume "volume5" Stack "opnfv_cw" [54d10ecc-e9d7-49fe-b0ca-dae26449bccb]
2016-07-14 00:27:28.240 40107 INFO heat.engine.clients.os.cinder [-] Creating 
Cinder client with volume API version 2.
2016-07-14 00:27:30.324 40107 INFO heat.engine.resource [-] creating 
CinderVolume "volume2" Stack "opnfv_cw" [54d10ecc-e9d7-49fe-b0ca-dae26449bccb]
2016-07-14 00:27:32.144 40098 INFO heat.engine.service 
[req-ccbc7bf8-e5e6-443d-aa11-61df9be533a3 - -] Service 
c1adfa2d-cc66-44d2-a0f6-240b00805169 is updated
2016-07-14 00:27:32.257 40104 INFO heat.engine.service 
[req-e0606cb0-29a8-4262-9e33-58467c3d6c18 - -] Service 
6169f661-9972-491e-a315-61a158797357 is updated
2016-07-14 00:27:32.349 40099 INFO heat.engine.service 
[req-306f847e-9562-4916-b61f-5d25c97c16fb - -] Service 
80fff45e-6c4e-493c-8c95-2d1aea09e9a8 is updated
2016-07-14 00:27:32.491 40101 INFO heat.engine.service 
[req-8fddf522-14a6-4296-b560-b7e8cbce49a0 - -] Service 
9bf6cff0-5656-48e5-b2ad-55fd71e7610e is updated
2016-07-14 00:27:34.567 40102 INFO heat.engine.service 
[req-efeb68c4-88d2-47fb-967f-e85691c4d4be - -] Service 
2bfbe1de-63dc-4db6-9367-a95e3f3cc611 is updated
2016-07-14 00:27:34.935 40105 INFO heat.engine.service 
[req-51890740-6f33-44d8-ac58-9443d1d55bb6 - -] Service 
89586269-3183-4288-a7b1-d724d15ba2c5 is updated
2016-07-14 00:27:35.046 40106 INFO heat.engine.service 
[req-702870f5-8720-46e0-9310-d390e7eacf23 - -] Service 
5c58c90c-0d90-4800-81cc-4649a822d98a is updated
2016-07-14 00:27:35.127 40103 INFO heat.engine.service 
[req-9ae5fcee-86c6-4305-a052-ee919725c3fa - -] Service 
7cebe82b-42ee-40bb-9e7d-8344f2793203 is updated
2016-07-14 00:27:35.277 40107 INFO heat.engine.service 
[req-d8f2aaf3-69bd-4674-94e3-be0146cad307 - -] Service 
1c19833e-4d3d-48d4-b6e5-d84c61fd5663 is updated
2016-07-14 00:27:38.678 40135 INFO heat.engine.service 
[req-3e4ee334-d09b-44d0-a3f5-02845d2ce756 - -] Service 
e3adaeb9-e68c-444a-b021-4a922c7cf21c is updated
2016-07-14 00:27:38.778 40110 INFO heat.engine.service 
[req-0b77a507-ebb2-48da-b803-616368793119 - -] Service 
70b1433c-4d73-42a8-b5d7-75dc9ef896d0 is updated
2016-07-14 00:27:38.922 40114 INFO heat.engine.service 
[req-aeac47e3-85d6-42ee-934d-64421ddfe6ee - -] Service 
c4cee34a-ccd3-4864-8407-0eee574543f1 is updated
2016-07-14 00:27:39.078 40129 INFO heat.engine.service 
[req-1c804362-5996-49c2-bfe5-a9f1a650aa57 - -] Service 
3484a3b7-6381-4c8b-babd-4190e07f4fb6 is updated
2016-07-14 00:27:39.155 40113 INFO heat.engine.service 
[req-08915cf1-0bb0-46e6-a611-ccf02cebc4a1 - -] Service 
43049010-97e8-49c7-b16d-da4b690aa983 is updated
2016-07-14 00:27:39.262 40112 INFO heat.engine.service 
[req-9a9f3531-bbaf-4e98-ad68-9b7643b1a4e7 - -] Service 
71468276-5928-4786-a610-2fffddfc4cbd is updated
2016-07-14 00:27:39.363 40115 INFO heat.engine.service 
[req-7d07e9de-210c-416a-9fb1-45e97e304676 - -] Service 
5e0fdf17-bb5f-434c-8457-34d9da915b80 is updated
2016-07-14 00:27:39.455 40134 INFO heat.engine.service 
[req-63745b8d-26cf-4825-b7a3-1d8b0722d183 - -] Service 
a0838b11-fcdc-4803-99a4-c083046e9cc9 is updated
2016-07-14 00:27:39.521 40121 INFO heat.engine.service 
[req-7905a259-17d0-4b0c-9017-ce7f93b0e46f - -] Service 
9cd09edb-364b-4e00-bb09-aeee13afe805 is updated
2016-07-14 00:27:39.621 40133 INFO heat.engine.service 
[req-5a02e254-c3b6-4a7f-8c23-9aa49de7ec3d - -] Service 
756bdce5-3c04-4018-905c-5cf5b22a6cd0 is updated
2016-07-14 00:27:39.713 40117 INFO heat.engine.service 
[req-8abce8de-82c9-42e4-8ab3-3cc8228ba28d - -] Service 
10960c1a-5c82-49a9-974d-06e3159a2f6b is updated
2016-07-14 00:27:39.789 40131 INFO heat.engine.service 
[req-f1590f18-e352-4375-92d5-530c11db6e5b - -] Service 
0b790835-ae32-4fa5-a7f0-2ef09e6e687f is updated
2016-07-14 00:27:39.864 40111 INFO heat.engine.service 
[req-6972ece7-b3e3-4e5d-8e92-7111f21ca0cb - -] Service 
8e251462-707d-4130-8eb0-6b18dc655cdf is updated
2016-07-14 00:27:40.006 40108 INFO heat.engine.service 
[req-fe701c68-8909-45fb-a098-9832bf7bf53f - -] Service 
1093bddb-b67f-42b6-849f-ef54ca80a56c is updated
2016-07-14 00:27:40.098 40124 INFO heat.engine.service 
[req-c4783dae-72e6-405a-b691-3dce116e4ece - -] Service 
b7b2eaea-4b50-4b08-9730-300e565340f8 is updated
2016-07-14 00:28:22.146 40107 INFO heat.engine.resource [-] CREATE: 
CinderVolume "volume2" Stack "opnfv_cw" [54d10ecc-e9d7-49fe-b0ca-dae26449bccb]
2016-07-14 00:28:22.146 40107 ERROR heat.engine.resource Traceback (most recent 
call last):
2016-07-14 00:28:22.146 40107 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/dist-packages/heat/engine/resource.py", line 612, in 
_action_recorder
2016-07-14 00:28:22.146 40107 ERROR heat.engine.resource yield
2016-07-14 00:28:22.146 40107 ERROR heat.engine.resour

[Openstack] heat: assign a port to instance without ip address

[openstack]

Dear lists,

i setup an instance with heat, which is accessible per ssh. So fine so 
good. But this instance should have more network interfaces with 
dedicated virtual networks.


i tried to assign a port to an instance without assigning an ip address.
But neutron does this always beginning with the first available
subnet address.

I tried to setup the network without a subnet but then heat complains
that it needs a fixed address:


ERROR heat.engine.resource ResourceFailure: BadRequest: 
resources.instance_fw_int_master.resources.instance_fw_int: Port 
94954e9b-3847-40e0-8bce-a71f648e5cf9 requires a FixedIP in order to be used.



I really do not need the layer3 stuff like dhcp and so on. A layer 2, 
like a switch/bridge is almost sufficient. Configuring ip addressing 
will be done with saltstack


My Setup is a 3-node (one
controller, two compute nodes) setup on CentOS 7 with Openstack Liberty.
I setup neutron with self-service networks option using Linux-Bridge.

Regards,

Joerg

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat][nova][cinder]Mount a CD-ROM ISO to an instance

[pnkk]

Thank you both!
Eugen, I thought of checking if we can use this iso as a block device by
specifying the device type as cdom
Pavlo, will try out to see how it works, thanks for the links

Regards,
Kanthi

On Fri, Jun 10, 2016 at 1:45 PM, Pavlo Shchelokovskyy <
pshchelokovs...@mirantis.com> wrote:

> Hi,
>
> do you mean the configdrive? It is iso9660 filesystem image attached to vm
> on boot by Nova and containing the bootstrap configuration for VM and is
> used by cloud-init [0]
>
> You can force creation of configdrive for a particular instance via Heat
> template too [1]
>
> [0] http://docs.openstack.org/user-guide/cli_config_drive.html
> [1]
> http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::Server-prop-config_drive
>
> Cheers,
>
> Dr. Pavlo Shchelokovskyy
> Senior Software Engineer
> Mirantis Inc
> www.mirantis.com
>
> On Thu, Jun 9, 2016 at 11:20 AM, pnkk  wrote:
>
>> Hi,
>>
>> Can you please suggest a way to mount a cdrom iso to a instance during
>> boot time along with the actual image.
>>
>> That iso has the bootstrap configuration needed for the VM.
>>
>> Regards,
>> Kanthi
>>
>>
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat][nova][cinder]Mount a CD-ROM ISO to an instance

[Pavlo Shchelokovskyy]

Hi,

do you mean the configdrive? It is iso9660 filesystem image attached to vm
on boot by Nova and containing the bootstrap configuration for VM and is
used by cloud-init [0]

You can force creation of configdrive for a particular instance via Heat
template too [1]

[0] http://docs.openstack.org/user-guide/cli_config_drive.html
[1]
http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::Server-prop-config_drive

Cheers,

Dr. Pavlo Shchelokovskyy
Senior Software Engineer
Mirantis Inc
www.mirantis.com

On Thu, Jun 9, 2016 at 11:20 AM, pnkk  wrote:

> Hi,
>
> Can you please suggest a way to mount a cdrom iso to a instance during
> boot time along with the actual image.
>
> That iso has the bootstrap configuration needed for the VM.
>
> Regards,
> Kanthi
>
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat][nova][cinder]Mount a CD-ROM ISO to an instance

[Eugen Block]

Hi,


mount a cdrom iso to a instance during boot
time along with the actual image.


do you mean to mount an iso when creating an instance or when an  
existing instance is booting?
If you have an existing instance you can attach a previously created  
volume (from that ISO) to your instance, and that volume stays  
attached even if you reboot your instance.


I don't think you can attach an ISO during creation, I may be wrong though.

Regards,
Eugen

Zitat von pnkk :


Hi,

Can you please suggest a way to mount a cdrom iso to a instance during boot
time along with the actual image.

That iso has the bootstrap configuration needed for the VM.

Regards,
Kanthi



--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [heat][nova][cinder]Mount a CD-ROM ISO to an instance

[pnkk]

Hi,

Can you please suggest a way to mount a cdrom iso to a instance during boot
time along with the actual image.

That iso has the bootstrap configuration needed for the VM.

Regards,
Kanthi
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat create-stack fails.

[Michael Van Der Beek]

Hi Eugen,

Yes I think I was mixing it up.
I've used the Mitaka guide now.

Got past orchestra now.
Can't get the telemetry to work.  Keeps giving me a blank list.
[root@controller ceilometer]# ceilometer meter-list
+--+--+--+-+-++
| Name | Type | Unit | Resource ID | User ID | Project ID |
+--+--+--+-+-++
+--+--+--+-+-++

Seems ceilometer tries to connect to aodh but thinks it is not responding.
2016-06-06 16:29:45.973 7743 WARNING ceilometer.api.controllers.v2.root [-] 
Can't connect to keystone, assuming aodh is disabled and retry later.

Aodh has an error.
2016-06-06 16:26:14.008 7423 ERROR aodh.evaluator ProgrammingError: 
(pymysql.err.ProgrammingError) (1146, u"Table 'aodh.alarm' doesn't exist") 
[SQL: u'SELECT alarm.alarm_id AS alarm_alarm_id, alarm.enabled AS 
alarm_enabled, alarm.name AS alarm_name, alarm.type AS alarm_type, 
alarm.severity AS alarm_severity, alarm.description AS alarm_description, 
alarm.timestamp AS alarm_timestamp, alarm.user_id AS alarm_user_id, 
alarm.project_id AS alarm_project_id, alarm.state AS alarm_state, 
alarm.state_timestamp AS alarm_state_timestamp, alarm.ok_actions AS 
alarm_ok_actions, alarm.alarm_actions AS alarm_alarm_actions, 
alarm.insufficient_data_actions AS alarm_insufficient_data_actions, 
alarm.repeat_actions AS alarm_repeat_actions, alarm.rule AS alarm_rule, 
alarm.time_constraints AS alarm_time_constraints \nFROM alarm \nWHERE 
alarm.enabled = true AND alarm.type != %s ORDER BY alarm.timestamp DESC'] 
[parameters: ('event',)]

But the database shows that the tables are present but has no records.
MariaDB [aodh]> show tables;
+-+
| Tables_in_aodh  |
+-+
| alarm   |
| alarm_history   |
| alembic_version |
+-+
3 rows in set (0.00 sec)

MariaDB [aodh]> select * from alarm;
Empty set (0.00 sec)

MariaDB [aodh]> select * from alarm_history;
Empty set (0.00 sec)

MariaDB [aodh]> select * from alembic_version;
+-+
| version_num |
+-+
| bb07adac380 |
+-+
1 row in set (0.01 sec)

I used the aodh-dbsync to create the tables. So I assume that is right. But not 
sure if the tables are suppose to blank.

Not much documented on what is supposed to be there as a default value in the 
tables.

Tried to create an instance anyway, using network type 2. 
Somehow the create provider network command is missing from the docs.
It starts off assuming that it was already created.. so tried to create it, 
messed it up abit.. trying to reverse that now.

Regards,

Michael
-Original Message-
From: Eugen Block [mailto:ebl...@nde.ag] 
Sent: Monday, June 6, 2016 3:04 PM
To: Michael Van Der Beek 
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Heat create-stack fails.

Hi Michael,

your statements regarding the Openstack version don't fit.

> I've been following the install guide found at 
> http://docs.openstack.org/juno/install-guide/install/yum/content/ch_pr
> eface.html

and

> I've only just started the openstack installation a couple of weeks 
> ago. So I'm using the latest install instructions. Definitely not an 
> upgrade.

sound like a mismatch to me.
Since you wrote that you use Juno install guide I assume that you don't use the 
latest version, that would be Mitaka. Here is the respective install guide for 
Red Hat and CentOS:  
http://docs.openstack.org/mitaka/install-guide-rdo.

Regards,
Eugen


Zitat von Michael Van Der Beek :

> Hi Engen,
>
> Yes the m1.tiny does exist.
> [root@controller ~]# nova flavor-list
> ++---+---+--+---+--+---+-+---+
> | ID | Name  | Memory_MB | Disk | Ephemeral | Swap | VCPUs |  
> RXTX_Factor | Is_Public |
> ++---+---+--+---+--+---+-+---+
> | 1  | m1.tiny   | 512   | 1| 0 |  | 1 | 1.0  
> | True  |
> | 2  | m1.small  | 2048  | 20   | 0 |  | 1 | 1.0  
> | True  |
> | 3  | m1.medium | 4096  | 40   | 0 |  | 2 | 1.0  
> | True  |
> | 4  | m1.large  | 8192  | 80   | 0 |  | 4 | 1.0  
> | True  |
> | 5  | m1.xlarge | 16384 | 160  | 0 |  | 8 | 1.0  
> | True  |
> ++---+---+--+---+--+---+-+---+
>
> So I don't know why it was reporting that either. The dashboard also 
> reports the same flavor list.
>
> I've only just started the openstack installation a couple of weeks 
> ago. So I'm using the latest install instructions. Definitely not an 
> upgrade.
> Even then som

Re: [Openstack] Heat create-stack fails.

[Eugen Block]

Hi Michael,

your statements regarding the Openstack version don't fit.


I've been following the install guide found at
http://docs.openstack.org/juno/install-guide/install/yum/content/ch_preface.html


and

I've only just started the openstack installation a couple of weeks  
ago. So I'm using the latest install instructions. Definitely not an  
upgrade.


sound like a mismatch to me.
Since you wrote that you use Juno install guide I assume that you  
don't use the latest version, that would be Mitaka. Here is the  
respective install guide for Red Hat and CentOS:  
http://docs.openstack.org/mitaka/install-guide-rdo.


Regards,
Eugen


Zitat von Michael Van Der Beek :


Hi Engen,

Yes the m1.tiny does exist.
[root@controller ~]# nova flavor-list
++---+---+--+---+--+---+-+---+
| ID | Name  | Memory_MB | Disk | Ephemeral | Swap | VCPUs |  
RXTX_Factor | Is_Public |

++---+---+--+---+--+---+-+---+
| 1  | m1.tiny   | 512   | 1| 0 |  | 1 | 1.0  
| True  |
| 2  | m1.small  | 2048  | 20   | 0 |  | 1 | 1.0  
| True  |
| 3  | m1.medium | 4096  | 40   | 0 |  | 2 | 1.0  
| True  |
| 4  | m1.large  | 8192  | 80   | 0 |  | 4 | 1.0  
| True  |
| 5  | m1.xlarge | 16384 | 160  | 0 |  | 8 | 1.0  
| True  |

++---+---+--+---+--+---+-+---+

So I don't know why it was reporting that either. The dashboard also  
reports the same flavor list.


I've only just started the openstack installation a couple of weeks  
ago. So I'm using the latest install instructions. Definitely not an  
upgrade.
Even then some commands have changed, so I had to look up new  
equivalents. Even the config file changes, some are not documented,
For example, vnc now has a separate [vnc] previously it was under  
[DEFAULT]. Hence, I do not know if the installation guide is  
pointing me to the correct installation locations.


Hence my problems with this. The have been upgrades to various  
pieces of software but guide has not been updated.


As a newbie at this, its hard to know what is correct or not, for  
two reasons, versions keep changing so rapidly, anything I google  
for may not exist anymore or may cause problems with the new  
installs. Secondly, there are no suggests as to what to do when  
certain configs fail.
I've already correct about 7-8 difference that causes it to fail.   
Like, if you don't configure the hostname correctly or specify in  
the config files, all of them report back to the controller as  
localhost.localdomain. This wasn't in the installation guide, I  
googled for a solution for this.


My guess is that once this Orchestra part is finish, I should have a  
basic working system.


Regards,

Michael
-Original Message-
From: Eugen Block [mailto:ebl...@nde.ag]
Sent: Friday, June 3, 2016 6:25 PM
To: Michael Van Der Beek 
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Heat create-stack fails.

So you have another config option you have to provide for all  
relevant services. Either you do this step by step changing one file  
after another and watch the logs to see the next failing option. Or  
you scan through the install guide to edit alle configs at once  
before restarting the servies.



HTTP exception thrown: Flavor m1.tiny could not be found.


You should also make sure that requested flavor exists.

Just out of curiosity, you're following the Juno install guide, is  
it possible that you have a mismatch between the version of the  
install guide and the Openstack version you actually installed? Or  
did you try a dist-upgrade? I upgraded from Liberty to Mitaka,  
that's where I had to change all config files according to the newer  
versions.

However, you'll have to edit all your configs matching the installed version.

Regards,
Eugen


Zitat von Michael Van Der Beek :


Hi Eugen,

Thanks for your help.

Had pretty interesting results.
I've added auth_type in the keystone section of glance.
[keystone_authtoken]
auth_uri = http://controller:5000/v2.0 identity_uri =
http://controller:35357 admin_tenant_name = service admin_user =
glance admin_password = a4b249a2373e72d7b869 #auth_type=password Had
the auth_type uncommented.

The it created an error starting.
glance MissingRequiredOptions: Auth plugin requires parameters which
were not given: auth_url

This seems to have also happened in heat-api.conf, cinder.conf,
nova.conf,neutron.conf Once the auth_type is removed from the
keystone_authtoken section all the service seems to start.

I have put auth_type everywhere else like in your file list you’ve
provided in the previous email.

Now I get a totally different error from the

Re: [Openstack] Heat create-stack fails.

[Michael Van Der Beek]

Hi Eugen,

Thanks for your help. I think I'm going to do a full reinstall again.

Just in case I missed something stupid.

Regards,

Michael

-Original Message-
From: Eugen Block [mailto:ebl...@nde.ag] 
Sent: Friday, June 3, 2016 6:25 PM
To: Michael Van Der Beek 
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Heat create-stack fails.

So you have another config option you have to provide for all relevant 
services. Either you do this step by step changing one file after another and 
watch the logs to see the next failing option. Or you scan through the install 
guide to edit alle configs at once before restarting the servies.

> HTTP exception thrown: Flavor m1.tiny could not be found.

You should also make sure that requested flavor exists.

Just out of curiosity, you're following the Juno install guide, is it possible 
that you have a mismatch between the version of the install guide and the 
Openstack version you actually installed? Or did you try a dist-upgrade? I 
upgraded from Liberty to Mitaka, that's where I had to change all config files 
according to the newer versions.
However, you'll have to edit all your configs matching the installed version.

Regards,
Eugen


Zitat von Michael Van Der Beek :

> Hi Eugen,
>
> Thanks for your help.
>
> Had pretty interesting results.
> I've added auth_type in the keystone section of glance.
> [keystone_authtoken]
> auth_uri = http://controller:5000/v2.0 identity_uri = 
> http://controller:35357 admin_tenant_name = service admin_user = 
> glance admin_password = a4b249a2373e72d7b869 #auth_type=password Had 
> the auth_type uncommented.
>
> The it created an error starting.
> glance MissingRequiredOptions: Auth plugin requires parameters which 
> were not given: auth_url
>
> This seems to have also happened in heat-api.conf, cinder.conf, 
> nova.conf,neutron.conf Once the auth_type is removed from the 
> keystone_authtoken section all the service seems to start.
>
> I have put auth_type everywhere else like in your file list you’ve 
> provided in the previous email.
>
> Now I get a totally different error from the stack-create.
> heat stack-create -f /root/test-stack.yml -P 
> "ImageID=cirros-0.3.3-x86_64;NetID=$NET_ID" testStack
>
> After a bit:
> [root@controller nova]# heat stack-list
> +--++---+-+--+
> | id   | stack_name | stack_status   
> | creation_time   | updated_time |
> +--++---+-+--+
> | a811426c-19f3-49bd-9e54-03400ccc13f5 | testStack  | CREATE_FAILED  
> | 2016-06-03T09:23:57 | None |
> +--++---+-+--+
>
> So I'm back to the failed creation. But the error is different this time.
>
> 2016-06-03 17:19:00.669 3174 INFO heat.engine.service 
> [req-1e70cc60-8d60-4090-b572-34fb003f5d1f - admin - default default] 
> Creating stack testStack
> 2016-06-03 17:19:00.700 3174 INFO heat.engine.resource 
> [req-1e70cc60-8d60-4090-b572-34fb003f5d1f - admin - default default] 
> Validating Server "server"
> 2016-06-03 17:19:00.701 3174 WARNING heat.engine.rsrc_defn 
> [req-1e70cc60-8d60-4090-b572-34fb003f5d1f - admin - default default] 
> Reading the ResourceDefinition as if it were a snippet of a 
> CloudFormation template is deprecated, and the ability to treat it as 
> such will be removed in the future. Resource plugins should use the 
> ResourceDefinition API to work with the definition of the resource 
> instance.
> 2016-06-03 17:19:00.701 3174 WARNING heat.engine.rsrc_defn 
> [req-1e70cc60-8d60-4090-b572-34fb003f5d1f - admin - default default] 
> Reading the ResourceDefinition as if it were a snippet of a 
> CloudFormation template is deprecated, and the ability to treat it as 
> such will be removed in the future. Resource plugins should use the 
> ResourceDefinition API to work with the definition of the resource 
> instance.
> 2016-06-03 17:19:00.702 3174 WARNING heat.engine.rsrc_defn 
> [req-1e70cc60-8d60-4090-b572-34fb003f5d1f - admin - default default] 
> Reading the ResourceDefinition as if it were a snippet of a 
> CloudFormation template is deprecated, and the ability to treat it as 
> such will be removed in the future. Resource plugins should use the 
> ResourceDefinition API to work with the definition of the resource 
> instance.
> 2016-06-03 17:19:01.915 3174 WARNING heat.common.context 
> [req-1e70cc60-8d60-4090-b572-34fb003f5d1f - admin - default default] 
> Using the keystone_authtoken user as the heat trustee user directly is 
>

Re: [Openstack] Heat create-stack fails.

[Michael Van Der Beek]

Hi Engen,

Yes the m1.tiny does exist.
[root@controller ~]# nova flavor-list
++---+---+--+---+--+---+-+---+
| ID | Name  | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | 
Is_Public |
++---+---+--+---+--+---+-+---+
| 1  | m1.tiny   | 512   | 1| 0 |  | 1 | 1.0 | 
True  |
| 2  | m1.small  | 2048  | 20   | 0 |  | 1 | 1.0 | 
True  |
| 3  | m1.medium | 4096  | 40   | 0 |  | 2 | 1.0 | 
True  |
| 4  | m1.large  | 8192  | 80   | 0 |  | 4 | 1.0 | 
True  |
| 5  | m1.xlarge | 16384 | 160  | 0 |  | 8 | 1.0 | 
True  |
++---+---+--+---+--+---+-+---+

So I don't know why it was reporting that either. The dashboard also reports 
the same flavor list.

I've only just started the openstack installation a couple of weeks ago. So I'm 
using the latest install instructions. Definitely not an upgrade.
Even then some commands have changed, so I had to look up new equivalents. Even 
the config file changes, some are not documented,
For example, vnc now has a separate [vnc] previously it was under [DEFAULT]. 
Hence, I do not know if the installation guide is pointing me to the correct 
installation locations.

Hence my problems with this. The have been upgrades to various pieces of 
software but guide has not been updated.

As a newbie at this, its hard to know what is correct or not, for two reasons, 
versions keep changing so rapidly, anything I google for may not exist anymore 
or may cause problems with the new installs. Secondly, there are no suggests as 
to what to do when certain configs fail.
I've already correct about 7-8 difference that causes it to fail.  Like, if you 
don't configure the hostname correctly or specify in the config files, all of 
them report back to the controller as localhost.localdomain. This wasn't in the 
installation guide, I googled for a solution for this.

My guess is that once this Orchestra part is finish, I should have a basic 
working system.

Regards,

Michael
-Original Message-
From: Eugen Block [mailto:ebl...@nde.ag] 
Sent: Friday, June 3, 2016 6:25 PM
To: Michael Van Der Beek 
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Heat create-stack fails.

So you have another config option you have to provide for all relevant 
services. Either you do this step by step changing one file after another and 
watch the logs to see the next failing option. Or you scan through the install 
guide to edit alle configs at once before restarting the servies.

> HTTP exception thrown: Flavor m1.tiny could not be found.

You should also make sure that requested flavor exists.

Just out of curiosity, you're following the Juno install guide, is it possible 
that you have a mismatch between the version of the install guide and the 
Openstack version you actually installed? Or did you try a dist-upgrade? I 
upgraded from Liberty to Mitaka, that's where I had to change all config files 
according to the newer versions.
However, you'll have to edit all your configs matching the installed version.

Regards,
Eugen


Zitat von Michael Van Der Beek :

> Hi Eugen,
>
> Thanks for your help.
>
> Had pretty interesting results.
> I've added auth_type in the keystone section of glance.
> [keystone_authtoken]
> auth_uri = http://controller:5000/v2.0 identity_uri = 
> http://controller:35357 admin_tenant_name = service admin_user = 
> glance admin_password = a4b249a2373e72d7b869 #auth_type=password Had 
> the auth_type uncommented.
>
> The it created an error starting.
> glance MissingRequiredOptions: Auth plugin requires parameters which 
> were not given: auth_url
>
> This seems to have also happened in heat-api.conf, cinder.conf, 
> nova.conf,neutron.conf Once the auth_type is removed from the 
> keystone_authtoken section all the service seems to start.
>
> I have put auth_type everywhere else like in your file list you’ve 
> provided in the previous email.
>
> Now I get a totally different error from the stack-create.
> heat stack-create -f /root/test-stack.yml -P 
> "ImageID=cirros-0.3.3-x86_64;NetID=$NET_ID" testStack
>
> After a bit:
> [root@controller nova]# heat stack-list
> +--++---+-+--+
> | id   | stack_name | stack_status   
> | creation_time   | updated_time |
> +--++---+-+--+
> | a811426c-19f3-49bd-9e54-03400ccc13f5 | testStack  | CREATE_FAILED  
> | 

Re: [Openstack] Heat create-stack fails.

[Eugen Block]

k_server_group_quota)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions
File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line  
1139, in _create_instance
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
 reservation_id, max_count)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions
File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line  
866, in _validate_and_build_base_options
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
 pci_request_info, requested_networks)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions
File  
"/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py",  
line 1062, in create_pci_requests_for_sriov_ports
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
 neutron = get_client(context, admin=True)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions
File  
"/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py",  
line 139, in get_client
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
 _ADMIN_AUTH = _load_auth_plugin(CONF)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions
File  
"/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py",  
line 114, in _load_auth_plugin
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
 auth_plugin = ks_loading.load_auth_from_conf_options(conf,  
NEUTRON_GROUP)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions
File  
"/usr/lib/python2.7/site-packages/keystoneauth1/loading/conf.py",  
line 135, in load_from_conf_options
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
 return plugin.load_from_options_getter(_getter, **kwargs)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions
File  
"/usr/lib/python2.7/site-packages/keystoneauth1/loading/base.py",  
line 148, in load_from_options_getter
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
 return self.load_from_options(**kwargs)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions
File  
"/usr/lib/python2.7/site-packages/keystoneauth1/loading/base.py",  
line 123, in load_from_options
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
 raise exceptions.MissingRequiredOptions(missing_required)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions  
MissingRequiredOptions: Auth plugin requires parameters which were  
not given: auth_url

2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions
2016-06-03 17:23:59.310 12059 INFO nova.api.openstack.wsgi  
[req-b8f7ce5b-8db8-402d-b9bc-3e55d7c4a360  
6b7fa6d27fc046dc8e991c25aa4a01c8 fd3a0ca3acf14106b4f45adaa8b0f0f8 -  
- -] HTTP exception thrown: Unexpected API Error. Please report this  
at http://bugs.launchpad.net/nova/ and attach the Nova API log if  
possible.


2016-06-03 17:23:59.312 12059 INFO nova.osapi_compute.wsgi.server  
[req-b8f7ce5b-8db8-402d-b9bc-3e55d7c4a360  
6b7fa6d27fc046dc8e991c25aa4a01c8 fd3a0ca3acf14106b4f45adaa8b0f0f8 -  
- -] 10.20.1.71 "POST /v2/fd3a0ca3acf14106b4f45adaa8b0f0f8/servers  
HTTP/1.1" status: 500 len: 465 time: 0.5185332



-Original Message-
From: Eugen Block [mailto:ebl...@nde.ag]
Sent: Friday, June 3, 2016 4:23 PM
To: Michael Van Der Beek 
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Heat create-stack fails.

There are several places to define the auth_type, basically for  
every openstack service like glance, cinder, neutron etc.

On controller node, the nova.conf contains two sections with auth_type.

[keystone_authtoken]
auth_type = password
username = nova
...
[neutron]
username = neutron
auth_type = password
...

But there is also the compute node, nova.conf:

[keystone_authtoken]
auth_type = password
username = nova
...
[neutron]
auth_type = password
username = neutron
...

So I assume you'll have to change all your configs, on my controller  
there are 7 configs containing auth_type, both neutron.conf and  
nova.conf contain two different sections as stated above:


control1:~ # egrep -rve "^#|^$" /etc/ | grep auth_type  
/etc/glance/glance-registry.conf:auth_type = password  
/etc/glance/glance-api.conf:auth_type = password  
/etc/neutron/neutron.conf:auth_type = password  
/etc/neutron/neutron.conf:auth_type = password  
/etc/nova/nova.conf:auth_type = password  
/etc/nova/nova.conf:auth_type = password  
/etc/cinder/cinder.conf:auth_type = password  
/etc/ceilometer/ceilometer.conf:auth_type = password  
/etc/heat/heat.conf:auth_type = password


On one of my compute nodes there are three configs, nova.conf also  
containing two different sections:


compute1:~ # egrep -rve "#|^$" /etc/ | grep auth_type  
/etc/nova/nova.conf:auth_type = password  
/etc/nova/nova.conf:auth_

Re: [Openstack] Heat create-stack fails.

[Michael Van Der Beek]

06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 114, in 
_load_auth_plugin
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
auth_plugin = ks_loading.load_auth_from_conf_options(conf, NEUTRON_GROUP)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/keystoneauth1/loading/conf.py", line 135, in 
load_from_conf_options
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions return 
plugin.load_from_options_getter(_getter, **kwargs)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/keystoneauth1/loading/base.py", line 148, in 
load_from_options_getter
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions return 
self.load_from_options(**kwargs)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/keystoneauth1/loading/base.py", line 123, in 
load_from_options
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions raise 
exceptions.MissingRequiredOptions(missing_required)
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
MissingRequiredOptions: Auth plugin requires parameters which were not given: 
auth_url
2016-06-03 17:23:59.305 12059 ERROR nova.api.openstack.extensions 
2016-06-03 17:23:59.310 12059 INFO nova.api.openstack.wsgi 
[req-b8f7ce5b-8db8-402d-b9bc-3e55d7c4a360 6b7fa6d27fc046dc8e991c25aa4a01c8 
fd3a0ca3acf14106b4f45adaa8b0f0f8 - - -] HTTP exception thrown: Unexpected API 
Error. Please report this at http://bugs.launchpad.net/nova/ and attach the 
Nova API log if possible.

2016-06-03 17:23:59.312 12059 INFO nova.osapi_compute.wsgi.server 
[req-b8f7ce5b-8db8-402d-b9bc-3e55d7c4a360 6b7fa6d27fc046dc8e991c25aa4a01c8 
fd3a0ca3acf14106b4f45adaa8b0f0f8 - - -] 10.20.1.71 "POST 
/v2/fd3a0ca3acf14106b4f45adaa8b0f0f8/servers HTTP/1.1" status: 500 len: 465 
time: 0.5185332


-Original Message-
From: Eugen Block [mailto:ebl...@nde.ag] 
Sent: Friday, June 3, 2016 4:23 PM
To: Michael Van Der Beek 
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Heat create-stack fails.

There are several places to define the auth_type, basically for every openstack 
service like glance, cinder, neutron etc.
On controller node, the nova.conf contains two sections with auth_type.

[keystone_authtoken]
auth_type = password
username = nova
...
[neutron]
username = neutron
auth_type = password
...

But there is also the compute node, nova.conf:

[keystone_authtoken]
auth_type = password
username = nova
...
[neutron]
auth_type = password
username = neutron
...

So I assume you'll have to change all your configs, on my controller there are 
7 configs containing auth_type, both neutron.conf and nova.conf contain two 
different sections as stated above:

control1:~ # egrep -rve "^#|^$" /etc/ | grep auth_type 
/etc/glance/glance-registry.conf:auth_type = password 
/etc/glance/glance-api.conf:auth_type = password 
/etc/neutron/neutron.conf:auth_type = password 
/etc/neutron/neutron.conf:auth_type = password /etc/nova/nova.conf:auth_type = 
password /etc/nova/nova.conf:auth_type = password 
/etc/cinder/cinder.conf:auth_type = password 
/etc/ceilometer/ceilometer.conf:auth_type = password 
/etc/heat/heat.conf:auth_type = password

On one of my compute nodes there are three configs, nova.conf also containing 
two different sections:

compute1:~ # egrep -rve "#|^$" /etc/ | grep auth_type 
/etc/nova/nova.conf:auth_type = password /etc/nova/nova.conf:auth_type = 
password /etc/neutron/neutron.conf:auth_type = password 
/etc/ceilometer/ceilometer.conf:auth_type = password

Hope this helps!
Regards,
Eugen


Zitat von Michael Van Der Beek :

> Hi Eugen,
>
> Based on the Mitaka guide. In the compute node, I've put in the 
> nova.conf [DEFAULT] ...
> rpc_backend = rabbit
> rabbit_host = controller
> rabbit_password = RABBIT_PASS
> auth_strategy = keystone
> my_ip = MANAGEMENT_INTERFACE_IP_ADDRESS
>
> [vnc]
> vnc_enabled = True
> vncserver_listen = 0.0.0.0
> vncserver_proxyclient_address = MANAGEMENT_INTERFACE_IP_ADDRESS 
> novncproxy_base_url = http://controller:6080/vnc_auto.html
>
> [keystone_authtoken]
> ...
> auth_uri = http://controller:5000/v2.0 identity_uri = 
> http://controller:35357 admin_tenant_name = service admin_user = nova 
> admin_password = NOVA_PASS
>
> [glance]
> ...
> host = controller
>
> [neutron]
> url = http://controller:9696
> auth_strategy = keystone
> admin_auth_url = http://controller:35357/v2.0 admin_tenant_name = 
> service admin_username = neutron admin_password = 23bcc86e9f99f8f48bc1
>
>
> My question is that now vnc seems to have a section of its own instead 
> of the Mitaka g

Re: [Openstack] Heat create-stack fails.

[Eugen Block]

There are several places to define the auth_type, basically for every  
openstack service like glance, cinder, neutron etc.

On controller node, the nova.conf contains two sections with auth_type.

[keystone_authtoken]
auth_type = password
username = nova
...
[neutron]
username = neutron
auth_type = password
...

But there is also the compute node, nova.conf:

[keystone_authtoken]
auth_type = password
username = nova
...
[neutron]
auth_type = password
username = neutron
...

So I assume you'll have to change all your configs, on my controller  
there are 7 configs containing auth_type, both neutron.conf and  
nova.conf contain two different sections as stated above:


control1:~ # egrep -rve "^#|^$" /etc/ | grep auth_type
/etc/glance/glance-registry.conf:auth_type = password
/etc/glance/glance-api.conf:auth_type = password
/etc/neutron/neutron.conf:auth_type = password
/etc/neutron/neutron.conf:auth_type = password
/etc/nova/nova.conf:auth_type = password
/etc/nova/nova.conf:auth_type = password
/etc/cinder/cinder.conf:auth_type = password
/etc/ceilometer/ceilometer.conf:auth_type = password
/etc/heat/heat.conf:auth_type = password

On one of my compute nodes there are three configs, nova.conf also  
containing two different sections:


compute1:~ # egrep -rve "#|^$" /etc/ | grep auth_type
/etc/nova/nova.conf:auth_type = password
/etc/nova/nova.conf:auth_type = password
/etc/neutron/neutron.conf:auth_type = password
/etc/ceilometer/ceilometer.conf:auth_type = password

Hope this helps!
Regards,
Eugen


Zitat von Michael Van Der Beek :


Hi Eugen,

Based on the Mitaka guide. In the compute node, I've put in the nova.conf
[DEFAULT]
...
rpc_backend = rabbit
rabbit_host = controller
rabbit_password = RABBIT_PASS
auth_strategy = keystone
my_ip = MANAGEMENT_INTERFACE_IP_ADDRESS

[vnc]
vnc_enabled = True
vncserver_listen = 0.0.0.0
vncserver_proxyclient_address = MANAGEMENT_INTERFACE_IP_ADDRESS
novncproxy_base_url = http://controller:6080/vnc_auto.html

[keystone_authtoken]
...
auth_uri = http://controller:5000/v2.0
identity_uri = http://controller:35357
admin_tenant_name = service
admin_user = nova
admin_password = NOVA_PASS

[glance]
...
host = controller

[neutron]
url = http://controller:9696
auth_strategy = keystone
admin_auth_url = http://controller:35357/v2.0
admin_tenant_name = service
admin_username = neutron
admin_password = 23bcc86e9f99f8f48bc1


My question is that now vnc seems to have a section of its own  
instead of the Mitaka guide which is Default so I put it in [vnc]


So the auth_type should be in keystone_authtoken?
Or neutron?
I've tried both and I still get the auth_type error on the controller?

Is the problem on the controller? Is the auth_type required in the  
nova.conf on the controller?


Regards,

Michael

-Original Message-
From: Eugen Block [mailto:ebl...@nde.ag]
Sent: Friday, June 3, 2016 3:38 PM
To: Michael Van Der Beek 
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Heat create-stack fails.

Hi Michael,

in addition to Pavlo's answer I just wanted to add what I use as  
auth_type, referring to the Mitaka guide the value is:


auth_type = password

Regards,
Eugen

Zitat von Pavlo Shchelokovskyy :


Hi Michael,

you should consult the docs for "keystoneauth" library [0], that is
actually using these options to construct an authentificated client.
It supports quite a number of auth plugins (that's what you specify as
auth_type), each having specific other options.

[0]
http://docs.openstack.org/developer/keystoneauth/authentication-plugin
s.html

Cheers,

Dr. Pavlo Shchelokovskyy
Senior Software Engineer
Mirantis Inc
www.mirantis.com

On Fri, Jun 3, 2016 at 6:21 AM, Michael Van Der Beek <
michael@antlabs.com> wrote:


Hi Eugen,



For some reason, I’m not getting any email from this list.

My mailserver doesn’t even show any attempts from the list server.



Anyway, the install guide does not specify what the auth_plugin is
suppose to be.

By default auth_plugin is depreciated.



# Authentication type to load (unknown value)

# Deprecated group;name - DEFAULT;auth_plugin

#auth_type=



As the install guide does not specified, any idea what should I put
in here.



The guide has many places that the commands have changed syntax so
its not very accurate any more.



Regards,



Michael

-

Hi,

I'm just guessing, but maybe you didn't change the auth_plugin in
nova.conf on compute node?

Regards,
Eugen



*From:* Michael Van Der Beek
*Sent:* Thursday, June 2, 2016 4:48 PM
*To:* 'openstack@lists.openstack.org' 
*Subject:* Heat create-stack fails.



Hi All,



Sorry to trouble you guys.

I’ve been following the install guide found at


http://docs.openstack.org/juno/install-guide/install/yum/content/ch_p
reface.html



I’ve gotten everything to work except the Orchestra.



When I do this.

[root@controller nova]# 

Re: [Openstack] Heat create-stack fails.

[Michael Van Der Beek]

Hi Eugen,

Based on the Mitaka guide. In the compute node, I've put in the nova.conf
[DEFAULT]
...
rpc_backend = rabbit
rabbit_host = controller
rabbit_password = RABBIT_PASS
auth_strategy = keystone
my_ip = MANAGEMENT_INTERFACE_IP_ADDRESS

[vnc]
vnc_enabled = True
vncserver_listen = 0.0.0.0
vncserver_proxyclient_address = MANAGEMENT_INTERFACE_IP_ADDRESS
novncproxy_base_url = http://controller:6080/vnc_auto.html

[keystone_authtoken]
...
auth_uri = http://controller:5000/v2.0
identity_uri = http://controller:35357
admin_tenant_name = service
admin_user = nova
admin_password = NOVA_PASS

[glance]
...
host = controller

[neutron]
url = http://controller:9696
auth_strategy = keystone
admin_auth_url = http://controller:35357/v2.0
admin_tenant_name = service
admin_username = neutron
admin_password = 23bcc86e9f99f8f48bc1


My question is that now vnc seems to have a section of its own instead of the 
Mitaka guide which is Default so I put it in [vnc]

So the auth_type should be in keystone_authtoken?
Or neutron?
I've tried both and I still get the auth_type error on the controller? 

Is the problem on the controller? Is the auth_type required in the nova.conf on 
the controller?

Regards,

Michael

-Original Message-
From: Eugen Block [mailto:ebl...@nde.ag] 
Sent: Friday, June 3, 2016 3:38 PM
To: Michael Van Der Beek 
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Heat create-stack fails.

Hi Michael,

in addition to Pavlo's answer I just wanted to add what I use as auth_type, 
referring to the Mitaka guide the value is:

auth_type = password

Regards,
Eugen

Zitat von Pavlo Shchelokovskyy :

> Hi Michael,
>
> you should consult the docs for "keystoneauth" library [0], that is 
> actually using these options to construct an authentificated client. 
> It supports quite a number of auth plugins (that's what you specify as 
> auth_type), each having specific other options.
>
> [0]
> http://docs.openstack.org/developer/keystoneauth/authentication-plugin
> s.html
>
> Cheers,
>
> Dr. Pavlo Shchelokovskyy
> Senior Software Engineer
> Mirantis Inc
> www.mirantis.com
>
> On Fri, Jun 3, 2016 at 6:21 AM, Michael Van Der Beek < 
> michael@antlabs.com> wrote:
>
>> Hi Eugen,
>>
>>
>>
>> For some reason, I’m not getting any email from this list.
>>
>> My mailserver doesn’t even show any attempts from the list server.
>>
>>
>>
>> Anyway, the install guide does not specify what the auth_plugin is 
>> suppose to be.
>>
>> By default auth_plugin is depreciated.
>>
>>
>>
>> # Authentication type to load (unknown value)
>>
>> # Deprecated group;name - DEFAULT;auth_plugin
>>
>> #auth_type=
>>
>>
>>
>> As the install guide does not specified, any idea what should I put 
>> in here.
>>
>>
>>
>> The guide has many places that the commands have changed syntax so 
>> its not very accurate any more.
>>
>>
>>
>> Regards,
>>
>>
>>
>> Michael
>>
>> -
>>
>> Hi,
>>
>> I'm just guessing, but maybe you didn't change the auth_plugin in 
>> nova.conf on compute node?
>>
>> Regards,
>> Eugen
>>
>>
>>
>> *From:* Michael Van Der Beek
>> *Sent:* Thursday, June 2, 2016 4:48 PM
>> *To:* 'openstack@lists.openstack.org' 
>> *Subject:* Heat create-stack fails.
>>
>>
>>
>> Hi All,
>>
>>
>>
>> Sorry to trouble you guys.
>>
>> I’ve been following the install guide found at
>>
>>
>> http://docs.openstack.org/juno/install-guide/install/yum/content/ch_p
>> reface.html
>>
>>
>>
>> I’ve gotten everything to work except the Orchestra.
>>
>>
>>
>> When I do this.
>>
>> [root@controller nova]# heat stack-create -f /root/test-stack.yml   -P
>> "ImageID=cirros-0.3.3-x86_64;NetID=$NET_ID" testStack
>>
>>
>> +--+++-+--+
>>
>> | id   | stack_name | stack_status   |
>> creation_time   | updated_time |
>>
>>
>> +--+++-+--+
>>
>> | a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  | 
>> | CREATE_IN_PROGRESS |
>> 2016-06-02T08:39:53 | None |
>>
>>
>> +--+++-

Re: [Openstack] Heat create-stack fails.

[Eugen Block]

Hi Michael,

in addition to Pavlo's answer I just wanted to add what I use as  
auth_type, referring to the Mitaka guide the value is:


auth_type = password

Regards,
Eugen

Zitat von Pavlo Shchelokovskyy :


Hi Michael,

you should consult the docs for "keystoneauth" library [0], that is
actually using these options to construct an authentificated client. It
supports quite a number of auth plugins (that's what you specify as
auth_type), each having specific other options.

[0]
http://docs.openstack.org/developer/keystoneauth/authentication-plugins.html

Cheers,

Dr. Pavlo Shchelokovskyy
Senior Software Engineer
Mirantis Inc
www.mirantis.com

On Fri, Jun 3, 2016 at 6:21 AM, Michael Van Der Beek <
michael@antlabs.com> wrote:


Hi Eugen,



For some reason, I’m not getting any email from this list.

My mailserver doesn’t even show any attempts from the list server.



Anyway, the install guide does not specify what the auth_plugin is suppose
to be.

By default auth_plugin is depreciated.



# Authentication type to load (unknown value)

# Deprecated group;name - DEFAULT;auth_plugin

#auth_type=



As the install guide does not specified, any idea what should I put in
here.



The guide has many places that the commands have changed syntax so its not
very accurate any more.



Regards,



Michael

-

Hi,

I'm just guessing, but maybe you didn't change the auth_plugin in
nova.conf on compute node?

Regards,
Eugen



*From:* Michael Van Der Beek
*Sent:* Thursday, June 2, 2016 4:48 PM
*To:* 'openstack@lists.openstack.org' 
*Subject:* Heat create-stack fails.



Hi All,



Sorry to trouble you guys.

I’ve been following the install guide found at


http://docs.openstack.org/juno/install-guide/install/yum/content/ch_preface.html



I’ve gotten everything to work except the Orchestra.



When I do this.

[root@controller nova]# heat stack-create -f /root/test-stack.yml   -P
"ImageID=cirros-0.3.3-x86_64;NetID=$NET_ID" testStack


+--+++-+--+

| id   | stack_name | stack_status   |
creation_time   | updated_time |


+--+++-+--+

| a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  | CREATE_IN_PROGRESS |
2016-06-02T08:39:53 | None |


+--+++-+--+



Later..

[root@controller nova]# heat stack-list


+--++---+-+--+

| id   | stack_name | stack_status  |
creation_time   | updated_time |


+--++---+-+--+

| a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  | CREATE_FAILED |
2016-06-02T08:39:53 | None |


+--++---+-+--+



From what I understand, the heat log shows this:

2016-06-02 16:39:53.681 2853 INFO heat.engine.stack [-] Stack CREATE
IN_PROGRESS (testStack): Stack CREATE started

2016-06-02 16:39:53.692 2853 INFO heat.engine.resource [-] creating Server
"server" Stack "testStack" [a3c21978-78e0-4cb1-b92e-cb853df4aa04]

2016-06-02 16:39:54.699 2853 INFO heat.engine.resource [-] CREATE: Server
"server" Stack "testStack" [a3c21978-78e0-4cb1-b92e-cb853df4aa04]

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource Traceback (most
recent call last):

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 704, in
_action_recorder

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource yield

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 775, in
_do_action

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource yield
self.action_handler_task(action, args=handler_args)

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File
"/usr/lib/python2.7/site-packages/heat/engine/scheduler.py", line 297, in
wrapper

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource step =
next(subtask)

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 746, in
action_handler_task

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource handler_data =
handler(*args)

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File
"/usr/lib/python2.7/site-packages/heat/engine/resources/openstack/nova/server.py",
line 861, in handle_crea

te

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource
admin_pass=admin_pass)

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resourc

Re: [Openstack] Heat create-stack fails.

[Pavlo Shchelokovskyy]

Hi Michael,

you should consult the docs for "keystoneauth" library [0], that is
actually using these options to construct an authentificated client. It
supports quite a number of auth plugins (that's what you specify as
auth_type), each having specific other options.

[0]
http://docs.openstack.org/developer/keystoneauth/authentication-plugins.html

Cheers,

Dr. Pavlo Shchelokovskyy
Senior Software Engineer
Mirantis Inc
www.mirantis.com

On Fri, Jun 3, 2016 at 6:21 AM, Michael Van Der Beek <
michael@antlabs.com> wrote:

> Hi Eugen,
>
>
>
> For some reason, I’m not getting any email from this list.
>
> My mailserver doesn’t even show any attempts from the list server.
>
>
>
> Anyway, the install guide does not specify what the auth_plugin is suppose
> to be.
>
> By default auth_plugin is depreciated.
>
>
>
> # Authentication type to load (unknown value)
>
> # Deprecated group;name - DEFAULT;auth_plugin
>
> #auth_type=
>
>
>
> As the install guide does not specified, any idea what should I put in
> here.
>
>
>
> The guide has many places that the commands have changed syntax so its not
> very accurate any more.
>
>
>
> Regards,
>
>
>
> Michael
>
> -
>
> Hi,
>
> I'm just guessing, but maybe you didn't change the auth_plugin in
> nova.conf on compute node?
>
> Regards,
> Eugen
>
>
>
> *From:* Michael Van Der Beek
> *Sent:* Thursday, June 2, 2016 4:48 PM
> *To:* 'openstack@lists.openstack.org' 
> *Subject:* Heat create-stack fails.
>
>
>
> Hi All,
>
>
>
> Sorry to trouble you guys.
>
> I’ve been following the install guide found at
>
>
> http://docs.openstack.org/juno/install-guide/install/yum/content/ch_preface.html
>
>
>
> I’ve gotten everything to work except the Orchestra.
>
>
>
> When I do this.
>
> [root@controller nova]# heat stack-create -f /root/test-stack.yml   -P
> "ImageID=cirros-0.3.3-x86_64;NetID=$NET_ID" testStack
>
>
> +--+++-+--+
>
> | id   | stack_name | stack_status   |
> creation_time   | updated_time |
>
>
> +--+++-+--+
>
> | a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  | CREATE_IN_PROGRESS |
> 2016-06-02T08:39:53 | None |
>
>
> +--+++-+--+
>
>
>
> Later..
>
> [root@controller nova]# heat stack-list
>
>
> +--++---+-+--+
>
> | id   | stack_name | stack_status  |
> creation_time   | updated_time |
>
>
> +--++---+-+--+
>
> | a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  | CREATE_FAILED |
> 2016-06-02T08:39:53 | None |
>
>
> +--++---+-+--+
>
>
>
> From what I understand, the heat log shows this:
>
> 2016-06-02 16:39:53.681 2853 INFO heat.engine.stack [-] Stack CREATE
> IN_PROGRESS (testStack): Stack CREATE started
>
> 2016-06-02 16:39:53.692 2853 INFO heat.engine.resource [-] creating Server
> "server" Stack "testStack" [a3c21978-78e0-4cb1-b92e-cb853df4aa04]
>
> 2016-06-02 16:39:54.699 2853 INFO heat.engine.resource [-] CREATE: Server
> "server" Stack "testStack" [a3c21978-78e0-4cb1-b92e-cb853df4aa04]
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource Traceback (most
> recent call last):
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File
> "/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 704, in
> _action_recorder
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource yield
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File
> "/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 775, in
> _do_action
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource yield
> self.action_handler_task(action, args=handler_args)
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File
> "/usr/lib/python2.7/site-packages/heat/engine/scheduler.py", line 297, in
> wrapper
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource step =
> next(subtask)
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File
> "/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 746, in
> action_handler_task
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource handler_data =
> handler(*args)
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File
> "/usr/lib/python2.7/site-packages/heat/engine/resources/openstack/nova/server.py",
> line 861, in handle_crea
>
> te
>
> 2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource
> admin_pass=admin_pass)
>
> 2016-06-02 

Re: [Openstack] Heat create-stack fails.

[Michael Van Der Beek]

Hi Eugen,

For some reason, I'm not getting any email from this list.
My mailserver doesn't even show any attempts from the list server.

Anyway, the install guide does not specify what the auth_plugin is suppose to 
be.
By default auth_plugin is depreciated.

# Authentication type to load (unknown value)
# Deprecated group;name - DEFAULT;auth_plugin
#auth_type=

As the install guide does not specified, any idea what should I put in here.

The guide has many places that the commands have changed syntax so its not very 
accurate any more.

Regards,

Michael
-
Hi,

I'm just guessing, but maybe you didn't change the auth_plugin in
nova.conf on compute node?

Regards,
Eugen

From: Michael Van Der Beek
Sent: Thursday, June 2, 2016 4:48 PM
To: 'openstack@lists.openstack.org' 
Subject: Heat create-stack fails.

Hi All,

Sorry to trouble you guys.
I've been following the install guide found at
http://docs.openstack.org/juno/install-guide/install/yum/content/ch_preface.html

I've gotten everything to work except the Orchestra.

When I do this.
[root@controller nova]# heat stack-create -f /root/test-stack.yml   -P 
"ImageID=cirros-0.3.3-x86_64;NetID=$NET_ID" testStack
+--+++-+--+
| id   | stack_name | stack_status   | 
creation_time   | updated_time |
+--+++-+--+
| a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  | CREATE_IN_PROGRESS | 
2016-06-02T08:39:53 | None |
+--+++-+--+

Later..
[root@controller nova]# heat stack-list
+--++---+-+--+
| id   | stack_name | stack_status  | 
creation_time   | updated_time |
+--++---+-+--+
| a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  | CREATE_FAILED | 
2016-06-02T08:39:53 | None |
+--++---+-+--+

>From what I understand, the heat log shows this:
2016-06-02 16:39:53.681 2853 INFO heat.engine.stack [-] Stack CREATE 
IN_PROGRESS (testStack): Stack CREATE started
2016-06-02 16:39:53.692 2853 INFO heat.engine.resource [-] creating Server 
"server" Stack "testStack" [a3c21978-78e0-4cb1-b92e-cb853df4aa04]
2016-06-02 16:39:54.699 2853 INFO heat.engine.resource [-] CREATE: Server 
"server" Stack "testStack" [a3c21978-78e0-4cb1-b92e-cb853df4aa04]
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource Traceback (most recent 
call last):
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 704, in 
_action_recorder
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource yield
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 775, in 
_do_action
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource yield 
self.action_handler_task(action, args=handler_args)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/heat/engine/scheduler.py", line 297, in 
wrapper
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource step = next(subtask)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 746, in 
action_handler_task
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource handler_data = 
handler(*args)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/heat/engine/resources/openstack/nova/server.py",
 line 861, in handle_crea
te
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource 
admin_pass=admin_pass)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 1233, in 
create
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource **boot_kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 667, in _boot
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource 
return_raw=return_raw, **kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/base.py", line 345, in _create
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource resp, body = 
self.api.client.post(url, body=body)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 455, in p

Re: [Openstack] Heat create-stack fails.

[Eugen Block]

Hi,

I'm just guessing, but maybe you didn't change the auth_plugin in  
nova.conf on compute node?


Regards,
Eugen

Zitat von Michael Van Der Beek :


Hi All,

Sorry to trouble you guys.
I've been following the install guide found at
http://docs.openstack.org/juno/install-guide/install/yum/content/ch_preface.html

I've gotten everything to work except the Orchestra.

When I do this.
[root@controller nova]# heat stack-create -f /root/test-stack.yml
-P "ImageID=cirros-0.3.3-x86_64;NetID=$NET_ID" testStack

+--+++-+--+
| id   | stack_name | stack_status
| creation_time   | updated_time |

+--+++-+--+
| a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  |  
CREATE_IN_PROGRESS | 2016-06-02T08:39:53 | None |

+--+++-+--+

Later..
[root@controller nova]# heat stack-list
+--++---+-+--+
| id   | stack_name | stack_status   
| creation_time   | updated_time |

+--++---+-+--+
| a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  | CREATE_FAILED  
| 2016-06-02T08:39:53 | None |

+--++---+-+--+

From what I understand, the heat log shows this:
2016-06-02 16:39:53.681 2853 INFO heat.engine.stack [-] Stack CREATE  
IN_PROGRESS (testStack): Stack CREATE started
2016-06-02 16:39:53.692 2853 INFO heat.engine.resource [-] creating  
Server "server" Stack "testStack"  
[a3c21978-78e0-4cb1-b92e-cb853df4aa04]
2016-06-02 16:39:54.699 2853 INFO heat.engine.resource [-] CREATE:  
Server "server" Stack "testStack"  
[a3c21978-78e0-4cb1-b92e-cb853df4aa04]
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource Traceback  
(most recent call last):
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line  
704, in _action_recorder

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource yield
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line  
775, in _do_action
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource yield  
self.action_handler_task(action, args=handler_args)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/heat/engine/scheduler.py", line  
297, in wrapper
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource step =  
next(subtask)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line  
746, in action_handler_task
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource  
handler_data = handler(*args)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/heat/engine/resources/openstack/nova/server.py", line 861, in  
handle_crea

te
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource  
admin_pass=admin_pass)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line  
1233, in create

2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource **boot_kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line  
667, in _boot
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource  
return_raw=return_raw, **kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/novaclient/base.py", line 345, in  
_create
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource resp,  
body = self.api.client.post(url, body=body)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 455,  
in post
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource return  
self._cs_request(url, 'POST', **kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 430,  
in _cs_request
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource resp,  
body = self._time_request(url, method, **kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File  
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 403,  
in _time_request
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource resp,  
body = self.request(url, method, **kwargs)
2016-06-02 16:39:54.699 2853 ERRO

[Openstack] Heat create-stack fails.

[Michael Van Der Beek]

Hi All,

Sorry to trouble you guys.
I've been following the install guide found at
http://docs.openstack.org/juno/install-guide/install/yum/content/ch_preface.html

I've gotten everything to work except the Orchestra.

When I do this.
[root@controller nova]# heat stack-create -f /root/test-stack.yml   -P 
"ImageID=cirros-0.3.3-x86_64;NetID=$NET_ID" testStack
+--+++-+--+
| id   | stack_name | stack_status   | 
creation_time   | updated_time |
+--+++-+--+
| a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  | CREATE_IN_PROGRESS | 
2016-06-02T08:39:53 | None |
+--+++-+--+

Later..
[root@controller nova]# heat stack-list
+--++---+-+--+
| id   | stack_name | stack_status  | 
creation_time   | updated_time |
+--++---+-+--+
| a3c21978-78e0-4cb1-b92e-cb853df4aa04 | testStack  | CREATE_FAILED | 
2016-06-02T08:39:53 | None |
+--++---+-+--+

>From what I understand, the heat log shows this:
2016-06-02 16:39:53.681 2853 INFO heat.engine.stack [-] Stack CREATE 
IN_PROGRESS (testStack): Stack CREATE started
2016-06-02 16:39:53.692 2853 INFO heat.engine.resource [-] creating Server 
"server" Stack "testStack" [a3c21978-78e0-4cb1-b92e-cb853df4aa04]
2016-06-02 16:39:54.699 2853 INFO heat.engine.resource [-] CREATE: Server 
"server" Stack "testStack" [a3c21978-78e0-4cb1-b92e-cb853df4aa04]
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource Traceback (most recent 
call last):
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 704, in 
_action_recorder
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource yield
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 775, in 
_do_action
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource yield 
self.action_handler_task(action, args=handler_args)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/heat/engine/scheduler.py", line 297, in 
wrapper
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource step = next(subtask)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 746, in 
action_handler_task
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource handler_data = 
handler(*args)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/heat/engine/resources/openstack/nova/server.py",
 line 861, in handle_crea
te
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource 
admin_pass=admin_pass)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 1233, in 
create
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource **boot_kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 667, in _boot
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource 
return_raw=return_raw, **kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/base.py", line 345, in _create
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource resp, body = 
self.api.client.post(url, body=body)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 455, in post
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource return 
self._cs_request(url, 'POST', **kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 430, in 
_cs_request
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource resp, body = 
self._time_request(url, method, **kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 403, in 
_time_request
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource resp, body = 
self.request(url, method, **kwargs)
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource   File 
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 397, in request
2016-06-02 16:39:54.699 2853 ERROR heat.engine.resource raise 
exceptions.from_response(resp, bo

Re: [Openstack] Openstack Heat for normal users?

[Pavlo Shchelokovskyy]

Hi Florian,

great to hear that your problem is solved.

As I pointed out, in Liberty you actually do not need the
"heat_stack_owner" role at all. Just make sure that in your heat.conf the
following option is set to empty value (which AFAIK is default in Liberty):

# Subset of trustor roles to be delegated to heat. If left unset, all roles
of
# a user will be delegated to heat when creating a stack. (list value)
  trusts_delegated_roles =

(that's new line right after after "=", for oslo_cfg to parse empty
ListOpt).

At some point, heat_stack_owner role was used by default as a single role
to be passed via trust, but now we can pass all roles at once without a
need of a special role.

So to avoid future confusion, you can consider deleting the
heat_stack_owner role and strictly advise people to not use heat_stack_user
role for actual (human) OpenStack users (this one is internal for Heat).
You could also rename that role to anything less confusing (like
"heat_internal_do_not_use" :) ) and reconfigure heat.conf and heat's
policy.json to use that name as a role for Heat-internal users.

Cheers,

Dr. Pavlo Shchelokovskyy
Senior Software Engineer
Mirantis Inc
www.mirantis.com

On Tue, May 17, 2016 at 5:29 PM, Florian Rommel <
florian.rom...@datalounges.com> wrote:

> Hi, thank you for pointing it out, apparently you need to have one of the
> roles applied in Liberty (which is what we used), but my demo user had both
> applied. If then chooses the lower level access, hence no access. Once I
> gave the user only heat_stack_owner i could deploy stacks within the normal
> projects as normal users.
>
> Thank you again.
>
> //Florian
>
> On 17 May 2016, at 16:37, Pavlo Shchelokovskyy <
> pshchelokovs...@mirantis.com> wrote:
>
> Hi,
>
> are you sure that's "heat_stack_owner" and _not_ "heat_stack_user" role
> that is assigned to your normal, non-admin user? These are frequently
> confused, but there's a great deal of difference between them, the latter
> role indeed has almost no access to Heat API.
>
> Also, what OpenStack version are you using? AFAIR starting from Kilo (or
> may be even later maintenance releases of Juno) one does not actually need
> the heat_stack_owner role altogether, all user roles should be passed via
> trust by default (you have to make sure Heat is configured to use Keystone
> V3 for that).
>
> Cheers,
>
> Dr. Pavlo Shchelokovskyy
> Senior Software Engineer
> Mirantis Inc
> www.mirantis.com
>
> On Tue, May 17, 2016 at 4:19 PM, Florian Rommel <
> florian.rom...@datalounges.com> wrote:
>
>> Hi, all, most of our major hurdles are now gone with Openstack and it
>> looks almost all great now..
>>
>> Now the tricky part. I have gotten into HEAT and have written many
>> templates and actually very complex ones too and I would love for normal
>> users and other tenants to be able to use them but I keep getting an error
>> retrieving stack list.
>> The user has heat stack owner assigned to him and i can see orchestration
>> in the dashboard but no stacks can be retrieved nor looked at the resource
>> types. What exactly kind of permissions/groups does the user need to be in?
>> Thanks again for any help already.
>> when i source the demo rc file i get:
>>
>> root@control:~ # source .opendemo
>> root@control:~ # heat stack-list
>> ERROR: You are not authorized to use index.
>> root@control:~ #
>>
>> while the admin rc gives:
>>
>> root@control:~ # heat stack-list
>>
>> +--++-++--+
>> | id   | stack_name | stack_status|
>> creation_time  | updated_time |
>>
>> +--++-++--+
>> | e7ca31f9-cd14-4f98-9f71-566ef69809c0 | Test4  | CREATE_COMPLETE |
>> 2016-05-17T12:37:33.684783 | None |
>>
>> +--++-++--+
>> root@control:~ #
>>
>> only difference is the project name and username/password.
>>
>> Best regards,
>> //FR
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack Heat for normal users?

[Florian Rommel]

Hi, thank you for pointing it out, apparently you need to have one of the roles 
applied in Liberty (which is what we used), but my demo user had both applied. 
If then chooses the lower level access, hence no access. Once I gave the user 
only heat_stack_owner i could deploy stacks within the normal projects as 
normal users.

Thank you again.

//Florian
> On 17 May 2016, at 16:37, Pavlo Shchelokovskyy  
> wrote:
> 
> Hi,
> 
> are you sure that's "heat_stack_owner" and _not_ "heat_stack_user" role that 
> is assigned to your normal, non-admin user? These are frequently confused, 
> but there's a great deal of difference between them, the latter role indeed 
> has almost no access to Heat API.
> 
> Also, what OpenStack version are you using? AFAIR starting from Kilo (or may 
> be even later maintenance releases of Juno) one does not actually need the 
> heat_stack_owner role altogether, all user roles should be passed via trust 
> by default (you have to make sure Heat is configured to use Keystone V3 for 
> that).
> 
> Cheers,
> 
> Dr. Pavlo Shchelokovskyy
> Senior Software Engineer
> Mirantis Inc
> www.mirantis.com 
> On Tue, May 17, 2016 at 4:19 PM, Florian Rommel 
> mailto:florian.rom...@datalounges.com>> 
> wrote:
> Hi, all, most of our major hurdles are now gone with Openstack and it looks 
> almost all great now..
> 
> Now the tricky part. I have gotten into HEAT and have written many templates 
> and actually very complex ones too and I would love for normal users and 
> other tenants to be able to use them but I keep getting an error retrieving 
> stack list.
> The user has heat stack owner assigned to him and i can see orchestration in 
> the dashboard but no stacks can be retrieved nor looked at the resource 
> types. What exactly kind of permissions/groups does the user need to be in?
> Thanks again for any help already.
> when i source the demo rc file i get:
> 
> root@control:~ # source .opendemo
> root@control:~ # heat stack-list
> ERROR: You are not authorized to use index.
> root@control:~ #
> 
> while the admin rc gives:
> 
> root@control:~ # heat stack-list
> +--++-++--+
> | id   | stack_name | stack_status| 
> creation_time  | updated_time |
> +--++-++--+
> | e7ca31f9-cd14-4f98-9f71-566ef69809c0 | Test4  | CREATE_COMPLETE | 
> 2016-05-17T12:37:33.684783 | None |
> +--++-++--+
> root@control:~ #
> 
> only difference is the project name and username/password.
> 
> Best regards,
> //FR
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
> 
> Post to : openstack@lists.openstack.org 
> 
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
> 
> 

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack Heat for normal users?

[Pavlo Shchelokovskyy]

Hi,

are you sure that's "heat_stack_owner" and _not_ "heat_stack_user" role
that is assigned to your normal, non-admin user? These are frequently
confused, but there's a great deal of difference between them, the latter
role indeed has almost no access to Heat API.

Also, what OpenStack version are you using? AFAIR starting from Kilo (or
may be even later maintenance releases of Juno) one does not actually need
the heat_stack_owner role altogether, all user roles should be passed via
trust by default (you have to make sure Heat is configured to use Keystone
V3 for that).

Cheers,

Dr. Pavlo Shchelokovskyy
Senior Software Engineer
Mirantis Inc
www.mirantis.com

On Tue, May 17, 2016 at 4:19 PM, Florian Rommel <
florian.rom...@datalounges.com> wrote:

> Hi, all, most of our major hurdles are now gone with Openstack and it
> looks almost all great now..
>
> Now the tricky part. I have gotten into HEAT and have written many
> templates and actually very complex ones too and I would love for normal
> users and other tenants to be able to use them but I keep getting an error
> retrieving stack list.
> The user has heat stack owner assigned to him and i can see orchestration
> in the dashboard but no stacks can be retrieved nor looked at the resource
> types. What exactly kind of permissions/groups does the user need to be in?
> Thanks again for any help already.
> when i source the demo rc file i get:
>
> root@control:~ # source .opendemo
> root@control:~ # heat stack-list
> ERROR: You are not authorized to use index.
> root@control:~ #
>
> while the admin rc gives:
>
> root@control:~ # heat stack-list
>
> +--++-++--+
> | id   | stack_name | stack_status|
> creation_time  | updated_time |
>
> +--++-++--+
> | e7ca31f9-cd14-4f98-9f71-566ef69809c0 | Test4  | CREATE_COMPLETE |
> 2016-05-17T12:37:33.684783 | None |
>
> +--++-++--+
> root@control:~ #
>
> only difference is the project name and username/password.
>
> Best regards,
> //FR
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Openstack Heat for normal users?

[Florian Rommel]

Hi, all, most of our major hurdles are now gone with Openstack and it looks 
almost all great now.. 

Now the tricky part. I have gotten into HEAT and have written many templates 
and actually very complex ones too and I would love for normal users and other 
tenants to be able to use them but I keep getting an error retrieving stack 
list.
The user has heat stack owner assigned to him and i can see orchestration in 
the dashboard but no stacks can be retrieved nor looked at the resource types. 
What exactly kind of permissions/groups does the user need to be in?
Thanks again for any help already.
when i source the demo rc file i get:

root@control:~ # source .opendemo
root@control:~ # heat stack-list
ERROR: You are not authorized to use index.
root@control:~ #

while the admin rc gives:

root@control:~ # heat stack-list
+--++-++--+
| id   | stack_name | stack_status| 
creation_time  | updated_time |
+--++-++--+
| e7ca31f9-cd14-4f98-9f71-566ef69809c0 | Test4  | CREATE_COMPLETE | 
2016-05-17T12:37:33.684783 | None |
+--++-++--+
root@control:~ #

only difference is the project name and username/password.

Best regards,
//FR
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat autoscaling: heat.engine.resource Forbidden: You are not authorized to perform the requested action.

[magicboiz]

Hi


I'm testing this simple template: 
https://github.com/openstack/heat-templates/blob/master/hot/autoscaling.yaml


But please notice that Fuel Health Test autoscale also fails.so I guess 
those trusts and domains might not be correctly deployed...


:(


Regards 

J.



De: Pavlo Shchelokovskyy

Enviado: martes 10 de mayo 20:04

Asunto: Re: [Openstack] Heat autoscaling: heat.engine.resource Forbidden: You 
are not authorized to perform the requested action.

Para: magicb...@hotmail.com

Cc: openstack@lists.openstack.org



Hi,


no, "heat_stack_owner" role is actually not needed in MOS 8.0. Earlier it was 
used as a special role to pass via trusts, but now all roles are passed via 
trust by default. You also do not have to be "admin" either, priviledge 
"escalation" is handled by Heat using Keystone V3 trusts and domains which 
should have been set up automatically during deployment.


One question though - Is by any chance the "heat_stack_user" role assigned to 
the actual ("human") user who is accessing Heat API? It _must_not_ be  - this 
is a special role used by internal Heat-created users (implementation detail), 
and it has _very_ limited privileges in regard Heat API access.


Also, could you show the template you are testing autoscaling with? just in 
case...



Cheers,



Dr. Pavlo Shchelokovskyy


Senior Software Engineer


Mirantis Inc


www.mirantis.com



On Tue, May 10, 2016 at 6:52 PM, magicb...@hotmail.com  
wrote:


Hi again,


these are the roles I have :


#openstack role list   

+--+-+

| ID   | Name    |

+--+-+

| 0d77782f1ae54fa799b0585b267fb746 | ResellerAdmin   |

| 2c0a5b381f2b4f10b42aaa09678210a5 | heat_stack_user |

| 9fe2ff9ee4384b1894a90878d3e92bab | _member_    |

| d819d32c0eba4c86a99241e741c241c1 | admin   |

| e0729bbb6f8544268fd371e50682754a | SwiftOperator   |



So, there is no "heat_stack_owner" role defined in my environment, but you're 
right, in 
http://docs.openstack.org/draft/install-guide-ubuntu/heat-install.html docs 
says:


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 



Is this a bug in Mirantis MOS 8.0? 



On 10/05/16 17:05, magicb...@hotmail.com wrote:



Hi Raghavendra,



how can I check those privileges? Even with "admin" user, I get the same 
error. :(


Best regards


J.


On 10/05/16 13:23, raghavendra@accenture.com wrote:




Hi Mag,


 


Please check if you have provided the heat-stack-owner and admin privileges to 
the tenant then try to spin up the Heat stack.


 


Regards,


Raghavendra Lad


 


From: magicb...@hotmail.com [mailto:magicb...@hotmail.com] 

Sent: Tuesday, May 10, 2016 4:30 PM

To: openstack@lists.openstack.org

Subject: [Openstack] Heat autoscaling: heat.engine.resource Forbidden: You are 
not authorized to perform the requested action.


 


Hi


testing Openstack Mitaka (deployed with Mirantis FUEL 8.0), when testing Heat 
Autoscaling, I get this error:


heat.engine.resource Forbidden: You are not authorized to perform the requested 
action.


 


Any ideas on what's going on?


 


Thanks in advance.


J


 


 




This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy. 

__


www.accenture.com












___ Mailing list: 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : 
openstack@lists.openstack.org Unsubscribe : 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 










___

Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Post to     : openstack@lists.openstack.org

Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack








___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat autoscaling: heat.engine.resource Forbidden: You are not authorized to perform the requested action.

[Pavlo Shchelokovskyy]

Hi,

no, "heat_stack_owner" role is actually not needed in MOS 8.0. Earlier it
was used as a special role to pass via trusts, but now all roles are passed
via trust by default. You also do not have to be "admin" either, priviledge
"escalation" is handled by Heat using Keystone V3 trusts and domains which
should have been set up automatically during deployment.

One question though - Is by any chance the "heat_stack_user" role assigned
to the actual ("human") user who is accessing Heat API? It _must_not_ be  -
this is a special role used by internal Heat-created users (implementation
detail), and it has _very_ limited privileges in regard Heat API access.

Also, could you show the template you are testing autoscaling with? just in
case...

Cheers,

Dr. Pavlo Shchelokovskyy
Senior Software Engineer
Mirantis Inc
www.mirantis.com

On Tue, May 10, 2016 at 6:52 PM, magicb...@hotmail.com <
magicb...@hotmail.com> wrote:

> Hi again,
>
> these are the roles I have :
>
> #openstack role list
> +--+-+
> | ID   | Name|
> +--+-+
> | 0d77782f1ae54fa799b0585b267fb746 | ResellerAdmin   |
> | 2c0a5b381f2b4f10b42aaa09678210a5 | heat_stack_user |
> | 9fe2ff9ee4384b1894a90878d3e92bab | _member_|
> | d819d32c0eba4c86a99241e741c241c1 | admin   |
> | e0729bbb6f8544268fd371e50682754a | SwiftOperator   |
>
>
> So, there is no "heat_stack_owner" role defined in my environment, but
> you're right, in
> http://docs.openstack.org/draft/install-guide-ubuntu/heat-install.html
> docs says:
>
> *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*
>
>
> Is this a bug in Mirantis MOS 8.0?
>
>
> On 10/05/16 17:05, magicb...@hotmail.com wrote:
>
> Hi Raghavendra,
>
>
> how can I check those privileges? Even with "admin" user, I get the same
> error. :(
>
> Best regards
>
> J.
> On 10/05/16 13:23, 
> raghavendra@accenture.com wrote:
>
> Hi Mag,
>
>
>
> Please check if you have provided the *heat-stack-owner* and *admin 
> *privileges
> to the tenant then try to spin up the Heat stack.
>
>
>
> Regards,
>
> Raghavendra Lad
>
>
>
> *From:* magicb...@hotmail.com [mailto:magicb...@hotmail.com
> ]
> *Sent:* Tuesday, May 10, 2016 4:30 PM
> *To:* openstack@lists.openstack.org
> *Subject:* [Openstack] Heat autoscaling: heat.engine.resource Forbidden:
> You are not authorized to perform the requested action.
>
>
>
> Hi
>
> testing Openstack Mitaka (deployed with Mirantis FUEL 8.0), when testing
> Heat Autoscaling, I get this error:
>
> *heat.engine.resource Forbidden: You are not authorized to perform the
> requested action.*
>
>
>
> Any ideas on what's going on?
>
>
>
> Thanks in advance.
>
> J
>
>
>
>
>
> --
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy.
>
> __
>
> www.accenture.com
>
>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat autoscaling: heat.engine.resource Forbidden: You are not authorized to perform the requested action.

[magicb...@hotmail.com]

Hi again,

these are the roles I have :

#openstack role list
+--+-+
| ID   | Name|
+--+-+
| 0d77782f1ae54fa799b0585b267fb746 | ResellerAdmin   |
| 2c0a5b381f2b4f10b42aaa09678210a5 | heat_stack_user |
| 9fe2ff9ee4384b1894a90878d3e92bab | _member_|
| d819d32c0eba4c86a99241e741c241c1 | admin   |
| e0729bbb6f8544268fd371e50682754a | SwiftOperator   |


So, there is no "heat_stack_owner" role defined in my environment, but 
you're right, in 
http://docs.openstack.org/draft/install-guide-ubuntu/heat-install.html 
docs says:


/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/


Is this a bug in Mirantis MOS 8.0?


On 10/05/16 17:05, magicb...@hotmail.com wrote:


Hi Raghavendra,


how can I check those privileges? Even with "admin" user, I get the 
same error. :(


Best regards

J.

On 10/05/16 13:23, raghavendra@accenture.com wrote:


Hi Mag,

Please check if you have provided the *heat-stack-owner* and *admin 
*privileges to the tenant then try to spin up the Heat stack.


Regards,

Raghavendra Lad

*From:*magicb...@hotmail.com [mailto:magicb...@hotmail.com]
*Sent:* Tuesday, May 10, 2016 4:30 PM
*To:* openstack@lists.openstack.org
*Subject:* [Openstack] Heat autoscaling: heat.engine.resource 
Forbidden: You are not authorized to perform the requested action.


Hi

testing Openstack Mitaka (deployed with Mirantis FUEL 8.0), when 
testing Heat Autoscaling, I get this error:


/heat.engine.resource Forbidden: You are not authorized to perform 
the requested action./


Any ideas on what's going on?

Thanks in advance.

J




This message is for the designated recipient only and may contain 
privileged, proprietary, or otherwise confidential information. If 
you have received it in error, please notify the sender immediately 
and delete the original. Any other use of the e-mail by you is 
prohibited. Where allowed by local law, electronic communications 
with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the 
purposes of information security and assessment of internal 
compliance with Accenture policy.

__

www.accenture.com




___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat autoscaling: heat.engine.resource Forbidden: You are not authorized to perform the requested action.

[magicb...@hotmail.com]

Hi Raghavendra,


how can I check those privileges? Even with "admin" user, I get the same 
error. :(


Best regards

J.

On 10/05/16 13:23, raghavendra@accenture.com wrote:


Hi Mag,

Please check if you have provided the *heat-stack-owner* and *admin 
*privileges to the tenant then try to spin up the Heat stack.


Regards,

Raghavendra Lad

*From:*magicb...@hotmail.com [mailto:magicb...@hotmail.com]
*Sent:* Tuesday, May 10, 2016 4:30 PM
*To:* openstack@lists.openstack.org
*Subject:* [Openstack] Heat autoscaling: heat.engine.resource 
Forbidden: You are not authorized to perform the requested action.


Hi

testing Openstack Mitaka (deployed with Mirantis FUEL 8.0), when 
testing Heat Autoscaling, I get this error:


/heat.engine.resource Forbidden: You are not authorized to perform the 
requested action./


Any ideas on what's going on?

Thanks in advance.

J




This message is for the designated recipient only and may contain 
privileged, proprietary, or otherwise confidential information. If you 
have received it in error, please notify the sender immediately and 
delete the original. Any other use of the e-mail by you is prohibited. 
Where allowed by local law, electronic communications with Accenture 
and its affiliates, including e-mail and instant messaging (including 
content), may be scanned by our systems for the purposes of 
information security and assessment of internal compliance with 
Accenture policy.

__

www.accenture.com


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Heat autoscaling: heat.engine.resource Forbidden: You are not authorized to perform the requested action.

[raghavendra.lad]

Hi Mag,

Please check if you have provided the heat-stack-owner and admin privileges to 
the tenant then try to spin up the Heat stack.

Regards,
Raghavendra Lad

From: magicb...@hotmail.com [mailto:magicb...@hotmail.com]
Sent: Tuesday, May 10, 2016 4:30 PM
To: openstack@lists.openstack.org
Subject: [Openstack] Heat autoscaling: heat.engine.resource Forbidden: You are 
not authorized to perform the requested action.


Hi

testing Openstack Mitaka (deployed with Mirantis FUEL 8.0), when testing Heat 
Autoscaling, I get this error:

heat.engine.resource Forbidden: You are not authorized to perform the requested 
action.



Any ideas on what's going on?



Thanks in advance.

J







This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy.
__

www.accenture.com
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Heat autoscaling: heat.engine.resource Forbidden: You are not authorized to perform the requested action.

[magicb...@hotmail.com]

Hi

testing Openstack Mitaka (deployed with Mirantis FUEL 8.0), when testing 
Heat Autoscaling, I get this error:


/heat.engine.resource Forbidden: You are not authorized to perform the 
requested action./



Any ideas on what's going on?


Thanks in advance.

J



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [heat]Provides different stack quota to tenant

[Clint Byrum]

Excerpts from Sylvernass Arthas's message of 2016-05-08 05:33:13 -0700:
> Hi, guys
> 
>   Now, all tenant share the public config "max_stacks_per_tenant" which 
> decides maximum number of stacks any one tenant may have active at one time, 
> the default value is 1000.
> Should heat provides ability to set this config by different tenant? For 
> example, in a enterprise, maybe tenant A needs 1 stack quota, tenant B 
> needs 100 stack quota, but now heat can't manage with it, at least in 
> Liberity.
>   So in future, will heat provides this ability or other policy to solve this?

I think enough people have stated that they want it that it will happen
some day. There may even be a spec now, I haven't been tracking all of
the specs. However, I don't actually think there's any point to Heat
quotas, as the resources used to run a Heat stack are so much cheaper
compared to the resources it enables the user to consume -- servers,
networks, volumes, etc. One might as well let users run as many heat
stacks as they want within reason, as their quotas on those items will
fill up far before they cost you any actual money.

In fact, the only reason the max setting exists now is to protect the code
that does stack listing from eating up all of the memory on the servers.
It has a second unintended use case which is to prevent anyone from
using Heat as free object storage. :)

It's important to take my words with a grain of salt. I'm not directly
involved with Heat anymore.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [heat]Provides different stack quota to tenant

[Sylvernass Arthas]

Hi, guys

  Now, all tenant share the public config "max_stacks_per_tenant" which decides 
maximum number of stacks any one tenant may have active at one time, the 
default value is 1000.
Should heat provides ability to set this config by different tenant? For 
example, in a enterprise, maybe tenant A needs 1 stack quota, tenant B 
needs 100 stack quota, but now heat can't manage with it, at least in Liberity.
  So in future, will heat provides this ability or other policy to solve this?
  Thank you.
Sylvernass
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Heat: error in templates related with JSON

[magicb...@hotmail.com]

Hi


I've setup an small lab based on Liberty (FUEL 8.0), and started to test 
some heat-templates:


/git clone https://github.com/openstack/heat-templates.git/

I've detected that all resources type "OS::Heat::SoftwareConfig" which 
have references to external files like "config: { get_file: 
db_install.sh }" aren't accepted by the heat server with an error 
related with JSON:


/[user1@linux wordpress]$openstack orchestration template validate -t 
WordPress_software-config_2-instances.yaml //
//b"#!/bin/bash -v\n\nyum -y install mariadb mariadb-server\ntouch 
/var/log/mariadb/mariadb.log\nchown mysql.mysql 
/var/log/mariadb/mariadb.log\nsystemctl start mariadb.service\n\n# Setup 
MySQL root password and create a user\nmysqladmin -u root password 
$db_rootpassword\ncat << EOF | mysql -u root 
--password=$db_rootpassword\nCREATE DATABASE $db_name;\nGRANT ALL 
PRIVILEGES ON $db_name.* TO '$db_user'@'%'\nIDENTIFIED BY 
'$db_password';\nFLUSH PRIVILEGES;\nEXIT\nEOF\n" is not JSON serializable/



It looks like the engine isn't able to serialize the content of the 
referenced files.


Any ideas? Thanks in advance

J.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Heat] Mitaka RC3 available

[Thierry Carrez]

Due to new release-critical issues spotted in Heat during RC2 testing, a 
new release candidate was created for Mitaka. You can find the RC3 
source code tarball at:


https://tarballs.openstack.org/heat/heat-6.0.0.0rc3.tar.gz

Unless new release-critical issues are found that warrant a last-minute 
release candidate respin, this tarball will be formally released as the 
final "Mitaka" version on April 7th. You are therefore strongly 
encouraged to test and validate this tarball !


Alternatively, you can directly test the mitaka release branch at:

http://git.openstack.org/cgit/openstack/heat/log/?h=stable/mitaka

If you find an issue that could be considered release-critical, please
file it at:

https://bugs.launchpad.net/heat/+filebug

and tag it *mitaka-rc-potential* to bring it to the Heat release crew's 
attention.



--
Thierry Carrez (ttx)

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack