Missing features in new architecture

[Lahiru Gunathilake <gl...@gmail.com>]

Hi devs,

Due to the architecture change I thought of discussing what are the missing
features in current trunk compared to 0.11 release. Of course we need to do
lot more features that 0.11 release but I think before that we can finalize
what we still need do to fix the gap between 0.11 and next release. If we
are not planning to do features in 0.11 release we can cut them down and
focus on the rest.

1. Workflow support and non of the xbaya features are working in trunk.
2. There is no workflow interpreter service and if we are planning to get
rid of axis2 we have to make workflow interpreter as a thrift service.
3. There is not notification mechanism between the client and the server,
to get a status we always have to pull from the registry.
4. There is no credential store support in trunk.
5.  We need to update most of the unit tests and make sure atleast we have
the unit tests which we had for 0.11 release.


I am sure I have missed some here, so if you have any missing features in
trunk due to re-architecting happen, please reply so that we can create a
jira with sub-tasks and work on them.

Thanks
Lahiru
-- 
System Analyst Programmer
PTI Lab
Indiana University

Re: Missing features in new architecture

[Saminda Wijeratne <sa...@gmail.com>]

+1 for the suggested order of priority


On Fri, Apr 11, 2014 at 1:05 PM, Lahiru Gunathilake <gl...@gmail.com>wrote:

> +1 for the prioritized list.
>
> Lahiru
>
>
> On Fri, Apr 11, 2014 at 4:04 PM, Marlon Pierce <ma...@iu.edu> wrote:
>
>> Some order of priority from the list below is
>>
>> * Credential Store
>>
>> * Application Catalog: this needs to be implemented, currently being
>> discussed on other threads.
>>
>> * Notifications: Use existing code base for now?  Use AMQP work from
>> last year's GSOC by Danushka? Make the Kafka leap?
>>
>> The workflow interpreter and XBaya will be lower priority.
>>
>> Comments?
>>
>> Marlon
>>
>> On 4/11/14 8:56 AM, Lahiru Gunathilake wrote:
>> > On Fri, Apr 11, 2014 at 8:53 AM, Marlon Pierce <ma...@iu.edu> wrote:
>> >
>> >> The Credential Store support looks like a priority to me.  Can someone
>> >> outline what it will take to get it working again?
>> >>
>> > +1, I can have a look.
>> >
>> > 9. Support to gram provider, bes provider and ec2 provider in gfac and
>> > adding monitoring mechanisms.
>> >
>> > Regards
>> > Lahiru
>> >
>> >
>> >
>> >> Marlon
>> >>
>> >> On 4/11/14 7:10 AM, Saminda Wijeratne wrote:
>> >>> I think you have covered the essentials. I think most of these missing
>> >>> features require creating thrift services and/or update to use thrift
>> >>> clients. To that end following should also be added.
>> >>>
>> >>> 6. Support for Application management (Application Catalog) through
>> >> thrift
>> >>> 7. Authenticated communication between the client-sdk and the thrift
>> >> server
>> >>> 8. Update the integration tests to cover the workflow support
>> >>>
>> >>>
>> >>>
>> >>> On Thu, Apr 10, 2014 at 8:11 PM, Lahiru Gunathilake <
>> glahiru@gmail.com
>> >>> wrote:
>> >>>
>> >>>> Hi devs,
>> >>>>
>> >>>> Due to the architecture change I thought of discussing what are the
>> >>>> missing features in current trunk compared to 0.11 release. Of
>> course we
>> >>>> need to do lot more features that 0.11 release but I think before
>> that
>> >> we
>> >>>> can finalize what we still need do to fix the gap between 0.11 and
>> next
>> >>>> release. If we are not planning to do features in 0.11 release we can
>> >> cut
>> >>>> them down and focus on the rest.
>> >>>>
>> >>>> 1. Workflow support and non of the xbaya features are working in
>> trunk.
>> >>>> 2. There is no workflow interpreter service and if we are planning to
>> >> get
>> >>>> rid of axis2 we have to make workflow interpreter as a thrift
>> service.
>> >>>> 3. There is not notification mechanism between the client and the
>> >> server,
>> >>>> to get a status we always have to pull from the registry.
>> >>>> 4. There is no credential store support in trunk.
>> >>>> 5.  We need to update most of the unit tests and make sure atleast we
>> >> have
>> >>>> the unit tests which we had for 0.11 release.
>> >>>>
>> >>>>
>> >>>> I am sure I have missed some here, so if you have any missing
>> features
>> >> in
>> >>>> trunk due to re-architecting happen, please reply so that we can
>> create
>> >> a
>> >>>> jira with sub-tasks and work on them.
>> >>>>
>> >>>> Thanks
>> >>>> Lahiru
>> >>>> --
>> >>>> System Analyst Programmer
>> >>>> PTI Lab
>> >>>> Indiana University
>> >>>>
>> >>
>> >
>>
>>
>
>
> --
> System Analyst Programmer
> PTI Lab
> Indiana University
>

