My expectation was that this model is covered by Warm and/or ServiceLevel

ServiceLevel will not work because of the way we define its use by clients. It is specifically designed to assume a load balancing use case. It will not work for primary backup use cases. Specifically in part 4 the definition of 'healthy' last paragraph about not switching to another server

image.png (103,108 bytes)   

image.png (103,108 bytes)   

Agreed at Dallas Face2Face Mar 23, 2023 to add a new subtype of NonTransparentRedundancyType to address the Primary/Standby use cases. Agreed on the following:

• failover approach fits best with Warm but the definition of Warm needs to relaxed
• The ServiceLevel of the standby which is fully ready to take over will be defined as Degraded 199 and explained to be fully functional as a standby. Other lower levels would be used to indicate a standby that is not prepared to take over due to some vendor specific reason.
• A property will be included in the new subtype which indicates the overall status of the primary and standby. At least representing 4 states (primary with standby, primary with no ready standby, standby ready to be primary and standby not ready.
• A method will be included in the new subtype which is used to manually fail over. Can be call in the primary or the secondary(s). If more than 1 secondary a call to the primary will result in the primary deciding which standby will take over.

Proposed types attached here.

image-3.png (53,458 bytes)   

image-3.png (53,458 bytes)   

Implemented new NonTransparentRedundancyType

Agreed to changes edited in Web meeting.

The new 6.3.15 NonTransparentBackupRedundancyType has a Property RedundantServerArray that is normally used for Transparent redundancy and the Property is not mentioned in the description. The RedundantServerDataType makes only sense together with Transparent redundancy.

Is this a copy&paste issue?

Agreed to changes in Virtual F2F.

There is no reason this should be limited to Transparent redundancy especially for the new NonTransparentBackupRedundancyType. For this type it makes perfect sense for each Server in the set to provide information about the other servers in the set.

Added a clarification to address the issue which we agreed to during the Virtual F2F.

Agreed to add a clarification during the F2F

Agreed to changes edited in virtual F2F.