Change: simplify description of worker-manager

Dropped descriptions of the future.

1 files changed, 3 insertions, 25 deletions

diff --git a/architecture.mdwn b/architecture.mdwn
index 228bd00..aa60976 100644
--- a/architecture.mdwn
+++ b/architecture.mdwn
@@ -275,33 +275,11 @@ servers. We will add a safer approach for that later.
 
 
 
-Worker (worker-manager) registration
+The worker-manager
 -----------------------------------------------------------------------------
 
-The sysadmin arranges to start a worker-manager on every build host.
-(FIXME: This may change. They may run on the same host, or not: the
-Ick architecture doesn't really care. But the current implementation
-only supports running commands on the same host.) If they run on the
-same host, the worker manager will start a sub-process. If on
-different hosts, the sub-process will be started using ssh.
-
-Each worker has a set of tags to describe its various attributes.
-Attributes include things like CPU architecture, operating system
-version, whether the worker can be trusted with credentials for
-logging into other systems, or for retrieving source code from the git
-server.
-
-The worker-manager will include tags to the IDP when it registers
-itself, and updates the tags when they change. The IDP will include
-tags in the access token, and the controller gets the tags from the
-access token.
-
-The sysadmin may force specific tags via the IDP. The IDP will ignore
-any such tags from the worker-manager. For example, whether a worker
-is trusted.
-
-The controller will be able to use the tags to choose which worker
-should execute which pipeline steps.
+The sysadmin arranges to start a worker-manager on every build host
+and installs IDP credentials for each worker-manager.
 
     @startuml
     hide footbox