|
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] |
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] |
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] |
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] |
High-availability Cluster
High-availability clusters (also known as HA clusters, fail-over clusters) are groups of computers that support server applications that can be reliably utilized with a minimum amount of down-time. They operate by using high availability software to harness redundant computers in groups or clusters that provide continued service when system components fail. Without clustering, if a server running a particular application crashes, the application will be unavailable until the crashed server is fixed. HA clustering remedies this situation by detecting hardware/software faults, and immediately restarting the application on another system without requiring administrative intervention, a process known as failover. As part of this process, clustering software may configure the node before starting the application on it. For example, appropriate file systems may need to be imported and mounted, network hardware may have to be configured, and some supporting applications may need to ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Service Availability Forum
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] |
Apache ZooKeeper
Apache ZooKeeper is an open-source server for highly reliable distributed coordination of cloud applications. It is a project of the Apache Software Foundation. ZooKeeper is essentially a service for distributed systems offering a hierarchical key-value store, which is used to provide a distributed configuration service, synchronization service, and naming registry for large distributed systems (see ''Use cases''). ZooKeeper was a sub-project of Hadoop but is now a top-level Apache project in its own right. Overview ZooKeeper's architecture supports high availability through redundant services. The clients can thus ask another ZooKeeper leader if the first fails to answer. ZooKeeper nodes store their data in a hierarchical name space, much like a file system or a tree data structure. Clients can read from and write to the nodes and in this way have a shared configuration service. ZooKeeper can be viewed as an atomic broadcast system, through which updates are totally ordere ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
CAP Theorem
In theoretical computer science, the CAP theorem, also named Brewer's theorem after computer scientist Eric Brewer, states that any distributed data store can provide only two of the following three guarantees:Seth Gilbert and Nancy Lynch"Brewer's conjecture and the feasibility of consistent, available, partition-tolerant web services" ''ACM SIGACT News'', Volume 33 Issue 2 (2002), pg. 51–59. . ; Consistency: Every read receives the most recent write or an error. ; Availability: Every request receives a (non-error) response, without the guarantee that it contains the most recent write. ; Partition tolerance: The system continues to operate despite an arbitrary number of messages being dropped (or delayed) by the network between nodes. When a network partition failure happens, it must be decided whether to do one of the following: * cancel the operation and thus decrease the availability but ensure consistency * proceed with the operation and thus provide availability but risk i ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Cloud Computing Architecture
Cloud computing architecture refers to the components and subcomponents required for cloud computing. These components typically consist of a front end platform (fat client, thin client, mobile), back end platforms (servers, storage), a cloud based delivery, and a network (Internet, Intranet, Intercloud). Combined, these components make up cloud computing architecture. Client platforms Cloud computing architectures consist of front-end platforms called clients or cloud clients. These clients are servers, fat (or thick) clients, thin clients, zero clients, tablets and mobile devices that users directly interact with. These client platforms interact with the cloud data storage via an application (middle ware), via a web browser, or through a virtual session. Virtual sessions in particular require secure encryption algorithm frame working which spans the entire interface. Zero client The zero or ultra-thin client initializes the network to gather required configuration files th ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Cloud Native Computing Foundation
The Cloud Native Computing Foundation (CNCF) is a Linux Foundation project that was founded in 2015 to help advance container technology and align the tech industry around its evolution. It was announced alongside Kubernetes 1.0, an open source container cluster manager, which was contributed to the Linux Foundation by Google as a seed technology. Founding members include Google, CoreOS, Mesosphere, Red Hat, Twitter, Huawei, Intel, Cisco, IBM, Docker, Univa, and VMware. Today, CNCF is supported by over 450 members. In order to establish qualified representatives of the technologies governed by the CNCF, a program was announced at the inaugural CloudNativeDay in Toronto in August, 2016. Dan Kohn (who also helped launch the Core Infrastructure Initiative) led CNCF as executive director until May 2020. The foundation announced Priyanka Sharma, director of Cloud Native Alliances at GitLab, would step into a general manager role in his place. Sharma describes CNCF as "a very impa ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Application Programming Interface
An application programming interface (API) is a way for two or more computer programs to communicate with each other. It is a type of software interface, offering a service to other pieces of software. A document or standard that describes how to build or use such a connection or interface is called an ''API specification''. A computer system that meets this standard is said to ''implement'' or ''expose'' an API. The term API may refer either to the specification or to the implementation. In contrast to a user interface, which connects a computer to a person, an application programming interface connects computers or pieces of software to each other. It is not intended to be used directly by a person (the end user) other than a computer programmer who is incorporating it into the software. An API is often made up of different parts which act as tools or services that are available to the programmer. A program or a programmer that uses one of these parts is said to ''call'' that ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
