Changes between Initial Version and Version 1 of specs/Phase I/BEN VLANs + Xen Virtual Machines

12/08/08 19:38:04 (11 years ago)
aydan (IP:



  • specs/Phase I/BEN VLANs + Xen Virtual Machines

    v1 v1  
     1= BEN VLANs + Xen Virtual Machines = 
     3[wiki:"specs/Phase I" Back to Phase I task list] 
     5Status: PENDING 
     7== User Story == 
     9Once we can successfully allocate a VLAN from BEN using Orca, we should be able to allocate Xen virtual machines and link them using the allocated BEN VLAN. 
     11== Technical Specification == 
     13Each virtual machine has two networks: 
     14 * a management network - used by Orca to manage the VM. IP addresses on this network are supplied and managed by the ORCA site at each BEN hub 
     15 * a data network - used by Orca to link related virtual machines in the same VLAN. IP addresses on this network are supplied and allocated by the end user 
     17To acquire a Xen virtual machine linked by a BEN VLAN, a service manager performs the following: 
     18 * requests a ticket for a BEN VLAN by sending the ticket to the BEN VLAN clearing house 
     19 * requests a ticket for VMs at the desired BEN hubs to the BEN VM clearing house (NOTE, for now the VLAN and VM clearing house will be two separate brokers) 
     20 * redeems the BEN VLAN ticket with the BEN VLAN site authority 
     21 * "attaches" the BEN VLAN lease to each BEN VM request and redeems the request with the appropriate BEN VM site 
     23If a service manager already has a lease for a BEN VLAN, it only needs to issue requests for BEN VMs. Note that the lease for the BEN VLAN must also be "attached" to each of the BEN VM reservations. 
     25== Implementation Notes == 
     27The first cut of this task will be implemented using the existing Orca broker and site VM policies. The goal is to make quick progress and identify the potential problematic areas first, and then simplify/optimize the policies. Note that once, the first iteration is over, we should switch to using the simplified Orca policies '''add links'''. 
     29We need a configuration with the following actors: 
     31 - BEN VLAN Site 
     32 - BEN VLAN Broker 
     33 - BEN VM Site (RENCI) 
     34 - BEN VM Site (DUKE) 
     35 - BEN VM Broker (one broker for all BEN Hubs) 
     36 - A service manager 
     38All actors will communicate using SOAP.  
     40We will implement the integration of the actors in several stages: 
     42 1. All actors in one container (command line execution) 
     43 2. All actors in one container (tomcat) 
     44 3. Separate the actors as follows: 
     45   - RENCI container: 
     46      - BEN VLAN Site, BEN VLAN Broker, BEN VM Broker, BEN VM Site (RENCI), Service Manager 
     47   - DUKE container: 
     48      - BEN VM Site (DUKE) 
     50To support the third stage, we will need some tools to simplify the deployment of multiple containers to enable rapid testing. In particular, we need tools to deploy all containers, authorize actors to talk to each other, make the necessary exports, and reset the inventory. Note: these tools are not absolutely necessary, but they will make future work much easier. 
     52The goal of stage one is to demonstrate the linking of VLANs and Xen VMs. We will implement an Orca unit test to test the request protocol for VMs with BEN VLAN. 
     54Before we can move to stage two, we need to create a portal plugin page to allow for the creation of VMs linked using a BEN VLAN. The exact specification of this plugin will be provided in the need future. 
     56Once stage two is complete, we can subdivide the actors into multiple containers. 
     58== Related Tickets == 
     60This section should list any tickets added as a result of this task.  
     62 * #