The use cases defined describe the functions and operations that are expected to deliver in the software. Two general use cases are defined: Virtual CPE for eHealth and Educational Institutions and Distributed and private cloud. Two scenarios, each of which covers related but separate requirements, have been defined for each case.
- UC1. Virtual CPE: emphasis is placed on defining the demarcation between provider and user
- UC2. Multiple Network Support: emphasis is placed on the defining the demarcation between two providers towards a single user.
- UC3. Distributed Cloud Infrastructure: describes a scenario where a single cloud infrastructure site can, through Mantychore, be extended to take advantage of resources at multiple physical sites without requiring the deployment of additional control infrastructure.
- UC4. Distributed Virtualised Hosting: describes a scenario where an institution can seamlessly migrate its existing physical infrastructure to an external cloud provider on a phased basis.
UC1. Virtual CPE
The demarcation of IP service between a service provider and client is typically performed by Client Premises Equipment (CPE). In HEAnet’s case, this equipment is often (not always) owned and operated by the provider, but it is always a part of the client’s network.
There are two main goals in virtualising this part of the infrastructure. The first is to remove the necessity for a separate physical device (or pair of devices) to sit alongside an existing layer 2 demarcation point, while still providing the flexibility of service that is needed toward the client. The second goal is to delegate a level of control over the virtualised CPE to the user, one which they would not normally be able to achieve when the device is managed by their provider.
UC2. Multiple Network Support
UNI•C operates the Danish National Research and Education Network (NREN), Forskningsnettet. A nation-wide Health Data Network connects all health care and health research institutions. Today, these two networks use completely separate infrastructures. However, a handful of institutions are connected to both networks with very different topologies and technical solutions. The primary use case will attempt to connect some of these institutions using virtual router instances instead of separate hardware.
The goal is to reduce the hardware required, by allowing two administrative teams to manage a single hardware device. At present, this demarcation can only be implemented by means of separate hardware, so a different router is needed for each network. With Mantychore, it is intended to use the administrative partitioning that can be provided by logical networks to provide access to both networks, managed separately, from the one router.
UC3. Distributed Cloud Infrastructure
This use case applies Mantychore to solve a distributed resources problem with a networking approach. Mantychore will be used to create a user-configurable and flexible network layer, which will harness distributed compute resources, presenting them in the required network configuration to allow them to be used as if they were co-located.
The network layer to be created is represented by the private network containing the worker nodes at TCD Grid-Ireland and others at remote sites. All the worker nodes are under the control of a single group of infrastructure machines (at TCD Grid-Ireland). The worker nodes should be in the same private address space/subnet/LAN, thereby allowing unicast, broadcast and, if possible, multicast traffic across all nodes. It would be desirable to allow DHCP be used to allocate addresses for these nodes.
UC4. Distributed Virtualised Hosting
Universities today often have their own private cloud, i.e., an internal hosting provider. It is often desirable to be able to move selected hosts in a private cloud to a commercial off-site hosting provider.
However, hosts are often parts of larger services with complex interdependencies. Moving a host may involve assigning a new IP address which in turn may imply that other parts of the service may need reconfiguration. In order to avoid this it is desirable to allow the hosting provider access to the same IP network as the customer. This use case describes how to achieve such private networks using Mantychore virtual router instances on top of a full mesh LSP MPLS network using RSVP. The goal is to enable a working pilot service.