In private cloud datacenters, Abiquo supports guest setup with cloud init or hypervisor tools. In public cloud providers, Abiquo supports cloud init, and in AWS it also supports provider setup tools.
Guest setup runs the first time you deploy a VM. The hypervisor tools guest setup also runs when you add a NIC. If the guest setup is not successful, the VM deploy or reconfigure will fail and roll back.
...
Mermaid | ||||||
---|---|---|---|---|---|---|
| ||||||
{"diagramDefinition":"flowchart LR\nZ(( ))\nstyle Z fill:#g1g,stroke:#100,stroke-width:20px\nZ-->A(<font color=ffffff>Public)\n A-->B(<font color=ffffff>AWS)-->C(\nA1[<font color=ffffff>Cloud-init</br>or similar]-->|Deploy|B1{<font color=ffffff>Provider}-->|Public|C1[/<font color=ffffff>Metadata/]-->D1{<font color=ffffff>AWS options)\n A-->D(+</br>win}-->|yes|E1[<font color=ffffff>Azure)-->E(ffffff>AWS guest</br>set up]\nB1-->|Hypervisor or VCD|F1[/<font color=ffffff>Win)ffffff>Configuration</br>drive/]-->F(>G1[<font color=ffffff>Guest passwords)\n Z-->G(<font color=ffffff>Private)\n G-->H(<font color=ffffff>Hypervisor tools)-->I(<font color=ffffff>Win)-->J(<font color=ffffff>Custom Specification)\n I-->K(<font color=ffffff>Unattend file)\n H-->L(<font color=ffffff>Linux)-->M(<font color=ffffff>Config)\n G-->N(<font color=ffffff>Cloud init)-->O(<font color=ffffff>Linux)-->P(<font color=ffffff>Check network in OS)\n N-->Q(<font color=ffffff>Win?)\nstyle A fill: #00457a,stroke: #00457a\nstyle G fill: #00457a,stroke: #00457a\nstyle Bffffff>Network via DCHP </br>or Static IP injection]\n\nA2[<font color=ffffff>Hypervisor</br>tools]-->|Deploy </br> </br> Reconfigure: no DHCP|B2{<font color=ffffff>OS}-->|Win|Z-->c2[/<font color=ffffff>Unattend file/]-->D2[<font color=ffffff>Network via </br>DHCP only]\nZ(( ))\nstyle Z fill:#g1g,stroke:#100,stroke-width:2px\nZ-->f2[/<font color=ffffff>Custom</br>specification/]-->G2[<font color=ffffff>Network via DHCP </br>or Static IP injection] \nB2-->|Linux|h2[/<font color=ffffff>Custom</br>specification/]-->I2[<font color=ffffff>Network via DHCP </br>or Static IP injection] \n \n \n \n\nstyle A1 fill: #ff9f3c,stroke: #ff9f3c\nstyle CB1 fill: #ff9f3c,stroke: #ff9f3c\nstyle DD1 fill: #ff9f3c,strokestrfke: #ff9f3c\nstyle EE1 fill: #ff9f3c,stroke: #ff9f3c\nstyle FF1 fill: #ff9f3c,stroke: #ff9f3c\nstyle HC1 fill: #ff9f3c,stroke: #ff9f3c\nstyle IG1 fill: #ff9f3c,stroke: #ff9f3c\nstyle JA2 fill: #ff9f3c,stroke: #ff9f3c\nstyle KB2 fill: #ff9f3c,stroke: #ff9f3c\nstyle Mc2 fill: #ff9f3c,stroke: #ff9f3c\nstyle ND2 fill: #ff9f3c,stroke: #ff9f3c\nstyle Of2 fill: #ff9f3c,stroke: #ff9f3c\nstyle Ph2 fill: #ff9f3c,stroke: #ff9f3c\nstyle QG2 fill: #ff9f3c,stroke: #ff9f3c\nstyle LI2 fill: #ff9f3c,stroke: #ff9f3c"} |
Table of guest setup functionality
Functionality | Hypervisor | Cloud-init | Cloud-init |
---|---|---|---|
Set fully qualified domain name (FQDN) | |||
Generate a random password at deploy and | Azure | ||
Inject network configuration if no DHCP server is available |
| ||
Inject SSH keys into guest. | |||
Configuration drive with environment variables and |
| ||
VM variables as metadata |
| ||
Bootstrap script or cloud configuration |
Notes:
- For Windows with hypervisor tools, use a custom specification instead of an unattend file. See Limitations of a custom specification to configure Windows
- For Linux with hypervisor tools, the platform will inject a global DNS configuration that will apply to all NICs on the VM
- See Configuration drive
Configure guest setup
...
Child pages (Children Display) |
---|
And for public cloud, see:
...
User guest setup functionality
For user guest setup functionality see: