Infrastructure has three standard "setups" adds to a "basic server setup".
general-use server (bare metal or virtual hosts)
private cloud node (bare metal hosts)
DFSc node (bare metal hosts)
dedicated services-of-things (virtual hosts)
odyssey database service (was co-managed with Steve W, MFCF?)
Do we still need weekly meetings (Dave)
one more next week then switch to alternate weeks which will have the linux then saltstack group meetings alternating.
Discussion of gitfs versus git submodules (Nathan)
gitfs is built-in to saltstack and does auto-pulls however versioning/commits isn't handle well
git submodules is good at versioning and only pulls by command however doesn't include using/pulling just a subdirectory
We can allow developers can use either! The production saltstack master administrator can update submodule setup "formulae" from git (noting auto-update of gitfs formulae).
SaltStack master versions (back porting of 20.04 use of PPA stable to 18.04) (Dave)
guideline will be that "new" os distro deployments will be setup to use the StaltStack stable ppa.
As new LTS releases come out we'll review this guideline.
Moving a service (ie: rebuild minion on latest LTS production release) (Nathan)
step 1: Inventory the minions creating what,why and who-admins documentation.
step 2: check/update SaltStack master to have any missing formulae.
step 3: demo rebuild of service host from scratch.
Information in this area is meant for use by CSCF staff and is not official documentation, but anybody who is interested is welcome to use it if they find it useful.