Consolidation recent works occurred at T1828 to further unify nginx configurations.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 12 2024
Jun 29 2023
May 18 2023
Mar 24 2023
⚠ It's been experimentally manually configured on WindRiver through zfs-auto-snapshot.
Mar 3 2023
We migrated from Zemke-Rhyne to Vault for credentials management.
Sep 12 2021
Feb 14 2020
Hypervisor configuration is now fine.
Feb 6 2020
Jan 24 2020
Jan 14 2020
We need this, tools is currently down.
We can mark this resolved, as the scope was to prepare the devserver role on ops repo.
Dec 5 2019
Nov 22 2019
Actually, there is now a port: https://www.freshports.org/shells/starship/
As Ysul will be superseded by Windriver, this task will need to be reevaluated.
Oct 22 2019
I've run again install-eggdrop with DEST at /opt/eggdrop in environment, per Salt viperserv role configuration.
Oct 21 2019
Sep 15 2019
Feb 15 2019
Jan 26 2019
DNS configuration
DNS delegation done.
Jan 25 2019
DNS delegation issues.
Ordered at OVH. BC 101687018.
Ordering domain name nasqueron-user-content.org
Dec 26 2018
Dec 13 2018
Nov 15 2018
Reducing a little bit the priority, all works fine with the current config, and each is correctly documented.
On another Salt configuration, Woods Cloud, where I'm going to reuse some blocks initially prepared from Nasqueron rOPS, I'm picking 9002as it's the same than the UID.
Nov 11 2018
Nov 10 2018
A GRE tunnel between Equatower and Dwellers have been prepared while Dwellers isn't connected to IntraNought, so we can push to Equatower Docker registry from Dwellers.
Nov 9 2018
Nov 4 2018
New containers roadmap is to wait Fedora CoreOS or a RHEL downstream before to provision and keep CentOS meanwhile.
Plan is to move nasquenautes to 3005 as not currently deployed (mediawiki is)
Migrating existing home directories
zfs allow isn't currently available in salt.states.zfs, and it's not really a problem to run again the permission command, so probably a cmd.run with require state to the ZFS create dataset operation.
$ zfs allow -s @local allow,clone,create,diff,hold,mount,promote,receive,release,rollback,snapshot,send arcology/usr/home $ zfs allow -s @descendent allow,clone,create,diff,destroy,hold,mount,promote,receive,release,rename,rollback,snapshot,send arcology/usr/home
Oct 30 2018
Also tested it's not an open relay: