Re: [Architecture] App Factory Tier Implementation

[Lahiru Manohara]

Hi Nadeeshani,

I have a few comments on this.

On Mon, Jan 4, 2016 at 3:55 PM, Nadeeshani Pathirennehelage <
nadeesha...@wso2.com> wrote:

>
> Hi All,
>
> This is the updated user interface design for the *application level tier
> implementation.*
>
> When an application owner creates a new application, he can select the
> pricing plan for that application.
>

I think this Maximum number of instance is referring to the max no of
containers. In future if we need to update our subscription plan, How can
we do that?

>
> ​
> Then, for each application, application owner can choose container specs
> for the Application.
>

IMO. We do not need to show unavailable container specifications to the
user. Is there any specific reason for that?

>
> ​
> Then, organization admin can view the details of each application.
>
>
> ​Thanks,
> Nadeeshani
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Best regards,

*Lahiru Manohara*
*Software Engineer*
Mobile: +94716561576
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] App Factory Tier Implementation

[Nadeeshani Pathirennehelage]

Hi All,

This is the updated user interface design for the *application level tier
implementation.*

When an application owner creates a new application, he can select the
pricing plan for that application.

​
Then, for each application, application owner can choose container specs
for the Application.

​
Then, organization admin can view the details of each application.


​Thanks,
Nadeeshani
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] App Factory Tier Implementation

[Dmitry Sotnikov]

It looks like Plans set limits on the number of container specifications -
which is probably a typo or something. Higher plans will likely allow to
have more *instances* (not types) of the containers and probably higher
variety (e.g. Free plan only having the small ones).

Also, after the plans are defined, it makes sense to let users sign-up to
them on Application rather than Organization level. So developers of
Application A pick the limits that work for them - maybe they use Free
because it is a PoC thing, and Application B needs small - because it is a
low traffic internal app, and then Application C needs extra-large because
it is a popular production app.

Plan can have some sort of monthly subscription price, container specs
allowed, max number of instances, maybe other limits (e.g. team size, or
shared storage), and maybe some sort of overage pricing (allowing to get
outside the limits and pay extra).

Dmitry

On Tue, Dec 15, 2015 at 8:48 PM, Nadeeshani Pathirennehelage <
nadeesha...@wso2.com> wrote:

> Hi All,
>
> *​Further clarification of Tier User Stories.*
>
> Appfactoery set up engineer will define the container_specs. As an example
> t2.small with the features CPU 1, memory 2 and memeory 4GB.
> He will also be defining the subscription plans.
>
> Then organizations(Tenants) can subscribe to the plans. Then that tenant
> would get assigned to the free tier. Free tier will allow to choose the
> containers of t2.small, t2.medium, t2.large with maximum of 6 containers
> where the Appfactory controls the maximum number of containers.
>
> So if a container is chosen, the containers that can be selected would
> reduce by one.
> If want tenant can upgrade their plan to paid tier.
>
> Kubernetes Quotas will control the container specs' Resources.
>
> Updated table structure is given below.
>
>
> ​
> ​Thanks,
>
> Nadeeshani.
>
> On Wed, Dec 16, 2015 at 6:41 AM, Imesh Gunaratne  wrote:
>
>> Thanks for the clarifications Kasun!
>>
>> On Tue, Dec 15, 2015 at 5:41 PM, Kasun De Silva  wrote:
>>
>>> Hi Imesh,
>>>
>>> See my comments inline,
>>>

- I can see the term "gear" is used in the tables but it's not
described. Is this an unit of resources (CPU, memory, disk, etc)? If so 
 how
do we plan to control that for a cluster of containers?

 Yes "Gear" is an unit of resources, but  AFAIU we should not use this
>>> word since openshift already use it.
>>> @Nadeeshani please use "Container Spec" instead for now until we figure
>>> out something better.
>>>

- What would be the entity that a tenant admin would subscribe to?
Is this a container cluster or a composite container deployment (which
would have a multiple clusters) or a set of app types?

 Tenant would subscribe to a Plan that is the main entity. Plan consist
