-
Notifications
You must be signed in to change notification settings - Fork 29
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
VM management for sanzu broker #52
Comments
We have coded a kind of "virtual machine orchestrator".
The 'virtual machine orchestrator' uses xml templates to describe libvirt configuration, and add user informations at connection time. We haven't published the 'virtual machine orchestrator', as it may be linked to you architecture, but we may add it to the sanzu anyway in the future. Keep in mind that there may be other ways to do this using on the shelves orchestrators and you are not linked to this custom "virtual machine orchestrator" |
Thanks for the answer, What I would like to do is the deployment of my own VM cluster and indeed, the method that you used was the one I was thinking of because I am also using a custom VM orchestrator (VMware vCenter). I am curious about the parameters you attribute to a VM and how much resources it consumes. |
Hi @serpilliere |
Hi, thank you for all answers @serpilliere ! |
Thank you for your help, I have now a better understanding of Sanzu and how it works.
I don't know if I should open another issue for this question, but I was wondering how does your VM cluster work. Indeed, I'm trying to have a better understanding of the structure but I didn't find something in the source code concerning the call of VM or something similar yet.
I saw in SSTIC acts that you are using a VMM and that there is a script run by the broker that took a free VM in a pool of unassigned VMs already started and once it's done, the VMM re-runs another VM so I was wondering what VMM did you use and how do you proceed to create this VM pool (VM templating...) ?
Originally posted by @rbah31 in #40 (comment)
The text was updated successfully, but these errors were encountered: