i3-MARKET V1

The I3-MARKET Cloud SW stack is represented in Figure 1 and it is composed of four layers: Cloud provisioning and management layer, DevOps SW layer, Third-party SW layer and I3M SW layer.

Figure 1 – I3M Cloud SW stack

Cloud provisioning and management layer oversees providing and managing all physical nodes that the i3-MARKET common infrastructure is composed of. ATOS will be leading the provision of the cloud layer. 

For the management of physical resources in a homogeneous way, an Ansible Tower instance will be deployed for the administration of said physical resources, thus having their management centralized from Ansible.

I3-MARKET DevOps will be a set of practices that will combine software development and IT operations and it will aim to shorten the I3-MARKET system development life cycle and provide continuous delivery with high software quality.

Third-party SW layers will be managed by GFT, UPC and Guardtime and it will be mainly in charge of providing the SW stack identified as SW requirements by i3-MARKET system. These SW requirements are: Hyperledger Besu, CocroachDB, Loopback4 and Keycloak.

Finally, i3-MARKET SW layer will be composed by all i3-MARKET artifacts.

Cloud Management

To manage all i3-MARKET cloud resources the proposed approach is based on the usage of  Ansible Tower as key pillar behind cloud operative. With Ansible Tower we can centralize and control the i3-MARKET shared IT infrastructure with a visual dashboard, role-based access control, job scheduling, integrated notifications, and graphical inventory management. Ansible Tower dashboard is shown in Figure 2.

Figure 2 – Ansible Tower dashboard view

Go to the beginning of the page