You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Suresh Marru <sm...@apache.org> on 2012/12/01 05:54:31 UTC
Re: Separation out Server & Client binary distributions in Airavata
A big + 1, this was long overdue. Thanks Saminda and Amila for initiating and jumping onto this.
We may also want to consider creating the JNLP as part of the default build. For instance, we can have a associated JNLP bundled with the server. That way we can have users directly click on JNLP and launch XBaya which is pointed to the server.
Cheers,
Suresh
On Nov 29, 2012, at 12:22 PM, Saminda Wijeratne <sa...@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
Re: Separation out Server & Client binary distributions in Airavata
Posted by Lahiru Gunathilake <gl...@gmail.com>.
Hi All,
Please be patient with me, I am doing bunch of commits related to
distribution changes. please do not take svn up for next half an hour.
Regards
Lahiru
On Wed, Dec 5, 2012 at 12:29 PM, Lahiru Gunathilake <gl...@gmail.com>wrote:
> Hi Suresh,
>
> On Wed, Dec 5, 2012 at 11:59 AM, Suresh Marru <sm...@apache.org> wrote:
>
>> Great!!. Do you also plan to have maven profiles for these three? You can
>> see the usage of checking out source and only building client or xbaya and
>> so on?
>>
> Yes, thats my plan, initially I will add all three in to default build and
> later will define a build profile for each distribution.
>
> Lahiru
>
>>
>> Suresh
>>
>> On Dec 5, 2012, at 11:54 AM, Lahiru Gunathilake <gl...@gmail.com>
>> wrote:
>>
>> > Since Amila is busy with integration tests, I can work on having
>> multiple
>> > build distribtuions. My plan is to have three separate directories in
>> > distribution and build these above three packs on them.
>> >
>> > Those would be airavata-server, xbaya-gui, airavata-client .. inside
>> > distribution folder.
>> >
>> >
>> > Thanks
>> > Lahiru
>> > On Fri, Nov 30, 2012 at 11:54 PM, Suresh Marru <sm...@apache.org>
>> wrote:
>> >
>> >> A big + 1, this was long overdue. Thanks Saminda and Amila for
>> initiating
>> >> and jumping onto this.
>> >>
>> >> We may also want to consider creating the JNLP as part of the default
>> >> build. For instance, we can have a associated JNLP bundled with the
>> server.
>> >> That way we can have users directly click on JNLP and launch XBaya
>> which is
>> >> pointed to the server.
>> >>
>> >> Cheers,
>> >> Suresh
>> >>
>> >> On Nov 29, 2012, at 12:22 PM, Saminda Wijeratne <sa...@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
>>
>>
>
>
> --
> System Analyst Programmer
> PTI Lab
> Indiana University
>
>
--
System Analyst Programmer
PTI Lab
Indiana University
Re: Separation out Server & Client binary distributions in Airavata
Posted by Lahiru Gunathilake <gl...@gmail.com>.
Hi Suresh,
On Wed, Dec 5, 2012 at 11:59 AM, Suresh Marru <sm...@apache.org> wrote:
> Great!!. Do you also plan to have maven profiles for these three? You can
> see the usage of checking out source and only building client or xbaya and
> so on?
>
Yes, thats my plan, initially I will add all three in to default build and
later will define a build profile for each distribution.
Lahiru
>
> Suresh
>
> On Dec 5, 2012, at 11:54 AM, Lahiru Gunathilake <gl...@gmail.com> wrote:
>
> > Since Amila is busy with integration tests, I can work on having multiple
> > build distribtuions. My plan is to have three separate directories in
> > distribution and build these above three packs on them.
> >
> > Those would be airavata-server, xbaya-gui, airavata-client .. inside
> > distribution folder.
> >
> >
> > Thanks
> > Lahiru
> > On Fri, Nov 30, 2012 at 11:54 PM, Suresh Marru <sm...@apache.org>
> wrote:
> >
> >> A big + 1, this was long overdue. Thanks Saminda and Amila for
> initiating
> >> and jumping onto this.
> >>
> >> We may also want to consider creating the JNLP as part of the default
> >> build. For instance, we can have a associated JNLP bundled with the
> server.
> >> That way we can have users directly click on JNLP and launch XBaya
> which is
> >> pointed to the server.
> >>
> >> Cheers,
> >> Suresh
> >>
> >> On Nov 29, 2012, at 12:22 PM, Saminda Wijeratne <sa...@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
>
>
--
System Analyst Programmer
PTI Lab
Indiana University
Re: Separation out Server & Client binary distributions in Airavata
Posted by Suresh Marru <sm...@apache.org>.
Great!!. Do you also plan to have maven profiles for these three? You can see the usage of checking out source and only building client or xbaya and so on?
Suresh
On Dec 5, 2012, at 11:54 AM, Lahiru Gunathilake <gl...@gmail.com> wrote:
> Since Amila is busy with integration tests, I can work on having multiple
> build distribtuions. My plan is to have three separate directories in
> distribution and build these above three packs on them.
>
> Those would be airavata-server, xbaya-gui, airavata-client .. inside
> distribution folder.
>
>
> Thanks
> Lahiru
> On Fri, Nov 30, 2012 at 11:54 PM, Suresh Marru <sm...@apache.org> wrote:
>
>> A big + 1, this was long overdue. Thanks Saminda and Amila for initiating
>> and jumping onto this.
>>
>> We may also want to consider creating the JNLP as part of the default
>> build. For instance, we can have a associated JNLP bundled with the server.
>> That way we can have users directly click on JNLP and launch XBaya which is
>> pointed to the server.
>>
>> Cheers,
>> Suresh
>>
>> On Nov 29, 2012, at 12:22 PM, Saminda Wijeratne <sa...@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
Re: Separation out Server & Client binary distributions in Airavata
Posted by Lahiru Gunathilake <gl...@gmail.com>.
Since Amila is busy with integration tests, I can work on having multiple
build distribtuions. My plan is to have three separate directories in
distribution and build these above three packs on them.
Those would be airavata-server, xbaya-gui, airavata-client .. inside
distribution folder.
Thanks
Lahiru
On Fri, Nov 30, 2012 at 11:54 PM, Suresh Marru <sm...@apache.org> wrote:
> A big + 1, this was long overdue. Thanks Saminda and Amila for initiating
> and jumping onto this.
>
> We may also want to consider creating the JNLP as part of the default
> build. For instance, we can have a associated JNLP bundled with the server.
> That way we can have users directly click on JNLP and launch XBaya which is
> pointed to the server.
>
> Cheers,
> Suresh
>
> On Nov 29, 2012, at 12:22 PM, Saminda Wijeratne <sa...@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