Re: Missing features in new architecture

[Lahiru Gunathilake <gl...@gmail.com>]

+1 for the prioritized list.

Lahiru


On Fri, Apr 11, 2014 at 4:04 PM, Marlon Pierce <ma...@iu.edu> wrote:

> Some order of priority from the list below is
>
> * Credential Store
>
> * Application Catalog: this needs to be implemented, currently being
> discussed on other threads.
>
> * Notifications: Use existing code base for now?  Use AMQP work from
> last year's GSOC by Danushka? Make the Kafka leap?
>
> The workflow interpreter and XBaya will be lower priority.
>
> Comments?
>
> Marlon
>
> On 4/11/14 8:56 AM, Lahiru Gunathilake wrote:
> > On Fri, Apr 11, 2014 at 8:53 AM, Marlon Pierce <ma...@iu.edu> wrote:
> >
> >> The Credential Store support looks like a priority to me.  Can someone
> >> outline what it will take to get it working again?
> >>
> > +1, I can have a look.
> >
> > 9. Support to gram provider, bes provider and ec2 provider in gfac and
> > adding monitoring mechanisms.
> >
> > Regards
> > Lahiru
> >
> >
> >
> >> Marlon
> >>
> >> On 4/11/14 7:10 AM, Saminda Wijeratne wrote:
> >>> I think you have covered the essentials. I think most of these missing
> >>> features require creating thrift services and/or update to use thrift
> >>> clients. To that end following should also be added.
> >>>
> >>> 6. Support for Application management (Application Catalog) through
> >> thrift
> >>> 7. Authenticated communication between the client-sdk and the thrift
> >> server
> >>> 8. Update the integration tests to cover the workflow support
> >>>
> >>>
> >>>
> >>> On Thu, Apr 10, 2014 at 8:11 PM, Lahiru Gunathilake <glahiru@gmail.com
> >>> wrote:
> >>>
> >>>> Hi devs,
> >>>>
> >>>> Due to the architecture change I thought of discussing what are the
> >>>> missing features in current trunk compared to 0.11 release. Of course
> we
> >>>> need to do lot more features that 0.11 release but I think before that
> >> we
> >>>> can finalize what we still need do to fix the gap between 0.11 and
> next
> >>>> release. If we are not planning to do features in 0.11 release we can
> >> cut
> >>>> them down and focus on the rest.
> >>>>
> >>>> 1. Workflow support and non of the xbaya features are working in
> trunk.
> >>>> 2. There is no workflow interpreter service and if we are planning to
> >> get
> >>>> rid of axis2 we have to make workflow interpreter as a thrift service.
> >>>> 3. There is not notification mechanism between the client and the
> >> server,
> >>>> to get a status we always have to pull from the registry.
> >>>> 4. There is no credential store support in trunk.
> >>>> 5.  We need to update most of the unit tests and make sure atleast we
> >> have
> >>>> the unit tests which we had for 0.11 release.
> >>>>
> >>>>
> >>>> I am sure I have missed some here, so if you have any missing features
> >> in
> >>>> trunk due to re-architecting happen, please reply so that we can
> create
> >> a
> >>>> jira with sub-tasks and work on them.
> >>>>
> >>>> Thanks
> >>>> Lahiru
> >>>> --
> >>>> System Analyst Programmer
> >>>> PTI Lab
> >>>> Indiana University
> >>>>
> >>
> >
>
>


-- 
System Analyst Programmer
PTI Lab
Indiana University

Re: Missing features in new architecture

[Marlon Pierce <ma...@iu.edu>]

Some order of priority from the list below is

* Credential Store

* Application Catalog: this needs to be implemented, currently being
discussed on other threads.

