Re: [Architecture] App Factory Tier Implementation

[Dakshika Jayathilaka]

Hi,

I have few questions on above user stories,

1. How* "setup Eng"* define base currency for this? (USD, LKR)
2. Do we have any plan on specifying regions?
3. Are we planning to provide any REST APIs for this? (AFAIK we are not
planning to have any payment modules in AF side. so probably we need to
have API for integrate with another app (ex: cloud Mgt App)  )

Thank you,.

Regards,

*Dakshika Jayathilaka*
PMC Member & Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911

On Mon, Dec 14, 2015 at 9:37 AM, Nadeeshani Pathirennehelage <
nadeesha...@wso2.com> wrote:

> Hi All,
> We are hoping to implement the tier implementation for the AppFactory.
> Tier is the subscription plan which is selected by the organization admin
> for the organization.
>
>1.
>
>AF Set Up Engineer should be able to define Tiers (free/paid v1/ paid
>v2).
>2.
>
>AF Set Up Engineer should be able to define Container Specs.
>(t2.small/ t2.medium/ m2.small )
>3. System should display each Subscription Plans ( Free / Paid v1 /
>paid v2) to the Organization Admin(Tenant) to choose a suitable plan for
>the organization.
>4.
>
>Organization Admin(Tenant) should be able to upgrade the subscription
>plan for the organization.
>5. System should display the each Container Specs Type(
>Small/medium/large) with its features such as CPU, memory, storage to all
>tenants.
>6.
>
>Organization Admin(Tenant) should be able to choose new Container
>Specs ( small , large , medium ) to the existing subscription plan.
>Organization members should use those Container Spec.
>7.
>
>Organization Admin(Tenant) should be able to remove Container Specs (
>small , large , medium ) from the existing subscription plan.
>8. System should be able to view the details such as Plan Type, list
>of Container Specs which is running and information of each Container Spec,
>of a given Organization.
>
>
> Table structure is given below.
>
>
> ​
>
> *These tables are filled with just reference values.*
> The above plan table can be expanded with more columns.
>
> ​The above table structure will be useful for the administration to
> develop applications for configuring the tiers. Moreover it will be useful
> to render the subscription plan to the end users through UI.
>
> Would appreciate it if you could give your suggestions and comments on
> this.
> Thanks,
> Nadeeshani
>
> --
> Pathirennehelage Nadeeshani
> Software Engineering Intern : WSO2 Inc
> Mobile : +94 (0) 716 545223
> nadeesha...@wso2.com
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] App Factory Tier Implementation

[Nadeeshani Pathirennehelage]

Hi All,
We are hoping to implement the tier implementation for the AppFactory. Tier
is the subscription plan which is selected by the organization admin for
the organization.

   1.

   AF Set Up Engineer should be able to define Tiers (free/paid v1/ paid
   v2).
   2.

   AF Set Up Engineer should be able to define Container Specs. (t2.small/
   t2.medium/ m2.small )
   3. System should display each Subscription Plans ( Free / Paid v1 / paid
   v2) to the Organization Admin(Tenant) to choose a suitable plan for the
   organization.
   4.

   Organization Admin(Tenant) should be able to upgrade the subscription
   plan for the organization.
   5. System should display the each Container Specs Type(
   Small/medium/large) with its features such as CPU, memory, storage to all
   tenants.
   6.

   Organization Admin(Tenant) should be able to choose new Container Specs
   ( small , large , medium ) to the existing subscription plan. Organization
   members should use those Container Spec.
   7.

   Organization Admin(Tenant) should be able to remove Container Specs (
   small , large , medium ) from the existing subscription plan.
   8. System should be able to view the details such as Plan Type, list of
   Container Specs which is running and information of each Container Spec, of
   a given Organization.


Table structure is given below.


​

*These tables are filled with just reference values.*
The above plan table can be expanded with more columns.

​The above table structure will be useful for the administration to develop
applications for configuring the tiers. Moreover it will be useful to
render the subscription plan to the end users through UI.

