2. www.altimetrik.com
DevOps 2.0 Approach :
-On-boarding better performer
-Micro service compatible
-Holistic Approach
-Tailored Solution
-Tested Best Practice
-Known by experience
-End to end coverage
5. www.altimetrik.com
SCM : Github
Single Master model with Release branch.
Features under practice like :
-Code Freeze Call
-Release Branch
-Cherry Pick
-Tagging
-Protected master & Sprint Branch
-Pull Request.
-Code review
-Unit test pre-merge
-Feature Integration test
6. www.altimetrik.com
Build : Maven (3.2.1)
Following Maven build life cycle.
- Uniformed build across environment, Predictable artifacts.
- 70+ POM files to integrate different application modules.
- Different set of artifacts for Prod & Non-Prod release.
- Using Snapshot for Non-Prod deployment
-Sunfire plugin for test integration
7. www.altimetrik.com
Continue Integration : Bamboo
- Queue Prioritisation
- Environment specific Build
- Feature & Module targeted build
- Unit & Integration test
- Code coverage base build status
- Artifact deployment on lower
environment
- Environment Sanity check
- Multiple slaves in different Availability
Zones
- Benchmark builds on the basis of CPU,
N/w and Storage
- Standardized slaves configuration
- Pager Duty integration for extremely
critical jobs
8. www.altimetrik.com
Artifact Repository : Nexus
-Version Controlled artifacts
-Reduced build time by 3rd party dependency storage
-Segregated artifacts for upper and lower environment
-Centralized access for all build plans.
-Easy manageability of distributed components.
9. www.altimetrik.com
Code Quality : Sonar
- Minimum passing level at 65%
- Lines of code
- Violations
- Integration Test Coverage
- Complexity
- LCOM4 (Lack of Cohesion of Methods)
- Package tangle index
- Comments & Duplicate Lines
10. www.altimetrik.com
Project Management 1 : JIRA
- Department vise JIRA Project
- Integration with TestRail, Github.
- Multiple workflow per Project
- KanBan DashBoard.
- Worklog, TimeSheet, Progress Check
11. www.altimetrik.com
Project Mgmt 2 : Confluence
- Tightly coupled with JIRA & Bamboo
- Easy linking of JIRA ticket
- Version controlled documentation.
- Template and rich formatting support
18. www.altimetrik.com
Database Mgmt : RDS (MySQL)
- Multi Dev & Multi Branch
- Refactor Your Database
- Reliable database update
- Open and Extensible
- Support XML, YAML, JSON or SQLformat
- Take control via ChangeSet, ChangeLog
19. www.altimetrik.com
Security 1: Environment Security
- Alert Logic
- Multi factor authentication
- Per Sprint AMI Update
- System and DB Login trace
- AWS Security Group
20. www.altimetrik.com
Security 2 : Application Security
- Per Module Veracode scan
- Scan after each Major release
- Application security testing
- Runtime security protection
21. www.altimetrik.com
Security 3: Data Transaction Security
EncrypUtil
- Encrypt text
- No confidential text.
AES265
- Encrypted credential
- No password stored on Database.
22. www.altimetrik.com
Other Services 1 : MailTrap
- Per environment account
- Fake SMTP Server
- Full API Support
- Efficient Pre-Production testing
24. www.altimetrik.com
Other Services 3 : Solr Cloud
- File based Indexing
- Master slave model
- Zookeeper File system
- Multi Shards, multi copy
- Incremental indexing
- High Availability
- Full functionality using API
25. www.altimetrik.com
Log Analyzer : Splunk
- Use of plug for easy operation like “DB Connect”
- Thresholds, key word match alert.
- Job Scheduling
- Dashboard, Report extraction
- Log analysis.
- Trend monitoring
- Integration with AWS Cloudtrail
28. www.altimetrik.com
Environment Support : Non-Prod
- Multiple build per day
- Multiple environment per use case
- Each one has its own ecosystem.
- Support to all component
- Readiness of
- QA Environment
- DevStack
- Build Verification Test Env
- QAPerf
- PreProd
- UAT
29. www.altimetrik.com
Production Release
- Pre-Release Checklist
- Pre-Release Meet (Drill)
- Production Release
- DR Stack update
- Post Release retrospect call
- What did we do well ?
- What should we have done better ?
30. www.altimetrik.com
Environment Support ( DR Site)
- Wakeup DR, scaling up the infrastructure
- Break read replica, convert DR DB to writer
- Start all the services
- Switching traffic route to DR
- Adjust DR for Production load
- Periodic test of DR Site
- Insure lease billing
38. www.altimetrik.com
Culture Practice 1 : Uniformed Style
- Talk in bit and bytes
- Uniformed directory structure.
- Uniformed way of change request
- Uniformed work process.
- Uniformed platform to communicate
- Skype
- Mail
- Slack
39. www.altimetrik.com
Culture Practice 2 : Uniformed work
- Documentation
- Full update on ticket
- Re-open ticket with same priority if not documented well.
- Link previous ticket.
- Link any dependency
- Link stockholder
- Link any pull request
- Link build status.
- Process documentation
40. www.altimetrik.com
Culture Practice 3 : Uniformed Infrastructure
- Infrastructure Standardisation
- Easy of handling inconsistency of :
- AWS (VPC, ACLs, ELBs, SNS, SQS, S3 policies, …)
- OS (kernel, packages, users, iptables)
- 3rd party software (Java, Tomcat, Ruby, nginx)
- AMIs
- Inventory
- Scripts
42. Thank You
To learn more about us visit
www.altimetrik.com
Rahul Janghel
Architect
Rahul.Janghel@Altimetrik.com
+91-96578-26527
Hinweis der Redaktion
Left is what we already have, right is what I am trying to peach in on top of 2.0
So, we already have tailored made solution, modular / stack / tire based / which can replace every piece or layer by choice.
Now focus on 2.0 is not just about building things, but to last long, along with performance.
Development and Release is mostly tools driven, how are we doing into operation ?
* Pre-Define :
- Branching Architecture
- Naming convention
- Merge Flow
* Using GitCola for Merging.
Nothing to add.
Nothing to add.
What will be included?
In the code compliance report we will include below things
1. Lines of code: Show the current number of lines, Classes & New Classes being added in the current release.
2. Violations: code compliance against 524 rules for the PMD, Findbugs and CheckStyle. The violations of the rules are categorized in 5 groups. Blocker, Critical, Major, Minor & Info.
3. Integration Test Coverage: code coverage through unit/integration test cases.
4. Complexity: complexity of the code by method, class & file.
5. LCOM4 (Lack of Cohesion of Methods): the methods of a single class are tied together.
6. Package tangle index:
I don’t want to spend time on this slide, as everyone know what it is and what it can deliver.
To provision a environment, we have many tools, this referring environment is using CloudFormation, and started using Chef.
However, as I am taking reference of a environment to create a model, here are few services which we need to complete a circle.
CloudWatch is actual pulling status details from all the AWS resources and supplying to other 3rd party tools like Pingdom and pagerduty.
Alert logic client is installed on each server, and sharing security details with server.
Alert logic client is installed on each server, and sharing security details with server.
Alert logic client is installed on each server, and sharing security details with server.
Culture is created as a by-product when we work and play together
If we want collaboration we must break down the silos and allow engineers with different expertise and perspectives to work together.
DevOps accelerates the rate at which the opportunities to collaborate present themselves.
Devops piller is automation.. that is difficult without collaboration…