Issue 12429: Service configuration (qos4ccm-rtf) Source: THALES (Mr. Olivier Hachet, olivier.hachet2@fr.thalesgroup.com) Nature: Uncategorized Issue Severity: Summary: Service configuration : The QoS4CCM standard doesn't speak about access of QoS Enabler at container level. The 'install_service_reference' operation definition allos to register service reference at container level but doesn't allow the configuration of the services in a standard way. This would be useful to have a configuration interface and to invoke it at service installation. We propose to define a standard QoS Usage's interface to make service configuration and to improve 'install_service_reference' operation definition. Resolution: We propose to define a standard QoS Usage's interface to make service configuration and to improve 'install_service_reference' operation definition. A new interface QoSUsage to the following interface to make service configuration in standard way. The definition is inserted at end of section 8.11.2 Revised Text: · The section 8.11.2 is updated by the addition of the QoSUsage interface 8.11.2 QoS Usage Interface ... In some very constrained environments, it can be more efficient to design services as interfaces, not necessarily part of a component. Since the service is co-localized with components, it can be designed as an interface accessible at container level. The following interface is a standard base interface for services and is designed to allow service configuration when installing reference using the install_service_reference operation. A service is identified with the characteristic it manages which is part of the QoSConstraint definition. A QoSConstraint shall also contain a sequence of QoSInstances. These QoSInstances are the concrete resource requirements. module Components { module QoS { local interface QoSUsage : public ExtensionComponent { attribute readonly string characteristic; Cookie install_qos_property( in QoSInstances instances ) raises(CCMException); void uninstall_qos_property( in Cookie ck ) ; } ; } ; } ; 8.11.2.1 characteristic : This attribute identifies a QoSCharacteristic corresponding to the service_id parameter of the install_service_reference operation. 8.11.2.2 install_qos_property : This operation is called by the container, to set the service configuration defined in QoSInstances that are description of the constraints. The QoSInstances can be expressed in a QoSPropertyInstance and bind to a component feature if needed. Whenever the service is not able to process a QoSValue it shall return a CCMException with the reason QOS_ERROR. This means that the QoS property can't be installed or managed by service. 8.11.2.3 uninstall_qos_property : This operation is called by the container to unset some QoS properties managed by the service and uninstall related QoSPropertyInstance if exist. Actions taken: May 7, 2008: received issue Discussion: End of Annotations:===== m: olivier.hachet2@fr.thalesgroup.com To: qos4ccm-rtf@omg.org Cc: issues@omg.org Subject: QoS4CCM issue Date: Wed, 7 May 2008 16:40:14 +0200 X-Mailer: Internet Mail Service (5.5.2655.55) Service configuration : The QoS4CCM standard doesn't speak about access of QoS Enabler at container level. The 'install_service_reference' operation definition allos to register service reference at container level but doesn't allow the configuration of the services in a standard way. This would be useful to have a configuration interface and to invoke it at service installation. We propose to define a standard QoS Usage's interface to make service configuration and to improve 'install_service_reference' operation definition. regards, Olivier ---------------------------------------------------------------------------- -- Olivier HACHET THALES Communications DLJ/FR/OPS-F/SAT/SC2 1-5, ave. Carnot / Bat.E - 91883 MASSY Cedex Tel : +33 1 69 75 32 39 Fax : +33 1 69 75 31 79