Sameboat Nodes

Design Intent & Ops concept:

Each associated with an app such as the 'geonode', a metro region designated by its principal airport code(s) or an existing virtual community.
As a demonstration of but separable from DCP/MCP continuously deploy a network of per app clusters for each based on my following infra

  • Domain Space (DS)
  • DCMS/CLiu
  • Popular Groups
  • The DS App Platform
  • DS smart doorbell and other videotelephony abstraction

Network rollout order

Geonodes

      The domain space Producer intends to operate these regional nodes:
  • ord.sameboat      new chicagoland: fourteen counties in NE illinois, NW indiana, and SE wisconsin.
  • seayvr.sameboat   central cascadia: king, kitsap, pierce and snohomish counties and the b.c. lower mainland.

    • all 3 above concurrently and these possibly later

  • bufyyz.sameboat     ca-us synapse: WNY ( cattaraugus, chattauqua, erie, and niagara ) and southern Ontario, the GTA, horseshoe postal codes.
                            while 4th in order for prod this is used as the first non-commons deployment for DevOps/CI purposes.

  • mvdeze.sameboat   rio plata

The design intent is that nodes will be started for a whole region or general interest area and organically develop districts and specific interest areas on a user driven basis.

Network Paas/SaaS

AKPERSONs with current S class or better can access the software repository, and DevOps can participate in the network as autonomous (i.e. self-supporting and self-managing) DCP operators.
AKSAMBAR SKUs will be available later for support and core domain space management of autonomous network Operators.

Historical Note

GeoNodes bear some thematic resemblance to Yahoo GeoCities, but now vs. what in the mid 90s was possible.
They weren't originally conceived as such and it's more or less incidental, unlike the purposeful homage in MCP.