>>> of a container cluster. He can use this container cluster to do his
>>> deployments.
>>>

- Are we planning to expose an API for billing integration?

 Yes, REST API will be provided for billing and subscription plan
>>> applications since we are planning to have payment modules and subscription
>>> modules separate from AF.  (Could be existing Cloudmgt app)
>>>

- Do we have a plan to integrate with an existing billing solution
to demonstrate billing capabilities?

 +1 for this, @AF team WDYT?
>>>
>>> Thanks,
>>> Kasun
>>>
>>> --
>>> *Kasun de Silva*
>>> Software Engineer | *WSO2 Inc.*; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email   : kas...@wso2.com
>>> mobile : +94 77 794 4260
>>>
>>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> 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
>
>


-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware


___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] App Factory Tier Implementation

[Manjula Rathnayake]

Hi Dakshika,

On Mon, Dec 14, 2015 at 11:52 AM, Dakshika Jayathilaka 
wrote:

> Hi,
>
> I have few questions on above user stories,
>
> 1. How* "setup Eng"* define base currency for this? (USD, LKR)
>
 Billing should be handled by a different application and we need to remove
cost per hour field from above tables.

> 2. Do we have any plan on specifying regions?
>
+1.

> 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)  )
>
Yes, REST API will be provided for billing and subscription plan
applications.

+1 for adding description, display name fields too.

thank you.

>
> 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
>>
>>
>


-- 
Manjula Rathnayaka
Associate Technical Lead
WSO2, Inc.
Mobile:+94 77 743 1987
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] App Factory Tier Implementation

[Kasun De Silva]

Hi Imesh,

See my comments inline,

>
>- I can see the term "gear" is used in the tables but it's not
>described. Is this an unit of resources (CPU, memory, disk, etc)? If so how
>do we plan to control that for a cluster of containers?
>
> Yes "Gear" is an unit of resources, but  AFAIU we should not use this word
since openshift already use it.
@Nadeeshani please use "Container Spec" instead for now until we figure out
something better.

>
>- What would be the entity that a tenant admin would subscribe to? Is
>this a container cluster or a composite container deployment (which would
>have a multiple clusters) or a set of app types?
>
> Tenant would subscribe to a Plan that is the main entity. Plan consist of
a container cluster. He can use this container cluster to do his
deployments.

>
>- Are we planning to expose an API for billing integration?
>
> Yes, REST API will be provided for billing and subscription plan
applications since we are planning to have payment modules and subscription
modules separate from AF.  (Could be existing Cloudmgt app)

>
>- Do we have a plan to integrate with an existing billing solution to
>demonstrate billing capabilities?
>
> +1 for this, @AF team WDYT?

Thanks,
Kasun

-- 
*Kasun de Silva*
Software Engineer | *WSO2 Inc.*; http://wso2.com
lean.enterprise.middleware

email   : kas...@wso2.com
mobile : +94 77 794 4260
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] App Factory Tier Implementation

[Imesh Gunaratne]

Few questions/points:

   - I can see the term "gear" is used in the tables but it's not
   described. Is this an unit of resources (CPU, memory, disk, etc)? If so how
   do we plan to control that for a cluster of containers?
   - What would be the entity that a tenant admin would subscribe to? Is
   this a container cluster or a composite container deployment (which would
   have a multiple clusters) or a set of app types?
   - Are we planning to expose an API for billing integration?
   - Do we have a plan to integrate with an existing billing solution to
   demonstrate billing capabilities?

Thanks

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
>
>


-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] App Factory Tier Implementation

[Imesh Gunaratne]

Thanks for the clarifications Kasun!

On Tue, Dec 15, 2015 at 5:41 PM, Kasun De Silva  wrote:

