-
Notifications
You must be signed in to change notification settings - Fork 2
/
Session-28-AWS&AzureDevops.txt
119 lines (67 loc) · 2.29 KB
/
Session-28-AWS&AzureDevops.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
Github, Jenkins
https://aws.amazon.com/devops/
Requirements:
Source code management(Github,SVN, Gitlab, Bitbucket)
CI-CD tools(jenkins , github action, gitlab) AWS provided tools Azure provided tools.
we are going to handle the code developed by Developer:
checkout the code --> compiling -> build the code --> test the code--> Artifact(release version)-> Deploy to the environment
Environment: Development, Test environment, Preprod environment, Production environment
Infracture as a Code : Terraform, ARM(Azure) Cloud Formation(AWS), pulumi
Configuration Management tool: Ansible, Chef, Puppet, saltstack
What is the Technology Stack: Java , Angular , Python, Mysql, Sql
Build tool: Maven, Flask, Gradle, ant
Artifact repository: Nexus , Jfrog, Azure Artifact repository
Architecture: Monolithic, Microservices
Containerization: Docker -> Docker Swarm -> K8s
AWS Devops Service:
Code Commit : Source code git repository
Code Build : Build and test code
Code Deploy: Automate code deployments to maintain application uptime
Code pipeline: Automate continuous delivery pipelines for fast and reliable updates
Cloud formation :
Stack : EC2, RDS, S3, Lamda, EKS , redshift
ec2 provisioned
RDS provisioned
s3 eroor during provisioning
it will revert all the changes
ec2 decommision
RDS decomission
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Azure:
https://portal.azure.com/ : Azure cloud services
Subscription:
Owner
Contributor
reader
Azure Storage account contributor
Azure Devops:
https://dev.azure.com/niladrismondal/niladrismondal/
https://dev.azure.com/<oraganization>/<projectname>
n number oraganization
each Organization can have n number of projects
Azure Devops Components:
1. Overview
Summary
Dashboard
Wiki (equivalent Confluence page)
2. Boards
work Item
Backlog
Sprint
3. Repos
files
commit
pushes
branches
tags
pull request
4. Pipeline
yon can create with two ways 1. Yaml approach 2. Classic editor
5. Test Plans
6. Artifacts
++++++++++++++++++++++++++++++++++++++++++++++++++++++
Documentation : Confluence
Board: Jira, Rally,
Repos: Github, Gitlab
CICD: Jenkins, bamboo
Artifacts: Nexus , JFrog