Config Management Initiative

Configuration Management Initiative

This page collects content for those interested in being involved in the Configuration Management Initiative for Drupal 8. Hopefully this page will be able to provide a high level status of the various activities surrounding the initiative including

  • Highlighted Discussions - Open discussions on architecture issues or high-level interesting topics
  • Detailed Plans - Game plan proposals with more implementation details
  • Associated Issues - Issues from d.o related to parts of the initiative

In the future I can see this as a place where, for instance, we might tag issues and/or discussions with a particular sprint for tracking purposes and the like. All work is going to be done in the core sandbox project for the initiative. Right now this is pretty dead. There is a branch for UUID support but work has not begun yet. If you are interested, please provide feedback on the game plan listed below!

This page is a work in progress. If you have any feedback on it, or if there is any information you think would be useful to add, please let us know.

All posts related to the Configuration Management Initiative

heyrocker's picture

Configuration management code sprint at BADCamp

Start: 
2011-10-23 10:00 - 22:00 America/Los_Angeles
Organizers: 
Event type: 
Sprint

I will be holding a code sprint for the Configuration Management Initative at BADCamp on Sunday, October 16. We will meet up in the Hacker's Lounge and run until we all pass out. While I will be focusing on my initiative, I would be happy to provide guidance for anyone interest in getting involved in the other initiatives as well. Man of the other initiative owners will be at BADCamp, so I am hoping to get them involved as well. See you all there!

Read more
heyrocker's picture

Configuration management code sprint at Pacific Northwest Drupal Summit

Start: 
2011-10-16 12:00 - 22:00 America/Los_Angeles
Organizers: 
Event type: 
Sprint

I will be holding a code sprint for the Configuration Management Initative at the Pacific Northwest Drupal Summit on Sunday, October 16. We will meet up in the Hacker's Lounge and run until we all pass out. While I will be focusing on my initiative, I would be happy to provide guidance for anyone interest in getting involved in the other initiatives as well. See you all there!

Read more
heyrocker's picture

DrupalCamp Copenhagen Configuration Management Initiative code sprint

Start: 
2011-09-19 10:00 - 18:00 Europe/Copenhagen
Organizers: 
Event type: 
Sprint

I will be holding a code sprint for the Drupal 8 Configuration Management Initiative on Friday, September 23 (the Friday before DrupalCamp) at the NodeOne Denmark offices, Flæsketorvet 68, about a 10 minute walk from Copenhagen central station. The sprint will focus on issues around file-based configuration and the entity system. Even if you're not into this topic, feel free to come and hack with us all day!

Read more
heyrocker's picture

Bi-weekly IRC meeting

Start: 
2011-09-20 19:00 - 20:00 UTC
Organizers: 
Event type: 
Online meeting (eg. IRC meeting)

Bi-weekly IRC meeting to focus on what needs to be done in the next two weeks, and hash out issues that need extensive discussion.

Read more
fago's picture

Entity API update and summary

Here is a short summary of what we discussed at the Drupalcon London.

There has been a core conversation talk by Peter Wolanin and me, of which you can find the video here and the slides here.

Roadmap

The further roadmap is to:

  • define the API + do a test entity type
  • port a core entity
  • do performance testing
  • implement revisions + port node and other entity types
  • refactor field storage

Performance testing basically should be repeated after every step.

Status

  • There is a first patch that moves the entity API in its own module, which we need to get in first.
    http://drupal.org/node/1018602 -> Needs review.
  • There is an issue for implementing basic CRUD and porting a first entity type: comment
    http://drupal.org/node/1184944 - work in progress
  • We've worked on defining the basics of the API at the Drupalcon codesprint (see below).
Read more
heyrocker's picture

Configuration management sprint - file formats

Welcome to another discussion from the configuration management initiative! So I believe that in the last thread we pretty much got everybody on board with the idea of 'We can use pure JSON as our file format if we use a hashed directory name and don't write the files by default.' This is great, however it then led to more discussion of 'Why are we using JSON anyways? Why aren't we using PHP/YAML/INI/LOLCODE etc.' Some good points were brought up in this discussion and I think it is worth hashing this out now.

Read more
webchick's picture

Summary of Configuration Management sprint

Last week, before DrupalCamp Colorado, Greg "heyrocker" Dunlap, David Strauss, Larry "Crell" Garfield, and Karoly "chx" Negyesi met to hash out architectural details and whip up some prototype code for the Drupal 8 Configuration Management initiative.

What problems are we trying to solve?

  • Currently there is no good way to move Drupal configuration information between environments because this data is scattered throughout the database in a variety of formats, oftentimes intermingled with content.
  • This also makes it impossible to version control this information, to store history, and to be able to rollback changes.
  • Every module stores their configuration data in a different format, there is no standardization at all, even within core.
  • There is also no standard API for saving this information (aside from the simple case of the variables table) so developer often roll their own solutions.
  • The entire contents of the variables table is loaded on each page request, even for rarely-accessed data, leading to memory bloat.
  • It is cumbersome to manage information that is different between server environments for the same project (database information, api keys, etc.)

We specifically are NOT (yet) trying to solve the problem of contextual configuration; only the underlying API that handles getting/setting this configuration data and shuffling it around to different sites.

The code that was developed at the sprint as a prototype is available at http://drupal.org/sandbox/heyrocker/1145636 for your reviewing pleasure. The main things to look at are the includes/config.inc and modules/config/config.test files.

What follows is a summary of the results. Your feedback is welcomed!

Read more
heyrocker's picture

Putting it all together

This document is a proposal for a high-level gameplan for the configuration management initiative.

Read more
heyrocker's picture

A new system for managing configuration

This is a proposed game plan for managing configuration information in Drupal 8. This is focused on config data - the kind of thing that is currently being managed by the variables system as well as more complicated items like Blocks or Views.

Read more
heyrocker's picture

Game plan for UUID support in core

One of the key aspects of solving the configuration management conundrum is identifying how to uniquely identify data between servers. To this end I propose implementing UUIDs in core for the identification of content, and to provide an API through which UUIDs can be generated and added use by contrib modules. While we are still talking through many big picture architectural issues, I think that it is possible to get moving on this and several other tasks to get the real work started. So here is my proposed game plan for this, created after some discussion with Dave Hall (skwashd) who has put a lot of work recently into porting the UUID module to D7.

Read more
Subscribe with RSS Syndicate content

Config Management Initiative

Group organizers

Group categories

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week