Should we use a single GitHub repository for Chef cookbooks? Or one GitHub repository per cookbook? Why choose one or the other approach in a give situation? What are the potential benefits and tradeoffs? Does anybody really know? Are we over-thinking this issue? Maybe we all should take a deep breath, tear our hair out, throw Chef under the bus and just write fu#king shell scripts!
Speaking simplistically, organizations tend to move towards DevOps in either of two ways...
Job titles are important because they describe what we do, which shapes our identity and guides our activity. It's important that job titles are rational and make sense. If they don't, it causes confusion and stress for individuals, teams, and organizations.
We built Bitlancer Strings originally to run on Rackspace Cloud. While we can support customers running in other cloud environments, Strings is more ideal for a persistent environment like Rackspace.
We blogged recently about Puppet-as-a-Service and what that gives you, in terms of automation on one end of the spectrum and insight/control on the other. In this post I want to drill down into infrastructure orchestration, which is part of what you get with the Bitlancer Strings' "Puppet-as-a-Service" approach to cloud automation.