Bug#760315: ITP: mesos -- Cluster manager for sharing distributed application frameworks
Alive! -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Bug#760315: ITP: mesos -- Cluster manager for sharing distributed application frameworks
On 30.08.2015 17:49, Dmitry Smirnov wrote: Hi Daniel, On Sunday 16 August 2015 12:26:51 Daniel Stender wrote: Yes, great, if you would like to share your preliminary work that would be very much welcome! I'll keep that in deb/copyright. I finally committed my draft packaging to http://anonscm.debian.org/cgit/collab-maint/mesos.git It is far from being usable. There are no Java/Python bindings and I did not test services. There is a lot of work ahead but I've made some progress with build-ability of a messy source tree -- very time consuming... And ... yes, I'm all right with a repo outline like this, let's do it that way. Please feel free to do any changes in the Mesos repository to your best convenience. :) Probably I won't be working on Mesos any time soon. I'll try to focus on Kubernetes and see how it goes... Thank you very much! I'll take a look in a couple of days. I've seen the Kubernetes ITP, another great devops app. Best for that! Till next time, Daniel -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
Bug#760315: ITP: mesos -- Cluster manager for sharing distributed application frameworks
Hi Daniel, On Sunday 16 August 2015 12:26:51 Daniel Stender wrote: Yes, great, if you would like to share your preliminary work that would be very much welcome! I'll keep that in deb/copyright. I finally committed my draft packaging to http://anonscm.debian.org/cgit/collab-maint/mesos.git It is far from being usable. There are no Java/Python bindings and I did not test services. There is a lot of work ahead but I've made some progress with build-ability of a messy source tree -- very time consuming... And ... yes, I'm all right with a repo outline like this, let's do it that way. Please feel free to do any changes in the Mesos repository to your best convenience. :) Probably I won't be working on Mesos any time soon. I'll try to focus on Kubernetes and see how it goes... -- Regards, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part.
Bug#760315: ITP: mesos -- Cluster manager for sharing distributed application frameworks
On 16.08.2015 05:02, Dmitry Smirnov wrote: Hi Daniel, It is great to see that you are working on packaging Mesos. For some time already I was also fiddling with its packaging but was (and still) reluctant to take over the RFS... It seems that Mesos have systematic issues with versioning of the libraries from libmesos all the way down to libprocess and libgmock. Because of this it might be best to refrain from packaging standalone libprocess and use its bundled copy (statically linked or installed to private location) until this problem is fixed upstream. My Mesos packaging is in very early draft stage but I might be able to contribute few things if you consider working in public repository (i.e. at collab-maint, etc.). Also due to burden of bundled upstream dependencies I recommend to use shallow (debian/* only) repository layout like the one that KDE team uses: https://pkg-kde.alioth.debian.org/gitguidelines.html Thank you. Hi Dmitry, I going to fix a couple of smaller packages from my WNPP stack before, but I am very interested in this. Thank you for the pointer on the libraries issue here, I'll keep that mind when I get into it, probably I'll approach you on this again, then. Yes, great, if you would like to share your preliminary work that would be very much welcome! I'll keep that in deb/copyright. And ... yes, I'm all right with a repo outline like this, let's do it that way. Greetings, Daniel -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
Bug#760315: ITP: mesos -- Cluster manager for sharing distributed application frameworks
Hi Daniel, It is great to see that you are working on packaging Mesos. For some time already I was also fiddling with its packaging but was (and still) reluctant to take over the RFS... It seems that Mesos have systematic issues with versioning of the libraries from libmesos all the way down to libprocess and libgmock. Because of this it might be best to refrain from packaging standalone libprocess and use its bundled copy (statically linked or installed to private location) until this problem is fixed upstream. My Mesos packaging is in very early draft stage but I might be able to contribute few things if you consider working in public repository (i.e. at collab-maint, etc.). Also due to burden of bundled upstream dependencies I recommend to use shallow (debian/* only) repository layout like the one that KDE team uses: https://pkg-kde.alioth.debian.org/gitguidelines.html Thank you. -- Regards, Dmitry Smirnov GPG key : 4096R/53968D1B --- The great enemy of the truth is very often not the lie -- deliberate, contrived and dishonest, but the myth, persistent, persuasive, and unrealistic. Belief in myths allows the comfort of opinion without the discomfort of thought. -- John F Kennedy signature.asc Description: This is a digitally signed message part.
