User story #8138


Support the Plan9 Network Operating System

Added by Florian Heigl about 8 years ago. Updated almost 8 years ago.

UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:


Rudder Agent for Plan9 Network Operating System

Currently, Plan9 nodes are not recognized on Rudder, not even as generic computing system, which is bad.
I think it would be a very great addition due to it's focus on scalability and central management.

A picture I found on Google
This is the logo, which looks really cute.

Plan 9 began in the late 1980s as an attempt to have it both ways: to build a systemthat was centrally administered and cost-effective using cheap modern microcomputersas its computing elements.
A large Plan 9 installation has a number of computers networked together, eachproviding a particular class of service. Shared multiprocessor servers provide computingcycles; other large machines offer file storage.
The view of the system is built upon three principles. First, resources are named and accessed like files in a hierarchical file system. Second, there is a standard protocol,called 9P, for accessing these resources.
(9P is also commonly used on Linux and might already be supported!) -- --
Plan9 is a supported platform for the Go language which all really professional SRE web hipsters use.

Needed Features:
  • Installing Plan9 "bundles" - adding software!
  • FusionInventory Support to properly detect screen resolution and optional hardware like TV cards
  • Management of special users and permssions (i.e. "none")
  • Unicode support
  • Support running in rtf and rudder-vagrant (a premade Vagrant box is already available! See the following URL:
  • Network configuration including NTP management via the central server (maybe it's easiest to run Rudder on this one?)
  • Process management (kill > /proc/pid/ctl)

h2.Bonus from this port:
  • SEO-wise Rudder would benefit a lot it then be added to the wikipedia page at
  • No other CM system currently has Plan9 on their supported OS list
  • The CFEngine fileserver could be replaced by the 9P fileserver that comes with any Plan9 system
  • This would offer higher performance and scalability (like an automatic relay placed in each node)
  • additional features would become available like HSM allowing to keep rarely accessed client information on a tape library (Green IT)
  • Security of the server installation would be improved by the obscurity, that the most script-kiddies have probably not even heard of such a great OS!
  • The network database (, chapter 4.1) could be fully integrated using a Rudder plugin
  • insane scalabiltiy - quoting from

_Plan 9’s abilities can even simplify its own deployment: we wrap a synthetic file system layer around the original command-line based front-end control interface to the Blue Gene. This synthetic file system gives the feel of direct interaction with each node, and plugs nicely into existing Plan 9 tools, such as the Acid debugger, allowing cluster-wide debugging of both applications and system software.
(Take that, Ansible)

An overview of configuration management in Plan9 is given here:


Also available in: Atom PDF