Issues for Mailing list of the AMSM 1.2 Revision Task Force
To comment on any of these issues, send email to amsm-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.
List of issues (green=resolved, yellow=pending Board vote, red=unresolved)
Issue 13220: CIM_Process/CIM_Thread OSName attribute missing
Issue 13316: The association with AMS_Host is redundant
Issue 14091: Issue: Figures 7.7 and 7.8 on pages resp. 38 and 39 are identical
Issue 13220: CIM_Process/CIM_Thread OSName attribute missing (amsm-rtf)
Click here for this issue's archive.
Source: THALES (Mr. Willy Boenink, willy.boenink(at)nl.thalesgroup.com)
Nature: Revision
Severity: Significant
Summary:
CIM_Process/CIM_Thread OSName attribute missing According the PIM on page 39, CIM_Process and CIM_Thread have an attribute OSName. In the DCPS PSM there is only an attribute Name and not an OSName.
Resolution: Add the attribute Name to both of them (CIM_Process and CIM_Thread). Add also the attribute Name to CIM_UnixProcess and CIM_UnixThread, because these inherit the attribute Name from CIM_Process and CIM_Thread.
Revised Text: {In Section 11.6, page 297/298, replace the CIM_Process block with the following snippet:
struct CIM_Process {
//
string Name;
//
string OSName;
//
string Handle;
// sequence of full names of elements of AMS_ExecutbaleSoftwareElement
sequence<string> CIM_ServiceProcess;
// sequence of full names of elements of CIM_Thread
sequence<string> CIM_ProcessThread;
};
the CIM_UnixProcess block with the following one:
struct CIM_UnixProcess {
//
string Name;
//
string OSName;
//
string Handle;
// sequence of full names of elements of AMS_ExecutbaleSoftwareElement
sequence<string> CIM_ServiceProcess;
// sequence of full names of elements of CIM_Thread
sequence<string> CIM_ProcessThread;
//
unsigned long long ProcessGroupID;
//
unsigned long long RealUserID;
//
sequence<string> Parameters;
};
The CIM_Thread block with the following one:
struct CIM_Thread {
//
string Name;
//
string OSName;
//
string Handle;
//
unsigned long Priority;
// the full name of an element of CIM_Process
// the full name of an element of CIM_UnixProcess
string Owner;
};
The CIM_UnixThread block with the following one:
//
struct CIM_UnixThread {
//
string Name;
//
string OSName;
//
string Handle;
//
unsigned long Priority;
// the full name of an element of CIM_Process
// the full name of an element of CIM_UnixProcess
string Owner;
};
Actions taken:
January 13, 2009: received issue
July 23, 2010: closed issue
Issue 13316: The association with AMS_Host is redundant (amsm-rtf)
Click here for this issue's archive.
Source: THALES (Mr. Willy Boenink, willy.boenink(at)nl.thalesgroup.com)
Nature: Revision
Severity: Significant
Summary: The association with AMS_Host is redundant. AMS_OperatingSystem has an association with AMS_Host, see figure 7.19 and 7.20 on page 96/97. This implies that the association with AMS_Host in Application Deployment Specification class diagram on page 57 is redundant
Resolution: The association of AMS_DeploymentLinkSpec with AMS_Host on page 59 in figure 7.13 can be removed. Due to this change, Figure 7.12 also needs to be changed. A new association of AMS_DeploymentLink with AMS_OperatingSystem called AMS_OSUsed will then replace the association AMS_HostUsed. Also the PSMs have to be updated.
Revised Text: see pagers 14 and 15 for diagrams. In section 7.5.2, page 61, remove in table the row which contains the association of AMS_HostUsed.
In section 7.10.5, page 106, remove in table the row which contains the association of AMS_HostUsed.
In section 7.10.7, page 107, add in table the following row:
· AMS_OSUsed, 0 .. *, AMS_DeploymentLink
In Section 8.6.5, page 141, replace the AMS_DeploymentLink block with the following snippet:
//
interface AMS_DeploymentLink : AMS_CIM::CIM_LogicalElement {
readonly attribute AMS_LogicalHardware::AMS_OperatingSystem OSUsed;
readonly attribute AMS_ApplicationModule::AMS_ExecutableSoftwareElement ESEDeployed;
readonly attribute AMS_DeploymentConfiguration Owner;
attribute string LinkID;
};
In Section 8.6.6, page 142, replace the AMS_DeploymentLinkSpec block with the following snippet:
//
interface AMS_DeploymentLinkSpec : AMS_CIM::CIM_LogicalElement {
readonly attribute
AMS_LogicalHardwareSpecification::AMS_ConfigurationSpecification
ConfSpecDLS;
readonly attribute AMS_ApplicationSpecification::AMS_ESESpec SEDeployed;
readonly attribute AMS_DeploymentLinkSpec DeploymentLinkDependency;
readonly attribute AMS_DeploymentSpec Owner;
// association class
readonly attribute AMS_CIM::CIM_Action ActionOnLink;
AMS_CIM::CIM_Action GetActionOnLink (
in AMS_ApplicationSpecification::AMS_ActionCheckCase state );
//
AMS_LogicalHardware::AMS_OperatingSystemListIterator GetOSUsedIterator ( );
readonly attribute AMS_LogicalHardware::AMS_OperatingSystemList OSUsed;
attribute string LinkID;
};
In Section 9.6.4, page 188, replace the AMS_DeploymentLinkType block with the following snippet:
<xsd:complexType name="AMS_DeploymentLinkType">
<xsd:complexContent>
<xsd:extension base="CIM_LogicalElementType">
<xsd:sequence>
<xsd:element name="AMS_OSUsed" type="AMS_Ref"
minOccurs="1" maxOccurs="1" />
<xsd:element name="AMS_ESEDeployed" type="AMS_Ref"
minOccurs="1" maxOccurs="1" />
</xsd:sequence>
<xsd:attribute name="LinkID" type="xsd:string" />
<xsd:attribute name="OwnerId" type="xsd:string" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
In Section 9.6.5, page 189/190, replace the AMS_DeploymentLinkSpecType block with the following snippet:
<xsd:complexType name="AMS_DeploymentLinkSpecType">
<xsd:complexContent>
<xsd:extension base="CIM_LogicalElementType">
<xsd:sequence>
<xsd:element name="AMS_ConfSpecDLS" type="AMS_Ref"
minOccurs="0" maxOccurs="1" />
<xsd:element name="AMS_SEDeployed" type="AMS_Ref"
minOccurs="0" maxOccurs="1" />
<xsd:element name="AMS_DeploymentLinkDependency"
type="AMS_Ref" minOccurs="0" maxOccurs="1" />
<xsd:element name="AMS_ActionOnLink"
type="AMS_ActionOnLink_LinkType" minOccurs="0" maxOccurs="1" />
<xsd:element name="AMS_OSUsed" type="AMS_Ref"
minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
<xsd:attribute name="LinkID" type="xsd:string" />
<xsd:attribute name="OwnerId" type="xsd:string" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
In Section 10.5.4, page 251, remove the AMS_HostUsed block.
In Section 10.5.6, page 264/265, replace the HostUsed block with the following snippet:
// ===================================================================
// OSUsed
// ===================================================================
[Association]
class AMS_OSUsed : CIM_Dependency {
[Override("Antecedent")]
AMS_DeploymentLink REF Antecedent;
[Overrride("Dependent"),
Max(1), Min(1)]
AMS_OperatingSystem REF Dependent;
};
In Section 11.6, page 297, replace the AMS_DeploymentLink block with the following snippet:
//
struct AMS_DeploymentLink {
// the full name of an element of AMS_DeploymentConfiguration
string Owner
// the full name of an element of AMS_OperatingSystem
string AMS_OSUsed;
// the full name of an element of AMS_ExecutableSoftwareElement
string AMS_ESEDeployed;
//
string LinkID;
};
In Section 11.6, page 303/304, replace the AMS_Host block with the following snippet:
//
struct AMS_Host {
// sequence of full names of elements of CIM_ServiceAccessPoint
sequence<string> CIM_HostedAccessPoint;
// sequence of full names of elements of CIM_NextHopRoute
sequence<string> CIM_HostedRoute;
// sequence of full names of elements of CIM_LogicalDevice
// sequence of full names of elements of AMS_Domain
// sequence of full names of elements of AMS_HardwareGroup
sequence<string> CIM_SystemComponent;
// sequence of full names of elements of CIM_Location
sequence<string, 1> CIM_ElementLocation;
// sequence of full names of elements of AMS_OperatingSystem
sequence<string> CIM_InstalledOS;
// sequence of full names of elements of AMS_OperatingSystem
sequence<string> CIM_RunningOS;
// AMS_Property<AMS_StdHWUtilisation, HU_NONSTD>
sequence<AMS_PropertyStdHWUtilisation> AMS_RTHU;
// sequence of full names of elements of AMS_ConfigurationSpecification
sequence<string, 1> AMS_ConfSpecCS;
//
string Name;
//
string ArchitectureInfo;
//
short Status;
//
short NetworkLoad;
//
short UtilizationTimeScale;
};
In Section 11.6, page 305/306, replace the AMS_DomainManager block with the following snippet:
//
struct AMS_DomainManager {
// sequence of full names of elements of CIM_ServiceAccessPoint
sequence<string> CIM_HostedAccessPoint;
// sequence of full names of elements of AMS_Domain
sequence<string, 1> AMS_DomainManagerRole;
// sequence of full names of elements of CIM_NextHopRoute
sequence<string> CIM_HostedRoute;
// sequence of full names of elements of CIM_LogicalDevice
// sequence of full names of elements of AMS_Domain
// sequence of full names of elements of AMS_HardwareGroup
sequence<string> CIM_SystemComponent;
// sequence of full names of elements of CIM_Location
sequence<string, 1> CIM_ElementLocation;
// sequence of full names of elements of AMS_OperatingSystem
sequence<string> CIM_InstalledOS;
// sequence of full names of elements of AMS_OperatingSystem
sequence<string> CIM_RunningOS;
// AMS_Property<AMS_StdHWUtilisation, HU_NONSTD>
sequence<AMS_PropertyStdHWUtilisation> AMS_RTHU;
// sequence of full names of elements of AMS_ConfigurationSpecification
sequence<string, 1> AMS_ConfSpecCS;
//
string Name;
//
string ArchitectureInfo;
//
short Status;
//
short NetworkLoad;
//
short UtilizationTimeScale;
};
Actions taken:
January 22, 2009: received issue
April 30, 2009: deferred
July 23, 2010: closed issue
Discussion: Not enough time.
Disposition: Deferred
Issue 14091: Issue: Figures 7.7 and 7.8 on pages resp. 38 and 39 are identical (amsm-rtf)
Click here for this issue's archive.
Source: THALES (Dr. Jacek Skowronek, jacek.skowronek(at)nl.thalesgroup.com)
Nature: Uncategorized Issue
Severity:
Summary: Issue: Figures 7.7 and 7.8 on pages resp. 38 and 39 are identical.
Resolution: Figure 7.7 should be replaced by another figure, which will be supplied as part fo the move to the new UML tool.
Cheers,
Resolution: New figure should be used instead of Figure 7.7
Revised Text:
Actions taken:
July 22, 2009: received issue
July 23, 2010: closed issue