3. C-DAC an overview
• C-DAC : seeded at Pune Centre in 1987
– High Performance Computing (HPC) – the focal area then
• Later started
– Multilingual Computing (1988)
– Advanced Computing Training School (ACTS) (1993)
• Subsequently added activities
– Healthcare
– e-Governance
• Multimedia
– Geo-Matics
• Merger of 3 premier societies of DIT with C-DAC in December, 2002
– ( ERDCI- 1982 – 88, NCST- 1985, CEDTI-1990 )
– ( Electronics, Software, Training & skills development)
5. Thematic focus areas of C-DAC
• High Performance Computing & Grid Computing
– Hardware, Software, Systems, Applications, Research, Technology,
Infrastructure
• Multilingual Computing and Heritage Computing
– Tools, Fonts, Products, Solutions, Research, Technology
Development
• Health Informatics
– Hospital Information System, Telemedicine, Decision Support
System, Tools, Traditional Knowledge-base and DSS for Medicine
• Software Technologies, including FOSS
– OSS, Multimedia, ICT for masses, E-Governance, Geo-Matics, ICT4D
6. Thematic focus areas of C-DAC
• Professional Electronics including VLSI & Embedded Systems
– Digital Broadband and Wireless Systems, Network Technologies,
Power Electronics, Real-Time Systems, Control Electronics,
Embedded Systems, VLSI/ASIC Design, Agri Electronics, Strategic
Electronics
• Cyber Security & Cyber Forensics
– Cyber Security tools, technologies & solution development, Research
& Training
11. GARUDA
• India’s National Grid Computing Initiative
• Distributed across 45 institutions in 17 locations.
• Total:1560 CPUs and 15.2 TF
• Network : National Knowledge Network (linking all research & educational
institutes on high speed backbone )
• Certificate : IGCA (Indian Grid Certificate Authority)
• Applications include - Disaster Management; Computer Aided Engineering;
Climate Modeling; Medical and Health Care; Collaborative Class Room
12. Garuda – Some Applications
• Development and parallelization of 2D model based Seismic Waveform
inversion algorithm and software for estimating the elastic properties of the
earth.
• Portal which provides a web-interface for Bioinformatics applications in
Sequence Analysis and Molecular Modeling running on a High Performance
Computer. iMolDock
• Molecular Modeling docking application, which helps the user to find out
appropriate ligands for particular proteins. EQ-Check
• To tackle problems related to checking and design of earthquake resistant
structures, potentially saving money, structures and lives. SD2000
• SD2000 is a supercomputing based Decision Support System using
Mathematical, Statistical and Artificial Intelligence more..
14. Private Cloud Infrastructure
Computational resources @ three locations Hyderabad, Bengaluru, Chennai
Make Model Processor RAM HDD Quantity
Dual Socket Quad Core Intel Xeon
HP DL 380 G5 X5460 @ 3.16GHz 32 GB 4 x 146GB 3
Dual Socket Quad Core Intel Xeon
HP DL 380G5 X5460 @ 3.16GHz 16 GB 2 x 250GB 1
Dual Socket Quad Core Intel Xeon
HP DL 160 G5 X5460 @ 3.16GHz 16 GB 2 x 250GB 40
Quad Core Intel Xeon E5405 @
HP DL 160G5 2.00GHz 2 GB 2 x 250GB 1
Dual Socket Dual Core Intel Xeon @
HP DL 360G4 3.60GHz 3 GB 160GB 8
HCL Global infinity Dual Core Intel Xeon @ 3.20GHz 2 GB 2 x 146GB 4
TOTAL 57
Computational resources
Make Description Capacity
20 x 300 GB 15K RPM SAS disks and 27 x 750 GB SATA disks 20 + 6 TB
EMC2 2 TB
TOTAL 28 TB
Network : NATIONAL KNOWLEDGE NETWORK
15. Underlying Technical components
CDAC Chennai Cloud powered by
•BOSS Advanced Server 1.0
•Xen Hypervisor 3.2
•Eucalyptus 2.0
•Hadoop
•Appscale
•Hyperic HQ
•CDAC Scripts for Metering & Billing integrated
with Eucalyptus
•CDAC Scripts for Elasticity integrated with
Eucalyptus
Garuda Grid powered by
•Globus Toolkit 4.*
•Torque
•Gridway
16. ON-GOING PROJECTS In Cloud
• Open Source Cloud Middleware development
• End to End Security for Cloud
• Integration of Garuda (India’s National Grid Computing Initiative)
with Cloud infrastructure @ Chennai.
• Cloud stack for e-Governance projects (State Data centre
pilot@Kerala)
17. Integration Requirements
• The cloud resources hosting virtualized grid environment through the images
bundled with the grid middleware should be customized for execution of high
performance, parallel processing distributed grid applications without any
issues or hindrances.
• The grid environment should be capable of hosting cloud instances and
applications.
• The virtual grid hosted over cloud should be incorporated into the virtual
organization formation across cloud and grid or within the cloud.
18. Integration - Requirements
• Resource management across networking barriers
• Execution management
• Monitoring and control of jobs & instances
• Backup and disaster recovery, live migration
• Enhanced security
• Common user interface
19. SCOPE OF THE INTEGRATION
• Private cloud lacks with resources resulting in “Cloud burst”
• Integrates cloud middleware with grid middleware along with its schedulers
• Optimal utilization of the grid resources by deploying cloud appliances and
applications into the grid
• Return on investment to the grid service providers
• High performance grid jobs are executed over virtual environment on cloud
instance
• Dedicated resource for grid not needed.
20. Integrator with Gridway
• Interfacing Gridway with Integrator.
• If the job state is pending gridway must invoke integrator
• Additional no of nodes to be created in cloud resources
• Image & Security
• Eucalyptus VM Creation
• Network Management between grid and cloud
• Execution Management
• Data Management
• Gridway has DRMAA (Distributed Resource Management Application API) for
user interface
21. Integrator
Request to
Submits Job create VM
If Job state is
pending
Meta Scheduler (Gridway) Eucalyptus Cloud
Creating VM in
Selects Resource Cloud
& Submit
Computing Nodes Cloud Resource
22. Integrator with Eucalyptus
• Interfacing Eucalyptus with Integrator
• If Eucalyptus cloud can't create VM, it must invoke integrator
• Additional number of nodes to be created in grid resource
• Image & Network Management
• Security Management between grid and cloud
• VM Creation in grid resources
23. Integrator
Request
Request to
Create VM
Meta Scheduler (Gridway) Eucalyptus Cloud
Creating VM in
Creating VM in
Cloud Nodes
Grid Nodes
Computing Nodes Cloud Resource
25. INTEGRATION MODULE
• Hierarchy of both grid and cloud is almost the same
• Components of Integrator
• Execution Manager
• Resource Manager
• Network Manager
• Imaging component
• Security component
• Portal
26. GRID JOB EXECUTION IN CLOUD
• Grid jobs under execution when need additional resources from cloud, request
is sent by meta scheduler to integrator
• Resource management component in integrator approaches cloud controller
• Bundled grid image from imaging component deployed into cloud with
concurrence from the cloud controller
• Cloud controller through cluster and node controller deploys the image on n
number of virtual instances
• Local scheduler runs on newly formed grid cluster over cloud resources and is
directly controlled by the meta scheduler at the grid site.
• Virtual organization can be formed across the new grid cluster in cloud and
clusters functioning at the grid site
27. CLOUD APPLICATION IN GRID
• Cloud image bundled and residing in the cloud controller fetched by integrator
imaging component
• Deployed into grid through meta scheduler after concurrence from meta
scheduler
• Cloud controller along with integrator – resource manager raises a request
• Meta scheduler deploys image bundle and application is hosted on the
instances
• Grid instances contains node controller and all nodes controllers operating in
grid site is controlled by a Cluster controller deployed internally
• Cluster controller directly controlled by Cloud controller operating in the cloud
site.
• Integrator is responsible for Metering of Cloud instances, Elasticity, Backup and
disaster recovery, Elastic Ip addressing of instances deployed onto Grid.
28. Image Management
• Image Management is mainly used to manage the virtual images.
• Image Management module maintains the metadata as an xml DB which
contains all the image related information.
• Virtual Image is the image which has created with operating system and
applications.
29. Security Management
• It is mainly used to authenticate and authorize the grid and cloud users.
• The security management should have the intelligent for mapping both the
grid and cloud users to access the resource.
30. Network Management
• It is responsible for assigning the IP address, host name and managing the
network translation between grid and cloud resources
