{"comment":{"created_at":"2011-10-23T23:23:21Z","body":"By this we mean that all definitions *begin* in the git repo -- everything in the chef server or AWS is either\r\n\r\n* configuration, which came from something in the cluster definitions, cookbooks etc.\r\n* intrinsic status reported by machines themselves\r\n\r\nWe store as little as possible in the AWS info -- there's some work required to remove the dependencies (#28) but there's nothing essential.","updated_at":"2011-10-23T23:23:21Z","url":"https://api.github.com/repos/infochimps/cluster_chef/issues/comments/2498501","id":2498501,"user":{"avatar_url":"https://secure.gravatar.com/avatar/99df54e24a1bed7d0edb6c51e7010d17?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"99df54e24a1bed7d0edb6c51e7010d17","url":"https://api.github.com/users/mrflip","id":6128,"login":"mrflip"}},"action":"created","issue":{"number":52,"created_at":"2011-09-28T17:53:39Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"The README.textile indicates that cluster_chef is recording data in git.  From what I've found, role information is currently stored and queried in AWS server properties and merged with config settings (at least for knife, I assume the same is done for cluster_chef in general).\r\n\r\nSpecifically:\r\n\r\n<pre>\r\n* *Chef server is never the repository of truth* -- it only mirrors the truth.\r\n  - a file is tangible and immediate to access\r\n* Specifically, we want truth to live in the git repo, and be enforced by the chef server. *There is no truth but git, and chef is its messenger*.\r\n  - this means that everything is versioned, documented and exchangeable.\r\n* *Systems, services and significant modifications cluster should be obvious from the `clusters` file*.  I don't want to have to bounce around nine different files to find out which thing installed a redis:server.\r\n  - basically, the existence of anything that opens a port should be obvious when I look at the cluster file.\r\n</pre>\r\n\r\nis this planned or is this approach discarded?  It would be very nice for cluster_chef to allow the state of a cluster at a point in time to be seen via git or some other dvcs since it would allow for the state of a cluster to be materialized and monitored from anywhere, not just via AWS tools, and without any aws authentication artifacts (keys, ids, etc.).","comments":1,"title":"README.textile appears to be different from the implementation","updated_at":"2011-10-23T23:23:21Z","url":"https://api.github.com/repos/infochimps/cluster_chef/issues/52","id":1766665,"assignee":null,"milestone":null,"closed_at":"2011-10-23T23:23:21Z","user":{"avatar_url":"https://secure.gravatar.com/avatar/7c7a3ee995b5aabbf43034f88aaf2ead?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"7c7a3ee995b5aabbf43034f88aaf2ead","url":"https://api.github.com/users/pcn","id":1056756,"login":"pcn"},"html_url":"https://github.com/infochimps/cluster_chef/issues/52","labels":[],"state":"closed"},"legacy":{"issue_id":1766665,"comment_id":2498501}}