Automating Software Development Life Cycle - A DevOps Approach
•Télécharger en tant que PPTX, PDF•
2 j'aime•3,654 vues
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (12)
Similaire à Automating Software Development Life Cycle - A DevOps Approach
Similaire à Automating Software Development Life Cycle - A DevOps Approach (20)
Dernier
Dernier (20)
Automating Software Development Life Cycle - A DevOps Approach
- 2. Akshaya Mahapatra Software Engineer @ VCE (Virtual Computing Environment) Experienced in ◦ Java/J2EE ◦ VMware products vSphere, vCloud ◦ Puppet Developing solutions for application deployment on cloud
- 3. 3
- 4. Why DevOps? Why now? Stages in SDLC ◦ Check-in ◦ Build and Test ◦ Infrastructure setup ◦ Release ◦ Monitoring and scaling A typical use case Q & A
- 5. Dev and Ops have different goals. ◦ Features vs SLA Skills are different. ◦ Dev team lacks infrastructure knowledge ◦ Ops team unaware of complexity of development. Slow feedback loop ◦ Business -> Ops ->Dev
- 6. An idea, practice or culture that brings Dev, Ops and Business together. How? ◦ Repeatable processes ◦ End-to-end automation. ◦ Continuous monitoring
- 7. Virtualization and Cloud Computing ◦ Programmable Infrastructure ◦ Just-in-time Provisioning Network Compute Storage Agile software development ◦ Speed is critical.
- 8. Application Needs ◦ Nodes can fail ◦ No “manual” configuration ◦ Heterogeneous Execution environments Advancement of technology ◦ Puppet eco-system
- 13. Apache License Initial Release – October 2000 Central Repository. ◦ Better access control Fast branching and tagging.
- 14. De-centralized. Inherent redundancy. Local repository. Efficient use of space. Offline Use
- 15. SVN GIT svn checkout. svn add svn commit. svn commit svn diff svn update online git clone git add git commit git push git diff git pull online/offline
- 16. All “stable” code goes to trunk. Major development in branches. ◦ Merge to trunk when stable. Snapshots for release are tagged.
- 17. Simple, Java based XML based configuration Dependency Management ◦ Project ->Target Ease of logging and debugging. Integration with major IDEs.
- 18. Beyond “typical” build ◦ Reporting ◦ Collaboration. ◦ Project life cycle. Automated dependency management Sensible default configuration Better suited for complex projects
- 20. Dependency in pom.xml <dependencies> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>${log4j.version}</version> </dependency> </dependencies>
- 21. Distribution Management in pom.xml <distributionManagement> <repository> <id>devops-snapshot</id> <name>DevOps Repository</name> <url>http://codecamp.com/repo/devops</url> </repository> </distributionManagement>
- 22. Open source Continuous Integration server http://jenkins-ci.org/ ◦ Written in Java ◦ Performs jobs ◦ Numerous plugins ◦ Wide support ◦ Post build actions
- 23. Code Repository (GIT/SVN) Maven Ant Junit TestNG Selenium Check-in Workspace Target Server Jenkins (Hudson) Build Update Test 3 1 2 4 Packaging Packaged Application
- 24. Clone VM Configure VM Blue Prints Templates Infra Setup 3 1 2 Power On Build Successful 4 VM VM VM VM vSphere
- 25. Cloning Specification: ◦ Networking Info ◦ DNS ◦ Domain Host/Cluster Information OS Customization ◦ Sysprep in windows ◦ IP configuration in Linux
- 26. Supported by VMware and up-to-date Clone VM: ◦ Create Clone Spec: Set host name, network info, data store, host resources, folder etc. ◦ Task task = vm.cloneVM_Task(vcFolder, vmName, cloneSpec); ◦ if (task.waitForTask() == Task.SUCCESS) return true; else return false;
- 27. Supported by VMware and up-to-date Clone VM: ◦ Add-PSSnapin VMware.VimAutomation.Core ◦ Connect-VIServer -Server $VC ◦ New-VM -Name $cloneName -VM $sourceVM - ResourcePool $respool -Datastore $datastore
- 28. Powershell New-NetIPAddress –InterfaceAlias “Local Area Connection” –IPv4Address “192.168.1.100” – PrefixLength 24 -DefaultGateway 192.168.1.1 Set-DnsClientServerAddress -InterfaceAlias “Local Area Connection” -ServerAddresses 192.168.1.254, 192.168.1.253
- 30. Install Applications on Templates ◦ Red hat with Apache ◦ Windows with SQL Server ◦ Cent OS with Tomcat ◦ Red hat with ActiveMQ Create Virtual Machines from templates. ◦ Applications already installed. Configure virtual machines.
- 31. Templates with Base OS ◦ Red hat ◦ Windows ◦ Cent OS Create Virtual Machines from templates. Install required components on virtual machines on demand using Puppet.
- 32. Open source Configuration Management http://puppetlabs.com/ ◦ Written in Ruby ◦ Infrastructure as code. ◦ Client Server system. ◦ Gaining lot of traction ◦ Simple domain specific language (DSL)
- 33. Catalog Puppet Master Node (Puppet Agent) Node (Puppet Agent) Facts Facts CatalogConfig Repository Client Server Architecture
- 34. package { "sudo": ensure => "installed" } package { 'mysql': ensure => installed, source => „C:/mysql-winx64.msi', }
- 35. User { “codecamp": ensure => "present", uid => "1001", gid => "1001", comment => “Code Camp Developer", home => "/home/codecamp ", shell => "/bin/bash" }
- 36. file { "C:/apache": ensure => directory, recurse => true, source =>puppet:///modules/apache", }
- 37. exec { "Install Apache" : command => 'install_apache.bat', require => File["C:/apache"'], path => "C:/apache/bin", }
- 38. service { "Apache2.4": ensure => running, require => Exec['Install Apache'], enable => true, }
- 39. Class apache { File { "C:/apache": } exec { "Install Apache" : } service { "Apache2.4": } }
- 40. node apache1 { include apache } node tomcat1{ include tomcat }
- 41. Get information on all the nodes: Host Name, domain, IP Address facter -p Puppet manifests can access them as global variable Ex: “$::hostname” Customizable.
- 42. class ntp { case $::operatingsystem { centos, redhat: { $service_name = 'ntpd'} debian, ubuntu: { $service_name = 'ntp' } } ………… }
- 43. Most of application deployment need Orchestration support ◦ Orchestration is “cumbersome” with base puppet. Changes need to wait until next “agent” run..
- 44. Open source Asynchronous Orchestration ◦ Can manage puppet runs. Scalable ◦ Parallel execution
- 45. Puppet Master Node (Puppet and mCollective Agent) Catalog mCollective Client Node (Puppet and mCollective Agent) ActiveMQ Commands Commands Catalog
- 46. Find out reachable nodes ◦ mco ping Find service status ◦ mco rpc service start service=httpd Run puppet agent once on a node ◦ mco puppet runonce –W hostname=apache1
- 47. Environments ◦ Development ◦ Test ◦ Production Defined as a config parameter. Puppet Master can handle multiple environments.
- 49. Managing what nodes get what classes.. ◦ Nodes.pp grows out of control when you have thousands of nodes. Solution: ◦ External Node Classifier
- 50. Key/Value pair lookup tool Provides environment hierarchy ◦ Default ◦ Node Name ◦ Environment ◦ Domain
- 53. VMware Products ◦ Hyperic – OS/Infrastructure ◦ App Insight – Inside Application Java Tools and APIs ◦ Sigar ◦ Jconsole
- 55. Web Server (Apache) App Server (Tomcat) App Server (Tomcat) App Server (Tomcat)
- 56. <application> <name>Puppet Demo</name> <nodes> <name>Tomcat Server</name> <template>CentOS56 64bit</template> <key>war_file</key> <instances>3</instances> </nodes> <nodes> <name>Apache Load Balancer</name> <template>CentOS56 64bit</template> </nodes> </application>
- 57. Clone templates to create virtual machines. ◦ One VM for apache Load Balancer ◦ Three VMs for Tomcat and App .war file. Create Puppet Manifest or Configure ENC. ◦ Associate Puppet/Classes with node names. Run Puppet Agent on Virtual Machines ◦ In correct sequence.
- 58. Install Apache ◦ mco puppet -W hostname=apache1 runonce Install Tomcat ◦ mco puppet -W role=apserver runonce Configure Apache ◦ mco puppet -W hostname=apache1 runonce
- 59. Puppet and Puppet Forge ◦ puppetlabs.com ◦ forge.puppetlabs.com/ VMware VIJava API ◦ vijava.sourceforge.net/ Provisioning ◦ github.com/puppetlabs/razor