Ansible users. How does every handle the SSH and root access parts? I assume you don't have ansible connecting directly as root on the destination servers, you use a regular user. Then how do you give that user sudo/root access and provide that user password so the ansible task can execute a root function?
That was the road block I last hit with Ansible and haven't gone back to try to resolve. bb On Thu, Nov 13, 2014 at 9:17 AM, John Stoffel <j...@stoffel.org> wrote: >>>>>> "Edward" == Edward Ned Harvey (lopser) <lop...@nedharvey.com> writes: > >>> From: Edmund White [mailto:ewwh...@mac.com] >>> >>> Try Blueprint, then - http://devstructure.com/blueprint/ > > Edward> That. Sounds. Awesome. Will try, thanks for the suggestion. > > This has been an awesome suggestion, and a discussion I've been > following with alot of enjoyment and hope to actually get off my ass > and start deploying some sort of CM. > > I have compute clusters with identical systems which I'd like to bring > into cohesion with each other, but the learning curve of cfengine2 and > cfengine3 has always turned me off, even though I keep making half > hearted efforts to deploy it. > > The other holdback is legacy systems. Lots of them. Old crufty > Solaris 5.8 systems, slightly better 5.9 and now a group of Solaris > 5.10 Sparc and x86_64 systems, along with 5.11 starting to appear. > Sigh... > > The other big issue has been just getting the rest of the team to > agree to use this setup. No sense in doing all this work if I'm not > going to get anyone else to use it as well. Which is a management > issue really, but the biggest stumbling block of all. > > So using chef/puppet/salt/ansible/blueprint all fall down on the > legacy support. But maybe that's just me being too perfectionist > here. But I do want to automate even these Sparc systems, esp the > standalone Oracle servers which need accounts sync'd between them, > though not all accounts on all systems. > > A pain. And the one which cfengine with it's C base seems the best > way to solve... > > So please keep up this discussion, and please keep posting solutions, > pointers and maybe even recipes for some of this would be solved. > > John > _______________________________________________ > Tech mailing list > Tech@lists.lopsa.org > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > This list provided by the League of Professional System Administrators > http://lopsa.org/ _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
