Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: run against a real chef server #184

Closed
rj-reilly opened this issue May 27, 2018 · 4 comments
Closed

Feature Request: run against a real chef server #184

rj-reilly opened this issue May 27, 2018 · 4 comments
Labels
Type: Enhancement Adds new functionality.

Comments

@rj-reilly
Copy link

rj-reilly commented May 27, 2018

From the documentation it looks like chef-workstation only runs against local cookbooks:

 <RECIPE>          The recipe to converge. This can be provided as one of:
                    1. Full path to a recipe file
                    2. Cookbook name. First we check the working directory for this
                       cookbook, then we check in the chef repository path. If a
                       cookbook is found we run the default recipe.
                    3. This behaves similarly to 'cookbook name' above, but it also allows
                       you to specify which recipe to use from the cookbook.

It would be awesome to also be able to use against a chef server, i think it would only work against already bootstrapped nodes, unless workstation is modified to also have the ability to bootstrap. I know there is knife ssh but i think chef workstation is a better interface and the idea of a inventory file to come is great for orchestration. we currently do this with ansible as i have found it easier to use than knife ssh for our use case for blue green deployments.

@cheeseplus
Copy link

As we think about how we re-frame interactions in the context of Workstation we've definitely had the same thought. The challenge here is to align it with or supplant other tooling while still keeping a targeted focus on simplicity, usability, and safety (guiding principles of this initiative). Which is to say this is a good one and we're already thinking about how to do this best.

@rj-reilly rj-reilly reopened this May 27, 2018
@robbkidd
Copy link
Contributor

🤔

@rj-reilly In the meantime, can you share more of your thoughts? In what ways do you find chef-run a better interface than knife ssh for initiating a chef-client run on multiple hosts already managed with a Chef Server?

@rj-reilly
Copy link
Author

@robbkidd I guess two things one is the hostname globbing, second is not having to execute a search when I am trying to put our blue cluster in to production and remove our green, again currently we do this with ansible ( which pains me ) but we have found it to be faster sans the lookup. I am sure there are knife ssh options i may be missing, but i saw the demo at chef conf started playing around with chef-run and liked it.

@cheeseplus
Copy link

Moved/combined into chef/chef-apply#41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Adds new functionality.
Projects
None yet
Development

No branches or pull requests

4 participants