Skip to content
This repository has been archived by the owner on Jan 23, 2020. It is now read-only.

Add dependencies for init.d scripts #73

Closed
wants to merge 2 commits into from
Closed

Conversation

Mayeu
Copy link

@Mayeu Mayeu commented Dec 2, 2013

The init.d scripts lacks dependencies on redis-sever and rabbitmq-server
(not all of them need them both). This dependancies lacking may prevent
some Sensu service to start when the machine is rebooted.

The init.d scripts lacks dependencies on redis-sever and rabbitmq-server
(not all of them need them both). This dependancies lacking may prevent
some Sensu service to start when the machine is rebooted.
@portertech
Copy link
Contributor

Usually not on the same box.

@portertech portertech closed this Dec 19, 2013
@Mayeu
Copy link
Author

Mayeu commented Dec 20, 2013

Thank you for your response.
Please note that I have updated the files to use "Should-{Start, Stop}" instead of "Require", thus allowing weak dependancies (but for an unknown reasons it does not appear in this pull request, maybe because it is closed ?).

If your rejection was not about the strong/weak dependancy, see my reasons for those commits:

  1. When you test a new software you do not start by testing it with complex multi-server configuration, but with only a simple one server configuration. This issue will arise at the first reboot test the user will made, and when a monotoring software does not restart by itself on the first reboot, its not interpreted as a good sign for the user.

  2. The documentation define the default architecture with a monitor box containning all pieces of software (http://sensuapp.org/docs/0.12/guide).

  3. The Sensu powered Chef and Puppets module define everything on the same host by default (localhost in this case), which is good for testing, but see 1).

  4. A small organization/network will not bother or will not have de capacity to seperate the Sensu installation on multiple server.

Regards.

@portertech portertech reopened this Dec 20, 2013
@portertech
Copy link
Contributor

The Sensu Server and API also depend on RabbitMQ. Should-* does define the weak dependency, however, what if there is a local RabbitMQ or Redis installation that shouldn't be started, unrelated to Sensu? What if a user build Redis from source, using an uncommon method of service management or supervision? I've been pushing this responsibility to configuration management or service supervisors. Still on the fence.

@portertech
Copy link
Contributor

Going to close this. Sensu now supports multiple transports and may soon support other data stores.

@portertech portertech closed this Apr 28, 2015
@Mayeu
Copy link
Author

Mayeu commented Apr 30, 2015

Going to close this. Sensu now supports multiple transports and may soon support other data stores.

Cool! I totally missed that fact!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants