More Related Content

Viewers also liked(20)


Similar to How we maintain 200+ Drupal sites in Georgetown University(20)


How we maintain 200+ Drupal sites in Georgetown University

  1. How we maintain 200+ Drupal sites in Georgetown University Vadym Myrgorod @dealancer
  2. About me
  3. About Georgetown University
  4. 258 sites that looks the same
  5. Session plan
  6. Infrastructure
  7. Drupal CMS Feature A Feature B Feature C Feature D Feature E
  8. Feature C Drupal CMS Feature A Feature B Feature D Feature E Site 1 Site 2 Site 3 Site 4 Site 5 Site 6 Site 7
  9. Multisiting
  10. sites.php <?php #biology $sites[''] = 'biology'; $sites[''] = 'biology'; $sites[''] = ‘biology';
  11. Multisiting
  12. Site 1 Site 2 Site 3 Site 4 Site 5 Site 6 Site 7
  13. Well known Drupal cloud Dev Test Prod
  14. Local development
  15. Setup any subsite locally within a few minutes
  16. Sitesync script
  17. Script highlights # Getting DB from the remote server ssh $HOST "drush @gudrupal.$ENV -l $SUBSITE sql-dump --skip-tables-key=common --gzip" > $# Resave theme settings drush @gudrupal.local -l $SUBSITE php-eval "# module_load_include('inc', 'system', 'system.admin'); foreach (array('at_georgetown') as $theme_name) { $form_state = form_state_defaults(); $form_state['build_info']['args'][0] = $theme_name; $form_state['values'] = array(); drupal_form_submit('system_theme_settings', $form_state); } "
  18. if (file_exists('sites/')) { require_once('sites/'); }
  19. $remote_url = 'http://' . $sitedir . ''; $conf[‘stage_file_proxy_origin'] = $remote_url; $files_dir = ‘sites/' . $sdir . '/files'; $conf[‘stage_file_proxy_origin_dir'] = $files_dir; $conf['reroute_email_enable'] = 1; $conf['reroute_email_address'] = ''; $conf['reroute_email_enable_message'] = 1;
  20. Development workflow
  21. Deploy new sites, don’t deploy untested code
  22. A successful Git branching model
  23. Environments Dev Test Prod develop hotfixes personal branches features branches master branch tag tag
  24. Change Control
  25. Be careful with Features do not overuse it
  26. Features are not a panacea
  27. DevOps
  28. Run certain amount of tasks almost each day across 258 sites
  29. How I did it 6 years ago Advice from my PM: do as described above if it is urgent
  30. What I’ve discovered $ drush updb -y $ drush -l biology fra -y $ drush @sites dis devel
  31. What I am doing now $ ./ subsites.txt prod "updb -y" "fra -y" "cc all" > ~/deployment-2014-07-21.txt
  32. What script can do that Drush can’t
  33. What else can be done
  34. Creating a new site
  35. We needed to create 80 new websites for less then a week
  36. Before we launched at least 5 sites a week
  37. It took me more then a day to create my first new site
  38. 4 scripts to automate site creation
  39. Site creation script
  40. Site installation script
  41. Script that adds new SAML record
  42. Sync script
  43. Finally, bulk scripts that do all previous tasks in a batch
  44. Then and now
  45. Why do producers of the hardware make it slower than it actually could be?
  46. Add a delay into your bulk scripts to prevent server from the high load
  47. Introducing Druml
  48. Questions? Email: Twitter: @dealancer
  49. Thanks! Email: Twitter: @dealancer

Editor's Notes

  1. Hi, my name is Vadym Myrgorod and welcome to my session. I will tell about our best practices of how we maintain 200 and more Drupal sites in Georgetown University.
  2. I have been doing Drupal for more then 6 years. I am originally from Ukraine. I’ve moved to the US 4 month ago. And right now I work in Georgetown University.
  3. There are many interesting facts about Georgetown University.
  4. Georgetown University was founded in 1789, one year earlier then the Washington `DC was founded. It was named in honour of King George II. Georgetown University was attended by the Bill Clinton, Jose Manuel Barrosso president of the European Commission There are aprox. 100 employees working in IT department. There is a huge migration into Drupal going on right now.
  5. We actually we have 258 sites. All sites looks the same and changes need to be pushed across all sites.
  6. This session won’t answer the question why we have so many sites, but it will tell: What infrastructure we have How we develop websites How we perform daily tasks And How we create new sites
  7. I would like to start with our infrastructure as it is an important part for understanding.
  8. It’s obvious we are using Drupal content management system :) We have configuration, views, content types and even custom code stored inside features. Each feature represents specific part of the functionality such as Homepage, Image rotator, List pages, etc. When new site is installed features are enabled by install profiles. An install profile also provides some basic configuration that could not be stored in features and creates Lorem Ipsum content. We have Unit and School install profiles which provide slightly different functionality.
  9. There are several ways to organise multiple Drupal sites. We use Drupal multisiting, which comes out of the box. It allows us to store physically all of our sites within a same Drupal directory. This also saves a space on the server. However each site uses own files directory and a database.
  10. A few words about multi siting for those who don’t know. It is a standard Drupal feature. To add new site you have to create subsite directory in the sites directory. You also need to specify domains associated with this sitename in sites.php file.
  11. This is a sample content of sites.php file. Here we assign production, test and dev domains for subsites. This makes Drupal know which site you are accessing when hitting a URL with a specific domain. In reality in sites.php we have 200 and more blocks like this ;)
  12. We moved out common site settings from the settings.php into, which is included into every settings file. That trick saves a lot of time if you need to update settings for all of the subsites and makes possible to override setting for a specific website. Also all modules that are common to all the sites could be stored in the all directory.
  13. And now it is an interesting topic. We have Single Sign On feature for all university services. User accounts are created via LDAP. We use simpleSAMLphp library and Drupal module called same name to implement Single Sign On functionality. Anybody who has a university account can log in to any Drupal site. When GU user logs in into the website via SAML a corresponding Drupal user is created automatically in this case.
  14. And of course we use Drupal cloud. It is very well known Drupal cloud and it is really hard not to guess a name of it :) Of course it is Boston based Drupal company :) I am not doing any advertisement ;)
  15. Let’s go further and talk about how we perform local development. Actually some automation starts here.
  16. As there are 200 and more sites, curtain bugs could only be reproduced on the few of them, so we needed an ability to quickly setup any subsite locally in just a few minutes.
  17. Do you know that many developers are very lazy and me to :) Each time I enter a new job I create sitesync script :) This scripts copy site from server to local environment.
  18. Here is a demo of how it works. Here we are. We have ready site for a local development just in few seconds. I shortened this video. In reality it takes 2 minutes, though it is significantly less then if you do it manually, which can take up to 30 minutes or even 1 hour.
  19. In this slide I highlighted only important parts of the code of the script. First snippet shows how we get DB from the remote server using Drush. There is a reason why I run drush through the SSH. When I specify subsite using -l key it is not correctly working from my machine. I think it depends on the operating system. So may be in the future we will use vagrant. Also when you sync a site from the remote machine to the local machine, for some themes like adaptive themes, CSS stylesheets are missing, because they are generated and stored in files directory. So you need to regenerate them by hitting Save button on the theme settings page. Second snippet shows how the PHP code that resaves theme settings is called via the drush command.
  20. We use file where we store local credentials and local settings. This file is include into common.settings.php. Keep this file on local machine only If this file exist, it is included and local settings are applied.
  21. We use Stage File Proxy module, that automatically synchronises files such as images in the files directory from the remote site to your local site. This is extremely useful. You don’t need to copy files via ssh or ftp. We also use reroute Email module that reroutes any outgoing email to your email address. If you are a Mac user, you should know that Mac is configured to send emails by default. If yo don’t want site users to see some weird emails, you can use this module.
  22. Our development workflow does not look like one on this image. But this is how it could like this if we wouldn’t do some big improvements.
  23. Deploy new sites, don’t deploy untested code. This is the major problem we were facing. Because the creation of the new site assumes deployment of code to the production, we need to be careful of what we are deploying. We need to deploy separately new features, bug fixes and new sites.
  24. Eventually we came to this solution. We use a successful Git branching model also known as Git Flow. There is also Git extension that implements this model. Git Flow simplifies the way 2 or more developers work together on the new features and maintain existing code. There are 3 main branches: master, hot fixes and develop. Master branch contains tested code ready for release, to make a release you simply create a tag on this branch and apply this tag to the production. If you have something urgent to fix you perform the fix in the hotfixes branch, test it and then merge it into master. All development goes in the develop branch. If you work on the big feature you can use a separate branch for this purpose. I have had many examples in my life, when a feature branch was committed into the develop branch after several releases were done. So it is important to have feature branches. Doing that way you will prevent unstable code going into production.
  25. We use 3 environments: dev, test and the prod. They are completely separated environments. Each site has own database, files directory and local git repo per each environment. Dev environment usually contains develop branch, but it can also be set to wrok with hotfixes, personal or feature branches. Test branch usually contains a master branch or a tag out of the master branch - in general it contains any code that should be tested before it goes to production. Prod branch always points to the tag of the master branch, that was previously tested.
  26. We also use some Change Control procedures that require us to have: Deployment script and the backup plan readt. This scripts must be approved by the several people, before they can be used. We need to have a deployment scheduled in the outage window. Outage window is the time during which university is not working, e.g. night or weekends. Then we perform deployment using this script and if something goes wrong we need to perform backup script to roll back changes. There could be an exceptions to make changes in the deployment plan, during the deployment, but they should be discussed with deployment manager. We also need to test changes. This CC is very important because we have lot’s of sites and we should avoid any serious problems going to production. What about minor deployments such as CSS changes? Well, it is up to you to decide what changes should go through the change control.
  27. And be careful with features, try not to overuse it.
  28. Really, Features are not a panacea, they could not solve all deployment problems in the world. Now I know that we should strongly avoid “featurifying” any objects or entities that contain numeric IDs. It could be anything that references content, vocabularies or roles. If the content is changed or even deleted, it will mess up a feature and we will see a feature in the overridden state. There is no guarantee that same object will have same IDs across multiple sites, because content could be created in the different order Moreover AUTO_INCREMENT delta could be changed and this is something that we can not affect on. We depend on our hosting which can change MySQL configuration in any moment, so the delta could change from 1 to 5, so if the role IDs go like 1, 2, 3 before change, they could go like 1, 5 and 15 after a change. This is why new sites will have overridden features. We had this problem: we lost IMCE profile settings for news sites, cause of the auto increment delta change. It happened because IMCE module were storing settings in Drupal variables, so after a change of the delta, IMCE module could not find a configuration for affected profiles for a new sites ;) That was fun to debug :) We had many “positive” emotions ;) However the solution was quite easy. We moved out IMCE settings from a feature into hook_install and hook_update_N. Physically it stored in the same feature but in the install file.
  29. Now let’s move to the next part. I am going to introduce you to how we perform doves and daily tasks such as clearing cache, executing db updates or reverting features. (Cause we do deployment every day, of course not, it is a joke but we do often :)
  30. Other problem we had is that the are curtain amount of tasks that should be run each day across 258 sites. Doing it through the Drupal UI won’t be very effective.
  31. If I were hired in Georgetown University 6 years ago, when I started to do Drupal development, I would do it that way. To perform DB updates I would be going through update.php url for every site and clicking next, next and next ;) If I needed to revert features I would use Features UI to revert features one by one for 200 websites :) And to enable a module I would go to the modules page and enable module I needed. I would repeat it 200 times :) cause I did not know the better way to do it. And now I will tell you better and faster way to do it! Though my product manager says you can do it ”wrong” but only if you have something urgent to fix ;)
  32. During years of development I’ve discovered many useful approaches how to save my own time. So I will share them with you. Use Drush - which allows you to perform Drupal operations through the command line. This exact command performs DB update. Using Drush aliases and the -l key you can access specific subsite on the specific environment. This command reverts features. We could even run a command for all subsites using @sites alias. Though, it does not run fast and may load your server, but it works for all sites.
  33. And this is what I am doing right now. This is a bash script that performs specific drush commands for the subsites on the specific environment. subistes.txt file contains list of sites that are affected. A regular deployment procedure looks like this. We can pass multiple drush commands into this script. In this case we are performing db updates, reverting features and clearing cache. Also we are saving output into the file. One small trick I can teach you when I perform overnight deployment. This output file could be placed in the Dropbox directory so either your or your team members know what’s happening. And one small thing: we are not using Dropbox ;) We are just using some other tools ;)
  34. And here is a demo of how this script works.
  35. Here are some benefits of such approach: We can perform multiple operations in a batch We can perform operations on multiple sites (not necessary all subsites) - you can have different groups sites to perform operations. We can control order of the execution, so the important sites goes first, so you can test them first We can set timeout between iterations, so it will reduce load on the servers
  36. 1. There are also additional scripts that I have created. There is a script that allows to run a PHP code for every site and use return a result to build a report. For example we get total amount of nodes for each sites in the CSV format. 2. There is also a script that allows to perform multiple bash commands for every server running your site. This could be useful if you need to analyse logs that are stored on the multiple servers.
  37. And now it is the most interesting part. It was a big challenge to automate site creation, but finally it is done.
  38. We’ve met new challenge recently: we needed to create 80 new website for less then a week.
  39. When I started to work in Georgetown University we were adding up to the five sites each week.
  40. It took me more then a day to create my first site. Then I improved this number to hours. And then I decided to automate this process and eventually created several scripts that helps me to do this.
  41. Here is a demo of how it works.
  42. We have a sync script synchronises files and database from one environment to another. This could be useful in various scenarios like deployment or some kind of backup. When create new site need to make sure it is the same on all environments.
  43. Finally, we have bulk scripts that do all previous tasks in a batch.
  44. Let’s compare of what we had before and what we have now. It took ~3 hours of work to create a website manually. Now we can create as many websites as we need with running just a 3 scripts. It saved me more 1.5 month of work to create 80 new websites just running this scripts over a night. I’ve just launched them and went sleep.
  45. However there is an important thing to know. Let me ask you a question. Why do producers of the hardware like processors or video cards make it slower than it actually could be? ?? Guess why? I remember the video card I had in the 2000 year. After a playing a computer games on the high graphic settings, video card could hang for a second, several times. !! So producers want hardware to be in use more time and be more reliable. They do not want it to be overheated and finally broken.
  46. This is exactly a reason why we should a add delay into our bulk scripts to prevent server from the high load.
  47. I would like to introduce you Druml. Druml is a Drupal multisite tool, that allows your to perform various operations that you have learnt today during my presentation. The reason we created this project, is that dealing with multiple sites is a common problem to many organisations and universities. Also there haven’t been a single good solution that perfectly fits into Drupal environment. And we developed this solution. Also keep in mind that it is very fresh Open Source which is in an active development phase and it may not cover all use cases, but our aim is to create a tool that will be a best match to various development workflows and infrastructures. So you are welcome to test and send me your feedback.