[chef] RE: Chef repository usage...


Chronological Thread 
  • From: "Sullivan, Jon Paul" < >
  • To: " " < >
  • Subject: [chef] RE: Chef repository usage...
  • Date: Mon, 23 Jul 2012 10:32:58 +0000
  • Accept-language: en-IE, en-US

I really like knife-essentials for uploading to a chef server.  It gives you the “knife upload” command that just pushes up what is different in your VCS.

 

https://github.com/jkeiser/knife-essentials

 

 

From: Morgan Blackthorne [mailto:
Sent: 23 July 2012 05:54
To:
Subject: [chef] Chef repository usage...

 

Still getting up to speed with chef. I know that most people suggest putting the Chef configuration into a VCS like SVN/Git/etc, but what I'm not clear about is what files should be put into the repo and uploaded (say with shef or knife) and what should only exist on the chef server. For day to day operations, do you suggest using shef to edit and test configurations, and then download the files into the VCS repo to archive, or should everything be done through the VCS repo and pushed to the chef server via knife for testing?

 

Is there a knife command that will take a full (properly formatted) directory structure and upload it to chef in one go, or do you have to upload everything individually?

 

Thanks for the help.


~*~ StormeRider ~*~

"With hearts immortal, we stand before our lives
A soul against oblivion, forever asking why
This upside down symphony in a paradox called life
Our hearts immortal
What you give to love, will never die"

 

 

 

Thanks,
Jon-Paul Sullivan J Cloud Services - @hpcloud

 

Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway.

Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John Rogerson's Quay, Dublin 2.

Registered Number: 361933

 

The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender.

 

To any recipient of this message within HP, unless otherwise stated, you should consider this message and attachments as "HP CONFIDENTIAL".

 




Archive powered by MHonArc 2.6.16.

§