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.
Difference between revisions of "Cosmos Architecture Meeting 06-Feb-08"
(→command line or web UI to manage COSMOS components?) |
|||
Line 31: | Line 31: | ||
=== command line or web UI to manage COSMOS components? === | === command line or web UI to manage COSMOS components? === | ||
+ | * For i9, we are going to keep what we have and only fix things that are broken. | ||
+ | * We will need to refactor the code to formalize the admin service. This will be done in i10. | ||
+ | * On Friday, we will review the use cases and identify those that have admin like function and associate the ER. |
Revision as of 12:20, 6 February 2008
Contents
Attendees
Minutes
Integration Build
- i9 build changed to run on Tomcat. Still a few problems with the annotation code that Joel is working on. Target is next Tuesday for the integration build. We are targeting Friday for this to be complete.
- Srinivas is not able to download the integration build. He will open a P1 bug and get Jagmit to fix this.
- There were three issues with the linux builds, however we should be able to smoke test this build to verify. However, b/c of a few bugs, we may want to try last week's build.
- Log files sizes
- Configuration
- "/" vs. "\"
- This build is less stable than last week's build.
- Registration of MDRs to brokers will not work b/c of annotation bug that Joel is targeted to fix by Friday.
- New features in this week's build include Metadata.
- Joel will open a bug on IPv6 and how Muse handles the host name resolution. Target is a plan of action by Friday.
command line or web UI to manage COSMOS components?
QA Discussion
- Everyone must read over this process. We will close on Friday: Speak then or forever hold your peace.
CMDBf Registration APIs
How to keep the integrity of the data b/t the federating CMDB and the MDR?
command line or web UI to manage COSMOS components?
- For i9, we are going to keep what we have and only fix things that are broken.
- We will need to refactor the code to formalize the admin service. This will be done in i10.
- On Friday, we will review the use cases and identify those that have admin like function and associate the ER.