You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Shameera Rathnayaka <sh...@gmail.com> on 2013/06/01 05:34:27 UTC
Re: "Monitoring and Messaging" Framework
Hi Danushka et.al,
I am working on defining a standard to convert JSON to XML and a suitable
method to do the conversion back and forth without any loss. I went through
some XSD's of Airavata backend and found that some elements have been
defined with some attributes ( i.e, "application-scheduling-context"
element in workflow_execution_context.xsd expect 10 attributes with it,
Hope this is not a deprecated XSD) therefore we need to address this issue
too. Most probably I can come up with an initial draft of this standard by
next couple of days. We can initiate a discussion based on the draft and
come to a final solution. After that we can do our works parallel .
Thanks,
Shameera.
On Sat, Jun 1, 2013 at 12:14 AM, Danushka Menikkumbura <
danushka.menikkumbura@gmail.com> wrote:
> Guys,
>
> I think we would end up emulating XBaya at some point down the line. In
> fact it could be something similar to what Creately [1] provides.
>
> Anyway we need to get few things straight in the first place.
>
> 1. Have an object model similar to that of XBaya so that it is possible to
> edit/run workflows done using XBaya on the Web UI and vice versa.
>
> 2. Develop a basic UI framework so that others can build on top of it. This
> would include different types of widget, menus, log/status windows, etc.
>
> 3. The protocol conversion layer (JSON/XML) that needs to be developed in
> parallel.
>
> 4. Make the UI extensible so that new components, etc could be added with
> relatively little effort.
>
> [1] - https://creately.com/app/?tempID=h165rwt81#
>
> Lets discuss and come up with a plan as having a solid architecture/base
> would pay off for sure.
>
> Thanks,
> Danushka
>
>
> On Fri, May 31, 2013 at 9:43 PM, Sanchit Aggarwal <
> sanchitagarwal108@gmail.com> wrote:
>
> > Hi
> > I think keeping in mind the current implementation of the Xbaya, it
> > would be good if we stick to single page web app with each of us
> > having our custom modules.We all can come up with a design which can
> > be used for all the interfaces, it will save the amount of time spend
> > for designing a page from scratch.
> >
> > Regards
> > Sanchit Aggarwal
> >
> >
> >
> > On Fri, May 31, 2013 at 9:21 PM, Subho Banerjee <su...@gmail.com>
> > wrote:
> > > Hi,
> > > I had one small query, are all of us (those working on the front end)
> > > working on a single page web app.
> > >
> > > Or will each of us have a page which we will design form top to bottom.
> > >
> > > In any case, maybe we can also agree on some common format to reuse the
> > > objects, so that we do not code replication.
> > >
> > > Cheers,
> > > Subho.
> > >
> > >
> > > On Fri, May 31, 2013 at 8:48 PM, Suresh Marru <sm...@apache.org>
> wrote:
> > >
> > >> Here are the all the proposals, please enable the public option, if
> you
> > >> haven't previously:
> > >>
> > >> Dunushka -
> > >>
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/danushka/1
> > >> Subho -
> > >>
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/subhobanerjee/13001
> > >> Vijayendra -
> > >>
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/vijayendra_purohit/33001
> > >> Sanchit -
> > >>
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/sanchitaggarwal/24001
> > >> Shameera -
> > >>
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/shameera/60002
> > >> Viknes -
> > >>
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/vikbalas/1
> > >>
> > >> Suresh
> > >>
> > >>
> > >> On May 31, 2013, at 11:15 AM, Danushka Menikkumbura <
> > >> danushka.menikkumbura@gmail.com> wrote:
> > >>
> > >> > Please check now. Sorry about that.
> > >> >
> > >> > Danushka
> > >> >
> > >> >
> > >> > On Fri, May 31, 2013 at 6:40 PM, Sanchit Aggarwal <
> > >> > sanchitagarwal108@gmail.com> wrote:
> > >> >
> > >> >> Hi Danushka
> > >> >>
> > >> >> It seems that your proposal is not public. can you please set it to
> > >> public.
> > >> >>
> > >> >> Regards
> > >> >> Sanchit Aggarwal
> > >> >>
> > >> >>
> > >> >>
> > >> >> On Fri, May 31, 2013 at 5:14 PM, Danushka Menikkumbura
> > >> >> <da...@gmail.com> wrote:
> > >> >>> Hi Vijayendra,
> > >> >>>
> > >> >>> That's great!.
> > >> >>>
> > >> >>> BTW where to get some insight into what you are trying to do in
> the
> > >> first
> > >> >>> place?. Maybe your proposal would do.
> > >> >>>
> > >> >>> Please find mine at [1]. Please go through sections 1.4, 1.5 and
> > 1.6 to
> > >> >> get
> > >> >>> a very high-level idea of what we are planning to do in terms of
> > >> >> supporting
> > >> >>> AMQP in WS-Messenger.
> > >> >>>
> > >> >>> [1] -
> > >> >>>
> > >> >>
> > >>
> >
> https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/danushka/1
> > >> >>>
> > >> >>> Thanks,
> > >> >>> Danushka
> > >> >>>
> > >> >>>
> > >> >>> On Fri, May 31, 2013 at 4:34 PM, Vijayendra Grampurohit <
> > >> >>> vijayendra.sdm@gmail.com> wrote:
> > >> >>>
> > >> >>>> Hi Dhanushka/All
> > >> >>>>
> > >> >>>> I will be involved in one of the sub-project under "Monitoring
> and
> > >> >>>> Messaging". As you are handling "AMQP Messaging protocol support
> > for
> > >> >>>> Airavata WS-Messenger", We need to come up with framework for
> > message
> > >> >>>> monitoring. Can we all start discussing here?
> > >> >>>>
> > >> >>>> Regards
> > >> >>>> Vijayendra
> > >> >>>>
> > >> >>
> > >>
> > >>
> >
>
--
Best Regards,
Shameera Rathnayaka.
email: shameera AT apache.org , shameerainfo AT gmail.com
Blog : http://shameerarathnayaka.blogspot.com/
Re: "Monitoring and Messaging" Framework
Posted by Danushka Menikkumbura <da...@gmail.com>.
Hi Shameera,
Sounds good.
Looking forward to it. Lets do a PoC once it is finalized.
Thanks,
Danushka
On Sat, Jun 1, 2013 at 9:04 AM, Shameera Rathnayaka
<sh...@gmail.com>wrote:
> Hi Danushka et.al,
>
> I am working on defining a standard to convert JSON to XML and a suitable
> method to do the conversion back and forth without any loss. I went through
> some XSD's of Airavata backend and found that some elements have been
> defined with some attributes ( i.e, "application-scheduling-context"
> element in workflow_execution_context.xsd expect 10 attributes with it,
> Hope this is not a deprecated XSD) therefore we need to address this issue
> too. Most probably I can come up with an initial draft of this standard by
> next couple of days. We can initiate a discussion based on the draft and
> come to a final solution. After that we can do our works parallel .
>
> Thanks,
> Shameera.
>
>
> On Sat, Jun 1, 2013 at 12:14 AM, Danushka Menikkumbura <
> danushka.menikkumbura@gmail.com> wrote:
>
> > Guys,
> >
> > I think we would end up emulating XBaya at some point down the line. In
> > fact it could be something similar to what Creately [1] provides.
> >
> > Anyway we need to get few things straight in the first place.
> >
> > 1. Have an object model similar to that of XBaya so that it is possible
> to
> > edit/run workflows done using XBaya on the Web UI and vice versa.
> >
> > 2. Develop a basic UI framework so that others can build on top of it.
> This
> > would include different types of widget, menus, log/status windows, etc.
> >
> > 3. The protocol conversion layer (JSON/XML) that needs to be developed in
> > parallel.
> >
> > 4. Make the UI extensible so that new components, etc could be added with
> > relatively little effort.
> >
> > [1] - https://creately.com/app/?tempID=h165rwt81#
> >
> > Lets discuss and come up with a plan as having a solid architecture/base
> > would pay off for sure.
> >
> > Thanks,
> > Danushka
> >
> >
> > On Fri, May 31, 2013 at 9:43 PM, Sanchit Aggarwal <
> > sanchitagarwal108@gmail.com> wrote:
> >
> > > Hi
> > > I think keeping in mind the current implementation of the Xbaya, it
> > > would be good if we stick to single page web app with each of us
> > > having our custom modules.We all can come up with a design which can
> > > be used for all the interfaces, it will save the amount of time spend
> > > for designing a page from scratch.
> > >
> > > Regards
> > > Sanchit Aggarwal
> > >
> > >
> > >
> > > On Fri, May 31, 2013 at 9:21 PM, Subho Banerjee <su...@gmail.com>
> > > wrote:
> > > > Hi,
> > > > I had one small query, are all of us (those working on the front end)
> > > > working on a single page web app.
> > > >
> > > > Or will each of us have a page which we will design form top to
> bottom.
> > > >
> > > > In any case, maybe we can also agree on some common format to reuse
> the
> > > > objects, so that we do not code replication.
> > > >
> > > > Cheers,
> > > > Subho.
> > > >
> > > >
> > > > On Fri, May 31, 2013 at 8:48 PM, Suresh Marru <sm...@apache.org>
> > wrote:
> > > >
> > > >> Here are the all the proposals, please enable the public option, if
> > you
> > > >> haven't previously:
> > > >>
> > > >> Dunushka -
> > > >>
> > >
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/danushka/1
> > > >> Subho -
> > > >>
> > >
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/subhobanerjee/13001
> > > >> Vijayendra -
> > > >>
> > >
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/vijayendra_purohit/33001
> > > >> Sanchit -
> > > >>
> > >
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/sanchitaggarwal/24001
> > > >> Shameera -
> > > >>
> > >
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/shameera/60002
> > > >> Viknes -
> > > >>
> > >
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/vikbalas/1
> > > >>
> > > >> Suresh
> > > >>
> > > >>
> > > >> On May 31, 2013, at 11:15 AM, Danushka Menikkumbura <
> > > >> danushka.menikkumbura@gmail.com> wrote:
> > > >>
> > > >> > Please check now. Sorry about that.
> > > >> >
> > > >> > Danushka
> > > >> >
> > > >> >
> > > >> > On Fri, May 31, 2013 at 6:40 PM, Sanchit Aggarwal <
> > > >> > sanchitagarwal108@gmail.com> wrote:
> > > >> >
> > > >> >> Hi Danushka
> > > >> >>
> > > >> >> It seems that your proposal is not public. can you please set it
> to
> > > >> public.
> > > >> >>
> > > >> >> Regards
> > > >> >> Sanchit Aggarwal
> > > >> >>
> > > >> >>
> > > >> >>
> > > >> >> On Fri, May 31, 2013 at 5:14 PM, Danushka Menikkumbura
> > > >> >> <da...@gmail.com> wrote:
> > > >> >>> Hi Vijayendra,
> > > >> >>>
> > > >> >>> That's great!.
> > > >> >>>
> > > >> >>> BTW where to get some insight into what you are trying to do in
> > the
> > > >> first
> > > >> >>> place?. Maybe your proposal would do.
> > > >> >>>
> > > >> >>> Please find mine at [1]. Please go through sections 1.4, 1.5 and
> > > 1.6 to
> > > >> >> get
> > > >> >>> a very high-level idea of what we are planning to do in terms of
> > > >> >> supporting
> > > >> >>> AMQP in WS-Messenger.
> > > >> >>>
> > > >> >>> [1] -
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/danushka/1
> > > >> >>>
> > > >> >>> Thanks,
> > > >> >>> Danushka
> > > >> >>>
> > > >> >>>
> > > >> >>> On Fri, May 31, 2013 at 4:34 PM, Vijayendra Grampurohit <
> > > >> >>> vijayendra.sdm@gmail.com> wrote:
> > > >> >>>
> > > >> >>>> Hi Dhanushka/All
> > > >> >>>>
> > > >> >>>> I will be involved in one of the sub-project under "Monitoring
> > and
> > > >> >>>> Messaging". As you are handling "AMQP Messaging protocol
> support
> > > for
> > > >> >>>> Airavata WS-Messenger", We need to come up with framework for
> > > message
> > > >> >>>> monitoring. Can we all start discussing here?
> > > >> >>>>
> > > >> >>>> Regards
> > > >> >>>> Vijayendra
> > > >> >>>>
> > > >> >>
> > > >>
> > > >>
> > >
> >
>
>
>
> --
> Best Regards,
> Shameera Rathnayaka.
>
> email: shameera AT apache.org , shameerainfo AT gmail.com
> Blog : http://shameerarathnayaka.blogspot.com/
>
Re: "Monitoring and Messaging" Framework
Posted by Suresh Marru <sm...@apache.org>.
On May 31, 2013, at 11:34 PM, Shameera Rathnayaka <sh...@gmail.com> wrote:
> Hi Danushka et.al,
>
> I am working on defining a standard to convert JSON to XML and a suitable
> method to do the conversion back and forth without any loss. I went through
> some XSD's of Airavata backend and found that some elements have been
> defined with some attributes ( i.e, "application-scheduling-context"
> element in workflow_execution_context.xsd expect 10 attributes with it,
> Hope this is not a deprecated XSD)
This is still relevant. Airavata is a Archeologists paradise, as you dig through the summer you will keep finding fossils.
The key use of such a nested schema is to let the execution client specify node level scheduling preferences.
Suresh
> therefore we need to address this issue
> too. Most probably I can come up with an initial draft of this standard by
> next couple of days. We can initiate a discussion based on the draft and
> come to a final solution. After that we can do our works parallel .
>
> Thanks,
> Shameera.
>
>
> On Sat, Jun 1, 2013 at 12:14 AM, Danushka Menikkumbura <
> danushka.menikkumbura@gmail.com> wrote:
>
>> Guys,
>>
>> I think we would end up emulating XBaya at some point down the line. In
>> fact it could be something similar to what Creately [1] provides.
>>
>> Anyway we need to get few things straight in the first place.
>>
>> 1. Have an object model similar to that of XBaya so that it is possible to
>> edit/run workflows done using XBaya on the Web UI and vice versa.
>>
>> 2. Develop a basic UI framework so that others can build on top of it. This
>> would include different types of widget, menus, log/status windows, etc.
>>
>> 3. The protocol conversion layer (JSON/XML) that needs to be developed in
>> parallel.
>>
>> 4. Make the UI extensible so that new components, etc could be added with
>> relatively little effort.
>>
>> [1] - https://creately.com/app/?tempID=h165rwt81#
>>
>> Lets discuss and come up with a plan as having a solid architecture/base
>> would pay off for sure.
>>
>> Thanks,
>> Danushka
>>
>>
>> On Fri, May 31, 2013 at 9:43 PM, Sanchit Aggarwal <
>> sanchitagarwal108@gmail.com> wrote:
>>
>>> Hi
>>> I think keeping in mind the current implementation of the Xbaya, it
>>> would be good if we stick to single page web app with each of us
>>> having our custom modules.We all can come up with a design which can
>>> be used for all the interfaces, it will save the amount of time spend
>>> for designing a page from scratch.
>>>
>>> Regards
>>> Sanchit Aggarwal
>>>
>>>
>>>
>>> On Fri, May 31, 2013 at 9:21 PM, Subho Banerjee <su...@gmail.com>
>>> wrote:
>>>> Hi,
>>>> I had one small query, are all of us (those working on the front end)
>>>> working on a single page web app.
>>>>
>>>> Or will each of us have a page which we will design form top to bottom.
>>>>
>>>> In any case, maybe we can also agree on some common format to reuse the
>>>> objects, so that we do not code replication.
>>>>
>>>> Cheers,
>>>> Subho.
>>>>
>>>>
>>>> On Fri, May 31, 2013 at 8:48 PM, Suresh Marru <sm...@apache.org>
>> wrote:
>>>>
>>>>> Here are the all the proposals, please enable the public option, if
>> you
>>>>> haven't previously:
>>>>>
>>>>> Dunushka -
>>>>>
>>>
>> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/danushka/1
>>>>> Subho -
>>>>>
>>>
>> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/subhobanerjee/13001
>>>>> Vijayendra -
>>>>>
>>>
>> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/vijayendra_purohit/33001
>>>>> Sanchit -
>>>>>
>>>
>> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/sanchitaggarwal/24001
>>>>> Shameera -
>>>>>
>>>
>> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/shameera/60002
>>>>> Viknes -
>>>>>
>>>
>> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/vikbalas/1
>>>>>
>>>>> Suresh
>>>>>
>>>>>
>>>>> On May 31, 2013, at 11:15 AM, Danushka Menikkumbura <
>>>>> danushka.menikkumbura@gmail.com> wrote:
>>>>>
>>>>>> Please check now. Sorry about that.
>>>>>>
>>>>>> Danushka
>>>>>>
>>>>>>
>>>>>> On Fri, May 31, 2013 at 6:40 PM, Sanchit Aggarwal <
>>>>>> sanchitagarwal108@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Danushka
>>>>>>>
>>>>>>> It seems that your proposal is not public. can you please set it to
>>>>> public.
>>>>>>>
>>>>>>> Regards
>>>>>>> Sanchit Aggarwal
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 31, 2013 at 5:14 PM, Danushka Menikkumbura
>>>>>>> <da...@gmail.com> wrote:
>>>>>>>> Hi Vijayendra,
>>>>>>>>
>>>>>>>> That's great!.
>>>>>>>>
>>>>>>>> BTW where to get some insight into what you are trying to do in
>> the
>>>>> first
>>>>>>>> place?. Maybe your proposal would do.
>>>>>>>>
>>>>>>>> Please find mine at [1]. Please go through sections 1.4, 1.5 and
>>> 1.6 to
>>>>>>> get
>>>>>>>> a very high-level idea of what we are planning to do in terms of
>>>>>>> supporting
>>>>>>>> AMQP in WS-Messenger.
>>>>>>>>
>>>>>>>> [1] -
>>>>>>>>
>>>>>>>
>>>>>
>>>
>> https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/danushka/1
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Danushka
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, May 31, 2013 at 4:34 PM, Vijayendra Grampurohit <
>>>>>>>> vijayendra.sdm@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Dhanushka/All
>>>>>>>>>
>>>>>>>>> I will be involved in one of the sub-project under "Monitoring
>> and
>>>>>>>>> Messaging". As you are handling "AMQP Messaging protocol support
>>> for
>>>>>>>>> Airavata WS-Messenger", We need to come up with framework for
>>> message
>>>>>>>>> monitoring. Can we all start discussing here?
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> Vijayendra
>>>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>
>>
>
>
>
> --
> Best Regards,
> Shameera Rathnayaka.
>
> email: shameera AT apache.org , shameerainfo AT gmail.com
> Blog : http://shameerarathnayaka.blogspot.com/