Skip to main contentdfsdf

  • Feb 14, 12

    Chef vision and interview with founders , explains a bit of comparision with cfengine

    • Cfengine applies resources based on their type – all the files are managed at once, then all the services, then all the packages. You can control the order they are run with the ‘actionsequence’, but each system gets only one order. So if you need to have a file copied, a package installed, and a service restarted, it’s easy enough to model.
    • Convergence is the answer – it’s okay that it has to run more than once, it will get there eventually.

    12 more annotations...

    • If you are a Ruby developer today looking for a fast way to manage the deployment of your Rails application, you should be using Chef. It will provide you with a plethora of options for dropping your application on a server and configuring the required pieces. Tweaking config files alongside your Rails controllers in the same repository is exactly what agile development is all about
  • Feb 14, 12

    Chef basics and quick over view

    • Cloud is API oriented, everything you see in cloud is ulitmately programmable.

       

      Virtualization is the foundation of Cloud but virtualization is not Cloud by itself. It certainly enables many of the things we talk about when we talk Cloud but it is not necessary sufficient to be a cloud. Google app engine is a cloud that does not incorporate virtualization. One of the reasons that virtualization is great is because you can automate the procurement of new boxes.

1 - 12 of 12
20 items/page
List Comments (0)