chef-boneyard / omnibus-chef-server Goto Github PK

View Code? Open in Web Editor NEW

44.0 59.0 33.0 2.82 MB

Deprecated: Omnibus packaging for Opscode Chef Server (OSC 11.x only).

License: Apache License 2.0

Ruby 38.50% HTML 25.78% CSS 27.93% JavaScript 0.22% Erlang 2.47% Shell 5.10%

omnibus-chef-server's Introduction

Chef Server Omnibus project

This project creates full-stack platform-specific packages for chef-server!

Installation

We'll assume you have Ruby 1.9+ and Bundler installed. First ensure all required gems are installed and ready to use:

$ bundle install --binstubs

Usage

Build

You create a platform-specific package using the build project command:

$ bin/omnibus build project chef-server

The platform/architecture type of the package created will match the platform where the build project command is invoked. So running this command on say a MacBook Pro will generate a Mac OS X specific package. After the build completes packages will be available in pkg/.

Clean

You can clean up all temporary files generated during the build process with the clean command:

$ bin/omnibus clean chef-server

Adding the --purge purge option removes ALL files generated during the build including the project install directory (/opt/opscode) and the package cache directory (/var/cache/omnibus/pkg):

$ bin/omnibus clean chef-server --purge

Cache

Lists source packages that are required but not yet cached:

$ bin/omnibus cache missing

Populate the S3 Cache:

$ bin/omnibus cache populate

Help

Full help for the Omnibus command line interface can be accessed with the help command:

$ bin/omnibus help

Vagrant-based Virtualized Build Lab

Every Omnibus project ships will a project-specific Berksfile and Vagrantfile that will allow you to build your projects on the following platforms:

CentOS 5 64-bit
CentOS 6 64-bit
Ubuntu 10.04 64-bit
Ubuntu 11.04 64-bit
Ubuntu 12.04 64-bit

Please note this build-lab is only meant to get you up and running quickly; there's nothing inherent in Omnibus that restricts you to just building CentOS or Ubuntu packages. See the Vagrantfile to add new platforms to your build lab.

The only requirements for standing up this virtualized build lab are:

VirtualBox - native packages exist for most platforms and can be downloaded from the VirtualBox downloads page.
Vagrant 1.2.1+ - native packages exist for most platforms and can be downloaded from the Vagrant downloads page.

The vagrant-berkshelf and vagrant-omnibus Vagrant plugins are also required and can be installed easily with the following commands:

$ vagrant plugin install vagrant-berkshelf
$ vagrant plugin install vagrant-omnibus

Once the pre-requisites are installed you can build your package across all platforms with the following command:

$ vagrant up

If you would like to build a package for a single platform the command looks like this:

$ vagrant up PLATFORM

The complete list of valid platform names can be viewed with the vagrant status command.

License

See the LICENSE file for details.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

omnibus-chef-server's People

Contributors

Stargazers

Watchers

omnibus-chef-server's Issues

chef-server-ctl reconfigure does not create symlinks for runit

I have installed chef-server on a gentoo system by extracting the debian package (chef-server_11.1.3-1_amd64.deb).

chef-server-ctl reconfigure freezes while waiting for RabbitMQ.

I figured out, that there was no symlinks created for RabbitMQ in /opt/chef-server/service

After creating symlinks for every service from /opt/chef-server/sv as soon as the reconfigure process freezes, i could configure and start chef-server.

Chef server does not rotate NGINX logs

These logs get huge pretty quick and eventually the server crashes when the root drive fills up. Even if you stick them on a larger data drive you can still fill up that drive causing logging to halt. This seems like a really big oversight that should get fixed asap.

Release for security updates needed

We need to review at least our security releases for other products since, but maybe a manifest of software in OSS Server 11, to determine necessary security updates.

OpenSSL
Last release had 1.0.1j, there are at least 14 fixed CVEs between 1.0.1j and 1.0.1m.
PostgreSQL
Last bump was 9.2.9, there are five CVEs fixed in 9.2.10.
Ruby
The Gemfile points to chef/omnibus-software@a08918d, which has ruby 1.9.3-p484 from 2013-11-22. There are surely countless CVEs fixed since then. Ruby 1.9.3-p551 appears to be the latest
Nginx
The Gemfile points to chef/omnibus-software@a08918d, which has nginx 1.4.4. The 1.4 changelog shows 1 CVE fixed in 1.4.7 which was released on 2014-03-18. I don't see a statement about 1.4 being EOL, but it looks like they've stopped shipping it. Ngingx 1.6 has a couple CVE fixes since then. I don't see any subsequent security fixes in Nginx 1.8. We did recently release Chef Server 12.0.8 which included what looks like 8 Nginx security fixes.

Potential issues:

This wasn't building in October? #99
The Gemfile refers to http://www.github.com/opscode/omnibus-ruby, which is gone?
Ruby 1.9.3 is EOL. In the 11.x client we chose to not to upgrade to a newer ruby for CVE-2015-1855 because it would be a lot of work and that CVE isn't a big deal

installing add-ons produces weird output

I'm assuming the string presentation of the class isn't what was intended here... what was?

# chef-server-ctl install chef-ha
.
.
.
Running handlers:
-- Installed Add-On Package: chef-ha
  - #<Class:0x00000003d12df8>::AddonInstallHandler
Running handlers complete```

Can we make nginx listen addresses configurable?

Can we make nginx listen addresses configurable via chef-server.rb config file?

Built-in runit cookbook shouldn't use upstart under docker

Docker has no upstart, it should try to fall back on old schoolz.

Unable to perform a generic database dump with pg_dump

Hi,

Prior to the recent postgres updates in omnibus, I used to be able to perform a backup of my Chef Server's database like this:

/opt/chef-server/embedded/bin/pg_dump -U opscode_chef -c opscode_chef > chef-server.pgsql

Unfortunately, that now results in a few errors:

pg_dump: [archiver (db)] connection to database "opscode_chef" failed: FATAL: no pg_hba.conf entry for host "[local]", user "opscode_chef", database "opscode_chef", SSL off

I can work around that error by specifying a TCP host: /opt/chef-server/embedded/bin/pg_dump --host 127.0.0.1 -U opscode_chef -c opscode_chef > chef-server.pgsql

But that presents a new error:

pg_dump: [archiver (db)] query failed: ERROR:  permission denied for schema sqitch
pg_dump: [archiver (db)] query was: LOCK TABLE sqitch.projects IN ACCESS SHARE MODE

Which I can work around finally by doing:

/opt/chef-server/embedded/bin/pg_dump --host 127.0.0.1 --schema public -U opscode_chef -c opscode_chef > chef-server.pgsql

In IRC, @juliandunn mentioned that this was probably a bug and to file an issue. So here I am!

current master doesn't build

Hey,

I tried to build current master, but had to patch omnibus-software as some checksums and download URLs are outdated. Current omnibus-software master doesn't work out of the box.

Is there any reason chef-server can't be updated to use the latest versions of omnibus and omnibus-software? Are there known blockers?