Thanks to everyone for the feedback. This was all very useful! -Adam
On Tuesday, August 29, 2017 at 8:44:12 AM UTC-4, Dick Davies wrote: > > This is currently an opinion argument, and you need to turn it into a > numbers argument. It's the only way to get past egos. > > If a team deliver what they're asked to do on spec and on time, I > personally don't care what tooling they use, whether it's ansible or > hand-crafted. > > If they're delivering late or low quality, start quantifying that and > maybe trial some automation, then compare the outputs. > > On 25 August 2017 at 20:23, Adam Shantz <[email protected] <javascript:>> > wrote: > > I agree, they shouldn't be in power. Alas, it's the situation I'm in, > and > > I'm not a Director/VP. The people I refer to are system engineers. My > > thought is they are comfortable being the only people with root access > (even > > though I've managed to get Ansible setup with some level of root > > privileges), and see it as a job security threat to allow other people > such > > access. The other "reason" I've received is that any mature > organization > > has "division of duties" to ensure no one person has too much power. > Which > > is true, but I'm trying to ensure business continuity without having to > > remember (and make manual changes) to systems that have special > > customizations. I've tried to explain that as the platform & business > > owner, I'm the one that has to answer when things go wrong. I also have > a > > proven track record of including people in decisions, but it seems like > a > > control thing. I just want consistent, reliable, repeatable upgrades. > > > > Adam > > > > > > > > > > On Friday, August 25, 2017 at 3:06:45 PM UTC-4, Karl Jorgensen wrote: > >> > >> On Fri, 2017-08-25 at 11:08 -0700, Adam Shantz wrote: > >> > >> Hi all - > >> > >> I have some difficult people in my organization that are in positions > of > >> power that think that just because doing something manually "isn't very > >> hard", it shouldn't be automated. For example, clone of VMs from > templates, > >> setting up sshd_config, etc. > >> > >> > >> Hm... such people should not be in power - perhaps if we knew more > about > >> their reasoning for this attitude then the list may be useful in > proposing > >> lines of arguments to convince them? > >> > >> Is there anyone out there that would be willing to exchange emails (so > I'm > >> not airing dirty laundry publicly) to trade ideas on how to deal with > these > >> difficult situations? Bonus if you're in/near the DC or Virginia, USA > area. > >> > >> > >> By the little you have revealed, I doubt they would be receptive from > >> advice from a random stranger :-| > >> > >> > >> > >> -- > >> > >> Karl E. Jorgensen <[email protected]> > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Ansible Project" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > To post to this group, send email to [email protected] > <javascript:>. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/ansible-project/bbcecd70-aae7-4274-a6f7-b8e21ea3f497%40googlegroups.com. > > > > > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/5cfe7cfd-32de-482f-a4a0-a4f9b56f933b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
