1 / 9

KSU CCM Workshop Future Collaboration Plans

KSU CCM Workshop Future Collaboration Plans. May 20, 2003. http://www.cis.ksu.edu/santos/KSU-CCM-Workshop. Cadena/CIAO Integration (PI Meeting). must be done manually by CIAO team. Cadena will spit out CCM .cad format (we will have this working by May 20). Cadena. CIAO. BasicSP. IDL3.

anthony-cabrera
Download Presentation

KSU CCM Workshop Future Collaboration Plans

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. KSU CCM WorkshopFuture Collaboration Plans May 20, 2003 http://www.cis.ksu.edu/santos/KSU-CCM-Workshop

  2. Cadena/CIAO Integration (PI Meeting) must be done manually by CIAO team Cadena will spit out CCM .cad format (we will have this working by May 20) Cadena CIAO BasicSP IDL3 CIDL deployment and configuration Interaction Points KSU CCM Workshop --- Reconciling the Boeing OEP and CCM

  3. Step I • BasicSP • IDL3 • Cadena spits it out • Run through CIAO IDL3 compiler • CIDL • currently not emitted by Cadena, but can be accomplished by traditional editing facilities • Packaging & Deployment • Cadena spits out CCM .cad (May 20) • Purpose: • demonstrate collaboration for PI meeting KSU CCM Workshop --- Reconciling the Boeing OEP and CCM

  4. Step II Context/ Container • Configurable containers for incorporating middleware communication layers • initial draft by Gurdip et. al. (May 30) • feedback and iteration (June, July) • stable proposal (end of July) • Purpose • needed to incorporate RT event-channel in a robust way XML info about communication paths, e.g., event-channel, data service KSU CCM Workshop --- Reconciling the Boeing OEP and CCM

  5. Step III • CCM .cad + initial RT/QoS properties • start with proposal by Venkatesh • incorporate feedback from Boeing/CIAO • draft with incorporating feedback from Boeing by PI meeting (June 4) • …continue with entire deployment framework through summer • Purpose • force us to… • agree on how to configure RT aspects of event channel required from OEP • allow us to scale to process rest of Boeing scenarios (for next PI meeting!) KSU CCM Workshop --- Reconciling the Boeing OEP and CCM

  6. Later Steps • Programmatic interfaces for Cadena so that CIAO could be “fully integrated” • Provide Bogor models and evidence of their effectiveness on Boeing scenarios for people to evaluate • Identify specialized uses of event-channel for particular use-cases • Full specification of priority-correlation in the context of the Boeing scenarios • Cadena property file and analysis tools (dependency and model-checking) integrated in GME • Collection of property specifications to show to Boeing along with further probing for more complex/useful properties • Beginning to prepare for PCES II OEP • at some point, need to move beyond current Boeing scenarios • Refactoring scheduling and other services to expose policies and mechanisms that can be specified/captured in modeling tools KSU CCM Workshop --- Reconciling the Boeing OEP and CCM

  7. PI meeting presentation • KSU ends with integration slide, which is then talked to by Vanderbilt and Wash U KSU CCM Workshop --- Reconciling the Boeing OEP and CCM

  8. Working Groups • Container configuration • .cad XML extensions • Model-checking (Bogor, GME) KSU CCM Workshop --- Reconciling the Boeing OEP and CCM

  9. Tonight… KSU CCM Workshop --- Reconciling the Boeing OEP and CCM

More Related