Hello Florian, right now the package is the same for all versions of Windows, so what you're doing should work just fine. However, that may not always be the case, so your solution might need to eventually account for that. Is there any way that proxy
servers and proxy config can make this somewhat transparent?
Probably the most likely case for the packages diverging would be omnibus support for 64-bit versions of Ruby — now that 64-bit Ruby on Windows is becoming mainstream (the Ruby Installer for Windows that is commonly used to install Ruby on Windows now
supports a 64-bit version for Ruby 2.0), this is a more feasible proposition for omnibus.
Thanks.
-Adam
From: Florian Hehlen <
">
>
Reply-To: " "> " < "> > Date: Friday, July 12, 2013 3:21 AM To: " "> " < "> > Subject: [chef] version of windows chef client HI,
I am changing the location that knife windows goes to download the client.
Is this: @set "REMOTE_SOURCE_MSI_URL=https://www.opscode.com/chef/download?p=windows&pv=%MACHINE_OS%&m=%MACHINE_ARCH%"
Changing it to: @set "REMOTE_SOURCE_MSI_URL=http://myhost/windows/x86_64/chef-client-11.4.4-2.windows.msi"
Is there any reason to worry about not having separate versions of the msi for all the windows versions and all the architectures. Firstly we only have 64bit machines. Is there any binary difference between the 2008, 2008r2, and 2012 clients?
LEGAL DISCLAIMER
This communication and any attached documents are strictly confidential and/or legally privileged and they may not be used or disclosed by someone who is not a named recipient. If you have received this electronic communication in error please notify the sender by replying to this electronic communication inserting the word "misdirected" as the subject and delete this communication from your system. |
Archive powered by MHonArc 2.6.16.