CDP Meeting 7 February 2012
Current responsibilities
1)Deploying drupal code to both pre-production and production environments using CI to progress each release through the environments.
2)Creating and maintaining scripts (in rake/ruby) to support developers. e.g. automating drupal installation steps, building software from multiple repositories.
3)Creating and maintaining a Vagrant image for use by developers as an environment which matches the production environment as far as possible within a single machine.
4)Creating and maintaining a puppet configuration management system to enable ITV's goals of configuration documentation as code.
5)Providing architectural oversight for development efforts to ensure that solutions meet ITV's quality goals and will function as expected.
6)Miscellaneous op's type tasks (configuring new servers, managing resource allocation across Vmware, user management in Stage).
7)Providing support to developers in debugging application level issues in a complex environment.
8)Performance testing and tuning of the LAMP stack.
9)Building a CI pipeline to support the itvPlayer development
10)Building a CI pipeline to support the MxM/NSW project.
Proposal
1)Drop all BAU ops responsibilities – we are not an ops team. We have identified the following issues (logged in jira) that need to be resolved in order to hand over this function to ops: WAF-777, WAF-772, WAF-771, WAF-769, WAF-764, WAF-763, WAF-761, WAF-758, WAF-757.
2)Formalise the CDP's role in the development teams. We would like to be part of any decisions that are made that affect the production environment as currently changes are announced after they have been implemented and my team is then put under pressure to deploy systems that we do not think are in ITV's best interests.
3)Assume the role of release management for ITV. This has already happened for the Bodoni project, and we have a Drupal resource for this. We expect to take over this function from Tag1 presently for the Player project. It makes sense for us to own this responsibility for the entire technology stack, but currently do not have the resource for this.
4)