Explain cloud federation stack.

-

 CLOUD FEDERATION STACK

The creation of a cloud federation needs research and development at several levels, including conceptual, logical, and operational, as well as infrastructure. The figure below depicts the obstacles encountered in creating and executing an organizational structure that coordinates cloud services from multiple administrative domains and allows them to function within the framework of a single unified service middleware. Each level of cloud federation brings unique issues and works at a different layer of the IT stack. It thus necessitates the application of various methodologies and technology. When the answers to the issues faced at each of these levels are combined, they provide a reference model for a cloud federation.



CONCEPTUAL LEVEL

The CONCEPTUAL LEVEL tackles the difficulties in presenting a cloud federation as a beneficial option for the usage of services leased by a single cloud provider. At this stage, it is critical to highlight the benefits of joining a federation for either service providers or service customers, as well as the additional opportunities that a federated environment brings in comparison to a single-provider solution. The conceptual level tackles the difficulties in presenting a cloud federation as a beneficial alternative for using services leased by a single cloud provider.

At this stage, it is critical to highlight the benefits of joining a federation for either service providers or service customers, as well as the additional opportunities that a federated environment brings in comparison to a single-provider solution. Elements of concern at this level are:

  • Motivations for cloud providers to join a federation
  • Motivations for service consumers to leverage a federation Advantages for providers in leasing their services to other providers
  • Obligations of providers once they have joined the federation Trust agreements between providers
  • Transparency versus consumers

The LOGICAL AND OPERATIONAL LEVEL

The LOGICAL AND OPERATIONAL LEVEL of a federated cloud identifies and resolves the issues by designing a framework that enables the aggregation of providers from various administrative data within the context of a single overlay infrastructure, which is the cloud federation. Policies and guides for interoperability are specified at this level. Furthermore, this is the layer at which decisions are th about how and when to lease a service to-or leverage a service from another provider The logical component sets the setting in which agreements among providers are established and services a negotiated, whereas the operational component describes and forms the federation's dynamic behavior a result of the single providers' choices. This is the stage at which MOCC is put into action and achieved 



 INFRASTRUCTURAL LEVEL

 INFRASTRUCTURAL LEVEL covers the technological problems involved in enabling diverse co-computing platforms to easily interoperate. It addresses the technological constraints that pre-independent cloud computing systems from belonging to distinct administrative domains. Th restrictions can be eliminated by using standardized protocols and interfaces. In other words, this level! for the federation is what the TCP/IP stack is for the Internet. The IaaS and PaaS layers of the C Computing Reference Model serve as the foundation for the infrastructure level. Interoperation interface services may also be implemented at the SaaS level, particularly for the realization of agreements and federated clouds.


Comments

Post a Comment

Popular posts from this blog

Pure Versus Partial EC

-
Image
Pure Versus Partial EC EC takes several forms depending on the degree of digitization (the transformation from physical to digital). Companies utilizing pure EC conduct all of their business online. Businesses utilizing partial EC conduct a portion of their business online and a portion of their business off-line OR,    Pure E-electronic commerce refers to a situation where a business transacts its business activities PURELY online. that is, the goods or services sold do not have any physical presence. take a business that sells software, for example, you just pay and download, or one that sells music files online. Partial E-Commerce on the other hand refers to a slightly opposite situation where a business has an online presence, but still has a physical location for the goods and services it sells. For example, Amazon, Walmart, and any other you can think of. you buy the goods online but receive them physically.                   ...
Read more

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)?

-
Image
a) A Snowflake Shema is shown in figure below: b) The specific OLAP operations to be performed: 1. Roll-up on course from course_id to department. 2. Roll-up on a student from student_id to university. 3. Dice on course, student with department ="CS" and university = "biguniversity" 4. Drill-down on a student from the university to student_name. c) N = 4 dimensions The cube will contain 54 = 625 cuboids.
Read more

Short note on E-Government Architecture

-
Image
1)  Presentation layer The presentation layer identifies and describes the system users, who require access to government information at different capacities, and the channels through which information can be accessed.  During system development, one is required to explicitly identify the government user, the system is intended to serve, and also the means through which this information is to be accessed so that the system can be tailored to meet these requirements. It manages the user’s interface with the system. If a pro- project is to be successful, different stakeholders need to be identified at the beginning, involved in the initial stages and kept involved throughout development and implementation. 2) E-government layer E-government public services utilize very specialized applications that are only available to certain agencies and not all agencies participating in the consortium. The main goal of the e-government layer is to achieve a government that;  does not as...
Read more