Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Talk:COSMOS Design 197868
Contents
General Comments
- Domain is used only for boot strapping. It's primary purpose is to hold onto a well defined set of EPRs.
The EPRs will be made available via resource properties.
- The following resource properties should be available:
DataBroker http://www.eclipse.org/cosmos/DataBroker
- Is the assembly necessary?
- Can we simplify the domain to remove the assembly?
- Why do we need to persist the contents of the domain?
- Why does domain extend abstract query?
- Use the wsdm tooling to create the endpoint.
- We need to reorganize the code to separate the domain from the broker to maximize deployment options
Using WS-RF
The design and the class diagram seem to be out of sync. For example, the class diagram indicates that the ManagementDomain will have a property called "dataBroker". There is only one of these. However, the operations, et. in the design indicate that there could not only be multiple databrokers w/in a domain, but also a "service brokers".
The reason behind the domain is to provide a single place for a DataManager to go and get the other infrastructure components it needs. Because the Domain will be a WSDM endpoint, the DataBroker can simply use the "getResourceProperty(http://org.eclipse.cosmos/DataBroker)" method. No additional API should be required.
Events/Topics
What events will the Domain either emit or subscribe to?
Metadata Exchange
What is expected when we do a MEX with the Domain? Who does it and under what circumstances? Does the Domain need to support MEX?
WSDM Capabilities
"Identity"
What is the URI of the Domain?
- The base URI and namespace for the domain will be: http://cosmos.eclipse.org/ManagementDomain/1.0
How do we identify it?
What should be returned when the WSDM identity property is asked for?
Operational Status
The Domain, Broker, and MDRs should support the Operational Status capability.
See // make sure the broker is loaded... DataBrokerClient.loadDataBrokerContext( brokerHostAddress, runtimePort); This should be replaced with an operational status query.
- ManagementDomain.pingManagementDomain() should be replaced
http://docs.oasis-open.org/wsdm/wsdm-muws2-1.1-spec-os-01.htm
Testing
- update org.eclipse.cosmos.dc.tests to include the junits (will need to convert to tptp test framework)
All other thoughts...
- Where do we get the "classifications"? See DataBrokerTests.testDataBrokerClient() This references something called "Performance" as a classification.