If you run your own Open Source Chef Server and want all the benefits of configuration management with none of the adminstration hassle, you can migrate to Hosted Chef without losing the work you've already done. Here's how...
BenefitsAs a Hosted Chef Customer you...
ApproachMigrate by taking the following actions: 1. Prepare your backup.
This will export from the chef server all data bags, roles, environments, and nodes, storing them as JSON files within the .chef/chef_server_backup directory. These JSON files will later be uploaded to Hosted Chef in step 5. 2. Create your accounts and organization on Hosted Chef.See Setup Opscode User and Organization for detailed instructions on creating a new organization. Rather than creating a new, local chef repository, you can reconfigure your current repository to use Hosted Chef.
3. Confirm that your new Opscode Hosted Chef organization has no nodes and just the validator clientThe only client that should be listed is your organization's validator client. No nodes should be listed. 4. Register your existing servers with Hosted ChefUse a custom Knife Bootstrap template to populate the nodes with the correct configuration file and validation certificate, delete the existing client certificate, and run chef-client to register the node as a new API client to the Opscode Hosted Chef Organization. If your nodes are running a Microsoft Windows platform, you will need to use the Knife Windows Bootstrap and modify the template for the Windows platform. Be sure to remove the client.pem file, typically c:\chef\client.pem. Note This assumes, as above, that your Hosted Chef organization has no data for these nodes. The run list will be empty. We will populate that from the backed up node data in a later step. It is important to bootstrap the nodes at this stage before restoring the backup, in order to avoid creating a permissions issue.
5. Upload data to your Hosted Chef organizationYou can restore the node data using a Knife Plugin (backup_restore.rb): Alternatively, can upload the data by hand:
6. Run chef-client on all of your nodesDepending on your environment, this could be done via knife ssh: Questions on the migration?Open a Hosted Chef ticket with any questions or issues encountered, or send an email to support@opscode.com. Need Specialized Assistance?If you have a particularly complex environment, and would like to seek Professional Services assistance, please contact us with your needs and we'll go over the possibilities with you.
|
|
|



1 Comment
comments.show.hideMar 01, 2012
Charles Johnson
Problems uncovered while following this doc: Backup & restore scripts don't cover cookbooks. Document doesn't mention migrating cookbooks, or migrating older cookbooks that may be required by pinned environments.