OpenSAF
   HOME
*



picture info

OpenSAF
OpenSAF (commonly styled SAF, the Service Availability Framework) is an open-source service-orchestration system for automating computer application deployment, scaling, and management. OpenSAF is consistent with, and expands upon, Service Availability Forum (SAF) and SCOPE Alliance standards. It was originally designed by Motorola ECC, and is maintained by the OpenSAF Project. OpenSAF is the most complete implementation of the SAF AIS specifications, providing a platform for automating deployment, scaling, and operations of application services across clusters of hosts. It works across a range of virtualization tools and runs services in a cluster, often integrating with JVM, Vagrant, and/or Docker runtimes. OpenSAF originally interfaced with standard C Application Programming interfaces (APIs), but has added Java and Python bindings. OpenSAF is focused on Service Availability beyond High Availability (HA) requirements. While little formal research is published to improve ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]  


picture info

OpenSAF V4 Architecture
OpenSAF (commonly styled SAF, the Service Availability Framework) is an open-source software, open-source Service-oriented architecture, service-orchestration (computing), orchestration system for automating computer application software, application deployment, scaling, and management. OpenSAF is consistent with, and expands upon, Service Availability Forum, Service Availability Forum (SAF) and SCOPE Alliance standards. It was originally designed by Motorola, Motorola ECC, and is maintained by the OpenSAF Project. OpenSAF is the most complete implementation of the Service Availability Forum, SAF AIS specifications, providing a platform for automating deployment, scaling, and operations of application services across clusters of hosts. It works across a range of virtualization tools and runs services in a cluster, often integrating with Java virtual machine, JVM, Vagrant (software), Vagrant, and/or Docker (software), Docker runtimes. OpenSAF originally interfaced with standard C ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]  


picture info

SCOPE Alliance
The SCOPE Alliance was a non-profit and influential Network Equipment provider (NEP) industry group aimed at standardizing "carrier-grade" systems for telecom in the Information Age. The SCOPE Alliance was founded in January 2006 by a group of NEP's, including Alcatel, Ericsson, Motorola, NEC, Nokia, and Siemens. In 2007, it added significantly to its membership. Mission Active between 2006 and 2012, its mission was to enable and promote the availability of open carrier-grade base platforms based on commercial off-the-shelf (COTS) hardware/software and free and open-source software building blocks, and promote interoperability between such components. SCOPE wanted to accelerate the deployment of carrier-grade base platforms (CGBP) for service provider applications so that NEP's could use them to build better solutions for their customers. By 2011, SCOPE achieved its aim, having accelerated innovation in carrier-grade communications technology and ATCA, NEPs sell integrated h ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]  




Hardware Platform Interface
The Hardware Platform Interface (HPI) is an open specification that defines an application programming interface (API) for platform management of computer systems. The API supports tasks including reading temperature or voltage sensors built into a processor, configuring hardware registers, accessing system inventory information like model numbers and serial numbers, and performing more complex activities, such as upgrading system firmware or diagnosing system failures. HPI is designed for use with fault-tolerant and modular high-availability computer systems, which typically include automatic fault detection features and hardware redundancy so that they can provide continuous Service Availability. Additional features common in hardware platforms used for high-availability applications include online serviceability and upgradeability via hot-swappable modules. The HPI specification is developed and published by the Service Availability Forum (SA Forum) and made freely available t ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]  


Carrier Grade Linux
Carrier Grade Linux (CGL) is a set of specifications which detail standards of availability, scalability, manageability, and service response characteristics which must be met in order for Linux kernel-based operating system to be considered "carrier grade" (i.e. ready for use within the telecommunications industry). The term is particularly applicable as telecom converges technically with data networks and commercial off-the-shelf commoditized components such as blade servers. Carrier-grade is a term for public network telecommunications products that require up to 5 nines or 6 nines (or 99.999 to 99.9999 percent) availability, which translates to downtime per year of 30 seconds (6 nines) to 5 minutes (5 nines). The term "5 nines" is usually associated with carrier-class servers, while "6 nines" is usually associated with carrier-class switches. CGL project and goals The primary motivation behind the CGL effort is to present an open architecture alternative to the closed, p ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]  


picture info

Service Availability
The Service Availability Forum (SAF or SA Forum) is a consortium that develops, publishes, educates on and promotes open specifications for carrier-grade and mission-critical systems. Formed in 2001, it promotes development and deployment of commercial off-the-shelf (COTS) technology. Description Service availability is an extension of high availability, referring to services that are available regardless of hardware, software or user fault and importance. Key principles of service availability: * Redundancy – "backup" capability in case of need to failover due to a fault * Stateful and seamless recovery from failures * Minimization of mean time to repair (MTTR) – time to restore service after an outage * Fault prediction & avoidance – take action before something fails The traditional definitions of high availability have their roots in hardware systems where redundancy of equipment was the primary mechanism for achieving uptime over a specific period. As software has c ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]  



MORE