[RESULT][VOTE] Release Apache Aurora 0.19.x packages

[Renan DelValle]

All,
The vote to accept the proposed packages as our official binary packages
for Apache Aurora 0.19.x has passed.


+1 (Binding)
--
Renan DelValle
David McLaughlin
Stephan Erb

There were no 0  or-1 votes. There were no non-binding votes.

The official packages are now available here:
https://dl.bintray.com/apache/aurora/

The GPG key used to sign the release are available at:
https://dist.apache.org/repos/dist/release/aurora/KEYS

Thank you to all who helped make this release.

-Renan

On Sun, Feb 25, 2018 at 4:20 AM, Stephan Erb 
wrote:

> +1
>
> On 21.02.18, 20:01, "David McLaughlin"  wrote:
>
> +1 from me.
>
> On Wed, Feb 21, 2018 at 9:57 AM, Renan DelValle 
> wrote:
>
> > Another friendly reminder that we can't release the binary packages
> for
> > 0.19.x without at least three +1 binding votes.
> >
> > Not releasing a package for 0.19.x will create a problem for anyone
> trying
> > to upgrade to later versions as we recommend upgrading version by
> version.
> >
> >  Any and all feedback regarding these binary packages, binding or
> > otherwise, is welcome so that we may fix any issues that crop up.
> >
> > Thanks,
> >
> > -Renan
> >
> >
> > On Wed, Feb 14, 2018 at 8:43 AM, Renan DelValle 
> wrote:
> >
> > > All,
> > >
> > > Friendly reminder to download, verify, and test so we can conclude
> the
> > > voting!
> > >
> > > Thanks!
> > >
> > > -Renan
> > >
> > > On Sun, Feb 11, 2018 at 1:37 PM, Renan DelValle 
> > wrote:
> > >
> > >> Kicking off the voting with a +1 (binding) from me.
> > >>
> > >> Tested all distributions using the test scripts.
> > >>
> > >> -Renan
> > >>
> > >> On Sun, Feb 11, 2018 at 1:35 PM, Renan DelValle  >
> > wrote:
> > >>
> > >>> All,
> > >>>
> > >>> I propose that we accept the following artifacts as the official
> deb
> > and
> > >>> rpm packaging for
> > >>> Apache Aurora 0.19.x:
> > >>>
> > >>> https://dl.bintray.com/rdelvalle/aurora/
> > >>>
> > >>> The Aurora deb and rpm packaging includes the following:
> > >>>
> > >>> ---
> > >>>
> > >>> The branch used to create the packaging is:
> > >>> https://git1-us-west.apache.org/repos/asf?p=aurora-packaging
> > >>> .git;a=tree;hb=refs/heads/0.19.x
> > >>>
> > >>> The packages are available at:
> > >>> https://dl.bintray.com/rdelvalle/aurora/
> > >>>
> > >>> The GPG keys used to sign the packages are available at:
> > >>> https://dist.apache.org/repos/dist/release/aurora/KEYS
> > >>>
> > >>> Please download, verify, and test. Detailed test instructions are
> > >>> available here:
> > >>> https://git1-us-west.apache.org/repos/asf?p=aurora-packaging
> > >>> .git;a=tree;f=test;hb=refs/heads/0.19.x
> > >>>
> > >>>
> > >>> The vote will close on Wed Feb 14 13:35:18 PST 2018
> > >>>
> > >>> [ ] +1 Release these as the deb and rpm packages for Apache
> Aurora
> > 0.19.x
> > >>> [ ] +0
> > >>> [ ] -1 Do not release these artifacts because...
> > >>>
> > >>> 
> > >>> 
> > >>>
> > >>
> > >>
> > >
> >
>
>
>

Re: [RESULT] [VOTE] Release Apache Aurora 0.19.x packages

[Bill Farner]

We'll need to step back to a new point release.  I should be able to kick
this off next week unless i am beaten to the punch.

On Mon, Jan 15, 2018 at 4:00 PM, Renan DelValle 
wrote:

