CI/CD on Windows-Based Environments - Noam Shochat, eToro - DevOpsDays Tel Aviv 2015
•Télécharger en tant que PPTX, PDF•
2 j'aime•531 vues
CI/CD on Windows-Based Environments - Noam Shochat, eToro - DevOpsDays Tel Aviv 2015
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à CI/CD on Windows-Based Environments - Noam Shochat, eToro - DevOpsDays Tel Aviv 2015
Similaire à CI/CD on Windows-Based Environments - Noam Shochat, eToro - DevOpsDays Tel Aviv 2015 (20)
Plus de DevOpsDays Tel Aviv
Plus de DevOpsDays Tel Aviv (20)
Dernier
Dernier (20)
CI/CD on Windows-Based Environments - Noam Shochat, eToro - DevOpsDays Tel Aviv 2015
- 1. CI/CD on Windows-based Environments Your Social Investment Network eToro©2015 Presentation materials are confidential and should not be copied, distributed or passed on, directly or indirectly, to any other person. Noam Shochat, Sr. DevOps Engineer | noamsh@etoro.com
- 2. ● The world’s largest social investment network ● Founded in 2007, raised $60M ● >200 employees (~half in Engineering) ● Offices in IL, UK, CY, RU and expending Some Basic Facts... eToro©2015 Presentation materials are confidential and should not be copied, distributed or passed on, directly or indirectly, to any other person.
- 3. 5M registered users. 140 Countries. 150M Trades.
- 5. eToro’s Legacy Technology ● HTML/ASP, Flash, iOS & Android clients ● 2 Geo-distributed data centers ● >130 Services ● > 500 Servers ● Hybrid MS tech stack & Open Source Server technologies (Redis, RabbitMQ, HAProxy, etc…) eToro©2015 Presentation materials are confidential and should not be copied, distributed or passed on, directly or indirectly, to any other person.
- 6. CI / CD ingredient CI / CD Code commit Deploy and tests in Production Build, Unit tests
- 7. Different OS’s 5 different environments Different development languages
- 9. Manage all with Jenkins
- 10. CI / CD Pipeline Check-In GitHub Mercurial Build MSBuild Unit tests NUnit Integratio n tests UI Testing Prod Deployment Managed by Jenkins QA Deployment
- 11. Jenkins Cross Platform Orchestration Jenkins master
- 12. Build your flow with Jenkins ● Build Flow plugin ● WorkFlow plugin
- 13. Inside Jenkins Job Script languages: ● Batch ● Powershell ● Shell ● Ruby
- 14. Auditing and reporting ● Graphite ● Splunk ● Slack
- 15. Provisioning servers and Deploy with Puppet
- 16. Things we’re doing with puppet define general::web_service( $artifact_source, $config_file_name='web.config', $configerb_path, $erb_config_file_name='web.config.erb', $deploy_destination, $zipfile_mount_name, $port=80, $enableanonymousauthentication=false, $template_config={} ) { include general::7zip include general::remotesign include general::basicfoldersinstall addwebsite {"${name}": port => $port, require => Class['enableiis'] } addwebsite::enablewindowsauthentication{"${name}": site_name => $name, require => [Class['enableiis'],Addwebsite["${name}"]], } addwebsite::enableanonymousauthentication{"${name}": site_name => $name, enable => $enableanonymousauthentication, require => [Class['enableiis'],Addwebsite["${name}"]], } ● Enable features ● Install 3rd party apps ● Creating folders ● Installing / Configure win services ● Installing / Configure websites (IIS)
- 20. Tools for Key Value store
- 21. Hiera ● Developed by Puppet labs, there for fully integrated with puppet ● Key value store ● Configuration file per environment on the same puppet master
- 22. ETCD acl to the office acl to the office Azure North Europe server 1 server 2 APP1 DLL APP2 DLL APP3 DLL CCM 2 UI - Admin server 3 server 4 CCM 4 Azure West Europe ILB LBS ILB LBS CCM 3CCM 1
- 23. CI / CD on Azure Cloud
- 24. PAAS in Azure ● Cloud service ● Slots ● Uploading Packages ● Integration with github (Git Hook)
- 25. IAAS on Azure ● Jenkins agent ● Puppet master ● Mcollective client ● Mcollective server and puppet agent on all servers.
- 26. Summaries ● Jenkins - Main CI / CD tool ● Puppet - Provisioning and deployment ● Mcollective - Orchestrate ● PowerShell Azure SDK - For deploying Web/worker roles ● This is all just tools - DevOps is a lot more
- 27. Wish List ● Automate the creation of new Jobs and Flows in Jenkins. ● More self service
- 29. Noam Shochat, Sr. DevOps Engineer | noamsh@etoro.com
Notes de l'éditeur
- So Now let’s talk about CI / CD and how it works on Microsoft based environment. CI / CD ingredient
- Now we know what is CI / CD but how do we implement it on our company? First, what are the challenges we are facing with?
- So, can we do it on our mostly microsoft based environment? Yes we can Despite most tools were designed first to work on unix based servers.
- The Jenkins agent connected to the Jenkins master in our local DC designated puppet master and Mcollective
- The Jenkins agent connected to the Jenkins master in our local DC designated puppet master and Mcollective
- The Jenkins agent connected to the Jenkins master in our local DC designated puppet master and Mcollective Mcollective server and puppet agent on each vm, same as on our on-premise.
- Our Mcollective client, the component which send the command to the servers, installed on a Ubuntu server. In that server we run a shell script that run the nco command that trigger puppet the run on the server we want to in accordance with the environment we want to deploy into.
- Developed by Puppet labs, there for fully integrated with puppet Key value store Configuration file per environment on the same puppet master
- We use etcd with inhouse development of admin UI for it. We call it CCM (Central Configuration Management). All applications are taking their configuration from it. It’s simplify when wanting to change configuration without logging to the server itself were the application is installed or when we use puppet for the deployment and hiera for the key-value it saves us the necessary to run full deployment.
- We can’t talk about microsoft / windows without talking on azure.
- Few key features in Azure makes it very easy. Cloud services Slots Uploading packages GitHook
- The Jenkins agent connected to the Jenkins master in our local DC designated puppet master and Mcollective Mcollective server and puppet agent on each vm, same as on our on-premise.
- The Jenkins agent connected to the Jenkins master in our local DC designated puppet master and Mcollective Mcollective server and puppet agent on each vm, same as on our on-premise.
- The Jenkins agent connected to the Jenkins master in our local DC designated puppet master and Mcollective Mcollective server and puppet agent on each vm, same as on our on-premise.