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 <[email protected]> wrote: > Thanks for the clarifications Kasun! > > On Tue, Dec 15, 2015 at 5:41 PM, Kasun De Silva <[email protected]> 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 : [email protected] >> 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 > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- 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
