Thanks everybody for answers. Our use case is to run our BigData platform on top of Mesos, pretty classic setup of Kafka, Spark, ES, HDFS + custom services currently with future extensions for other components as decided. It seems doable with Magnum API. We will currently run mostly barebone but we already know we will need some deployments on top of Openstack where Openstack will be in charge to primarily control resources. We are not in hurry with it so we have some time to work out details. Good to know options exists we will follow to review them closely as more detailed requirements arise.
On Tue, Feb 16, 2016 at 9:28 AM, o...@magnetic.io <o...@magnetic.io> wrote: > Hi Everybody, > > i would also suggest using the Magnum API to do this. For our > Canary-testing/releasing & autoscaling platform Vamp (www.vamp.io) we’re > currently setting up a collaboration project to develop a Vamp-Magnum > driver. This way Vamp workflows can orchestrate and coordinate the scaling > activities between IaaS and Mesos/Marathon (or any other supported > scheduler). This coordination is essential as challenges like bin-packing > and other optimisation strategies will become evident very quickly. > > If there’s interest in collaboration on this please give me a ping! > > cheers, Olaf > > Olaf Molenveld > co-founder / CEO > ------------------------------------- > *magnetic.io <http://magnetic.io>: innovating enterprises* > *VAMP: canary test and release platform for containers* > E: o...@magnetic.io > T: +31653362783 > Skype: olafmol > www.magnetic.io > www.vamp.io > > On 16 Feb 2016, at 09:20, Guangya Liu <gyliu...@gmail.com> wrote: > > Hi Peter, > > Have you ever tried Magnum (https://github.com/openstack/magnum) which is > the container service in OpenStack leveraging HEAT to integrate with > Kubernetes, Swarm and Mesos. With Magnum, you do not need to maintain your > own HEAT template but just let Magnum do this for you, it is more simple > than using HEAT directly. > > The Magnum can now supports both scale up and scale down, when scale down, > the Magnum will select the node which does not have container or have the > least containers. > > The mesos now support "Host Maintain" ( > https://github.com/apache/mesos/blob/master/docs/maintenance.md) which > can be leveraged by HEAT or Magnum, when HEAT or Magnum want to scale down > a host, we can call some cloud-init script to first maintain the host > before HEAT delete it. The host maintain will emit "InverseOffer" and you > can update the framework to handle "InverseOffer" for the host which is > going to be scale down. > > Thanks, > > Guangya > > > On Tue, Feb 16, 2016 at 4:02 PM, Petr Novak <oss.mli...@gmail.com> wrote: > >> Hello, >> we are considering adopting Mesos but at the same time we need to run it >> on top of OpenStack at some places. My main questions is about how and if >> autoscaling defined via HEAT templates works together. And has to be done. >> I assume that scaling up is not much a problem - when Mesos detects more >> resources it notifies frameworks which might scale based on their buildin >> strategies, though I assume it can't be defined in HEAT templates. Scaling >> down has to go through some cooperation between Mesos and HEAT. Do I have >> to update Mesos frameworks source code to somehow listen to OpenStack >> events or something like this? >> >> Is there any ongoing effort from Mesosphere and OpenStack to integrate >> more closely in this regard? >> >> Many thanks for any points regarding other possible problems and any >> clarification, >> Petr >> > > >
