This blog on Openstack modelled using Archimate follows on from Openstack Cloud in Archimate – Part 1.
Horizon = Dashboard Functionality
Mission: Horizon is the canonical implementation of OpenStack’s dashboard, which is extensible and provides a web based user interface to OpenStack services.
Horizon = Dashboard Structural Logical Architecture
- Is “stateless” — doesn’t require a database.
- Delegates error handling to the back-end.
- Doesn’t support all the API functions exposed by the other Openstack Applications.
- Can use memcached or database to store sessions.
- Gets updated via API polling.
- Uses Django Project, which is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. See more detail on Django here: https://www.slideshare.net/balakumarp/django-framework
- It can be extended.
As mentioned in Part 1., the Openstack Cloud can be managed via a command line interface (CLI). This Dashboard makes is a lot easier to facilitate simple queries and changes, but does not support all the ever evolving services served by all the relevant Applications. To get all the functionality, one would need to connect to the CLI manually or REST services using the API programmatically.
Horizon = Dashboard Behavioural Services Architecture
Horizon does not offer or provide any of its own services, it simply consumes all the services from the other applications. Since in latest blogs we will show all Services offered by each application, nothing will be modelled here.
This next blog in the series is OpenStack Cloud Networking in Archimate – Part 3.