...
Delft-FEWS components are being deployed on many different architectures and hardware. The three main deployment types are
- physical servers - traditional server installation on top of OS.
- virtual machines - centralize administrative tasks while improving improved scalability and overall hardware-resource utilization and centralized administrative tasks..
- containers . - cloud virtualization that benefit from a more efficient abstraction layer than virtual machines.
When organizations are in the initial stage of (re-)defining their IT infrastructure, it is commonly recognized that after virtualization, containerization is the next logical step in the evolution of IT infrastructure. While we simplify / improve the possible to install Delft-FEWS on on-premise hardware, or in virtual machines. Delft-FEWS system installation on regular hardware / VMS is currently done by organizing a central database, installing RPMs / MSIs / unzipping the binaries, setting OS environment variables and starting a launcher service. For installation in the cloud this is not going to be much different. Usually this is controlled using data driven yaml / json configuration files to apply the needed actions.
| component | cloud readiness status | Room for improvements |
|---|---|---|
| Database | Both db docker containers as well as managed instances are already possible. Managed instances require minor adjustments of the db scripts. | Support one set of database scripts for all db flavors managed and unmanaged. |
Master Controller | Yes | Enable service replication |
Admin Interface | Yes | |
Operator Client / SA | Use Database proxy (Azure: Azure Virtual Desktop) | |
| ConfigManager | See Operator Client, in addition the AdminInterface API can be used. | |
Forecasting Shell Server | Yes | Facilitate auto scaling. |
WebServices | Yes | |
DatabaseProxy | Yes | |
OpenArchive | Yes |
...