Ask Your Question

Eric GH's profile - activity

2017-11-15 06:22:44 -0600 received badge  Nice Question (source)
2015-05-31 01:08:33 -0600 received badge  Taxonomist
2014-09-17 08:34:20 -0600 received badge  Famous Question (source)
2014-08-28 09:30:49 -0600 received badge  Notable Question (source)
2014-08-28 08:39:19 -0600 answered a question subnet vs network to set in the OS::Neutron::Port

Just tried. It did not pass thru with the only subnet-id

Property network_id not assigned
2014-08-28 08:03:21 -0600 received badge  Popular Question (source)
2014-08-27 21:52:44 -0600 asked a question subnet vs network to set in the OS::Neutron::Port

in the OS::Neutron::Port defination

heat_template_version: 2013-05-23
...
resources:
  ...
  the_resource:
    type: OS::Neutron::Port
    properties:
      admin_state_up: Boolean
      allowed_address_pairs: [{"ip_address": String, "mac_address": String}, {"ip_address": String, "mac_address": String}, ...]
      device_id: String
      device_owner: String
      **fixed_ips**: [{"subnet_id": String, "subnet": String, "ip_address": String}, {"subnet_id": String, "subnet": String, "ip_address": String}, ...]
      mac_address: String
      name: String
      **network: String**
      security_groups: [Value, Value, ...]
      value_specs: {...}

Both the network and subnet are optional Properties

Is that true if I have both information I would rather just use the subnet (as it shall belong to one network) if I use static IP?

2014-07-29 08:34:22 -0600 commented answer Heat run user-data before create user

Not sure if you run the nova command with the userdata option. You might like see more here

http://docs.openstack.org/user-guide/...

I thought the 'ubuntu' user is built in the default image. and ec2-user is the user to when manipulate the cloudinit/userdata.

2014-07-25 09:49:46 -0600 answered a question Heat run user-data before create user

I believe you are right. see below /etc/rc.d/rc5.d/

lrwxrwxrwx. 1 root root 26 Mar  4 21:15 S50cloud-init-local -> ../init.d/cloud-init-local
lrwxrwxrwx. 1 root root 20 Mar  4 21:15 S51cloud-init -> ../init.d/cloud-init
lrwxrwxrwx. 1 root root 22 Mar  4 21:15 S52cloud-config -> ../init.d/cloud-config
lrwxrwxrwx. 1 root root 21 Mar  4 21:15 S53cloud-final -> ../init.d/cloud-final
lrwxrwxrwx. 1 root root 14 Feb 25 12:00 S55sshd -> ../init.d/sshd

The cloud-init process is at 50-53 step in the boot sequence.

And one workaround for this case is to manually create user before other content in the user-data

2014-07-22 08:44:46 -0600 received badge  Famous Question (source)
2014-07-14 21:15:19 -0600 commented question wait condition in HOT heat template

hi zaneb - thanks for the attention.

From the log seem the signal/curl did not yield any error. Though "first_wait" can not finish the instantiation and "second" never get instantiated.

2014-07-14 18:40:36 -0600 received badge  Notable Question (source)
2014-07-14 15:30:25 -0600 answered a question Metadata proxy 500 error from instances havana

Not sure if runing "export no_proxy=169.254.169.254" helps in your situation.

2014-07-10 16:36:13 -0600 commented answer Error: Resource create failed: WaitConditionTimeout: 0 of 1 received

I have post another record here https://ask.openstack.org/en/question... highly appreciate any input. Thanks.

2014-07-10 12:20:08 -0600 commented answer wait condition in HOT heat template

NP HoangDo. We are all learning here :) Now the HOT template supports the updateWaitcondition. So assume this (boot)waitcondition will be supported too. so let's wait for guru to share the snippet.

2014-07-10 10:53:37 -0600 received badge  Student (source)
2014-07-10 10:39:14 -0600 received badge  Popular Question (source)
2014-07-10 08:46:40 -0600 commented answer wait condition in HOT heat template

Thanks HoangDo

