Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Looking at the topology of the system, we have three types of nodes:

  • clients, that have a UI and are used by humans to manipulate data in one or more repositories;
  • servers, that contain repositories and can replicate data, where servers can also be relay servers;
  • gateways, containing the management agent and the installed software components.

On-line scenario

The on-line scenario has the simplest network topology. Everything is on-line. You have two roles: release manager and gateway operator. The release manager is responsible for the store, linking bundles to licenses. He can see a list of gateways in the system to determine the impact of his edits on these gateways, before he actually commits them. In fact he can see two statusses here: the status of a gateway compared to what is approved and the status compared to what is currently on the gateway (where the latter is derived from the audit log information). The gateway operator creates gateways and links them to licenses. Furthermore, at some point, the gateway operator will detect that for some gateways, updates exist (by looking at both the store and the gateway operator repository). Per gateway, he can now approve such a set of bundles. This set will be tagged with a version for that gateway and eventually get installed by the management agent.

...