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

Pyload Chef cookbook reference to README #2578

Open
wants to merge 2 commits into
base: stable
Choose a base branch
from

Conversation

djessich
Copy link

In past three weeks I have created a Pyload Chef Cookbook available here https://github.com/gridtec/cookbook-pyload. It is tested on different platforms, such as Debian, Ubuntu, Redhat, CentOS, Fedora and OpenSUSE and it supports ArchLinux. It is testd on TravisCI. It is already released in version 1.0.0 to the Chef Supermarket.

As I think that the cookbook should be referenced in the Pyload project, I added a reference to README. While I was working on that, I've also rewritten the README to markdown style and updated the domain in it (would also fix #2574).

@vuolter vuolter added the enhancement New feature or bugfix label Oct 19, 2016
@vuolter vuolter added this to the 0.5.x milestone Oct 19, 2016
@AxeMax
Copy link

AxeMax commented Dec 12, 2016

This cookbook-approach is new to me. Sounds interesting.
Is there an advantage over DEB/RPM-Packages? Does it work for Windows/MacOS?

@djessich
Copy link
Author

djessich commented Dec 15, 2016

@Burnout5151:
Well, Chef its another way of doing things. A DEB or RPM package installs a package only for one platform (Debian or RedHat in that case) in one specific version and that's it. The packages inner layout are not equal, they are different for different OS, so you need to create packages for each platform.

Whereas Chef focuses on whole infrastructure automation, a Chef cookbook offers the possibility to automatically install and maintain whatever the cookbook does (in this case install and maintain Pyload) for multiple OS (if the cookbook supports multiple OS) using a single source. You can decide if you execute the cookbook just once, to install Pyload, or to execute it occasionally, to install Pyload and maintain the installation, which means "hold it in that state, it has been described in the Chef cookbook". The latter would mean, if something is changed (f.e. the sys-v-init script), it will be reset by the Chef cookbook into the original state.

Moreover, Chef provides you the ability to do standard system operations together with usual development standards (so called DevOps approach), such as testing (f.e. does a configfile has the content it should have?), version management, etc. With a single (or multiple) bash script this may also work, but f.e. testing in bash is rather limited (as far as I know) and also, it is not OS transparent (see above), as you can see with the provided sys-v-init scripts in the Pyload cookbook.

More info on Chef can be found in the official documentation at https://www.chef.io/.

To answer your second question: Chef ships with Windows and MacOS support, but the cookbook I've written does not support them. Well, thats not the major problem, as the support for Windows or MacOS could be added to the cookbook.

@djessich
Copy link
Author

I've worked on some improvements of the cookbook and I've added support for FreeBSD 10+. So the cookbook will work now on the following platforms: ArchLinux, Debian, Ubuntu, CentOS, RedHat, Fedora, OpenSUSE and FreeBSD.

@djessich
Copy link
Author

djessich commented Dec 21, 2016

As @Burnout5151 mentioned, there has been activity on the 1.0.0 branch. If @vuolter declares version 1.0.0 useable, I will make the cookbook compatible to it as soon as possible. Could we also reference the Pyload Chef cookbook in version 1.0.0 then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or bugfix
Development

Successfully merging this pull request may close these issues.

Update domain in Readme
3 participants