forked from immarvin/xcat-docker
-
Notifications
You must be signed in to change notification settings - Fork 0
/
docker-compose.yml
75 lines (70 loc) · 2.62 KB
/
docker-compose.yml
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
63
64
65
66
67
68
69
70
71
72
73
74
75
version: '3.2'
services:
xcatmn:
#the xCAT docker image name and tag, with format [xCAT docker image name]:[tag]
image: schwarzwald/xcat-docker
#Needed to run as systemd service. Otherwise will freeze upon startup.
cap_add:
- SYS_ADMIN
#tty enable
tty: true
#stdin enable
stdin_open: true
#the /etc/hosts entry of container itself to be added into /etc/hosts inside container
#the format is "[FQDN] [host name]: [IP address]"
#FQDN is madatory. the domain name of FQDN will be set in site.domain
extra_hosts:
- "xcatmn.clusters.com xcatmn:10.5.107.101"
#the network objects the container will be connected to
networks:
#the service network, connecting to the hardware control point of the cluster
svcnet:
#the IP address of container in service network
ipv4_address : 192.160.0.101
#the management network, connecting to the compute nodes in the cluster
mgtnet:
#the IP address of container in management network
ipv4_address : 10.5.107.101
volumes:
#the "/install" volume is used to keep user data in xCAT,
#such as osimage resources
- xcat-install:/install
#the "/.dbbackup" volume is used to backup and restore xCAT DB tables
#Dockerized xCAT will restore xCAT DB tables if specified
#"dumpxCATdb -p /.dbbackup" should be run manually to save xCAT DB inside container
- xcat-dbbackup:/.dbbackup
#the "/var/log/xcat/" volume is used to keep xCAT logs
- xcat-logs:/var/log/xcat/
#tftpboot generated files
- xcat-tftpboot:/tftpboot
volumes:
xcat-install:
xcat-dbbackup:
xcat-logs:
xcat-tftpboot:
networks:
mgtnet:
driver: "bridge"
driver_opts:
com.docker.network.bridge.name: "mgtbr"
#com.docker.network.bridge.host_binding_ipv4: "10.5.107.1"
ipam:
config:
#the subnet of the bridge network in CIDR format
#should be exactly the same as the network configuration of network interface
#attached to the bridge
- subnet: 10.5.107.0/24
#service network, attached to the network interface on
#Docker host facing the bmc network
svcnet:
driver: "bridge"
driver_opts:
#the network bridge name created on the Docker host
com.docker.network.bridge.name: "svcbr"
#com.docker.network.bridge.host_binding_ipv4: "192.168.0.1"
ipam:
config:
#the subnet of the bridge network in CIDR format
#should be exactly the same as the network configuration of network interface
#attached to the bridge
- subnet: 192.160.0.0/24