Unable to 'up' about vagrant-mesos

[everpeace]

@yaronr Thank you for trying my project!!

We should use Ubuntu 14.04 because 13.04 has already reached at End of Life.
https://wiki.ubuntu.com/Releases

I will push the changes in several days.

If you wanted to try it by yourself, please use a vagrantbox of 14.04 like below in your Vagrantfile:

  config.vm.provider :virtualbox do |vb, override|
    override.vm.box = "Official Ubuntu 14.04 daily Cloud Image amd64 (Development release,  No Guest Additions)"
    override.vm.box_url = "https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"

Thanks!

[everpeace]

I believe your issue has been fixed in a2ad21d. so, I close this issue.
Please feel free to re-open this issue if you wanted.

[yaronr]

@everpeace Thank YOU for sharing all this work and effort with the community. Great work!
I will try out the new commit

[yaronr]

I'm new to GIT

Can you please tell me how to get this update?
Did git checkout, but apparently 'I have the latest' (origin/master)

10x.

(Y)

On Aug 4, 2014, at 6:38 PM, Shingo Omura [email protected] wrote:

I believe your issue has been fixed in a2ad21d. so, I close this issue.
Please feel free to re-open this issue if you wanted.

—
Reply to this email directly or view it on GitHub.

[everpeace]

If your working directory was clean,

$ git status
# On branch master
nothing to commit (working directory clean)

please try this

$ git pull origin master

Or, if you work with YOUR own forked repo, please try this

$ git remote add upstream https://github.com/everpeace/cookbook-mesos.git
$ git pull upstream master

I recommend you to finish git tutorial, like : https://www.atlassian.com/git/tutorial/git-basics.

[yaronr]

Hi

FYI, inspired by your vagrant-mesos project, I created a Docker based Mesos (+Storm) setup on github: https://github.com/yaronr/docker-mesos

I liked the simplicity and elegance of fig + docker, and the dev-ops implications (especially resource consumption) - so my shared project uses that approac )
It would be great if you could take a look and maybe contribute.

Cheers,
(Y)

[everpeace]

Wow! Thank you for the information!

I also have been thinking vagrant is a little bit 'heavy' in laptop even though it has 8GB memory. Actually, this is one of reasons why I supported AWS provider in my project though. Anyway, I'm glad to hear your contribution :-)

I recommend you to mention your work to @ApacheMesos in twitter. Then, I expect they retweet your work to mesos developer community!

[yaronr]

Regarding @ApacheMesos - that's a great idea, but only after we make some improvements - right now I'm not sure it's good enough.
Your help will be appreciated

I'm assembling a group of very good people to help take this project forward, and I would like to invite you to join. I think you would enjoy collaborating with the team.

What do you say?

(Y)

On Aug 12, 2014, at 7:37 PM, Shingo Omura [email protected] wrote:

Wow! Thank you for the information!

I also have been thinking vagrant is a little bit 'heavy' in laptop even though it has 8GB memory. Actually, this is one of reasons why I supported AWS provider in my project though. Anyway, I'm glad to hear your contribution :-)

I recommend you to mention your work to @ApacheMesos in twitter. Then, I expect they retweet your work to mesos developer community!

—
Reply to this email directly or view it on GitHub.

[everpeace]

I'm glad to hear that.

With all due respect, I noticed mesosphere guys already started similar project mesosphere/docker-containers.

I am happy to join your team, though. But I think it's better for us to contribute mesosphere's project than creating multiple similar projects.

What do you think??

[yaronr]

Hi

I'm glad to hear that you want to join!

I think that mesosphere/docker-containers is all about running using docker inside mesos, which is the opposite of what I'm trying to do - running mesos on top of docker.

I have started this project after trying to find existing projects that do that, including mesosphere/docker-containers, and - contacting mesosphere.
I believe that if we get a decent setup together, the mesosphere guys will happily take over from that point, and fork it into mesos/.. (but it's probably not going to be mesos/docker-containers)

(Y)

On Aug 15, 2014, at 9:53 AM, Shingo Omura [email protected] wrote:

I'm glad to hear that.

With all due respect, I noticed mesosphere guys already started similar project mesosphere/docker-containers.

I am happy to join your team, though. But I think it's better for us to contribute mesosphere's project than creating multiple similar projects.

—
Reply to this email directly or view it on GitHub.