Reference Guide
Table Of Contents
- 1 Introduction
- 2 Establishing Your Test and Development Environments
- 3 Developing Applications
- Introduction
- Authentication
- REST API
- Audit Logging
- Alert Logging
- Configuration
- High Availability
- OpenFlow
- Metrics Framework
- GUI
- SKI Framework - Overview
- SKI Framework - Navigation Tree
- SKI Framework - Hash Navigation
- SKI Framework - View Life-Cycle
- SKI Framework - Live Reference Application
- UI Extension
- Introduction
- Controller Teaming
- Distributed Coordination Service
- Persistence
- Backup and Restore
- Device Driver Framework
- 4 Application Security
- 5 Including Debian Packages with Applications
- 6 Sample Application
- Application Description
- Creating Application Development Workspace
- Application Generator (Automatic Workspace Creation)
- Creating Eclipse Projects
- Updating Project Dependencies
- Building the Application
- Installing the Application
- Application Code
- 7 Testing Applications
- 8 Built-In Applications
- Appendix A
- Appendix B
- Bibliography
Table 3 System Status
System Status
Coordination Services
Reason
Active
Available
The controller is healthy and part of a cluster with
a quorum.
Suspended
Unavailable
The controller is unhealthy or part of a cluster with
no quorum.
Unreachable
Depends whether active or
suspended
The controller is unreachable because of failures
or network partition.
Considerations:
•
A system never sees itself as unreachable.
•
The strategy followed on the event of a network partition is to suspend controllers that are
part of a cluster with no quorum.
The following figure illustrates two examples of how each controller sees the status of the other
controllers that are part of the team. Examples show a 5-node cluster for simplicity; this does not mean
this release supports teams of such size. The behavior shown in the examples can easily be applied to
any cluster size.
84