that's certainly a good idea, but we need to deliver documentation of the bare metal
steps first.
we can provide arbitrary layers of convenience _after_ we've explained how to build,
install and configure the core components.
no auto-magic, no shortcuts, no additional layers of complexity that hide what's going
on underneath.
On 06 Nov 2014, at 11:47, Harald Pehl <hpehl(a)redhat.com> wrote:
What about providing a couple of Docker images to quickly setup
something devs can play around with? This way we could demo different solutions:
- WildFly Monitor + Cassandra + RHQ Metrics
- WildFly Monitor + InfluxDB + Grafana
I can try to put something together and push it to
https://hub.docker.com/
.: Harald
> Am 06.11.2014 um 11:33 schrieb Heiko W.Rupp <hrupp(a)redhat.com>:
>
>
>> Am 06.11.2014 um 10:42 schrieb Heiko Braun <hbraun(a)redhat.com>:
>>
>>
>> Currently the docs are a little misleading, as it says you should install the
monitor susbystem as described in the README but then points to the quickstart scripts
('start.sh') that download and install a dedicated WF instance.
>>
>> I think it would be better to focus on the steps needed to install all components
on an existing server.
>
> We should perhaps write a start_big.sh that also installs your Cassandra subsystem,
the wildfly monitor
> and then rhq-metrics(.war)
>
> Anyone with shell-fu around? :)
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
---
Harald Pehl
JBoss by Red Hat
http://hpehl.info