Open Stack

Hello All,

I have configured openstack Havana on Ubuntu 12.04 . I configured heat & ceilometer.

When I was creating stack I found that stack creation failed in log

2014-03-21 05:37:50.170 22127 TRACE heat.engine.resource     raise exception.StackValidationFailed(message=msg)
2014-03-21 05:37:50.170 22127 TRACE heat.engine.resource StackValidationFailed: Unknown resource Type : AWS::CloudWatch::Alarm
2014-03-21 05:37:50.170 22127 TRACE heat.engine.resource
2014-03-21 05:37:50.203 22127 WARNING heat.engine.service [-] Stack create failed, status FAILED

So I added default.yaml in /etc/ceilometer/environment.d/
resource_registry:

    # allow older templates with Quantum in them.

    "OS::Quantum*": "OS::Neutron*"

    # Choose your implementation of AWS::CloudWatch::Alarm

    #"AWS::CloudWatch::Alarm": "file:///etc/heat/templates/AWS_CloudWatch_Alarm.yaml"

#   "AWS::CloudWatch::Alarm": "OS::Heat::CWLiteAlarm"

    "OS::Metering::Alarm": "OS::Ceilometer::Alarm"

#    "AWS::RDS::DBInstance": "file:///etc/heat/templates/AWS_RDS_DBInstance.yaml"

#    "AWS::CloudWatch::Alarm": "OS::Ceilometer::Alarm"


If I remove the comment from #   "AWS::CloudWatch::Alarm": "OS::Heat::CWLiteAlarm"         , restarted  my heat services . If I try to create a stack it shows below error

2014-03-21 05:34:09.748 21972 INFO heat.engine.resource [-] creating LoadBalancer "ElasticLoadBalancer"
2014-03-21 05:34:09.809 21972 INFO heat.engine.resource [-] Validating CeilometerAlarm "latency_watcher"
2014-03-21 05:34:09.809 21972 ERROR heat.engine.parser [-] Property error : latency_watcher: Property meter_name not assigned
2014-03-21 05:34:09.809 21972 TRACE heat.engine.parser Traceback (most recent call last):
2014-03-21 05:34:09.809 21972 TRACE heat.engine.parser   File "/usr/lib/python2.7/dist-packages/heat/engine/parser.py", line 308, in validate
2014-03-21 05:34:09.809 21972 TRACE heat.engine.parser     result = res.validate()
2014-03-21 05:34:09.809 21972 TRACE heat.engine.parser   File "/usr/lib/python2.7/dist-packages/heat/engine/resource.py", line 490, in validate
2014-03-21 05:34:09.809 21972 TRACE heat.engine.parser     return self.properties.validate()
2014-03-21 05:34:09.809 21972 TRACE heat.engine.parser   File "/usr/lib/python2.7/dist-packages/heat/engine/properties.py", line 695, in validate
2014-03-21 05:34:09.809 21972 TRACE heat.engine.parser     raise exception.StackValidationFailed(message=msg)
2014-03-21 05:34:09.809 21972 TRACE heat.engine.parser StackValidationFailed: Property error : latency_watcher: Property meter_name not assigned
2014-03-21 05:34:09.809 21972 TRACE heat.engine.parser
2014-03-21 05:34:09.811 21972 ERROR heat.engine.resource [-] CREATE : LoadBalancer "ElasticLoadBalancer"
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource Traceback (most recent call last):
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource   File "/usr/lib/python2.7/dist-packages/heat/engine/resource.py", line 358, in _do_action
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource     handle_data = handle()
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource   File "/usr/lib/python2.7/dist-packages/heat/engine/resources/loadbalancer.py", line 382, in handle_create
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource     return self.create_with_template(templ, param)
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource   File "/usr/lib/python2.7/dist-packages/heat/engine/stack_resource.py", line 101, in create_with_template
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource     nested.validate()
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource   File "/usr/lib/python2.7/dist-packages/heat/engine/parser.py", line 314, in validate
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource     raise StackValidationFailed(message=str(ex))
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource StackValidationFailed: Property error : latency_watcher: Property meter_name not assigned
2014-03-21 05:34:09.811 21972 TRACE heat.engine.resource
2014-03-21 05:34:09.842 21972 WARNING heat.engine.service [-] Stack create failed, status FAILED



Template details:
"CPUAlarmHigh": {
     "Type": "OS::Ceilometer::Alarm",
     "Properties": {
        "description": "Scale-up if cpu_util > 50% for 1 minute",
        "meter_name": "cpu_util",
        "enabled": "True",
        "repeat_actions": "True",
        "statistic": "avg",
        "period": "60",
        "evaluation_periods": "3",
        "threshold": "50",
         "comparison_operator" : "gt",
         "alarm_actions": [ { "Ref": "WebServerScaleUpPolicy" } ],
        "matching_metadata": {"metadata.user_metadata.server_group": "WebSG"}

      }
   },

"CPUAlarmLow": {
     "Type": "OS::Ceilometer::Alarm",
     "Properties": {
        "description": "Scale-up if cpu_util < 15% for 1 minute",
        "meter_name": "cpu_util",
        "enabled": "True",
        "repeat_actions": "True",
        "statistic": "avg",
        "period": "60",
        "evaluation_periods": "3",
        "threshold": "15",
         "comparison_operator" : "lt",
         "alarm_actions": [ { "Ref": "WebServerScaleUpPolicy" } ],
        "matching_metadata": {"metadata.user_metadata.server_group": "WebSG"}
        }
     },

"ElasticLoadBalancer" : {
      "Type" : "AWS::ElasticLoadBalancing::LoadBalancer",
      "Properties" : {
        "AvailabilityZones" : { "Fn::GetAZs" : "" },
         "Listeners" : [ {
          "LoadBalancerPort" : "80",
          "InstancePort" : "80",
          "Protocol" : "HTTP"
        } ],
        "HealthCheck" : {
          "Target" : "HTTP:80/",
          "HealthyThreshold" : "3",
          "UnhealthyThreshold" : "5",
          "Interval" : "30",
          "Timeout" : "5"
        }


Pelase help me


Regards,
Malleshi CN

________________________________

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140321/17809faf/attachment.html>