cwebberOps

+----------------+------+---------+---------+-------+
|       OS       | INIT | SYSTEMD | UPSTART | RUNIT |
+----------------+------+---------+---------+-------+
|                |      |         |         |       |
| CentOS 5       | X    |         |         | X     |
|                |      |         |         |       |
| CentOS 6       | X    |         |         | X     |
|                |      |         |         |       |
| CentOS 7       | X    | X       |         | X     |
|                |      |         |         |       |

cwebberOps

2014-08-12 - Dependency API Issues - Community

Start every PM stating the following

1. This is a blameless Postmortem.
2. We will not focus on the past events as they pertain to "could've" "should've"...
3. All follow up action items will be assigned to a team/individual before the end of the meeting. If the item is not going to be top priority leaving the meeting, don't make it a follow up item.

Incident Leader: Christopher Webber

cwebberOps

2014-07-14 - Berkshelf Protocol Mismatch - Community

Start every PM stating the following

1. This is a blameless Post Mortem.
2. We will not focus on the past events as they pertain to "could've" "should've"...
3. All follow up action items will be assigned to a team/individual before the end of the meeting. If the item is not going to be top priority leaving the meeting, don't make it a follow up item.

Incident Leader: Christopher Webber

cwebberOps

2014-07-08 - Supermarket Unresponsive - Community

Start every PM stating the following

1. This is a blameless Post Mortem.
2. We will not focus on the past events as they pertain to "could've" "should've"...
3. All follow up action items will be assigned to a team/individual before the end of the meeting. If the item is not going to be top priority leaving the meeting, don't make it a follow up item.

Incident Leader: Christopher Webber

cwebberOps

2014-07-08 - Berkshelf v2 Outage - Community

Start every PM stating the following

1. This is a blameless Post Mortem.
2. We will not focus on the past events as they pertain to "could've" "should've"...
3. All follow up action items will be assigned to a team/individual before the end of the meeting. If the item is not going to be top priority leaving the meeting, don't make it a follow up item.

Incident Leader: Christopher Webber

cwebberOps

Commit All The Things! - A Guide to Managing Pull Requests

Assumptions

• All spec and kitchen tests have been added as needed
• Code itself has been reviewed and verified
• hub and stove are in use

Merging

Use the squash command below to merge the request onto the master branch.

cwebberOps

if node[:platform] == 'ubuntu'
  an_provider = Chef:Something:Upstart
else
  an_provider = nil
end

service 'sshd' do
  provider an_provider
  action [:enable, :start]
end

cwebberOps

As we setup our rails environment we added the following to our schema.rb:

  enable_extension "plpgsql"
  enable_extension "pg_trgm"

As we move to prod the reality is that enabling those extensions requires a super user. How do people handle this kind of migration in Prod? Is it done separate from the schema.rb?

And if it is done separate how do you handle it in tests? Just not sure where to go with this...

cwebberOps

class 'foo' {

  file { '/foo':
    ensure => present
  }
  
  service { 'foo':
    ensure => running
  }
  

cwebberOps

file {
  '/path':
    ensure => directory;
  '/path/to':
    ensure => directory;
  '/path/to/file':
    ensure => present,
    content => template('modulename/file.erb');
}