Issue 7666: Host Collocation Deployment Directive Capability Lacking (deployment-rtf) Source: Raytheon (Mr. Gerald Lee Bickle, Gerald.L.Bickle(at)raytheon.com) Nature: Uncategorized Issue Severity: Summary: Problem: The CCM DTD and SCA DTD in the assembly descriptors has the capability to direct deployment of components on the same processor. The capability is needed for deployment considerations to direct which components are to be collocated on the same processor. Example use case is there are devices in the system with the same characteristics but when deploying the components, one wants to ensure that certain components are deployed on the same processor not on different processors with the same characteristics. Recommended solution: Is to add an optional zero to many Host Collocation element to the ComponentAssemblyDescription. Resolution: Revised Text: Actions taken: September 3, 2004: received issue Discussion: See issue #7667 for disposition End of Annotations:===== ubject: Deployment and Configuration Final Adopted Spec Issue To: issues@omg.org Cc: Deployment RTF X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 From: Gerald_L_Bickle@raytheon.com Date: Fri, 3 Sep 2004 06:55:16 -0500 X-MIMETrack: Serialize by Router on NotesServer3/HDC(Release 5.0.13a |April 8, 2004) at 09/03/2004 06:55:15 AM X-SPAM: 0.00 Deployment and Configuration specification Issue: Host Collocation Deployment Directive Capability Lacking Problem: The CCM DTD and SCA DTD in the assembly descriptors has the capability to direct deployment of components on the same processor. The capability is needed for deployment considerations to direct which components are to be collocated on the same processor. Example use case is there are devices in the system with the same characteristics but when deploying the components, one wants to ensure that certain components are deployed on the same processor not on different processors with the same characteristics. Recommended solution: Is to add an optional zero to many Host Collocation element to the ComponentAssemblyDescription. Jerry Bickle Engineering Fellow Network Centric Systems 1010 Production Rd Fort Wayne, IN 46808-4711 260-429-6280 Date: Tue, 30 Nov 2004 21:58:59 +0100 From: Andreas Hoffmann Organization: Fraunhofer FOKUS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: de, en, en-us, en-gb To: Deployment RTF Subject: Resolution outline for issues #7666 and #7667 and the "separation issue" (no number so far) This is an outline for the resolution for the issues #7666 and #7667 as well as the "separation issue" just raised. It includes the capability to request host and process collocation as well as to request the instantiation of components on separate nodes or in separate processes for fault tolerance or other reasons. Note: Please note that required collocation of components for performance reasons should be used very carefully. It may limit the reuse of component assemblies. It is often better to use a special requirement on the communication path between two components instead of requesting collocation of those components (asl already discussed). -- Best regards / Viele Gruesse Andreas ==================================================================== Andreas Hoffmann Fraunhofer FOKUS - Research Institute for Open Communication Systems Kaiserin-Augusta-Allee 31 D - 10589 Berlin Phone: +49 30 3463-7392 Fax: +49 30 3463-8392 Email: andreas.hoffmann@fokus.fraunhofer.de Web: http://www.fokus.fraunhofer.de/tip/ ==================================================================== Date: Wed, 01 Dec 2004 13:51:57 +0100 From: Andreas Hoffmann Organization: Fraunhofer FOKUS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: de, en, en-us, en-gb To: Deployment RTF Subject: Proposed resolution for issue #7666 Proposed resolution for issue #7666 (Host Collocation Deployment Directive Capability Lacking) The proposed resolution is to merge this issue with issue #7667 (Process Collocation Deployment Directive Capability Lacking). Here is the issue description: Issue 7666: Host Collocation Deployment Directive Capability Lacking Problem: The CCM DTD and SCA DTD in the assembly descriptors has the capability to direct deployment of components on the same processor. The capability is needed for deployment considerations to direct which components are to be collocated on the same processor. Example use case is there are devices in the system with the same characteristics but when deploying the components, one wants to ensure that certain components are deployed on the same processor not on different processors with the same characteristics. Recommended solution: Is to add an optional zero to many Host Collocation element to the ComponentAssemblyDescription. Rationale for proposed merger: Both issues (#7666 & #7667) ask for a solution for expressing special requirements for the collocation of components. These collocation requirements are in both cases an input for the deployment planning process. The collocation requirements can be expressed in the same manner for host and process collocation (just different values). Thus, the proposed resultion is to merge this issue with issue #7667 (Process Collocation Deployment Directive Capability Lacking). -- Best regards / Viele Gruesse Andreas ==================================================================== Andreas Hoffmann Fraunhofer FOKUS - Research Institute for Open Communication Systems Kaiserin-Augusta-Allee 31 D - 10589 Berlin Phone: +49 30 3463-7392 Fax: +49 30 3463-8392 Email: andreas.hoffmann@fokus.fraunhofer.de Web: http://www.fokus.fraunhofer.de/tip/ ==================================================================== 260-429-5060 Fax