Dependecies of OpenStack VM
Is the time of an OpenStack virtual machine creation depends on its content?
for example, in my configuration instances launched with m1.medium flavor take more time than launched with m1.large
for example, an empty virtual machine and another machine contain a system (Docker for example)
What are the variations that can impact a VM?
@Bernd Bausch have you any idea about this question ?
What do you mean by time of VM creation? Time until the instance is ACTIVE? Time until you get a login prompt in the console? Time until you can ssh into it?
Different images perform different things when starting up. Time until prompt and time until ssh depend on VM's startup process.
What do you mean by VM content? Image or Flavor? You first example tests the same image with different flavors. The second example uses different images.
I heard that Windows clears all RAM when starting. If so, RAM size impacts startup time. Other than that, I don't know how flavors impact this.
@Bernd Bausch I mean by content, systems installed inside an instance such as docker
The time is the time until the vm being active, m1.medium VM take more time than m1.large VM
In this case, the first example doesn't match the question. Content is the same, flavors are different.
I don't know when exactly an instance's state is set to ACTIVE, but perhaps this diagram helps.