Re: [mcollective-users] Nasty error message on mcollective.log

- Original Message - > From: "Ravi Kumar" > To: "mcollective-users" > Sent: Friday, 12 August, 2016 16:48:11 > Subject: [mcollective-users] Nasty error message on mcollective.log > Hi Folks, > > On couple of servers in my

Re: [mcollective-users] mColllective registration meta.rb

mColllective registration meta.rb > getting proper response for mco ping and other mco commands. Only thing is > not getting this meta registration message across country. > > On Mon, Aug 8, 2016 at 4:08 PM, R.I.Pienaar <r...@devco.net> wrote: > >> >>

Re: [mcollective-users] mColllective registration meta.rb

- Original Message - > From: "Ravi Kumar" > To: "mcollective-users" > Sent: Monday, 8 August, 2016 12:27:04 > Subject: Re: [mcollective-users] mColllective registration meta.rb > problem is registration messages are not going

Re: [mcollective-users] Exec "mco puppet runonce" the agent can't work

You need to also install the mcollective puppet agent as per here https://github.com/puppetlabs/mcollective-puppet-agent As you're on puppet 4 you might want to try https://github.com/ripienaar/mcollective-choria/wiki which sets everything up for you and uses a less resource intensive

Re: [mcollective-users] choria - issue - undoubtably me

On Tue, Jan 31, 2017, at 17:02, Paul Seymour wrote: > > > On Tuesday, 31 January 2017 15:55:01 UTC, R.I.Pienaar wrote: > > > > Can you stick the resulting server.cfg on a gist so I can see the whole > > thing? > > > > I use the puppetlabs ini m

Re: [mcollective-users] long running mcollectived which can't use filters

This is really weird, even if your fact cache got corrupt others would still work My guess is somehow the agents lost one of their subscriptions to the middleware, the stomp gem stores a view of whats been subscribed and on reconnect it resubscribes and I guess something could have gone wrong

Re: [mcollective-users] Registration monitor not receiving messages properly in big infra

--- R.I.Pienaar > On 30 Aug 2016, at 08:02, rakare2...@gmail.com wrote: > > Yeah. Its work fine with activemq but the issue with rabbitmq only. Looks > like its not getting valid subscription id header when it connects to > rabbitmq. If you dont mind can you let me know what

Re: [mcollective-users] Registration monitor not receiving messages properly in big infra

re why its not getting the subscription > id. That'll be the bit where I said its ancient and needs a rework :) It uses old APIs. > > > > On Monday, August 29, 2016 at 8:23:46 PM UTC+5:30, R.I.Pienaar wrote: >> >> >> >> - Original Message --

Re: [mcollective-users] Registration monitor not receiving messages properly in big infra

- Original Message - > From: "rakare2015" > To: "mcollective-users" > Sent: Monday, 29 August, 2016 16:47:12 > Subject: Re: [mcollective-users] Registration monitor not receiving messages > properly in big infra > I just >

Re: [mcollective-users] Retrieving error messages from puppet agent using mco

- Original Message - > From: "mcollective-users" > To: "mcollective-users" > Sent: Friday, 28 October, 2016 11:34:52 > Subject: [mcollective-users] Retrieving error messages from puppet agent > using mco > Hi, >

Re: [mcollective-users] mCollective connection broken with error

- Original Message - > From: "rakare2015" > To: "mcollective-users" > Sent: Wednesday, 2 November, 2016 14:29:35 > Subject: Re: [mcollective-users] mCollective connection broken with error > on activemq i dont see any logs for

Re: [mcollective-users] overcome mcollective connectivity issue due to time drift

n server.cfg right? Or can it possible to > change the default ttl value to highest one while running with mco command. > > On Wednesday, November 2, 2016 at 7:17:48 PM UTC+5:30, R.I.Pienaar wrote: >> >> You can set ttl in the config file to some large number, though you r

Re: [mcollective-users] overcome mcollective connectivity issue due to time drift

