slapos.core/slapos-proxy.cfg.example at master · SlapOS/slapos.core · GitHub

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
54
55
56
57
58
59
60
61
62
# This is an example configuration file for a standalone micro slapos master
# a.k.a slapproxy
[slapos]
instance_root = /srv/slapgrid
software_root = /opt/slapgrid
computer_id = local_computer

[slapproxy]
host = 127.0.0.1
port = 5000
database_uri = /opt/slapos/slapproxy.db


###############################
# Optional, advanced parameters
###############################

# Below is the list of software maintained by slapos.org and contributors
# It is used to simulate a proper configuration of a real slapos master.
software_product_list =
  erp5 https://lab.node.vifib.com/nexedi/slapos/raw/1.0.48/software/erp5/software.cfg
  kvm https://lab.node.vifib.com/nexedi/slapos/raw/1.0.48/software/kvm/software.cfg
  slaprunner https://lab.node.vifib.com/nexedi/slapos/raw/1.0.48/software/slaprunner/software.cfg
  frontend https://lab.node.vifib.com/nexedi/slapos/raw/1.0.48/software/apache-frontend/software.cfg
  monitor https://lab.node.vifib.com/nexedi/slapos/raw/1.0.48/software/monitor/software.cfg
  cloudooo https://lab.node.vifib.com/nexedi/slapos/raw/1.0.48/software/cloudooo/software.cfg
  wendelin https://lab.node.vifib.com/nexedi/slapos/raw/1.0.48/software/wendelin/software.cfg

# Here goes the list of slapos masters that slapos.proxy is authorized to
#     contact to forward an instance request.
#
# Each section beginning by "multimaster/" is a different SlapOS Master,
#     represented by its URL.
#
# For each section, you need to specify the URL of the SlapOS Master in the
#     section name itself.
#
# For each section, you can specify if needed the location of key/certificate
#     used to authenticate to this slapOS Master.
#
# For each section, you can specify if needed a list of Software Releases,
#     separated by carrier return. Any instance request matching one of those
#     Software Releases will be automatically forwarded to this SlapOS Master
#     and will not be allocated locally.
#
# When doing an instance request, you can specify in filter (a.k.a SLA) a
#     "master_url" that will be used by the slapproxy to forward the request.


# Uncomment the sections bellow to enable multi-master sections, and set
# your cert/key.
#[multimaster/https://slap.vifib.com]
#key = key file path coming from your slapos master account
#cert = certificate file path coming from your slapos master account
#software_release_list =
#  http://git.erp5.org/gitweb/slapos.git/blob_plain/HEAD:/software/apache-frontend/software.cfg

#[multimaster/http://imaginary-slapos-master.example]
# No certificate here: it is http.
#software_release_list =
#  http://slapos.example/my_software_release.cfg
#  /some/arbitrary/local/unix/path