[Bug 225169] New Port: net-mgmt/prometheus2: Systems monitoring and alerting toolkit

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225169

--- Comment #7 from David O'Rourke <dor.bsd at xm0.uk> ---
My current plans here are:

 - Set PORTNAME=prometheus
 - Change things in this port so that it takes over all of the `prometheus_`
rcconf variables.
 - Set rcconf defaults to `prometheus` variants of what they are currently.
 - The init script for this port will check the $prometheus_data_dir that is
set, and if it finds a `VERSION` file containing `1`, it will exit with an
error status and without starting Prometheus.
   This should ensure that Prometheus 2 doesn't do anything to endanger the
historical Prometheus 1 data, and allows the user to either move the directory
out of the way, if they wish to perform the "migration", or simply delete it if
they don't care.

On the Prometheus 1 side:

 - Set PORTNAME=prometheus1
 - Move rcconf variables to `prometheus1_`.
 - Set defaults for rcconf variables to `prometheus1` variants of what ever
they're currently set to.
 - Add a pkg-message to prometheus1 explaining a little about the migration,
the rcconf variable name changes and moving configs/directories around if
needed.

Both ports should receive some pkg-message information:
 - Pointing to the main Prometheus migration documentation.
 - Explain the FreeBSD specific steps.

The flow for upgrading here for a user that DID NOT want to upgrade to
Prometheus 2 yet should look like the following:

 a) They read ahead of time what was happening and simply didn't upgrade the
prometheus package.
 b) They upgraded and attempted to restart prometheus, it's fine because the
init script refused to start Prometheus 2 with an old data directory.
 c) Ahead of time, they read what was happening, and prepare themselves to move
to the prometheus1 package.

Users wishing to upgrade to Prometheus 2 and "migrate":
 - Upgrade and see that prometheus won't restart because of the data dir
checking. They should refer to pkg-message instructions on upgrading, install
prometheus1 package, move rcconf variables over, etc.

Users withing to upgrade to Prometheus 2 and not "migrate" (they want to lose
old data):
 - Update, see that Prometheus won't start, delete and recreate data dir, start
Prometheus.

-- 
You are receiving this mail because:
You are the assignee for the bug.