You can set ttl in the config file to some large number, though you really should fix the actual problem. - Original Message - > From: "rakare2015" > To: "mcollective-users" > Sent: Wednesday, 2 November, 2016 14:38:53 >

Re: [mcollective-users] mCollective connection broken with error

- Original Message - > From: "rakare2015" > To: "mcollective-users" > Sent: Wednesday, 2 November, 2016 14:05:30 > Subject: [mcollective-users] mCollective connection broken with error > Unable to figure out why getting below

Re: [mcollective-users] mCollective registration receiver tune

- Original Message - > From: "rakare2015" > To: "mcollective-users" > Sent: Wednesday, 26 October, 2016 14:30:49 > Subject: [mcollective-users] mCollective registration receiver tune > Am > using >

[mcollective-users] A Choria update

: http://choria.io --- R.I.Pienaar -- --- 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 mo

[mcollective-users] choria/mcollective_choria release 0.0.25

to them *choria/nats release 0.0.8:* *Bug Fixes:* * Fix installation on RedHat 6 * Use the clientcert variable rather than FQDN to improve the situation where FQDN != certname Thanks to first time contributor Abhishek Dastidar for these 2 bug fixes. -- R.I.Pienaar / www.devco.net

Re: [mcollective-users] timeout for mco command when middleware is down

gt; > --- > 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 htt

Re: [mcollective-users] mco query with nested facts filter

On Tue, Mar 14, 2017, at 18:59, Michael Smith wrote: > That flattened view matches approaches we've discussed using elsewhere. > That certainly seems reasonable. yeah and facter.soon will have a flattened output of its own too with all the tools more or less supporting this I wonder if there's

Re: [mcollective-users] mco query with nested facts filter

On Wed, Mar 15, 2017, at 18:48, Michael Smith wrote: > PUP-6040 was talking > about > using this for 'puppet facts'. > #puppet-dev gave some .pp code to do it, easy to port https://puppetcommunity.slack.com/files/thrnio/F4JCD81L2/-.pp I'll

Re: [mcollective-users] nats-pure and kernel tuning for gnatsd

