mesos / cloudfoundry-mesos Goto Github PK

View Code? Open in Web Editor NEW

108.0 41.0 26.0 148 KB

Cloud Foundry on Mesos Framework

License: Apache License 2.0

Go 100.00%

cloudfoundry-mesos's People

Stargazers

Watchers

cloudfoundry-mesos's Issues

Modify diego-release to use modified auctioneer

Rather than manually replacing the auctioneer binary (noted here: https://github.com/mesos/cloudfoundry-mesos/blob/master/docs/getting-started.md), I would recommend forking and modifying the Diego BOSH release to deploy the modified auctioneer itself.
-You will need to modify the job template for the auctioneer https://github.com/cloudfoundry-incubator/diego-release/blob/develop/jobs/auctioneer/templates/auctioneer_ctl.erb
-The only other step you should need would be to replace the auctioneer submodule in the diego-release with your auctioneer (it would make sense to fork the CF auctioneer and put your changes in there to streamline this process).

Failed to push app in Cloud Foundry on Mesos environment

Hi,

I followed the steps in https://github.com/mesos/cloudfoundry-mesos/blob/master/docs/getting-started.md to set up a Cloud Foundry on Mesos env, basically in my env, there is only one physical machine which has vagrant and virtualbox installed, and there are two VMs on this physical machine:

The first VM was created by Bosh-Lite and has CF and Diego deployed in it
The second VM has Mesos 0.25.0 (both Mesos master and Mesos slave ) deployed in it, and I also installed docker in it and pulled the image "jianhuiz/diego-cell":

# docker images
docker images 
REPOSITORY            TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
jianhuiz/diego-cell   219-1434-307        05ca264e13b6        8 weeks ago         1.425 GB
jianhuiz/diego-cell   latest              05ca264e13b6        8 weeks ago         1.425 GB

And I also patched auctioneer so that it can register Mesos as a framework, see the Mesos master log:

I1231 13:07:23.623427 25130 master.cpp:2179] Received SUBSCRIBE call for framework 'Diego Scheduler' at scheduler(1)@10.244.16.134:40726
I1231 13:07:23.623734 25130 master.cpp:2250] Subscribing framework Diego Scheduler with checkpointing disabled and capabilities [  ]
I1231 13:07:23.625143 25136 hierarchical.hpp:515] Added framework 04e03265-6fbf-4925-a484-b0010b412ffc-0006

