Hybrid Applications on      JBoss & OpenShiftDeveloping a hybrid application management anddeployment strategy for JBoss E...
Very briefly...Andrew Phillips, VP Products, XebiaLabsAndrew is VP of Products for XebiaLabs, providers of the industry-le...
Deployment in your Automation Landscape
Continuous Integration•    Emerged at the end of the ‘90s as one    of the XP practices•    By continuously building and t...
Continuous Integration Shortcomings•    Deployment to the target platform often    not part of the CI cycle➔    Deployment...
With Continuous Deployment...•    Smoke tests    •        Landing page    •        Line of Life•    Functional tests on ta...
Continuous Deployment Flow
Continuous Deployment Flow•    Dev Team    •        Full nightly build    •        Tag package as “released”/”ready”•    A...
Something from Dev...For each version of the application, we shallprovide one single package containing all theartifacts a...
...and something from OpsWe shall provide fully configured infrastructureitems (hosts, application servers, web servers,da...
Application Management•    Track application versions and their contents•    Track deployed applications and their setting...
Application Deployment•    Deployments start out easy...                                    DEV
Application Deployment•    ...and end up complicated                                PROD
Application Deployment•    ...and end up complicated                                PROD
Application Deployment•    ...and end up complicated                                PROD
Application Deployment•    Now there are new environments you want to try                                        PROD     ...
Challenges                                                           ?•    Can I use the same applications/deployment pack...
DiscussionLive Demo
DiscussionDiscuss...
Thanks             Thank you!Deployit: www.xebialabs.com/tourBlog: blog.xebialabs.comTwitter: @xebialabsYouTube: youtube.c...
Were looking forward to seeing you! Visit us at #2920 in the Partner Pavilion for a copy of    our recent JBoss Applicatio...
Upcoming SlideShare
Loading in …5
×

Developing a Hybrid Application Management and Deployment Strategy to JBoss and OpenShift

906 views

Published on

Slides from the JBoss World session on "Developing a Hybrid Application Management and Deployment Strategy to JBoss and OpenShift" on Wed 27th 2012.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
906
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Developing a Hybrid Application Management and Deployment Strategy to JBoss and OpenShift

  1. 1. Hybrid Applications on JBoss & OpenShiftDeveloping a hybrid application management anddeployment strategy for JBoss EAP and OpenShift
  2. 2. Very briefly...Andrew Phillips, VP Products, XebiaLabsAndrew is VP of Products for XebiaLabs, providers of the industry-leadingrelease automation solution, Deployit. Andrew is a cloud, service deliveryand automation expert and has been part of the shift to more automatedapplication delivery platforms. Sitting on panels and driving blog andsocial media conversations, Andrew regularly contributes to key trend-defining technology discussions.
  3. 3. Deployment in your Automation Landscape
  4. 4. Continuous Integration• Emerged at the end of the ‘90s as one of the XP practices• By continuously building and testing software quality should improve• Tests often limited to unit tests (e.g. JUnit)• Sometimes also functional tests (e.g. Selenium)
  5. 5. Continuous Integration Shortcomings• Deployment to the target platform often not part of the CI cycle➔ Deployment procedures not tested!➔ Application not tested on ultimate target platform!
  6. 6. With Continuous Deployment...• Smoke tests • Landing page • Line of Life• Functional tests on target platform (e.g. Selenium) • Content of the landing page • Typical run• Performance tests (e.g. JMeter) • Response time of the landing page • Response time of the simple / complex path
  7. 7. Continuous Deployment Flow
  8. 8. Continuous Deployment Flow• Dev Team • Full nightly build • Tag package as “released”/”ready”• Acceptance/QA • Deploy “released” package to Test environment • Perform tests • If OK, tag package as “accepted”• Production/Ops • Deploy “accepted” packages to Production
  9. 9. Something from Dev...For each version of the application, we shallprovide one single package containing all theartifacts and resource definitionsThe package shall be independent of the targetenvironment
  10. 10. ...and something from OpsWe shall provide fully configured infrastructureitems (hosts, application servers, web servers,databases etc.) grouped by environmentWe shall associate configured environmentvariable values to all environments
  11. 11. Application Management• Track application versions and their contents• Track deployed applications and their settings in the target environments• Compare deployed applications across environments
  12. 12. Application Deployment• Deployments start out easy... DEV
  13. 13. Application Deployment• ...and end up complicated PROD
  14. 14. Application Deployment• ...and end up complicated PROD
  15. 15. Application Deployment• ...and end up complicated PROD
  16. 16. Application Deployment• Now there are new environments you want to try PROD DEV
  17. 17. Challenges ?• Can I use the same applications/deployment packages?• Can I maintain a unified overview?• Can I keep my current change/release management procedures?• Can I experiment with hybrid environments?
  18. 18. DiscussionLive Demo
  19. 19. DiscussionDiscuss...
  20. 20. Thanks Thank you!Deployit: www.xebialabs.com/tourBlog: blog.xebialabs.comTwitter: @xebialabsYouTube: youtube.com/xebialabs
  21. 21. Were looking forward to seeing you! Visit us at #2920 in the Partner Pavilion for a copy of our recent JBoss Application Management andDeployment whitepaper or email info@xebialabs.com

×