Re: Fwd: [Breaking Change 0.24 & Upgrade path] ZooKeeper MasterInfo change.

[CCAAT]

On 09/25/2015 04:34 PM, Raúl Gutiérrez Segalés wrote:


On Sep 25, 2015 9:08 AM, "Marco Massenzio" > wrote:
 >
 > +1 to what Alex says.
 >
 > As far as we know, the functionality we use (ephemeral sequential
nodes and writing simple data to a znode) is part of the "base API"
offered by ZooKeeper and every version would support it.
 > (then again, not a ZK expert here - if anyone knows better, please
feel free to correct me).
 >

Yup, not of that is changing in the upcoming ZooKeeper releases (3.4.7 &
3.5.2) and probably never will.

-rgs




That simplifies the related dependencies for zookeeper.


Thanks,
James

Re: Official RPMs

[Artem Harutyunyan]

We use https://github.com/mesosphere/mesos-deb-packaging in conjunction
with some internal tooling (that Marco mentioned) to distribute package
building. So you should be able to find all the actual package building
code in that repo. Please let us know if you have questions.

Cheers,
Artem.

On Saturday, September 26, 2015, CCAAT  wrote:

> On 09/25/2015 07:36 PM, Marco Massenzio wrote:
>
>> Yes, the plan is definitely to make the tooling available to the
>> project: there is nothing "secret" about it - at the moment,
>> unfortunately, it relies on a bit of internal infrastructure and, well,
>> yesss, it's a bit too crafty to be ready for "external consumption"
>> but we're working on it!
>>
>
> Hello Marco,
>
> I' packaging up for gentoo linux. Just the itemized list of
> what/where/when you setup config files and such would be a keen help to my
> efforts. I can substitute in gentoo-centric tools, if you can provide a
> brief description on what your infra/tools are doing.
> A skeletal spec, if you like.
>
>
> James
>
>
>
>
>
>> /Marco Massenzio/
>> /Distributed Systems Engineer
>> http://codetrips.com/
>>
>> On Fri, Sep 25, 2015 at 11:33 AM, Zameer Manji > > wrote:
>>
>> Could mesosphere donate their tooling for packaging mesos to the
>> project? This way any project member or contributor can build
>> packages and it can be apart of the release process.
>>
>> On Fri, Sep 25, 2015 at 10:53 AM, Artem Harutyunyan
>> > wrote:
>>
>> The repositories have been updated yesterday, and the downloads
>> page
>> was updated today. Mesos 0.24 packages are now available at
>> https://mesosphere.com/downloads/. Thank you very much for your
>> patience!
>>
>> Cheers,
>> Artem.
>>
>> On Tue, Sep 22, 2015 at 11:02 AM, Marco Massenzio
>> > wrote:
>>  > Hi guys,
>>  >
>>  > just wanted to let you all know that we (Mesosphere) fully
>> intend to
>>  > continue supporting distributing binary packages for the
>> current set of
>>  > supported OSes (namely, Ubuntu / Debian / RedHat / CentOS as
>> listed in [0]).
>>  >
>>  > Sorry that 0.24 slipped through the cracks, the person who
>> actually takes
>>  > care of that and knows the magic incantations has been
>> unwell, and a number
>>  > of other competing priorities got in the way - we will
>> eventually be
>>  > automating the process, so that downloadable binary packages
>> are created out
>>  > of each release/RC build (and, possibly, even more often)
>> without pesky
>>  > humans getting in the way :) but this may take some time.
>>  > We're building the 0.24 ones as we speak, so please bear with
>> us while this
>>  > gets done.
>>  >
>>  > Any questions / suggestions, we'd love to hear those too!
>>  >
>>  > [0] https://mesosphere.com/downloads/
>>  >
>>  > Marco Massenzio
>>  > Distributed Systems Engineer
>>  > http://codetrips.com
>>  >
>>  > On Tue, Sep 22, 2015 at 10:54 AM, CCAAT
>> > wrote:
>>  >>
>>  >> On 09/21/2015 03:01 PM, Vinod Kone wrote:
>>  >>>
>>  >>> +Jake Farrell
>>  >>>
>>  >>> The mesos project doesn't publish platform dependent
>> artifacts.  We
>>  >>> currently only publish platform independent artifacts like
>> JAR (to
>>  >>> apache maven) and interface EGG (to PyPI).
>>  >>>
>>  >>> Recently we made the decision
>>  >>>
>> > >
>> for
>>  >>> the project to not officially support different language
>> (java, python)
>>  >>> framework libraries going forward (likely after 1.0). The
>> project will
>>  >>> only support C++ libraries which will live in the repo and
>> link to other
>>  >>> language libraries from our website.
>>  >>>
>>  >>> The main reason was that the PMC lacks the expertise to
>> support various
>>  >>> language bindings and hence we wanted to remove the support
>> burden.
>>  >>>
>>  >>> Option #1) It looks like we could do a similar thing with
>> RPMs/DEBs,
>>  >>> i.e., link to 3rd party artifacts from the project website.
>> Similar to
>>  >>> the client library authors, we could hold package maintainers
>>  >>> accountable by providing guidelines.
>>  >>>
>>  >>> Option #2) Since the project officially 

Re: OS X build

[James Peach]