Everything looks good at this point, and then I pushed the hello world app (https://github.com/jianhuiz/cf-apps/tree/master/hello) from the physical machine, but it failed:

root@machine1~/workspace/cf-apps/hello> cf push 
Using manifest file /root/workspace/cf-apps/hello/manifest.yml

Creating app hello in org diego / space diego as admin...
OK

Using route hello.bosh-lite.com
Binding hello.bosh-lite.com to hello...
OK

Uploading hello...
Uploading app files from: /root/workspace/cf-apps/hello
Uploading 1020B, 2 files
Done uploading               
OK

Starting app hello in org diego / space diego as admin...

FAILED
hello failed to stage within 15.000000 minutes

The following is what I saw in Mesos slave log for how a task was handled:

I1231 13:38:06.042736 25308 slave.cpp:1270] Got assigned task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d for framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:38:06.044637 25308 gc.cpp:84] Unscheduling '/tmp/mesos/slaves/04e03265-6fbf-4925-a484-b0010b412ffc-S0/frameworks/04e03265-6fbf-4925-a484-b0010b412ffc-0007' from gc
I1231 13:38:06.045428 25308 gc.cpp:84] Unscheduling '/tmp/mesos/slaves/04e03265-6fbf-4925-a484-b0010b412ffc-S0/frameworks/04e03265-6fbf-4925-a484-b0010b412ffc-0007/executors/diego-executor' from gc
I1231 13:38:06.046202 25308 slave.cpp:1386] Launching task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d for framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:38:06.055021 25308 slave.cpp:4852] Launching executor diego-executor of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 with resources  in work directory '/tmp/mesos/slaves/04e03265-6fbf-4925-a484-b0010b412ffc-S0/frameworks/04e03265-6fbf-4925-a484-b0010b412ffc-0007/executors/diego-executor/runs/3aed6c87-bbab-4ed6-8504-3fdcf5d030f9'
I1231 13:38:06.056267 25308 slave.cpp:1604] Queuing task 'de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d' for executor diego-executor of framework '04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:38:06.067430 25303 docker.cpp:766] Starting container '3aed6c87-bbab-4ed6-8504-3fdcf5d030f9' for executor 'diego-executor' and framework '04e03265-6fbf-4925-a484-b0010b412ffc-0007'
I1231 13:38:17.363279 25306 slave.cpp:2379] Got registration for executor 'diego-executor' of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 from executor(1)@192.168.33.10:36629
I1231 13:38:17.365413 25309 docker.cpp:1016] Ignoring updating container '3aed6c87-bbab-4ed6-8504-3fdcf5d030f9' with resources passed to update is identical to existing resources
I1231 13:38:17.366082 25309 slave.cpp:1760] Sending queued task 'de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d' to executor 'diego-executor' of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:38:17.370671 25309 slave.cpp:2717] Handling status update TASK_STARTING (UUID: bfa93e28-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 from executor(1)@192.168.33.10:36629
I1231 13:38:17.371459 25309 status_update_manager.cpp:322] Received status update TASK_STARTING (UUID: bfa93e28-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:38:17.372618 25310 slave.cpp:3016] Forwarding the update TASK_STARTING (UUID: bfa93e28-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 to [email protected]:5050
I1231 13:38:17.373111 25310 slave.cpp:2946] Sending acknowledgement for status update TASK_STARTING (UUID: bfa93e28-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 to executor(1)@192.168.33.10:36629
I1231 13:38:17.381140 25309 status_update_manager.cpp:394] Received status update acknowledgement (UUID: bfa93e28-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:38:18.382237 25309 slave.cpp:2717] Handling status update TASK_RUNNING (UUID: c043858f-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 from executor(1)@192.168.33.10:36629
I1231 13:38:18.383672 25306 status_update_manager.cpp:322] Received status update TASK_RUNNING (UUID: c043858f-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:38:18.385082 25307 slave.cpp:3016] Forwarding the update TASK_RUNNING (UUID: c043858f-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 to [email protected]:5050
I1231 13:38:18.385604 25307 slave.cpp:2946] Sending acknowledgement for status update TASK_RUNNING (UUID: c043858f-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 to executor(1)@192.168.33.10:36629
I1231 13:38:18.393615 25308 status_update_manager.cpp:394] Received status update acknowledgement (UUID: c043858f-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:39:46.461815 25309 slave.cpp:2717] Handling status update TASK_FINISHED (UUID: f4c37272-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 from executor(1)@192.168.33.10:36629
W1231 13:39:46.463006 25309 docker.cpp:1028] Ignoring update as no supported resources are present
I1231 13:39:46.463824 25308 status_update_manager.cpp:322] Received status update TASK_FINISHED (UUID: f4c37272-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:39:46.464979 25304 slave.cpp:3016] Forwarding the update TASK_FINISHED (UUID: f4c37272-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 to [email protected]:5050
I1231 13:39:46.465512 25304 slave.cpp:2946] Sending acknowledgement for status update TASK_FINISHED (UUID: f4c37272-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 to executor(1)@192.168.33.10:36629
I1231 13:39:46.473815 25305 status_update_manager.cpp:394] Received status update acknowledgement (UUID: f4c37272-afc3-11e5-a4c5-080027ca3ef9) for task de94ffb7-940e-4a81-9b05-d744dc6f72a5-cd164ebc23264d0da8d3bedb2acdb10d of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:39:51.973965 25307 docker.cpp:1592] Executor for container '3aed6c87-bbab-4ed6-8504-3fdcf5d030f9' has exited
I1231 13:39:51.974119 25307 docker.cpp:1390] Destroying container '3aed6c87-bbab-4ed6-8504-3fdcf5d030f9'
I1231 13:39:51.974411 25307 docker.cpp:1494] Running docker stop on container '3aed6c87-bbab-4ed6-8504-3fdcf5d030f9'
I1231 13:39:51.975558 25304 slave.cpp:3433] Executor 'diego-executor' of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007 has terminated with unknown status
I1231 13:39:51.976263 25304 slave.cpp:3544] Cleaning up executor 'diego-executor' of framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:39:51.976714 25308 gc.cpp:56] Scheduling '/tmp/mesos/slaves/04e03265-6fbf-4925-a484-b0010b412ffc-S0/frameworks/04e03265-6fbf-4925-a484-b0010b412ffc-0007/executors/diego-executor/runs/3aed6c87-bbab-4ed6-8504-3fdcf5d030f9' for gc 6.99998869856593days in the future
I1231 13:39:51.976972 25304 slave.cpp:3633] Cleaning up framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007
I1231 13:39:51.976969 25308 gc.cpp:56] Scheduling '/tmp/mesos/slaves/04e03265-6fbf-4925-a484-b0010b412ffc-S0/frameworks/04e03265-6fbf-4925-a484-b0010b412ffc-0007/executors/diego-executor' for gc 6.99998869405037days in the future
I1231 13:39:51.977311 25308 gc.cpp:56] Scheduling '/tmp/mesos/slaves/04e03265-6fbf-4925-a484-b0010b412ffc-S0/frameworks/04e03265-6fbf-4925-a484-b0010b412ffc-0007' for gc 6.99998868960889days in the future
I1231 13:39:51.977401 25304 status_update_manager.cpp:284] Closing status update streams for framework 04e03265-6fbf-4925-a484-b0010b412ffc-0007

