Difference between revisions of "Puppet Project"

From RiceFamily Wiki
Jump to: navigation, search
(Articles)
(Articles)
Line 5: Line 5:
 
** [https://blog.dobrev.eu/blog/2016/04/28/the-foreman-the-scalable-way-part-1/ Part 1]
 
** [https://blog.dobrev.eu/blog/2016/04/28/the-foreman-the-scalable-way-part-1/ Part 1]
 
** [https://blog.dobrev.eu/blog/2016/10/18/the-foreman-the-scalable-way-part-2/ Part 2]
 
** [https://blog.dobrev.eu/blog/2016/10/18/the-foreman-the-scalable-way-part-2/ Part 2]
 +
* [https://theforeman.org/2015/12/journey_to_high_availability.html Foreman : Journey to High Availability]
  
 
= Subject =
 
= Subject =

Revision as of 02:13, 6 September 2017

Articles

Subject

  • Puppet
  • Ansible
  • BigFix

Puppet

Exists already in the environment.

  • Has been moved to NC-1.
  • Needs to have FailOver on F5.
  • What does Puppet do that BigFix can also do?
  • What does BigFix do that Puppet can't?
  • Should we proceed with the Project or wait?
  • Puppet WILL be used in the OpenStack environment. At least initially.
  • What are the impacts if the Puppet server goes down?
    • Is there a backup?
    • Do clients still keep the endpoints stable?
  • Red Hat helping us with OpenStack October 10th 8-9 week engagement.
  • Target is right after Thanksgiving.
  • Configuring Puppet is considered complex with a 'steep learning curve'.
  • We won't need the second server for "load", just for Disaster Recovery.
  • May be using it's own Github environment.
  • What determines if a Linux host is pointed to Puppet/Foreman?

  • Catchup with Keisha to get Sean and I access to the G3 Puppet/Foreman environment.

GitHub

Apparently our group will be picking this up as well. Greg Brown is going to pick it up.