Prioritize white-rabbit in containers startup sequence
ClosedPublic
Actions

Authored by dereckson on Dec 29 2015, 14:13.

Tags

None

Referenced Files

	Unknown Object (File)
	Thu, May 22, 10:22

	Unknown Object (File)
	Sun, May 18, 05:43

	Unknown Object (File)
	Sat, May 17, 22:16

	Unknown Object (File)
	Fri, May 16, 22:36

	Unknown Object (File)
	Fri, May 16, 17:47

	Unknown Object (File)
	Thu, May 15, 23:24

	Unknown Object (File)
	Wed, May 14, 12:35

	Unknown Object (File)
	May 3 2025, 13:55

View All Files

Subscribers

None

Details

Reviewers

Sandlayth

Commits

rOPS32a96daa004f: Prioritize white-rabbit in containers startup sequence

Summary

Our message broker is a key piece of infrastructure for notifications
and should be started before any other container could need it, which
is currently the case of the Phabricator containers.

Test Plan

no op

Diff Detail

Repository

rOPS Nasqueron Operations

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

dereckson updated this revision to Diff 310.Dec 29 2015, 14:13

dereckson retitled this revision from to Prioritize white-rabbit in containers startup sequence.

dereckson updated this object.

dereckson edited the test plan for this revision. (Show Details)

dereckson added a reviewer: Sandlayth.

Sandlayth accepted this revision.Dec 29 2015, 19:42

Sandlayth edited edge metadata.

This revision is now accepted and ready to land.Dec 29 2015, 19:42

Closed by commit rOPS32a96daa004f: Prioritize white-rabbit in containers startup sequence (authored by dereckson, committed by dereckson). · Explain WhyDec 29 2015, 20:02

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

Path

Size

paas/

docker/

systemd-unit/

files/

containers.conf

4 lines

Diff 322

View Options

paas/docker/systemd-unit/files/containers.conf

Prioritize white-rabbit in containers startup sequenceClosedPublicActions