Issue 11509: Section: 7.1.11.10 (amsm-ftf)
Source: Naval Surface Warfare Center (Mr. Paul V. Werme, paul.werme(at)navy.mil)
Nature: Enhancement
Severity: Significant
Summary: The specific set of HW Utilizations and semantics should be reviewed to remove ambiguities. In particular, the time scale over which utilizations are measured should be explicitly stated. In addition, the specific set of HW Utilizations should be reviewed to determine whether additional information is needed, e.g., 1) network data input and output values and rates. 2) Per cpu statistics, 3) per network connection statistics, 4) page faults and rates, 5) size of the process ready queue, etc...

Resolution: Add a new template sub-classing AMS_Property to have the ability to accounts hardware and software resource usage with time, duration and units; and use it in AMS_Host and AMS_LANEndPoint.
Revised Text: Pages 97, 98:
Replace Fig. 7.20 (Network class diagram (1/2)) with:
 
Replace Fig. 7.21 (Network class diagram (2/2)) with:
 

Page 103:
In the paragraph of the section 7.1.10.5 (AMS_Host Class) just before the table, replace "AMS_Property" with "AMS_Accounting".
In the table of the section 7.1.10.5 (AMS_Host Class), replace "AMS_Property" with "AMS_Accounting".

Page 103:
Add the following paragraph just before the table of the section 7.1.10.6 (AMS_LANEndPoint Class):
It has also an association to AMS_Accounting<AMS_StdHWUtilisation,HU_NONSTD> in order to design platform-specific hardware utilizations (cf. AMS_StdHWUtilisation for the normalized set of platform-specific hardware utilizations).
In the table of the same section, add the following lines:
Associations	Multiplicity	Class
AMS_RTHU <<optional HSM>>	0 .. *	AMS_Accounting<AMS_StdHWUtilisation,HU_NONSTD>

