Overview

bisos.dnsCap provides DNS management facilities that contribute to BISOS Capabilities. In BISOS, a Capability is a specific concept, specified and realized through bisos.capability. dnsCap is not itself a Capability; it is one ingredient — the DNS aspect — of a full CBS (Capability Bundle Specification), alongside sibling aspects such as webCap and sbom.

Concretely, dnsCap supplies the DNS naming an application needs. Its first backend maintains /etc/hosts entries for the .here domain (e.g. airflow.here), using the bisos.banna dblock machinery to keep those entries in sync.

dnsCap_seed.cs is a seed. Common usages take the form of a <name>-here-dns.pcs plant that names the fqdn to manage.

Table of Contents TOC

• Overview

• Relation to BISOS Capabilities

• Part of BISOS — ByStar Internet Services Operating System

• bisos.dnsCap is a Command-Only PyCS Facility

• Installation

  • Installation With pip

  • Installation With pipx

• Usage

  • Example: managing airflow.here in /etc/hosts

  • Commands

• Key Files

• Documentation and Blee-Panels

• Support

• Planned Improvements

Relation to BISOS Capabilities

A BISOS Capability is specified and realized by bisos.capability as a CBS (Capability Bundle Specification) — a bundle of component aspects. dnsCap is the DNS aspect of that bundle. Its sibling aspects include:

• dnsCap — DNS naming (this package): /etc/hosts and, later, other DNS backends.

• webCap — the web-service aspect.

• sbom — the Software Bill Of Materials aspect (typically a *-sbom.pcs plant).

A CBS composes these aspects into the complete specification of a Capability. dnsCap can be used on its own (as shown below) or as an ingredient invoked from within a CBS. For the Capability concept itself, see bisos.capability.

Part of BISOS — ByStar Internet Services Operating System

Layered on top of Debian, BISOS (By* Internet Services Operating System) is a unified and universal framework for developing both internet services and software-service continuums that use internet services. See Bootstrapping ByStar, BISOS and Blee for information about getting started with BISOS.

BISOS is a foundation for The Libre-Halaal ByStar Digital Ecosystem which is described as a cure for losses of autonomy and privacy in a book titled: Nature of Polyexistentials

bisos.dnsCap is part of BISOS. It is a standalone package that can be used independently of the full BISOS environment.

bisos.dnsCap is a Command-Only PyCS Facility

bisos.dnsCap is a command-line tool. It is a PyCS single-unit command service. PyCS is a framework that converges development of CLI tools and services. PyCS is an alternative to FastAPI, Typer and Click.

bisos.dnsCap uses the PyCS-Framework to provide the DNS aspect of a BISOS Capability:

1. Update /etc/hosts with the DNS entries for a .here fqdn (via the bisos.banna dblock machinery).

2. Verify that /etc/hosts contains the expected banna dblock markers.

3. Resolve and ping a managed fqdn to confirm the entry is in effect.

The core of PyCS-Framework is the bisos.b package (the PyCS-Foundation). See bisos.b for an overview.

Installation

The sources for the bisos.dnsCap pip package are maintained at: https://github.com/bisos-pip/dnsCap.

The bisos.dnsCap pip package is available at PYPI as https://pypi.org/project/bisos.dnsCap

You can install bisos.dnsCap with pip or pipx.

pip install bisos.dnsCap

pipx install bisos.dnsCap

Usage

from bisos.dnsCap import dnsCap_seedInfo
cntrlInfo = dnsCap_seedInfo.cmndsControlInfo
cntrlInfo.dnsSpecMethod = dnsCap_seedInfo.DnsSpecMethod.etcHosts
cntrlInfo.fqdn = "airflow.here"

bin/airflow-here-dns.pcs -i dnsCap_update

bin/airflow-here-dns.pcs -i dnsCap_verify

bin/airflow-here-dns.pcs -i dnsCap_resolve  airflow.here
bin/airflow-here-dns.pcs -i dnsCap_fqdnPing airflow.here

####+BEGIN: bx:dblock:global:run-result-stdout :command "bannaInfo.cs -i bannaForEtcHosts"
127.0.22.100  airflow.here  # port=24006
127.0.22.101  csLineInvoker.here  # port=24002
127.0.22.102  csLineInvoker_dev.here  # port=25002
127.0.22.103  csPlayerPerf.here  # port=23001
127.0.22.104  csPlayerPerf_dev.here  # port=23501
127.0.22.105  csPlayerUi.here  # port=24001
127.0.22.106  csPlayerUi_dev.here  # port=25001
127.0.22.107  sonCliLineInvoker.here  # port=24004
127.0.22.108  sonCliLineInvoker_dev.here  # port=25004
127.0.22.109  sonCliPlayerUi.here  # port=24003
127.0.22.110  sonCliPlayerUi_dev.here  # port=25003
127.0.22.111  starterSidebar.here  # port=24005
127.0.22.112  starterSidebar_dev.here  # port=25005

####+END:

Key Files

• py3/bin/dnsCap_seed.cs — the seed entry point.

• py3/bin/airflow-here-dns.pcs — example plant for airflow.here.

• py3/bin/exmpl-here-dns.pcs — example plant for exmpl.here.

• py3/bisos/dnsCap/dnsCap_csu.py — the four dnsCap_* commands.

• py3/bisos/dnsCap/dnsCap_seedInfo.py — DnsSpecMethod enum (etcHosts, tinydns) and the fqdn / dnsSpecMethod control info.

Documentation and Blee-Panels

bisos.dnsCap is part of ByStar Digital Ecosystem http://www.by-star.net.

This module’s primary documentation is in the form of Blee-Panels.

See file:./panels/bisos.dnsCap/_nodeBase_/fullUsagePanel-en.org for a starting point.

Support

Planned Improvements

• Implement the tinydns backend (DnsSpecMethod.tinydns is currently a placeholder).

• Handle dnsCap_update on a fresh /etc/hosts with no pre-existing dblock markers.