push a few config files to dozen or so servers
Alfred Perlstein
alfred at freebsd.org
Sat Feb 7 23:26:58 UTC 2015
On Feb 7, 2015, at 11:15 AM, Charles Sprickman wrote:
> On Feb 7, 2015, at 12:17 PM, Paul Mather <paul at gromit.dlib.vt.edu> wrote:
>
>> On Feb 6, 2015, at 5:31 PM, parv <parv at pair.com> wrote:
>>
>>> in message <6CC9FCD8-EB12-4DD1-A76E-8F43C044340F at ultra-secure.de>,
>>> wrote Rainer Duffner thusly...
>>>>
>>> ...
>>>> I???ve always wanted to try ansible, which looks like it has
>>>> decent support for FreeBSD.
>>>>
>>>> Anybody got experience with that?
>>>
>>> From Dan L (not me) ...
>>>
>>> http://dan.langille.org/2013/12/22/ansible-versus-salt/
>>>
>>> https://twitter.com/search?q=from%3Adlangille%20ansible&src=typd
>>>
>>>
>>> - parv
>>
>>
>> One of the reasons I've been looking at Salt recently is because of this post in December 2014 by Craig Rodrigues, who set up and maintains the FreeBSD project's Jenkins cluster:
>>
>> https://lists.freebsd.org/pipermail/freebsd-testing/2014-December/000693.html
>>
>> Going by that post, it seems that he is leaning towards using Salt to manage the cluster.
>>
>> My hope is that if jenkins.freebsd.org is using Salt for infrastructure management then perhaps FreeBSD support might get a boost in the Salt community.
>
>
>> I'm previously familiar with Puppet and am looking at Salt at the moment. There are similar concepts between the two, e.g., pillars = hiera; grains = facter; etc.
>
> Devops is a lovely thing, and I see the appeal, and it’s nice there’s a community building all manner of software to assist in managing large groups of servers.
>
> <rant>
> But the trend of developers coming up with cute and/or clever names for concepts, configuration items, and behaviors simply has to stop. It serves no purpose but to be cute. One could even call it intentional documentation obfuscation. It annoys me to no end.
> </rant>
One could say the same about any specialized vernacular used. Why say "float bowl" or "pilot jet" when talking about carbeurtors as opposed to a more descriptive term such as "the area in the carb where fuel accumulates to supply the jets with fuel which is metered by a float device". Well obviously because it's part of the lexicon of carburetor work.
Same has to be done for things such as devops tools, even when all they are doing is combining commonly used things into a single thing.
Knee jerk reaction to being upset that a new term is being said when you don't know what it is. It's better to control that reaction and look towards what can be learned from it.
>
> So what is in use for the jenkins cluster, anyone know?
>
> And any totally FreeBSD-centric HOWTOs on either ansible or salt?
>
> Charles
>
>
>> I haven't looked at Ansible very closely, but it seems that Salt also covers the same ground in its strong focus on orchestration.
>>
>> I think all these systems are very good in their own right, but in the end community support for your preferred OS is paramount. I'm hoping that FreeBSD looking at using Salt for the Jenkins cluster might boost FreeBSD support in the Salt community.
>>
>> Cheers,
>>
>> Paul.
>>
>>
>> _______________________________________________
>> freebsd-stable at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>
More information about the freebsd-stable
mailing list