Aperi Development Status Meeting 08/25/08

From Eclipsepedia

Jump to: navigation, search

Aperi Wiki Home Aperi Meetings Aperi Development Meetings

Dial in numbers:

Toll Free: 877-421-0029 International: 770-615-1246 Passcode: 003399

Attendees:

IBM (Al Heitman, Dave Wolfe, Todd Singleton, Chris King)

Minutes:

  • Project Leader Notes:
    • Announcements
      • Todd is leaving IBM for a new opportunity and therefore leaving the Aperi project. Al thanked Todd for all his hard work and dedication to the Aperi project over the years. Todd was one of the original members of the Aperi team. We wished Todd good luck in his next career. We are actively seeking a replacement for Todd.
      • Al and Todd completed the hand-off of the build responsibilities last week.
      • There were some other changes in the Aperi M5 resource plan. There will be a delay in the staffing ramp up that was to occur in Sept. Himanshu will no longer be joining the Aperi team. There will be another person moved over to Aperi that has yet to be named.
      • Al is working on impacts to the milestone 5 release and pulling together a replan. Based on some replacement assumptions and learning curves, Al indicated that it looks like a 2 month delay in milestone 5.
    • Installer Issue
      • Issues surfaced in June that Eclipse installers are not allowed to download non-approved 3rd party libraries.
      • Al submitted IPzilla Contribution Questionnaire for Apache Geronimo. Eclipse needs the source code for the jar file we want to include. Al is working on parsing down the source zip. It may take a while as there are about 2500 files in the jar Aperi is using.
      • DoJo not approved. Martine and Dave have a proposal to take out that functionality that reqs DoJo. They plan to review the plan. Al will add 5 day item to schedule to remove DoJo dependency in m5 plan.
    • Misc. Project Info
    • 2008 planning (R0.5)
      • Still need milestones for Virtual Fabric / FC Security spec. from Brocade. Al sent a request to John for milestone details.
      • Still need milestones for Linux HA Cluster support from Novell. Al sent a request to Robert for any milestone details.
      • Al working on schedule update to show planned iterations. Al just published an update with the plans for the SSO/SRM framework update. However, with the staffing impacts, the latest schedule is going to change. Dave is working on the details of LIC iteration plan.
      • Martine has action item to take the SMIS serialization scheme to convert SMIS CIM LIC spec. and map that back to the LIC schema. He is working with Dave to determine which route Aperi should take in m5.
    • Aperi Committers:
      • The following committers still need the legal “paperwork” completed before full committer access is granted.
        • John Crandall
        • Jenny Monesson
  • Release Engineer Notes (Todd):
    • Build status/process
      • Ramani indicated that the CVS SAN Simulator build doesn’t match their local build. Todd fixed the SAN Simulator and posted to website last week. Todd sent a note to Ramani to see if the build is ok.
  • Aperi Downloads:
    • August totals are 314 downloads so far this month with 183 for the SRM Application and 131 for the SAN Simulator.
    • Latest stats
  • Development items/issues:
    • SSO – Todd complete the STS client code and checked it in. He is going to update the client to the latest Higgins code this week. Todd also posted a “how to” document to the Aperi wiki but has to make an update based on the latest Higgins code. He has 3rd party libraries from the Eclipse Higgins project that will need CQ’s submitted to get Eclipse IP approval for the Aperi project. Todd sent Al the list and Al started investigating previous CQ’s. There are 28 jars that are introduced so Al started a spreadsheet to keep track of the list. Todd will update the how to documentation for the latest Higgins war file. Todd will document how to update the SRM application launch points to enable use of the info card and SSO.
    • LIC – Dave is working on a rollout plan for the LIC. Al will work with Dave to update the project plan to incorporate the additional rollout items and task details. Martine is working with SNIA to make non-CIM based clients compatible with CIM based ones. Dave started the effort with the CMS based approach. However, when Martine went to SNIA for CIM SMIS LIC update, one of the side conversations is to standardize the XML spec. for non CIM based clients. One suggestion is to serialize the CIM into XML, then no need for the CMS based model and the implementations are compatible. Martine and Dave will make a decision this week, to either go with serialized CIM SMIS based XML or the CMS based mode.
    • SAN Simulator - The code is checked into CVS. Todd completed the final build last week. We need to get committer community to do a code review before we release it. Al asked Ramani to initiate the code review via the Aperi-Dev.
    • Java Help – Chris/TBD - This activity is scheduled to start in the next few weeks. Al mentioned that the scheduling of this item may move around in the replan work. Chris can start on his items and the conversions prior to the development item.
    • Virtual Fabric / FC Security spec – need update from John.
    • Linux HA cluster support – need update from Robert.
  • IDVT:
  • ID:
    • Chris has completed the Aperi M5 ID plan. He put a version out on wiki and sent the request for a review out to Aperi-Dev. The review closed last Friday. Chris will displace the review comments and put the log out on the wiki. Chris plans to start the approval process this week.
  • Project Schedule:
  • Action Items:
Item Owner Target Status
Obtain two mentors Al 08/31/08 Per new development process rules, we need to obtain two project mentors. Harm Sluiman is one. Discussed with Tom last week. Bjorn has a list of mentors we can use. Al to follow up with Bjorn.
Document Control Al 08/31/08 Write up text for Aperi document control. Al wrote up a proposal process to review documents here -> http://wiki.eclipse.org/Document_Review_and_Approval_Process. Al initiated a review on Aperi-Dev. Comments are starting to come in. Once the review is complete and the comments are displaced, Al will initiate a vote to adopt the process.