On Tue, Apr 4, 2017, at 18:41, Christopher Wood wrote: > (Writing this out here for posterity and people seeing similar items.) > > A little while ago I erroneously thought that gnatsd might use openssl > and thus had gnatsd tagged to restart on openssl package update via > puppet. (Found

[mcollective-users] choria/mcollective_choria release 0.0.26

:* *New Features:* * If you're on a systemd distribution you can now set the number of open files the gnatsd process is allowed Special thanks to Tim Meusel and David Hollinger III for their contributions to these releases -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You received

Re: [mcollective-users] Understanding about direct addressing mode

> "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 --

Re: [mcollective-users] mco rpc vs mco

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. &g

[mcollective-users] Federated Collectives

nced across them all - to produce the 1 messages. In my testing this actually speeds things up a fair bit since a lot of the hard work of making the requests are now load shared across groups of workers, its transparent and supports all mcollective features. -- R.I.Pienaar / www.devco.net / @

Re: [mcollective-users] mco query with nested facts filter

On Sun, Mar 12, 2017, at 07:50, rakare2...@gmail.com wrote: > ohh.. Then I may have to downgrade the facter to little lower version > make > use of all the facts through mcollective. > > Do you think any solution for this with the latest facts version with > nested structure? If not then the

Re: [mcollective-users] Federated Collectives

I wrote up some early end user docs about how this might function, I've not yet written a released Federation Broker but the docs might paint a better picture: http://choria.io/docs/configuration/federations/ On Sun, Mar 12, 2017, at 10:20, R.I.Pienaar wrote: > Hello, > > Recently

Re: [mcollective-users] Re: Use mCollective geographically

e so when its a 'strange issue'. -- 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+unsubs

Re: [mcollective-users] make use of registrationmonitor discovery

On Sat, Mar 11, 2017, at 06:29, rakare2...@gmail.com wrote: > I have registration meta configured and have the inventory detail of all > of > my servers, so I would like to use > the > https://github.com/puppetlabs/mcollective-plugins/tree/master/agent/registration-monitor/discovery > you

Re: [mcollective-users] make use of registrationmonitor discovery

On Sat, Mar 11, 2017, at 06:46, rakare2...@gmail.com wrote: > Hey, > > No I did not make any change on that file. I just simply downloaded .rb > and > .ddl files > from > https://raw.githubusercontent.com/puppetlabs/mcollective-plugins/master/agent/registration-monitor/discovery/ > > and

Re: [mcollective-users] make use of registrationmonitor discovery

7 > filesystems: ext4,iso9660,vfat > hardwareisa: x86_64 > gemhome: /usr/lib/ruby/gems/1.8 > operatingsystemrelease: "6.7" > swapsize: 8.00 GB > allow_virtual_packages: "false" > uniqueid: sdf32345f > processor2: Intel(R) Xeon(R) CPU E5-2660 0

Re: [mcollective-users] [ANN] Plugin releases: puppet-agent 1.13.0, service-agent 3.1.4

; "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

[mcollective-users] Choria Module Releases

configuration by using a template to manage config files *choria/nats version 0.0.12:* *Enhancements:* * TLS timeouts are configurable using *tls_timeout* and *cluster_tls_timeout*. * NATS upgraded to 1.0.0 -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You received this message because you

[mcollective-users] Choria releases headsup

days, maybe next week. I am also looking for Beta testers for a new network broker and federation broker all in one binary if anyone feel like spending some of their time testing these with me get in touch. -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You received this message because

Re: [mcollective-users] Maximum payload violation from mcollective rpc client

On Tue, Jul 4, 2017, at 17:57, jhoutman via mcollective-users wrote: > Hi group, > > > We have build a few custom mcollective plugins, that are build on the > rpcclient. > > With one of those we now get the following error: > natswrapper.rb:138:in `block in start' Disconnected from NATS: >

Re: [mcollective-users] Maximum payload violation from mcollective rpc client

hey On Thu, Jul 6, 2017, at 10:45, 'Jos Houtman' via mcollective-users wrote: > Hi, > > A common case is deploying a database, hadoop jobs, running sql script. > > The request can be small, because files are usually out of bounds and > downloaded as part of the task. > > The output of the

[mcollective-users] Choria users list

and such on this list and of course have no problem supporting people anywhere, but if Choria users could start moving over there that would be great. Thanks -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You received this message because you are subscribed to the Google Groups

[mcollective-users] Choria Releases

, a nicer error will be produced now *choria/discovery_proxy 0.1.0:** * *Enhancements:** * * To match functionality with choria this also now supports the dot notation for fact queries -- R.I.Pienaar / www.devco.net / @ripienaar Links: 1. https://groups.google.com/forum/#!forum/choria

Re: [mcollective-users] Limit the "blast radius" by having individual users per environment/collective

On Wed, May 3, 2017, at 14:41, Turbo Fredriksson wrote: > On 3 May 2017, at 12:36, R.I.Pienaar <r...@devco.net> wrote: > > > Of course this is done not using AMQP but via the Stomp plugin for > > RabbitMQ so that'll be interesting to get going. > >

[mcollective-users] Choria PuppetDB Discovery

e knows Go well I could do with some feedback on the Go code. -- 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 emai

Re: [mcollective-users] ActiveMQ dropping connection for all the network of brokers after the queue overloaded

On Tue, May 30, 2017, at 06:35, Karthi Sweet wrote: > I have configured ActiveMQ network of brokers with different locations > with > MCollective and it was working fine. All the MCollective servers are > configured with identity. One of my team member had executed the mco > commands with

[mcollective-users] Choria Releases

heir help with these releases -- 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 mcollec

Re: [mcollective-users] [ANN] Plugin release: service-agent 3.1.5

ions, 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] Puppet and Service Agent releases

hello, After Michael did releases yesterday of the above agents I did the matching Choria releases to Forge today. -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubs

Re: [mcollective-users] languages for writing agents

On Tue, Oct 3, 2017, at 15:38, Trevor Vaughan wrote: > General exec seems fine and I'm a fan of gRPC in general with the caveat > that none of this is viable in a FIPS environment unless it gets wrapped > in stunnel or IPSec. presumably neither does the entire Go based agent though :) We

[mcollective-users] languages for writing agents

://github.com/puppetlabs/marionette-collective/tree/master/ext/action_helpers [2] https://github.com/hashicorp/go-plugin -- 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

Re: [mcollective-users] languages for writing agents

On Tue, Oct 3, 2017, at 16:01, Trevor Vaughan wrote: > On Tue, Oct 3, 2017 at 9:51 AM, R.I.Pienaar <r...@devco.net> wrote: > > > > > > > On Tue, Oct 3, 2017, at 15:38, Trevor Vaughan wrote: > > > General exec seems fine and I'm a fan of gRPC in

Re: [mcollective-users] languages for writing agents

On Tue, Oct 3, 2017, at 16:28, Trevor Vaughan wrote: > On Tue, Oct 3, 2017 at 10:08 AM, R.I.Pienaar <r...@devco.net> wrote: > > > > > > > On Tue, Oct 3, 2017, at 16:01, Trevor Vaughan wrote: > > > On Tue, Oct 3, 2017 at 9:51

[mcollective-users] Re: [choria-users] Bolt tasks was Re: languages for writing agents

t the last will be subject to the exact same service > description language ie. JSON Schema or similar. > > So there will be a translation layer from service description to service > executor and the executors would be compiled in, JSON, grpc, lua etc. I > probably won’t let people ad

[mcollective-users] Choria Module Releases

to be used *Removals:* * Remove the *mcollective_assert* task -- R.I.Pienaar / www.devco.net / @ripienaar Links: 1. https://puppet.com/docs/bolt/0.x/writing_plans.html#handling-plan-function-results 2. https://groups.google.com/forum/#!forum/choria-users -- --- You received this message

Re: [mcollective-users] Agent, Identity and Class filters how to exclude host

On Fri, Nov 10, 2017, at 16:51, Christopher Wood wrote: > mco find > > versus > > mco find -S '!fqdn=web1.example.com' > > The filters page is definitely worth reading over closely, I didn't even > realize this myself for... an embarrassingly long time. > >

[mcollective-users] Choria Integration of Puppet Tasks

hello, I am working on and will soon release full integration of Puppet Tasks into MCollective via Choria. I made a video of the feature you can see @ https://www.youtube.com/watch?v=LLyjPjZW7TE Let me know if you have any questions! -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You

Re: [mcollective-users] Mcollective and Windows

On Mon, Nov 6, 2017, at 16:02, Dimitri Yioulos wrote: > Hey, all. > > Somehow, I've stumbled and bumbled my way toward a working mCollective (I > did not use Choria.io). The Linux agents seem to be working well, for > the > most part. But, as with a lot of shops, mine is a mixed

Re: [mcollective-users] Re: Mcollective and Windows

On Mon, Nov 6, 2017, at 17:52, Dimitri Yioulos wrote: > OK. I was using a 3.x version of puppet-agent. I uninstalled that, and > installed puppet-agent-x64-latest.msi. I see where it not only creates > the > puppet service, but also the mcollective service. Great. On looking > in

[mcollective-users] testers wanted

questions! -- R.I.Pienaar / www.devco.net / @ripienaar Links: 1. https://nats.io/documentation/streaming/nats-streaming-intro/ -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubscribe from this group and stop receiv

[mcollective-users] Choria Module Releases

would be welcome! Onto the releases: *choria/mcollective_choria version 0.5.0:* * Arch Linux support *choria/mcollective version 0.3.0:* * Arch Linux support Thanks goes to Tim Meusel for his work in bringing us these enhancements! -- R.I.Pienaar / www.devco.net / @ripienaar Links: 1. https

[mcollective-users] Choria Server 0.3.0 Release

will soon do some more releases too, so if you're tracking my releases closely it might be worth waiting a few days and do it all in one. -- R.I.Pienaar / www.devco.net / @ripienaar Links: 1. https://github.com/choria-io/go-choria/releases 2. https://packagecloud.io/choria/release -- --- You

[mcollective-users] Choria Module Releases

:* *Enhancements* -- 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...@google

[mcollective-users] Re: [choria-users] Choria Module Releases

I hit send a bit early, here's what I left out: > *choria/mcollective_agent_puppet version 2.1.0:* > *Enhancements* *choria/mcollective_agent_puppet version 2.1.0:* *Enhancements:* * Add a playbook to find stuck Puppet Agents that will never check in with Puppet Server again -- --- You

[mcollective-users] Choria Module Release

with no input arguments can be run * Allow Hash inputs to be supplied on the CLI as JSON strings * Ensure required arguments can be supplied via JSON data * Improve application descriptions *choria/mcollective_agent_bolt_tasks version 0.8.1:* As above -- R.I.Pienaar / www.devco.net / @ripienaar

[mcollective-users] Choria Module Release

Server gives about tasks as immature, but we'll get there in the end. *choria/mcollective_choria version 0.8.2:* *Bug Fixes:* * Handle tasks without any JSON metadata included *choria/mcollective_agent_bolt_tasks version 0.8.2:* As above -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You

Re: [mcollective-users] Mcollective not connecting to Activemq

t? you can put your mco command in debug by editing the client.cfg (or ~/.mcollective) and setting the loglevel. In general I would say any and everyone who is doing a new deploy should NOT be using ActiveMQ and they should use choria.io instead which gives a MUCH less awful experience -- R.I.Pienaar /

Re: [mcollective-users] MCollective Message Decode in Python

error means some data at the end is missing - often normal - base64 data has to be dividable by 4, if not add "=" at the end till it is. Then it should work not sure what happens that your data is corrupt though -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You receive

Re: [mcollective-users] MCollective Message Decode in Python

On Wed, 24 Jan 2018, at 21:26, rakare2...@gmail.com wrote: > Ok, if we have too many machines connected with ActiveMQ then we can't > solve this problem at all right? we've discussed this many times, you're welcome to read your own past threads -- --- You received this message because you

Re: [mcollective-users] MCollective Message Decode in Python

and if you see at the end of body value the closed > curly '}' is missing. But not sure if its missing or its not showing due to > the encryption. Would you please help me to understand why it comes like > this? > > > On Sunday, January 21, 2018 at 11:38:09 PM UTC+5:30, R.I.Pie

Re: [mcollective-users] MCollective Message Decode in Python

On Wed, 24 Jan 2018, at 21:20, rakare2...@gmail.com wrote: > Oh that's really great! If you don't mind could you please share the > ActiveMQ.xml config details on the central ActiveMQ, So I can also try with > the same config to see if that helps. no, we already determined you are trying to

Re: [mcollective-users] MCollective Message Decode in Python

On Wed, 24 Jan 2018, at 21:10, rakare2...@gmail.com wrote: > I agree. Can you suggest any better tuning for ActiveMQ to make Ruby STOMP > consumer to consume message more fast. Right now it consumes around 2000 > messages per 1-2mins of time, but am looking consumer where it can receive >

Re: [mcollective-users] Random "Exit code 100" on hosts

On Fri, 12 Jan 2018, at 17:38, Turbo Fredriksson wrote: > I'm getting "Exit code 100" on random hosts when trying to run "mco apt > update". > > I can't see anything in any log that could help me try to figure this one > out. Anyone > have suggestion on how to debug this? the apt man page

Re: [mcollective-users] Some discrepancy in direct addressing mode with reply-to

work, I guess the best hints lie in the server debug log. Does it send a reply and does it do so to the right target? -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubs

Re: [mcollective-users] Some discrepancy in direct addressing mode with reply-to

e same request id - ie. do you want a true batch mode where all requests have the same ID or many seperate requests would be fine? I still am curious why you need to use direct mode rather than broadcast > > On Sunday, January 28, 2018 at 6:23:35 PM UTC+5:30, R.I.Pienaar wrote: > >

Re: [mcollective-users] Some discrepancy in direct addressing mode with reply-to

y which comes from different subcollectives. So I > don't have specific facts filter to run in broadcast mode and also I can't > make such facts also. Its basically kind of requirement for us to run this > often. > > > On Sunday, January 28, 2018 at 9:14:52 PM UTC+5:30, R.I.Pien

[mcollective-users] headsup about PuppetDB discovery and PuppetDB 5.2

hello, If any choria users are using the PuppetDB integration for discovery please note that I've had reports of this breaking in PuppetDB 5.2. Upgrade with caution. This ticket tracks the issue @ Puppet Inc https://tickets.puppetlabs.com/browse/PDB-3852 -- R.I.Pienaar / www.devco.net

[mcollective-users] Upcoming releases

style of management. -- 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-user

[mcollective-users] Re: Upcoming releases

, R.I.Pienaar wrote: > hello, > > It's been a while since I made any releases - I have been super busy > with the new brokers and daemons and waiting for Puppet 5.4.0 to ship. > I wanted to write a mail giving everyone an update on where we are and > what is happening. > >

[mcollective-users] Choria Module Releases

Stangl and Tim Meusel for their contributions to this release! -- R.I.Pienaar / www.devco.net / @ripienaar Links: 1. https://www.devco.net/archives/2018/02/25/choria-playbooks-dsl.php -- --- You received this message because you are subscribed to the Google Groups "mcollective-users&q

[mcollective-users] Choria Server Version 0.5.1

a crucial step on our path to be better behaved in Cloud environments. -- 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 fro

[mcollective-users] Release Choria Server 0.6.0

is set (choria-io/provisioning-agent#41) *Bug Fixes:* * Ensure provisioning mode is active only for the server and not client invocations (#402) -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You received this message because you are subscribed to the Google Groups "mcollective-

Re: [mcollective-users] mco puppet runonce -I hostname setting wrong host identity

"} > > so when application reads user.name , its getting user name as > "RANGER_WIN7$" which is wrong. > > Any one has clue why this is happening? The one with the $ is a managed service account, so its basically a different account than you'd have when logging

[mcollective-users] Choria Plugin Releases

for compatibility with the packager Thank you Vadym Chepkov for your help in testing and debugging this one! -- 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 grou

Re: [mcollective-users] Reseting last_run_summary?

above command does not run puppet, that file is the status of a puppet run. So there's no connection between the package agent and this file at all, it will never update it, reading it has no relevance. -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You received this message because you are

[mcollective-users] Re: [choria-users] headsup about PuppetDB discovery and PuppetDB 5.2

: https://github.com/ripienaar/choria-aws-test On Thu, 15 Feb 2018, at 15:59, R.I.Pienaar wrote: > hello, > > If any choria users are using the PuppetDB integration for discovery > please note that I've had reports of this breaking in PuppetDB 5.2. > > Upgrade with caution

Re: [mcollective-users] IBM MQ Plugin for mcolletive?

m > plugin out there maybe? I have not seen one, writing a new one is not documented unfortunately but there are plenty of examples out there -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You received this message because you are subscribed to the Google Groups "m

Re: [mcollective-users] Puppet Agent 5.5.0 Headsup

se out early this week > > https://github.com/choria-io/puppet-mcollective/pull/162 > > Thank you Romain. > > --- > R.I.Pienaar > > > On 25 Mar 2018, at 12:19, R.I.Pienaar <r...@devco.net> wrote: > > > > hello, > > > > Puppet Agent 5.5.

[mcollective-users] Puppet Agent 5.5.0 Headsup

For now, 5.5.0 is best avoided. -- 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-user

Re: [mcollective-users] Choria Releases

hello, Further to this I just released choria/choria 0.7.1 which resolved 2 debian issues: * apt-get update is run when adding repos * identity is now specifically configured to the fqdn Thanks Jason Spalding and Mateusz Gozdek for your kind help On Wed, 21 Mar 2018, at 16:53, R.I.Pienaar

[mcollective-users] Choria Releases

nux * Deprecate the Ruby Federation Broker * Remove YAML playbook * Remove the mco federation observe command -- R.I.Pienaar / www.devco.net / @ripienaar Links: 1. https://master.choria.io/docs/adapters/ 2. https://choria.io/docs/deployment/broker/ 3. https://choria.io/docs/tasks/ 4. ht

[mcollective-users] Upcoming deprecations

how this can help you. This will help everyone though who want to ingest data from Choria into other systems. Especially I am keen to explore asynchronous RPC a bit more soon, this will be foundational to that. Proposed docs for this: http://dev.choria.io/docs/adapters/ -- R.I.Pien

[mcollective-users] choria/mcollective_choria release 0.11.0

contributions to this release -- 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-user

[mcollective-users] Choria Module Releases

OpenBSD support * Improve FreeBSD support * Support packaging modules with Puppet installed via gem *choria/choria version 0.11.0:* * Improve itterators in the plan DSL to return collected results instead of items * Support building modules with Puppet installed from gem -- R.I.Pienaar

[mcollective-users] Choria releases

* to users of the go framework *choria/mcollective_choria and choria/mcollective_agent_bolt_tasks 0.13.0:* * Support integrating Choria CLI with centralised AAA services *choria/mcollective_agent_nrpe 4.1.0:* * Support running commands as non root via sudo -- R.I.Pienaar / www.devco.net / @ripienaar

[mcollective-users] Choria Releases

file paths * Support intermediate certificate chains * Export the PKI and TLS modes via choria_util#info * Increase choria_util timeout to allow for slow facter -- R.I.Pienaar / www.devco.net / @ripienaar -- --- You received this message because you are subscribed to the Google Groups

[mcollective-users] Choria Server release 0.9.0

timeout to facilitate slow facter runs * Fix reboot splay time when doing self updates -- 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 e

[mcollective-users] Choria Server release 0.8.0

plugin.security.always_overwrite_cache (#476[6]) * Support running Choria Server in a namespace on Enterprise Linux via a COMMAND_PREFIX in the init script (#473[7]) * Support writing server status regularly (#476[8]) * Switch to github.com/gofrs/uuid for UUID generation -- R.I.Pienaar

[mcollective-users] Choria Module Releases - Puppet 6 Support

by default * Use the correct hash2config function -- R.I.Pienaar / www.devco.net / @ripienaar Links: 1. https://choria.io/mcollective 2. https://choria.io/docs/deployment/mcollective/#puppet-6 3. https://rubygems.org/gems/choria-mcorpc-support 4. https://choria.io/docs/configuration

[mcollective-users] May 2019 Releases

overflow better Choria Stream Replicator 0.4.1 Links: Changes <https://github.com/choria-io/stream-replicator/compare/0.3.1...0.4.1>, Release <https://github.com/choria-io/stream-replicator/releases/tag/0.4.1> Enhancements * Allow TLS to be enabled for only one side of th

[mcollective-users] March Releases

Hello, We're pleased to release March releases of Choria and related modules. Special thanks to Romain Tartière, Trey Dockendorf, Tim Meusel and Mark Frost for their contributions in this release. Read all about it here: https://choria.io/blog/post/2021/03/29/april_releases/ -- R.I.Pienaar