Dependecies of OpenStack VM

asked 2019-04-18 10:47:27 -0500

najeh gravatar image

updated 2019-04-18 16:28:18 -0500

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?

edit retag flag offensive close merge delete


@Bernd Bausch have you any idea about this question ?

najeh gravatar imagenajeh ( 2019-04-18 16:28:50 -0500 )edit

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.

Bernd Bausch gravatar imageBernd Bausch ( 2019-04-18 18:17:11 -0500 )edit

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 gravatar imageBernd Bausch ( 2019-04-18 18:21:01 -0500 )edit

@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

najeh gravatar imagenajeh ( 2019-04-19 05:04:26 -0500 )edit

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.

Bernd Bausch gravatar imageBernd Bausch ( 2019-04-19 06:27:08 -0500 )edit