> On Sep 26, 2015, at 12:01 PM, Vaibhav Khanduja  
> wrote:
> 
> I am running into issues with build on my MAC - OSX … the configure scripts 
> complaints about libapr-1 not present. I was able to find a workaround by 
> passing configure with —with-apr option. Looks like the script checks for 
> variable to be valid shell variable, if not it is rejected.
> 
> I was able workaround with having quotes and missing a “-“ for the variable
> 
>  ../configure -disable-python --disable-java 
> "-with-apr=/usr/local/Cellar/apr/1.5.2/libexec/“
> 
> the configure —help though suggests to use —with-apr

AFAICT you are supposed to use apr-1-config to fish out the libapr path when 
using Homebrew. I think that is would be reasonable for the Mesos build to just 
automatically use apr-1-config if it is present.

./configure --with-apr=$(apr-1-config --prefix)

>  
> 
> am I missing something here?
> 
> Thx

Re: Official RPMs

[CCAAT]

On 09/25/2015 07:36 PM, Marco Massenzio wrote:

Yes, the plan is definitely to make the tooling available to the
project: there is nothing "secret" about it - at the moment,
unfortunately, it relies on a bit of internal infrastructure and, well,
yesss, it's a bit too crafty to be ready for "external consumption"
but we're working on it!


Hello Marco,

I' packaging up for gentoo linux. Just the itemized list of 
what/where/when you setup config files and such would be a keen help to 
my efforts. I can substitute in gentoo-centric tools, if you can provide 
a brief description on what your infra/tools are doing.

A skeletal spec, if you like.


James






/Marco Massenzio/
/Distributed Systems Engineer
http://codetrips.com/

On Fri, Sep 25, 2015 at 11:33 AM, Zameer Manji > wrote:

Could mesosphere donate their tooling for packaging mesos to the
project? This way any project member or contributor can build
packages and it can be apart of the release process.

On Fri, Sep 25, 2015 at 10:53 AM, Artem Harutyunyan
> wrote:

The repositories have been updated yesterday, and the downloads page
was updated today. Mesos 0.24 packages are now available at
https://mesosphere.com/downloads/. Thank you very much for your
patience!

Cheers,
Artem.

On Tue, Sep 22, 2015 at 11:02 AM, Marco Massenzio
> wrote:
 > Hi guys,
 >
 > just wanted to let you all know that we (Mesosphere) fully
intend to
 > continue supporting distributing binary packages for the
current set of
 > supported OSes (namely, Ubuntu / Debian / RedHat / CentOS as
listed in [0]).
 >
 > Sorry that 0.24 slipped through the cracks, the person who
actually takes
 > care of that and knows the magic incantations has been
unwell, and a number
 > of other competing priorities got in the way - we will
eventually be
 > automating the process, so that downloadable binary packages
are created out
 > of each release/RC build (and, possibly, even more often)
without pesky
 > humans getting in the way :) but this may take some time.
 > We're building the 0.24 ones as we speak, so please bear with
us while this
 > gets done.
 >
 > Any questions / suggestions, we'd love to hear those too!
 >
 > [0] https://mesosphere.com/downloads/
 >
 > Marco Massenzio
 > Distributed Systems Engineer
 > http://codetrips.com
 >
 > On Tue, Sep 22, 2015 at 10:54 AM, CCAAT
> wrote:
 >>
 >> On 09/21/2015 03:01 PM, Vinod Kone wrote:
 >>>
 >>> +Jake Farrell
 >>>
 >>> The mesos project doesn't publish platform dependent
artifacts.  We
 >>> currently only publish platform independent artifacts like
JAR (to
 >>> apache maven) and interface EGG (to PyPI).
 >>>
 >>> Recently we made the decision
 >>>

for
 >>> the project to not officially support different language
(java, python)
 >>> framework libraries going forward (likely after 1.0). The
project will
 >>> only support C++ libraries which will live in the repo and
link to other
 >>> language libraries from our website.
 >>>
 >>> The main reason was that the PMC lacks the expertise to
support various
 >>> language bindings and hence we wanted to remove the support
burden.
 >>>
 >>> Option #1) It looks like we could do a similar thing with
RPMs/DEBs,
 >>> i.e., link to 3rd party artifacts from the project website.
Similar to
 >>> the client library authors, we could hold package maintainers
 >>> accountable by providing guidelines.
 >>>
 >>> Option #2) Since the project officially supports certain
platforms
 >>> (Ubuntu, CentOS, OSX) and continuously tests this via CI,
we could've
 >>> the CI continuously build and upload the packages. Not sure
what's ASF
 >>> stance on this is. I filed a ticket
 >>>  a while
ago with
 >>> INFRA regarding something similar, but never received any
response.
 >>>
 >>> Personally, with the direction the project is headed
towards, I prefer
 >>> #1.
 >>
 >>
 >> +1 (Option #1)
 >>
 >> This 'Option #1' approach will require the 

OS X build

[Vaibhav Khanduja]

I am running into issues with build on my MAC - OSX … the configure scripts
complaints about libapr-1 not present. I was able to find a workaround by
passing configure with —with-apr option. Looks like the script checks for
variable to be valid shell variable, if not it is rejected.

I was able workaround with having quotes and missing a “-“ for the variable

 ../configure -disable-python --disable-java
"-with-apr=/usr/local/Cellar/apr/1.5.2/libexec/“

the configure —help though suggests to use —with-apr

am I missing something here?

Thx