- **summary**: AMF PR Doc: BAD_OPERATION needs to be returned for si-swap when
there is single controller --> amf: BAD_OPERATION needs to be returned for
si-swap when there is single controller
- **status**: accepted --> unassigned
- **assigned_to**: Praveen --> nobody
- **Part**: doc --> d
- **Milestone**: 4.6.0 --> 4.7-Tentative
- **Comment**:
AMF PR doc is updated for case c) in below mentioned change-sets. For other
cases, ticket will remain open.
changeset: 149:7db7d054b191
tag: tip
parent: 146:f6b6282eb97e
user: [email protected]
date: Tue Apr 07 15:41:31 2015 +0530
summary: amf: update for 4.6 release [#1169, #1158, #964, #1153, #1235]
changeset: 148:3ce1d815cb2b
branch: opensaf-4.5.x
parent: 143:1d06fc8336d7
user: [email protected]
date: Tue Apr 07 15:36:37 2015 +0530
summary: amf: update for 4.5.1 release [#538, #1169]
changeset: 147:393b155b47cd
branch: opensaf-4.4.x
parent: 142:ea2199a72dfe
user: [email protected]
date: Tue Apr 07 15:34:41 2015 +0530
summary: amf: update for 4.4.2 release [#538, #1169]
---
** [tickets:#1294] amf: BAD_OPERATION needs to be returned for si-swap when
there is single controller**
**Status:** unassigned
**Milestone:** 4.7-Tentative
**Created:** Tue Mar 31, 2015 07:51 AM UTC by Sirisha Alla
**Last Updated:** Tue Mar 31, 2015 11:26 AM UTC
**Owner:** nobody
In the scenario of https://sourceforge.net/p/opensaf/tickets/1169/, when the
standby middleware SU is in instantiating state then TRY_AGAIN needs to be
returned. Else BAD_OPERATION needs to be returned. Returning TRY_AGAIN in all
scenarios is a deviation from spec.
AMF spec in 9.4.8 says:
"If no standby assignments are available for an SI (potentially because the AMF
cluster is in a degenerated status, and reduction procedures have been engaged)
when this operation is invoked on a particular logical entity, the
SA_AIS_ERR_BAD_OPERATION error value shall be returned.
In other words, this operation shall be allowed by the Availability Management
Framework to proceed under the following circumstances.
1) The concerned SI is assigned active or quiescing to one service unit.
2) The concerned SI is assigned standby to at least another service unit.
3) The HA readiness state of the service unit currently assigned the standby HA
state for the target service instance is ready-for-assignment.
4) The node capacity limits for the affected AMF nodes are not violated when the
HA state assignments are swapped.
The Availability Management Framework shall not proceed with this procedure when
the presence state of the constituent service units of the service group
protecting the SI is instantiating, restarting, or terminating, and should
return an SA_AIS_ERR_TRY_AGAIN error value conveying that the action is valid
but not currently possible."
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
