Call for testing: Ubuntu / Debian packages for Chef 0.8

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ohai, Chefs!

We are planning to release the Chef 0.8.x Debian/Ubuntu packages on
the Opscode APT repository (apt.opscode.com) “Real Soon Now”. The
current version 0.8.10, but subject to change.

This may be a breaking change for people using the repository for Chef
version 0.7.16 due to authentication changes in 0.8.x0.

The 0.8 packages are currently in a Launchpad PPA, for testing on
Ubuntu Lucid and Karmic, to keep them separate from our official APT
repo. We would like upgrading to be as painless as possible, so we are
soliciting feedback for new installations or upgrades with these
packages.

https://launchpad.net/~jtimberman/+archive/opschef/+packages

Clients:

 sudo apt-get install chef

Server:

 sudo apt-get install chef chef-server

The package chef-server-webui provides the WebUI, and is optional in
0.8. You’ll need to specify it to install as well if you want to use it.

There are a lot of improvements to the packaging from v0.7.16. Please
see the complete list of the changes in the packaging from earlier
versions in the Debian changelog:

http://github.com/opscode/opscode-packages/raw/master/debian/chef/debian/changelog

We’re looking for issues with the packaging itself - packaging
specific configuration or the init/postinst scripts, dependency
management, etc. Note that the various Chef daemons are configured to
log in /var/log/chef.

Thanks!


Opscode, Inc
Joshua Timberman, Senior Solutions Engineer
C: 720.334.RUBY E: joshua@opscode.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iEYEARECAAYFAkvF6ikACgkQO97WSdVpzT3GFACdHy6gJrnfEwGhyxVatrb/QlDa
Z1kAnjcT/QtNjxAg6/1lHDruzsuRozFd
=OnAF
-----END PGP SIGNATURE-----

On Wed, Apr 14, 2010 at 5:15 PM, Joshua Timberman joshua@opscode.com wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ohai, Chefs!

We are planning to release the Chef 0.8.x Debian/Ubuntu packages on the
Opscode APT repository (apt.opscode.com) "Real Soon Now". The current
version 0.8.10, but subject to change.

FANTASTIC!!!

Many thanks, will be testing tomorrow.

Is there any specific testing framework you would like me to adhere
too? Or is it just a free for all to see what breaks? :slight_smile:

Joel

--
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'

I'll test the Debian packages. Thanks for making them!

-lee

On Wed, Apr 14, 2010 at 1:01 PM, Joel Merrick joel.merrick@gmail.com wrote:

On Wed, Apr 14, 2010 at 5:15 PM, Joshua Timberman joshua@opscode.com wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ohai, Chefs!

We are planning to release the Chef 0.8.x Debian/Ubuntu packages on the
Opscode APT repository (apt.opscode.com) "Real Soon Now". The current
version 0.8.10, but subject to change.

FANTASTIC!!!

Many thanks, will be testing tomorrow.

Is there any specific testing framework you would like me to adhere
too? Or is it just a free for all to see what breaks? :slight_smile:

Joel

--
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'

--


Lee Azzarello
drop.io staff hacker

Client notes:

Thought I would throw a few notes out there for everyone, as I have been using timbermans ppa for a few weeks now on 8.x, hope this helps someone out.

I used the debconf-utils package for the seed file, so you might need to apt-get that if you dont have it already

python-software-properties is the easiest way to use the ppa

apt-get install python-software-properties debconf-utils

I was scripting this on a bunch of servers so I needed to seed the servers in

update mychefserver.com with your actually chef server

echo < chef.seed