I might not have specified my question clearly. The depends_on keyword only control the booting sequence in general, not in accuracy. the depends_on keywords really can not control the "second" to start after the "first"'s time consuming cloud-init steps are done.

2014-07-09 07:34:31 -0600 asked a question wait condition in HOT heat template

Hi all,

Anyone kindly send me one copy of HOT heat template that utilize the wait conditions (to control the boot sequence).

THANKS A lot!

Eric

I tried snippet as below: Not working for me. From the log seem the signal/curl did not yield any error. Though "first_wait" can not finish the instantiation and "second" never get instantiated.

 first:
    type: OS::Nova::Server
    properties:
      key_name: PCM-I
      flavor: m1.small
      user_data:
        str_replace:
          template: |
            #!/bin/bash -v
            **# TIME-CONSUMING TASKS here**
            /usr/bin/cfn-signal -s true $wait_handle
          params:
            $wait_handle: {get_resource: first_wait_handle}
  first_wait_handle:
    type: AWS::CloudFormation::WaitConditionHandle
  first_wait:
    type: AWS::CloudFormation::WaitCondition
    depends_on: first
    properties:
      Handle: {get_resource: first_wait_handle}
      Timeout: 1000
  second:
    type: OS::Nova::Server
    depends_on: first_wait
    properties:
      key_name: PCM-I
      image: v37
      flavor: m1.small
      networks:
        - port: { get_resource: server2_port }
      user_data: |
        #!/bin/bash
        echo "second is up"

the user data execution yield no error but the VM "second" can not the instantiate.

/usr/bin/cfn-signal -s true http://152.148.165.80:8000/v1/waitcondition//arn%3Aopenstack%3Aheat%3A%3A782fc66f9e654fc887ff8c41f0539125%3Astacks%2Fh01%2F2502b22d-68fa-4f11-9db3-fdd157ba6df7%2Fresources%2Ffirst_wait_handle?Timestamp=2014-07-09T19%3A32%3A57Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=1d9b6cc686994b569c78401989f377b8&SignatureVersion=2&Signature=aJeIaDcktR2uUPpb6BLqvVA3jVGCBTw364FxxWGXa%2Bk%3D 
echo $?
DEBUG [2014-07-09 15:33:43,807] cfn-signal called Namespace(data='Application has completed configuration.', exit=None, exit_code=None, reason='Configuration Complete', success='true', unique_id='00000', url='http://152.148.165.80:8000/v1/waitcondition//arn%3Aopenstack%3Aheat%3A%3A782fc66f9e654fc887ff8c41f0539125%3Astacks%2Fh01%2F2502b22d-68fa-4f11-9db3-fdd157ba6df7%2Fresources%2Ffirst_wait_handle?Timestamp=2014-07-09T19%3A32%3A57Z') 
DEBUG [2014-07-09 15:33:43,807] Running command: curl -X PUT -H 'Content-Type:' --data-binary '{"Status": "SUCCESS", "Reason": "Configuration Complete", "Data": "Application has completed configuration.", "UniqueId": "00000"}' "http://152.148.165.80:8000/v1/waitcondition//arn%3Aopenstack%3Aheat%3A%3A782fc66f9e654fc887ff8c41f0539125%3Astacks%2Fh01%2F2502b22d-68fa-4f11-9db3-fdd157ba6df7%2Fresources%2Ffirst_wait_handle?Timestamp=2014-07-09T19%3A32%3A57Z"

Provision done: 2014-07-09 15:33:43.959063

