1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
# 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 a registry service. With additional units added, the charm sets up the replication of the registry.
The Registry service is at the top of the Quobyte service hierarchy:
- It acts as the central registry for volumes, services, and devices.
- It stores the system configuration.
- It also resolves identifiers to their network location.
- It runs global rebalance maintenance tasks.
- It acts as the global time source.
Together with the quobyte-data and quobyte-metadata charms it forms a Quobyte installation.
While there is only a single system registry in the system, the Registry is usually replicated across three Registry service instances.
During normal operation, most services and clients talk to the Registry service to synchronize their time and lookup identifiers that are not in their caches yet.
# Usage
The quobyte-registry charm has two 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
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 the variable to True. You can obtain a copy of the license at http://java.com/license
The quobyte-registry charm makes use of the [Storage support](https://jujucharms.com/docs/stable/storage) in Juju which allows you to specify the used storage and size.
Here's an example: in order to deploy the Registry service on 3 machines using Amazon EBS with 100GB per instance on EC2, do:
juju deploy quobyte-registry qb-reg --storage registry-storage=ebs,100G
juju add-unit -n2 qb-reg
juju set qb-reg repo_id=<repo_id>
juju set qb-reg oracle-java-license-accepted=true
The quobyte-registry charm configures the Registry service and sets up the replication among the instances.
The deployed Registry service manages the storage provided by the Quobyte Data and Metadata services.
The quobyte-webconsole and quobyte-api charm -- which can be collocated with the Registry -- provide the interface for further configuration of the Quobyte system.
# Contact Information
To contact [Quobyte](http://www.quobyte.com) you can drop us a line [here](http://www.quobyte.com/contact).
Charm authors:
- [Bruno Ranieri](https://launchpad.net/~3-bruno/+contactuser)
|