Service Management¶
This document describes a contract life cycle: deployment, management, and use.
Assumptions¶
- All this features will be accessible by humans and some of the features – by machines (third-party software).
- System Administrator is always a human role.
- Infrastructure-domain Administrator is always a human role.
- User-domain Administrator is a human role but could partially be a machine role.
- Contract Administrator might be either a human role or a machine role.
- Host Owner and Switch Owner are machine roles.
User Interaction and Design¶
Service Deployment and Management¶
Referring to fig. Service Development and Management presented below, a schematic view of methods for service deployment and management within the system is provided.
Any service deployment may begin with designing a service template by, as an example, the system customer’s devops team. During the service template design process, the devops team creates configuration for every service endpoint role defined within this virtual service.
The system administrator may install service templates received from one or a plurality of devops teams and enable them for use in one or a plurality of user domains.
The domain administrator may create one or a plurality of contracts in the domain. Instantiating of any contract may be accompanied with allocation of platform resources, e.g. a group identifier, and designation of particular service template to the contract. To delegate the permissions to manage content distribution within the contract, the domain administrator may assign the contract administrator role to one or a plurality of users.
A contract administrator may create a set of contract roles and assign one or a plurality of contract roles to the users in the domain. Any contract role may be created only by customizing the service roles from the service template designated to the contract.
All the actions performed by system, domain, and contract administrators may undergo an authorization procedure.
Fig. 51 Figure. Service Deployment & Management
Service Template¶
Referring to fig. Service Template presented below, a schematic view of virtual service template is disclosed.
Network Virtual Service Template describes a set of communication rules for data exchange participants. Such a set of rules frames a particular communication model. A variety of communication models might be described by means of service template – from the simplest one like a sender-receiver model to more complex ones such as, for example, publish-subscribe or consensus networking models.
Each service template composed of, at least, one or, more common, a plurality of service roles. Every single service role has a corresponding configuration for communication endpoints. On a low level, such configuration contents a special packet specification and a set of communication endpoint management settings.
A set of channel management requirements governs all the communication endpoint management settings within the template. Such the requirements determine, for example, keep-alive intervals, time-outs, etc.
The special packet specification contents description of default communication pathways, a delivery instructions map and binary, program data map and default values, authorization token default values.
The service template may contain the description of communication graph that defines, for examples, rendezvous points, main and backup pathways. Thus each service role endpoint configuration may inherit a part of the communication graph as the description of its default communication pathways.
Delivery instructions are stored within the service template in the instruction repository. All the stored instruction blocks may be reused within the template across multiple service roles to set the map and binary of delivery instructions.
A communication data structure within the service template is used to describe organization of data used to facilitate communication. Every service role derives data for its Program Data Map and Default Values section from the template’s communication data structure.
Channel management requirements dictate which of endpoint management settings are to be used across all the service roles within the template. In such a way, consistency of endpoint management settings is guaranteed all across the template.
Referring to the figure Service Development & Management presented above, a schematic view of methods for service deployment and management within the system is provided.
To enable the service, a system administrator may create a user domain and assign a domain administrator to it. The system administrator may allocate shared platform resources, e.g. a pool of group identifiers, for use in the user domain.
A user domain administrator may create one or a plurality of users in its own domain. One or a plurality of system roles may be assigned to each user by the domain administrator.
All the actions performed by system, domain, and contract administrators may undergo an authorization procedure.