Cross-Service Network Overview
Virtuozzo offers a full-stack Cloud Platform for your business, including the PaaS Virtuozzo Application Management and IaaS Virtuozzo Infrastructure solutions. The Cross-Service Network is a feature that allows communication between virtual machines on Virtuozzo Infrastructure and containers on Virtuozzo Application Management using the built-in tools. It allows end users to utilize both solutions as a single product for their purposes.
For example, end-users can use the feature to:
- connect Virtuozzo Infrastructure VMs with Application Management containers (e.g., databases) for data processing
- consume resources (e.g., Kubernetes) from Application Management while they are deployed in Virtuozzo Infrastructure
- consume S3 Storage from Virtuozzo Infrastructure on Application Management applications
Below you can find the implementation scheme:
- if both Application Management and Virtuozzo Infrastructure installations are based in the same data center (recommended) - the setup uses a common united L2 network between services (Public Network)
- if platforms are in the different data centers – the L3 setup can be implemented
This setup does not provide centralized access control list (ACL) management on both Application Management and Virtuozzo Infrastructure products. The appropriate ACL implementation must be done via a third party – usually a cloud management platform (CMP). Based on the API provided by Application Management and Virtuozzo Infrastructure, the CMP has information about the customers’ instances from both services and can link nodes inside the Cross-Service Network on behalf of a user.
Pre-Conditions
Before setting up a cross-service network between Virtuozzo Infrastructure and Application Management, the cloud admin needs to:
- dedicate and manually set up an internal network to be used as a shared private cross-service network between products - for example, 100.64.0.0/15
- ensure it is not already used for either of the products
- divide the dedicated network into subnets
- the size of subnets and their number is defined based on the partner’s needs
- each subnet must be configured separately on the PaaS and IaaS sides
- each Application Management region has its own dedicated subnet from the cross-service network
