[ogsa-wg] Proposed agenda for June 29th call
Frank Siebenlist
franks at mcs.anl.gov
Wed Jun 28 02:11:28 CDT 2006
I'm on the road this Thursday and unable to call-in.
The internal authz call-out interface discussion has so far yielded 23
email messages in the last couple of days among David, Von and myself
without any clear decisive stated direction yet - please bear with us
while we struggle to find the right PATH.
-Frank.
Hiro Kishimoto wrote:
> Hi all,
>
> The following is a proposed agenda for OGSA-WG telecon on June 29th.
> Thursday from 8:30am - 10:30am (CDT).
>
> Dial-in numbers for Thursday:
> Free: +1-888-452-0308
> Intl/Toll: +1-484-644-0505
> PIN: 71815
>
> Screen share service will be provided.
> URL: http://ogsa.glance.net
> Session key: 0629
> See more explanation:
> http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html
>
> 1) Early discussion (20 min)
> Note taker assignment
> Roll call
> Telecon minutes approval (June 22 & 29)
> - https://forge.gridforum.org/sf/go/doc13624?nav=1
> - https://forge.gridforum.org/sf/go/doc13628?nav=1
> Action Items status review (see the bottom of this email)
> July F2F and GGF18 plan update (if any)
> Agenda bashing
>
> 2) CDDLM & EMS joint discussion (Jun and Hiro, 30 min)
> Jun and Hiro will send out revised material before the call.
>
> minutes form July 12 call
>> - Reviewed Hiro's presenation and XML documents.
>>
>> - Jun pointed out that codebase is used incorrectly. It should be
>> used in the BLAST declaration not in the PosixApplication.
>> - Also it is not clear what the meaning of pre-script is.
>> ACTION: Hiro to talk with Chris Smith and clarify meaning of
>> pre-script
>> ACTION: Jun will correct the CDL XML examples written by Hiro.
>>
>> - What should be the granular unit of components?
>> - It may be better to define 'filesystem' or 'database' as
>> separate components since they may be re-usable in other
>> contexts. For example, they might be usable also by a 3-tier
>> application component.
>> - It was agreed that this kind of refinement is needed. But it is
>> not a showstopper for delivering the top level CDL for the EMS
>> sequence scenarios.
>>
>> - For the EMS scenarios the following CDL documents are needed:
>> - Original CDL from the repository;
>> - CDL modified by JM before submission to Deployment service
>> (portal)
>> - CDL after deployment (can be retrieved by JM to refine the JSDL
>> document)
>> [The deltas should be fairly small.]
>> - Some explanation on what the constructs in the CDL document mean
>> would also be useful since not everyone will have read the CDDLM
>> documents.
>> - Also highlighting what information (if any) is expected to taken
>> from the JSDL document and used in CDL (and vice versa)
>> - In the simplest case it is 'hostname' and path to the installed
>> executable.
>> - Andreas volunteered to review these CDL documents before the EMS
>> call to make sure they provide the expected information.
>
> 3) EMS scenarios (Steven and Andreas, 30 min)
> Andreas will send out revised scenario document before the call
>
>> - EMS team (Steven, Andreas, Donal) to review data staging scenario
>> (section 5 of https://forge.gridforum.org/sf/go/doc13591?nav=1 )
>> Bring to people's attention again at the next EMS call.
>> (postpone until June 29)
>> - Add sequence diagrams to the scenarios: (postpone until June 29)
>> - Andreas will do the "Install application" scenario (3.1)
>> - Mike will do the "Install application using ACS" scenario (3.3)
>> - Other volunteers welcome. (Andreas will ask Donal for the EPS
>> scenario)
>> - Andreas has started doing the sequence diagrams in RSM
>> - Darren volunteered to help out
>> - Review again at the next EMS call (June 29)
>> - Andreas will merge draft scenarios and sequence diagrams to the
>> "EMS Architecture Scenarios" document (postpone until June 29)
>
> 4) OGSA authorization call-out proposal review (Frank 20 min)
> > - Frank is now consulting with people in GGF (David Chadwick, Von
> > Welch) on whether his approach can be defined within the AuthZ
> > group. If there is no agreement then he will accept the XACML
> > group's decision.
>
> 5) Basic Security Profile Public Comments review (Takuya 20 min)
> Takuya will send out proposed text change before the call
>
> Minutes from June 22nd call
>> Reviewed public comments and Takuya's proposed replies
>> 1. Add text explaining that the Secure Channel profile is not
>> required by all ogsa services. The introduction is probably a
>> good place for this.
>> 2. [Basic-Security-Profile] usage. The term is defined in the
>> document. Takuya to check whether such special terms are used
>> consistently and that they stand out. Refer to the WSRF BP for a
>> similar example.
>> 3. Ciphersuites: Agreed that it important to list acceptable
>> ciphers.
>> - As a first step Takuya will list up available ones (from the
>> WS-I BSP); select the ones that are in common use; and then
>> select the ones that are considered sufficiently safe.
>> - Review the list at the next BSP teleconf
>> 4. Multiple keys in keyinfo field?
>> - Takuya to talk to Von in order to understand the use case for
>> multiple keys; and will propose a resolution at the next BSP
>> teleconf.
>
> 6) Wrap up
> AOB
>
> <*NEXT CALL*>
> July 3 (Mon): Independence day (no call)
> July 6 (Thu): EMS scenarios (Steven and Andreas)
> July 10 (Mon): Information model (Ellen and Fred)
> Roadmap 1.1 (Hiro, ChrisJ, and Jem)
> Security & BSP Public Comments review (Frank and Takuya)
> CDDLM & EMS (Jun and Hiro)
> July 13 (Thu): F2F prep (Tom and Hiro)
> July 17-20: F2F meeting in Chicago (ANL)
>
> Telecon schedule on wiki:
> https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/TeleconSchedule
>
>
> <*ACTION ITEMS*>
> > From June 26 call
> - Hiro to confirm contact with (ex-)EGA TC
>
> > From June 12 call
> - Jun will correct the CDL XML examples written by Hiro.
>
> > From June 8 call
> - EMS team (Steven, Andreas, Donal) to review data staging scenario
> (section 5 of https://forge.gridforum.org/sf/go/doc13591?nav=1 )
> Bring to people's attention again at the next EMS call.
> (postpone until June 29)
> - Add sequence diagrams to the scenarios: (postpone until June 29)
> - Andreas will do the "Install application" scenario (3.1)
> - Mike will do the "Install application using ACS" scenario (3.3)
> - Other volunteers welcome. (Andreas will ask Donal for the EPS
> scenario)
> - Andreas has started doing the sequence diagrams in RSM
> - Darren volunteered to help out
> - Review again at the next EMS call (June 29)
> - Andreas will merge draft scenarios and sequence diagrams to the
> "EMS Architecture Scenarios" document (postpone until June 29)
>
> > From May 22 call
> - Jay will contact Platform (Chris Smith) and Condor (Miron Livny)
> to get feedback on pros / cons of the two rendering approaches
> (postpone until June 19)
> - Darren/Andreas will take the Modeling position paper and
> discuss it within the JSDL-WG as well (postpone until June 19)
>
> > From April 5 F2F meeting
> - Marvin to send e-mail that explains concerns on compliance suite
> by GGF & EGA.
>
> Deferred
> - Frank to write up and send to the list a one page summary of
> the authorization call-out proposal.
> (April 24 call, postpone until June 14)
> - Jay check and find out relatively small funding to Globus
> to develop document on their security work (April 6 F2F)
> - Hiro to schedule a discussion in the OGSA F2F after the
> converged specs drafts are released to discuss which sets of
> specs to use within OGSA. (April 4 F2F)
--
Frank Siebenlist franks at mcs.anl.gov
The Globus Alliance - Argonne National Laboratory
More information about the ogsa-wg
mailing list