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