chef-dk is chef-client + other chef related tools (berkshelf, test-kitchen,
foodcritic etc). chef-dk also provides the chef command (currently it
provides scaffolding and gem installation [1]). If you are not familiar
with ruby, you might find chef-dk easier to deal with. If you are already
familiar with ruby/bundler it should not matter much (infact you might be
able to get more customized things by raw chef-client + bundler,, i have
painful experience from vagrant's plugin in past ). chef-dk will also
fasten then installation process (since its omnibus), this also means you
have to install it as root, unlike the chef-client which can be installed
as normal user (for development workstations).
thanks all for the clarification.
I was able to install chef-dk and create some sample cookbooks, was able to
upload the same to the chef server.
The thing thats bothering me is that - the workstation does not show up as
a node in the web-ui.
Is this the expected behavior?
Thanks.
On Nov 3, 2014 1:29 PM, "Adam Jacob" adam@getchef.com wrote:
There is also an omnibus chef client. If its a workstation, use chefdk.
On Nov 2, 2014 10:17 PM, "Vikas Roonwal" pvikasroonwal@gmail.com wrote:
Hi,
I have a chef server on a linux machine and want to use a windows machine
to upload cookbooks.
I notice that there are 2 options:
Chef client - it seems to contains items for both client and
workstation
Chef-dk - it seems to contain items related to workstation alone.
I wanted to know if the above understanding is correct?
Also - which would be a better choice since both enable knife and
cookbook related commands.
thanks all for the clarification.
I was able to install chef-dk and create some sample cookbooks, was able
to upload the same to the chef server.
The thing thats bothering me is that - the workstation does not show up as
a node in the web-ui.
Is this the expected behavior?
Thanks.
On Nov 3, 2014 1:29 PM, "Adam Jacob" adam@getchef.com wrote:
There is also an omnibus chef client. If its a workstation, use chefdk.
On Nov 2, 2014 10:17 PM, "Vikas Roonwal" pvikasroonwal@gmail.com wrote:
Hi,
I have a chef server on a linux machine and want to use a windows
machine to upload cookbooks.
I notice that there are 2 options:
Chef client - it seems to contains items for both client and
workstation
Chef-dk - it seems to contain items related to workstation alone.
I wanted to know if the above understanding is correct?
Also - which would be a better choice since both enable knife and
cookbook related commands.
thanks all for the clarification.
I was able to install chef-dk and create some sample cookbooks, was able to
upload the same to the chef server.
The thing thats bothering me is that - the workstation does not show up as a
node in the web-ui.
Is this the expected behavior?
Yes, because your workstation isn't itself being managed by Chef, only
the nodes that are registered with the server are.