opendev/system-config
Code Issues Proposed changes
aedd023738
system-config/playbooks/roles/nodepool-builder/templates/docker-compose.yaml.j2

37 lines
1.2 KiB
Plaintext
Raw Normal View History

Drop version specifier for nodepool-builder compose We don't actually need version 3. Mark it as version 2 to keep it inline with everything else. In general we should only increase past v2 if we need a specific feature. Change-Id: Ie243da369ddec30e0eca4805434d572e12c40491
2020-03-17 13:11:25 -05:00
version: '2'
nodepool-builder: add volume for /var/lib/containers podman, used by the new containerfile element, requires a non-overlayfs volume at /var/lib/containers to be able to start and extract the container images for us to build from. Add a separate volume for this. Change-Id: I6629034ad0b300d392d3d989dbbf17a1343c06e1
2021-06-10 08:39:28 +10:00
nodepool-builder: deploy from container This deploys the nodepool-builder container and verifies it has started in testinfra. Change-Id: I8a717d06f1291a4112b2753641ff88f074cf0b31
2020-03-03 12:30:20 +11:00
services:
nodepool-builder:
image: docker.io/zuul/nodepool-builder:{{ nodepool_builder_container_tag|default('latest') }}
user: nodepool
network_mode: host
restart: always
Set stop_grace_period on nodepool-builder containers By default docker-compose sends a sigterm to containers when they are stopping. It then waitsfor 10 seconds before sending a sigkill. Our nodepool-builder containers are restarted when new images are available and if that happens during a dib build we leak contents into dib_tmp. One theory is that we aren't giving dib enough time to clean up after itself so increase the 10 second period before sending sigkill to 90 seconds. I'm not sure if this will actually help, but it can't hurt much. If the processes die quicker we don't go any slower and if they don't die quicker then we're giving them more time to clean up. Change-Id: Id12cac89cccfc14a8d262e8f8494046df777a80a
2021-01-21 15:12:15 -08:00
stop_grace_period: 90s
nodepool-builder: configure upload workers, reduce nb03 Add a variable to configure upload-workers for nodepool-builder daemons. Reduce our defaults for nb03 to see if we can get more reliable uploads. Change-Id: I819bdd262c7118cbde4e6ffdc12aa3ac64569a96
2021-04-15 09:09:04 +10:00
command: nodepool-builder -f -c /etc/nodepool/nodepool.yaml -l /etc/nodepool/builder-logging.conf --upload-workers {{ nodepool_builder_upload_workers }}
nodepool-builder: deploy from container This deploys the nodepool-builder container and verifies it has started in testinfra. Change-Id: I8a717d06f1291a4112b2753641ff88f074cf0b31
2020-03-03 12:30:20 +11:00
privileged: true
environment:
- DEBUG=1
Run nodepool launchers with ansible and containers We don't run start in prod normally but we do need to run it in the gate. Change-Id: Iec50684280409eb978bf5638bf74ae16fad8aa26
2020-04-16 10:18:51 -05:00
- STATSD_HOST=graphite.opendev.org
- STATSD_PORT=8125
nodepool-builder: deploy from container This deploys the nodepool-builder container and verifies it has started in testinfra. Change-Id: I8a717d06f1291a4112b2753641ff88f074cf0b31
2020-03-03 12:30:20 +11:00
volumes:
# nodepool config
- /etc/nodepool:/etc/nodepool:ro
nodepool-builder: put container configs in /etc Currently we deploy the openstacksdk config into ~nodepool/.config on the container, and then map this directory back to /etc/openstack in the docker-compose. The config-file still hard-codes the limestone.pem file to ~nodepool/.config. Switch the nodepool-builder_opendev group to install to /etc/openstack, and update the nodepool config file template to use the configured directory for the .pem path. Also update the testing paths. Story: #2007407 Task: #39015 Change-Id: I9ca77927046e2b2e3cee9a642d0bc566e3871515
2020-03-16 10:01:14 +11:00
# openstacksdk config
- /etc/openstack:/etc/openstack:ro
nodepool-builder: deploy from container This deploys the nodepool-builder container and verifies it has started in testinfra. Change-Id: I8a717d06f1291a4112b2753641ff88f074cf0b31
2020-03-03 12:30:20 +11:00
# project-config
- /opt/project-config:/opt/project-config:ro
# dib temporary storage; see config in project-config
- /opt/dib_tmp:/opt/dib_tmp:rw
nodepool-builder: add /opt/dib_cache This was missing but is part of the required runtime directories for the container (for now, until we maybe move all this to volumes). Change-Id: I9e173eb799026520588722caaf60a160abc6b130
2020-03-13 13:21:35 +11:00
# dib cache; see config in project-config
- /opt/dib_cache:/opt/dib_cache:rw
nodepool-builder: deploy from container This deploys the nodepool-builder container and verifies it has started in testinfra. Change-Id: I8a717d06f1291a4112b2753641ff88f074cf0b31
2020-03-03 12:30:20 +11:00
# dib image output; see config in project-config
- /opt/nodepool_dib:/opt/nodepool_dib:rw
# logs (builder + dib build logs under /build)
nodepool-builder: put container configs in /etc Currently we deploy the openstacksdk config into ~nodepool/.config on the container, and then map this directory back to /etc/openstack in the docker-compose. The config-file still hard-codes the limestone.pem file to ~nodepool/.config. Switch the nodepool-builder_opendev group to install to /etc/openstack, and update the nodepool config file template to use the configured directory for the .pem path. Also update the testing paths. Story: #2007407 Task: #39015 Change-Id: I9ca77927046e2b2e3cee9a642d0bc566e3871515
2020-03-16 10:01:14 +11:00
- /var/log/nodepool:/var/log/nodepool:rw
nodepool-builder: add volume for /var/lib/containers podman, used by the new containerfile element, requires a non-overlayfs volume at /var/lib/containers to be able to start and extract the container images for us to build from. Add a separate volume for this. Change-Id: I6629034ad0b300d392d3d989dbbf17a1343c06e1
2021-06-10 08:39:28 +10:00
# for the containerfile element/podman; it needs a non-overlayfs
# mounted here.
- /opt/dib_containers:/var/lib/containers
Copy Permalink