In this page, we explore various concepts behind Continuuity Loom administration and explain various tools used in Continuuity Loom for administrators to configure and manage their clusters. At the core of a Loom cluster is the notion of a Template, which is the blueprint or the primordial stuff of what Loom clusters are comprised of—it is the essence or the DNA of how different parts and components come together to materialize into a cluster.
As mentioned above, Continuuity Loom works through the use of Templates, which dictate the configuration of the clusters that users can spin up. An administrator can specify any number of such templates to put into their Catalog for users.
Several concepts central to cluster configuration are definable in Continuuity Loom. These aspects are:
Templates are defined by specifying hardware types, image types, and services that can be used in a cluster, as well as a set of constraints that describes how those hardware types, image types, and services should be laid out in a cluster. Template creation can be done in two ways: 1) Admin UI and 2) Web Services REST Cluster API.
Continuuity Loom includes several tools for administrators to simplify their administrative tasks. Apart from the Admin UI, Continuuity Loom provides several additional metrics and monitoring tools. Continuuity Loom allows administrators to configure their servers and write custom plugins for allocating machines with your providers or to implement custom services. Administrators who are more command line driven, or who wish to write quick administrative scripts, can employ the Web services API.
Please refer to the following pages for more details: