New pages
From Nasqueron Agora
28 October 2025
- 19:5819:58, 28 October 2025 Registries (hist | edit) [896 bytes] Dereckson (talk | contribs) (Created page with "== Object identifiers (OID) == Nasqueron uses the Private Enterprise Number (PEN) '''60024'''. Operations grimoire/OID is our object identifiers registry for 1.3.6.1.4.1.60024 hierarchy == Tags == RFC 4151 tags are defined for the following purposes: * YAML tags === As YAML tags === Tags from the Keruald project are defined using keruald.nasqueron.org domain. {| class="wikitable" |+ Keruald YAML tags |- ! Tag !! Short notation !! Purpose |- | tag:keruald.n...")
- 01:1401:14, 28 October 2025 Dereckson pad/English (hist | edit) [4,154 bytes] Dereckson (talk | contribs) (After proofreading with GPT 4, I got the idea to ask for a grammar memento)
- 00:4800:48, 28 October 2025 Operations grimoire/OID (hist | edit) [1,070 bytes] Dereckson (talk | contribs) (Created page with "Nasqueron OID registry starts at 1.3.6.1.4.1.60024. == OID entries == * 1.3.6.1.4.1.60024 {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nasqueron(60024)} ** 1.3.6.1.4.1.60024.1 Nasqueron LDAP *** 1.3.6.1.4.1.60024.1.1 LDAP objectclasses **** 1.3.6.1.4.1.60024.1.1.1 ''Reserved for nasquenaute class''<ref group="Note">If custom attributes specific to the Nasqueron project are needed, the plan is to define them in a class that extends 1.3....")
- 00:3700:37, 28 October 2025 Operations grimoire/LDAP (hist | edit) [1,052 bytes] Dereckson (talk | contribs) (Created page with "This page discusses future LDAP implementation. == Goals == * Foundation of a SSO, source of truth for internal credentials, especially if we use Keycloak * Allow applications to check credentials == Products to evaluate == * 389 Directory Server * OpenLDAP * directly slapd == Schema == The page wolfplex:OID defines a class inetWolf, to add properties in addition to inetOrgPerson class. We can follow that schema. If we need to define custom LDAP elements, we c...")
25 October 2025
- 15:2915:29, 25 October 2025 ServPulse/Note of Intent (hist | edit) [5,313 bytes] Dereckson (talk | contribs) (Created page with "== Foreword == When a service is down or degraded, it's important to communicate efficiently with all the involved parties - Nasqueron members, visitors using our sites, Nasqueron operations SIG - about the status, what we know, what we do. Cachet gave us satisfaction for a clear status page easy to use until 2018, where development stalled. James Brooks, Cachet author, sold Cachet to a company with plans for it, plans apparently never developed as far as we could see...")
- 14:5814:58, 25 October 2025 ServPulse/Other existing solutions (hist | edit) [1,979 bytes] Dereckson (talk | contribs) (Report information gathered by GPT 5)
23 October 2025
- 23:5123:51, 23 October 2025 ServPulse/Development guide (hist | edit) [262 bytes] Dereckson (talk | contribs) (Created page with "== Axios == An example of integration between Axios and Vue: https://v2.vuejs.org/v2/cookbook/using-axios-to-consume-apis.html This example was for Vue v2, we probably want to target Vue 3.")
- 23:4623:46, 23 October 2025 ServPulse/Domain (hist | edit) [985 bytes] Dereckson (talk | contribs) (Created page with "== Lexicon == ;StatusPage :The entity representing the status page itself. :'''Attributes:''' title, description, URL ;Component :This concept represents the various components or elements being monitored on the status page, such as servers, services, applications, databases, and other relevant entities. :'''Attributes:''' name, description, status (e.g., up, down, degraded). ;Metrics :This concept represents the performance metrics or indicators being measured for ea...")
- 23:4023:40, 23 October 2025 ServPulse/Project identity (hist | edit) [1,332 bytes] Dereckson (talk | contribs) (Created page with "== Brainstorming about names == When we brainstormed about the name, it seems the orientation of the project would be more about ping/monitor/perform health check than report the status of the sites: * StatusHub * PulseMonitor * SystemTracker * ServiceWatch * HealthCheckr * SiteScope * StatusMate * OpsAlert * MonitorMe * CheckPoint A synthwave and cyberpunk inspired list: * NeonStatus * CyberPulse * SynthWatch * RetroStatus * WaveCheck * CyberScope * PulseWave * Synt...")
20 October 2025
- 23:0323:03, 20 October 2025 Monday office hours/2025-10-21 (hist | edit) [1,241 bytes] Dereckson (talk | contribs) (Created page with "Our focus was to debug DNS NOTIFY to solve {{T|2148}}. We discussed received internships candidates. We've also briefly discussed Phabricator inbound mail configuration, acme.sh logs rotation. == DNS == ; Debug session * {{T|2148}} - HE refuses our DNS NOTIFY requests ; CI validation * {{T|2149}} - idea to check diff to see if we bumped the serial (pre-commit, Jenkins) ; Next * {{T|2154}} - Better IPv6 support for ns1.nasqueron.org ; Administrative change : HE: nas...")
- 17:5417:54, 20 October 2025 Lexicon (hist | edit) [3,560 bytes] Dereckson (talk | contribs) (Created page with "This lexicon defines key terms, expressions, and internal concepts used across the Nasqueron open source project. == B == ; Bastion : A hardened entry point to connect securely to the Nasqueron infrastructure, generally via SSH. Only the bastion is exposed to the Internet; internal hosts are accessed through it. : 📖 Operations grimoire/Recommended SSH configuration == D == ; DevCentral : The name of the Phabricator/Phorge instance used at Nasqueron to coordina...")
2 October 2025
- 21:2421:24, 2 October 2025 Operations grimoire/Recommended SSH configuration (hist | edit) [1,343 bytes] Dereckson (talk | contribs) (Created page with "== Consolidated OpenSSH configuration == The introduction of ProxyJump has simplified the bastion configuration since OpenSSH version 7.5: <syntaxhighlight> Host *.nasqueron.drake ProxyJump windriver.nasqueron.org Host 172.27.27.* ProxyJump windriver.nasqueron.org </syntaxhighlight> Older version of OpenSSH can use instead: <code>ProxyCommand "ssh -W %h:%p windriver.nasqueron.org"</code> == Use bastion as proxy == To connect on a server where the port 22 i...")
25 September 2025
- 23:3523:35, 25 September 2025 Naemon (hist | edit) [4,700 bytes] Dereckson (talk | contribs) (Created page with "'''Naemon''' has been identified as a simple and maintained solution for a Nagios-compatible monitoring system. Shinken and Sensu have been dismissed as open core solutions. == Naemon deployment and FreeBSD porting plan = == Overview == To improve Nasqueron infrastructure monitoring, we propose a three-step approach using Naemon, a Nagios-compatible monitoring system. Our 2024 test showed compatibility with FreeBSD is a reasonable middle-term goal, but need a sensibl...")
24 September 2025
- 17:1517:15, 24 September 2025 Limiting Factor (hist | edit) [2,084 bytes] Dereckson (talk | contribs) (Created page with "== Development with Limiting Factor == === Axum === Gotchas during development of With axum and limiting-factor-axum: ==== Order of extractors ==== [https://docs.rs/axum/latest/axum/extract/index.html#the-order-of-extractors axum::extract order of extractors] - the request is consumed by an extractor, so it must be the LAST parameter of any request handler method. For example, to use RequestBody: <syntaxhighlight language="rust"> use limiting_factor_axum::api::guards:...")
22 September 2025
- 21:3421:34, 22 September 2025 Monday office hours/2025-09-22 (hist | edit) [1,325 bytes] Dereckson (talk | contribs) (Created page with "Our focus was to switch DNS hosting authoritative source to ns1.nasqueron.org server, and switch HE ones as secondary. == DNS == ;Infrastructure changes: * {{T|1217}}: ns1.nasqueron.org is now the primary DNS server, DNS can be managed on Git with history and review ;Code merge: * {{D|3654}}: Define nasqueron.org DNS zone * {{D|3691}}: Use @ syntax for zone apex ;Administrative changes: * '''HE:''' nasqueron.org zone managed as secondary in nasqueron DNS account * '''...")
17 September 2025
- 21:2921:29, 17 September 2025 Nasqueron Labs (hist | edit) [559 bytes] Dereckson (talk | contribs) (Created page with "== Next labs == {| class="wikitable" |+ Nasqueron Labs to come |- ! Task !! Title !! Planning date !! Organizer |- | {{T|2126}} || Authenticate CI to Vault with OIDC (Jenkins x OpenBao) || ''to determine with interested nasquenautes'' || Dereckson |}")
15 September 2025
- 23:2423:24, 15 September 2025 Operations grimoire/Services (hist | edit) [1,646 bytes] Dereckson (talk | contribs) (Created page with "== Systemd, rc and runit == Nasqueron infrastructure uses 3 services software: {| class="wikitable" |+ Service management |- ! OS !! Use case !! Software !! Commands |- | FreeBSD || Standard || rc || service <service> <command> |- | Linux || Standard || systemd || systemctl <command> <service> |- | Linux || Docker containers || runit || sv <service> <command> |} Note how systemd inverts the general order by putting the command before the service. == Systemd == === Se...")
14 September 2025
- 12:5212:52, 14 September 2025 Dev zone/Reports (hist | edit) [1,836 bytes] Dereckson (talk | contribs) (Created page with "The Nasqueron internal reports repository is a monorepo containing SQL queries and tools to produce reports about Nasqueron internal data. == Python tools == === Configure PYTHONPATH === Python allows to develop several packages at the same time providing all the src/ folders to your PYTHONPATH variables. First, ensure you don't have any module installed through .whl running <code>pip freeze</code>. If you see something like <code>nasqueron-reports==0.1.0</code>, it co...")
12 September 2025
- 21:5621:56, 12 September 2025 Dev zone/Vault (hist | edit) [10,329 bytes] Dereckson (talk | contribs) (Created page with "This page explains how to query vault from an application. For infrastructure point of view, see Operations grimoire/Vault and Operations grimoire/Eglide/Vault. == Guides == === Python with hvac === In Python, the [https://python-hvac.org/ hvac library] is recommended. ==== Step 1 - Connect to Vault ==== Connection is straightforward and works out of the box even without parameters: <syntaxhighlight lang="python"> VAULT_CA_CERTIFICATE = "/usr/local/share/cert...")
