Nova hypervisor agents #8122
Draft
Nova hypervisor agents #8122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is heavily WIP, so better keep it apart for that reason alone. The other is, we want to deploy the hypervisor independently in a different cluster without pulling in rabbitmq, mariadb, etc...
Changing it doesn't help much, as the hypervisor-nodename comes from the OS directly.
Gardener cannot provide yet stable hostnames, so we need to hack it for now like that.
The common share moves all instance related storage to shared storage, making failover and migration easier.
This requires too much permissions for the pods, so it needs some replacing. But it works for now.
Cold migration requires that the nova user can ssh to the destination host to copy some file or at least to verify that it is a shared file-system between source and destination.
If the certificate expires, the services fails to restart eventually, so we have to start the service somehow. Any socket would do, and technically the shell command talks to the admin socket, but we want the tls socket to be up too, so why not start that one.
For a transitionary period, this script might co-exist with other handlers.
We will hopefully drop this soon.
As it contains a secret, it is already in a k8s-secret.
cert management is done by kvm-node-agent and placed to /var/lib/kvm-node-agent - a minor script is needed till symlinks are propagated via orabos image. downward api is now used for detecting host (nodename) and host ip address.
/var/lib/kvm-node-agent only exists on the host, not in the container. The links need to be relative, not absolute.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.