Please find the Image. On Tue, Jun 23, 2015 at 2:48 PM, Punnadi Gunarathna <[email protected]> wrote:
> Hi All, > > > With Stratos 4.1.0 upgrade, there will be one Stratos deployment for all 3 > lifecycle stages. > > There will be 2 deployments: > > 1. > > For ideal Production setup, there will be 3 physical Kubernetes > clusters with 1 master and n number of minions. > 2. > > For Dev setup, there will be 1 physical Kubernetes clusters with 1 > master and 1 minion as depicted in the below diagram > > > > > For both a and b scenarios, same json artifacts will be used with > appropriate values to differentiate each stage separately. > > Below are the json files required for each stage: > > > 1. > > kubernetes-cluster.json > 2. > > autoscaling-policy.json > 3. > > network-partition.json > 4. > > deployment-policy.json > 5. > > cartridge.json (e.g: php.json) > 6. > > application-policy.json > 7. > > application.json > > > But for scenario a, kubernetes-cluster.json file configuration values will > be different as there will be 3 physical clusters for each stage. > > But for scenario b, even though there are 3 separate > kubernetes-cluster.json file for each stage, their configuration values > will be similar as there will be only one physical cluster for all the 3 > stages. > > > For single tenant applications, deploy application will implicitly do the > signup where as for multi-tenant applications, once the application is > deployed, signup has to be done separately for each tenant. > > Feel free to share your thoughts on this. > > > Reference: > https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Single+Cartridge+Application+on+Kubernetes > > > On Thu, Jun 18, 2015 at 2:36 PM, Punnadi Gunarathna <[email protected]> > wrote: > >> Hi All, >> >> I will be working on the above task and following are the details of what >> will be done and why. >> >> Problems pertaining in current deployment: >> >> 1. If all the servers are required to setup on a single machine, existing >> deployment requires 16GB RAM to run. >> 2. Each LC Stage requires separate Stratos deployment. >> 3. Since the deployment requires more resources, Developers are having a >> hard time in setting up a development environment locally. >> 3. App Factory is highly coupled with Private PaaS. There is no PaaS API >> defined in App Factory front to plug-in any other available PaaS. >> 4. Stratos 4.1.0 provides out of the box Docker suppport which provides >> more capabilities and requires less resources compared to Stratos 4.0.0 >> >> Hence team App Factory has decided to incorporate Stratos 4.1.0 to >> resolve these issues and provide a better user experience. >> Meeting notes are found in [1] mail thread. >> Diagram which depicts the single Stratos deployment for a AF deployment >> found in [2]. >> >> [1]Meeting Notes - AF - Stratos 4.1.0 Integration Review >> [2] >> https://docs.google.com/drawings/d/18Si9qizcZX-bUrIo_ghevJ7UdWLsYfwdNtN80Ns2ht0/edit >> >> I will update more details on the design and approach when they are ready. >> Feel free to post your comments and feedback. >> >> -- >> Thanks and Regards, >> >> Punnadi Gunarathna >> Senior Software Engineer, >> WSO2, Inc.; http://wso2.com <http://wso2> >> Blog: http://hi-my-world.blogspot.com/ >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> >> >> >> <http://lalajisureshika.blogspot.com/> >> > > > > -- > Thanks and Regards, > > Punnadi Gunarathna > Senior Software Engineer, > WSO2, Inc.; http://wso2.com <http://wso2> > Blog: http://hi-my-world.blogspot.com/ > Tel : 94 11 214 5345 > Fax :94 11 2145300 > > > > <http://lalajisureshika.blogspot.com/> > -- Thanks and Regards, Punnadi Gunarathna Senior Software Engineer, WSO2, Inc.; http://wso2.com <http://wso2> Blog: http://hi-my-world.blogspot.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 <http://lalajisureshika.blogspot.com/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
