system/DeserviceProfiles

A collection of deservice profiles. Used to switch a portion of the system’s servers to a soft out-of-service mode. In out-of-service mode, microservices do not participate in processing new requests, but continue to process previously started processes.

Created and used by the microservice mware.

Contained only in the master domain.

Storage Type: category.

The set of profiles in a decommissioning state define the set of servers and microservice instances for which to initiate a soft gradual decommissioning process.

Active-Passive category microservices gradually (no faster than one group per minute) change the leader, moving it to a follower node that is in the zone of normal-service servers.

Active-Active category microservices are no longer used by the balancer and in the hash ring. In this case:

  • sg - responds 503 to REGISTER, SUBSCRIBE, and INVITE requests with new dialogs if the site has other instances in the normal service area and if no exceptions are configured for the instance in the configuration.

  • esg - responds 503 to REGISTER, SUBSCRIBE, and INVITE requests with new dialogs to the shoulder deployed to the provider. This only happens if account is configured to support running on multiple esg instances and no exceptions are configured.

  • mg - for a few minutes, the controller takes the instance out of service and does not allocate new calls to it. The last instance always remains active, even though it may be in the queue to be taken out of service.

  • bgmg - are not taken out of service because they are bound to specific instances of esg and sg running on the same server. As long as esg/sg is active and serving any calls, the bgmg microservice cannot be shut down. If locally executing instances of esg/sg do not start new calls, bgmg is not automatically applied.

  • b2b, conf, ivr, svc et al. - do not receive new assignments.

  • ws - is not taken out of service. It is potentially possible to forward new connections/requests to alternate servers located in the normal service area.

When you turn off deservice mode, the system gradually brings the microservices back online:

  • Active-Active are returned to the balancer and hash ring;

  • Active-Passive gradually (not faster than one group per minute) make TakeOver - return the leader to his normal place.

Table 1. Class fields
Field Description

id

Identifier

name

Profile Name.

description

Profile Description.

servers

A list of server names set in the current configuration.

status

Profile Condition:

  • normal - normal operating mode is in effect.

  • deservice - decommissioning mode is enabled.