[[chef-dev]] Automated testing for Chef Server/Client installs


Chronological Thread 
  • From: Sergio Rubio < >
  • To:
  • Subject: [[chef-dev]] Automated testing for Chef Server/Client installs
  • Date: Fri, 6 May 2011 17:29:08 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=AHOD72GWKwcACDg1oTIPHaabjysW4ibId2M47/xna0CNeafd5U4kdtDIkkqsG9mgY+ YT/1lqSWD78S86mO4i1Y8Dm+lAMABSW98xij2Sbqx4jdV6os9yg60zv8Yhtv/dOtI2+h 6IXeHjTDNosQMDkKpn3Maambaq84BMNgKhV94=

Hey all,

I'm gonna start writing some tests to QA RPM Chef client/server installs to ensure a minimum level of quality for the RBEL Chef packages.

Do you guys have something to share that I could reuse?

My plan is to:

1. Use Vagrant boxes to setup multi arch/version CentOS/FrameOS installs
2. Use a cookbook to install a Chef server from RBEL packages
3. Bootstrap a few Vagrant multi arch/version CentOS/FrameOS nodes
4. Add some official cookbooks to the nodes run_list
5. Print OK if everything is cool :)

Any suggestion is greatly appreciated.

Thanks!

--
Sergio Rubio

FrameOS Linux
http://www.frameos.org
twitter:   @rubiojr
blog:      http://blog.frameos.org


  • [[chef-dev]] Automated testing for Chef Server/Client installs, Sergio Rubio, 05/06/2011

Archive powered by MHonArc 2.6.16.

§