In the general case:

  $ mco rpc puppet status:

is a single call after discovery, it does one thing and provides only
the one UI.  `mco rpc` is a attempt to make a one-size-fits-all user
interface to ANY agent that complies to the RPC framework.  In this goal
it succeeds in as much as you can call anything and see the results. 
But it fails in that people who want to build tools ontop of mcollective
have their own uses and contexts.

So as a puppet user for example, you'd rather see:

    dev1.devco.net: Currently idling; last completed run 23 minutes 10
    seconds ago
    dev4.devco.net: Currently idling; last completed run 19 minutes 38
    seconds ago
    dev2.devco.net: Currently idling; last completed run 9 minutes 51
    seconds ago

than pages of this:

dev1.devco.net
         Applying: false
   Daemon Running: true
     Lock Message:
          Enabled: true
           Idling: true
         Last Run: 1489155759
          message: Currently idling; last completed run 23 minutes 34
          seconds ago
   Since Last Run: 1414
           Status: idling


`mco puppet status` produce the first output.  

It's a way for people to write tools that either just show the results
in different ways or do higher order orchestrations like the 'mco puppet
runall' does.

There's no true answer to which is better/faster.


On Fri, Mar 10, 2017, at 15:31, rakare2...@gmail.com wrote:
> Hi,
> 
> Just to understand what would be difference between run mco commands with 
> the direct agents like "mco shell -I <servername> 'uname -a' " and with
> rpc 
> like "mco rpc --agent shell --action run --argument command=whomai". Is 
> there any performance specific relation either mcollective side or 
> middleware side?
> 
> 
> 
> Regards
> Ravi
> 
> -- 
> 
> --- 
> You received this message because you are subscribed to the Google Groups
> "mcollective-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mcollective-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


-- 
R.I.Pienaar / www.devco.net / @ripienaar

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"mcollective-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mcollective-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to