service management

[lpuskas]

service specific details need to be abstracted and made configurable

Requirements:

• administrators should be able to "register" a new service under an existing provider or a completely new provider
• cloudinfo behaves similarly to the existing services in case of the newly registered ones
• existing services behaviour will not be extended or altered

Design:

• the initial format for importing cloud information is similar to what CI currently supports
• service data is thought as configuration, passed to the app in yaml format
• service data is loaded into the application on startup

• • information shared between services need to be reflected in the data definition
• • the above introduces ordering between service information loading: dynamic services -those that get the information from providers -need to be started before static services

Tasks:

• design the data model for service configuration
• design the operational model (how the configuration is loaded)
• implement the configuration loader
• integrate the loader to the current product / factor out the redundant solutions
• include / exclude - data from existing services