Berkself has a nofreeze option iirc it does not bump the version....are u using knife-spork?
On Jun 5, 2013 10:26 AM, "Morgan Blackthorne" < > wrote:Hacking internals isn't what I want. :)Any ideas on the Berkshelf reuploading without a version change? Is there a config setting to alter that behavior, perhaps?
On Wednesday, June 5, 2013, Ranjib Dey wrote:
no. but its ruby so there must be a way to hack it (which will involve tampering core chef's classes/modules) to do what you wantOn Wed, Jun 5, 2013 at 10:11 AM, Morgan Blackthorne < > wrote:
I'm assuming that the cookbook metadata can't be overridden like resources can?
On Wednesday, June 5, 2013, Ranjib Dey wrote:
there are no clear solution right now. this issue have been discussed previously , specifically in context of platform specific cookbooks. Currently chef does not have support for conditional cookbook dependency. So even if a parent cookbook conditionally uses a dependent cookbook , it has to declare this in its metadata. iirc it was suggested in certain cases the cookbook author can skip enlisting those conditional cookbooks as dependency in metadata and it was also assumed that the user will have an understanding of this, and will assign those conditional cookbooks explicitly in the node's run list when they need them. but i dont think we can generalized these approach for all cookbooks.On Wed, Jun 5, 2013 at 9:49 AM, Morgan Blackthorne < > wrote:
I'm only using a handful of cookbooks directly, but my berkshelf list is large. Pulling in Apache2 and Nginx adds in a lot of dependencies, one of which is perl, and one of the Java cookbooks ends up pulling in Gnome and X-windows. One of the chef cookbooks (chef-client?) pulls in Windows. These are all headless Linux instances without X installed (and I'd like to keep it that way, heh).When the run list is compiled and the cookbooks are sent to the client, they end up transferring a lot of cookbooks that never end up actually getting used. And if I touch any of the higher level cookbooks (like the one for my org that configures some things via LWRPs and overrides some cookbook resources), berkshelf then has to parse the list of all those dependencies as well just to upload my local cookbook. I even tried using a group to filter things down but dependencies are resolved even when using groups. Berks also seems to re-upload every cookbook even if the version number hasn't changed, which is odd to me. (Fixing that would minimize at least some of the annoyance factor of how long "berks upload" takes.)Is this just a situation where "deal with it" is the most practical advice, or is there a way to break some of these dependencies that I know aren't going to be reached in my use case (like the gnome and windows cookbooks...)?
--
--~*~ StormeRider ~*~"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."(from Smallville Season 6x1: "Zod")
On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
--
--~*~ StormeRider ~*~"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."(from Smallville Season 6x1: "Zod")
On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
Archive powered by MHonArc 2.6.16.