Windows documentation is broken

Hi guys -

I’m not sure if/when this changed, but when I follow your instructions for
creating a new knife client (
http://wiki.opscode.com/display/chef/Workstation+Setup+for+Windows), it
winds up NOT creating a client.

The first time through, you need to do “knife configure -i” which also means
you need to have a copy of the webui.pem file available as well (locally).

Am I missing something?

Hi Maven,

Thank you for catching that and letting us know!

We wrote the directions assuming users were following our new documentation
on installing Chef Server, which will obviously not always be the case. We
added a note to these directions as well as the ones for Linux and Mac with
an explanation on how to create the admin user. The webui is also an admin
user, so you can feel free to use that if you'd prefer. Please let us know
if you run into any issues with the directions now that they've been
updated.

Thanks,
Jessica

On Thu, Oct 27, 2011 at 2:59 PM, Maven User maven.2.user@gmail.com wrote:

Hi guys -

I'm not sure if/when this changed, but when I follow your instructions for
creating a new knife client (
http://wiki.opscode.com/display/chef/Workstation+Setup+for+Windows), it
winds up NOT creating a client.

The first time through, you need to do "knife configure -i" which also
means you need to have a copy of the webui.pem file available as well
(locally).

Am I missing something?

So how does this work exactly (I'm not any more clear than I was when I
posted before)?

If say, I'm a new hire and I'm going to be working on some recipes, what are
the steps exactly for setting up knife?

On Thu, Oct 27, 2011 at 8:04 PM, Jessica Bourne jessica@opscode.com wrote:

Hi Maven,

Thank you for catching that and letting us know!

We wrote the directions assuming users were following our new documentation
on installing Chef Server, which will obviously not always be the case. We
added a note to these directions as well as the ones for Linux and Mac with
an explanation on how to create the admin user. The webui is also an admin
user, so you can feel free to use that if you'd prefer. Please let us know
if you run into any issues with the directions now that they've been
updated.

Thanks,
Jessica

On Thu, Oct 27, 2011 at 2:59 PM, Maven User maven.2.user@gmail.comwrote:

Hi guys -

I'm not sure if/when this changed, but when I follow your instructions for
creating a new knife client (
http://wiki.opscode.com/display/chef/Workstation+Setup+for+Windows), it
winds up NOT creating a client.

The first time through, you need to do "knife configure -i" which also
means you need to have a copy of the webui.pem file available as well
(locally).

Am I missing something?

Hi Maven,

I'm sorry the documentation wasn't more helpful, please let us know if there
is anything we could improve about it to make it clearer. First, we
recommend creating an admin key by following the steps in the Chef Server
guide:
http://wiki.opscode.com/display/chef/Installing+Chef+Server+Manually#InstallingChefServerManually-CreateaKnifeClientforYourLaptop%252FDesktop

This will walk you through running the command 'knife client create'. For
example entering 'knife client create maven -n -a -f /tmp/maven.pem' on the
Chef Server will create the admin key at /tmp/maven.pem. You'll then want to
copy this key and the validation.pem over to the workstation you are
configuring in the C:\chef.chef directory.

Once this is done, you can follow the workstation guide:
http://wiki.opscode.com/display/chef/Workstation+Setup+for+Windows#WorkstationSetupforWindows-CreateaConfigurationFolder

This will have you run the 'knife configure' command to create the knife.rb.
You will need to enter data here that is specific to your setup, as the
defaults will not work. We updated the wiki page to include an example with
some defaults that you might find helpful.

Thanks,
Jessica

On Thu, Oct 27, 2011 at 7:10 PM, Maven User maven.2.user@gmail.com wrote:

So how does this work exactly (I'm not any more clear than I was when I
posted before)?

If say, I'm a new hire and I'm going to be working on some recipes, what
are the steps exactly for setting up knife?

On Thu, Oct 27, 2011 at 8:04 PM, Jessica Bourne jessica@opscode.comwrote:

Hi Maven,

Thank you for catching that and letting us know!

We wrote the directions assuming users were following our new
documentation on installing Chef Server, which will obviously not always be
the case. We added a note to these directions as well as the ones for Linux
and Mac with an explanation on how to create the admin user. The webui is
also an admin user, so you can feel free to use that if you'd prefer. Please
let us know if you run into any issues with the directions now that they've
been updated.

Thanks,
Jessica

On Thu, Oct 27, 2011 at 2:59 PM, Maven User maven.2.user@gmail.comwrote:

Hi guys -

I'm not sure if/when this changed, but when I follow your instructions
for creating a new knife client (
http://wiki.opscode.com/display/chef/Workstation+Setup+for+Windows), it
winds up NOT creating a client.

The first time through, you need to do "knife configure -i" which also
means you need to have a copy of the webui.pem file available as well
(locally).

Am I missing something?

There are issues here as well:

http://wiki.opscode.com/display/chef/Knife

You can't search for "nodes".

On Thu, Oct 27, 2011 at 11:04 PM, Jessica Bourne jessica@opscode.comwrote:

Hi Maven,

I'm sorry the documentation wasn't more helpful, please let us know if
there is anything we could improve about it to make it clearer. First, we
recommend creating an admin key by following the steps in the Chef Server
guide:
http://wiki.opscode.com/display/chef/Installing+Chef+Server+Manually#InstallingChefServerManually-CreateaKnifeClientforYourLaptop%252FDesktop

This will walk you through running the command 'knife client create'. For
example entering 'knife client create maven -n -a -f /tmp/maven.pem' on the
Chef Server will create the admin key at /tmp/maven.pem. You'll then want to
copy this key and the validation.pem over to the workstation you are
configuring in the C:\chef.chef directory.

Once this is done, you can follow the workstation guide:
http://wiki.opscode.com/display/chef/Workstation+Setup+for+Windows#WorkstationSetupforWindows-CreateaConfigurationFolder

This will have you run the 'knife configure' command to create the
knife.rb. You will need to enter data here that is specific to your setup,
as the defaults will not work. We updated the wiki page to include an
example with some defaults that you might find helpful.

Thanks,
Jessica

On Thu, Oct 27, 2011 at 7:10 PM, Maven User maven.2.user@gmail.comwrote:

So how does this work exactly (I'm not any more clear than I was when I
posted before)?

If say, I'm a new hire and I'm going to be working on some recipes, what
are the steps exactly for setting up knife?

On Thu, Oct 27, 2011 at 8:04 PM, Jessica Bourne jessica@opscode.comwrote:

Hi Maven,

Thank you for catching that and letting us know!

We wrote the directions assuming users were following our new
documentation on installing Chef Server, which will obviously not always be
the case. We added a note to these directions as well as the ones for Linux
and Mac with an explanation on how to create the admin user. The webui is
also an admin user, so you can feel free to use that if you'd prefer. Please
let us know if you run into any issues with the directions now that they've
been updated.

Thanks,
Jessica

On Thu, Oct 27, 2011 at 2:59 PM, Maven User maven.2.user@gmail.comwrote:

Hi guys -

I'm not sure if/when this changed, but when I follow your instructions
for creating a new knife client (
http://wiki.opscode.com/display/chef/Workstation+Setup+for+Windows), it
winds up NOT creating a client.

The first time through, you need to do "knife configure -i" which also
means you need to have a copy of the webui.pem file available as well
(locally).

Am I missing something?

Hi,

On Fri, Oct 28, 2011 at 9:51 AM, Maven User maven.2.user@gmail.com wrote:

There are issues here as well:

http://wiki.opscode.com/display/chef/Knife

You can't search for "nodes".

This should be fixed now.

Cheers,

Steven