* Notifications: Use existing code base for now?  Use AMQP work from
last year's GSOC by Danushka? Make the Kafka leap?

The workflow interpreter and XBaya will be lower priority.

Comments?

Marlon

On 4/11/14 8:56 AM, Lahiru Gunathilake wrote:
> On Fri, Apr 11, 2014 at 8:53 AM, Marlon Pierce <ma...@iu.edu> wrote:
>
>> The Credential Store support looks like a priority to me.  Can someone
>> outline what it will take to get it working again?
>>
> +1, I can have a look.
>
> 9. Support to gram provider, bes provider and ec2 provider in gfac and
> adding monitoring mechanisms.
>
> Regards
> Lahiru
>
>
>
>> Marlon
>>
>> On 4/11/14 7:10 AM, Saminda Wijeratne wrote:
>>> I think you have covered the essentials. I think most of these missing
>>> features require creating thrift services and/or update to use thrift
>>> clients. To that end following should also be added.
>>>
>>> 6. Support for Application management (Application Catalog) through
>> thrift
>>> 7. Authenticated communication between the client-sdk and the thrift
>> server
>>> 8. Update the integration tests to cover the workflow support
>>>
>>>
>>>
>>> On Thu, Apr 10, 2014 at 8:11 PM, Lahiru Gunathilake <glahiru@gmail.com
>>> wrote:
>>>
>>>> Hi devs,
>>>>
>>>> Due to the architecture change I thought of discussing what are the
>>>> missing features in current trunk compared to 0.11 release. Of course we
>>>> need to do lot more features that 0.11 release but I think before that
>> we
>>>> can finalize what we still need do to fix the gap between 0.11 and next
>>>> release. If we are not planning to do features in 0.11 release we can
>> cut
>>>> them down and focus on the rest.
>>>>
>>>> 1. Workflow support and non of the xbaya features are working in trunk.
>>>> 2. There is no workflow interpreter service and if we are planning to
>> get
>>>> rid of axis2 we have to make workflow interpreter as a thrift service.
>>>> 3. There is not notification mechanism between the client and the
>> server,
>>>> to get a status we always have to pull from the registry.
>>>> 4. There is no credential store support in trunk.
>>>> 5.  We need to update most of the unit tests and make sure atleast we
>> have
>>>> the unit tests which we had for 0.11 release.
>>>>
>>>>
>>>> I am sure I have missed some here, so if you have any missing features
>> in
>>>> trunk due to re-architecting happen, please reply so that we can create
>> a
>>>> jira with sub-tasks and work on them.
>>>>
>>>> Thanks
>>>> Lahiru
>>>> --
>>>> System Analyst Programmer
>>>> PTI Lab
>>>> Indiana University
>>>>
>>
>

Re: Missing features in new architecture

[Lahiru Gunathilake <gl...@gmail.com>]

On Fri, Apr 11, 2014 at 8:53 AM, Marlon Pierce <ma...@iu.edu> wrote:

> The Credential Store support looks like a priority to me.  Can someone
> outline what it will take to get it working again?
>
+1, I can have a look.

9. Support to gram provider, bes provider and ec2 provider in gfac and
adding monitoring mechanisms.

Regards
Lahiru



>
> Marlon
>
> On 4/11/14 7:10 AM, Saminda Wijeratne wrote:
> > I think you have covered the essentials. I think most of these missing
> > features require creating thrift services and/or update to use thrift
> > clients. To that end following should also be added.
> >
> > 6. Support for Application management (Application Catalog) through
> thrift
> > 7. Authenticated communication between the client-sdk and the thrift
> server
> > 8. Update the integration tests to cover the workflow support
> >
> >
> >
> > On Thu, Apr 10, 2014 at 8:11 PM, Lahiru Gunathilake <glahiru@gmail.com
> >wrote:
> >
> >> Hi devs,
> >>
> >> Due to the architecture change I thought of discussing what are the
> >> missing features in current trunk compared to 0.11 release. Of course we
> >> need to do lot more features that 0.11 release but I think before that
> we
> >> can finalize what we still need do to fix the gap between 0.11 and next
> >> release. If we are not planning to do features in 0.11 release we can
> cut
> >> them down and focus on the rest.
> >>
> >> 1. Workflow support and non of the xbaya features are working in trunk.
> >> 2. There is no workflow interpreter service and if we are planning to
> get
> >> rid of axis2 we have to make workflow interpreter as a thrift service.
> >> 3. There is not notification mechanism between the client and the
> server,
> >> to get a status we always have to pull from the registry.
> >> 4. There is no credential store support in trunk.
> >> 5.  We need to update most of the unit tests and make sure atleast we
> have
> >> the unit tests which we had for 0.11 release.
> >>
> >>
> >> I am sure I have missed some here, so if you have any missing features
> in
> >> trunk due to re-architecting happen, please reply so that we can create
> a
> >> jira with sub-tasks and work on them.
> >>
> >> Thanks
> >> Lahiru
> >> --
> >> System Analyst Programmer
> >> PTI Lab
> >> Indiana University
> >>
>
>


