Add monitoring for the deployed version for all site repos

[bhazelton]

Particularly the correlator, but also all other repos installed on site. Probably want columns for machine name, environment name, repository name along with the standard git info (hash, branch, upstream etc).

[dannyjacobs]

We really need this. Currently running hera_corr_f on a hacky branch to shim up the hacked fengine.
Can we make a table in M&C that tracks host, repo, path, checked out branch, hash. Imagining a really simple script that runs on each machine given a local list of repos.

[bhazelton]

Ok, so does this table schema seem right? The starred columns are part of the primary key. I guess one question is: do we ever have 2 copies of a repo on a host that we want to use? If so, the path needs to be part of the primary key. Also, is there anything else we should record? Environment comes to mind, but not sure how to get that reliably.

*host
*repo
*starttime
stoptime
path
upstream
branch
hash

@dannyjacobs @plaplant @mkolopanis @david-deboer

[mkolopanis]

What about environment as a (primary?) key value. It would be a string point to the base level of the environment. Could easily track conda, virtual env, even system level that wau.

…

On Tue, Aug 25, 2020, 16:09 Bryna Hazelton ***@***.***> wrote: Ok, so does this table schema seem right? The starred columns are part of the primary key. I guess the question is: do we ever have 2 copies of a repo on a host that we want to use? If so, the path needs to be part of the primary key. *host *repo *starttime stoptime path branch hash @dannyjacobs <https://github.com/dannyjacobs> @plaplant <https://github.com/plaplant> @mkolopanis <https://github.com/mkolopanis> @david-deboer <https://github.com/david-deboer> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#491 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACB7BLLGEPAHADXVHK5DJMLSCRADTANCNFSM4OHEEXCA> .

[mkolopanis]

Or is that path? On Tue, Aug 25, 2020, 16:14 Matthew Kolopanis <[email protected]> wrote:

…

What about environment as a (primary?) key value. It would be a string point to the base level of the environment. Could easily track conda, virtual env, even system level that wau. On Tue, Aug 25, 2020, 16:09 Bryna Hazelton ***@***.***> wrote: > Ok, so does this table schema seem right? The starred columns are part of > the primary key. I guess the question is: do we ever have 2 copies of a > repo on a host that we want to use? If so, the path needs to be part of the > primary key. > > *host > *repo > *starttime > stoptime > path > branch > hash > > @dannyjacobs <https://github.com/dannyjacobs> @plaplant > <https://github.com/plaplant> @mkolopanis <https://github.com/mkolopanis> > @david-deboer <https://github.com/david-deboer> > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#491 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACB7BLLGEPAHADXVHK5DJMLSCRADTANCNFSM4OHEEXCA> > . >

[bhazelton]

input info -- should live as a text or yaml file in hera_ops:
host
package
environment
path

M&C table:
*host: string
*package: string
*starttime: gps second
*environment: string
stoptime: gps second
installed_version: string
installed_branch: string
installed_hash: string
local_path: string
local_remote: string
local_branch: string
local_hash: string