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

libvirt install: use fqdn for libvirt instance names #354

Closed
michaelgugino opened this issue Sep 27, 2018 · 4 comments · Fixed by #660
Closed

libvirt install: use fqdn for libvirt instance names #354

michaelgugino opened this issue Sep 27, 2018 · 4 comments · Fixed by #660

Comments

@michaelgugino
Copy link
Contributor

michaelgugino commented Sep 27, 2018

[root@mguginop50 ~]# virsh list
 Id    Name                           State
----------------------------------------------------
 1     master0                        running
 2     bootstrap                      running
 3     worker-sdb9x                   running

This output should match resolvable fqdn of the cluster. Would make cleaning up / managing easier.

@wking
Copy link
Member

wking commented Sep 27, 2018

Would make cleaning up / managing easier.

We have stubs for libvirt cleanup from #324 that use prefixes. Thoughts on that approach?

@michaelgugino
Copy link
Contributor Author

@wking I'm not worried about deprovisioning as a function of the installer, I'm concerned with good house-keeping and sensible naming of the libvirt instances. It doesn't make any sense to call a machine 'master0' in libvirt and then name it <cluster-name>-master-0.tt.testing everywhere else.

@wking
Copy link
Member

wking commented Nov 13, 2018

It doesn't make any sense to call a machine 'master0' in libvirt and then name it <cluster-name>-master-0.tt.testing everywhere else.

With #660, master nodes will be named {cluster-name}-master-{count}, which matches the hostname portion of their domain names. I don't think we need the base-domain suffix, because we're already requiring a unique-to-that-libvirt cluster name. Does that sound good to you?

@michaelgugino
Copy link
Contributor Author

@wking sounds good, thanks!

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

Successfully merging a pull request may close this issue.

2 participants