quobyte api #1

  • By quobyte
  • Latest version (#1)
  • trusty
  • Stable
  • Edge

Description

Quobyte is a distributed file system that turns commodity servers into a unified software storage system. As a genuine data center file system it supports high-performance workloads ranging from Big Data to VMs. It is completely fault-tolerant and massively scalable.
.
Quobyte simplifies the design, deployment, and management of storage infrastructures of any size.
.
This charm deploys the API service. It provides a convenient way to administrate a Quobyte installation.


Overview

Quobyte is a distributed file system that turns commodity servers into a unified software storage system. As a genuine data center file system it supports high-performance workloads ranging from Big Data to VMs. It is completely fault-tolerant and massively scalable.

This charm deploys the API service. Like the quobyte-webconsole charm, it provides a convenient way to administrate a Quobyte installation.

Usage

The quobyte-api charm has three mandatory configuration items. Without them, the installation will not go through.

repo_id:
    In order to access your Quobyte packages an id from your Quobyte support account is integrated into the package repository path. You can fetch your repo_id at https://support.quobyte.com

quobyte-license-accepted:
    Set parameter to accept the Quobyte License, obtainable at http://www.quobyte.com/cloud/juju/assets/license

oracle-java-license-accepted:
    Quobyte depends on an Oracle Java 8 Installation. The charm installs Java, when the Oracle Java License is accepted by setting this variable to True. You may obtain a copy of the license at http://java.com/license

By adding a relation with a deployed quobyte-registry charm, the quobyte-metadata charm is configured, e.g. for a Registry service named qb-reg and an API Service named qb-api:

juju add-relation qb-reg qb-api

The API service can be used via JSON RPC 2.0 or with the qmgmt commandline tool:

qmgmt -u http://<api-host>:<api-port> <command> [parameters]

The documentation for the RPC and qmgmt can be found at support.quobyte.com.

Configuration

To configure the API service, a relation to a deployed Registry service is needed. For a Registry service named qb-reg and an API service named qb-api type:

juju add-relation qb-reg qb-api

or deploy the quobyte-data charm again and add a relation to the Registry service as shown above.

Collocation

The API service can be collocated with other Quobyte services. The deployment can be controlled by providing the id of the targeted machine that's already hosting services.

juju deploy --to 1 quobyte-api qb-api

deploys the quobyte-api charm named as qb-api to machine 1.

Known Limitations and Issues

  • while the API Service supports SSL encryption, the current charm does not provide a possibility to set this up.

Contact Information

To contact Quobyte you can drop us a line here.

Charm authors:
- Bruno Ranieri

Configuration

quobyte-license-accepted
(boolean) Set parameter to accept the Quobyte License, obtainable at http://www.quobyte.com/cloud/juju/assets/license
repo_id
(string) Set to customer repository id. The default is a placeholder id.
loremipsum1234loremipsum1234lore
oracle-java-license-accepted
(boolean) Quobyte depends on an Oracle Java 8 Installation. Set parameter to accept the Java License, obtainable at http://java.com/license