|wiki1479: Home page|
Welcome to the SCRM Working Group Wiki!
Created within Open Grid Forum's working group known as the Standards Development Organization Collaboration on Networked Resources Management (SCRM-WG), this is a repository of relevant standards from work by leading industry bodies including the Open Grid Forum (OGF), the Distributed Management Task Force (DMTF), the Organization for the Advancement of Structured Information Standards (OASIS), the Storage Networking Industry Association (SNIA), the Tele Management Forum (TMF), the European Telecommunications Standards Institute (ETSI), the Internet Engineering Task Force (IETF), the International Telecommunication Union - Telecommunication Standardization Sector (ITU-T), and the World Wide Web Consortium (W3C).
There is a Landscape that describes the terms and concepts used by these standards.
Also available is a catalog of various events relevant to the SDOs and other industry bodies.
Click here for how to contribute this wiki.
CIM Infrastructure Specification v2.5
The DMTF Common Information Model (CIM) Infrastructure is an approach to the management of systems and networks that applies the basic structuring and conceptualization techniques of the object-oriented paradigm. The approach uses a uniform modeling formalism that together with the basic repertoire of object-oriented constructs supports the cooperative development of an object-oriented schema across multiple organizations. This document describes an object-oriented meta model based on the Unified Modeling Language (UML). This model includes expressions for common elements that must be clearly presented to management applications (for example, object classes, properties, methods and associations).
The Common Information Model (CIM) is conceptual information model for describing computing and business entities in internet, enterprise and service provider environments. It provides a consistent definition and structure of data , using object oriented techniques. The CIM includes expressions for common elements that must be clearly presented to management applications like object classes, properties, methods and associations to name a few. CIM uses a set of terminology specific to the model and the principles of object oriented programming. The standard language used to define elements of CIM is Managed Object Format (MOF).
DSP0214 Server Management Command Line Protocol Specification (SM CLP) V1.0.0
The principal goal of this specification is to define a light-weight, human-oriented command line protocol which is also suitable for scripting environments. This includes a direct mapping to a subset of the CIM Schema. The command line protocol will specify the syntax and semantics used to allow the manipulation of the Managed Elements and Associations within servers, as collections or individually.
DSP0215 Server Management Managed Element Addressing Specification (SM ME) V1.0.0
This document describes the Server Management (SM) Managed Element (ME) Addressing standard. SM ME Addressing provides an easy user friendly way to address CIM objects (classes and instances). This specification may be used to define valid targets for SM CLP commands. It is intended that this specification be usable by other Protocols.
DSP0226 Web Services for Management (WS Management) V1.0.0
This specification describes a general SOAP-based protocol for managing systems such as PCs, servers, devices, Web services and other applications, and other manageable entities.
DSP0230 WS-CIM Mapping Specification V1.0.0c
This specification provides the normative rules and recommendations that describe the structure of the XML Schema, WSDL fragments and metadata fragments corresponding to the elements of CIM models, and the representation of CIM instances as XML instance documents.
DSP0231 CIM Simplified Policy Language (CIM-SPL) V1.0.0a
This specification provides a means for specifying if condition-then-action style policy rules to manage computing resources using constructs defined by CIM.
DSP0243 Open Virtualization Format (OVF) V1.0.0
This specification describes an open, secure, portable, efficient and extensible format for the packaging and distribution of software to be run in virtual machines.
DSP0252 Configuration Management Database Federation (CMDBf) V1.0.0
This specification facilitates the sharing of information between configuration management databases (CMDBs) and other management data repositories (MDRs).
Open Grid Services Architecture version 1.0 v1.0
The document focuses on requirements and the scope of important capabilities required to support Grid systems and applications in both e-science and e-business. The capabilities described are Execution Management, Data, Resource Management, Security, Self-Management, and Information. The description of the capabilities is at a high-level and includes, to some extent, the interrelationships between the capabilities.
The OGSA WSRF Basic Profile 1.0 is an OGSA Recommended Profile as Proposed. This profile describes uses of widely accepted specifications that have been found to enable interoperability. The specifications considered in this profile are specifically those associated with the addressing, modeling, and management of state: WS-Addressing, WS-ResourceProperties, WS-ResourceLifetime, WS-BaseNotification, and WS-BaseFaults.
This document provides a high level overview of the CDDLM space by describing requirements, analyzing use cases, and by providing an overview of the related work within OGF, other standard bodies, as well as in industry and academia in general. The document sets the stage for the follow-up documents that will present in more detail the language, component model, and basic CDDLM services.
The SmartFrog Language spec describes a language primarily intended for configuration description and deployment. It is declarative, i.e. it supports attribute value pairs. Furthermore, it supports inheritance, references (including lazy), parameterization, predicates and schemas. It has the same functionality as CDL (see next paragraph), except that it is not XML-based. SmartFrog language predates CDL and it was used as a model when creating CDL. The two languages will be compatible. CDL is primarily intended for machines, SmartFrog for humans.
The CDDLM Configuration Description Language (CDL) is an XML-based language for declarative description of system configuration that consists of components (deployment objects) defined in the CDDLM Component Model. The language provides ways to describe properties (names, values, and types) of components including value references so that data can be assigned dynamically with preserving specified data dependencies. A system is described as a hierarchical structure of components. The language also provides prototype-based template functionality (i.e., prototype references) so that the user can describe a system by referring to component descriptions given by component providers.
The CDDLM Component Model outlines the requirements for creating a deployment object responsible for the lifecycle of a deployed resource. Each deployment object is defined using the CDL language and mapped to its implementation. The deployment object provides a WSResourceFramework (WSRF) compliant "Component Endpoint" for lifecycle operations on the managed resource. The model also defines the rules for managing the interaction of objects with the CDDLM Deployment API in order to provide an aggregate, controllable lifecycle and the operations which enable this process.
The deployment API is the WSRF-based SOAP API for deploying applications to one or more target computers. Every set of computers to which systems can be deployed hosts one or more "Portal Endpoints", WSRF resources which provide a means to create new "System Endpoints". A System Endpoint represents a deployed system. The caller can upload files to it, then submit a deployment descriptor for deployment. A System Endpoint is effectively a component in terms of the Component Model specification it implements the properties and operations defined in that document. It also adds the ability to resolve references within the deployed system, enabling remote callers to examine the state of components with it.
In order to install and operate complex systems such as n-tier systems more efficiently and automatically, it is necessary to specify and manage, as a unit, a diverse set of application related information. The Application Contents Service (ACS) provides central management of such application information. The Application Contents Service specification will focus on two main topics: a) Application Repository Interface (ARI), specifying repository service and its interface to Application Contents; and b) Application Archive Format (AAF), specifying archive format to register a set of Application Contents to the ACS as a unit. The Application Contents include application binaries and related information; e.g. program binaries, configuration data, procedure descriptions for lifecycle management, requirements descriptions for the hardware and underlying middleware, policy rules, and anything needed to create a task on grid systems.
This document describes the Job Submission Interface Model. It is based on the "job" schema in DMTF's Common Information Model (CIM), version 2.8. It includes a UML diagram of the classes associated with job submission, the managed object format (MOF) for those classes, and an XML representation of the UML.
This document describes Web Services Agreement Specification (WS-Agreement), an XML language for specifying an agreement between a resource/service provider and a consumer, and a protocol for creation of an agreement using agreement templates. The specification consists of three parts to be used in a composable manner: a schema for specifying an agreement, a schema for specifying an agreement template, and a set of port types and operations for managing agreement life-cycle, including creation, termination, and monitoring of agreement states.
This document follows the recommendations of “OGSA Profile Definition Version 1.0” and describes an extension to the WS-Addressing specification to include extensibility elements for abstract names and for resolvers, as well as port types for the WS-Naming resolution services.
SMI - Structure of Management Information Version 2 (Internet Standard: STD 58)
The SMIv2 is the Data Modeling language used for writing MIB module specifications. The SMIv2 consists of the following 3 RFCs which together comprise Internet Standard STD 58.
RFC 2578 - Structure of Management Information Version 2 (SMIv2).
Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using an adapted subset of OSI's Abstract Syntax Notation One, ASN.1 (1988). It is the purpose of this document, the Structure of Management Information (SMI), to define that adapted subset, and to assign a set of associated administrative values.
RFC 2579 - Textual Conventions for SMIv2.
When designing a MIB module, it is often useful to define new types similar to those defined in the SMI. In comparison to a type defined in the SMI, each of these new types has a different name, a similar syntax, but a more precise semantics. These newly defined types are termed textual conventions, and are used for the convenience of humans reading the MIB module. It is the purpose of this document to define the initial set of textual conventions available to all MIB modules.
RFC 2580 - Conformance Statements for SMIv2.
It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes.
SNMP - Simple Network Management Protocol Version 3 (Internet Standard: STD 62)
The SNMP version 3 specifies the SNMPv3 framework and consists of the following set of RFCs which together compise Internet Standard STD 62.
RFC 3411 - An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks.
This document describes an architecture for describing Simple Network Management Protocol (SNMP) Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. The major portions of the architecture are an SNMP engine containing a Message Processing Subsystem, a Security Subsystem and an Access Control Subsystem, and possibly multiple SNMP applications which provide specific functional processing of management data.
RFC 3412 - Message Processing and Dispatching for the Simple Network Management Protocol (SNMP).
This document describes the Message Processing and Dispatching for Simple Network Management Protocol (SNMP) messages within the SNMP architecture. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model.
RFC 3413 - Simple Network Management Protocol (SNMP) Applications.
This document describes five types of Simple Network Management Protocol (SNMP) applications which make use of an SNMP engine as described in STD 62, RFC 3411. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders.
RFC 3414 - User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3).
This document describes the User-based Security Model (USM) for Simple Network Management Protocol (SNMP) version 3 for use in the SNMP architecture. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a Management Information Base (MIB) for remotely monitoring/managing the configuration parameters for this Security Model.
RFC 3415 - View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP).
This document describes the View-based Access Control Model (VACM) for use in the Simple Network Management Protocol (SNMP) architecture. It defines the Elements of Procedure for controlling access to management information. This document also includes a Management Information Base (MIB) for remotely managing the configuration parameters for the View-based Access Control Model.
RFC 3416 - Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP).
This document defines version 2 of the protocol operations for the Simple Network Management Protocol (SNMP). It defines the syntax and elements of procedure for sending, receiving, and processing SNMP PDUs.
RFC 3417 - Transport Mappings for the Simple Network Management Protocol (SNMP).
This document defines the transport of Simple Network Management Protocol (SNMP) messages over various protocols.
RFC 3418 - Management Information Base (MIB) for the Simple Network Management Protocol (SNMP).
This document defines managed objects which describe the behavior of a Simple Network Management Protocol (SNMP) entity.
SNMP - Additional documents in the SNMP space.
The first document (RFC 3410) is an informational RFC that explains the set of SNMP documents that describe versions 1, 2 and 3 of SNMP. It also contains applicability statements.
Two additional RFCs (3419 as a Proposed Standard and 3430 as an Experimental RFC) complement the SNMP and SMI specifications.
RFC 3584 (as a Best Current Practice document: BCP 74) describes the co-existence of SNMP versions 1, 2 and 3.
Further we list RFC 3444 and RFC 3535 (Informational RFCs) which provide extra information.
RFC 3410 - Introduction and Applicability Statements for Internet-Standard Management Framework.
The purpose of this document is to provide an overview of the third version of the Internet-Standard Management Framework, termed the SNMP version 3 Framework (SNMPv3). This Framework is derived from and builds upon both the original Internet-Standard Management Framework (SNMPv1) and the second Internet-Standard Management Framework (SNMPv2).
RFC 3419 - Textual Conventions for Transport Addresses.
This document introduces a Management Information Base (MIB) module that defines textual conventions to represent commonly used transport-layer addressing information. The definitions are compatible with the concept of TAddress/TDomain pairs introduced by the Structure of Management Information version 2 (SMIv2) and support the Internet transport protocols over IPv4 and IPv6.
RFC 3430 - Simple Network Management Protocol Over Transmission Control Protocol Transport Mapping.
This memo defines a transport mapping for using the Simple Network Management Protocol (SNMP) over TCP. The transport mapping can be used with any version of SNMP.
RFC 3584 - Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework.
The purpose of this document is to describe coexistence between version 3 of the Internet-standard Network Management Framework, (SNMPv3), version 2 of the Internet-standard Network Management Framework (SNMPv2), and the original Internet-standard Network Management Framework (SNMPv1). This document also describes how to convert MIB modules from SMIv1 format to SMIv2 format.
RFC 3444 - On the Difference between Information Models and Data Models.
There has been ongoing confusion about the differences between Information Models and Data Models for defining managed objects in network management. This document explains the differences between these terms by analyzing how existing network management model specifications (from the IETF and other bodies such as the International Telecommunication Union (ITU) or the Distributed Management Task Force (DMTF)) fit into the universe of Information Models and Data Models.
This memo documents the main results of the 8th workshop of the Network Management Research Group (NMRG) of the Internet Research Task Force (IRTF) hosted by the University of Texas at Austin.
RFC 3535 - Overview of the 2002 IAB Network Management Workshop.
This document provides an overview of a workshop held by the Internet Architecture Board (IAB) on Network Management. The workshop was hosted by CNRI in Reston, VA, USA on June 4 thru June 6, 2002. The goal of the workshop was to continue the important dialog started between network operators and protocol developers, and to guide the IETFs focus on future work regarding network management. This report summarizes the discussions and lists the conclusions and recommendations to the Internet Engineering Task Force (IETF) community.
NETCONF - Network Configuration (approved as Proposed Standard)The Netconf documents listed here are now IETF Proposed Standards.
The protocol requires that the mapping over SSH is mandatory to implement while the mapping over BEEP and SOAP are optional.
RFC 4741 - NETCONF Configuration Protocol
The NETCONF configuration protocol defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML) based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized on top of a simple Remote Procedure Call (RPC) layer.
RFC 4742 Using the NETCONF Configuration Protocol over Secure Shell (SSH)
This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem.
RFC 4744 - Using the NETCONF Protocol over Blocks Extensible Exchange Protocol (BEEP)
This document specifies an application protocol mapping for the NETCONF protocol over the Blocks Extensible Exchange Protocol (BEEP).
RFC 4743 - Using the Network Configuration Protocol (NETCONF) Over the Simple Object Access Protocol (SOAP)
The Network Configuration Protocol (NETCONF) is applicable to a wide range of devices in a variety of environments. The emergence of Web Services gives one such environment, and is presently characterized by the use of the Simple Object Access Protocol (SOAP). NETCONF finds many benefits in this environment: from the re-use of existing standards, to ease of software development, to integration with deployed systems. Herein, we describe SOAP over HTTP (Hypertext Transport Protocol) and SOAP over BEEP (Blocks Exchange Extensible Protocol) bindings for NETCONF.
(see also JCA-Mgt)
M.3016.0 Security for the Management Plane- Overview This Recommendation provides an overview and framework for the security of the management plane for telecom networks, including Next Generation Networks (NGN). In particular, it describes security threats and solutions related to the communication of management information between telecom network resources and associated management systems in telecom management networks, and also between management systems.
M.3016.1 Security for the Management Plane- Security Requirements This Recommendation provides the security requirements for the management plane of telecom networks, including Next Generation Networks (NGN). In particular, it describes security requirements related to the communication of management information between telecom network resources and associated management systems in telecom management networks, and also between management systems.
This Recommendation provides the security services for the management plane of telecom networks, including Next Generation Networks (NGN). In particular, it describes security services related to the communication of management information between telecom network resources and associated management systems in telecom management networks, and also between management systems.
This Recommendation provides the security mechanisms for the management plane of telecom networks, including Next Generation Networks (NGN). In particular, it describes security mechanisms related to the communication of management information between telecom network resources and associated management systems in telecom management networks, and also between management systems.
This Recommendation specifies a Proforma for the security requirements, mechanisms and services in Recommendations M.3016.1-3. The Proforma when completed by different organizations results in a profile for the security requirements, services and mechanisms. These profiles may be used by implementations to specify conformance.
M.3050 series- Enhanced Telecom Operations Map This Recommendation is equivalent to the Enhanced Telecom Operations Map¬Æ (eTOM) version 7.0 developed by the TeleManagement Forum TMF as a reference framework for categorizing all the business activities that a service provider will use. It is a multipart document with the following structure:
This Recommendation presents the management principles, requirements, and architecture for managing Next Generation Networks (NGN) to support business processes to plan, provision, install, maintain, operate and administer Next Generation Network (NGN) resources and services. It defines concepts of the NGN management architecture, i.e., its business process view, functional view, information view, and physical views; and their fundamental elements. It also describes the relationships among the architectural views and provides a framework to derive the requirements for the specification of management physical views from the management functional and information views. A logical reference model for partitioning of management functionality, the Logical Layered Architecture (LLA), is also provided.
This document identifies the various existing, or work-in-progress specifications relevant to NGN management. These specifications are not all ITU-T Recommendations, but also come from other standards making bodies with expertise in defining management interfaces. For example, the roadmap tags the 3GPP (3rd Generation Partnership Project) specs for mobile telephony relevant to the IMS (IP Multimedia Subsystem) management. IMS is expected to be a key building block for NGN. An additional and important feature of the document is that it provides gap analysis, identifying areas where standards are still needed, and also identifies overlapping specifications requiring harmonization.
The scope of the Joint Coordination Activity on Management (JCA-Mgt) is the coordination of the management standardization work inside and outside of the ITU-T. This JCA includes the coordination responsibilities previously addressed by the NGN Management Focus Group (NGNMFG) regarding NGN management, but goes beyond by including also the coordination of the work related to the next generation of telecommunication management networks as well as management of the NGN.
As with the NGNMFG, the management work is focused on the specification of management interfaces associated with a telecommunication management network. Such management interfaces include interfaces between a network element and a management system and between two management systems, but exclude management interfaces between network elements.
Participation is open to leaders and other invited individuals from ITU-T and non-ITU-T organizations with expertise and specifications applicable to management interfaces.
Participation is open to leaders and other invited individuals from organizations with expertise and specifications applicable to management interfaces, including the following:
ETSI (The European Tececommunications Standards Institute) has a Technical committee TC GRID whose goal is to address issues associated with the convergence between IT (Information Technology) and Telecommunications, with particular reference to the lack of interoperable Grid solutions in situations which involve contributions from both the IT and Telecom industries. This places the focus on scenarios where connectivity goes beyond the local network. The TC GRID activities have an emphasis on interoperable Grid applications and services based on global standards and the validation tools to support these standards.
The technical scope of TC GRID is broad. It includes, but is not restricted to: resource and service access, protocols, middleware, security and service engineering across the full lifecycle
Convergence is viewed in a broad sense including: IT and Telecommunications, Grid and Web Services, Fixed and mobile communications and Ubiquitous services
In addition a Specialist Task Force (STF) has been established, to support the work of the Technical Committee.
The STF will produce a Final Report for delivery to the EC and the ETSI deliverables produced by the STF will include: DTR/GRID-0001-1 Study of ICT Grid interoperability gaps; Part 1: Inventory of ICT Stakeholders, DTR/GRID-0001-2 Study of ICT Grid interoperability gaps; Part 2: List of identified Gaps , ICT Grid Interoperability State of the Art Website and mailing list, A workshop of Grid Stakeholders and DTR/GRID-0002 ICT Grid Interoperability Testing Framework
This technical report addresses the need to identify interoperability gaps in existing and emerging Global/European Grid standards. It provides an inventory and analysis across the range of relevant standards-making bodies with a view to determining the shortcomings; overlaps and loopholes in current, proposed, and de facto Grid standards at all levels of the middleware/protocol stack (network to application interfaces), with specific consideration for large-scale commercialization and interoperability of standards/systems relevant to the ICT sector (i.e. the ETSI constituency).
This is part 1 of a 2 part document providing a study of ICT Grid interoperability gaps. The present document captures the current state of Grid technologies and identifies the key stakeholders, including standards making bodies, research projects, production grids and other initiatives. Additionally, it identifies a recommended base of standards and de facto standards in the form of a Grid ICT Profile, taking into account the requirements for interoperability in the ICT domain.
This is part two of a two part document providing a study of ICT Grid interoperability gaps. The present document provides an initial gap analysis. The gaps have been identified through analysis of a series of scenarios, a summary of which can be found in the appendices. By selecting common themes across those scenarios it has been possible to identify specific requirements. These have directed the analysis of specific Grid standards. Standards identified may be Grid specific standards or other standards which support an integrated Grid NGN environment.
This Technical Report offers a standard, uniform way of describing grid resources, so as to make these resources available to grid-based applications.
When building a grid, one is confronted to several problems, among which inlcude: choosing a grid framework, as many are available, when running a grid-enabled application, one must rewrite configuration directives when switching to a different grid framework, a grid can be built on widely different hardware infrastructures, from an heterogenous set of desktop machines to a dedicated cluster, or even any combination of those and grid infrastructures can also be very dynamic, it should be easy to add or remove machines, and such changes should be transparent to users.
To simplify this, the GCM Interoperability Deployment standard offers a uniform way to describe grid resources, how they are connected to one another, how they can be activated, and how they can be accessed.
This Technical Report follows on from TR 102 827 and describes an XML schema for describing application constraints and resources to be used for deploying these applications on distributed and parallel infrastructures, like enterprise and scientific grids or job schedulers.
The standard will help enterprises and laboratories to manage their IT software within large-scale computer and telecom infrastructures with the necessary virtualization.
Its primary audience are users of grid-based applications who will need to write application descriptors so they can run them on the grid for their grid.
Web Services Distributed Management (WSDM) Management Using Web Service (MUWS) v1.0
Management Using Web Services (MUWS) defines a Web service interface for management providers. This can be used to manage any manageable resource and any manager. WSDM MUWS 1.0 defines how to represent and access the manageability interfaces of resources as Web services. It is the foundation of enabling management applications to be built using Web services and allows resources to be managed by many managers with one set of instrumentation. This specification provides interoperable, base manageability for monitoring and control managers using Web services.
Management Of Web Services (MOWS) defines a specialization for the case where the manageable resource is a Web service. Specifically, WSDM MOWS defines the manageability model for managing Web services as a resource and how to describe and access that manageability using MUWS
Creating an XML-based data model and format for exchanging information about the contents of data centers and other IT resources and information used in managing those resources
The WS-Notification family of specifications defines a standard Web services approach to notification. WS-Base Notification is the base specification on which all the other specifications in the family depend. It defines the normative Web services interfaces for two of the important roles in the notification pattern, namely the NotificationProducer and NotificationConsumer roles. This specification includes standard message exchanges to be implemented by service providers that wish to act in these roles, along with operational requirements expected of them.
This document defines a mechanism to organize and categorize items of interest for subscription known as "topics". These are used in conjunction with the notification mechanisms defined in WS-Base Notification. WS-Topics defines three topic expression dialects that can be used as subscription expressions in subscribe request messages and other parts of the WS-Notification system. It further specifies an XML model for describing metadata associated with topics.
This document standardizes the means by which the definition of the properties of a WS-Resource may be declared as part of a Web service interface in terms of a resource properties document. This resource properties document serves to define a basis for access to the resource properties through Web service interfaces. This specification also defines a standard set of message exchanges that allow a requestor to query or update the property values of the WS-Resource. The set of properties defined in the resource properties document associated with the service interface defines the constraints on the valid contents of these message exchanges. (The relationship between Web services and stateful resources is defined in WS-Resource i.e. a WS-Resource represents the composition of a stateful resource and a Web service. One characteristic of a WS-Resource is the set of properties associated with the resource.)
This specification defines message exchanges to standardize the means by which a WS-Resource may be destroyed, and resource properties WS-ResourceProperties that may be used to inspect and monitor the lifetime of a WS-Resource. This specification defines two means of destroying a WS-Resource: immediate destruction and time-based, scheduled destruction. The relationship between Web services and stateful resources is defined in WS-Resource
Standardizing XML schema that describes the characteristics of an installable unit (IU) of software that are relevant for core aspects of its deployment, configuration, and maintenance. This document will be referred to as the Solution Deployment Descriptor (SDD).
SMI-S(ANSI INCITS 388-2004)
SMI-S supplies profiles of Resource Information Models speciic for storage and is a Discipline Specific Management standard for the Storage Industry. This Technical Specification defines the a method for the interoperable management of a heterogeneous Storage Area Network (SAN). This Technical Specification describes the information available to a WBEM Client from an SMI-S compliant CIM Server. This Technical Specification describes an object-oriented, XML-based, messaging-based interface designed to support the specific requirements of managing devices in and through Storage Area Networks (SANs).
The CDMI standard is applicable to public, private and hybrid storage clouds and is expected to be implemented by service providers and cloud infrastructure vendors for all cloud deployment models. More than just a data path to the cloud, the CDMI also includes the ability to manage service levels that data receives when it is stored in the cloud. The CDMI also includes a common interoperable data exchange format for securely moving data and its associated data requirements from cloud to cloud.
NGOSS (New Generation Operations Systems and Software) v4.5 Lifecycle & methodology eTOM SID Architecture
An integrated framework of technical specifications which may be used to develop Operation Support Systems (OSS and BSS) / Management Systems for the Communications / Telecommunications Industry.
SOAP Version 1.2 Part 1- Messaging Framework v1.2
SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. "Part 1: Messaging Framework" defines, using XML technologies, an extensible messaging framework containing a message construct that can be exchanged over a variety of underlying protocols.
SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. SOAP Version 1.2 Part 2: Adjuncts defines a set of adjuncts that may be used with SOAP Version 1.2 Part1: Messaging Framework. This specification depends on SOAP Version 1.2 Part 1: Messaging Framework.
This document describes an abstract feature and a concrete implementation of it for optimizing the transmission and/or wire format of SOAP messages. The concrete implementation relies on the XML-binary Optimized Packaging format for carrying SOAP messages.
This document describes an abstract feature and a concrete implementation of it for optimizing the transmission and/or wire format of SOAP messages. The concrete implementation relies on the XML-binary Optimized Packaging format for carrying SOAP messages.
This specification defines the core language which can be used to describe Web services based on an abstract model of what the service offers. It also defines criteria for a conformant processor of this language.
Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts defines some extensions for use in WSDL 2.0:
Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 - Core (this document) defines a set of abstract properties and an XML Infoset XML Information Set representation thereof to reference Web services and to facilitate end-to-end addressing of endpoints in messages. This specification enables messaging systems to support message transmission through networks that include processing nodes such as endpoint managers, firewalls, and gateways in a transport-neutral manner.
Web Services Addressing 1.0 - SOAP Binding defines the binding of the abstract properties defined in Web Services Addressing 1.0 - Core to SOAP Messages.
Web Services Addressing 1.0 - Metadata defines how the abstract properties defined in Web Services Addressing 1.0 - Core are described using WSDL, how to include WSDL metadata in endpoint references, and how WS-Policy can be used to indicate the support of WS-Addressing by a Web service.
The Web Services Policy 1.5 - Framework provides a general purpose model and corresponding syntax to describe the policies of entities in a Web services-based system. Web Services Policy Framework defines a base set of constructs that can be used and extended by other Web services specifications to describe a broad range of service requirements and capabilities.
Web Services Policy 1.5 - Attachment defines two general-purpose mechanisms for associating policies, as defined in Web Services Policy 1.5 - Framework, with the subjects to which they apply. It also defines how these general-purpose mechanisms may be used to associate policies with WSDL and UDDI descriptions.
|Contact Webmaster | Report a problem | GridForge Help|