Friday, Medina, 13:00

• Releases in the past have been essentially drops.
  • With chef 12 this will be a little more open.
  • We have released many repositories
    • A list of repositories will be sent to the mailing list later today
• Is the server group adopting the RFC process? Yes. Everyone in chef is.
• There is a new plugin architecture for addons, can we discuss that more, and how people can make use of it in the community?
  • Addons are conceptually simple
  • In a separate root in /opt
  • Only interaction with chef itself 3 places
    • Config is in /etc/opscode
    • For postgres you can integrate with the enterprise-chef-common cookbook
    • Addons.d for nginx in a specific location (/var/opt/???)
    • This will be documented
• What's the future of pushy?
  • Ongoing work with pushy
  • Upgrading to 0mq 4
  • It will probably just ship with chef server itself, and be open just as part of the chef server.
  • Does it do what we wanted it to do? Yes. It was built mostly to work with the enterprise stuff, which is now open source.
• How easy would it be to implement the Berkshelf API server as an addon?
  • Relatively simple
  • Should probably just be in the chef server, but.
  • If you wanted as an addon, you just add a new endpoint in nginx, and it will have access to the parts it needs (e.g. postgres) as an addon.
• Discussed the repositories for the chef-server and how there are many
  • There is a chef-server repo newly created to help document all of this
  • https://github.com/opscode/chef-server
• API docs are poorly documented
  • We are currently making use of RAML (http://raml.org/) to assist with this, but it will take time.
• Are there plans on what we will be deprecating in future?
  • Not really.
• Is there a future for hosted chef given the new ability to install addons?
  • Yes, hosted is moving to become more like a regular chef-server install rather than its own thing. Of course, you won't be able to install custom addons. Analytics will be there, pushy may be also.
• Discussion on chef-ha and cookbooks
  • There are chef-metal scripts to do so.
  • A few are internal and not quite ready for release but will be once they are.
• Is a tierd topology built in to chef 12?
  • Yes, it's built in to chef 12
  • With open source chef 11, you had to do it manually, but it's now built in as a first class topology in 12.
• Discussed splitting up components - rabbit, solr, postgres on separate servers.
  • Or rather, allowing chef server to access external components rather than splitting up the various components of chef server itself.
  • It's something we might look at doing.
  • There was definite interest in the idea.
  • Most of this would be backend components split up onto separate servers.
  • We can open an RFC on this

• RFC for allowing chef-server to access external components such as rabbit, solr and so on.