Integrate w/ DRD [#2555359]

Drupal Remote Dashboard appears to provide a tonne of useful insight into the health of monitored sites. In #1477258: Aegir Support? , it appears that Aegir shouldn't conflict with the DRD setup. I'm concerned about security, as a quick scan of that issue appears to discuss pulling DB creds out of sites' settings.php. That said, that could be functionality we could circumvent via Aegir's existing tooling. It looks like a key needs to be injected into settings.php to secure connections between the server and dashboard.

Comments

Comment #1

21 August 2015 at 13:10

ergonlogic created an issue. See original summary.

Comment #2

daften CreditAttribution: daften at Picabit commented 21 August 2015 at 15:15

This seems like an excellent idea as a contrib module, not in core.
But the way DRD works right now is that each site needs the drd_server module, because that site itself can only deliver the data. I'm curious in how this could be circumvented from aegir itself.

Comment #3

ergonlogic

he/him

English

Montréal, Québec 🇨🇦

CreditAttribution: ergonlogic commented 21 August 2015 at 16:09

Right, this should definitely be in contrib, but we could eventually pull it into the distribution via 'golden contrib'. Once it's stabilized, and proven its worth, of course.

I think requiring drd_server on the site is a reasonable requirement. That's how we provide a link to phpmyadmin in https://www.drupal.org/project/hosting_dblogin. It's not ideal, of course, but it would allow for an opt-in/opt-out mechanism from within the site itself, which isn't necessarily a bad idea.

An alternative would be to poll for this data as a backend task. This would also remove the need for a shared key, etc. I haven't really looked at how DRD is architected yet, so I don't know how easy or hard it'd be to do something like that. That said, this looks promising:

drush @drd drd-action drd.list.updates --filter-status=1

This is described as:

... looking into all domains on all cores and collects the latest data about available updates of Drupal core, modules and themes. Those details can then be looked at in an aggregated format when going to http://www.example.com/admin/drd/modules where you can see all components for all your Drupal sites in your entire network.

Now this might just be triggering an update via the front-end, in which case it doesn't help us much. Something worth investigating though...