In the above log, I can see the task can be started and running, but later (about 1 min) it finished, and then the executor exited which seems not correct ...

Any help will be appreciated!

BTW, before I patched auctioneer, the app can be pushed successfully and running very well in the original Cloud Foundry + Diego env (without integrating with Mesos)

Is this project dead?

No updates in some time, and dependencies are old versions of CF. Will this project be updated?

Translating Diego Resource to Mesos Resource

There's no clear translation between Diego's concept of a Resource, and Mesos' concept of a resource:

cloudfoundry-mesos/scheduler/scheduler_interface.go

Line 9 in 85dcd82

// TODO: how to allocate cpu since no cpu requirement in diego auction

We should look into ways to determine the CPU requirement of a Diego task and the Container Capacity of a Mesos Resource Offer.

is the project still continue to maintain? thanks!

Project rationale missing from the docs

Great job !

I couldn't find in the documentation + links provided a good overview of the rationale for this effort. In other words, why would I want to replace the auction process from Diego by Mesos offers? Are we talking about better performance, more features, etc. ? What in your particular case led you to bridge between both systems and host the cells into a docker container controlled by Mesos?

Do you have any insight to share ?

Issue in "patch and build auctioneer"

Hi,
I encountered this error when follow the "patch and build auctioneer" of getting started.

go get ./...
# github.com/mesos/cloudfoundry-mesos/scheduler
../../../../mesos/cloudfoundry-mesos/scheduler/init.go:50: cannot use secret (type []byte) as type *string in field value

I changed below lines in init.go and it succeeded in compiling auctioneer

                secret, err := ioutil.ReadFile(*mesosAuthSecretFile)
                str_secret := string(secret[:])
                ...
                cred = &mesos.Credential{
                        Principal: proto.String(*mesosAuthPrincipal),
                        Secret:    &str_secret,
                }

Have you met this issue before? or it is related with my host environment?

Lack of clear setup description

Hey - i've been trying to setup this project as part of an evaluation spike but have to admit am getting nowhere. Would it be possible to have a clear description of how this was tested ? The executor does not seem to start for me and dies after a bit, the auctioneer code appears to be stale and so on. Is this project still active ?

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.