#chef

/

      • cookie559 has quit
      • spuder joined the channel
      • _f1gm3nt joined the channel
      • fclausen has quit
      • _f1gm3nt has quit
      • fatdragon has quit
      • nd__ has quit
      • brucebag
        Environments file not needed for chef_environment
      • coderanger
        Hmm?
      • _f1gm3nt joined the channel
      • Gnut joined the channel
      • jdossey has quit
      • ranger81 joined the channel
      • fclausen joined the channel
      • fatdragon joined the channel
      • fatdragon has quit
      • trilitheus has quit
      • aruns joined the channel
      • indistylo joined the channel
      • mikedodge04 joined the channel
      • mikedodge04 has quit
      • Guest124 joined the channel
      • aruns__ joined the channel
      • Guest124
        I'm making changes to a cookbook that runs in all our infrastructure, but I would like to be able to run it on just 1 or 2 servers, before making these changes definite. Is there any easy way to do this?
      • coderanger
        Put those two servers in a special Chef environment and set the cookbook version restriction there
      • ranger81 joined the channel
      • Lucky_ABA has quit
      • Guest124
        coderanger: was hoping there was a way to manually run a checkout copy of a cookbook, ansible style
      • thanks though. I'll see what I can do with that suggestion
      • coderanger
        There are some very very footgun-y hidden options for that
      • MattMaker has quit
      • But I wouldn't recommend them (hence why we keep them undocumented)
      • Guest124
        ah :)
      • btw, I think I ran into your page recently :)
      • mind giving me a hint or two as to how I can use these options? I'm just curious to play with those :)
      • coderanger
        So the main one is --skip-cookbook-sync
      • which disables the data sync for cookbooks at the start of the run
      • You could run it once normally to fill the cache
      • Then disable the daemon-mode service if you have one
      • Manually update files in the cache
      • and run `chef-client --skip-cookbook-sync`
      • But if you abuse this or do something wrong and it breaks, you get to keep all the pieces ;-)
      • overlord_tm has quit
      • Gnut has quit
      • jblack has quit
      • pulpo joined the channel
      • Guest124
        coderanger: ah!
      • if I read you correctly,
      • does that mean then, it won't update the /var/chef/cache/cookbooks/ and therefore, you could possibly apply your changes locally to the in-cache copy?
      • coderanger
        Yes
      • Guest124
        that's perfect :)
      • jblack joined the channel
      • coderanger
        You could also potentially use chef-solo for testing, but it depends on how heavily you use Chef Server features
      • Guest124
        I can't really say much on that, I'm fairly new to chef and though I have access to our chef-servers, I tend to avoid making changes to them as little as possible, hence this option sounds like pretty good way for me to do a verification of a cookbook that's failed on a few select machines :)
      • zeroshft has quit
      • coderanger
        For a one off it's not the worst possible option, but in general if you want the ability to do canary deploys as part of your flow then I would find another option :)
      • nefilim joined the channel
      • nefilim has quit
      • Guest124
        absolutely. I'm pretty sure this is not how our production teams are doing canary deployments too. I made this change that worked in over >1000 hosts, but failed on 150. After reviewing the code and testing, I'm still puzzled as to why it failed on 150. All I have it the minimal output of the chef-client failure, but didn't manage to get ahold of the client.log
      • essentially, it points to a service block, for a non-started / non-enabled service, but as this caused a few alarms, it was reverted almost immediately so hopefully I'll be able to test the negative and positive scenario using this method
      • Lucky_ABA joined the channel
      • /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-cli-1.5.0/lib/mixlib/cli.rb:191:in `parse_options': invalid option: --skip-cookbook-syn
      • is this only in newer versions?
      • (although it seems like it's missing a c, that's because I failed to highlight the whole line)
      • Lucky_ABA has quit
      • coderanger
        Let me double check the option name
      • MattMaker joined the channel
      • spuder joined the channel
      • r3dk1ng joined the channel
      • r3dk1ng
        hello all
      • Guest124
        r3dk1ng: hello
      • r3dk1ng
        has AWS reported what the root cause for their outage was today?
      • Guest124
      • coderanger
        Not that I've heard, they are usually pretty quiet on that kind of thing though
      • r3dk1ng
        Yeah... we what did we learn? Alot of sites aren't fully HA :)
      • coderanger
        Eh, planning for S3 being down is overkill for almost everyone
      • Guest124
        yeah. I worked for amazon. The general policy/trend is to keep as much info away from public as possible.
      • r3dk1ng
        @coderanger it wasn't only S3
      • coderanger
        It has happened something like 3 times in past decade
      • r3dk1ng
        @coderanger I am an AWS customer, their N.Virgina status page had 60% of their services impacted... not just HA... even EC2, EFS, and Lambda
      • S3 was the first to get published and the media ran with it
      • coderanger
        It's not clear if it was a cascade effect or something deeper than S3
      • Like we know a bunch of services use S3 internally
      • So might be related, or might not be
      • r3dk1ng
        All my EFS shares when away
      • and then came back
      • also I could not do any autoscaling
      • of new instances
      • coderanger
        ¯\_(ツ)_/¯
      • r3dk1ng
        true
      • coderanger
        It would be cool is more people did multi-cloud whatevers but the ROI is pretty terrible so I don't think it's really fair to expect
      • r3dk1ng
        Multi Cloud for DR... perhaps
      • but not for HA
      • I agree
      • coderanger
        I mean yes, but even a well rehearsed full-site DR set up can take several hours. So from the point it was clear this wasn't just an S3 blip ...
      • But yes, more people should at least practice it :)
      • Guest124
        coderanger: any luck with the --skip.. etc? :)
      • coderanger
        Oh sorry, got distracted
      • Guest124
        np! appreciate your help :)
      • coderanger
        It is --skip-cookbook-sync
      • What command are you calling?
      • Guest124
        chef-client --skip-cookbook-sync
      • coderanger
        What version of chef-client?
      • (chef-client --version)
      • Guest124
        11.12.8
      • Lucky_ABA joined the channel
      • coderanger
        Ahh yeah, that's many years old
      • Guest124
        Oh well! :)
      • is there any alternative for these older versions?
      • coderanger
        Not really, short of hacking up the Chef code itself
      • d^sh joined the channel
      • prg3 joined the channel
      • r3dk1ng has quit
      • troyready has quit
      • cdown has quit
      • cdown joined the channel
      • troyready joined the channel
      • BabyMario joined the channel
      • vish2k8 joined the channel
      • macros has quit
      • EricGonc_ has quit
      • EricGonczer_ joined the channel
      • trip joined the channel
      • trip is now known as Guest59784
      • Guest59784 has quit
      • MattMaker has quit
      • MattMaker joined the channel
      • MattMaker has quit
      • MattMaker joined the channel
      • geggam__ is now known as geggam
      • ranger81 joined the channel
      • astrobunny joined the channel
      • vish2k8 has quit
      • ranger81 joined the channel
      • vish2k8 joined the channel
      • nicolasbock has quit
      • BabyMario has quit
      • EricGonczer_ has quit
      • ranger81 joined the channel
      • spuder joined the channel
      • Guest124 has quit
      • spuder joined the channel
      • spuder has quit
      • mikedodge04 joined the channel
      • astrobunny has quit
      • astrobunny joined the channel
      • biox has quit
      • biox joined the channel
      • astrobunny has quit
      • AllanEspinosa has quit