Switch to Policyfile #78

Closed
opened 2019-07-04 09:39:54 +00:00 by greg · 5 comments
Owner

knife-solo is deprecated (https://github.com/matschaffer/knife-solo), and I have just had an issue with an old attribute being persisted into the node file for barnard in my home directory on barnard (~/chef-solo/nodes/barnard.kosmos.org.json) that was hard to figure out

A Policyfile is an optional way to manage role, environment, and community cookbook data with a single document that is uploaded to the Chef Infra Server. The file is associated with a group of nodes, cookbooks, and settings. When these nodes perform a Chef Infra Client run, they utilize recipes specified in the Policyfile run-list.

https://docs.chef.io/config_rb_policyfile.html

We might be able to use chef-run together with Policyfile to replicate our current knife-solo setup

knife-solo is deprecated (https://github.com/matschaffer/knife-solo), and I have just had an issue with an old attribute being persisted into the node file for barnard in my home directory on barnard (`~/chef-solo/nodes/barnard.kosmos.org.json`) that was hard to figure out > A Policyfile is an optional way to manage role, environment, and community cookbook data with a single document that is uploaded to the Chef Infra Server. The file is associated with a group of nodes, cookbooks, and settings. When these nodes perform a Chef Infra Client run, they utilize recipes specified in the Policyfile run-list. > > https://docs.chef.io/config_rb_policyfile.html We might be able to use [chef-run](https://www.chef.sh/docs/chef-workstation/chef-run-users-guide/) together with Policyfile to replicate our current knife-solo setup
Author
Owner

In my experience chef-run is far from ready: error messages are cryptic, I can't find a way to set a policy group (replaces environments) or to load data bag items, which is a deal breaker

Policyfile seem to be well supported when using Chef Server by now, but without one it is hard to work with. I would put this issue on hold until a tool that supports Policyfiles without a Chef Server is released, because running Chef Server for only two servers is overkill.

In my experience `chef-run` is far from ready: error messages are cryptic, I can't find a way to set a policy group (replaces environments) or to load data bag items, which is a deal breaker Policyfile seem to be well supported when using Chef Server by now, but without one it is hard to work with. I would put this issue on hold until a tool that supports Policyfiles without a Chef Server is released, because running Chef Server for only two servers is overkill.
raucao added this to the (deleted) milestone 2019-09-09 10:21:32 +00:00
Owner

OK. Created an icebox milestone for things on hold.

OK. Created an icebox milestone for things on hold.
greg changed title from Switch to Policyfile, replace knife-solo to Switch to Policyfile 2019-10-11 09:20:11 +00:00
greg removed this from the (deleted) milestone 2019-10-11 09:20:21 +00:00
Author
Owner

I have removed this one from the Icebox and changed its title, Knife-Zero supports Policyfile: https://knife-zero.github.io/tips/with_policyfile/

I have removed this one from the Icebox and changed its title, Knife-Zero supports Policyfile: https://knife-zero.github.io/tips/with_policyfile/
raucao added the
ops
label 2020-11-23 12:02:54 +00:00
Owner

@greg Is this issue still relevant in your opinion?

@greg Is this issue still relevant in your opinion?
Author
Owner

I think we can close this one, I haven't looked at Policyfiles since then. We can always reopen it if we feel the need to investigate again

I think we can close this one, I haven't looked at Policyfiles since then. We can always reopen it if we feel the need to investigate again
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#78
No description provided.