4:54 p.m.
On 12/10/14, 9:28 AM, Dev Ops wrote:
On Wed, Dec 10, 2014 at 3:37 PM, Brian Stansberry
<brian.stansberry(a)redhat.com <mailto:brian.stansberry@redhat.com>> wrote:
On 12/10/14, 5:14 AM, Dev Ops wrote:
>
>
> On Wed, Dec 10, 2014 at 10:58 AM, Harald Pehl <hpehl(a)redhat.com
<mailto:hpehl@redhat.com>
> <mailto:hpehl@redhat.com <mailto:hpehl@redhat.com>>> wrote:
>
>>
>> Am 09.12.2014 um 12:42 schrieb Dev Ops <devopsmoreorless(a)gmail.com
<mailto:devopsmoreorless@gmail.com>
>> <mailto:devopsmoreorless@gmail.com
<mailto:devopsmoreorless@gmail.com>>>:
>>
>> Hi,
>> thanks for pointing me to the github repo.
>>
>> I need to do a couple of things:
>>
>> 1. provide a graphical and complete view of all server-groups -
>> along with the hosts - something like the following
>>http://bl.ocks.org/mbostock/1062288
> That's something we've always wanted to have in the console.
> Currently the console has some weak points when it comes to manage
> big domains with lots of hosts and servers. Some kind of bird's-eye
> view for big topologies would definitely be an improvement.
>>
>> 2. provide a button to download the deployed application;
> Not sure what's the use case behind that. Maybe you can elaborate
> more on that.
>
>
> Most of the time I "operate" in environments and situation where
there
> is NOT an artifact repository.
> People merely know the existence of words like CI, CD and so on, thus
> before upgrading a web-application they need to back it up.
> Having a button next to the application can be handy.
>
Supporting this would require some server-side functionality, as we
don't expose the content in the content repository via the management
API. It would probably be pretty simple to do though, using the
attach-a-stream-to-a-response thing we've added in 9. Used now by the
log download feature.
Great! Thus implementing a download-content button should be pretty
straightforward.
Are you saying you plan to take on the server-side bit? That would be
great, and I'd be happy to help out.
Dates for WF 9.0.0.Final? More or less... :-)
>
>> Next would be extending point 2. by providing different colors for
>> different metric values.
>> Likely, heap memory metric going to saturation, the balloon would
>> be colored has almost red (#cc0000)... every hosts could have its
>> own metric (heap memory, cpu usage, connection pool statistics,
>> etc...).
>> Alerts and notifications are not needed, as there are already
>> other software accomplishing these tasks (nagios, jon, etc...).
>>
>> Regards,
>> DevOps guy
>
> Any contributions which address these enhancements are highly
> welcome! The management console is implemented in GWT. There's some
> documentation about the internals and how to get started at [1]. You
> can ping me anytime on #wildfly-management if you need more details
> or to discuss the next steps.
>
> [1]http://hal.github.io/
>
> .: Harald
>
>>
>>
>> On Tue, Dec 9, 2014 at 11:13 AM, Harald Pehl <hpehl(a)redhat.com
<mailto:hpehl@redhat.com>
>> <mailto:hpehl@redhat.com <mailto:hpehl@redhat.com>>>
wrote:
>>
>> The source code for the management console lives in its own
>> repository athttps://github.com/hal/core
>>
>> I'm curious, what kind of customization do you have in mind?
>>
>> .: Harald
>>
>>> Am 09.12.2014 um 11:06 schrieb Dev Ops
>>> <devopsmoreorless(a)gmail.com
<mailto:devopsmoreorless@gmail.com>
<mailto:devopsmoreorless@gmail.com
<mailto:devopsmoreorless@gmail.com>>>:
>>>
>>> Hi all,
>>> where do I find the source of the web application which
>>> provides the Management console?
>>>
>>> I need to add something to it, but I don't know where to
get
>>> the source.
>>>
>>>
>>> TIA,
>>> DevOps guy
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev(a)lists.jboss.org
<mailto:wildfly-dev@lists.jboss.org>
<mailto:wildfly-dev@lists.jboss.org
<mailto:wildfly-dev@lists.jboss.org>>
>>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> ---
>> Harald Pehl
>> JBoss by Red Hat
>> http://hpehl.info <http://hpehl.info/>
>>
>>
>
> ---
> Harald Pehl
> JBoss by Red Hat
>http://hpehl.info
>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
>wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat