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

kvm: do not configure libvirtd to listen on TCP port 16509 #169

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

weizhouapache
Copy link
Member

This is the trillian setting for
apache/cloudstack-documentation#301
KVM: do not listen on TCP port when configure kvm host #301

@weizhouapache
Copy link
Member Author

Copy link
Member

@rohityadavcloud rohityadavcloud left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but some comments;
For firewall - both should be enabled? And, if listening on 16514 by default, the process may fail unless ssl/tls certs are configured.

@weizhouapache
Copy link
Member Author

weizhouapache commented Jan 31, 2023

LGTM but some comments; For firewall - both should be enabled? And, if listening on 16514 by default, the process may fail unless ssl/tls certs are configured.

@rohityadavcloud
16509 are only used for vm migration if no ssl is provisioned. it is useless in recent cloudstack versions.
if we add kvm host on cloudtack UI or via api, it will automatically set up certificates and use TLS port 16514.

it is not needed any more to configure libvirt to listen on unsecure tcp port 16509.

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 this pull request may close these issues.

2 participants