openstack nova实例启动的内部构件.docxVIP

PAGE 2 Source /posts/openstack-nova-internals-of-instance-launching/ OpenStack Nova internals of instance launching January 30, 2011 This article describes the internals of launching an instance in OpenStack Nova. Overview Launching a new instance involves multiple components inside OpenStack Nova: API server: handles requests from the user and relays them to the cloud controller. Cloud controller: handles the communication between the compute nodes, the networking controllers, the API server and the scheduler. Scheduler: selects a host to run a command. Compute worker: manages computing instances: launch/terminate instance, attach/detach volumes… Network controller: manages networking resources: allocate fixed IP addresses, configure VLANs… Note: There are more components in Nova like the authentication manager, the object store and the volume controller but we are not going to study them as we are focusing on instance launching in this article. The flow of launching an instance goes like this: The API server receives a run_instances command from the user. The API server relays the message to the cloud controller (1). Authentication is performed to make sure this user has the required permissions. The cloud controller sends the message to the scheduler (2). The scheduler casts the message to a random host and asks him to start a new instance (3). The compute worker on the host grabs the message (4). The compute worker needs a fixed IP to launch a new instance so it sends a message to the network controller (5,6,7,8). The compute worker continues with spawning a new instance. We are going to see all those steps in details next. API You can use the OpenStack API or EC2 API to launch a new instance. We are going to use the EC2 API. We add a new key pair and we use it to launch an instance of type m1.tiny. 1 cd /tmp/ 2 euca-add-keypair test test.pem 3 euca-run-instances -k test -t m1.tiny ami-tiny run_instances() in api/ec2/cloud.py is called which res