Pages 104, 105:
In the enumeration in the section 7.1.10.10 (AMS_StdHWUtilisation class), replace the bulleted list with the following items:
·	HU_NONSTD: special value that denotes a non-normalized value (i.e. use the "Name" attribute instead.
·	HU_CPU: The amount of time the CPU was occupied during the measurement interval.
·	HU_RUNQ: Average run queue length over the measurement interval.
·	HU_WAIT: The amount of time, processes had to wait for IO during the measurement interval.
·	HU_LAN_BTX: The amount of bytes sent via the LAN endpoint transmitter during the measurement interval.
·	HU_LAN_BRX: The amount of bytes received via the LAN endpoint receiver during the measurement interval.
·	HU_LAN_PTX: The amount of packets sent via the LAN endpoint transmitter during the measurement interval.
·	HU_LAN_PRX: The amount of packets received via the LAN endpoint receiver during the measurement interval.
·	HU_PMS: The amount of occupied Physical Memory Space.
·	HU_PFS: The amount of occupied Paging File Space.
·	HU_DSK_WR: The amount of bytes written to disk during the measurement interval.
·	HU_DSK_RD: The amount of bytes read from disk during the measurement interval.
·	HU_OFS: The amount of bytes, of the file systems, that is occupied.
·	HU_FS: The amount of bytes of the file systems.
·	HU_PN: number of running processes.
·	HU_TN: number of running threads.


Page 112 and following pages:
Replace Fig. 7.26 (AMS_Property template class diagram) with:
 
Add a new section 7.1.12.1 "AMS_Accounting<Class T, T v> Template":
The AMS_Accounting template adds to the AMS_Property value-name pairs the following data:
·	Capability: Maximum capability for the property. An empty string denotes unrestricted capability.
·	Time: Expresses the time the measurement was finished.
·	Duration: Duration of the measurement interval in micro seconds. A value of 0 denotes a sample of absolute value.
·	Units: The units in which the Value is expressed. Standardized values are:
o	Time standardized values:
§	ns (nanoseconds)
§	us (microseconds)
§	ms (milliseconds)
§	s (seconds)
o	Memory size standardized values:
§	B (byte)
§	kB (kilobyte)
§	MB (megabyte)
§	GB (gigabyte)
§	TB (terabyte)
This template provides the ability to accounts hardware and software resource usage.
Attributes	Type	
Capability	String	
Time	String	
Duration	uint32	
Units	String	

Page 162 and following ones:
In section 8.6.9 (AMS_LogicalHardware.idl), find and replace "Property" with "Accounting".
In the interface "AMS_Accounting_StdHWUtilisation", add the following attributes:
attribute string Capability;
attribute string Time;
attribute AMS_Util::AMS_uint32	Duration;
attribute string Units;
In the interface "AMS_LANEndPoint", add the following attribute and function:
AMS_Accounting_StdHWUtilisationListIterator GetStdHWUtilisationListIterator ( );
readonly attribute AMS_Accounting_StdHWUtilisationList RTHU;
Replace the enum "AMS_StdHWUtilisation" with the following:
enum AMS_StdHWUtilisation {
	HU_NONSTD,
	HU_CPU,
	HU_RUNQ,
	HU_WAIT,
	HU_LAN_BTX,
	HU_LAN_BRX,
	HU_LAN_PTX,
	HU_LAN_PRX,
	HU_PMS,
	HU_PFS,
	HU_DSK_WR,
	HU_DSK_RD,
	HU_OFS,
	HU_FS
	HU_PN,
	HU_TN
}

Page 206 and following ones:
In section 9.6.8 ("Logical Hardware"), find and replace "Property" with "Accounting".
In the complex type "AMS_Accounting_StdHWUtilisationType", add the following attributes:
<xsd:attribute name="Capability" type="xsd:string" use="required" />
<xsd:attribute name="Time" type="xsd:string" use="required" />
<xsd:attribute name="Duration" type="xsd:int" use="required" />
<xsd:attribute name="Units" type="xsd:string" use="required" />
In the complex type "AMS_LANEndPointType", add the following lines just before the line with "</xsd:extension>":
<xsd:sequence>
<xsd:element name="AMS_RTHU" type="AMS_RTHU_LinkType" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
Replace the simple type "AMS_StdHWUtilisation" with:
<xsd:simpleType name="AMS_StdHWUtilisation">
	<xsd:restriction base="xsd:string">
		<xsd:enumeration value="HU_NONSTD" />
		<xsd:enumeration value="HU_CPU" />
		<xsd:enumeration value="HU_RUNQ"/>
		<xsd:enumeration value="HU_WAIT"/>
		<xsd:enumeration value="HU_LAN_BTX"/>
		<xsd:enumeration value="HU_LAN_BRX"/>
		<xsd:enumeration value="HU_LAN_PTX"/>
		<xsd:enumeration value="HU_LAN_PRX"/>
		<xsd:enumeration value="HU_PMS"/>
		<xsd:enumeration value="HU_PFS"/>
		<xsd:enumeration value="HU_DSK_WR"/>
		<xsd:enumeration value="HU_DSK_RD" />
		<xsd:enumeration value="HU_OFS" />
		<xsd:enumeration value="HU_FS" />
		<xsd:enumeration value="HU_PN" />
		<xsd:enumeration value="HU_TN" />
	</xsd:restriction>
</xsd:simpleType>

Page 259 and following ones:
In section 10.1.4.6 (Logical Hardware), find and replace "Property" with "Accounting".
In section 10.1.4.6 (Logical Hardware), just after the first 'pragma', add the following lines:
//==================================================================
// Accounting
//===================================================================
      [Description ("")]
class AMS_Accounting {

     [Key]
     string InstanceID;

     string Name;
     string Value;
     string Capability;
     string Time;
     uint32 Duration;
     string Units;
};
Replace the definition of class AMS_RTHU at the end of the section 10.1.4.6 (Logical Hardware) with the following one:
//=================================================================== 
// RTHU
//===================================================================
      [Association, Aggregation,
       Description("An association between"
          "AMS_Accounting<AMS_StdHWUtilisation, HU_NONSTD> class in order"
          "to design platform-specific hardware utilisation.")]
class AMS_RTHU : CIM_Dependency {

      [Key, aggregate,
       Override("Antecedent"),
       Max(1), Min(1)]
      AMS_Host REF Antecedent;

      [Overrride("Dependent")]
      AMS_Accounting REF Dependent;

      ValueMap { "0", "1", "2", "3", "4", "5", "6", "7", "8", "9",
                 "10", "11"},
      Values { "HU_NONSTD", "HU_CPU", "HU_RUNQ", 
               "HU_WAIT", "HU_LAN_BTX", "HU_LAN_BRX", "HU_LAN_PTX", "HU_LAN_PRX",  
               "HU_PMS", "HU_PFS", 
               "HU_DSK_WR", "HU_DSK_RD", 
               "HU_OFS", "HU_FS", "HU_PN", "HU_TN"}]
      uint16 AMSStdHWUtilisation;
};
At the end of the section 10.1.4.6 (Logical Hardware), add the following lines:
//=================================================================== 
// RTHU_LAN
//===================================================================
      [Association, Aggregation,
       Description("")]
class AMS_RTHU_LAN : CIM_Dependency {

      [Key, aggregate,
       Override("Antecedent"),
       Max(1), Min(1)]
      AMS_LANEndPoint REF Antecedent;

      [Overrride("Dependent")]
      AMS_Accounting REF Dependent;

      ValueMap { "0", "1", "2", "3", "4", "5", "6", "7", "8", "9",
                 "10", "11"},
      Values { "HU_NONSTD", "HU_CPU", "HU_RUNQ", 
               "HU_WAIT", "HU_LAN_BTX", "HU_LAN_BRX", "HU_LAN_PTX", "HU_LAN_PRX",  
               "HU_PMS", "HU_PFS", 
               "HU_DSK_WR", "HU_DSK_RD", 
               "HU_OFS", "HU_FS", "HU_PN", "HU_TN"}]
      uint16 AMSStdHWUtilisation;
};

