airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Danushka Menikkumbura <danushka.menikkumb...@gmail.com>
Subject Re: Decoupling GFac Providers
Date Tue, 05 Mar 2013 05:28:51 GMT
Hi Lahiru,

Yes. That is what I meant. Can we incorporate HostDescriptionType with it?

Thanks,
Danushka


On Tue, Mar 5, 2013 at 10:46 AM, Lahiru Gunathilake <glahiru@gmail.com>wrote:

> Hi Danushka,
>
> We already have a provider configuration file (gfac-config.xml) if this is
> what you meant. Please have a look in to LocalProviderTest to see how it
> works.
>
> Regards
> Lahiru
>
> On Tue, Mar 5, 2013 at 12:07 AM, Danushka Menikkumbura <
> danushka.menikkumbura@gmail.com> wrote:
>
> > Hi Suresh,
> >
> > I agree with Amila, we should not get any implementation details into
> > > schemas. The Schemas are a contract between user and the system. Its
> > within
> > > the system how it executes the task user wants to accomplish. These
> > schemas
> > > are completely agnostic to how Airavata talks to a system. For
> instance,
> > > user should be able to say, I want to run a job on Amazon and the host
> > > description has EC2 end points. But we should not at that level
> > > describe/tag classes on how Airavata talks to EC2.
> > >
> >
> > I get your point. Makes sense.
> >
> > Then the other option would be to have provider implementation details
> > defined in a configuration file (airavata.xml?).
> >
> > Thanks,
> > Danushka
> >
>
>
>
> --
> System Analyst Programmer
> PTI Lab
> Indiana University
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message