CycleServer is the platform on which CycleCloud runs, designed with a plugin-based architecture. Internally, CycleServer itself is composed of a set of plugins built on top of this architecture (as are other Cycle products). Developers may use these plugin APIs to replace or extend CycleServer functionality by writing and installing new plugins.
This guide will provide step-by-step instructions to get you started developing for CycleServer.
CycleServer: The platform on which CycleCloud runs. It provides APIs which can be used to add everything from simple user interfaces and data queries to complete applications.
CycleCloud: Cycle Computing’s application for managing cloud resources. Data is stored as records in CycleCloud, and can be managed using a RESTful API.
Plugin: A plugin is a unit of code, along with a set of resources (files) that can be used by the code. Each plugin is identified by a single dot-separated name (lower-case with optional underscores by convention).
Component: A component is a set of plugins loaded as a unit. Each plugin is contained in exactly one component. By convention, component names are short (i.e. ‘sysmon’), and plugin names are prefixed with their component name.
In This Guide
- CycleServer Services
- Development Requirements
- CycleServer Datastore
- Permissions and Constraint-based Authorization
- CycleCloud Overview
- Custom Orchestration
- RESTful API
- CycleCloud Cluster Services Registration
- Attribute Reference
- Cloud Resource Reference