Ducea.com Website Review

Depending on the size of the databases you have in mysql innodb the time it takes mysql to restart can be horribly slow (for very big innodb databases). There are some tricks that can speed this up, but the most effective one that I’ve found and use all the time in similar situations is to pre-flush the di*ty pages right before shutdown; this can be done like this: Let the server run like this for a while and after you see it settle in, the restart (or stop) should be much faster. love the new features like partial search, chef-apply and knife-essentials inclusions, awesome formatted output, etc. Of course When you are ready to upgrade, you will notice that unfortunately there is no official migration path. This howto will docu*ent what I’ve used myself for such migrations and hopefully will help you too if you are trying to perform a similar upgrade. OPSCODE has done an amazing job with the omnibus installers and starting with Chef 11, the chef server has support for this also. Meaning you can install a new chef server simply by installing the rpm or deb for your platform and everything should be installed for you In order to migrate to a new chef server we need to migrate from the old server: It is important to have all the clients with their proper public keys because if not we would have to re-register each one of them. Personally, I’ve migrated using this process several servers from open source chef 0.10.x to chef 11, but theoretically this should work from any chef server implementation (hosted, private, etc.) because we are do*nloading and uploading the as*ets using the api calls. While working on migrating a chef server from 0.10.x to version 11, I ended up extending the BackupExport KNIFE-BACKUP will backup all cookbook versions available on the chef server. Cookbooks are normally available in a repository and should be easy to upload like that, but if you are using various cookbook versions in each environment then it might not be so trivial to find