that we did early on in the project. Useful then, but not
> any longer. It might have even predated Quick Dev.
>
> FYI - We have an opening for Metron Team Historian. Send a cover letter,
> CV and $150 application fee to me for consideration. :)
>
>
>
>
>
> On F
dated. It now points to full dev and the link just says "Dev
> > Platform"
> >
> > On Fri, Oct 6, 2017 at 8:39 AM, Nick Allen <n...@nickallen.org> wrote:
> >
> > > +1 To killing Quick Dev and updating the Wiki. Quick Dev has been
> broken
> >
Fri, Oct 6, 2017 at 8:39 AM, Nick Allen <n...@nickallen.org> wrote:
>
> > +1 To killing Quick Dev and updating the Wiki. Quick Dev has been broken
> > for eons. Simon's point about "profusion of installs" makes a lot of
> sense
> > too.
> &g
Wiki updated. It now points to full dev and the link just says "Dev
Platform"
On Fri, Oct 6, 2017 at 8:39 AM, Nick Allen <n...@nickallen.org> wrote:
> +1 To killing Quick Dev and updating the Wiki. Quick Dev has been broken
> for eons. Simon's point about "profusi
+1 To killing Quick Dev and updating the Wiki. Quick Dev has been broken
for eons. Simon's point about "profusion of installs" makes a lot of sense
too.
On Fri, Oct 6, 2017 at 8:33 AM Simon Elliston Ball <
si...@simonellistonball.com> wrote:
> +1 we see a lot o
epoint the site. That will give us one less thing to
> upgrade to centos 7 as well.
>
> Jon
>
> On Fri, Oct 6, 2017, 08:27 Justin Leet <justinjl...@gmail.com> wrote:
>
>> So what are we going to do with Quick Dev? I'm pretty sure everybody's
>> been using full dev for
I say we kill it and repoint the site. That will give us one less thing to
upgrade to centos 7 as well.
Jon
On Fri, Oct 6, 2017, 08:27 Justin Leet <justinjl...@gmail.com> wrote:
> So what are we going to do with Quick Dev? I'm pretty sure everybody's
> been using full dev fo
So what are we going to do with Quick Dev? I'm pretty sure everybody's
been using full dev for awhile now (and quick dev is probably broken since
I'm sure we haven't been regularly updating it).
I just realized our website links to a wiki page that says to use quick
dev. Given that quick dev
Github user mattf-horton commented on the issue:
https://github.com/apache/incubator-metron/pull/578
and thanks for the quick check, @dlyle65535 . In process to commit...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
GitHub user mattf-horton opened a pull request:
https://github.com/apache/incubator-metron/pull/578
METRON-946 Full/Quick dev should default network_host to [ _local_, _â¦
## Contributor Comments
@dlyle65535 observed that even single-node installs should have ES bind
t;>
>> On April 21, 2017 at 10:37:39, Nick Allen (n...@nickallen.org) wrote:
>>
>> Not sure if I am doing something stupid, but I cannot deploy "Quick Dev"
>> from master currently. Full details in
>> https://issues.apache.org/jira/browse/METRON-872.
>>
>
>
backwa...@gmail.com>
> wrote:
>
> > If it is docker, then it is just the Dockerfiles.
> > I think you can have vagrant use docker as a back end too right?
> >
> >
> >
> > On April 25, 2017 at 14:34:14, Nick Allen (n...@nickallen.org) wrote:
> >
&g
docker as a back end too right?
>
>
>
> On April 25, 2017 at 14:34:14, Nick Allen (n...@nickallen.org) wrote:
>
> >> I hadn't really reasoned about the notion of a "released" Quick Dev
> image,
> but I can see a lot of value in having a versioned sandbox type
ou can have vagrant use docker as a back end too right?
>
>
>
> On April 25, 2017 at 14:34:14, Nick Allen (n...@nickallen.org) wrote:
>
> >> I hadn't really reasoned about the notion of a "released" Quick Dev
> image,
> but I can see a lot of value in havi
If it is docker, then it is just the Dockerfiles.
I think you can have vagrant use docker as a back end too right?
On April 25, 2017 at 14:34:14, Nick Allen (n...@nickallen.org) wrote:
>> I hadn't really reasoned about the notion of a "released" Quick Dev
image,
but I can se
really reasoned about the notion of a "released" Quick Dev
> image,
> but I can see a lot of value in having a versioned sandbox type image- but
> maybe not quick dev, maybe not even Vagrant? We could actually pre-package
> everything needed and save some provisioning time on
>> I hadn't really reasoned about the notion of a "released" Quick Dev image,
but I can see a lot of value in having a versioned sandbox type image- but
maybe not quick dev, maybe not even Vagrant? We could actually pre-package
everything needed and save some provisioning
Right now, we have the images that get pushed to Atlas for Quick Dev
<https://atlas.hashicorp.com/metron/boxes/quick_dev> versioned
independently from the rest of Metron. We currently have versions 0.1.0
and 0.2.0.
What happens when a user downloads an official release of Metron, like
ay be that we need a new image built to make this
> not an upgrade situation?
>
>
> On April 21, 2017 at 10:37:39, Nick Allen (n...@nickallen.org) wrote:
>
> Not sure if I am doing something stupid, but I cannot deploy "Quick Dev"
> from master currently. Full details
19 matches
Mail list logo