-- 
System Analyst Programmer
PTI Lab
Indiana University

Re: Missing features in new architecture

[Marlon Pierce <ma...@iu.edu>]

The Credential Store support looks like a priority to me.  Can someone
outline what it will take to get it working again?

Marlon

On 4/11/14 7:10 AM, Saminda Wijeratne wrote:
> I think you have covered the essentials. I think most of these missing
> features require creating thrift services and/or update to use thrift
> clients. To that end following should also be added.
>
> 6. Support for Application management (Application Catalog) through thrift
> 7. Authenticated communication between the client-sdk and the thrift server
> 8. Update the integration tests to cover the workflow support
>
>
>
> On Thu, Apr 10, 2014 at 8:11 PM, Lahiru Gunathilake <gl...@gmail.com>wrote:
>
>> Hi devs,
>>
>> Due to the architecture change I thought of discussing what are the
>> missing features in current trunk compared to 0.11 release. Of course we
>> need to do lot more features that 0.11 release but I think before that we
>> can finalize what we still need do to fix the gap between 0.11 and next
>> release. If we are not planning to do features in 0.11 release we can cut
>> them down and focus on the rest.
>>
>> 1. Workflow support and non of the xbaya features are working in trunk.
>> 2. There is no workflow interpreter service and if we are planning to get
>> rid of axis2 we have to make workflow interpreter as a thrift service.
>> 3. There is not notification mechanism between the client and the server,
>> to get a status we always have to pull from the registry.
>> 4. There is no credential store support in trunk.
>> 5.  We need to update most of the unit tests and make sure atleast we have
>> the unit tests which we had for 0.11 release.
>>
>>
>> I am sure I have missed some here, so if you have any missing features in
>> trunk due to re-architecting happen, please reply so that we can create a
>> jira with sub-tasks and work on them.
>>
>> Thanks
>> Lahiru
>> --
>> System Analyst Programmer
>> PTI Lab
>> Indiana University
>>

Re: Missing features in new architecture

[Saminda Wijeratne <sa...@gmail.com>]

I think you have covered the essentials. I think most of these missing
features require creating thrift services and/or update to use thrift
clients. To that end following should also be added.

6. Support for Application management (Application Catalog) through thrift
7. Authenticated communication between the client-sdk and the thrift server
8. Update the integration tests to cover the workflow support



On Thu, Apr 10, 2014 at 8:11 PM, Lahiru Gunathilake <gl...@gmail.com>wrote:

> Hi devs,
>
> Due to the architecture change I thought of discussing what are the
> missing features in current trunk compared to 0.11 release. Of course we
> need to do lot more features that 0.11 release but I think before that we
> can finalize what we still need do to fix the gap between 0.11 and next
> release. If we are not planning to do features in 0.11 release we can cut
> them down and focus on the rest.
>
> 1. Workflow support and non of the xbaya features are working in trunk.
> 2. There is no workflow interpreter service and if we are planning to get
> rid of axis2 we have to make workflow interpreter as a thrift service.
> 3. There is not notification mechanism between the client and the server,
> to get a status we always have to pull from the registry.
> 4. There is no credential store support in trunk.
> 5.  We need to update most of the unit tests and make sure atleast we have
> the unit tests which we had for 0.11 release.
>
>
> I am sure I have missed some here, so if you have any missing features in
> trunk due to re-architecting happen, please reply so that we can create a
> jira with sub-tasks and work on them.
>
> Thanks
> Lahiru
> --
> System Analyst Programmer
> PTI Lab
> Indiana University
>