Page 281 and following ones:
In section 11.1.6, find and replace Property with Accounting.
In section 11.1.6, replace the "struct AMS_PropertyStdHWUtilisation" block and following pragma line with the following lines:
	//
	struct AMS_AccountingStdHWUtilisation {
		//
		string Name;
		AMS_StdHWUtilisation StdName;
		//
		string Value;
		string Capability;
		string Time;
		long Duration;
		string Units;
	};
#pragma keylist AMS_AccountingStdHWUtilisation Name,StdName
In section 11.1.6, in the "struct AMS_LANEndPoint" block, add the following lines:
// AMS_Accounting<AMS_StdHWUtilisation, HU_NONSTD>
sequence<AMS_AccountingStdHWUtilisation> AMS_RTHU;
In section 11.1.6, replace the "enum AMS_StdHWUtilisation" with:
enum AMS_StdHWUtilisation {
	HU_NONSTD,
	HU_CPU,
	HU_RUNQ,
	HU_WAIT,
	HU_LAN_BTX,
	HU_LAN_BRX,
	HU_LAN_PTX,
	HU_LAN_PRX,
	HU_PMS,
	HU_PFS,
	HU_DSK_WR,
	HU_DSK_RD,
	HU_OFS,
	HU_FS
	HU_PN,
	HU_TN
}


Actions taken:
September 21, 2007: received issue
July 23, 2009: closed issue
Discussion: 
Full study of these points need more time.
End of Annotations:=====

m: webmaster@omg.org
Date: 20 Sep 2007 22:27:50 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report



--------------------------------------------------------------------------------

Name: Paul V. Werme
Company: NSWCDD
mailFrom: paul.werme@navy.mil
Notification: No
Specification: AMSM
Section: 7.1.11.10
FormalNumber: dtc/07-05-02
Version: Beta 1
RevisionDate: 07-05-02
Page: 103
Nature: Enhancement
Severity: Significant
HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
Description
The specific set of HW Utilizations and semantics should be reviewed to remove ambiguities. In particular, the time scale over which utilizations are measured should be explicitly stated. In addition, the specific set of HW Utilizations should be reviewed to determine whether additional information is needed, e.g., 1) network data input and output values and rates. 2) Per cpu statistics, 3) per network connection statistics, 4) page faults and rates, 5) size of the process ready queue, etc...

From: Hugues.VINCENT@fr.thalesgroup.com
To: amsm-ftf@omg.org
Subject: Issue 11509
Date: Tue, 15 Jan 2008 10:35:13 +0100
X-Mailer: Internet Mail Service (5.5.2655.55)





Issue 11509: The specific set of HW Utilizations and semantics should be
reviewed to remove ambiguities. In particular, the time scale over which
utilizations are measured should be explicitly stated. In addition, the
specific set of HW Utilizations should be reviewed to determine whether
additional information is needed, e.g., 1) network data input and output
values and rates. 2) Per cpu statistics, 3) per network connection
statistics, 4) page faults and rates, 5) size of the process ready queue,
etc... 



We're still waiting for Paul Werme's review of HW Utilizations (as decided
in Jacksonville). 

Disposition: Transferred
OMG Issue No:  11509
Title:	Specification of HW Utilizations
Source:
NSWCDD
Summary:
The specific set of HW Utilizations and semantics should be reviewed to remove ambiguities. In particular, the time scale over which utilizations are measured should be explicitly stated. In addition, the specific set of HW Utilizations should be reviewed to determine whether additional information is needed, e.g., 1) network data input and output values and rates. 2) Per cpu statistics, 3) per network connection statistics, 4) page faults and rates, 5) size of the process ready queue, etc...
Discussion:
Full study of these points need more time.
Disposition:	Transferred to FTF2


m: Hugues.VINCENT@fr.thalesgroup.com
To: amsm-ftf@omg.org
Cc: jacek.skowronek@nl.thalesgroup.com
Subject: Outcome from Orlando's meeting: Issue 11509, implementer's issues
Date: Sat, 27 Sep 2008 18:00:38 +0200
X-Mailer: Internet Mail Service (5.5.2653.19)


Dear all,


Please find attached two contributions from Jacek (Thales Naval Netherlands)
and already presented during Orlando's meeting:
- a first ppt document describes a solution for the issue 11509,
- the second document is an excel sheet with a list of potential issues that
still have to be double checked by Jacek but that give a good view of issues
that will be posted end of October. 
As a reminder, the comments due date (September, 7th) is the date before
which all issues must be studied and is not the date after which no new
issues may be taken into acount: it's the FTF's decision. Since these issues
come from an implementer, I'm going to take them into account (as new issues
coming from Selex would be - if coming before Feb. 2009 because it'd be too
close from the report's due date).


Please comment these documents.



Best regards,
Hugues


  
 <<ISSUE11509_HW_Util.ppt>>  <<AMSM_ISSUES.xls>> 



 ISSUE11509_HW_Util.ppt 


 AMSM_ISSUES.xls