The document describes the Django infrastructure setup at UGent for developing and deploying web applications. It discusses setting up Git repositories for source code and packages, using Git flow for version control. It also outlines the server infrastructure with load balancers, web and app servers, and databases. Projects are deployed through a continuous deployment pipeline using Jenkins to build, test and deploy code through testing, QA and production environments. Future plans include adding asynchronous messaging, response caching, improved acceptance testing and monitoring.

1. Django Infrastructure @ UGent
Kevin Van Wilder

2. Why We Set Up the Django Infrastructure
As an Alternative to Plomino
● Rapid application development
● yet Reliable, Maintainable, Scaleable
● Better at Handling Large Loads
● Seperate Applications from Portal Site

3. Source Code Infrastructure

4. Git Repositories
Each project has 2 repositories
● site-<projectname>.git
○ Django Source Code
○ Business Logic of the application
● pkg-<projectname>.git
○ Debian Package Source Code
○ Installation Logic of the application
Each repository has a specific code structure.
○ Why? Automation!

5. Git Flow
http://nvie.com/posts/a-successful-git-branching-model/

6. Server Infrastructure

7. Load Balancer
djprd
Web + App
djprd1
Web + App
djprd2
...
DB
Overview Production Infrastructure

8. Managed by
Developers
Managed by Jenkins Pipeline & Puppet
Load Balancer
djprd
Web + App
djprd1
Web + App
djprd2
DB
framboo
s
Load Balancer
djqas
Web + App
djqas1
Web + App
djqas2
Web + App
djtst1
Web + App
djdev1
Complete Infrastructure

9. “Web + App” Servers
Puppetized
Continuous Deployment via Jenkins
Each server contains all the apps
Load Balanced

10. Database
framboos.ugent.be
Maar migratiemogelijkheden naar:
● PostgreSQL
● MySQL
● SQLite
● Oracle

11. Support Tools

12. Version Overview

13. Supporting Tools

14. Supporting Tools

15. Other Tools
Ansible
Maintenance Task Orchestration
● db syncs
● process restarts
● etc

16. Continuous Deployment Pipeline

17. Jenkins

18. Project Specific
Buildsteps
Project Independent Buildsteps
Build Unit Test
Acceptance
Test
Package Deploy TST
Deploy QAS
Deploy PRD
Onderwijstips
Kwalifacts
Telefoonboek
UGent Mobile
Abstract Jenkins Pipeline

19. Abstract Jenkins Pipeline
Build
Unit Test
Acceptance
Test
Package
Deploy TST
Deploy QAS
Deploy PRD
Start Project
Build The only part of the pipeline that is specific to a project
Starts execution of the pipeline
Calls the “Build” job with the project-specific parameters:
PROJECT_NAME
PACKAGE_NAME
To add a new project pipeline, simply...
Duplicate this job
Change the values of the parameters

20. Abstract Jenkins Pipeline
Build
Unit Test
Acceptance
Test
Package
Deploy TST
Deploy QAS
Deploy PRD
Start Project
Build
Build
Clones the Git code for the web application
Unit Test
Finds all the written unit tests and executes them
Acceptance Test
Currently not yet implemented.
Finds all the written acceptance tests and executes them
Package
Clones the Git code for the debian package
Copies over the tested source code
Builds a Debian Package

21. Abstract Jenkins Pipeline
Package
Deploy TST
Deploy QAS
Deploy PRD
Start Project
Build
Deploy TST
Built packages are automatically deployed to Testing
Deploy QAS
Manual trigger for deployment to Quality Assurance
Can only be triggered if successful deploy to TST
Deploy PRD
Manual trigger for deployment to Production
Can only be triggered if successful deploy to QAS
Build
Unit Test
Acceptance
Test

22. Future

23. Future
Asynchronous Messaging (RabbitMQ)
Caching
Response Caching (Varnish)
Low-Level Caching (Memcached)
Acceptance Testing (Selenium)
Seperate database for each environment
More Monitoring (Graphite)

24. Kevin Van Wilder
@KevinVanWilder
Open Source Consultant
INUITS
Duboisstraat 50 - 2060 Antwerp
http://www.inuits.eu
QUESTIONS ?