Mumbai University >Information Technology>Sem7>Cloud Computing

Marks: 10 M

Year: May 2012

1. Fabric Controller abstracts underlying infrastructure components like virtualized server, network, components, DNS, load balance and OS replication from compute and storage service.

2. FC read service configuration information of cloud service to deploy the service and spawns server virtual machine required to deploy the services.

3. The deployment of service and spawning virtual instance of service are transparent to developers.

4. Once deployed it is managed by windows Azure.

5. User needs to specify the end states of cloud services in configuration file, and window Azure will provide necessary hardware, software to achieve it.

Fabric Controller Task.

1. Allocates the nodes.

2. Starts operating system images on the nodes.

3. Configure the settings as per service model described by the service creator.

4. Starts the service roles on allocated nodes.

5. Configures load balance access routers and switches.

6. Maintains the desired number of role instances of the service irrespective of any service, hardware or operating system failure.

• When FC is building a node in data center, Fabric Agent (FA) is included in and automatically initialized in root partition.

• FA exposes an API letting an instance interact with FC and is then used to managed guest Agent (GA) running in a guest VM i.e. child partition.

• Behind the scene, FC also makes itself highly available by replicating itself across group of machines. In short, FC is the kernel of cloud OS and manages both servers and services in data center.

Role of Fabric controller:

1) WAFC is a distributed applications that is replicated among group of machines.

2) WAFC controls & manages the servers and software’s that run on MS Data centers.

3) It has its own resources in its own environments like computers, load balancing, switches, etc

4) It keeps track of all windows Azure applications in fabric.

5) It can communicate with fabric agent (FA) on each machine.

6) It decides where the new application will learn.

7) It selects the physical server (node) so the hardware is automatically utilized.

8) It uses the configuration information from the XML file of each app to keep track of

->various instances of applications.

->no of virtual machines to be created for the app

9) It manages the OS instance in each instance of web & workers roles which includes

->OS patch updates

->System updates

->s/w updates

This allows developer to focus entirely on the creation of applications & not to worry about the management of the platform.

10) It makes sure that at least 2 instances of each function are underway. This allows you to turn one of them to update their s/w without stopping the entire application.

11) WAFC functions as the kernel of Azure OS.

12) It provisions, stores, delivers, monitors, command virtual machines & physical servers that make up Azure.