> Hi Imesh,
>
> See my comments inline,
>
>>
>>- I can see the term "gear" is used in the tables but it's not
>>described. Is this an unit of resources (CPU, memory, disk, etc)? If so 
>> how
>>do we plan to control that for a cluster of containers?
>>
>> Yes "Gear" is an unit of resources, but  AFAIU we should not use this
> word since openshift already use it.
> @Nadeeshani please use "Container Spec" instead for now until we figure
> out something better.
>
>>
>>- What would be the entity that a tenant admin would subscribe to? Is
>>this a container cluster or a composite container deployment (which would
>>have a multiple clusters) or a set of app types?
>>
>> Tenant would subscribe to a Plan that is the main entity. Plan consist of
> a container cluster. He can use this container cluster to do his
> deployments.
>
>>
>>- Are we planning to expose an API for billing integration?
>>
>> Yes, REST API will be provided for billing and subscription plan
> applications since we are planning to have payment modules and subscription
> modules separate from AF.  (Could be existing Cloudmgt app)
>
>>
>>- Do we have a plan to integrate with an existing billing solution to
>>demonstrate billing capabilities?
>>
>> +1 for this, @AF team WDYT?
>
> Thanks,
> Kasun
>
> --
> *Kasun de Silva*
> Software Engineer | *WSO2 Inc.*; http://wso2.com
> lean.enterprise.middleware
>
> email   : kas...@wso2.com
> mobile : +94 77 794 4260
>
>


-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] App Factory Tier Implementation

[Nadeeshani Pathirennehelage]

Hi All,

*​Further clarification of Tier User Stories.*

Appfactoery set up engineer will define the container_specs. As an example
t2.small with the features CPU 1, memory 2 and memeory 4GB.
He will also be defining the subscription plans.

Then organizations(Tenants) can subscribe to the plans. Then that tenant
would get assigned to the free tier. Free tier will allow to choose the
containers of t2.small, t2.medium, t2.large with maximum of 6 containers
where the Appfactory controls the maximum number of containers.

So if a container is chosen, the containers that can be selected would
reduce by one.
If want tenant can upgrade their plan to paid tier.

Kubernetes Quotas will control the container specs' Resources.

Updated table structure is given below.


​
​Thanks,

Nadeeshani.

On Wed, Dec 16, 2015 at 6:41 AM, Imesh Gunaratne  wrote:

> Thanks for the clarifications Kasun!
>
> On Tue, Dec 15, 2015 at 5:41 PM, Kasun De Silva  wrote:
>
>> Hi Imesh,
>>
>> See my comments inline,
>>
>>>
>>>- I can see the term "gear" is used in the tables but it's not
>>>described. Is this an unit of resources (CPU, memory, disk, etc)? If so 
>>> how
>>>do we plan to control that for a cluster of containers?
>>>
>>> Yes "Gear" is an unit of resources, but  AFAIU we should not use this
>> word since openshift already use it.
>> @Nadeeshani please use "Container Spec" instead for now until we figure
>> out something better.
>>
>>>
>>>- What would be the entity that a tenant admin would subscribe to?
>>>Is this a container cluster or a composite container deployment (which
>>>would have a multiple clusters) or a set of app types?
>>>
>>> Tenant would subscribe to a Plan that is the main entity. Plan consist
>> of a container cluster. He can use this container cluster to do his
>> deployments.
>>
>>>
>>>- Are we planning to expose an API for billing integration?
>>>
>>> Yes, REST API will be provided for billing and subscription plan
>> applications since we are planning to have payment modules and subscription
>> modules separate from AF.  (Could be existing Cloudmgt app)
>>
>>>
>>>- Do we have a plan to integrate with an existing billing solution
>>>to demonstrate billing capabilities?
>>>
>>> +1 for this, @AF team WDYT?
>>
>> Thanks,
>> Kasun
>>
>> --
>> *Kasun de Silva*
>> Software Engineer | *WSO2 Inc.*; http://wso2.com
>> lean.enterprise.middleware
>>
>> email   : kas...@wso2.com
>> mobile : +94 77 794 4260
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
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] 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] 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