URL of Chef Server (e.g., http://chef.example.com:4000):

chef chef/chef_server_url string http://mychefserver.com:4000
EOF

sudo debconf-set-selections < chef.seed

sudo add-apt-repository ppa:jtimberman/opschef

remove old chef client

sudo apt-get purge chef

update to pickup new chef from ppa

sudo apt-get update

install chef

sudo apt-get install chef

copy your validation.pem from chef server to /etc/chef

I was unable to get this to work

so I used knife on the chef server

knife client create <server_fqdn> -f <server_fqdn>.pem

I put this on a common nfs share to all my servers <example user home :slight_smile: >

copy it to /etc/chef/client.pem on your system.

make sure it all works

sudo chef-client

#use knife or ui to edit your clients.

On Apr 14, 2010, at 9:15 AM, Joshua Timberman wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ohai, Chefs!

We are planning to release the Chef 0.8.x Debian/Ubuntu packages on the Opscode APT repository (apt.opscode.com) "Real Soon Now". The current version 0.8.10, but subject to change.

This may be a breaking change for people using the repository for Chef version 0.7.16 due to authentication changes in 0.8.x0.

The 0.8 packages are currently in a Launchpad PPA, for testing on Ubuntu Lucid and Karmic, to keep them separate from our official APT repo. We would like upgrading to be as painless as possible, so we are soliciting feedback for new installations or upgrades with these packages.

https://launchpad.net/~jtimberman/+archive/opschef/+packages

Clients:

sudo apt-get install chef

Server:

sudo apt-get install chef chef-server

The package chef-server-webui provides the WebUI, and is optional in 0.8. You'll need to specify it to install as well if you want to use it.

There are a lot of improvements to the packaging from v0.7.16. Please see the complete list of the changes in the packaging from earlier versions in the Debian changelog:

http://github.com/opscode/opscode-packages/raw/master/debian/chef/debian/changelog

We're looking for issues with the packaging itself - packaging specific configuration or the init/postinst scripts, dependency management, etc. Note that the various Chef daemons are configured to log in /var/log/chef.

Thanks!


Opscode, Inc
Joshua Timberman, Senior Solutions Engineer
C: 720.334.RUBY E: joshua@opscode.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iEYEARECAAYFAkvF6ikACgkQO97WSdVpzT3GFACdHy6gJrnfEwGhyxVatrb/QlDa
Z1kAnjcT/QtNjxAg6/1lHDruzsuRozFd
=OnAF
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Apr 14, 2010, at 11:01 AM, Joel Merrick wrote:

Is there any specific testing framework you would like me to adhere
too? Or is it just a free for all to see what breaks? :slight_smile:

I don't have any specific framework, just a general workflow.

  • Install the packages.
  • Verify everything starts up, service names:
    chef-client
    chef-server
    chef-solr
    chef-solr-indexer
    chef-server-webui (if installed)
    rabbitmq-server
    couchdb
  • Check that the client was able to register using the validation.pem
  • Generate a knife client config
  • Interact with the API via knife (upload cookbooks, roles, add to a
    node run list, verify knife search works, etc)
  • Log into the webui if its installed
  • Anything else you can think of :-).

Note that on package installation for some of the init scripts, they
say the service failed to start when it actually didn't. The scripts
need a bit of tweaking to properly detect the PID vs the command-line
of the running process, because the names change on startup.


Opscode, Inc
Joshua Timberman, Senior Solutions Engineer
C: 720.334.RUBY E: joshua@opscode.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iEYEARECAAYFAkvGPnMACgkQO97WSdVpzT3WWQCeKzHMyTpJGchZitHwLkW3CpD1
GucAn1fHhGhJRB1PZkZPBnpuq/YyPMnZ
=2sy0
-----END PGP SIGNATURE-----

On Wed, Apr 14, 2010 at 1:03 PM, Joshua Miller jassinpain@gmail.com wrote:

apt-get install python-software-properties debconf-utils

I think you only need debconf-utils if you're playing with
'debconf-get-selections' to test debconf.

echo < chef.seed

URL of Chef Server (e.g., http://chef.example.com:4000):

chef chef/chef_server_url string http://mychefserver.com:4000
EOF

sudo debconf-set-selections < chef.seed

FWIW, you can omit the temporary file:

echo "chef chef/chef_server_url string
http://mychefserver.com:4000" | debconf-set-selections

Bryan