Inline with $subject, we have now moved previously implemented Mesos Membership Scheme to dcos-common repository with commit history: https://github.com/wso2/dcos-common
We have also renamed the term Mesos to DC/OS in the following pull request: https://github.com/wso2/dcos-common/pull/2 Really appreciate your thoughts on this. Thanks Imesh On Wed, Jan 24, 2018 at 9:06 PM, Imesh Gunaratne <im...@wso2.com> wrote: > Hi All, > > I created resources for deploying WSO2 API-M on DC/OS v1.10: > https://github.com/wso2/dcos-apim/pull/2 > > This includes three Marathon applications for orchestrating one MySQL > instance, one API-M instance and one API-M Analytics instance. The MySQL > Marathon application is only intended for evaluation purposes, for > enterprise deployments a production ready RDBMS would need to be used. > > Moving forward, we need to improve this and support API-M deployment > pattern 1 by adding one more API-M instance and one additional API-M > Analytics instance. Afterwards similar resources need to be created for all > five API-M deployment patterns. > > Compared to DC/OS v1.7, I noticed following improvements in DC/OS v1.10: > > - Container to container communication with overlay networking > - Service discovery with Minuteman > - Built-in Marathon runtime > > Please try this out and let me know your thoughts. > > [1] https://docs.mesosphere.com/1.10/ > [2] https://github.com/dcos/minuteman > > Thanks > Imesh > > -- > *Imesh Gunaratne* > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 <+94%2077%20374%202057> > W: https://medium.com/@imesh TW: @imesh > lean. enterprise. middleware > > -- *Imesh Gunaratne* WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@imesh TW: @imesh lean. enterprise. middleware
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
