You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating multiple VPCs in a project it gets created with a network domain like this: cs<project_account_id>. This means all VPCs in the same project gets the same network domain. Creating instances with duplicate names in a project with the same FQDN is currently possible. This can create issues when registering these instances to FreeIPA etc.
Similarly, duplicate hostnames within a VPC can be created if the instances are in different tiers.
It would be nice to have an option to restrict duplicate instance names in a project, network domain and VPC.
The text was updated successfully, but these errors were encountered:
automatic resolution by adding a counter or adding vpc-id
making the field obligatory and/or throw an error on conflict and let the user add the name
not sure what is preferable, but I think user friendliness may suffer in both approaches.
* automatic resolution by adding a counter or adding vpc-id
* making the field obligatory and/or throw an error on conflict and let the user add the name
not sure what is preferable, but I think user friendliness may suffer in both approaches.
@DaanHoogland these should do, there is one more option. A global setting to restrict duplicate instance names per network domain.
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
SUMMARY
When creating multiple VPCs in a project it gets created with a network domain like this: cs<project_account_id>. This means all VPCs in the same project gets the same network domain. Creating instances with duplicate names in a project with the same FQDN is currently possible. This can create issues when registering these instances to FreeIPA etc.
Similarly, duplicate hostnames within a VPC can be created if the instances are in different tiers.
It would be nice to have an option to restrict duplicate instance names in a project, network domain and VPC.
The text was updated successfully, but these errors were encountered: