Skip to main content

CometCloud is an autonomic computing engine

 Overview

CometCloud is an autonomic computing engine for Cloud and Grid environments. It is based on the Comet decentralized coordination substrate, and supports highly heterogeneous and dynamic cloud/Grid infrastructures, integration of public/private clouds and autonomic cloudbursts. CometCloud provides a shared coordination space over the Chord overlay network and various types of programming paradigms such as Master/Worker, Workflow, and MapReduce/Hadoop.

CometCloud supports autonomic cloudbursts and autonomic cloud-bridging on a virtual cloud which integrates local computational environments and public cloud services on-the-fly. Also it supports real-world scientific and engineering applications.

What is CometCloud capable of?

  • Support core programming paradigms for real-world data and compute intensive applications
  • Enables autonomic cloudbursts and cloud-bridging and on-demand scale-out and scale-in, driven by dynamic policies, economic model, QoS constraints, etc.
  • Programming system support deployment of native (Java as well as non-Java) applications without any change.
  • Current deployments include a virtual cloud integrating Amazon EC2, Eucalyptus, local clusters, and TeraGrid.
  • Incorporates mechanisms for fault-tolerance to handle node and communication failures and recovery.

 

What are CometCloud Features?

  • Pull-based task consumption: workers pull tasks from the Comet space whenever they are available
  • Policy-based autonomic cloudbursts: CometCloud supports on-demand scale-out and scale-in by policy and economic model.
  • Cloud-bridging: CometCloud provides a cloud-bridging over a virtual cloud which integrates datacenter, clouds such as Amazon EC2 and Eucalyptus, and Grids such as Teragrid.
  • Support for multi-core processors: users can run multiple workers on a node and utilized multiple cores.
  • Support MapReduce with naïve disk writing: instead of using Hadoop file system, CometCloud uses the Comet space for storing data to support MapReduce and writes data into the disk if available memory amount goes below a threshold.
  • Master throttling: CometCloud can control the rate of task generation of masters. If the rate is high, then more tasks keep in the space.
  • Multiple masters: multiple masters can generate tasks and insert them into the same Comet space to collaborate.
  • Task update: if a task with the same task id is inserted, the existing task is updated.
  • Garbage collection: if tasks remain in the space for some time without being consumed, then they are cleared.
  • Distributed task generation by workers: even workers can generate tasks and insert them into the space. Because every task should have a unique task id, CometCloud provides a way to provide a globally unique id to distributed workers.
  • Fault-tolerance by replicating task space: each node replicates the preceding node’s local space, and it merges the replicated space when its preceding node fails.
Labels:

Comments

Post a Comment

Popular posts from this blog

2.1 VIRTUAL MACHINES PROVISIONING AND MANAGEABILITY

In this section, we will have an overview on the typical life cycle of VM and its major possible states of operation, which make the management and automation of VMs in virtual and cloud environments easier than in traditional computing environments As shown in Figure above, the cycle starts by a request delivered to the IT department, stating the requirement for creating a new server for a particular service.  IT administration to start seeing the servers’ resource pool, matching these resources with the requirements, and starting the provision of the needed virtual machine.  Once provisioned machine started, it is ready to provide the required service according to an SLA, or a time period after which the virtual is being released.
Post a Comment
Read more

2.2 VIRTUAL MACHINE MIGRATION SERVICES

Migration service, in the context of virtual machines, is the process of moving a virtual machine from one host server or storage location to another; there are different techniques of VM migration, hot/life migration, cold/regular migration, and live storage migration of a virtual machine. In process of migration, all key machines’ components, such as CPU, storage disks, networking, and memory, are completely virtualized, thereby facilitating the entire state of a virtual machine to be captured by a set of easily moved data files. 2.2.1. Migrations Techniques Live Migration and High Availability Live migration (which is also called hot or real-time migration) can be defined as the movement of a virtual machine from one physical host to another while being powered on.  Live migration process takes place without any noticeable effect from the end user’s point of view (a matter of milliseconds).  One of the most significant advantages of live migration is the fact that it facili...
Post a Comment
Read more

Open SaaS and SOA

A considerable amount of SaaS software is based on open source software.  When open source software is used in a SaaS,  it referred to as Open SaaS.  The advantages of using open source software are that systems are much cheaper to deploy because you don’t have to purchase the operating system or software, there is less vendor lock-in, and applications are more portable.  The popularity of open source software, from Linux to APACHE, MySQL, and Perl (the LAMP platform) on the Internet, and the number of people who are trained in open source software make Open SaaS an attractive proposition.  The impact of Open SaaS will likely translate into better profitability for the companies that deploy open source software in the cloud, resulting in lower development costs and more robust solutions. SOA (Service-Oriented Architecture): SOA is an architectural approach for designing and developing software systems that are composed of loosely coupled services.  In an SO...
Post a Comment
Read more