The Open Virtualization Format (OVF) standard provides the industry with a standard packaging format for software solutions based on virtual systems, solving critical business needs for software vendors and cloud computing service providers.
OVF has been developed by the DMTF (see also the DMTF OVF Standards Watch link).
ISO/IEC 17788 provides an overview of cloud computing along with a set of terms and definitions. It is a terminology foundation for cloud computing standards.
ISO/IEC 17788 is applicable to all types of organizations (e.g., commercial enterprises, government agencies, not-for-profit organizations).
ISO/IEC 17789 specifies the cloud computing reference architecture (CCRA). The reference architecture includes the cloud computing roles, cloud computing activities, and the cloud computing functional components and their relationships.
ISO/IEC 17963 describes a Web services protocol based on SOAP for use in management‑specific domains. These domains include the management of entities such as PCs, servers, devices, Web services and other applications manageable entities. Services can expose only a WS-Management interface or compose the WS-Management service interface with some of the many other Web service specifications.
A crucial application for these services is in the area of systems management. To promote interoperability between management applications and managed resources, ISO/IEC PAS 17963 identifies a core set of Web service specifications and usage requirements that expose a common set of operations central to all systems management. This includes the ability to do the following:
a) get, put (update), create, and delete individual resource instances, such as settings and dynamic values;
b) enumerate the contents of containers and collections, such as large tables and logs;
c) subscribe to events emitted by managed resources;
d) execute specific management methods with strongly typed input and output parameters.
In each of these areas of scope, ISO/IEC 17963 defines minimal implementation requirements for conformant Web service implementations. An implementation is free to extend beyond this set of operations, and to choose not to support one or more of the preceding areas of functionality if that functionality is not appropriate to the target device or system.
ISO/IEC 17963 intends to meet the following requirements:
a) constrain Web services protocols and formats so that Web services can be implemented with a small footprint in both hardware and software management services;
b) define minimum requirements for compliance without constraining richer implementations;
c) ensure backward compatibility and interoperability with WS-Management version 1.0;
d) ensure composability with other Web services specifications.
This standard has been developed by the DMTF (see also the DMTF WS-Management Standards Watch link).
This document:
- Describes a framework for the structured expression of data-related policies and practices in the cloud computing environment, based on the data taxonomy in ISO/IEC 19944:2017;
- provides guidelines on application of the taxonomy for handling of data based on data subcategory and classification;
- covers expression of data-related policies and practices including, but not limited to data geolocation, cross border flow of data, data access and data portability, data use, data management, and data governance;
- describes how the framework can be used in codes of conduct for practices regarding data at rest and in transit, including cross border transfer of data, as well as remote access to data;
- provides use cases for data handling challenges, i.e. control, access and location of data according to ISO/IEC 19944:2017 data categories.
This document is applicable primarily to cloud service providers, cloud service customers and cloud service users, but also to any person or organization involved in legal, policy, technical or other implications of taxonomy based data management in cloud services.
The Trusted Cloud Initiative helps cloud providers develop industry-recommended, secure and interoperable identity, access and compliance management configurations, and practices. The Trusted Cloud Initiative will develop reference models and education in a vendor-neutral manner, inclusive of all CSA members and affiliates who wish to participate. The Trusted Cloud Initiative Reference Architecture is both a methodology and a set of tools that enable security architects, enterprise architects and risk management professionals to leverage a common set of solutions that fulfill their common needs to be able to assess where their internal IT and their cloud providers are in terms of security capabilities and to plan a roadmap to meet the security needs of their business.
This document presents the NIST Federated Cloud Reference Architecture model. This actor/role based model used the guiding principles of the NIST Cloud Computing Reference Architecture to develop an 11 component model which are described individually and how they function as an ensemble. There are many possible deployments and governance options which lend themselves to create a suite of federation options from simple to complex. The basics of cloud federation can be described through the interactions of the actors in a layered three planes representation of trust, security, and resource sharing and usage. A discussion on possible future standards and use cases are also described in great detail.
Regional cloud providers that operate data centers and associated wide-area networking across their region are well positioned to cooperatively build a global cloud infrastructure with other regional cloud providers, and thus, become a valuable party for Content and Application Providers (CPs and APs). We call the formalization of such cooperation a federated cloud. In a federated cloud, application and/or content requests placed to a cloud provider can be served locally -- e.g., by a supporting cloud provider, even when this supporting cloud provider only has an indirect relationship to the AP or CP by way of a primary cloud provider. In this case, a primary cloud provider is defined as the cloud provider with which an AP or CP has a direct contractual arrangement for cloud services. A federated cloud member simultaneously acts as a primary cloud provider and a supporting cloud provider as defined by their relationship with different APs and CPs.
In a federated cloud, part or all of each individual provider's compute, storage, and networking resources become part of a federated pool of cloud resources. Management systems of these individual (regional) cloud providers are linked to facilitate end-to-end cloud services capability. By definition, a federated cloud includes a clearing house to settle expenditures and revenues of the end-to-end cloud services based on agreed methods, interfaces, and procedures for settlement.
The concept of a Federated Cloud comprised of interconnected Service Providers (SP) was introduced in ATIS Standard ATIS-0200003, CDN Interconnection Use Case Specifications and High Level Requirements [https://global.ihs.com/doc_detail.cfm?&csf=ASA&input_doc_number=%20&inpu.... This initial standard described the role of the SPs in the cloud as distributors of content from Content Providers (CP) to End Users (EU). Thus, SPs serve as Content Distribution Network (CDN) Providers. The set of content delivery Life Cycle interactions between two CDN Providers is defined in ATIS-0200003. The method for content distribution in ATIS-0200003 was limited to Unicast Cache-based distribution.
Under certain conditions depending on network configurations and type of content, it may be advantageous to distribute content via Multicast methods. From a network perspective, Multicast is scalable and results in significant savings in efficiencies and capacity utilization.
The purpose of this ATIS Standard is to introduce Multicast-based content distribution. This standard provides the following:
Overview of the Multicast delivery mechanism
Set of content types that are suitable for delivery via Multicast methods
Description of various Multicast methods that can be deployed to interconnect two CDN Providers and distribute content.
The scope of this Standard is limited to use cases and requirements to support the interactions between two CDN Providers for content distribution via Multicast. The Use Cases describe:
Generic interactions supporting Life Cycle Multicast use between two CDN Providers.
Specific Multicast configurations/scenarios that can be deployed for interconnection and content distribution.
Multicast related specifics to support Billing, Provisioning, Reporting, and other network functions will be covered in future ATIS documents. Multicast-based content delivery to mobility-based End User devices is for further study.
The ATIS Cloud Services Forum is examining a number of services that establish the foundation for development, operations, deployment, and management of cloud-based services. These include content delivery, telepresence, and virtual desktop. Video services, including the already-present one-way and growing two-way communications, will be a substantial catalyst for additional growth and expansion of the Internet. Telepresence services provide a business model and architectural model that are foundational to cloud services, and provide important elements of the Cloud Services Data Model for Cloud Service Enablers. This specification focuses on telepresence services, recognizing that telepresence services are an integral part of a broader unified communications solution set.
There are many aspects of the telepresence service. This is an evolving document establishing a foundation for continuing work efforts. The specification explores a provider-agnostic and product-agnostic implementation, and will consider two primary aspects of the telepresence service that are detailed here by the examination of use cases deployed today and those resulting in the application of "the cloud" and other aspects of business and technology architecture guiding service evolution in the future. First, a description of the telepresence service is provided. Second, a more detailed description of the two key aspects of the telepresence service is provided. Topics 2f and 2g detail aspects of telepresence interconnectivity which will be addressed in a future specification.
Virtual desktop services enable enterprise IT organizations to logically centralize desktop resources so as to reduce desktop management costs and support any-device, any-network access to desktops by end-users. The emergence of Virtual Desktop Infrastructure as a service additionally allows enterprise IT organizations to take advantage of cloud resources instead of building their own infrastructures. As a result, enterprises can further reduce IT costs.
This document describes the virtual desktop (VD) requirements for enterprise services and specifies a federation framework for deploying VD services across multiple networks and administrative domains. In particular, the framework allows cloud service providers to host VD services for enterprises and at the same time maintain seamless network connectivity to enterprise resources. For the sake of end-user experience, it is essential that VD sessions can be transparently moved between data centers or between service providers without compromising security and isolation. Such transparent migration of VD session poses significant requirements on the underlying networks, which are also addressed by this document.
With the emergence of Cloud Services spanning one or many cloud infrastructures managed by various providers, it is imperative that a checklist be developed that provides cloud services lifecycle guidance/requirements for service providers/developers as they integrate these lifecycle functions.
The goal driven checklist is to be developed with the purpose to facilitate the following six lifecycle functions from a cloud service provider. These lifecycle functions can be aggregated in the three categories of build, capture, and modify to facilitate a simpler description of the goals.
Assessment and acceptance (i.e., build) of services onto the cloud platform/infrastructure.
Ongoing audit (i.e., capture) of services on the cloud platform/infrastructure.
Augmentation, abridging, and annulment (i.e., modify) of services within the cloud platform/infrastructure.
The goal of the checklist is to realize greater efficiencies through formalization and automation of integrations between cloud service providers and their corollary actors during the cloud services lifecycle. While the focus in this document is on the cloud services lifecycle, note that the unique goal oriented approach and related paradigms described herein could also be applied elsewhere.