> Should we try releasing the binaries again now that we tackled this issue?
> There's been a few folks on the Slack channel have been asking when the
> binaries for 0.19 will be released.
>
> -Renan
>
> On Wed, Dec 13, 2017 at 5:23 PM, Bill Farner  wrote:
>
> > I reverse my vote to -1 and am closing the vote as failed.
> >
> > Turns out i had some old debs in my dist/ dir, and the test script picked
> > those up.  After clearing those, i encounter the same issue.
> >
> > Here is the culprit:
> >
> > $ ag -i THERMOS_EXECUTOR_RESOURCES
> > specs/debian/aurora-scheduler.startup.sh
> > 37:  -thermos_executor_resources="$THERMOS_EXECUTOR_RESOURCES" \
> >
> > specs/debian/aurora-scheduler.upstart
> > 34:  -thermos_executor_resources="$THERMOS_EXECUTOR_RESOURCES" \
> >
> > specs/debian/aurora-scheduler.init
> > 75:-thermos_executor_resources="$THERMOS_EXECUTOR_RESOURCES" \
> >
> > specs/debian/aurora-scheduler.default
> > 65:THERMOS_EXECUTOR_RESOURCES=""
> >
> > thermos_executor_resources is passed an empty string.  Here is the option
> > definition:
> >
> > @Parameter(names = "-thermos_executor_resources",
> > > description = "A comma separated list of additional resources to copy
> > > into the sandbox."
> > > + "Note: if thermos_executor_path is not the thermos_executor.pex file
> > > itself, "
> > > + "this must include it.")
> > > public List thermosExecutorResources = ImmutableList.of();
> >
> >
> > We expect this to become an empty list, however the parser emits a list
> of
> > size one, containing an empty string.  I've filed AURORA-1962
> >  for the issue.
> >
> >
> > On Wed, Dec 13, 2017 at 3:31 PM, Renan DelValle <
> renanidelva...@gmail.com>
> > wrote:
> >
> > > I'm running into the same issues as Stephan. I tried with Trusty,
> Xenial,
> > > and Jessie. Same issue with all.
> > >
> > > Somehow a Mesos fetcher entry with a URI value of '' gets injected into
> > the
> > > task protobuf.
> > >
> > > This is the command I ran for Trusty:
> > > ./test/test-artifact.sh test/deb/ubuntu-trusty/
> > > /repo/artifacts/aurora-ubuntu-trusty/dist
> > >
> > > Oddly enough, we have deployed 0.19.0 packages for trusty without any
> > issue
> > > on at least two of our test clusters so it may have to do with our
> > > artifacts tests?
> > >
> > > I tried upgrading the trusty box to Mesos 1.2.2 and the problem
> > persisted.
> > >
> > > -Renan
> > >
> > > On Wed, Dec 13, 2017 at 9:28 AM, Mohit Jaggi 
> > wrote:
> > >
> > > > +1
> > > >
> > > > On Wed, Dec 13, 2017 at 9:03 AM, Bill Farner 
> > wrote:
> > > >
> > > > > We would need at least 2 more binding votes to complete this
> release.
> > > Do
> > > > > folks need more time?
> > > > >
> > > > > On Tue, Dec 12, 2017 at 2:49 PM, thinker0 
> > wrote:
> > > > >
> > > > > > +1, we 0.19.0 small production tested
> > > > > > 2017년 12월 13일 (수) 04:05, Mohit Jaggi 님이
> 작성:
> > > > > >
> > > > > > > +0, we don't use the packages. If you just need someone to test
> > and
> > > > > > verify,
> > > > > > > I can do that. Let me know.
> > > > > > >
> > > > > > > On Tue, Dec 12, 2017 at 9:53 AM, Bill Farner <
> wfar...@apache.org
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Friendly reminder that the vote is due to close tomorrow!
> > > > > > > >
> > > > > > > > Stephan - is the issue you described reproducible?  Did i run
> > the
> > > > > same
> > > > > > > test
> > > > > > > > command(s) as you?
> > > > > > > >
> > > > > > > > On Sun, Dec 10, 2017 at 8:32 PM, Bill Farner <
> > wfar...@apache.org
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > +1 from me, as the test script passes for all artifacts
> > > > > > > > >
> > > > > > > > > I did not have time to run them prior to opening the vote;
> > but
> > > i
> > > > do
> > > > > > not
> > > > > > > > > encounter the failure you did:
> > > > > > > > >
> > > > > > > > > $ ./test/test-artifact.sh test/deb/debian-jessie/
> > > > > > > > > /repo/artifacts/aurora-debian-jessie/dist
> > > > > > > > > 
> > > > > > > > > OK (all tests passed)
> > > > > > > > > Connection to 127.0.0.1 closed.
> > > > > > > > > ==> aurora_jessie: Forcing shutdown of VM...
> > > > > > > > >
> > > > > > > > > the branch is missing
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > That i cannot speak for, unfortunately.
> > > > > > > > >
> > > > > > > > > For those who have yet to try out the builds, here are the
> > test
> > > > > > > commands
> > > > > > > > i
> > > > > > > > > ran.  You can reproduce these by first downloading the
> > > artifacts
> > > > > (in
> > > > > > my
> > > > > > > > > case, they were under artifacts/*)
> > > > > > > > >
> > > > > > 

Re: [RESULT] [VOTE] Release Apache Aurora 0.19.x packages

[Renan DelValle]

Should we try releasing the binaries again now that we tackled this issue?
There's been a few folks on the Slack channel have been asking when the
binaries for 0.19 will be released.

-Renan

On Wed, Dec 13, 2017 at 5:23 PM, Bill Farner  wrote:

> I reverse my vote to -1 and am closing the vote as failed.
>
> Turns out i had some old debs in my dist/ dir, and the test script picked
> those up.  After clearing those, i encounter the same issue.
>
> Here is the culprit:
>
> $ ag -i THERMOS_EXECUTOR_RESOURCES
> specs/debian/aurora-scheduler.startup.sh
> 37:  -thermos_executor_resources="$THERMOS_EXECUTOR_RESOURCES" \
>
> specs/debian/aurora-scheduler.upstart
> 34:  -thermos_executor_resources="$THERMOS_EXECUTOR_RESOURCES" \
>
> specs/debian/aurora-scheduler.init
> 75:-thermos_executor_resources="$THERMOS_EXECUTOR_RESOURCES" \
>
> specs/debian/aurora-scheduler.default
> 65:THERMOS_EXECUTOR_RESOURCES=""
>
> thermos_executor_resources is passed an empty string.  Here is the option
> definition:
>
> @Parameter(names = "-thermos_executor_resources",
> > description = "A comma separated list of additional resources to copy
> > into the sandbox."
> > + "Note: if thermos_executor_path is not the thermos_executor.pex file
> > itself, "
> > + "this must include it.")
> > public List thermosExecutorResources = ImmutableList.of();
>
>
> We expect this to become an empty list, however the parser emits a list of
> size one, containing an empty string.  I've filed AURORA-1962
>  for the issue.
>
>
> On Wed, Dec 13, 2017 at 3:31 PM, Renan DelValle 
> wrote:
>
> > I'm running into the same issues as Stephan. I tried with Trusty, Xenial,
> > and Jessie. Same issue with all.
> >
> > Somehow a Mesos fetcher entry with a URI value of '' gets injected into
> the
> > task protobuf.
> >
> > This is the command I ran for Trusty:
> > ./test/test-artifact.sh test/deb/ubuntu-trusty/
> > /repo/artifacts/aurora-ubuntu-trusty/dist
> >
> > Oddly enough, we have deployed 0.19.0 packages for trusty without any
> issue
> > on at least two of our test clusters so it may have to do with our
> > artifacts tests?
> >
> > I tried upgrading the trusty box to Mesos 1.2.2 and the problem
> persisted.
> >
> > -Renan
> >
> > On Wed, Dec 13, 2017 at 9:28 AM, Mohit Jaggi 
> wrote:
> >
> > > +1
> > >
> > > On Wed, Dec 13, 2017 at 9:03 AM, Bill Farner 
> wrote:
> > >
> > > > We would need at least 2 more binding votes to complete this release.
> > Do
> > > > folks need more time?
> > > >
> > > > On Tue, Dec 12, 2017 at 2:49 PM, thinker0 
> wrote:
> > > >
> > > > > +1, we 0.19.0 small production tested
> > > > > 2017년 12월 13일 (수) 04:05, Mohit Jaggi 님이 작성:
> > > > >
> > > > > > +0, we don't use the packages. If you just need someone to test
> and
> > > > > verify,
> > > > > > I can do that. Let me know.
> > > > > >
> > > > > > On Tue, Dec 12, 2017 at 9:53 AM, Bill Farner  >
> > > > wrote:
> > > > > >
> > > > > > > Friendly reminder that the vote is due to close tomorrow!
> > > > > > >
> > > > > > > Stephan - is the issue you described reproducible?  Did i run
> the
> > > > same
> > > > > > test
> > > > > > > command(s) as you?
> > > > > > >
> > > > > > > On Sun, Dec 10, 2017 at 8:32 PM, Bill Farner <
> wfar...@apache.org
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > +1 from me, as the test script passes for all artifacts
> > > > > > > >
> > > > > > > > I did not have time to run them prior to opening the vote;
> but
> > i
> > > do
> > > > > not
> > > > > > > > encounter the failure you did:
> > > > > > > >
> > > > > > > > $ ./test/test-artifact.sh test/deb/debian-jessie/
> > > > > > > > /repo/artifacts/aurora-debian-jessie/dist
> > > > > > > > 
> > > > > > > > OK (all tests passed)
> > > > > > > > Connection to 127.0.0.1 closed.
> > > > > > > > ==> aurora_jessie: Forcing shutdown of VM...
> > > > > > > >
> > > > > > > > the branch is missing
> > > > > > > >
> > > > > > > >
> > > > > > > > That i cannot speak for, unfortunately.
> > > > > > > >
> > > > > > > > For those who have yet to try out the builds, here are the
> test
> > > > > > commands
> > > > > > > i
> > > > > > > > ran.  You can reproduce these by first downloading the
> > artifacts
> > > > (in
> > > > > my
> > > > > > > > case, they were under artifacts/*)
> > > > > > > >
> > > > > > > > ./test/test-artifact.sh test/deb/debian-jessie/
> > > > > > > > /repo/artifacts/aurora-debian-jessie/dist/
> > > > > > > > ./test/test-artifact.sh test/deb/ubuntu-trusty/
> > > > > > > > /repo/artifacts/aurora-ubuntu-trusty/dist/
> > > > > > > > ./test/test-artifact.sh test/deb/ubuntu-xenial/
> > > > > > > > /repo/artifacts/aurora-ubuntu-xenial/dist/
> > > > > > > > ./test/test-artifact.sh test/rpm/centos-7/
> > > > > > /repo/artifacts/aurora-centos-
> > > > > > > > 

[RESULT] [VOTE] Release Apache Aurora 0.19.x packages

[Bill Farner]

I reverse my vote to -1 and am closing the vote as failed.

Turns out i had some old debs in my dist/ dir, and the test script picked
those up.  After clearing those, i encounter the same issue.

Here is the culprit:

$ ag -i THERMOS_EXECUTOR_RESOURCES
specs/debian/aurora-scheduler.startup.sh
37:  -thermos_executor_resources="$THERMOS_EXECUTOR_RESOURCES" \

specs/debian/aurora-scheduler.upstart
34:  -thermos_executor_resources="$THERMOS_EXECUTOR_RESOURCES" \

specs/debian/aurora-scheduler.init
75:-thermos_executor_resources="$THERMOS_EXECUTOR_RESOURCES" \

specs/debian/aurora-scheduler.default
65:THERMOS_EXECUTOR_RESOURCES=""

thermos_executor_resources is passed an empty string.  Here is the option
definition:

@Parameter(names = "-thermos_executor_resources",
> description = "A comma separated list of additional resources to copy
> into the sandbox."
> + "Note: if thermos_executor_path is not the thermos_executor.pex file
> itself, "
> + "this must include it.")
> public List thermosExecutorResources = ImmutableList.of();


We expect this to become an empty list, however the parser emits a list of
size one, containing an empty string.  I've filed AURORA-1962
 for the issue.


On Wed, Dec 13, 2017 at 3:31 PM, Renan DelValle 
wrote:

> I'm running into the same issues as Stephan. I tried with Trusty, Xenial,
> and Jessie. Same issue with all.
>
> Somehow a Mesos fetcher entry with a URI value of '' gets injected into the
> task protobuf.
>
> This is the command I ran for Trusty:
> ./test/test-artifact.sh test/deb/ubuntu-trusty/
> /repo/artifacts/aurora-ubuntu-trusty/dist
>
> Oddly enough, we have deployed 0.19.0 packages for trusty without any issue
> on at least two of our test clusters so it may have to do with our
> artifacts tests?
>
> I tried upgrading the trusty box to Mesos 1.2.2 and the problem persisted.
>
> -Renan
>
> On Wed, Dec 13, 2017 at 9:28 AM, Mohit Jaggi  wrote:
>
> > +1
> >
> > On Wed, Dec 13, 2017 at 9:03 AM, Bill Farner  wrote:
> >
> > > We would need at least 2 more binding votes to complete this release.
> Do
> > > folks need more time?
> > >
> > > On Tue, Dec 12, 2017 at 2:49 PM, thinker0  wrote:
> > >
> > > > +1, we 0.19.0 small production tested
> > > > 2017년 12월 13일 (수) 04:05, Mohit Jaggi 님이 작성:
> > > >
> > > > > +0, we don't use the packages. If you just need someone to test and
> > > > verify,
> > > > > I can do that. Let me know.
> > > > >
> > > > > On Tue, Dec 12, 2017 at 9:53 AM, Bill Farner 
> > > wrote:
> > > > >
> > > > > > Friendly reminder that the vote is due to close tomorrow!
> > > > > >
> > > > > > Stephan - is the issue you described reproducible?  Did i run the
> > > same
> > > > > test
> > > > > > command(s) as you?
> > > > > >
> > > > > > On Sun, Dec 10, 2017 at 8:32 PM, Bill Farner  >
> > > > wrote:
> > > > > >
> > > > > > > +1 from me, as the test script passes for all artifacts
> > > > > > >
> > > > > > > I did not have time to run them prior to opening the vote; but
> i
> > do
> > > > not
> > > > > > > encounter the failure you did:
> > > > > > >
> > > > > > > $ ./test/test-artifact.sh test/deb/debian-jessie/
> > > > > > > /repo/artifacts/aurora-debian-jessie/dist
> > > > > > > 
> > > > > > > OK (all tests passed)
> > > > > > > Connection to 127.0.0.1 closed.
> > > > > > > ==> aurora_jessie: Forcing shutdown of VM...
> > > > > > >
> > > > > > > the branch is missing
> > > > > > >
> > > > > > >
> > > > > > > That i cannot speak for, unfortunately.
> > > > > > >
> > > > > > > For those who have yet to try out the builds, here are the test
> > > > > commands
> > > > > > i
> > > > > > > ran.  You can reproduce these by first downloading the
> artifacts
> > > (in
> > > > my
> > > > > > > case, they were under artifacts/*)
> > > > > > >
> > > > > > > ./test/test-artifact.sh test/deb/debian-jessie/
> > > > > > > /repo/artifacts/aurora-debian-jessie/dist/
> > > > > > > ./test/test-artifact.sh test/deb/ubuntu-trusty/
> > > > > > > /repo/artifacts/aurora-ubuntu-trusty/dist/
> > > > > > > ./test/test-artifact.sh test/deb/ubuntu-xenial/
> > > > > > > /repo/artifacts/aurora-ubuntu-xenial/dist/
> > > > > > > ./test/test-artifact.sh test/rpm/centos-7/
> > > > > /repo/artifacts/aurora-centos-
> > > > > > > 7/dist/rpmbuild/RPMS/x86_64
> > > > > > >
> > > > > > > Each command took about 5 mins to run in my case.
> > > > > > >
> > > > > > > A belated thanks to Stephan for adding the test script!
> > > > > > >
> > > > > > > commit b904b5f
> > > > > > >> Author: Stephan Erb 
> > > > > > >> Date:   Tue Feb 14 23:33:41 2017 +0100
> > > > > > >> Add basic test scripts for RPM and DEB packages
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Sun, Dec 10, 2017 at 1:06 PM, Stephan Erb 
> > > > wrote:
> > > > > > >
> > > >