Please find the attached slides on agenda to discuss today.
I will need inputs from each reference implementation.
Thanks,
Jun Tatemura
NEC Laboratories America
I am pleased to announce the availability of the HP CDDLM endpoint,
public beta
release
The URL for the portal is :-
http://deployapi.iseran.com:8080/alpine/portal/
It is visible through the (three) firewalls, and has been tested remotely.
A GET will return a short note confirming the endpoint's existence. Make
sure
you have the trailing / as the servlet is unforgiving. If the connection
is refused, the endpoint is probably down.
Notes
-this is a new SOAP stack with its own WSA and WSRF implementation. It only
implements the subset we need, and those are not adequately interop
tested.
please mail your results to the group or direct to me.
-deployment is not working. I will find out why next week, but will then
have to actually implement security on the endpoint before deploying a
fixed
version
-System:addFile is not finished, and when it is it will initially only
support
inline (base 64) content, not attachments. MTOM Is not on the todo list.
-WS-Notification has not even begun; I dont even implement the
properties that
list supported topics. Frankly, I'm not overwhelmingly motivated to
implement
WS-N.
-It's hosted on a laptop on the WLAN somewhere in my house. It needs more
memory. Please be gentle with it :)
Monday in the UK is a holiday (May 1st, Socialist Unity Day!), so there
is no
likelihood of any changes to the stack being made before Tuesday. I'll field
basic interop problems first (namespaces, WSA headers, SOAPAction), then
worry
about
-better fault reporting
-automating a checkout, rebuild and redeploy early every morning.
-testing Alpine's WSA impl. against the .NET 2.0 endpoints
-making the server-side logs public by logging to log4j's HTML logger and
serving those pages up somewhere.
-have the server host the deployapi tests for our client and run them
against
all public stacks, again serving the data up for browsing.
Clearly not all of these can be achieved in the finite time before
GGF17, but we
should be able to make progress along both the interop and functionality
axes. Now if you'll excuse me, I have an extended weekend to attend to.
Steve
Hi Team,
Hiro will join us next meeting to discuss the topic addressed in the
email below (SDD and ACS/CDDLM/JSDL). This will be a good opportunity to
ask Hiro about his position wrt interoperability and standardization, as
well as about other topics. BTW Hiro is the member of the CDDLM mailing
list, so you can start any discussion using email.
Best regards,
Dejan.
> -----Original Message-----
> From: Hiro Kishimoto [mailto:hiro.kishimoto@jp.fujitsu.com]
> Sent: Sunday, April 30, 2006 11:22 PM
> To: Milojicic, Dejan S (HP Labs)
> Cc: Stuart Schaefer; Jun Tatemura
> Subject: Re: OASIS SDD-TC
>
> Thanks Dejan,
>
> I agree with you. Please discuss at your meeting. I can join to answer
> any question from your group if you like.
>
> It is May 3rd Wednesday 6am PDT (= 10pm JST), right?
>
> Thanks again,
> ----
> Hiro Kishimoto
>
> Milojicic, Dejan S (HP Labs) wrote:
> > Thanks Hiro,
> >
> > I personally think that this is a good idea. Please let us discuss
> > this as a team at the next Wednesday meeting and I will get back to
> > you thereafter. Again, personally I think that this is the right
> > approach, but we are used to make decisions as a team and I
> prefer to
> > do it this way again.
> >
> > Best regards,
> >
> > Dejan.
> >
> >> -----Original Message-----
> >> From: Hiro Kishimoto [mailto:hiro.kishimoto@jp.fujitsu.com]
> >> Sent: Saturday, April 29, 2006 5:39 PM
> >> To: Dejan Milojicic; Stuart Schaefer; Jun Tatemura
> >> Subject: OASIS SDD-TC
> >>
> >> Hi Dejan, Stuart, and Jun,
> >>
> >> As you may already heard form Jun, OASIS SDD-TC (they are
> working on
> >> closely related technology; solution installation) is now
> calling for
> >> submission.
> >>
> >> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sdd
> >> http://lists.oasis-open.org/archives/sdd/200604/msg00027.html
> >> http://www.oasis-open.org/committees/download.php/17882/oasis-
> >> sdd-requirements-v1.1.doc
> >>
> >> Although their focus is non-grid domain, the last thing I
> would see
> >> is GGF and OASIS will publish two incompatible deployment
> standards
> >> and thus impose a unnecessary burden on both end users and
> software
> >> providers.
> >>
> >> In order to avoid such worst case scenario, I think GGF should
> >> provide related GGF specifications for SDD-TC and ask them to
> >> consider.
> >> It does not mean CDDLM-WG should work with SDD-TC and modify or
> >> update your specs to meet their needs. Instead, just ask SDD-TC to
> >> make their spec compatible with CDDLM and another GGF's specs.
> >>
> >> The following is the list of GGF's specs we would like to offer;
> >>
> >> (1) Application Contents Service Specification 1.0
> >> (2) CDDLM XML-CDL
> >> (3) CDDLM component model
> >> (4) Job Submission Description Language 1.0
> >> (SDD-TC also covers required resource description)
> >>
> >> We exclude CDDLM Deployment API since SDD-TC does not
> cover interface
> >> specification.
> >>
> >> It is very important for OGSA and GGF in general to keep
> consistent
> >> with wider Web service community. For this reason, ACS-WG
> and JSDL-WG
> >> already agree to the above plan and we would like to hear your
> >> thoughts.
> >>
> >> Thanks,
> >> --
> >> Hiro Kishimoto
> >>
> >>
> >
> >
>
>
