I ended my last SkyeEngine Fabric post with an unresolved problem. The client-to-client transfer design worked, but the fastest numbers came from containers on one machine. Restarting those containers could move the …
Continue reading
The HubN Registry now has a proper workflow for requesting, configuring and tracking a peering session. The actual network is older than that workflow. Several BGP sessions were already running. They had working …
Continue reading
Most of my recent SkyeEngine writing has been about models, corpora and the machinery needed to build them. Running all of that is a different problem. The GPU workers, storage, inference services and tools don’t …
Continue reading
The HubN Registry stores allocations and requested state. Other services use that information to publish reverse DNS, generate ROAs, issue certificates and decide which BGP sessions ought to exist. For a long time the …
Continue reading
HubN has its own DNS hierarchy, certificate authorities and RPKI repository. Most of the individual parts had been working for a while. The less convincing bit was what happened while they changed. A manifest could be …
Continue reading
The second version of SkyeEngine Code could launch agents, route requests and show their replies. It still learned most of what it knew by watching rows appear in somebody else’s message database and guessing what those …
Continue readingNo posts on this page match that filter.