Comment 3 for bug 1581447

The security groups refer to each other in the template, and cause circular reference. Heat wouldn't know which ones to create first, and hence it bails out with the Circular Reference exception. Not sure if we can re-write this template in a way that we avoid circular reference, I will leave it to the experts. Other possible solutions could be to (1) First create the stack with security groups and then take the physical resource ids of security groups and update the template and update the stack; (2) In heat we add a new resource OS::Neutron::AddSGRules, which will give the template authors the flexibility to add SG rules in same template.