All geek questions in one place

Local development of the mesosphere

I am currently studying the use of Mesosphere in production to run multiple microservices as Docker containers.

I got a DCOS deployment and was able to successfully start one of the services. Before continuing this approach, I also need to capture the side of development (not just Mesos or the mesosphere, but the development of microservices).

Are there any recommendations on how to launch a local deployment of Mesosphere in Vagrantbox or something similar that will allow our developers to launch all the services that are in our ecosystem from existing docker images and launch the one service that you are currently using Does time work from a local code folder?

I already know how to link the devs code folder to the Vagrant machine and also get the Docker part, but I am alienated from losing the whole part of the Mesosphere integration anyway.

Is there anyone who could send me some resource on the Internet that describes a possible solution for this? Have any of you done something similar and would like to share some information about this?

+4
source share
2 answers

Peak like

Mesosphere , DCOS. , DCOS. -. DCOS Enterprise Edition. , -: https://mesosphere.com/contact/ p >

, , , Mesos Marathon.

Disambiguation

2017-08-03

DC/OS:

+4

, ""... , .

, , DCOS, Mesos Marathon Chronos. , CoreOS Mesos/Marathon ( , ..):

  • Vagrant / ( CoreOS/Mesos/Marathon user_data).
  • (, - CoreOS, Mesos/Marathon/Chronos).
  • ( , CoreOS, Mesos 0.25.0 0.14.1)

(TeamCity , Jenkins .. ), Docker Docker. .

API Marathon , , . Docker, , Docker ( "forcePullImage": true, , ).

+1

Source: https://habr.com/ru/post/1629583/

More articles:


All Articles