SEVEN PEAKS SPEAKS

“Spooky Cloud Realm”

The Monster of “Dev+Ops”

26.10.22

SEVEN PEAKS SOFTWARE

​

​

Cloud Team - People

Giorgio

Dinand

Korn

Nicolas

Siw

Bank

SEVEN PEAKS SOFTWARE

​

​

Cloud Team - Certifications

SEVEN PEAKS SOFTWARE

Giorgio Desideri

Senior cloud lead who have been working in IT since 2006.

​

I studied dark arts especially casting obscure spells regarding software applications creations and summoning several creatures for spiritual leading of undead teams.

​

Certified cloud architect for AWS and Azure.

LET’S START !

AGENDA

The “Monster

• Why DevOps is a monster ?
• The extensions of the monster
• The Blue Monster : Azure DevOps
• The other colored monster
• Orange Monster : AWS DevOps
• Cyan Monster : GCP DevOps

Develop + Operations

Why DevOps is a Monster ?

Allow me to tell you a story …

The Monster of DevOps

Allow me to tell you a story

Once upon a time, there were some Developers which have to deliver a software application named “Bob”.

​

Together with the Developers, there were also some other people which have to support and maintain Bob. Those people are called the Operations.

The Monster of DevOps

Allow me to tell you a story

The day of the 1st release ( or 1st deployment ) of Bob, someone asked to the Developers how to deploy / deliver their Bob-code, and moreover, the Operations people joined to the conversation.

​

According their silos structure, the code was developed ( and probably tested ), the server or the cloud services were ready to receive the compiled code, but now no one were able to complete the operations.

Then THE IDEA was born

The Monster of DevOps

Allow me to tell you a story

Developers which want to develop Bob, they should be able to understand and implement the way how-to deploy Bob

​

Operations which want to deliver Bob, they should be able to understand and implement the way how-to configure, manage and maintenance Bob

The Monster of DevOps

Allow me to tell you a story

DevOps role was born. A “monster” that understands both of the part and allow the Developers and Operations to accomplish their goals.

It born as:

• Hybrid, doesn’t belong to any of the parties
• Conscious, because of it has to listen and understand the requirements of both of the parties
• Aware & Responsive, be able to decide what should be done and able to response

X-DevOps

The extension of the monster

Extension of the Monster

X-DevOps

• SecDevOps
• Incorporate the security team responsibilities
• QA
• Bob should be tested and its quality ensured
• Agile
• Bob should be managed and all the activities should be linked together

The Blue Monster

Azure DevOps

Blue Monster

Anatomy

Blue Monster

Anatomy

Organization

Project FE

BE Project

Infra Project

…

Blue Monster

DevOps Repos

Repository types:

• Git
• TFVC

​

Integration

• Boards
• Pipeline

​

Blue Monster

DevOps Pipelines

• “Pipeline”
• Continuous Integration
• Classic or YAML
• “Release”
• Continuous Deployment
• Classic
• Deployment Groups
• Task Groups
• Libraries

Blue Monster

DevOps Artifacts

• Represents what is going to be deployed
• Storage of the output of CI Pipelines
• Versioned
• Shareable across pipelines

Blue Monster

DevOps Test Plans

• “It is not a bug, it is a feature”
• Definition of Plans for testing cases
• Automated test cases
• Manual test cases
• Integrated with Working Item swimlines inside the Boards
• Area / Project / Feature Path

Blue Monster

DevOps Boards

• Monitoring and Report services
• Project types
• Basic
• Agile
• Scrum
• CMMI
• Project based on Working Items

Other Coloured Monsters

Other public cloud DevOps services

Orange Monster

AWS DevOps

Code Commit

Code Pipeline

Code Deploy

Code Build

Cyan Monster

GCP DevOps

Cloud Source Repository

Cloud Container Registry

Cloud Build

Questions ?

UPCOMING MEETUP

Check out our event page

Stay tuned for what’s coming next!

​