Hey Thomas,
Could you share the scripts you're using to publish to pypi? It's not part
of the release process as of yet:
http://mesos.apache.org/documentation/latest/release-guide/
The 0.21.1 eggs were never published:
https://issues.apache.org/jira/browse/MESOS-2310
On Thu, Aug 14, 2014 at
There is one important step to do during the upgrade:
- Upgrade your python framework and executor. You'll be able to either
import using the new configuration or the old. Replace the existing
imports with this:
try:
from mesos.native import MesosExecutorDriver, MesosSchedulerDriver
Thomas,
We are about to cut the 0.20.0 release. I am updating the docs/upgrades.md.
Regarding the python binding change, can you let us know the exact deploy
procedure if someone is using the old python binding?
More specifically, say all masters/slaves/executors/schedulers are using
0.19.1.
It might work to use
0.19 with a 0.20 mesos (or visa versa), but there be dragons =)
Is there a deprecation cycle? How should folks be upgrading Python
schedulers
and executors to 0.20.0 if they are not statically bundling libmesos?
Is there an upgrade order required?
We will need to
You'll want to match the python bindings to your mesos version as the
functionality is coming from libmesos itself. It might work to use
0.19 with a 0.20 mesos (or visa versa), but there be dragons =)
On Fri, Aug 1, 2014 at 1:30 PM, Jie Yu yujie@gmail.com wrote:
Thomas,
Thank you for the
- What problem are we trying to solve?
Currently, the python bindings group protobufs, stub implementations
and compiled code into a single python package that cannot be
distributed easily. This forces python projects using mesos to copy
protobufs around and forces a onerous dependency on anyone
`pip install mesos.interface` now works =)
On Fri, Aug 1, 2014 at 9:37 AM, Thomas Rampelberg tho...@saunter.org wrote:
- What problem are we trying to solve?
Currently, the python bindings group protobufs, stub implementations
and compiled code into a single python package that cannot be
Thomas,
Thank you for the heads-up. One question: what if mesos and python binding
have different versions? For example, is it ok to use a 0.19.0 python
binding and having a 0.20.0 mesos? Same question for the reverse.
- Jie
On Fri, Aug 1, 2014 at 9:37 AM, Thomas Rampelberg tho...@saunter.org
Woah, this is really awesome Thomas! Especially the pip install ;-)
Looking forward to bringing pesos up to speed with this.
On 1 August 2014 21:30, Jie Yu yujie@gmail.com wrote:
Thomas,
Thank you for the heads-up. One question: what if mesos and python binding
have different versions?
