murano/releasenotes/notes/shared-net-port-creation-0eda66be4444cf2f.yaml
Alexander Tivelkov 247c4bdfb9 Murano can now properly attach VMs to shared networks
When spawning VMs attached to pre-existing networks murano used to
generate a Heat template with a fixed_ips property for Neutron ports.
This can cause a policy violation if the target network is not owned
by the deploying tenant (i.e. the network is shared by some other
project).

This has been addressed: ExistingNeutronNetwork class no longer
generates the fixed_ips property of the port if the target network is
not owned by a current project.

Change-Id: I0c60a522f4223fdc47f87b950da1a0822a8cbdbe
Closes-bug: #1644797
2016-11-29 18:17:12 +03:00

11 lines
454 B
YAML

---
issues:
- If a VM being a part of some shared-ip group is attached to the network
which is not owned by the current tenant (shared network) a policy
violation may occur thus failing the deployment.
fixes:
- Murano no longer specifies fixed-ip parameter for ports when creating VMs
attached to networks owned and shared by other tenants. Specifying this
parameter for non-owned networks could cause violation of neutron policies.