Yes, and our interpretation is that the maintenance state is set before the SU
is ACTIVATED (unlocked), not DEACTIVATED (locked).
Also see :
3.3.2.3 Actions of the Upgrade Step
1. Online installation of new software
2. Lock deactivation unit
3. Terminate deactivation unit
4. Offline uninstallation of old software
5. Modify information model and set maintenance status
6. Offline installation of new software
7. Instantiate activation unit
8. Unlock activation unit
9. Online uninstallation of old software
/Bertil
From: Nagendra Kumar [mailto:[email protected]]
Sent: den 4 oktober 2013 08:59
To: [opensaf:tickets]
Subject: [opensaf:tickets] Re: #477 AMF should honour admin commands on
middleware SU only when originated from SMF
Hi Bertil,
Is the below snaps getting referred by SMF ?:
4.2.1.3 Detection of Asynchronous Failures of AMF Entities
For AMF entities, this means that if a service unit is upgraded by an
upgrade step, its saAmfSUMaintenanceCampaign attribute must be set by the
Software Management Framework before the activation unit is activated.
Thanks
-Nagu
From: Bertil Engelholm [mailto:[email protected]]
Sent: 04 October 2013 12:21
To: [opensaf:tickets]
Subject: [tickets]<http://sourceforge.net/p/opensaf/tickets/_discuss/>
[opensaf:tickets] Re: #477 AMF should honour admin commands on middleware SU
only when originated from SMF
Today SMF is setting maintenance state after locking e.g. SU's (according to
SMF spec) so I wonder if this
change will work ? What is the purpose with this change ?
/Bertil
From: Nagendra Kumar [mailto:[email protected]]
Sent: den 4 oktober 2013 08:35
To: [opensaf:tickets]
Subject: HYPERLINK
"http://sourceforge.net/p/opensaf/tickets/_discuss/"[tickets]<http://sourceforge.net/p/opensaf/tickets/_discuss/>
[opensaf:tickets] #477 AMF should honour admin commands on middleware SU only
when originated from SMF
changeset: 4530:c567a8243dcc
tag: tip
user: Nagendra
[email protected]<mailto:[email protected]>
"mailto:[email protected]"[email protected]
date: Fri Oct 04 12:05:16 2013 +0530
summary: amfd: Allow admin operation on middleware only when originated from
SMF HYPERLINK
<mailto:[email protected]%0bdate:%20Fri%20Oct%2004%2012:05:16%202013%20+0530%0bsummary:%20amfd:%20Allow%20admin%20operation%20on%20middleware%20only%20when%20originated%20from%20SMF%20HYPERLINK%20>
"http://sourceforge.net/p/opensaf/tickets/477/"[#477]<http://sourceforge.net/p/opensaf/tickets/477/>http://sourceforge.net/p/opensaf/tickets/477/
HYPERLINK
"http://sourceforge.net/p/opensaf/staging/ci/c567a8243dcc988855273e3218015afffae8694b/"[staging:c567a8]<http://sourceforge.net/p/opensaf/staging/ci/c567a8243dcc988855273e3218015afffae8694b/>
________________________________
HYPERLINK
"http://sourceforge.net/p/opensaf/tickets/477/"[tickets:#477]<http://sourceforge.net/p/opensaf/tickets/477/>http://sourceforge.net/p/opensaf/tickets/477/
AMF should honour admin commands on middleware SU only when originated from SMF
Status: fixed
Created: Wed Jun 26, 2013 09:36 AM UTC by Mathi Naickan
Last Updated: Mon Sep 09, 2013 11:54 AM UTC
Owner: Nagendra Kumar
AMF should allow admin commands on middleware SU only if these commands are
originated from SMF.
Commands like lock, lock-in and unlock, unlock-in of middleware 2N su should
succeed only when SMF trigerrs them through the campaign.
If we dont bring in this restriction then there are problem areas (that are
still not concretely defined but can be potential problems) as described in the
migrated ticket #443.
Once this is fixed, the patch distributed by anders is acknowledged.
________________________________
Sent from sourceforge.net because
[email protected]<mailto:[email protected]>
"mailto:[email protected]"[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.
________________________________
HYPERLINK
"http://sourceforge.net/p/opensaf/tickets/477/"[tickets:#477]<http://sourceforge.net/p/opensaf/tickets/477/>
AMF should honour admin commands on middleware SU only when originated from SMF
Status: fixed
Created: Wed Jun 26, 2013 09:36 AM UTC by Mathi Naickan
Last Updated: Fri Oct 04, 2013 06:35 AM UTC
Owner: Nagendra Kumar
AMF should allow admin commands on middleware SU only if these commands are
originated from SMF.
Commands like lock, lock-in and unlock, unlock-in of middleware 2N su should
succeed only when SMF trigerrs them through the campaign.
If we dont bring in this restriction then there are problem areas (that are
still not concretely defined but can be potential problems) as described in the
migrated ticket #443.
Once this is fixed, the patch distributed by anders is acknowledged.
________________________________
Sent from sourceforge.net because HYPERLINK
"mailto:[email protected]"[email protected]
is subscribed to http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
________________________________
[tickets:#477]<http://sourceforge.net/p/opensaf/tickets/477/> AMF should honour
admin commands on middleware SU only when originated from SMF
Status: fixed
Created: Wed Jun 26, 2013 09:36 AM UTC by Mathi Naickan
Last Updated: Fri Oct 04, 2013 06:35 AM UTC
Owner: Nagendra Kumar
AMF should allow admin commands on middleware SU only if these commands are
originated from SMF.
Commands like lock, lock-in and unlock, unlock-in of middleware 2N su should
succeed only when SMF trigerrs them through the campaign.
If we dont bring in this restriction then there are problem areas (that are
still not concretely defined but can be potential problems) as described in the
migrated ticket #443.
Once this is fixed, the patch distributed by anders is acknowledged.
________________________________
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/opensaf/tickets/477/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
---
** [tickets:#477] AMF should honour admin commands on middleware SU only when
originated from SMF**
**Status:** fixed
**Created:** Wed Jun 26, 2013 09:36 AM UTC by Mathi Naickan
**Last Updated:** Fri Oct 04, 2013 06:35 AM UTC
**Owner:** Nagendra Kumar
AMF should allow admin commands on middleware SU only if these commands are
originated from SMF.
Commands like lock, lock-in and unlock, unlock-in of middleware 2N su should
succeed only when SMF trigerrs them through the campaign.
If we dont bring in this restriction then there are problem areas (that are
still not concretely defined but can be potential problems) as described in the
migrated ticket #443.
Once this is fixed, the patch distributed by anders is acknowledged.
---
Sent from sourceforge.net because [email protected] is
subscribed to http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
