Rapid deployment models for uPortal
Download as PPTX, PDF0 likes191 views
Tom Freestone presented at the 2011 Jasig Conference on moving portal development to a continuous integration and delivery model. He discussed how traditional portal development led to errors and issues due to inconsistent environments across development, testing, staging and production. He advocated for empowering portal teams by enabling continuous integration, flexible and quick deployments, and treating the application as code with binaries, data and configuration managed in repositories. This would reduce errors, lower stress and allow anyone to deploy quickly.
Rapid deployment models for uPortal
- 1. Tom Freestone Senior Developer Brigham Young University 2011 Jasig Conference June 20, 2013
- 2. • Portals ran on large, beefy, expensive machines • Developed Deployment Anti-patterns
- 3. • Involves Install Cookbooks • Boring and Repetitive = Errors • Requires a Jedi Master to Debug – Don’t Get Hit by a Bus Anti-Pattern • Not a Good Use of Resources
- 4. • Assume Development Environment is the Same as Production. • Assumptions = Killer
- 5. • Servers have Personalities • Manual Configuration / Debugging • Changes are not Propagated • Unable to Reproduce Errors
- 6. • Mass produce “Servers” • Problem of Sprawl – 125% year increase in servers • How do you deal with configuration differences between dev, test, stage, prod?
- 7. • Empower our Portal Teams • Reduce Errors • Lower Stress • Flexibility • Everyone can Deploy Quickly
- 8. • Continuous Integration – Prove your software works with each commit • Benefits – Build is Repeatable – Early Warning of Problems – Wiring and Configuration that Works – Effective Teams • Use Continuous Integration with Portal and Portlets
- 9. • An Application is composed of Binaries, Data and Configuration. • Artifact Repositories – Maven – Yum (rpm)
- 10. 1. Enable maven resource plugin <project> ... <name>My Resources Plugin Practice Project</name> ... <build> ... <resources> <resource> <directory>src/main/resources</directory> <filtering>true</filtering> </resource> ... </resources> ... </build> ... </project> 2. HelloWorld.txt Hello ${name} 3. Command Line mvn resources:resources Output : Hello My Resources Plugin Practice Project
- 12. 1. pom.xml <profiles> <profile> <id>development</id> <properties> <greeting>Welcome to Jasig</greeting> <properties> </profile> <profile> <id>production</id> <properties> <greeting>Welcome to Denver</greeting> <properties> </profile> </profiles> 2. helloWorld.text Hello ${greeting} 3. Command Line mvn package -P production -> Hello Welcome to Denver mvn package -P development -> Hello Welcome to Jasig
- 14. <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>rpm-maven-plugin</artifactId> <version>2.1-alpha-1</version> <extensions>true</extensions> ... <configuration> ... <mappings> <mapping> <directory>/tmp</directory> </mapping> </mappings> ... </configuration> ...</plugin> </plugins> </build> <packaging>rpm</packaging>
- 15. • CAS • Portlets • uPortal as a rpm