#780 New AMF behavour adding components to existing SU is not backwards compatible

[Hans Feldt]

SMF campaigns cannot add e.g. components in the upgradestep when the SU is locked. Instead components must be added before the step to an unlocked SU. With the new feature introduced in #597 such campaigns no longer work since the component will be instantiated immediately potentially before the SW is installed (which it can be in the upgrade step).

It is proposed to restrict this new feature to be allowed for MW components only. More thinking and careful design needs to be done for supporting runtime addition of components that the user wants to have instantiated when they are added.

[Nagendra Kumar]

Changed the documentation for automatic instantiation and deletion to support middleware SG only.

[Bertil Engelholm]

Hi Nagendra,

we have a requirement that it should be possible to do this also for applications in the future and we need to
find a solution how to do this and still be backwards compatible. I.e. the components that wants to be started
automatically needs to add some information and the existing components should work as before.
The question is how to do this. We have discussed two options. Either add possibility to explicitly call new admin operations
on comp/csi (lock, unlock) or add a new attribute or attribute value to the component types telling AMF that it should
be started automatically. Any other possibilities?

/Bertil

From: Nagendra Kumar [mailto:nagendra-k@users.sf.net]
Sent: den 13 februari 2014 10:40
To: opensaf-tickets@lists.sourceforge.net
Subject: [tickets] [opensaf:tickets] #780 New AMF behavour adding components to existing SU is not backwards compatible

Changed the documentation for automatic instantiation and deletion to support middleware SG only.

---

[tickets:#780]http://sourceforge.net/p/opensaf/tickets/780/ New AMF behavour adding components to existing SU is not backwards compatible

Status: review
Created: Thu Feb 13, 2014 06:57 AM UTC by Hans Feldt
Last Updated: Thu Feb 13, 2014 09:19 AM UTC
Owner: Nagendra Kumar

SMF campaigns cannot add e.g. components in the upgradestep when the SU is locked. Instead components must be added before the step to an unlocked SU. With the new feature introduced in #597 such campaigns no longer work since the component will be instantiated immediately potentially before the SW is installed (which it can be in the upgrade step).

It is proposed to restrict this new feature to be allowed for MW components only. More thinking and careful design needs to be done for supporting runtime addition of components that the user wants to have instantiated when they are added.

---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.netopensaf-tickets@lists.sourceforge.net 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.

[Nagendra Kumar]

Hi Bertil,
I will raise an enhancement ticket and we can discuss the same in that ticket.

Thanks
-Nagu

[Nagendra Kumar]

changeset: 4968:c4b12097b48b
branch: opensaf-4.4.x
parent: 4966:f823f90f1cad
user: Nagendra Kumarnagendra.k@oracle.com
date: Fri Feb 14 12:08:49 2014 +0530
summary: amf: add check for middleware component for automatic comp instantiation and deletion [#780]

changeset: 4969:215055a5f7fa
tag: tip
parent: 4967:234989190ad9
user: Nagendra Kumarnagendra.k@oracle.com
date: Fri Feb 14 12:09:07 2014 +0530
summary: amf: add check for middleware component for automatic comp instantiation and deletion [#780]

[staging:c4b120]
[staging:215055]