2021-04-20 21:31:37 +00:00
|
|
|
# Contributing Storage
|
|
|
|
|
|
|
|
If your host machine can be reasonably sure of being online most, if not all, of
|
|
|
|
the time, and has 100GB or more of unused drive space you'd like to contribute
|
|
|
|
to the network, then this document is for you.
|
|
|
|
|
2022-11-03 14:38:31 +00:00
|
|
|
## Create `daemon.yml`
|
2021-04-20 21:31:37 +00:00
|
|
|
|
|
|
|
First, if you haven't already, [create a `daemon.yml`
|
|
|
|
file](../user/creating-a-daemonyml-file.md). This will be used to
|
2023-08-05 21:53:17 +00:00
|
|
|
configure your `isle daemon` process with the storage locations and
|
2021-04-20 21:31:37 +00:00
|
|
|
capacities you want to contribute.
|
|
|
|
|
2022-11-03 14:38:31 +00:00
|
|
|
## Edit `daemon.yml`
|
2021-04-20 21:31:37 +00:00
|
|
|
|
|
|
|
Open your `daemon.yml` file in a text editor, and find the
|
|
|
|
`storage.allocations` section.
|
|
|
|
|
|
|
|
Each allocation in the allocations list describes the space being contributed
|
|
|
|
from a single physical drive. If you only have one drive then you will only need
|
|
|
|
one allocation listed.
|
|
|
|
|
|
|
|
The comments in the file should be self-explanatory, but ask your admin if you
|
|
|
|
need any clarification.
|
|
|
|
|
|
|
|
Here are an example set of allocations for a host which is contributing space
|
|
|
|
from two separate drives:
|
|
|
|
|
|
|
|
```
|
|
|
|
storage:
|
|
|
|
allocations:
|
|
|
|
|
|
|
|
# 1.2 TB are being shared from drive1
|
2023-08-05 21:53:17 +00:00
|
|
|
- data_path: /mnt/drive1/isle/data
|
|
|
|
meta_path: /mnt/drive1/isle/meta
|
2021-04-20 21:31:37 +00:00
|
|
|
capacity: 1200
|
|
|
|
|
|
|
|
# 100 GB (the minimum) are being shared from drive2
|
2023-08-05 21:53:17 +00:00
|
|
|
- data_path: /mnt/drive2/isle/data
|
|
|
|
meta_path: /mnt/drive2/isle/meta
|
2021-04-20 21:31:37 +00:00
|
|
|
capacity: 100
|
|
|
|
```
|
|
|
|
|
2022-11-05 16:16:25 +00:00
|
|
|
## Set Up Your Firewall
|
|
|
|
|
|
|
|
See the doc on [Firewalls](./firewalls.md), to be sure that your host's firewall
|
|
|
|
is properly set up for providing storage.
|
|
|
|
|
2021-04-20 21:31:37 +00:00
|
|
|
## Restart the Daemon
|
|
|
|
|
2023-08-05 21:53:17 +00:00
|
|
|
With the `daemon.yml` configured, you should restart your `isle daemon`
|
2021-04-20 21:31:37 +00:00
|
|
|
process.
|
|
|
|
|
2023-08-05 21:53:17 +00:00
|
|
|
The `isle daemon` will automatically allow the ports used for your
|
2022-11-03 13:30:54 +00:00
|
|
|
storage allocations in the vpn firewall.
|
|
|
|
|
2021-04-20 21:31:37 +00:00
|
|
|
## Further Reading
|
|
|
|
|
2023-08-05 21:53:17 +00:00
|
|
|
Isle uses the [garage][garage] project for its storage system. See the
|
2021-04-20 21:31:37 +00:00
|
|
|
[Managing Garage](managing-garage.md) document for more
|
|
|
|
information on how to interact directly with the garage instance being run by
|
2023-08-05 21:53:17 +00:00
|
|
|
isle.
|
2021-04-20 21:31:37 +00:00
|
|
|
|
|
|
|
[garage]: https://garagehq.deuxfleurs.fr/documentation/quick-start/
|