Date: Thu, 01 Feb 2018 20:57:21 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 225169] New Port: net-mgmt/prometheus2: Systems monitoring and alerting toolkit Message-ID: <bug-225169-13-3k3stBYsaC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-225169-13@https.bugs.freebsd.org/bugzilla/> References: <bug-225169-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225169 --- Comment #7 from David O'Rourke <dor.bsd@xm0.uk> --- My current plans here are: - Set PORTNAME=3Dprometheus - 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 direct= ory out of the way, if they wish to perform the "migration", or simply delete i= t if they don't care. On the Prometheus 1 side: - Set PORTNAME=3Dprometheus1 - 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, insta= ll prometheus1 package, move rcconf variables over, etc. Users withing to upgrade to Prometheus 2 and not "migrate" (they want to lo= se old data): - Update, see that Prometheus won't start, delete and recreate data dir, s= tart Prometheus. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225169-13-3k3stBYsaC>