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 < [email protected]> 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 > [email protected] > > _______________________________________________ > Architecture mailing list > [email protected] > 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 [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
