FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Merge pull request #37 from jpwhitemn/master · Huijiny/developer-scripts@f6045cb · GitHub

Commit f6045cb

Browse files
authored
Merge pull request edgexfoundry#37 from jpwhitemn/master
Docker compose files for releases, development, etc. and organization of same into folder
2 parents 596640d + 2d5c7e0 commit f6045cb

5 files changed

Lines changed: 656 additions & 5 deletions

File tree

‎compose-files/README.md‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# last updated: 12/15/2017
2+
3+
## Docker Compose Files
4+
This folder contains Docker Compose files for the following releases and usages:
5+
* docker-compose-barcelona-0.2.0.yml: This file uses the EdgeX **Barcelona release 0.2.0** container images. See Note 1
6+
* docker-compose-barcelona-0.2.1.yml: This file uses the EdgeX **Barcelona release 0.2.1** container images. Release 0.2.1 was a bug fix release to version 0.2.0. See Note 2
7+
* docker-compose.yml: This file uses the latest EdgeX container images from Docker Hub. This should be considered the EdgeX **developer's latest usable container images**.
8+
* docker-compose-nexus.yml: This file uses the latest EdgeX container images from the EdgeX Nexus repository (**developer working images**) managed by the Linux Foundation. See Note 3
9+
10+
## Notes
11+
1. The Barcelona 0.2 release of EdgeX has an issue whereby the health check address for each of the microservices was not set correctly. The release will still run and perform its duties, but Consul will not be able to apprpriately know the status of all the services.
12+
2. Some of the 0.2.1 release containers did not require a fix and are left at version 0.2.0
13+
3. These are the latest pre-release, developer build, containers and should only be used by developers that need the absolute latest container images as built by the continous integration process. NOTE: using this Docker Compose will require you have access to the EdgeX Nexus repository. See https://wiki.edgexfoundry.org/display/FA/Getting+Docker+Images+from+EdgeX+Nexus+Repository
14+
4. Note that all the Docker Compose files have device service elements that have all been commented out (except for the device-virtual). Uncomment the sections for the device services you need.
15+
16+
## Donations
17+
Other members of the community that are creating unique, updated or special EdgeX deployments are invited to add their Docker Compose files to this folder. When contributing, please use the following naming conventions:
18+
docker-compose-[release name or organization]-[purpose if applicable]-[version if applicable].yml
19+
20+
For example:
21+
* docker-compose-dell-WithDellUIs.yml
22+
* docker-compose-samsung-smartfactory-1.1.yml
23+
Lines changed: 298 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,298 @@
1+
# /*******************************************************************************
2+
# * Copyright 2017 Dell Inc.
3+
# *
4+
# * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
5+
# * in compliance with the License. You may obtain a copy of the License at
6+
# *
7+
# * http://www.apache.org/licenses/LICENSE-2.0
8+
# *
9+
# * Unless required by applicable law or agreed to in writing, software distributed under the License
10+
# * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
11+
# * or implied. See the License for the specific language governing permissions and limitations under
12+
# * the License.
13+
# *
14+
# * @author: Jim White, Dell
15+
# * EdgeX Foundry, Barcelona Release, version 0.2.0
16+
# *******************************************************************************/
17+
18+
version: '2'
19+
services:
20+
volume:
21+
image: edgexfoundry/docker-edgex-volume:0.2
22+
container_name: edgex-files
23+
networks:
24+
- edgex-network
25+
volumes:
26+
- /data/db
27+
- /edgex/logs
28+
- /consul/config
29+
- /consul/data
30+
31+
config-seed:
32+
image: edgexfoundry/docker-core-config-seed:0.2
33+
ports:
34+
- "8300:8300"
35+
- "8400:8400"
36+
- "8500:8500"
37+
- "8600:8600"
38+
container_name: edgex-config-seed
39+
hostname: edgex-core-consul
40+
networks:
41+
edgex-network:
42+
aliases:
43+
- edgex-core-consul
44+
volumes_from:
45+
- volume
46+
depends_on:
47+
- volume
48+
49+
mongo:
50+
image: edgexfoundry/docker-edgex-mongo:0.2
51+
ports:
52+
- "27017:27017"
53+
container_name: edgex-mongo
54+
hostname: edgex-mongo
55+
networks:
56+
- edgex-network
57+
volumes_from:
58+
- volume
59+
depends_on:
60+
- volume
61+
62+
logging:
63+
image: edgexfoundry/docker-support-logging:0.2
64+
ports:
65+
- "48061:48061"
66+
container_name: edgex-support-logging
67+
hostname: edgex-support-logging
68+
networks:
69+
- edgex-network
70+
volumes_from:
71+
- volume
72+
depends_on:
73+
- volume
74+
- config-seed
75+
- mongo
76+
77+
notifications:
78+
image: edgexfoundry/docker-support-notifications:0.2
79+
ports:
80+
- "48060:48060"
81+
container_name: edgex-support-notifications
82+
hostname: edgex-support-notifications
83+
networks:
84+
- edgex-network
85+
volumes_from:
86+
- volume
87+
depends_on:
88+
- logging
89+
90+
metadata:
91+
image: edgexfoundry/docker-core-metadata:0.2
92+
ports:
93+
- "48081:48081"
94+
container_name: edgex-core-metadata
95+
hostname: edgex-core-metadata
96+
networks:
97+
- edgex-network
98+
volumes_from:
99+
- volume
100+
depends_on:
101+
- logging
102+
103+
data:
104+
image: edgexfoundry/docker-core-data:0.2
105+
ports:
106+
- "48080:48080"
107+
- "5563"
108+
container_name: edgex-core-data
109+
hostname: edgex-core-data
110+
networks:
111+
- edgex-network
112+
volumes_from:
113+
- volume
114+
depends_on:
115+
- logging
116+
117+
command:
118+
image: edgexfoundry/docker-core-command:0.2
119+
ports:
120+
- "48082:48082"
121+
container_name: edgex-core-command
122+
hostname: edgex-core-command
123+
networks:
124+
- edgex-network
125+
volumes_from:
126+
- volume
127+
depends_on:
128+
- metadata
129+
130+
## scheduler container does not come up on Consul - bug fix in the works.
131+
scheduler:
132+
image: edgexfoundry/docker-support-scheduler:0.2
133+
ports:
134+
- "48085:48085"
135+
container_name: edgex-support-scheduler
136+
hostname: edgex-support-scheduler
137+
networks:
138+
- edgex-network
139+
volumes_from:
140+
- volume
141+
depends_on:
142+
- metadata
143+
144+
export-client:
145+
image: edgexfoundry/docker-export-client:0.2
146+
ports:
147+
- "48071:48071"
148+
container_name: edgex-export-client
149+
hostname: edgex-export-client
150+
networks:
151+
- edgex-network
152+
volumes_from:
153+
- volume
154+
depends_on:
155+
- data
156+
157+
export-distro:
158+
image: edgexfoundry/docker-export-distro:0.2
159+
ports:
160+
- "48070:48070"
161+
- "5566"
162+
container_name: edgex-export-distro
163+
hostname: edgex-export-distro
164+
networks:
165+
- edgex-network
166+
volumes_from:
167+
- volume
168+
depends_on:
169+
- export-client
170+
171+
rulesengine:
172+
image: edgexfoundry/docker-support-rulesengine:0.2
173+
ports:
174+
- "48075:48075"
175+
container_name: edgex-support-rulesengine
176+
hostname: edgex-support-rulesengine
177+
networks:
178+
- edgex-network
179+
volumes_from:
180+
- volume
181+
depends_on:
182+
- export-distro
183+
184+
#################################################################
185+
# Device Services
186+
#################################################################
187+
188+
device-virtual:
189+
image: edgexfoundry/docker-device-virtual:0.2
190+
ports:
191+
- "49990:49990"
192+
container_name: edgex-device-virtual
193+
hostname: edgex-device-virtual
194+
networks:
195+
- edgex-network
196+
volumes_from:
197+
- volume
198+
depends_on:
199+
- data
200+
- command
201+
202+
# device-bluetooth:
203+
# image: edgexfoundry/docker-device-bluetooth:0.2
204+
# ports:
205+
# - "49988:49988"
206+
# - "5000:5000"
207+
# container_name: edgex-device-bluetooth
208+
# hostname: edgex-device-bluetooth
209+
# privileged: true
210+
# network_mode: "host"
211+
# cap_add:
212+
# - NET_ADMIN
213+
# # networks:
214+
# # - edgex-network
215+
# volumes_from:
216+
# - volume
217+
# depends_on:
218+
# - data
219+
# - command
220+
221+
# device-snmp:
222+
# image: edgexfoundry/docker-device-snmp:0.2
223+
# ports:
224+
# - "49989:49989"
225+
# container_name: edgex-device-snmp
226+
# hostname: edgex-device-snmp
227+
# networks:
228+
# - edgex-network
229+
# volumes_from:
230+
# - volume
231+
# depends_on:
232+
# - data
233+
# - command
234+
235+
# device-modbus:
236+
# image: edgexfoundry/docker-device-modbus:0.2
237+
# ports:
238+
# - "49991:49991"
239+
# container_name: edgex-device-modbus
240+
# networks:
241+
# - edgex-network
242+
# volumes_from:
243+
# - volume
244+
# privileged: true
245+
# depends_on:
246+
# - data
247+
# - command
248+
249+
# device-fischertechnik:
250+
# image: edgexfoundry/docker-device-fischertechnik:0.2
251+
# ports:
252+
# - "49985:49985"
253+
# container_name: edgex-device-fischertechnik
254+
# networks:
255+
# - edgex-network
256+
# volumes_from:
257+
# - volume
258+
# privileged: true
259+
# depends_on:
260+
# - data
261+
# - command
262+
263+
# device-bacnet:
264+
# image: edgexfoundry/docker-device-bacnet:0.2
265+
# ports:
266+
# - "49986:49986"
267+
# - "5002:5002"
268+
# container_name: edgex-device-bacnet
269+
# hostname: edgex-device-bacnet
270+
# networks:
271+
# - edgex-network
272+
# volumes_from:
273+
# - volume
274+
# depends_on:
275+
# - data
276+
# - command
277+
278+
# device-mqtt:
279+
# image: edgexfoundry/docker-device-mqtt:0.2
280+
# ports:
281+
# - "49982:49982"
282+
# - "14377:14377"
283+
# container_name: edgex-device-mqtt
284+
# hostname: edgex-device-mqtt
285+
# networks:
286+
# - edgex-network
287+
# volumes_from:
288+
# - volume
289+
# depends_on:
290+
# - data
291+
# - command
292+
293+
networks:
294+
edgex-network:
295+
driver: "bridge"
296+
...
297+
298+

0 commit comments

Comments
 (0)

Back | FazBrowse Home | New Git URL