Would appreciate it if you could give your suggestions and comments on this.
Thanks,
Nadeeshani

-- 
Pathirennehelage Nadeeshani
Software Engineering Intern : WSO2 Inc
Mobile : +94 (0) 716 545223
nadeesha...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [ESB] Adding features for VFS inbound(include option copy and leave as it is) and ESB polling inbound(support with cron).

[Malaka Silva]

Eranda currently what you mentioned is already available with ESB 490.

Check param transport.vfs. MoveTimestampFormat in [1]

[1] https://docs.wso2.com/display/ESB490/File+Inbound+Protocol

On Sat, Dec 12, 2015 at 5:40 PM, Eranga Perera  wrote:

> Hi,
>
> Another usefull behaviour I think that we should provide is the ability
> set some property for vfs inbound, so that when the file is moved/copied
> the original name will be appended by some sequence number or a time stamp.
> This will be usefull in case if the third party application is generating
> the same file name each time it is deposited to the in folder and it will
> help to track all files being processed without overwriting the previous
> files.
>
> Eranga.
>
> Eranga Perera
> Senior Lead Solutions Engineer
> WSO2, Inc.
> Mobile :  +94 72 778 4250
> eran...@wso2.com
> On Dec 12, 2015 4:52 PM, "Kalyani Yogeswaranathan" 
> wrote:
>
>> Hi Kirishanthy,
>>
>> These resources may help you to get some knowledge about VFS Transport[1]
>> and File inbound[2].
>>
>>1. https://docs.wso2.com/display/ESB490/VFS+Transport
>>2. https://docs.wso2.com/display/ESB490/File+Inbound+Protocol
>>3.
>>
>> https://github.com/wso2/carbon-mediation/tree/master/components/inbound-endpoints
>>
>> Thank you.
>>
>> On Fri, Dec 11, 2015 at 11:49 AM, Jagath Sisirakumara Ariyarathne <
>> jaga...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> To get the input for polling interval/cron configuration, how about
>>> using a toggle button like in Scheduled Tasks.
>>>
>>> [image: Inline image 1]
>>>
>>> In this case, we can set interval as default selection. Based on the
>>> selection, you can use required implementation.
>>>
>>> Thanks.
>>>
>>> On Fri, Dec 11, 2015 at 10:56 AM, Kirishanthy Tharmalingam <
>>> kirishan...@wso2.com> wrote:
>>>
 Hi all ,

 Now I'm working on following improvement in the VFS inbound and ESB
 polling inbound.

1. For VFS inbound we only have the option to delete or move file
after processed or after error. Need to give the options copy and  
 leave as
it is.
2. Current ESB polling inbound only support interval. But we need
to have the ability to schedule it using cron expressions.

 In first case leave as it is the good option because we can used the
 same file again and again.
 In the copy option we copy the same file again and again, so If the
 file is already exist in the destination directory delete the file and copy
 the file again.
 use case of copy option is we can update the content of the
 file(because it is exist in the source directory), then the next polling we
 can copy the updated file to the destination directory.(because delete
 the existing file in the destination directory and copy the updated file).
 Is there any other use case? Please correct if am I wrong.

 In the second case,I'm using  the separate UI field for getting value
 for interval and cron , If the cron value is available then polling is
 working with cron time period , if the cron is not available then the
 polling is working with the interval.
 Is there a different way to implement this feature?

 --
 Thanks & Regards,
 Kirishanthy
 Associate Software Engineer
 Mobile : +94 778333939
 kirishan...@wso2.com

>>>
>>>
>>>
>>> --
>>> Jagath Ariyarathne
>>> Technical Lead
>>> WSO2 Inc.  http://wso2.com/
>>> Email: jaga...@wso2.com
>>> Mob  : +94 77 386 7048
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Kalyani Yogeswaranathan*
>>
>> *Associate software engineer*
>> *WSO2 Inc.*
>>
>> *Mobile: 0776390284 <0776390284>*
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/

https://store.wso2.com/store/

Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture