That is tragic for MCollective (and other things at Puppet).  I hope it can 
be maintained outside of Puppet umbrella (where things go to die), and have 
integration/migration docs/tools later.

I noticed that Salt Stack had striking similarities.  Any thoughts on diffs 
MCollective vs. Salt Stack vs. Choria? I ask this not from marketing bs, 
but real get down to the nerd enthusiasts perspective.

On Monday, April 30, 2018 at 11:19:46 PM UTC-7, R.I. Pienaar wrote:
>
>
> On 1 May 2018, at 08:04, Joaquin Menchaca <[email protected] 
> <javascript:>> wrote:
>
> Both Choria and Jerakia look awesome.  I am so glad these awesome folks 
> are still innovating.  I will explore these after my pilot project.  They 
> look useful outside of Puppet, especially Jerakia, I can see using this 
> across CAP (Chef-Ansible-Puppet).
>
> Whatever happened to MCollective?  That sort of went to Puppet and died.  
> I remember the book I picked up at an PupetConf said the tool was support 
> to be orchestrator for both Puppet and Chef.
>
>
> Yeah that’s roughly what happened. Those testing out the Puppet 6 nightly 
> will notice mcollective is not in puppet agent anymore
>
>  
> Choria as the site suggests is both modernising mcollective to make it 
> usable to today’s open source user and also redeveloping huge parts of it 
> and adding new end user features. It will provide a trivially installable 
> way to keep using it post the packaging change in puppet agent. So it’s not 
> like it’s going away. 
>
> As for puppet/chef etc support. It does, and have always, support other CM 
> or indeed no CM. Given that I had to make it usable on my own again I out 
> of realities of available time had to focus on one CM tool to fix the 
> installation story first
>
> That’s not to say it does not support living in other ones it’s just not 
> as turnkey easy
>
> Someone in the community can totally write some cookbooks to install and 
> deploy it la plugins and it will work
>
> This will become easier soon as the new choria daemons are 1 binary but we 
> will see how that turns out. 
>
>
>
> For my main scope, I want to use minimum method for data injection, so 
> maybe bolt or hiera.  It's interesting that this is not something easy on 
> Puppet, and that Puppet really doesn't have variables (really connstants), 
> so the original design was data was embedded into the module.  The 
> parameters is fills the role of variables that can be overridden.  
>
> Wait, Dayyyuuuum..  Jerakia can Consul... WOW.
>
>
> On Monday, April 30, 2018 at 1:28:21 PM UTC-7, Andreas Zuber wrote:
>>
>> On 04/30/2018 06:29 PM, Joaquin Menchaca wrote: 
>> > 
>> > Bolt has me curious.  I have dabbled around with it, running commands 
>> or 
>> > a script to a remote node.  Are there other ways I could use this?  
>> > Could I use it to introduce custom facts, or inject values into 
>> > puppetdb? hiera?  The docs are not all that intuitive (had to step 
>> > through gem source code to discern how to use ssh transport for my 
>> > environment). 
>>
>> Have a look at https://choria.io/docs/playbooks/basics/ . Like Bolt it 
>> can run puppet tasks, but you can also write whole plans in the puppet 
>> language to orchestrate a cluster. 
>>
>> It is super easy to setup with the modules provided and is based on 
>> mcollective which already comes with the puppet AIO package. 
>>
>> Regards 
>> Andreas 
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/f5610774-cdd4-4dc6-ab7d-31839f945943%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/puppet-users/f5610774-cdd4-4dc6-ab7d-31839f945943%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/361ecaa7-8122-492a-8347-faf117d930ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to