Actual bug state can be found in Murano launchpad page.
Due to current Heat limitation services that involve load-balancer creation (farms) can be deployed only by tenant administrators.
When Heat creates different clients for Nova, Cinder and others it doesn't pass SSL-related options to clients' constructor. If Nova is configured to have SSL endpoints and self-signed certificates Heat will fail to create instances because there is no way to disable server certificate validation as there is no "insecure" flag passed etc.
Farm services can't be deployed without KeyPair. If KeyPair is not set load balancer won't be created and these messages will show up in logs:
2013-08-06 09:10:07 - Unable to deploy instance ipkrmhk0vzq4b6 (asp-farm_instance_0) due to Unexpected state 2013-08-06 09:10:07 - Unable to create a Server Farm load balancer on unit ipkrmhk0vzq4b6 (asp-farm_instance_0) due to Unexpected stateAnd deploy will hang up.
MS SQL Cluster service relies on Quantum for 'virtual-ip' (address-pair) functionality, and to work on Nova Network or Quantum configured as "Mixed Flat and Private Network", anti-spoofing rules on compute nodes should be disabled.
Internet Information Services Web Farm & ASP.NET Application Web Farm services are based on Heat, particularly on resource called AWS::ElasticLoadBalancing::LoadBalancer, that currently does not support specification of any network related parameters. Without support for network configuration specification LoadBalancer does not work in Murano over OpenStack deployments with Quantum configured as "Per-tenant Routers with Private Networks".
