With this architecture, will Stratos be a wrapper for different other PaaS frameworks?
With Jclouds we get a unified interface for multiple IaaSes, with this approach we thinking of proposing Stratos to provide a unified interface to talk to different PaaS s? On Wed, Apr 13, 2016 at 5:38 PM, Chamil de Alwis <cham...@apache.org> wrote: > As Lakmal mentioned, IMO it is important to focus on a single user > experience on top of multiple PaaS frameworks. Various PaaSes have their > own implementations and compositions of common PaaS and Container cluster > related concepts. IMO Stratos Ignite Architecture should scope, at least > initially, to consolidate these concepts to a single abstraction. This > should add minimum new knowledge as it could easily become a new "PaaS" to > learn if the abstraction becomes too complex. > > Go lang has proven itself to be able to handle development processes > involved with current Container related space, so I'm +1 to use it. > > > Regards, > Chamila de Alwis > Committer and PMC Member - Apache Stratos > Blog: code.chamiladealwis.com > > On Wed, Apr 13, 2016 at 10:27 PM, Raj Chudasama <raj.chudas...@gmail.com> > wrote: > >> this looks great! >> >> i hope that you all keep this open to dev community for input as well as >> share your progress. please take all your decisions through the >> appropriate Apache 2.0 guidelines. >> >> i can see a bright future with these changes. GO did bring many >> improvements to PCF. >> >> >> >> On Tue, Apr 12, 2016 at 7:59 PM, Lakmal Warusawithana <lak...@apache.org> >> wrote: >> >>> Hi Devs, >>> >>> Couple of time community were discussed about Stratos refacing to carter >>> new technology and threads. Yesterday I have met (unplanned meeting) few >>> PMC/committers (Lakmal, Imesh, Akila, Chamilad, IsuruH) offline and >>> discussed and came up $subject. Please share your valuable thoughts and >>> feedback. >>> >>> Stratos 4.x and previous versions are mainly focused on run application >>> on top of IaaS. To support multiple IaaSes, we used apache jclouds. But >>> rise of the container technology future app dev and deployment will couple >>> with containers not VM. Because of that we have integrated k8s support in >>> Stratos 4.1.x release. But if we carefully looked at 4.1.x and new k8s >>> releases, we are adding additional layer to k8s without any benefits. >>> Personally I don't like to duplicate engineering effort if it does not >>> giving any value to community. This is the background that we thought of >>> why Stratos need refacing. >>> >>> Stratos 5.0 - proposing name "Ignite Architecture", we though of fully >>> focus on container based application development/deployment. >>> >>> >>> >>> We do not want to reinvent or compete with current PaaS providers. We >>> propose to change the strategy to support multi PaaS instead of support >>> multiple IaaS(Stratos 4.x). In high level, Stratos will provide unique >>> workflow across deferent PaaS to deploy apps. Users are not going to tie up >>> with PaaS vendors, they will have flexibility to use any PaaS. Stratos will >>> play a role in-between PaaS and SaaS. Initially we can start with k8s >>> (since we all have domain knowledge) then will add Mesos, CF, ECS etc >>> support. >>> >>> User experience should be very simple. One main problem I have seen in >>> all of these PaaS, their technologies are very complicate to understand >>> average user. >>> >>> This is total rewrite of Stratos. We discussed to rewrite with GO, main >>> reason Stratos itself should run in-side a container. >>> >>> Please share your thoughts. >>> >>> p.s: @(Imesh, Akila, Chamilad, IsuruH) please add if I missed anything. >>> >>> -- >>> Lakmal Warusawithana >>> Vice President, Apache Stratos >>> Blog : http://lakmalsview.blogspot.com/ >>> >> >> > -- Sajith Kariyawasam *Committer and PMC member, Apache Stratos, * *WSO2 Inc.; http://wso2.com <http://wso2.com>* *Mobile: 0772269575*
