YOU MAY DOWNLOAD THESE IN A PRESENTATION FORMAT
DON’T WORRY MORE OF SUCH THING WILL COME SOON
In the simplest terms, the federation is a means to enable interaction or collaboration of some sort. Federation is an overloaded term with different meanings to different stakeholders.
Abstract:
In the simplest terms, the federation is a means to enable interaction or collaboration of some sort. Federation is an overloaded term with different meanings to different stakeholders. What does it entail in this context and with regard to the cloud computing model? What is the scope of capabilities it can or must support? Of course, federation can have multiple definitions in different use cases, in different application domains, and at different levels in the system stack. In some situations, federation is used to mean identity federation. This means being able to ingest identity credentials from external identity providers. This can be used to provide single sign-on (SSO) – a very useful capability.
The above diagram describes the generic federated cloud. We will look into this in upcoming slides. They are too similar to the generic one but they are more useful as they are already a part of some clouds.
Multi-Cloud or Multi-tenancy in cloud:
The term multi-cloud has been used when cloud provider capabilities are “integrated” by defining a separate interface layer for each “back-end” provider whereby a single, common interface can be presented to the user. This approach achieves cloud interoperability by using the rich feature set of the cloud capabilities, but integrates them very shallowly, if at all. Another approach is to use a “lowest common denominator” approach. Here, some minimal feature set across all providers is used, e.g. VMs, and the “integrated” infrastructure system is built on top using, for example, Docker, Kubernetes, OpenStack, or various DevOps solutions. This approach provides portability.
Bursting (hybrid) architecture. As Figure (a) shows,
The cloud bursting or hybrid architecture combines the existing on-premise infrastructure (usually a private cloud) with remote resources from one or more public clouds to provide extra capacity to satisfy peak demand periods. Because the local cloud OS has no advanced control over the virtual resources deployed in external clouds beyond the basic operations the providers allow, this architecture is loosely coupled. Most existing open cloud managers support the hybrid cloud architecture, which has been explored in various research efforts and is used in infrastructures such as StratusLab (http://stratuslab.eu).
Aggregate Architecture:
aggregation consists of two or more partner clouds that interoperate to aggregate their resources and provide users with a larger virtual infrastructure. This architecture is usually partially coupled, since partners could be provided with some kind of advanced control over remote resources, depending on the terms and conditions of contracts with other partners.
Multi tier Architecture :
aggregation consists of two or more partner clouds that interoperate to aggregate their resources and provide users with a larger virtual infrastructure. This architecture is usually partially coupled, since partners could be provided with some kind of advanced control over remote resources, depending on the terms and conditions of contracts with other partners.
Cloud OS:
a cloud OS’s role is to efficiently manage datacenter resources to deliver a flexible, secure, and isolated multitenant execution environment for user services that abstracts the underlying physical infrastructure and offers different interfaces and APIs for interacting with the cloud. While local users and administrators can interact with the cloud using local interfaces and administrative tools that offer rich functionality for managing, controlling, and monitoring the virtual and physical infrastructure, remote cloud users employ public cloud interfaces that usually provide more limited functionality. OpenNebula (http://opennebula.org) is an example of an open cloud OS platform focused on datacenter virtualization that fits with the architecture Virtual machine manager
These are the other component of multi cloud in an IaaS environment
Microservice as the basis of federating multiple cloud datacenters as part of a cohesive federation,where datacenter providers can meet the performance requirements of client applications through optimal placement and migration of microservices across datacenters.
Create vcn
PaaS Multi-Cloud and Its Kernel:
This kernel draws inspiration from our FRASCATI,platform for reconfigurable SOA and from the domain of Software Product Line (SPL) design. An SPL can be defined as ”a set of software-intensive systems that share a common, managed set of features and that are developed from a common set of core assets in a prescribed way” . A Feature Model is used to compactly define all features in an SPL and their valid combinations. Another PaaS would be kubernetes based oracle kubernetes engine. However the above sections describe a conceptual kernel design for PaaS Multi cloud but PaaS multi cloud holds some basic components we will discuss them. multi-PaaS cloud (cloud4SOA):In order to implement a multi-PaaS application management solution the two main features required are the PaaS management (to manage applications at different PaaS) and the Cloud monitoring (to monitor the applications across PaaS). Based on the results of table 2.2 only Cloud4SOA satisfies these two requirements.
Teleportation of VMs:
It’s a most recent development happening in vmware lab and they put this research on live as they are able to teleport all the vms during migration. We will take a quick look at this and we will finish up with a quick recap of the priorior tech jargon which we must consider. They developed teleportation for migration purposes.
within multi cloud GPU virtualizations comes with a different way.Modern developer and data scientist may require to use certain GPUs as virtualized.so VCF (vmware cloud foundation) offers GPU virtualization as a service (SaaS) in some specific manner. You need to use GPU and GPU Virtualized cluster as a part of SaaS within Multi cloud which you need to get through brokers to other providers. Call to Action:Audit how GPUs are used in your organization’s infrastructure! Calculate the costs and utilization of the existing GPUs in the environment;What are the use cases for GPUs across different groups?;Propose an internal virtualized GPUaaS infrastructure by combining all resources for better utilization and cost optimization.
High Speed Networking with PVRDMA & RoCE:
Remote Direct Memory Access (RDMA) provides direct memory access from the memory between hosts bypassing the Operating System and CPU. This can boost network and host performance with reduced latency & CPU load while providing higher bandwidth. RDMA compares favorably to TCP/IP, which adds latency and consumes significant CPU and memory resources. Mellanox conducted Benchmarks that demonstrated NVIDIA® vComputeServer or virtualized GPUs achieve two times better efficiency by using VMware’s paravirtualized RDMA (PVRDMA) technology than when using traditional networking protocols.vSphere Bitfusion: vSphere Bitfusion extends the power of VMware vSphere’s virtualization technology to GPUs. vSphere Bitfusion helps enterprises disaggregate the GPU compute and dynamically attach GPUs anywhere in the datacenter just like attaching storage. Bitfusion enables use of any arbitrary fractions of GPUs. Support more users in test and development phase. vSphere Bitfusion supports the CUDA API and demonstrates virtualization and remote attach for all hardware. GPUs are attached based on CUDA calls at run-time, maximizing utilization of GPU servers anywhere in the network.
Reviews:
GPU VIrtualization in Multi cloud:vSphere Bitfusion extends the power of VMware vSphere virtualization technology to GPUs. vSphere Bitfusion helps enterprises disaggregate the GPU compute and dynamically attach GPUs anywhere in the datacenter just like attaching storage. Bitfusion enables use of any arbitrary fractions of GPUs.
There are certain aspects of research still pretty much possible where instances’ lifespan is quite lesser than usual or providers willing to reuse the resources for other purposes except cloud’s end users after a certain time.
In a nutshell the microservice architecture is quite convincing and adopted by all other cloud providers quite decently: kubernetes, swarm, DevOps, modal cloud etc.
After researching previous works there are certain concerns which still exist; those are security in multi-tenancy and broker designing with respect to multi-tenancy or multi cloud. From a practical point of view task management is still challenging.
References:
DON’T WORRY MORE OF SUCH THING WILL COME SOON
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |