Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to restrict duplicate instance names in same network domain, VPC etc #9775

Open
rajujith opened this issue Oct 7, 2024 · 4 comments

Comments

@rajujith
Copy link
Collaborator

rajujith commented Oct 7, 2024

ISSUE TYPE
  • Improvement Request
COMPONENT NAME
API,UI 
CLOUDSTACK VERSION
4.19.1.1
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.

@DaanHoogland
Copy link
Contributor

@rajujith I can think of two solutions

  • 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.

@rajujith
Copy link
Collaborator Author

rajujith commented Oct 8, 2024

@rajujith I can think of two solutions

* 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.

@DaanHoogland DaanHoogland added this to the 4.19.2.0 milestone Oct 8, 2024
@kiranchavala
Copy link
Contributor

kiranchavala commented Oct 9, 2024

@rajujith can this PR solve the issue to some extent #9780

@rajujith
Copy link
Collaborator Author

rajujith commented Oct 9, 2024

@rajujith can this PR solve the issue to some extent #9780

Doesn't look like it @kiranchavala .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants