Explain Aneka Task Programming Model in detail.

 ANEKA TASK-BASED PROGRAMMING

Aneka supports different task-based programming via its Task Programming Model, which is the Aneka framework's core foundation for enabling the execution of bag-of-tasks applications. The Aneka abstraction is used to realize task programming. Task programming is accomplished through the abstraction of the Aneka.Tasks.ITask. Using this abstraction as a foundation, support for legacy application execution, parameter sweep apps, and workflows have been implemented into the framework.

Aneka Task Programming Model

  • The Task Programming Model provides an easy-to-use framework for rapidly constructing distributed applications on top of Aneka. It provides a minimal set of APIs, most of which are centered on the Aneka.Tasks.ITask interface. Interface, together with the services facilitates task execution in the middleware.
  • Distributed applications are created as ITask instances, and the combined execution of these instances forms a running application. The tasks and numerous required dependencies, such as data files and libraries, are gathered and handled by the Aneka Application class, which supports task execution. The client-side view of a task-based application is made up of two additional components: Aneka Task and TaskManager. AnekaTask is the runtime wrapper that Aneka uses to represent a task within the middleware; and the TaskManager is the underlying component that communicates with Aneka, submits tasks, monitors their execution, and gathers results.


  • Four services in the middleware coordinate their actions to perform task-based applications.MembershipCatalogue, TaskScheduler, ExecutionService, and StorageService are examples.
  • MembershipCatalogue is the cloud's primary access point, and it serves as a service directory for locating the TaskScheduler service, which is in charge of controlling the execution of task-based applications. Its primary role is to assign task instances to resources that use the ExecutionService for task execution and task state monitoring. If the application needs data transfer support in the form of data files, input files, or output files, an accessible StorageService will be used as a staging facility.

Developing applications with the task model:-

  1. Defining classes implementing the ITask interface 
  2. Creating a properly configured AnekaApplication instance
  3. Creating ITask instances and wrapping them into Aneka Task instances 
  4. Executing the application and waiting for its completion

  • The Aneka Tasks namespace contains almost all of the client-side functionalities required for developing task-based applications. The ITask interface, which exposes only one method: Execute, is the most fundamental component for building tasks. The method is invoked to have the job executed on the remote node.

ITask interface

namespace Aneka.Tasks
{
/// <summary> ///Interface ITask. Defines the interface for implementing a task.
///</summary>
public interface ITask
{
/// <summary>
///Executes the sine function.
///</summary> public void Execute():
}
}

Comments

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

Suppose that a data warehouse consists of the four dimensions; date, spectator, location, and game, and the two measures, count and charge, where charge is the fee that a spectator pays when watching a game on a given date. Spectators may be students, adults, or seniors, with each category having its own charge rate. a) Draw a star schema diagram for the data b) Starting with the base cuboid [date; spectator; location; game], what specific OLAP operations should perform in order to list the total charge paid by student spectators at GM Place in 2004?

Discuss classification or taxonomy of virtualization at different levels.