airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saminda Wijeratne <samin...@gmail.com>
Subject Re: Separation out Server & Client binary distributions in Airavata
Date Thu, 29 Nov 2012 18:30:49 GMT
Thanks Amila. I created a jira task[1] for you to provide the patch for
this.

Saminda

1. https://issues.apache.org/jira/browse/AIRAVATA-669

On Thu, Nov 29, 2012 at 12:54 PM, Amila Jayasekara
<thejaka.amila@gmail.com>wrote:

> I am working on changing distribution. I will work on this.
>
> Thanks
> Amila
>
> On Thu, Nov 29, 2012 at 12:25 PM, Lahiru Gunathilake <glahiru@gmail.com>
> wrote:
> > I am +1 for this and this is very clean and ideally nobody is going to
> use
> > airavata pack right away so providing these in separate would make life
> > easier for users to use three component separately.
> >
> > Thanks Saminda for bringing this up.
> >
> > Lahiru
> >
> > On Thu, Nov 29, 2012 at 12:22 PM, Saminda Wijeratne <samindaw@gmail.com
> >wrote:
> >
> >> Hi Devs,
> >>
> >> Currently we have both XBaya & the Airavata services bundled together
> when
> >> we create the final distribution. This can arise confusion to the users
> &
> >> unnecessary overhead of retrieving/understanding/configuring for
> different
> >> stakeholders. Shall we have different distributions as follows?
> >>
> >>
> >>    1. Airavata server binary distribution  - everything related to
> hosting
> >>    an Airavata Server
> >>    2. XBaya binary distribution              - everything needed for
> XBaya
> >>    to run independently
> >>    3. Airavata client binary distribution   - all the libraries required
> >>    for a 3rd party client to use the Airavata API
> >>
> >>
> >> (This would mean that we'll have 3 binary packs for an Airavata release)
> >>
> >> Regards,
> >> Saminda
> >>
> >
> >
> >
> > --
> > System Analyst Programmer
> > PTI Lab
> > Indiana University
>

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