Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status

RSS

kronos (6) Versions 1.0.1

Kronos manages windows scheduled tasks

Policyfile
Berkshelf
Knife
cookbook 'kronos', '~> 1.0.1', :supermarket
cookbook 'kronos', '~> 1.0.1'
knife supermarket install kronos
knife supermarket download kronos
README
Dependencies
Quality 17%

Description

Manages Windows {2003,2008} Scheduled Tasks via settings stored inside chef data bags.

https://github.com/cixelsyd/cookbooks/tree/master/kronos

Kronos version >= 1.0.1 is a complete re-write for chef-client version 11! Previously, all kronos-managed tasks were completely removed and re-created on each chef run. Now kronos only modifies discrete tasks as appropriate.

Requirements

Windows, Task Scheduler version 1 or 2.

Attributes

Attributes are extremely limited and mostly point at templates. All task configuration information is located inside data bags. See "schedule.rb" attribute file for details.

Usage

Give tasks a name and place their settings into a data bag. Then create another data bag that contains the hostnames of your nodes and attach a comma-delineated list of task names to each node. Kronos will ensure that the tasks are appropriately scheduled on the servers. Additionally, kronos now keeps the working directory clean of all non-active task xml files, so no zombie tasks will get rescheduled if they were previously removed from the host data bag!

Kronos for Windows 2003 is more simplistic than the 2008 version. For Windows 2003, Kronos does not permit "non-managed" tasks, as it deletes all tasks at the beginning of each run. On Windows 2003, if the task does not have the correct data bag entry, it will be deleted by Kronos on the subsequent run. This was for simplicity sake. Kronos for 2003 accepts all the main task scheduler version 1.0 settings; see "create_task.bat.erb" for the command line that is run, and the "schedule.rb" attribute file for additional information.

Kronos for Windows 2008 is slightly more advanced in that it permits "non-managed" tasks to co-exist with Kronos tasks. All tasks that are managed by Kronos have a "kronos-" prefix; this is the primary method of distinguishing between them. Kronos for Windows 2008 currently accepts slightly fewer schedule options than Windows 2003; at the moment they are limited to "minute", "hourly", "daily", "weekly" and "monthly". NOTE! "Monthly" currently means something different for Task Scheduler version 1.0 and 2.0; in Task Scheduler 2.0 it means "once-a-month". The "modifier" setting for "monthly" type tasks represents the number of "the day of the month" on the calendar. Ditto, "weekly" utilizes the "modifier" setting in a crontab-esk manner (0=Sunday, 5=Friday, etc). Other scheduling options will be added at a later date as the task.xml.erb file is expanded. See "schedule.rb" attribute file for details.

Note that task scheduler 2.0 for Windows 2008 is significantly more complicated than version 1.0, hence the mucking about with the registry.

Kronos version >= 1.0.1 now works even better with chef-client version >= 11.6.0! Kronos does not modify tasks unless specifically necessary, and also ensures that any tasks that had been deleted manually from machines are re-created appropriately on the subsequent chef run. Kronos >= 1.0.1 and chef-client >= 11.6.0 are highly preferred!

Dependent cookbooks

reginjector >= 0.1.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

1.0.1 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

1.0.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

1.0.1 failed this metric

FC043: Prefer new notification syntax: kronos/recipes/schedule.rb:211
FC043: Prefer new notification syntax: kronos/recipes/schedule_2008.rb:137
FC064: Ensure issues_url is set in metadata: kronos/metadata.rb:1
FC065: Ensure source_url is set in metadata: kronos/metadata.rb:1
FC066: Ensure chef_version is set in metadata: kronos/metadata.rb:1
FC069: Ensure standardized license defined in metadata: kronos/metadata.rb:1
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric
            

1.0.1 passed this metric

Testing File Metric
            

1.0.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

1.0.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number