Github user jieyu commented on a diff in the pull request:
https://github.com/apache/mesos/pull/206#discussion_r106755477
--- Diff: docs/contributors.yaml ---
@@ -167,6 +167,14 @@
- charles.al...@metamarkets.com
jira_user: drcrallen
reviewboard_user: drcrallen
Hi Marcus,
The CNI Spec you are seeing is the latest SPEC of v0.3 . Mesos currently
supports v0.2 and below. You can check out the by looking at the "tags" in
the CNI repo. For e.g.,
https://github.com/containernetworking/cni/blob/v0.4.0/SPEC.md
We have tickets open to support SPEC v0.3. Hopefull
Hi,
I've been working on potentially building a custom CNI plugin. I'm
following the spec found here:
https://github.com/containernetworking/cni/blob/master/SPEC.md
I've found that the documented JSON result for the ADD command doesn't
result in Mesos or upstream frameworks being able to iden
GitHub user chhsia0 opened a pull request:
https://github.com/apache/mesos/pull/206
Update contributors.yaml
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chhsia0/mesos patch-1
Alternatively you can review and apply these chan
OK, I discovered it myself, this test uses absolute paths.
@Benjamin You were right it's not backward compatible. I'll work on this.
mesos 1.3.0 framework failed with mesos 1.3.48291 master and mesos 1.3.0
agent
pt., 17 mar 2017 o 13:44 użytkownik Tomek Janiszewski
napisał:
@Benjamin thanks
@Benjamin thanks for taking a look at this. I tried to run
mesos/test-upgrade.py but it failed on starting the framework? Below are
the logs? What am I doing wrong?
./support/test-upgrade.py --prev build --next build-varint
Running upgrade test from mesos 1.3.0 to mesos 1.3.0
+--+-
