holms / chef-starter Goto Github PK

It's better make this a requirement for a while. Just for non-interrupting setup.

If you changed any of your cookbooks in Berksfiles, changes will be ignored while Berksfile.lock file present.

Move all site-cookbooks, roles, nodes to repo dir, which will be ignored.

Purpose is to use it as git repo, so you could store your deployment in your git repo.

I've misunderstood concept of chef again..

You can't just upload nodes configs to chef-server, because nodes state will be reset. And this is critical in some situations. For example, let's take a cookbook called "chef-logstash" which is created by lusis. It's heavily relies on nodes state. So if you have spinning cron jobs on your nodes, which will run chef-client periodically, there's a big chance that recipe will fail to execute. During that time when you uploaded your node config (resets a state), logstash::agent cookbook will try to find IP of logstash::server node, and it will fail, because state is empty.

This can be fixed by adding plugin of with knife plugin which provides knife node update command. or exporting node by hand, and merging it with current node config, in some /tmp dir, and upload it back.

http://stackoverflow.com/questions/20119427/how-can-i-update-state-of-node-instead-of-overwriting-it

Duplicate: #25

Yeap, I don't have any freaking idea what's going on. I've completely removed all possible chef file from file system. Yet it fails to find that command on reinstall. RPM installation probably fails to put in in there.. this needs investigation.

For now just rebuild your vm.

Because, if the file will exist with same name, Makefile will fail

probably will just add $CHEF_NODE_USERNAME to .makerc

Search for .make.lock file when executing make install, abort action if found with message to remove a lock.

make cook action for bootstraping all nodes in nodes folder, this will also execute
make update action

Currently echo is used. sed would be better, as it could just patch /etc/sudoers file, adding NOPASSWD to sudo group line.

Tried to add passwordless policy to /etc/sudoers with ssh execute. But it failed with error sorry, you must have a tty to run sudo

point is to wipe cookbooks, roles, envs, completely, because after you'll modify your costume book,, or version was bumped by books author,, you'll endup using old cookbook. which is probably you don't want to

moved ssh key installation steps to install_ssh_key target. Put it before destroy target

have an issue with knife [env/role/node] from file *

from command line it works, from makefile it doesn't, although by one file it works.

this will solve update issues

Great tool for testing cookbooks!!!

https://github.com/test-kitchen/

http://stackoverflow.com/questions/20119427/how-can-i-update-state-of-node-instead-of-overwriting-it

Should be "Node FQDN: "

Cooks a node which you specify yourself.

Need to find out how to make knife, append new configuration to current one in .chef/knife.rb. because default path'es are /var/chef/

This breaks all repo structure.

created node template from knife node create myhostname proposed template

forgot to add creds for knife-bootstrap, also --sudo param

we need default template in feature so renaming it.

• Removing node from client list
• Removing node from node list
• Removing chef-client keys from node
• Bootstrap chef-client

For now everything executes, one by one. It's quite hard to follow.

because cook-all is risky to use anyway so, not gonna be used regularly

...Or else empty generate Berksfile won't be copied with Berksfile.sample.