Systemd units to start and stop containers
- Revising files hierarchy
Systemd units to start and stop containers
Systemd unit to start and stop Docker containers
Let's take a shorcut.
Adding to this sprint.
As said in T579, we have two approach:
To be coherent with D102, files should be in roles/paas/docker/systemd-unit/files/
Plugins we use:
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
We've rebooted yesterday Dwellers as part of the /dev/sdb1 migration for T600.
Live at http://status.nasqueron.org/.
Part 1 - Reclaim /dev/sdb1
Container launched, web server is listening at port 39080.
DNS configuration
Besides Cachet, we also have another solution: http://staytus.co/
Batch added relevant MQ tasks to new Message queues project.
Batch added relevant MQ tasks to new Message queues project.
Batch added relevant MQ tasks to new Message queues project.
We've redeployed RabbitMQ with more network ports open and STOMP / MQTT / management plugins enabled.
I'm not sure at all that Sandstorm fit well with nasqueron way of thinking
Container launched on Dwellers for white-rabbit.nasqueron.org ActiveMQ broker, see P130.
Let's go for a test drive of RabbitMQ.
Plugins exist for RabbitMQ:
To play safe, we should also remap DevCentral as devcentral_ instead of phabricator_. A separate task has been filed for that, T563.
Operations log