You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2010/05/20 19:19:07 UTC
[DISCUSS] ServiceMix administrator tools
Hi all,
I would like to discuss around SM-1813.
In this task, I propose to add a set of new Ant tasks. The purpose is to
provide tool for ServiceMix administrators such as:
- list endpoints (name, descriptor)
- enable JDBC auditor
- reload log configuration
- etc ...
using the command line.
Of course, most of these tasks can be achieved using JConsole (or other
JMX clients).
However, in production, most of the time, the administrator:
- doesn't have graphical environment (Unix Xorg)
- would like to script some actions (to deploy, etc)
- would like to script some monitoring (plug list endpoint/service unit
in Nagios for example to check if all is deployed)
- etc
As we already provide Ant tasks (some defined in the JBI specification),
I think that the most logical is to provide new ServiceMix specific ant
tasks for both SMX3 and NMR.
Another way is to provide a shell like servicemix-shell (mostly for SMX3).
What do you think ?
Thanks
Regards
JB
Re: [DISCUSS] ServiceMix administrator tools
Posted by Chris Custine <ch...@gmail.com>.
You can currently script the commands via ssh (ssh smx@localhost -p 8101
osgi:list) for the SMX4 console. We already have the plumbing for a generic
admin client, we just need to package it up as a more lightweight and
standalone app. If you look at admin:connect, that is the general direction
I am thinking about. All we really need to do is create an assembly with
minimal dependencies and a more script and user friendly shell command that
wraps the ssh or admin:connect parts for SMX4, and add the remote SMX3 bits.
We could easily detect the server version that you are connecting to and
start only relevant command bundles.
I had thought about this a few weeks ago, and I definitely think this can be
done. If we get the requirements out in the open here, I think we can make
everyone happy. Just my 2 cents.
Chris
--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org
On Thu, May 27, 2010 at 8:42 AM, Charles Moulliard <cm...@gmail.com>wrote:
> Hi Chris,
>
> The idea to propose/use a CLI is excellent and similar to command
> lines already existing with ActiveMq and available through
> activemq-admin.bat. But that means that the CLI should be available
> inside Karaf and not externally using a shell/dos script. In this
> case, it will not be possible for users wanting to use Nagios,
> OpenARM, ... monitoring engines to use such command lines.
>
> For Hyperic, Fuse HQ, we can use JMX as they have a plugin.
>
> Kind regards,
>
> Charles Moulliard
>
> Senior Enterprise Architect (J2EE, .NET, SOA)
> Apache Camel/ServiceMix Committer
>
> *******************************************************************
> - Blog : http://cmoulliard.blogspot.com
> - Twitter : http://twitter.com/cmoulliard
> - Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
>
>
> On Thu, May 27, 2010 at 4:20 PM, Chris Custine <ch...@gmail.com>
> wrote:
> > I haven't thought about this very much, but what about creating a
> specific
> > admin CLI project based on Karaf? Obviously with SMX4 you can do all of
> > this by scripting remote SSH commands with the built in Karaf/SSHD stuff,
> > but you could use the overlapping command names (Listing JBI endpoints,
> etc)
> > that exist for SMX4 and re-implement them for SMX3 so that there is a
> > migration path for SMX3->SMX4. In addition, this one instance of the CLI
> > could run as a daemon and you could script admin functions for multiple
> SMX3
> > instances via this one admin instance using the built in SSHD in Karaf.
> >
> > Not sure if it is all practical, but I wanted to throw these ideas out
> there
> > too.
> >
> > Chris
> > --
> > Chris Custine
> > FUSESource :: http://fusesource.com
> > My Blog :: http://blog.organicelement.com
> > Apache ServiceMix :: http://servicemix.apache.org
> > Apache Felix :: http://felix.apache.org
> > Apache Directory Server :: http://directory.apache.org
> >
> >
> > On Thu, May 20, 2010 at 11:19 AM, Jean-Baptiste Onofré <jb@nanthrax.net
> >wrote:
> >
> >> Hi all,
> >>
> >> I would like to discuss around SM-1813.
> >>
> >> In this task, I propose to add a set of new Ant tasks. The purpose is to
> >> provide tool for ServiceMix administrators such as:
> >> - list endpoints (name, descriptor)
> >> - enable JDBC auditor
> >> - reload log configuration
> >> - etc ...
> >> using the command line.
> >>
> >> Of course, most of these tasks can be achieved using JConsole (or other
> JMX
> >> clients).
> >> However, in production, most of the time, the administrator:
> >> - doesn't have graphical environment (Unix Xorg)
> >> - would like to script some actions (to deploy, etc)
> >> - would like to script some monitoring (plug list endpoint/service unit
> in
> >> Nagios for example to check if all is deployed)
> >> - etc
> >>
> >> As we already provide Ant tasks (some defined in the JBI specification),
> I
> >> think that the most logical is to provide new ServiceMix specific ant
> tasks
> >> for both SMX3 and NMR.
> >>
> >> Another way is to provide a shell like servicemix-shell (mostly for
> SMX3).
> >>
> >> What do you think ?
> >>
> >> Thanks
> >> Regards
> >> JB
> >>
> >
>
Re: [DISCUSS] ServiceMix administrator tools
Posted by James Strachan <ja...@gmail.com>.
On 27 May 2010 17:16, Chris Custine <ch...@gmail.com> wrote:
> We already have intelligent tab completion for some command sets such as
> features, config, and possibly a few others. It could be easily added for
> any other command set as well. If you are talking about doing that from a
> bash shell,
am cool with booting up the shell from bash, then the completion
happens inside the karaf shell...
> that could be done for commands themselves (export a completion
> script to a file based on installed commands), but variable names, etc might
> be a bit tough because we would basically have to boot the shell and get the
> possible completions on every tab. But hey, I'm sure we can come up with
> something! :-)
We should be able to complete on things like endpoint names, arguments
or whatever inside the karaf shell right?
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
Re: [DISCUSS] ServiceMix administrator tools
Posted by Chris Custine <ch...@gmail.com>.
We already have intelligent tab completion for some command sets such as
features, config, and possibly a few others. It could be easily added for
any other command set as well. If you are talking about doing that from a
bash shell, that could be done for commands themselves (export a completion
script to a file based on installed commands), but variable names, etc might
be a bit tough because we would basically have to boot the shell and get the
possible completions on every tab. But hey, I'm sure we can come up with
something! :-)
Chris
--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org
On Thu, May 27, 2010 at 9:00 AM, James Strachan <ja...@gmail.com>wrote:
> I'm liking the idea of a universal set of modular consoles/command
> line shells which can be deployed together in karaf. I also like the
> idea of the shell being available on the command line too. This
> shouldn't be too hard though right? i.e. a command line script which
> boots up karaf with one (or more) of the shells inside.
>
> Extra points awarded for tab completion inside commands (e.g. smart
> completing individual commands and arguments such as endpoint names
> etc)
>
> On 27 May 2010 15:42, Charles Moulliard <cm...@gmail.com> wrote:
> > Hi Chris,
> >
> > The idea to propose/use a CLI is excellent and similar to command
> > lines already existing with ActiveMq and available through
> > activemq-admin.bat. But that means that the CLI should be available
> > inside Karaf and not externally using a shell/dos script. In this
> > case, it will not be possible for users wanting to use Nagios,
> > OpenARM, ... monitoring engines to use such command lines.
> >
> > For Hyperic, Fuse HQ, we can use JMX as they have a plugin.
> >
> > Kind regards,
> >
> > Charles Moulliard
> >
> > Senior Enterprise Architect (J2EE, .NET, SOA)
> > Apache Camel/ServiceMix Committer
> >
> > *******************************************************************
> > - Blog : http://cmoulliard.blogspot.com
> > - Twitter : http://twitter.com/cmoulliard
> > - Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> >
> >
> >
> > On Thu, May 27, 2010 at 4:20 PM, Chris Custine <ch...@gmail.com>
> wrote:
> >> I haven't thought about this very much, but what about creating a
> specific
> >> admin CLI project based on Karaf? Obviously with SMX4 you can do all of
> >> this by scripting remote SSH commands with the built in Karaf/SSHD
> stuff,
> >> but you could use the overlapping command names (Listing JBI endpoints,
> etc)
> >> that exist for SMX4 and re-implement them for SMX3 so that there is a
> >> migration path for SMX3->SMX4. In addition, this one instance of the
> CLI
> >> could run as a daemon and you could script admin functions for multiple
> SMX3
> >> instances via this one admin instance using the built in SSHD in Karaf.
> >>
> >> Not sure if it is all practical, but I wanted to throw these ideas out
> there
> >> too.
> >>
> >> Chris
> >> --
> >> Chris Custine
> >> FUSESource :: http://fusesource.com
> >> My Blog :: http://blog.organicelement.com
> >> Apache ServiceMix :: http://servicemix.apache.org
> >> Apache Felix :: http://felix.apache.org
> >> Apache Directory Server :: http://directory.apache.org
> >>
> >>
> >> On Thu, May 20, 2010 at 11:19 AM, Jean-Baptiste Onofré <jb@nanthrax.net
> >wrote:
> >>
> >>> Hi all,
> >>>
> >>> I would like to discuss around SM-1813.
> >>>
> >>> In this task, I propose to add a set of new Ant tasks. The purpose is
> to
> >>> provide tool for ServiceMix administrators such as:
> >>> - list endpoints (name, descriptor)
> >>> - enable JDBC auditor
> >>> - reload log configuration
> >>> - etc ...
> >>> using the command line.
> >>>
> >>> Of course, most of these tasks can be achieved using JConsole (or other
> JMX
> >>> clients).
> >>> However, in production, most of the time, the administrator:
> >>> - doesn't have graphical environment (Unix Xorg)
> >>> - would like to script some actions (to deploy, etc)
> >>> - would like to script some monitoring (plug list endpoint/service unit
> in
> >>> Nagios for example to check if all is deployed)
> >>> - etc
> >>>
> >>> As we already provide Ant tasks (some defined in the JBI
> specification), I
> >>> think that the most logical is to provide new ServiceMix specific ant
> tasks
> >>> for both SMX3 and NMR.
> >>>
> >>> Another way is to provide a shell like servicemix-shell (mostly for
> SMX3).
> >>>
> >>> What do you think ?
> >>>
> >>> Thanks
> >>> Regards
> >>> JB
> >>>
> >>
> >
>
>
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>
Re: [DISCUSS] ServiceMix administrator tools
Posted by James Strachan <ja...@gmail.com>.
I'm liking the idea of a universal set of modular consoles/command
line shells which can be deployed together in karaf. I also like the
idea of the shell being available on the command line too. This
shouldn't be too hard though right? i.e. a command line script which
boots up karaf with one (or more) of the shells inside.
Extra points awarded for tab completion inside commands (e.g. smart
completing individual commands and arguments such as endpoint names
etc)
On 27 May 2010 15:42, Charles Moulliard <cm...@gmail.com> wrote:
> Hi Chris,
>
> The idea to propose/use a CLI is excellent and similar to command
> lines already existing with ActiveMq and available through
> activemq-admin.bat. But that means that the CLI should be available
> inside Karaf and not externally using a shell/dos script. In this
> case, it will not be possible for users wanting to use Nagios,
> OpenARM, ... monitoring engines to use such command lines.
>
> For Hyperic, Fuse HQ, we can use JMX as they have a plugin.
>
> Kind regards,
>
> Charles Moulliard
>
> Senior Enterprise Architect (J2EE, .NET, SOA)
> Apache Camel/ServiceMix Committer
>
> *******************************************************************
> - Blog : http://cmoulliard.blogspot.com
> - Twitter : http://twitter.com/cmoulliard
> - Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
>
>
> On Thu, May 27, 2010 at 4:20 PM, Chris Custine <ch...@gmail.com> wrote:
>> I haven't thought about this very much, but what about creating a specific
>> admin CLI project based on Karaf? Obviously with SMX4 you can do all of
>> this by scripting remote SSH commands with the built in Karaf/SSHD stuff,
>> but you could use the overlapping command names (Listing JBI endpoints, etc)
>> that exist for SMX4 and re-implement them for SMX3 so that there is a
>> migration path for SMX3->SMX4. In addition, this one instance of the CLI
>> could run as a daemon and you could script admin functions for multiple SMX3
>> instances via this one admin instance using the built in SSHD in Karaf.
>>
>> Not sure if it is all practical, but I wanted to throw these ideas out there
>> too.
>>
>> Chris
>> --
>> Chris Custine
>> FUSESource :: http://fusesource.com
>> My Blog :: http://blog.organicelement.com
>> Apache ServiceMix :: http://servicemix.apache.org
>> Apache Felix :: http://felix.apache.org
>> Apache Directory Server :: http://directory.apache.org
>>
>>
>> On Thu, May 20, 2010 at 11:19 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
>>
>>> Hi all,
>>>
>>> I would like to discuss around SM-1813.
>>>
>>> In this task, I propose to add a set of new Ant tasks. The purpose is to
>>> provide tool for ServiceMix administrators such as:
>>> - list endpoints (name, descriptor)
>>> - enable JDBC auditor
>>> - reload log configuration
>>> - etc ...
>>> using the command line.
>>>
>>> Of course, most of these tasks can be achieved using JConsole (or other JMX
>>> clients).
>>> However, in production, most of the time, the administrator:
>>> - doesn't have graphical environment (Unix Xorg)
>>> - would like to script some actions (to deploy, etc)
>>> - would like to script some monitoring (plug list endpoint/service unit in
>>> Nagios for example to check if all is deployed)
>>> - etc
>>>
>>> As we already provide Ant tasks (some defined in the JBI specification), I
>>> think that the most logical is to provide new ServiceMix specific ant tasks
>>> for both SMX3 and NMR.
>>>
>>> Another way is to provide a shell like servicemix-shell (mostly for SMX3).
>>>
>>> What do you think ?
>>>
>>> Thanks
>>> Regards
>>> JB
>>>
>>
>
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
Re: [DISCUSS] ServiceMix administrator tools
Posted by Charles Moulliard <cm...@gmail.com>.
Hi Chris,
The idea to propose/use a CLI is excellent and similar to command
lines already existing with ActiveMq and available through
activemq-admin.bat. But that means that the CLI should be available
inside Karaf and not externally using a shell/dos script. In this
case, it will not be possible for users wanting to use Nagios,
OpenARM, ... monitoring engines to use such command lines.
For Hyperic, Fuse HQ, we can use JMX as they have a plugin.
Kind regards,
Charles Moulliard
Senior Enterprise Architect (J2EE, .NET, SOA)
Apache Camel/ServiceMix Committer
*******************************************************************
- Blog : http://cmoulliard.blogspot.com
- Twitter : http://twitter.com/cmoulliard
- Linkedlin : http://www.linkedin.com/in/charlesmoulliard
On Thu, May 27, 2010 at 4:20 PM, Chris Custine <ch...@gmail.com> wrote:
> I haven't thought about this very much, but what about creating a specific
> admin CLI project based on Karaf? Obviously with SMX4 you can do all of
> this by scripting remote SSH commands with the built in Karaf/SSHD stuff,
> but you could use the overlapping command names (Listing JBI endpoints, etc)
> that exist for SMX4 and re-implement them for SMX3 so that there is a
> migration path for SMX3->SMX4. In addition, this one instance of the CLI
> could run as a daemon and you could script admin functions for multiple SMX3
> instances via this one admin instance using the built in SSHD in Karaf.
>
> Not sure if it is all practical, but I wanted to throw these ideas out there
> too.
>
> Chris
> --
> Chris Custine
> FUSESource :: http://fusesource.com
> My Blog :: http://blog.organicelement.com
> Apache ServiceMix :: http://servicemix.apache.org
> Apache Felix :: http://felix.apache.org
> Apache Directory Server :: http://directory.apache.org
>
>
> On Thu, May 20, 2010 at 11:19 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
>
>> Hi all,
>>
>> I would like to discuss around SM-1813.
>>
>> In this task, I propose to add a set of new Ant tasks. The purpose is to
>> provide tool for ServiceMix administrators such as:
>> - list endpoints (name, descriptor)
>> - enable JDBC auditor
>> - reload log configuration
>> - etc ...
>> using the command line.
>>
>> Of course, most of these tasks can be achieved using JConsole (or other JMX
>> clients).
>> However, in production, most of the time, the administrator:
>> - doesn't have graphical environment (Unix Xorg)
>> - would like to script some actions (to deploy, etc)
>> - would like to script some monitoring (plug list endpoint/service unit in
>> Nagios for example to check if all is deployed)
>> - etc
>>
>> As we already provide Ant tasks (some defined in the JBI specification), I
>> think that the most logical is to provide new ServiceMix specific ant tasks
>> for both SMX3 and NMR.
>>
>> Another way is to provide a shell like servicemix-shell (mostly for SMX3).
>>
>> What do you think ?
>>
>> Thanks
>> Regards
>> JB
>>
>
Re: [DISCUSS] ServiceMix administrator tools
Posted by Chris Custine <ch...@gmail.com>.
I haven't thought about this very much, but what about creating a specific
admin CLI project based on Karaf? Obviously with SMX4 you can do all of
this by scripting remote SSH commands with the built in Karaf/SSHD stuff,
but you could use the overlapping command names (Listing JBI endpoints, etc)
that exist for SMX4 and re-implement them for SMX3 so that there is a
migration path for SMX3->SMX4. In addition, this one instance of the CLI
could run as a daemon and you could script admin functions for multiple SMX3
instances via this one admin instance using the built in SSHD in Karaf.
Not sure if it is all practical, but I wanted to throw these ideas out there
too.
Chris
--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org
On Thu, May 20, 2010 at 11:19 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Hi all,
>
> I would like to discuss around SM-1813.
>
> In this task, I propose to add a set of new Ant tasks. The purpose is to
> provide tool for ServiceMix administrators such as:
> - list endpoints (name, descriptor)
> - enable JDBC auditor
> - reload log configuration
> - etc ...
> using the command line.
>
> Of course, most of these tasks can be achieved using JConsole (or other JMX
> clients).
> However, in production, most of the time, the administrator:
> - doesn't have graphical environment (Unix Xorg)
> - would like to script some actions (to deploy, etc)
> - would like to script some monitoring (plug list endpoint/service unit in
> Nagios for example to check if all is deployed)
> - etc
>
> As we already provide Ant tasks (some defined in the JBI specification), I
> think that the most logical is to provide new ServiceMix specific ant tasks
> for both SMX3 and NMR.
>
> Another way is to provide a shell like servicemix-shell (mostly for SMX3).
>
> What do you think ?
>
> Thanks
> Regards
> JB
>
Re: [DISCUSS] ServiceMix administrator tools
Posted by Charles Moulliard <cm...@gmail.com>.
Hi JB, All,
Administration is from my point of view the next "chantier" that we
must tackle for SMX3/SMX4. Why, JMX is a great tool but oriented
developer and administrators are reluctant to use it. They prefer to
use Nagios (MRTG, ...) with shell scripts to monitor
servers/services/instances ....
So, it is important that we have a discussion about what we can
propose for administrators to allow SMX/ActiveMq and Camel
monitoring/administration/alerting.
Kind regards,
Charles Moulliard
Senior Enterprise Architect (J2EE, .NET, SOA)
Apache Camel/ServiceMix Committer
*******************************************************************
- Blog : http://cmoulliard.blogspot.com
- Twitter : http://twitter.com/cmoulliard
- Linkedlin : http://www.linkedin.com/in/charlesmoulliard
On Thu, May 20, 2010 at 7:19 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi all,
>
> I would like to discuss around SM-1813.
>
> In this task, I propose to add a set of new Ant tasks. The purpose is to
> provide tool for ServiceMix administrators such as:
> - list endpoints (name, descriptor)
> - enable JDBC auditor
> - reload log configuration
> - etc ...
> using the command line.
>
> Of course, most of these tasks can be achieved using JConsole (or other JMX
> clients).
> However, in production, most of the time, the administrator:
> - doesn't have graphical environment (Unix Xorg)
> - would like to script some actions (to deploy, etc)
> - would like to script some monitoring (plug list endpoint/service unit in
> Nagios for example to check if all is deployed)
> - etc
>
> As we already provide Ant tasks (some defined in the JBI specification), I
> think that the most logical is to provide new ServiceMix specific ant tasks
> for both SMX3 and NMR.
>
> Another way is to provide a shell like servicemix-shell (mostly for SMX3).
>
> What do you think ?
>
> Thanks
> Regards
> JB
>