THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Info |
|---|
Under heavy construction |
Introduction
| Excerpt |
|---|
Apache ACE consists of a number of components, which can be deployed more-or-less independently. |
...
Alternative topologies
TODO create more professional looking images
The three topologies below are just examples; you can take (almost) any component, and drop it somewhere in your network, all components are intended to be distributed.
Single server
In the case of a single server, the OBR and the required server components are deployed on one system, and all target nodes connect to that one. This is the scenario that Getting Started with the File Based Server uses.
Offline
This scenario can be used in the case of a service engineer who takes his laptop to a machine to be serviced. Assuming that these devices do not have internet connectivity (for cost- or security reasons), the engineer loads up his laptop with the most recent situation from the server (this will happen automatically), and later connect it to the machine. The machine will get its new software, and upload its logs to the service laptop; the logs will later be synced back to the server.
Firewalled
In this scenario, the administration is done on the 'big bad internet', but the server on the internet only contains metadata. The actual code is located in the OBR's behind the firewall; here, we also see the distribution possiblities show the possible topologies: single server and gateway, separate OBR, several relays, where does the client fit in, how to work behind a firewall, etc.
Provisioning
Software provisioning is the main task of ACE. The provisioning components are responsible for determining the set of bundles to be deployed to a given target, creating a deployment package, and feeding the deployment package to the Deployment Admin.
...