If I manually run the command in the vm... Same result. (please note that http://152.148.165.80:8000/v1 is Cloudformation address)

[root@h01-first-4uc2my6jgaxh /]# /usr/bin/cfn-signal -e 0 http://152.148.165.80:8000/v1/waitcondition//arn%3Aopenstack%3Aheat%3A%3A782fc66f9e654fc887ff8c41f0539125%3Astacks%2Fh01%2F92dc4efb-2372-4f09-93cf-79cd6efbc69c%2Fresources%2Ffirst_wait_handle?Timestamp=2014-07-22T13%3A41%3A49Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=656537dd84064705a73a8e9bb9c5dd60&SignatureVersion=2&Signature=fXdSTNue0kH8OCjAdU%2BGR72uQacMIsgA7sjWImDegw8%3D
[1] 4817
[2] 4818
[3] 4819
[4] 4820
[root@h01-first-4uc2my6jgaxh /]# DEBUG [2014-07-22 10:36:30,191] cfn-signal called Namespace(data='Application has completed configuration.', exit=None, exit_code='0', reason='Configuration Complete', success='true', unique_id='00000', url='http://152.148.165.80:8000/v1/waitcondition//arn%3Aopenstack%3Aheat%3A%3A782fc66f9e654fc887ff8c41f0539125%3Astacks%2Fh01%2F92dc4efb-2372-4f09-93cf-79cd6efbc69c%2Fresources%2Ffirst_wait_handle?Timestamp=2014-07-22T13%3A41%3A49Z')
DEBUG [2014-07-22 10:36:30,191] Running command: curl -X PUT -H 'Content-Type:' --data-binary '{"Status": "SUCCESS", "Reason": "Configuration Complete", "Data": "Application has completed configuration.", "UniqueId": "00000"}' "http://152.148.165.80:8000/v1/waitcondition//arn%3Aopenstack%3Aheat%3A%3A782fc66f9e654fc887ff8c41f0539125%3Astacks%2Fh01%2F92dc4efb-2372-4f09-93cf-79cd6efbc69c%2Fresources%2Ffirst_wait_handle?Timestamp=2014-07-22T13%3A41%3A49Z"

[1]   Done                    /usr/bin/cfn-signal -e 0 http://152.148.165.80:8000/v1/waitcondition//arn%3Aopenstack%3Aheat%3A%3A782fc66f9e654fc887ff8c41f0539125%3Astacks%2Fh01%2F92dc4efb-2372-4f09-93cf-79cd6efbc69c%2Fresources%2Ffirst_wait_handle?Timestamp=2014-07-22T13%3A41%3A49Z
[2]   Done                    SignatureMethod=HmacSHA256
[3]-  Done                    AWSAccessKeyId=656537dd84064705a73a8e9bb9c5dd60
[4]+  Done                    SignatureVersion=2
[root ...
(more)
2014-04-15 00:35:45 -0600 received badge  Famous Question (source)
2014-04-14 08:28:05 -0600 received badge  Scholar (source)
2014-04-14 08:28:05 -0600 commented answer AttributeError: 'Client' object has no attribute 'software_configs'

Thanks Steve... That is very clear answer. Will double check the heat-engine and see if take the software_config

2014-04-01 09:35:26 -0600 received badge  Enthusiast
2014-03-31 23:48:45 -0600 received badge  Notable Question (source)
2014-03-31 12:59:04 -0600 received badge  Popular Question (source)
2014-03-25 09:13:44 -0600 commented answer AttributeError: 'Client' object has no attribute 'software_configs'

Thanks unmesh-gurjar!

I upgraded the heat client to 0.2.8. And still see the same issue...

2014-03-24 19:41:13 -0600 asked a question AttributeError: 'Client' object has no attribute 'software_configs'

Hi Gurus....

I met one problem when draft the HOT template. For user_data part.. Please see below for the key tags..

--------------------------------------
    heat_template_version: 2013-05-23
    ....
    resources:
      volume_format_init:
        type: OS::Heat::SoftwareConfig
        properties:
          config: |
            !/bin/bash
            mkdir -p /opt/mysql3
    ....

      OPPA:
        type: OS::Nova::Server
        properties:
          admin_user: lps
          key_name: { get_param : key_name }
    ....
          user_data_format: RAW
          user_data: |
            get_resource: volume_format_init
---------------------------------------------------------

With above template I could pass the template-validation but when I try to do the stack-create it will fail with message as below.

AttributeError: 'Client' object has no attribute 'software_configs'

[root@vNode3 v3]# heat --version
0.2.6

Same issue even I upgrade the heat client to 0.2.8.

Highly appreciate any hint/clue.

Thanks,