Re: Kerberos changes affected quick-dev and full-dev

2017-04-04 Thread Michael Miklavcic 
Awesome, thanks David!

On Tue, Apr 4, 2017 at 7:16 AM, Casey Stella  wrote:

> Thanks David!
>
> On Mon, Apr 3, 2017 at 8:43 PM, David Lyle  wrote:
>
> > I've pushed a new Vagrant image for Quick Dev. You should be asked to
> > update the box the next time you 'vagrant up' Quick Dev.
> >
> > -D...
> >
> >
> > On Mon, Apr 3, 2017 at 2:33 PM, Casey Stella  wrote:
> >
> > > Thanks Justin,  the packer build is started, but this is going to take
> > some
> > > time.  Please use full-dev to validate your PRs in the meantime.  I
> will
> > > update this thread once it's uploaded.
> > >
> > > On Mon, Apr 3, 2017 at 2:13 PM, Justin Leet 
> > wrote:
> > >
> > > > The PR to fix full-dev is in master now.  We still need a new packer
> > > build
> > > > before we have quick-dev available again.
> > > >
> > > > Justin
> > > >
> > > > On Mon, Apr 3, 2017 at 10:53 AM, Justin Leet 
> > > > wrote:
> > > >
> > > > > Btw, here is a workaround for full-dev. In Ambari, add the line
> > > > "topology.worker.childopts="
> > > > > (no argument) to the elasticsearch.properties template, then
> restart
> > > > > indexing through Ambari to propogate the change out.
> > > > >
> > > > > For example, make the Storm section look like:
> > > > >
> > > > > # Storm #
> > > > > indexing.workers=1
> > > > > indexing.executors=0
> > > > > topology.worker.childopts=
> > > > >
> > > > > Justin
> > > > >
> > > > > On Mon, Apr 3, 2017 at 10:46 AM, Casey Stella 
> > > > wrote:
> > > > >
> > > > >> Hey guys,
> > > > >>
> > > > >> Just a quick heads up, the kerberos related changes (797 and 793)
> > that
> > > > >> went
> > > > >> in last week had mpack changes.  This means that a new packer
> build
> > > > needs
> > > > >> to be updated for quickdev to work.  Unfortunately, that didn't
> > happen
> > > > >> *and* there's a follow-on bug (METRON-818) that also involves
> mpack
> > > > >> changes
> > > > >> (https://github.com/apache/incubator-metron/pull/506).
> > > > >>
> > > > >> Also, this change fixes a bug introduced in 797 with full-dev, so
> > it's
> > > > >> getting high priority attention just right now.  I just wanted to
> > send
> > > > an
> > > > >> update and make sure everyone was aware of what's going on if you
> > try
> > > > >> full-dev or quick-dev and it fails for you.  I expect 818 to get
> in
> > > > >> quickly
> > > > >> (already has 2 +1s, so pretty much as soon as travis returns we'll
> > > > >> commit),
> > > > >> which should fix full-dev.
> > > > >>
> > > > >> Casey
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: Kerberos changes affected quick-dev and full-dev

2017-04-04 Thread Casey Stella 
Thanks David!

On Mon, Apr 3, 2017 at 8:43 PM, David Lyle  wrote:

> I've pushed a new Vagrant image for Quick Dev. You should be asked to
> update the box the next time you 'vagrant up' Quick Dev.
>
> -D...
>
>
> On Mon, Apr 3, 2017 at 2:33 PM, Casey Stella  wrote:
>
> > Thanks Justin,  the packer build is started, but this is going to take
> some
> > time.  Please use full-dev to validate your PRs in the meantime.  I will
> > update this thread once it's uploaded.
> >
> > On Mon, Apr 3, 2017 at 2:13 PM, Justin Leet 
> wrote:
> >
> > > The PR to fix full-dev is in master now.  We still need a new packer
> > build
> > > before we have quick-dev available again.
> > >
> > > Justin
> > >
> > > On Mon, Apr 3, 2017 at 10:53 AM, Justin Leet 
> > > wrote:
> > >
> > > > Btw, here is a workaround for full-dev. In Ambari, add the line
> > > "topology.worker.childopts="
> > > > (no argument) to the elasticsearch.properties template, then restart
> > > > indexing through Ambari to propogate the change out.
> > > >
> > > > For example, make the Storm section look like:
> > > >
> > > > # Storm #
> > > > indexing.workers=1
> > > > indexing.executors=0
> > > > topology.worker.childopts=
> > > >
> > > > Justin
> > > >
> > > > On Mon, Apr 3, 2017 at 10:46 AM, Casey Stella 
> > > wrote:
> > > >
> > > >> Hey guys,
> > > >>
> > > >> Just a quick heads up, the kerberos related changes (797 and 793)
> that
> > > >> went
> > > >> in last week had mpack changes.  This means that a new packer build
> > > needs
> > > >> to be updated for quickdev to work.  Unfortunately, that didn't
> happen
> > > >> *and* there's a follow-on bug (METRON-818) that also involves mpack
> > > >> changes
> > > >> (https://github.com/apache/incubator-metron/pull/506).
> > > >>
> > > >> Also, this change fixes a bug introduced in 797 with full-dev, so
> it's
> > > >> getting high priority attention just right now.  I just wanted to
> send
> > > an
> > > >> update and make sure everyone was aware of what's going on if you
> try
> > > >> full-dev or quick-dev and it fails for you.  I expect 818 to get in
> > > >> quickly
> > > >> (already has 2 +1s, so pretty much as soon as travis returns we'll
> > > >> commit),
> > > >> which should fix full-dev.
> > > >>
> > > >> Casey
> > > >>
> > > >
> > > >
> > >
> >
>

Re: Kerberos changes affected quick-dev and full-dev

2017-04-03 Thread David Lyle 
I've pushed a new Vagrant image for Quick Dev. You should be asked to
update the box the next time you 'vagrant up' Quick Dev.

-D...


On Mon, Apr 3, 2017 at 2:33 PM, Casey Stella  wrote:

> Thanks Justin,  the packer build is started, but this is going to take some
> time.  Please use full-dev to validate your PRs in the meantime.  I will
> update this thread once it's uploaded.
>
> On Mon, Apr 3, 2017 at 2:13 PM, Justin Leet  wrote:
>
> > The PR to fix full-dev is in master now.  We still need a new packer
> build
> > before we have quick-dev available again.
> >
> > Justin
> >
> > On Mon, Apr 3, 2017 at 10:53 AM, Justin Leet 
> > wrote:
> >
> > > Btw, here is a workaround for full-dev. In Ambari, add the line
> > "topology.worker.childopts="
> > > (no argument) to the elasticsearch.properties template, then restart
> > > indexing through Ambari to propogate the change out.
> > >
> > > For example, make the Storm section look like:
> > >
> > > # Storm #
> > > indexing.workers=1
> > > indexing.executors=0
> > > topology.worker.childopts=
> > >
> > > Justin
> > >
> > > On Mon, Apr 3, 2017 at 10:46 AM, Casey Stella 
> > wrote:
> > >
> > >> Hey guys,
> > >>
> > >> Just a quick heads up, the kerberos related changes (797 and 793) that
> > >> went
> > >> in last week had mpack changes.  This means that a new packer build
> > needs
> > >> to be updated for quickdev to work.  Unfortunately, that didn't happen
> > >> *and* there's a follow-on bug (METRON-818) that also involves mpack
> > >> changes
> > >> (https://github.com/apache/incubator-metron/pull/506).
> > >>
> > >> Also, this change fixes a bug introduced in 797 with full-dev, so it's
> > >> getting high priority attention just right now.  I just wanted to send
> > an
> > >> update and make sure everyone was aware of what's going on if you try
> > >> full-dev or quick-dev and it fails for you.  I expect 818 to get in
> > >> quickly
> > >> (already has 2 +1s, so pretty much as soon as travis returns we'll
> > >> commit),
> > >> which should fix full-dev.
> > >>
> > >> Casey
> > >>
> > >
> > >
> >
>

Re: Kerberos changes affected quick-dev and full-dev

2017-04-03 Thread Casey Stella 
Thanks Justin,  the packer build is started, but this is going to take some
time.  Please use full-dev to validate your PRs in the meantime.  I will
update this thread once it's uploaded.

On Mon, Apr 3, 2017 at 2:13 PM, Justin Leet  wrote:

> The PR to fix full-dev is in master now.  We still need a new packer build
> before we have quick-dev available again.
>
> Justin
>
> On Mon, Apr 3, 2017 at 10:53 AM, Justin Leet 
> wrote:
>
> > Btw, here is a workaround for full-dev. In Ambari, add the line
> "topology.worker.childopts="
> > (no argument) to the elasticsearch.properties template, then restart
> > indexing through Ambari to propogate the change out.
> >
> > For example, make the Storm section look like:
> >
> > # Storm #
> > indexing.workers=1
> > indexing.executors=0
> > topology.worker.childopts=
> >
> > Justin
> >
> > On Mon, Apr 3, 2017 at 10:46 AM, Casey Stella 
> wrote:
> >
> >> Hey guys,
> >>
> >> Just a quick heads up, the kerberos related changes (797 and 793) that
> >> went
> >> in last week had mpack changes.  This means that a new packer build
> needs
> >> to be updated for quickdev to work.  Unfortunately, that didn't happen
> >> *and* there's a follow-on bug (METRON-818) that also involves mpack
> >> changes
> >> (https://github.com/apache/incubator-metron/pull/506).
> >>
> >> Also, this change fixes a bug introduced in 797 with full-dev, so it's
> >> getting high priority attention just right now.  I just wanted to send
> an
> >> update and make sure everyone was aware of what's going on if you try
> >> full-dev or quick-dev and it fails for you.  I expect 818 to get in
> >> quickly
> >> (already has 2 +1s, so pretty much as soon as travis returns we'll
> >> commit),
> >> which should fix full-dev.
> >>
> >> Casey
> >>
> >
> >
>

Re: Kerberos changes affected quick-dev and full-dev

2017-04-03 Thread Justin Leet 
The PR to fix full-dev is in master now.  We still need a new packer build
before we have quick-dev available again.

Justin

On Mon, Apr 3, 2017 at 10:53 AM, Justin Leet  wrote:

> Btw, here is a workaround for full-dev. In Ambari, add the line 
> "topology.worker.childopts="
> (no argument) to the elasticsearch.properties template, then restart
> indexing through Ambari to propogate the change out.
>
> For example, make the Storm section look like:
>
> # Storm #
> indexing.workers=1
> indexing.executors=0
> topology.worker.childopts=
>
> Justin
>
> On Mon, Apr 3, 2017 at 10:46 AM, Casey Stella  wrote:
>
>> Hey guys,
>>
>> Just a quick heads up, the kerberos related changes (797 and 793) that
>> went
>> in last week had mpack changes.  This means that a new packer build needs
>> to be updated for quickdev to work.  Unfortunately, that didn't happen
>> *and* there's a follow-on bug (METRON-818) that also involves mpack
>> changes
>> (https://github.com/apache/incubator-metron/pull/506).
>>
>> Also, this change fixes a bug introduced in 797 with full-dev, so it's
>> getting high priority attention just right now.  I just wanted to send an
>> update and make sure everyone was aware of what's going on if you try
>> full-dev or quick-dev and it fails for you.  I expect 818 to get in
>> quickly
>> (already has 2 +1s, so pretty much as soon as travis returns we'll
>> commit),
>> which should fix full-dev.
>>
>> Casey
>>
>
>

Re: Kerberos changes affected quick-dev and full-dev

2017-04-03 Thread Justin Leet 
Btw, here is a workaround for full-dev. In Ambari, add the line
"topology.worker.childopts="
(no argument) to the elasticsearch.properties template, then restart
indexing through Ambari to propogate the change out.

For example, make the Storm section look like:

# Storm #
indexing.workers=1
indexing.executors=0
topology.worker.childopts=

Justin

On Mon, Apr 3, 2017 at 10:46 AM, Casey Stella  wrote:

> Hey guys,
>
> Just a quick heads up, the kerberos related changes (797 and 793) that went
> in last week had mpack changes.  This means that a new packer build needs
> to be updated for quickdev to work.  Unfortunately, that didn't happen
> *and* there's a follow-on bug (METRON-818) that also involves mpack changes
> (https://github.com/apache/incubator-metron/pull/506).
>
> Also, this change fixes a bug introduced in 797 with full-dev, so it's
> getting high priority attention just right now.  I just wanted to send an
> update and make sure everyone was aware of what's going on if you try
> full-dev or quick-dev and it fails for you.  I expect 818 to get in quickly
> (already has 2 +1s, so pretty much as soon as travis returns we'll commit),
> which should fix full-dev.
>
> Casey
>