Ticket #1352 (closed feature request: fixed)

Opened 6 months ago

Last modified 5 months ago

Datagard should have a command for installing and upgrading components

Reported by: bergie Assigned to: jval
Priority: critical Milestone: 8.09.6 Ragnaroek
Component: Midgard Data Version: 8.09 Ragnaroek
Keywords: Cc:

Description

Currently new components are installed using the PEAR command. However, this means that server administrators often forget to perform the important post-installation operations:

  • Database update
  • Apache stop/start
  • MidCOM cache invalidate

If we had a datagard command for component installation these could be done nicely and automatically.

Change History

09/21/09 15:23:02 changed by jval

<jval> Piotras: syntax for #1352 would perhaps be like this: datagard -a pear -p midcom_helper_search

<Piotras> jval: exactly :)

09/21/09 17:58:21 changed by jval

(In [23446]) Implement extra pear packages (components) install/upgrade feature, refs #1352

09/21/09 18:18:24 changed by jval

As already noted in the first comment, the syntax for this feature is (supports multiple packages too - the important part here to notice is that the "-a pear" part is mandatory and that the package name(s) need the -p switch in front of them): datagard -a pear -p [package]...

Because this feature was added to the existing pear action, the database update is already handled properly (the pear action includes dbupdate call after the pear package installs/upgrades).

These still require attention:

  • Apache HTTP Server restart
  • MidCOM cache invalidate

09/29/09 14:31:56 changed by jval

(In [23516]) Forgot to change one appearance of arg_app_name to arg_package. Changing now. Refs #1352

09/29/09 14:46:32 changed by jval

(In [23517]) Fix datagard: This new feature broke the pear action because arguments were't handled properly. Fixed now. Refs #1352

10/06/09 13:57:48 changed by piotras

  • status changed from new to closed.
  • resolution set to fixed.

Fixed in r23544

10/06/09 14:34:37 changed by jval

  • status changed from closed to reopened.
  • resolution deleted.

<bergie> jval: after new components you need to refresh at least the manifest cache

<jval> bergie: so 1352 should be reopened?

<bergie> if it doesn't invalidate midcom PHP cache, yes

<Piotras> jval: maybe just rm -rf /var/cache/midgard/midcom/* ?

<jval> bergie: unless you tell us something else should be done instead, that's going to be the solution :)

<bergie> jval: that is OK

10/06/09 14:38:29 changed by jval

MIDGARD_SETUP_DIRECTORY_VAR."/cache/midgard/midcom" seems to be the actual path we should use.

10/06/09 15:15:19 changed by jval

  • owner changed from piotras to jval.
  • status changed from reopened to new.

10/06/09 15:15:58 changed by jval

  • status changed from new to assigned.

10/06/09 15:29:54 changed by jval

  • status changed from assigned to closed.
  • resolution set to fixed.

(In [23547]) Remove MidCOM caches during install/upgrade/pear actions (where MidCOM packages are concerned), fixes #1352