1 / 22

INFN OCCI implementation on Grid Infrastructure

INFN OCCI implementation on Grid Infrastructure. Michele Orrù INFN-CNAF OGF27, 13/10/2009. Outline. Farm virtualization: WNoD The need for IaaS integration IaaS Application internal architecture IaaS Application flow of control Future works. Virtualization within INFN.

harsha
Download Presentation

INFN OCCI implementation on Grid Infrastructure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. INFN OCCI implementation on Grid Infrastructure Michele Orrù INFN-CNAF OGF27, 13/10/2009 M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  2. Outline • Farm virtualization: WNoD • The need for IaaS integration • IaaS Application internal architecture • IaaS Application flow of control • Future works M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  3. Virtualization within INFN • INFN Tier-1 currently supports ca. 20 Virtual Organizations: each one has different software and resource requirements, and well-established workflows that should not be changed • To satisfy their needs INFN has developed a solution called WNoD (Virtual Worker Nodes on Demand) • With this kind of approach the installed software is not coupled anymore with physical hardware, and the resources are always dynamically shared thanks to the creation of VO-specific VMs at job execution time. Farm virtualization: WNoD M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  4. WNoD: high level design Farm virtualization: WNoD M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  5. Emerging Cloud requirements • Usage of Grid resources in a flexible way, without the complex workflow that a typical grid job might have • Third-party users (academia, industry, government) needing dynamic virtual execution environments • INFN developers needing customized platforms to deploy and test their applications • The idea is to keep the same LRMS that is already handling jobs from the Grid computing interface, and then expose a second service to manage requests of cloud-like resources. The need for IaaS integration M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  6. Grid & Cloud: high level overview • A mixed Grid infrastructure (both real and virtual worker nodes): only for job submission The need for IaaS integration M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  7. Grid & Cloud: high level overview • The same pool of resources is used to provide cloud-like services on the actual Grid infrastructure • This allows to have homogeneous sharing with the resources used through the Grid interface • Machines don’t need to be dedicated to either service The need for IaaS integration M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  8. The IaaS layer • We have implemented OGF's OCCI API as the interface of our application, due to its open and slim nature • This solution works today, with a small subset of the OCCI API: the user requests a computing resource, gets an IP address back from the application and can then connect to the VM via SSH. • The accounting and the authentication/authorization layers of the application will be completely integrated with the existing Grid infrastructure. • Java Enterprise application built with industry leader technologies such as Spring, Hibernate, JPA, Restlet, Jetty, Maven IaaS Application internal architecture M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  9. IaaS Application architecture IaaS Application internal architecture • We can fully leverage on unique Spring features such as Dependency Injection and Inversion of Control M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  10. OCCI implementation • RESTfulws endpoints are defined in Spring’s application context XML files: following the “compute” descriptor. <bean id="root" class="org.restlet.ext.spring.SpringRouter"> <property name="attachments"> <map> <entry key="/compute/{computeId}"> <bean class="org.restlet.ext.spring.SpringBeanFinder"> <lookup-method name="create" bean="computeResource"/> <property name="beanName" value="computeResource" /> </bean> </entry> </map> </property> </bean> <bean name="computeResource" class="com.infn.cnaf.resources.compute.ComputeResource" scope="prototype"> <property name="batchSystemController" ref="bsController" /> </bean> IaaS Application internal architecture M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  11. OCCI implementation • Operations are mapped to HTTP verbs with annotation metadata (@Get, @Post, @Put, @Delete) • Right now only plain-text format is supported on responses • We are integrating ATOM and JSON formats: • @Post • public Representation storeRepresentation(Representation entity) { • if (entity.getMediaType().equals(MediaType.APPLICATION_WWW_FORM, true)) {…}} IaaS Application internal architecture • @Get(“json”) • public Representation toJson() {…} M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  12. Flow of control: create compute resource 0/8 IaaS Application flow of control M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  13. Flow of control: create compute resource 1/8 IaaS Application flow of control M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  14. Flow of control: create compute resource 2/8 IaaS Application flow of control M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  15. Flow of control: create compute resource 3/8 IaaS Application flow of control M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  16. Flow of control: create compute resource 4/8 IaaS Application flow of control M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  17. Flow of control: create compute resource 5/8 IaaS Application flow of control M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  18. Flow of control: create compute resource 6/8 IaaS Application flow of control M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  19. Flow of control: create compute resource 7/8 IaaS Application flow of control M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  20. Flow of control: create compute resource 8/8 IaaS Application flow of control M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  21. On the way… • Support for multi-core VMs • UI improvements (Web based UI) • Full compliance with the OCCI API • Billing Future works M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

  22. Questions??? Questions? M.Orrù (INFN-CNAF) INFN OCCI implementation on Grid Infrastructure

More Related