victoriia basarab - special aspects of dev ops platform development
•
0 likes•135 views
Victoria Basarab discussed different approaches to developing a DevOps platform and highlighted a hybrid model. She outlined three cases: 1) where bad processes transform DevOps into just operations work, 2) where the DevOps team works isolated in a Scrum model, and 3) where the DevOps team understands product needs and builds solutions to meet them. The best approach balances focused iterative development from Scrumban with feedback from development teams and knowledge transfer. A DevOps platform should evolve quickly but be refactored constantly to meet changing needs.
Report
Share
Report
Share
Download to read offline
Recommended
Chris Homer - Moving the entire stack to k8s within a year – lessons learned
1) The document discusses lessons learned from thredUP's experience migrating their entire infrastructure stack to Kubernetes over the course of a year.
2) Some key challenges included addressing performance issues, DNS errors, and pod distribution after cluster maintenance.
3) Migrating to Kubernetes provided benefits like halving deployment times, making rollbacks fast and easy, and decreasing hardware provisioning costs.
DevOps with OpenShift - Fabien Dupont - ManageIQ Design Summit 2016
This document discusses DevOps workflows using OpenShift and ManageIQ. It describes using GitLab for source code management, CI/CD, and collaboration. OpenShift is used as a platform for deploying and managing containerized applications. ManageIQ orchestrates provisioning of the DevOps tools including FreeIPA for authentication, GitLab, and OpenShift. The ecosystem is integrated through a CI/CD pipeline that builds, tests, reviews, and deploys code changes from a Git repository to OpenShift.
vodQA Pune (2019) - Jenkins pipeline As code
This document discusses Jenkins pipeline as code. It provides an overview of continuous integration and continuous delivery practices. It introduces Jenkins and describes its project types including freestyle and pipeline. Key benefits of using Jenkins pipeline are that the pipeline is implemented as code in source control, is durable across Jenkins restarts, and is extensible. The document contrasts scripted and declarative pipeline syntax. It also discusses using Jenkins Job Builder to configure Jenkins jobs from YAML/JSON templates. The presenters provide their contact information for any questions.
Meetup Devops-Geneva-19.10.2019
Bonjour à tous,
Pour ce meetup, nous avons la chance d'être reçu dans les locaux de Richemont.
Je remercie particulièrement Cédric Georg ainsi que l'équipe de Richemont pour leur accueil.
A ce meetup DevOps, nous aurons 2 Retours d'Expérience, voici l'agenda de la soirée:
18:30 - Ouverture des portes
(il faudra donner votre nom et prénom ainsi que votre numéro de plaque d'immatriculation si vous êtes venu en voiture, c'est pour la sécurité, et oui, on ne rigole pas ici :-))
18:50 - Introduction de Matthieu et de Cédric
19:00 - Richemont et sa transformation DevOps
Richemont, fort de sa transformation digitale, a dû s'adapter afin de faire travailler ensemble, avec des outils d'automatisation et de communication, les équipes de développeurs et les équipes opérationnelles.
Squad, DevOps, Tests, Sécurité, Agile et Scrum, comment tous ces termes ont sû devenir le quotidien de Richemont en seulement quelques années.
Nous verrons comment nous avons mis cela en place, quels ont été les points positifs et négatifs de cette transformation.
19:40 - SixSq et l'automatisation du docker sur des edge points (DEMO)
Edge computing is gaining in popularity to address the explosion of data produced by IoT sensors, and the need to better manage AI both in the cloud and at the edge. To address this paradigm shift, SixSq has launched two open source projects: Nuvla for managing applications, and NuvlaBox, a cloud-in-a-box edge solution.
Using these open source projects, in this session we'll demonstrate how edge computing can now be integrated to agnostically operate containerized applications on CaaS infrastructures anywhere, using a Raspberry Pi-based platform.
CICD with Jenkins
This document discusses Continuous Integration/Continuous Delivery (CICD) with Jenkins. It begins with an introduction to how developing and releasing software can be complicated. It then provides an overview of CICD, including that continuous integration verifies new changes through testing, continuous delivery enables continuous deployment to production, and continuous deployment automatically deploys all passed changes. The document discusses how Jenkins is an open-source automation server that helps automate the software development process for CICD. It concludes with best practices for Jenkins, such as high availability, sizing Jenkins machines appropriately, and organizing pipelines and jobs.
Reproducible development to live applications with Red Hat CDK and Red Hat Op...
Reproducible development to live applications with Red Hat Container Development Kit and Red Hat OpenShift Application Runtime
Docker Dhahran Nov 2016 meetup
Docker "Global Mentor Week" is your opportunity to #learndocker. to learn how to build, ship, and run modern distributed applications with ease. thanks to the Docker platform.
Right now, Docker has developed out a series of self-paced online labs that will be available during the meetup. Docker’s meetup groups worldwide are hosting a series of complimentary events to help newcomers and intermediate users learn Docker.
We'll have hands-on labs for both beginners and intermediate users, labs targeting both developers and operations. There is something for everyone. Docker mentor will be on hand at this event to help you prepare. and work through the self-paced materials. Bring your laptop, have fun and learn Docker!
OpenShift As A DevOps Platform
OpenShift is a DevOps platform that provides a container application platform for deploying and managing containerized applications and microservices. It uses Kubernetes for orchestration and Docker containers. OpenShift provides features for the complete application lifecycle including continuous integration/delivery (CI/CD), automated image builds, deployments, networking, authentication, and integration with external services and registries. Developers can create and deploy applications from source code, templates, or Docker images to OpenShift without needing deep knowledge of Docker or Kubernetes.
Recommended
Chris Homer - Moving the entire stack to k8s within a year – lessons learned
1) The document discusses lessons learned from thredUP's experience migrating their entire infrastructure stack to Kubernetes over the course of a year.
2) Some key challenges included addressing performance issues, DNS errors, and pod distribution after cluster maintenance.
3) Migrating to Kubernetes provided benefits like halving deployment times, making rollbacks fast and easy, and decreasing hardware provisioning costs.
DevOps with OpenShift - Fabien Dupont - ManageIQ Design Summit 2016
This document discusses DevOps workflows using OpenShift and ManageIQ. It describes using GitLab for source code management, CI/CD, and collaboration. OpenShift is used as a platform for deploying and managing containerized applications. ManageIQ orchestrates provisioning of the DevOps tools including FreeIPA for authentication, GitLab, and OpenShift. The ecosystem is integrated through a CI/CD pipeline that builds, tests, reviews, and deploys code changes from a Git repository to OpenShift.
vodQA Pune (2019) - Jenkins pipeline As code
This document discusses Jenkins pipeline as code. It provides an overview of continuous integration and continuous delivery practices. It introduces Jenkins and describes its project types including freestyle and pipeline. Key benefits of using Jenkins pipeline are that the pipeline is implemented as code in source control, is durable across Jenkins restarts, and is extensible. The document contrasts scripted and declarative pipeline syntax. It also discusses using Jenkins Job Builder to configure Jenkins jobs from YAML/JSON templates. The presenters provide their contact information for any questions.
Meetup Devops-Geneva-19.10.2019
Bonjour à tous,
Pour ce meetup, nous avons la chance d'être reçu dans les locaux de Richemont.
Je remercie particulièrement Cédric Georg ainsi que l'équipe de Richemont pour leur accueil.
A ce meetup DevOps, nous aurons 2 Retours d'Expérience, voici l'agenda de la soirée:
18:30 - Ouverture des portes
(il faudra donner votre nom et prénom ainsi que votre numéro de plaque d'immatriculation si vous êtes venu en voiture, c'est pour la sécurité, et oui, on ne rigole pas ici :-))
18:50 - Introduction de Matthieu et de Cédric
19:00 - Richemont et sa transformation DevOps
Richemont, fort de sa transformation digitale, a dû s'adapter afin de faire travailler ensemble, avec des outils d'automatisation et de communication, les équipes de développeurs et les équipes opérationnelles.
Squad, DevOps, Tests, Sécurité, Agile et Scrum, comment tous ces termes ont sû devenir le quotidien de Richemont en seulement quelques années.
Nous verrons comment nous avons mis cela en place, quels ont été les points positifs et négatifs de cette transformation.
19:40 - SixSq et l'automatisation du docker sur des edge points (DEMO)
Edge computing is gaining in popularity to address the explosion of data produced by IoT sensors, and the need to better manage AI both in the cloud and at the edge. To address this paradigm shift, SixSq has launched two open source projects: Nuvla for managing applications, and NuvlaBox, a cloud-in-a-box edge solution.
Using these open source projects, in this session we'll demonstrate how edge computing can now be integrated to agnostically operate containerized applications on CaaS infrastructures anywhere, using a Raspberry Pi-based platform.
CICD with Jenkins
This document discusses Continuous Integration/Continuous Delivery (CICD) with Jenkins. It begins with an introduction to how developing and releasing software can be complicated. It then provides an overview of CICD, including that continuous integration verifies new changes through testing, continuous delivery enables continuous deployment to production, and continuous deployment automatically deploys all passed changes. The document discusses how Jenkins is an open-source automation server that helps automate the software development process for CICD. It concludes with best practices for Jenkins, such as high availability, sizing Jenkins machines appropriately, and organizing pipelines and jobs.
Reproducible development to live applications with Red Hat CDK and Red Hat Op...
Reproducible development to live applications with Red Hat Container Development Kit and Red Hat OpenShift Application Runtime
Docker Dhahran Nov 2016 meetup
Docker "Global Mentor Week" is your opportunity to #learndocker. to learn how to build, ship, and run modern distributed applications with ease. thanks to the Docker platform.
Right now, Docker has developed out a series of self-paced online labs that will be available during the meetup. Docker’s meetup groups worldwide are hosting a series of complimentary events to help newcomers and intermediate users learn Docker.
We'll have hands-on labs for both beginners and intermediate users, labs targeting both developers and operations. There is something for everyone. Docker mentor will be on hand at this event to help you prepare. and work through the self-paced materials. Bring your laptop, have fun and learn Docker!
OpenShift As A DevOps Platform
OpenShift is a DevOps platform that provides a container application platform for deploying and managing containerized applications and microservices. It uses Kubernetes for orchestration and Docker containers. OpenShift provides features for the complete application lifecycle including continuous integration/delivery (CI/CD), automated image builds, deployments, networking, authentication, and integration with external services and registries. Developers can create and deploy applications from source code, templates, or Docker images to OpenShift without needing deep knowledge of Docker or Kubernetes.
Hands-on GitOps Patterns for Helm Users
This document provides an overview of a presentation on hands-on GitOps patterns for Helm users. Some key points:
- The presentation will cover why Helm patterns are useful for Flux and how Flux and Helm work better together.
- It will demonstrate moving Helm releases from CI to Flux continuous delivery, including common use cases, features, and pitfalls to avoid.
- There will be a live demo of an example using infrastructure and application definitions colocated in Git.
- The presentation aims to provide a good starting point for adopting GitOps with Flux and Helm. It will explain how Flux controllers automatically reconcile source definitions with cluster state.
從系統思考看 DevOps：以 microservices 為例 (DevOps: a system dynamics perspective)
Presented at DevOps Taiwan Meetup #8 (2017-10-26).
Recording (about 90 minutes): https://www.youtube.com/watch?v=zMeA3CjOi60
Introduction:
台灣第一次舉辦的 DevOpsDays Taipei，涵蓋許多精彩的文化與技術議題。
大會中，許多講者不約而同提到「系統思考」的概念，這是什麼？許多講者也提到 microservices 的重要性，但為什麼許多人想導入，卻鍛羽而歸？
此演講以系統思考的 causal loop diagram 角度，探討 microservices 常見的導入誤區：意外的敵人 (accidental adversaries) 及捨本逐末 (shifting the burden) ，並根據系統基模角度提出對應的槓桿解。
希望你聽了之後，能夠初步掌握系統思考的切入點，也對於 microservices 導入，多了一分把握。
提醒：建議先複習一下 Andrew Wu 在【DevOps Taiwan Meetup #4 (2017/02/22) - 這一夜讓我們來聊聊 Microservices】的內容：
- https://goo.gl/Drfeiw
- https://goo.gl/zXkESo
jSpring 2018 "Continuous Delivery Patterns for Modern Architectures and Java"
This document discusses continuous delivery patterns for modern architectures and Java. It covers topics like moving from complicated to complex systems, how architecture is becoming more about technical leadership, and encoding all requirements into a continuous delivery pipeline. It also discusses challenges with modern app architectures like multiple services/pipelines, independent service deployment, and evolving architecture. Continuous delivery, testing microservice integration, contracting testing, and measuring what matters are also covered.
Cloud agnostic continuous quality assurance
The document discusses implementing cloud agnostic continuous quality assurance. It recommends using common tools like source control (Gerrit), build automation (Jenkins), code review, and code quality analysis (SonarQube) to ensure quality and allow moving projects between cloud providers. These tools were demonstrated working together using Docker containers to provide continuous quality assurance in a cloud agnostic manner. The document emphasizes automating as much as possible and having processes to enforce coding standards and measure quality.
CQRS - Eine Einführung - NOUG 2011
1) CQRS is an architectural pattern that separates read and write operations into different models. This allows for optimized read and write models and behaviors.
2) The basic CQRS architecture involves separating the read and write concerns into different layers - a thin read layer for optimized querying and presentation, a domain model for business logic and validation, and command handlers that process commands to enact changes.
3) CQRS does not require eventual consistency - the read and write models can be kept perfectly consistent through mechanisms like event sourcing that propagate write events to the read models.
Common blind spots on the journey to production vijay raghavan aravamudhan
Common Blindspots on the Journey to Production and Beyond- Presented at XP Conference India 2015 by Vijay Raghavan Aravamudhan
Multi-container Applications on OpenShift with the Ansible Service Broker Mul...
The Kubernetes/OpenShift Service Catalog and Open Service Broker API are creating a new way for users to provision and manage services on Kubernetes/OpenShift through a collection of Service Brokers. One of these brokers, the Ansible Service Broker, is focused on providing a mechanism for allowing applications defined with Ansible to be exposed to the Service Catalog. We call this application definition an Ansible Playbook Bundle (APB); a lightweight definition that is essentially a few Ansible playbooks named for each of the Open Service Broker API methods. The bundle is packaged as a container image with an Ansible runtime for distribution to be consumed by the Ansible Service Broker. In this talk we will introduce the concept of the Ansible Playbook Bundle and Ansible Service Broker. Additionally, we will walk through a few example and live demo demonstrating how to define and deploy multi-container applications.
Puzzle ITC Talk @Docker CH meetup CI CD_with_Openshift_0.2
This document discusses continuous delivery using OpenShift. It begins with an overview of OpenShift v3, including that it is a container platform as a service based on Docker and Kubernetes. It then covers key concepts in continuous integration and continuous delivery like automated database migrations and rolling updates. Finally, it provides an example of setting up a continuous integration/continuous delivery pipeline in OpenShift using Jenkins, including building and deploying a Java/Maven application through various stages.
Setting up Notifications, Alerts & Webhooks with Flux v2 by Alison Dowdney
Watch the recording here: https://youtu.be/cakxixc-yQk
❗️ Notifications & Alerts ⚠️
When operating a cluster, different teams may wish to receive notifications about the status of their GitOps pipelines. For example, the on-call team would receive alerts about reconciliation failures in the cluster, while the dev team may wish to be alerted when a new version of an app was deployed and if the deployment is healthy.
Webhook Receivers
The GitOps toolkit controllers are by design pull-based. In order to notify the controllers about changes in Git or Helm repositories, you can setup webhooks and trigger a cluster reconciliation every time a source changes. Using webhook receivers, you can build push-based GitOps pipelines that react to external events.
Alison Dowdney, Developer Experience Engineer at Weaveworks and CNCF Ambassador, walks through how to define a provider, an alert, git commit status, exposing the webhook receiver and defining a git repository and receiver.
Resources
Flux2 Documentation: https://fluxcd.io/docs/
Flux Guide: Setup Notifications: https://fluxcd.io/docs/guides/notifications/
Flux Guide: Setup Webhook receivers: https://fluxcd.io/docs/guides/webhook-receivers/
Flux Roadmap: https://fluxcd.io/docs/roadmap/
Alison's Demo Repo: https://github.com/alisondy/flux-demos
Enabling Cloud Native Buildpacks for Windows Containers
SpringOne 2020
Daniella Corricelli: Product Manager, VMware;
Malini Valliath: Member of Technical Staff, VMware;
Micah Young: Software Engineer, VMware;
Andrew Meyer: Software Engineer, VMware
Jelastic Docker Orchestrator
Meetup presentation of Jelastic as Docker orchestrator. You will be able to deploy a docker environment from this presentation on Hidora cloud provider based in Switzerland.
VOLODYMYR TSAP, BAQ, "CI/CD Infrastructure as a Code"
This document discusses CI/CD infrastructure as code and describes a proposed internal product called DJEG, which stands for Docker Jenkins Elasticsearch Grafana. DJEG is presented as a complete CI/CD development platform that can be deployed in 15 minutes, compared to 3-6 months to build such a system from scratch. It is based on open source tools like Jenkins, Nexus, Elasticsearch, Grafana, and integrates them with features like centralized user management, logging, monitoring, and alerting. The implementation focuses on an infrastructure as code approach and using templates to simplify deploying the system across platforms like AWS, GCP, Kubernetes, and Azure.
Perforce Innovations Showcase
Innovation at Perforce never stops. Since the last MERGE conference, there have been continual updates across the board in response to user requests. In this session, we're going to look at what's new and take a peek at what's in the works so that you can start planning to exploit them when they're available.
Aws ug dxb 2021 container series iv
AWS user group meetup container series DXB Dubai
n this session, we will explore the popular workload manager and scheduler Kubernetes. Amazon managed kubernetes service, Elastic Container Service for Kubernetes (Amazon EKS) takes care of the heavy-lifting and lets one focus on managing the containerized workloads. EKS, however, still gives you the flexibility and choice where to run, and how to efficiently run your data-plane that hosts your workloads. In this session, we cover what you need to know to get your application up and running with Kubernetes on AWS. We show how Amazon EKS makes deploying Kubernetes on AWS simple and scalable.
⏳ Agenda
1- Review the general Kubernetes architecture and relate to EKS
2- How to set up and provision your Kubernetes cluster using console and eksctl.
3- Discuss the important abstractions that developers use to map their traditional application into any kubernetes platform.
4- How to deploy software efficiently, while sustaining reliable and scalable applications.
5- Deploy your first microservices on EKS
6- EKS possible development deployment workflow
ApacheCon Europe 2016 : CONTAINERS IN ACTION - Transform Application Delivery...
The document discusses DevOps and the use of containers and Docker for building and deploying applications. It describes how traditionally infrastructure and applications were separate domains managed by different teams, but with DevOps these are combined. Docker allows building each component of an application as a separate containerized microservice that can be linked and deployed together. The document provides examples of using Docker commands to build and run containers for different tiers of an application and linking them together. It promotes trying OpenShift as a hosted container application platform for implementing DevOps.
QCon SF 2017 - Microservices: Service-Oriented Development
Conventional wisdom is that microservices is an architecture that is the spiritual successor to service-oriented architecture. While true, this myopic view of microservices ignores some of the profound workflow shifts in today’s microservices organizations.
The reality is that microservices is an architecture _and_ workflow. In this talk, we’ll introduce the workflow of service-oriented development. Rafael will talk about how the real goal of microservices is to break up a monolithic development workflow. We’ll show you how, by breaking up your workflow, you can build software that lets you move fast and make things.
[RHFSeoul2017]6 Steps to Transform Enterprise Applications
The document provides a 6 step approach to transforming enterprise applications:
1. Re-organizing to DevOps;
2. Implementing self-service, on-demand infrastructure;
3. Automating deployments using tools like Puppet, Chef, and Kubernetes;
4. Establishing continuous integration and deployment pipelines;
5. Adopting advanced deployment techniques like blue-green deployments;
6. Moving to a microservices architecture.
Кирилл Толкачев. Микросервисы: огонь, вода и девопс
The document discusses microservices and distributed tracing. It notes that without distributed tracing, it can be difficult to trace requests across multiple services to understand where delays are occurring. It then shows how distributed tracing works, with services adding tracing identifiers to logs and calls to other services to enable correlating logs and traces from all involved services for a single request. This allows generating a single, unified trace to understand end-to-end request performance across multiple microservices.
Jfrog artifactory artifact management c tamilmaran presentation - copy
JFrog Artifactory is an artifact management tool that allows users to store, manage, and distribute software artifacts. It supports all major package formats and integrates with various DevOps tools and technologies. JFrog Artifactory provides a single place to manage binaries for continuous integration and deployment pipelines. It offers features like access control, high availability, security analysis, and integration with tools like Jenkins, Docker, and Kubernetes.
LV Dev Efficiency NIDays 2015
The presentation discussed various tools and techniques for improving LabVIEW development efficiency, including project templates, frameworks, and tools available in LabVIEW and from third parties. It covered using project templates to standardize projects, frameworks to provide common functionality and communication mechanisms, and tools for version control, debugging, and more. The presentation emphasized building proficiency through training courses and online resources like blogs, forums, and conferences to continuously improve development skills and efficiency.
DevOps Days Kyiv 2019 -- DevOps platform development - lessons learned // Vic...
The document discusses lessons learned from developing a DevOps platform. It notes that businesses expect the platform to never break down, be highly available, automatically scale to meet demand, have automated infrastructure and CI/CD pipelines covered by tests, and permanently meet all developer requirements without needing support. The solution architect questioned how realistic these expectations were. It suggests formalizing a knowledge sharing process and checklist to transfer DevOps knowledge and responsibilities from the DevOps team to development teams as the DevOps toolkit evolves rapidly.
Dev-HRE-Ops - Addressing the _Last Mile DevOps Challenge_ in Highly Regulated...
Slides from our DevOps World 2021 Session entitled Dev-HRE-Ops Addressing the Last Mile DevOps Challenge in Highly Regulated Environments
More Related Content
What's hot
Hands-on GitOps Patterns for Helm Users
This document provides an overview of a presentation on hands-on GitOps patterns for Helm users. Some key points:
- The presentation will cover why Helm patterns are useful for Flux and how Flux and Helm work better together.
- It will demonstrate moving Helm releases from CI to Flux continuous delivery, including common use cases, features, and pitfalls to avoid.
- There will be a live demo of an example using infrastructure and application definitions colocated in Git.
- The presentation aims to provide a good starting point for adopting GitOps with Flux and Helm. It will explain how Flux controllers automatically reconcile source definitions with cluster state.
從系統思考看 DevOps：以 microservices 為例 (DevOps: a system dynamics perspective)
Presented at DevOps Taiwan Meetup #8 (2017-10-26).
Recording (about 90 minutes): https://www.youtube.com/watch?v=zMeA3CjOi60
Introduction:
台灣第一次舉辦的 DevOpsDays Taipei，涵蓋許多精彩的文化與技術議題。
大會中，許多講者不約而同提到「系統思考」的概念，這是什麼？許多講者也提到 microservices 的重要性，但為什麼許多人想導入，卻鍛羽而歸？
此演講以系統思考的 causal loop diagram 角度，探討 microservices 常見的導入誤區：意外的敵人 (accidental adversaries) 及捨本逐末 (shifting the burden) ，並根據系統基模角度提出對應的槓桿解。
希望你聽了之後，能夠初步掌握系統思考的切入點，也對於 microservices 導入，多了一分把握。
提醒：建議先複習一下 Andrew Wu 在【DevOps Taiwan Meetup #4 (2017/02/22) - 這一夜讓我們來聊聊 Microservices】的內容：
- https://goo.gl/Drfeiw
- https://goo.gl/zXkESo
jSpring 2018 "Continuous Delivery Patterns for Modern Architectures and Java"
This document discusses continuous delivery patterns for modern architectures and Java. It covers topics like moving from complicated to complex systems, how architecture is becoming more about technical leadership, and encoding all requirements into a continuous delivery pipeline. It also discusses challenges with modern app architectures like multiple services/pipelines, independent service deployment, and evolving architecture. Continuous delivery, testing microservice integration, contracting testing, and measuring what matters are also covered.
Cloud agnostic continuous quality assurance
The document discusses implementing cloud agnostic continuous quality assurance. It recommends using common tools like source control (Gerrit), build automation (Jenkins), code review, and code quality analysis (SonarQube) to ensure quality and allow moving projects between cloud providers. These tools were demonstrated working together using Docker containers to provide continuous quality assurance in a cloud agnostic manner. The document emphasizes automating as much as possible and having processes to enforce coding standards and measure quality.
CQRS - Eine Einführung - NOUG 2011
1) CQRS is an architectural pattern that separates read and write operations into different models. This allows for optimized read and write models and behaviors.
2) The basic CQRS architecture involves separating the read and write concerns into different layers - a thin read layer for optimized querying and presentation, a domain model for business logic and validation, and command handlers that process commands to enact changes.
3) CQRS does not require eventual consistency - the read and write models can be kept perfectly consistent through mechanisms like event sourcing that propagate write events to the read models.
Common blind spots on the journey to production vijay raghavan aravamudhan
Common Blindspots on the Journey to Production and Beyond- Presented at XP Conference India 2015 by Vijay Raghavan Aravamudhan
Multi-container Applications on OpenShift with the Ansible Service Broker Mul...
The Kubernetes/OpenShift Service Catalog and Open Service Broker API are creating a new way for users to provision and manage services on Kubernetes/OpenShift through a collection of Service Brokers. One of these brokers, the Ansible Service Broker, is focused on providing a mechanism for allowing applications defined with Ansible to be exposed to the Service Catalog. We call this application definition an Ansible Playbook Bundle (APB); a lightweight definition that is essentially a few Ansible playbooks named for each of the Open Service Broker API methods. The bundle is packaged as a container image with an Ansible runtime for distribution to be consumed by the Ansible Service Broker. In this talk we will introduce the concept of the Ansible Playbook Bundle and Ansible Service Broker. Additionally, we will walk through a few example and live demo demonstrating how to define and deploy multi-container applications.
Puzzle ITC Talk @Docker CH meetup CI CD_with_Openshift_0.2
This document discusses continuous delivery using OpenShift. It begins with an overview of OpenShift v3, including that it is a container platform as a service based on Docker and Kubernetes. It then covers key concepts in continuous integration and continuous delivery like automated database migrations and rolling updates. Finally, it provides an example of setting up a continuous integration/continuous delivery pipeline in OpenShift using Jenkins, including building and deploying a Java/Maven application through various stages.
Setting up Notifications, Alerts & Webhooks with Flux v2 by Alison Dowdney
Watch the recording here: https://youtu.be/cakxixc-yQk
❗️ Notifications & Alerts ⚠️
When operating a cluster, different teams may wish to receive notifications about the status of their GitOps pipelines. For example, the on-call team would receive alerts about reconciliation failures in the cluster, while the dev team may wish to be alerted when a new version of an app was deployed and if the deployment is healthy.
Webhook Receivers
The GitOps toolkit controllers are by design pull-based. In order to notify the controllers about changes in Git or Helm repositories, you can setup webhooks and trigger a cluster reconciliation every time a source changes. Using webhook receivers, you can build push-based GitOps pipelines that react to external events.
Alison Dowdney, Developer Experience Engineer at Weaveworks and CNCF Ambassador, walks through how to define a provider, an alert, git commit status, exposing the webhook receiver and defining a git repository and receiver.
Resources
Flux2 Documentation: https://fluxcd.io/docs/
Flux Guide: Setup Notifications: https://fluxcd.io/docs/guides/notifications/
Flux Guide: Setup Webhook receivers: https://fluxcd.io/docs/guides/webhook-receivers/
Flux Roadmap: https://fluxcd.io/docs/roadmap/
Alison's Demo Repo: https://github.com/alisondy/flux-demos
Enabling Cloud Native Buildpacks for Windows Containers
SpringOne 2020
Daniella Corricelli: Product Manager, VMware;
Malini Valliath: Member of Technical Staff, VMware;
Micah Young: Software Engineer, VMware;
Andrew Meyer: Software Engineer, VMware
Jelastic Docker Orchestrator
Meetup presentation of Jelastic as Docker orchestrator. You will be able to deploy a docker environment from this presentation on Hidora cloud provider based in Switzerland.
VOLODYMYR TSAP, BAQ, "CI/CD Infrastructure as a Code"
This document discusses CI/CD infrastructure as code and describes a proposed internal product called DJEG, which stands for Docker Jenkins Elasticsearch Grafana. DJEG is presented as a complete CI/CD development platform that can be deployed in 15 minutes, compared to 3-6 months to build such a system from scratch. It is based on open source tools like Jenkins, Nexus, Elasticsearch, Grafana, and integrates them with features like centralized user management, logging, monitoring, and alerting. The implementation focuses on an infrastructure as code approach and using templates to simplify deploying the system across platforms like AWS, GCP, Kubernetes, and Azure.
Perforce Innovations Showcase
Innovation at Perforce never stops. Since the last MERGE conference, there have been continual updates across the board in response to user requests. In this session, we're going to look at what's new and take a peek at what's in the works so that you can start planning to exploit them when they're available.
Aws ug dxb 2021 container series iv
AWS user group meetup container series DXB Dubai
n this session, we will explore the popular workload manager and scheduler Kubernetes. Amazon managed kubernetes service, Elastic Container Service for Kubernetes (Amazon EKS) takes care of the heavy-lifting and lets one focus on managing the containerized workloads. EKS, however, still gives you the flexibility and choice where to run, and how to efficiently run your data-plane that hosts your workloads. In this session, we cover what you need to know to get your application up and running with Kubernetes on AWS. We show how Amazon EKS makes deploying Kubernetes on AWS simple and scalable.
⏳ Agenda
1- Review the general Kubernetes architecture and relate to EKS
2- How to set up and provision your Kubernetes cluster using console and eksctl.
3- Discuss the important abstractions that developers use to map their traditional application into any kubernetes platform.
4- How to deploy software efficiently, while sustaining reliable and scalable applications.
5- Deploy your first microservices on EKS
6- EKS possible development deployment workflow
ApacheCon Europe 2016 : CONTAINERS IN ACTION - Transform Application Delivery...
The document discusses DevOps and the use of containers and Docker for building and deploying applications. It describes how traditionally infrastructure and applications were separate domains managed by different teams, but with DevOps these are combined. Docker allows building each component of an application as a separate containerized microservice that can be linked and deployed together. The document provides examples of using Docker commands to build and run containers for different tiers of an application and linking them together. It promotes trying OpenShift as a hosted container application platform for implementing DevOps.
QCon SF 2017 - Microservices: Service-Oriented Development
Conventional wisdom is that microservices is an architecture that is the spiritual successor to service-oriented architecture. While true, this myopic view of microservices ignores some of the profound workflow shifts in today’s microservices organizations.
The reality is that microservices is an architecture _and_ workflow. In this talk, we’ll introduce the workflow of service-oriented development. Rafael will talk about how the real goal of microservices is to break up a monolithic development workflow. We’ll show you how, by breaking up your workflow, you can build software that lets you move fast and make things.
[RHFSeoul2017]6 Steps to Transform Enterprise Applications
The document provides a 6 step approach to transforming enterprise applications:
1. Re-organizing to DevOps;
2. Implementing self-service, on-demand infrastructure;
3. Automating deployments using tools like Puppet, Chef, and Kubernetes;
4. Establishing continuous integration and deployment pipelines;
5. Adopting advanced deployment techniques like blue-green deployments;
6. Moving to a microservices architecture.
Кирилл Толкачев. Микросервисы: огонь, вода и девопс
The document discusses microservices and distributed tracing. It notes that without distributed tracing, it can be difficult to trace requests across multiple services to understand where delays are occurring. It then shows how distributed tracing works, with services adding tracing identifiers to logs and calls to other services to enable correlating logs and traces from all involved services for a single request. This allows generating a single, unified trace to understand end-to-end request performance across multiple microservices.
Jfrog artifactory artifact management c tamilmaran presentation - copy
JFrog Artifactory is an artifact management tool that allows users to store, manage, and distribute software artifacts. It supports all major package formats and integrates with various DevOps tools and technologies. JFrog Artifactory provides a single place to manage binaries for continuous integration and deployment pipelines. It offers features like access control, high availability, security analysis, and integration with tools like Jenkins, Docker, and Kubernetes.
LV Dev Efficiency NIDays 2015
The presentation discussed various tools and techniques for improving LabVIEW development efficiency, including project templates, frameworks, and tools available in LabVIEW and from third parties. It covered using project templates to standardize projects, frameworks to provide common functionality and communication mechanisms, and tools for version control, debugging, and more. The presentation emphasized building proficiency through training courses and online resources like blogs, forums, and conferences to continuously improve development skills and efficiency.
What's hot (20)
從系統思考看 DevOps：以 microservices 為例 (DevOps: a system dynamics perspective)
從系統思考看 DevOps：以 microservices 為例 (DevOps: a system dynamics perspective)
jSpring 2018 "Continuous Delivery Patterns for Modern Architectures and Java"
jSpring 2018 "Continuous Delivery Patterns for Modern Architectures and Java"
Common blind spots on the journey to production vijay raghavan aravamudhan
Common blind spots on the journey to production vijay raghavan aravamudhan
Multi-container Applications on OpenShift with the Ansible Service Broker Mul...
Multi-container Applications on OpenShift with the Ansible Service Broker Mul...
Puzzle ITC Talk @Docker CH meetup CI CD_with_Openshift_0.2
Puzzle ITC Talk @Docker CH meetup CI CD_with_Openshift_0.2
Setting up Notifications, Alerts & Webhooks with Flux v2 by Alison Dowdney
Setting up Notifications, Alerts & Webhooks with Flux v2 by Alison Dowdney
Enabling Cloud Native Buildpacks for Windows Containers
Enabling Cloud Native Buildpacks for Windows Containers
VOLODYMYR TSAP, BAQ, "CI/CD Infrastructure as a Code"
VOLODYMYR TSAP, BAQ, "CI/CD Infrastructure as a Code"
ApacheCon Europe 2016 : CONTAINERS IN ACTION - Transform Application Delivery...
ApacheCon Europe 2016 : CONTAINERS IN ACTION - Transform Application Delivery...
QCon SF 2017 - Microservices: Service-Oriented Development
QCon SF 2017 - Microservices: Service-Oriented Development
[RHFSeoul2017]6 Steps to Transform Enterprise Applications
[RHFSeoul2017]6 Steps to Transform Enterprise Applications
Кирилл Толкачев. Микросервисы: огонь, вода и девопс
Кирилл Толкачев. Микросервисы: огонь, вода и девопс
Jfrog artifactory artifact management c tamilmaran presentation - copy
Jfrog artifactory artifact management c tamilmaran presentation - copy
Similar to victoriia basarab - special aspects of dev ops platform development
DevOps Days Kyiv 2019 -- DevOps platform development - lessons learned // Vic...
The document discusses lessons learned from developing a DevOps platform. It notes that businesses expect the platform to never break down, be highly available, automatically scale to meet demand, have automated infrastructure and CI/CD pipelines covered by tests, and permanently meet all developer requirements without needing support. The solution architect questioned how realistic these expectations were. It suggests formalizing a knowledge sharing process and checklist to transfer DevOps knowledge and responsibilities from the DevOps team to development teams as the DevOps toolkit evolves rapidly.
Dev-HRE-Ops - Addressing the _Last Mile DevOps Challenge_ in Highly Regulated...
Slides from our DevOps World 2021 Session entitled Dev-HRE-Ops Addressing the Last Mile DevOps Challenge in Highly Regulated Environments
Solving the Automation Puzzle - how to select the right automation framework ...
From open source to commercial tools - how we selected the right tool for our automation framework in several projects and products in HPE Software.
Selecting the right automation framework is hard. Today, there are so many possibilities. From open source solutions (Selenium Appium, etc.), to our own developed commercial tools (QTP, UFT, Mobile Center) What was the process that we do in order to select the right automation framework. Our approach was to 1st define our needs from such a framework and we ended up with a list of 10 must have requirements for such a framework and then went on to pick the right tool. We ended up with different frameworks for different projects with a wide combinations of open source (yes, we at HP use open source) to our own tools (UFT, LeanFT, etc.)
"Platform Engineering in practice — Why and How to start", Serg Hospodarets
The tech industry went from IT to DevOps, and Platform Engineering showed it well to enable effective software products development.
Serg with his teams re-architected and delivered a few Web Cloud Platforms, and applied engineering reorganizations, to improve companies’ products delivery.
It was done at scale- a few hundred engineers and operations, dozens of products, hundreds of microservices and customers.
This talk aims to share the experience and learned practices, including practical technical tooling suggestions, processes, and team organization tips. And, of course, live and coding demos.
tip oopt pse-summit2017
Optical Planning Tool, Common-AP. First Open Source Optical Planner for Packet-Optical integration and Multi-Layer Optimization
An Introduction to Microservices
Another day, another buzzword in the world of software development! ‘Microservices’ is a new approach to structuring server-side software. But is it really new? In this talk I’ll walk you through the birth and ‘raison d’etre’ of microservices and tell about pro’s and con’s of the approach.
Having laid the foundation, we will take a look at best-practices and patterns for building micro service architectures and combine this with a tour of current technologies and development tools.
Finally, I will take a quick look at the future and discuss some of the remaining challenges. All parts of the presentation will be accompanied by structural examples based on a real ecommerse system.
DevOps@Morpho in 2014
Overview of DevOps implementation at Morpho in 2014
(Created on 2014-11-12 ; Updated slide 28 with new statistics on 2014-12-07)
(Updated my selfie... on 2015-07-11)
A Story of Cultural Change: PayPal's 2 Year Journey to 150,000 Containers wit...
Adopting containers at scale is fundamentally a cultural change. In late 2015, PayPal decided to migrate en masse to containers for applications built on many different frameworks over the last 15 years. It was a bold and strategic plan that included how to showcase value of containers to leadership, a phased execution strategy, building the right team to lead, and cultural transformation. Changing application code, deployment methods, and operational tools were at onset non-negotiable. This session will share how the plan was pitched and the learnings that unfolded as PayPal carefully changed everything - and nothing at the same time - to get to 150,000 containers running in production in 2 years.
How to setup a development environment for ONAP
Presentation used during the ONAP session
https://onapbeijing2017.sched.com/event/D5q3/how-to-setup-a-development-environment-for-onap
Choosing Automation for DevOps & Continuous Delivery in the Enterprise
Andrew Phillips' slides from the "Leading the IT Transformation" events in Boston, New York, and Austin, with Gary Gruver.
Dev Ops for systems of record - Talk at Agile Australia 2015
Mirco Hering is a DevOps and Agile lead with over 10 years of experience improving IT delivery through automation, methodology, and innovation. The document discusses applying DevOps principles to systems of record like packaged software, non-custom code, and older custom code. It outlines challenges in automating builds, deployments, testing and integrating these systems. It provides examples of automating merges and traceability for a Siebel system to help systems of record adopt DevOps practices and continuous delivery.
Dev ops
The document discusses the Software Development Life Cycle (SDLC) and DevOps. It defines SDLC as a process used by the software industry to design, develop, and test high-quality software. SDLC aims to produce software that meets expectations within time and cost estimates. The document then discusses DevOps, defining it as a culture promoting collaboration between development and operations teams to deploy code to production faster using automation. It outlines the DevOps lifecycle and principles, why DevOps is needed to streamline the software delivery process, and tools used in DevOps.
Orchestrate Your End-to-end Mainframe Application Release Pipeline
What steel and concrete are to a skyscraper, the mainframe is to the global economy. The mainframe is the transactional backbone for 96 of the world’s top 100 banks, 23 of the 25 top US retailers and 9 out of 10 of the world’s largest insurance companies.
When you think of a mainframe, you probably think of an old green computer screen. Did you know you can use the same modern tools and techniques with mainframes that you use with cloud and mobile?
With the growth of mission-critical mainframe workloads showing no signs of slowing down, application delivery cannot remain slow and complex. Organizations must apply the same DevOps processes to the mainframe as they do with other platforms.
Compuware and XebiaLabs enable large enterprises to automatically build, test and deploy mainframe releases within a cross-platform application release pipeline.
Soft lifecycle
The document discusses several software development process models including waterfall, iterative development, prototyping, RAD, spiral, RUP, and agile processes. The waterfall model is a linear sequential process while iterative development allows for incremental improvements. Prototyping allows users to provide early feedback. RAD combines waterfall and prototyping and emphasizes rapid development. Spiral model iterates through risk analysis, development, and planning phases. RUP is object-oriented and divided into cycles. Agile processes emphasize working software, incremental delivery, flexibility, and customer involvement.
DevOps / Agile Tools Seminar 2013
I recently presented this 2 hours session about the automation model developed in Videobet, the tools used in the R&D, QA and operations:
Issue mgmt.: JIRA/Greenhopper
Build system and repository: Maven & Nexus
Build server: QuickBuild
Code quality: Sonar
Continuous Integration: Selenium Grid
Crash dump analysis: Socorro
Database versioning: Flyway DB
Making software development processes to work for you
Mikko Paukkila discusses optimizing software development processes to balance bureaucracy and flexibility. He advocates for continuous integration to find errors early and speed up feedback loops. Tools like Git, Jenkins, Gerrit enable CI by automating builds, testing and code reviews. Process optimizations include reducing time from change to product, automating more tests, and ensuring developers have easy environments and fast feedback. The goal is enabling smooth development flows from needs to requirements to changes to high quality products.
Gopikrishanan
Gopikrishnan Balasubramanian is a senior technical lead with over 10 years of experience in the IT industry, including telecom and video domains. He has expertise in C/C++, Python, cloud technologies like Docker and Kubernetes. Some of his projects include hybrid visual quality enhancement for set-top boxes and IP set-tops. He has extensive experience in the full SDLC, from requirements to packaging final products. He is proficient in languages, cloud tools, protocols, scripting, defect tracking, and build tools.
Efficient platform engineering with Microk8s & gopaddle.pdf
This document discusses the evolution of DevOps and platform engineering challenges. It introduces gopaddle as a low-code DevSecOps platform for Kubernetes that can provide automated multi-cloud provisioning, issue identification, and app release automation. Using MicroK8s and the gopaddle Lite addon allows setting up a platform in 15-20 minutes, improving efficiency and reducing time to develop and deploy microservices compared to traditional methods.
Achieving Full Stack DevOps at Colonial Life
In an ever more competitive marketplace, organizations have turned to Agile and DevOps practices to deliver software innovations to market more quickly and with high quality. Across industries, companies are making heavy investments in tools and process improvements around automated build, test, continuous integration and delivery, and release automation and orchestration. However, despite these investments, many organizations are still struggling to bring the necessary speed and quality to their software delivery. In many cases, this is because Agile and DevOps improvements have not been applied to the entire software stack and are often limited to application code delivery.
This webinar will explore the transformation that Colonial Life made in bringing DevOps to the entire software stack. Specifically, beyond automating and accelerating the validation and delivery of application code, this webinar will focus on the critical role that data and the database play in modern software delivery and the tools and processes that can bring the same automation to database code.
After this webinar, you will understand:
* What holds organizations back despite an Agile application development process
* The benefits of automating the validation and deployment of database changes
* A template for bringing DevOps to the entire software stack
Drupal Europe 2018: Hackers automate but the drupal community still downloads...
“Automatic Updates for Drupal” was, is and will be a matter of debate. In this open discussion, we want to welcome everyone who wants to learn more about the current state of update processes within the Drupal Community, and especially about possible future scenarios in Drupal.
We welcome everyone who’s interested in joining the discussion about auto update possibilities and bringing in critical reflections.
Similar to victoriia basarab - special aspects of dev ops platform development (20)
DevOps Days Kyiv 2019 -- DevOps platform development - lessons learned // Vic...
DevOps Days Kyiv 2019 -- DevOps platform development - lessons learned // Vic...
Dev-HRE-Ops - Addressing the _Last Mile DevOps Challenge_ in Highly Regulated...
Dev-HRE-Ops - Addressing the _Last Mile DevOps Challenge_ in Highly Regulated...
Solving the Automation Puzzle - how to select the right automation framework ...
Solving the Automation Puzzle - how to select the right automation framework ...
"Platform Engineering in practice — Why and How to start", Serg Hospodarets
"Platform Engineering in practice — Why and How to start", Serg Hospodarets
A Story of Cultural Change: PayPal's 2 Year Journey to 150,000 Containers wit...
A Story of Cultural Change: PayPal's 2 Year Journey to 150,000 Containers wit...
Choosing Automation for DevOps & Continuous Delivery in the Enterprise
Choosing Automation for DevOps & Continuous Delivery in the Enterprise
Dev Ops for systems of record - Talk at Agile Australia 2015
Dev Ops for systems of record - Talk at Agile Australia 2015
Orchestrate Your End-to-end Mainframe Application Release Pipeline
Orchestrate Your End-to-end Mainframe Application Release Pipeline
Making software development processes to work for you
Making software development processes to work for you
Efficient platform engineering with Microk8s & gopaddle.pdf
Efficient platform engineering with Microk8s & gopaddle.pdf
Drupal Europe 2018: Hackers automate but the drupal community still downloads...
Drupal Europe 2018: Hackers automate but the drupal community still downloads...
More from Dariia Seimova
juliya tkachova - dev ops on scale from philosophy to toolset
Juliya Tkachova - Dev ops on scale from philosophy to toolset
rohit sharma - dev ops virtual assistant - automate devops stuffs using nlp a...
Stanley was a sysadmin who was bored with repetitive tasks. He adopted DevOps practices like automation but still had to manually trigger commands. He then started using ChatOps through Slack but still had to send commands. Finally, he developed VoiceOps to automate tasks through voice assistants like Google Assistant. This allows even non-technical executives to get answers by speaking naturally. Some tasks he automated include fetching server lists, checking statuses and uptime, executing jobs, and restarting services. The solution uses APIs, scripts, and integrates automation with NLP chatbots. This provides benefits like speed, natural language, context, and frictionless use.
ostap soroka - aws architecture and a human body
The document compares the architecture of AWS to the human body. It discusses four versions of AWS architecture that mirror biological concepts: 1) Autoscaling is similar to homeostasis in maintaining stable internal conditions; 2) Message queues resemble the way the body regulates blood sugar levels; 3) Auto healing is like apoptosis in removing damaged cells; 4) AWS has evolved over billions of years, mirroring the development of the human form. The architecture aims to provide flexible, scalable, and robust systems like the highly effective design of the human body.
sveta smirnova - my sql performance schema in action
This document summarizes MySQL Performance Schema and how it can be used to analyze database performance. Performance Schema instruments internal MySQL operations and collects runtime performance data. It provides visibility into SQL statements, locks, memory usage, and other aspects. The document discusses configuring Performance Schema instrumentation, using its tables and views to identify slow queries, lock contention, and other issues.
faisal mushtaq - an enterprise cloud cost management framework
The document discusses cost management challenges in the cloud for enterprises and provides recommendations to address them. It outlines a cost management framework including initial planning, operational visibility and forecasting, governance, automation and optimization. It also discusses automation tools that can help with cost management tasks like visibility, optimization and billing. Finally, it presents a case study of a retail customer migrating to Google Cloud Platform where cost management was not initially planned and provides recommendations to help address their challenges.
mykola marzhan - jenkins on aws spot instance
The document discusses options for running a Jenkins master instance on AWS. It considers using Spot Instances but they are prone to interruption. An Amazon Elastic File System (EFS) volume can be used to persist data for the Jenkins master, but EFS has limitations for small files. Spot Fleets through the EC2 Fleet plugin allow workers to run on Spot Instances in different Availability Zones with auto-scaling. Configuration files for CloudFormation and Terraform are provided to automate the Jenkins infrastructure deployment.
maksym vlasov - culture of git as roots of your ci
This document discusses best practices for using Git to improve work efficiency. It recommends using Git aliases to create shortcuts for common commands, using Git hooks at different stages of the development process, learning how to effectively read a project's commit history, maintaining a global .gitignore file, signing all commits with GPG for security, and customizing Git configuration to fit your specific workflow needs. Overall it promotes developing a strong "culture of Git" to serve as the foundation for continuous integration practices.
vitaly davidoff - end 2 end containers secure sdlc process
Containers provide security benefits but also introduce new risks that must be managed throughout the software development lifecycle (SDLC). The article discusses how to secure containers from development through production by implementing policies for identity and access management, configuration management, vulnerability management, logging and monitoring.
yegor maksymchuk - open shift as a cloud for data science
This document discusses using OpenShift as a cloud platform for data science. It provides an overview of Kubernetes and OpenShift, comparing their key differences. It then discusses how Apache Spark can be used for data science in the cloud and integrated with OpenShift using Oshinko, which provides tools to deploy and manage Spark clusters on OpenShift. It demonstrates running a sample workflow of deploying a Spark cluster, Zeppelin notebook, and running an example notebook on the Spark cluster using Oshinko on OpenShift.
More from Dariia Seimova (9)
juliya tkachova - dev ops on scale from philosophy to toolset
juliya tkachova - dev ops on scale from philosophy to toolset
rohit sharma - dev ops virtual assistant - automate devops stuffs using nlp a...
rohit sharma - dev ops virtual assistant - automate devops stuffs using nlp a...
sveta smirnova - my sql performance schema in action
sveta smirnova - my sql performance schema in action
faisal mushtaq - an enterprise cloud cost management framework
faisal mushtaq - an enterprise cloud cost management framework
maksym vlasov - culture of git as roots of your ci
maksym vlasov - culture of git as roots of your ci
vitaly davidoff - end 2 end containers secure sdlc process
vitaly davidoff - end 2 end containers secure sdlc process
yegor maksymchuk - open shift as a cloud for data science
yegor maksymchuk - open shift as a cloud for data science
Recently uploaded
ANATOMY AND BIOMECHANICS OF HIP JOINT.pdf
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
Azure Interview Questions and Answers PDF By ScholarHat
Azure Interview Questions and Answers PDF By ScholarHat
RPMS TEMPLATE FOR SCHOOL YEAR 2023-2024 FOR TEACHER 1 TO TEACHER 3
RPMS Template 2023-2024 by: Irene S. Rueco
Executive Directors Chat Leveraging AI for Diversity, Equity, and Inclusion
Let’s explore the intersection of technology and equity in the final session of our DEI series. Discover how AI tools, like ChatGPT, can be used to support and enhance your nonprofit's DEI initiatives. Participants will gain insights into practical AI applications and get tips for leveraging technology to advance their DEI goals.
Hindi varnamala | hindi alphabet PPT.pdf
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
How to Fix the Import Error in the Odoo 17
An import error occurs when a program fails to import a module or library, disrupting its execution. In languages like Python, this issue arises when the specified module cannot be found or accessed, hindering the program's functionality. Resolving import errors is crucial for maintaining smooth software operation and uninterrupted development processes.
The simplified electron and muon model, Oscillating Spacetime: The Foundation...
Discover the Simplified Electron and Muon Model: A New Wave-Based Approach to Understanding Particles delves into a groundbreaking theory that presents electrons and muons as rotating soliton waves within oscillating spacetime. Geared towards students, researchers, and science buffs, this book breaks down complex ideas into simple explanations. It covers topics such as electron waves, temporal dynamics, and the implications of this model on particle physics. With clear illustrations and easy-to-follow explanations, readers will gain a new outlook on the universe's fundamental nature.
BÀI TẬP BỔ TRỢ TIẾNG ANH 8 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2023-2024 (CÓ FI...
BÀI TẬP BỔ TRỢ TIẾNG ANH 8 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2023-2024 (CÓ FI...Nguyen Thanh Tu Collection
https://app.box.com/s/y977uz6bpd3af4qsebv7r9b7s21935vdExploiting Artificial Intelligence for Empowering Researchers and Faculty, In...
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...Dr. Vinod Kumar Kanvaria
Exploiting Artificial Intelligence for Empowering Researchers and Faculty,
International FDP on Fundamentals of Research in Social Sciences
at Integral University, Lucknow, 06.06.2024
By Dr. Vinod Kumar KanvariaCommunity pharmacy- Social and preventive pharmacy UNIT 5
Covered community pharmacy topic of the subject Social and preventive pharmacy for Diploma and Bachelor of pharmacy
The History of Stoke Newington Street Names
Presented at the Stoke Newington Literary Festival on 9th June 2024
www.StokeNewingtonHistory.com
Main Java[All of the Base Concepts}.docx
This is part 1 of my Java Learning Journey. This Contains Custom methods, classes, constructors, packages, multithreading , try- catch block, finally block and more.
How to Manage Your Lost Opportunities in Odoo 17 CRM
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
clinical examination of hip joint (1).pdf
described clinical examination all orthopeadic conditions .
Digital Artifact 1 - 10VCD Environments Unit
Digital Artifact 1 - 10VCD Environments Unit - NGV Pavilion Concept Design
Recently uploaded (20)
Azure Interview Questions and Answers PDF By ScholarHat
Azure Interview Questions and Answers PDF By ScholarHat
RPMS TEMPLATE FOR SCHOOL YEAR 2023-2024 FOR TEACHER 1 TO TEACHER 3
RPMS TEMPLATE FOR SCHOOL YEAR 2023-2024 FOR TEACHER 1 TO TEACHER 3
Executive Directors Chat Leveraging AI for Diversity, Equity, and Inclusion
Executive Directors Chat Leveraging AI for Diversity, Equity, and Inclusion
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...
The simplified electron and muon model, Oscillating Spacetime: The Foundation...
The simplified electron and muon model, Oscillating Spacetime: The Foundation...
BÀI TẬP BỔ TRỢ TIẾNG ANH 8 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2023-2024 (CÓ FI...
BÀI TẬP BỔ TRỢ TIẾNG ANH 8 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2023-2024 (CÓ FI...
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...
Community pharmacy- Social and preventive pharmacy UNIT 5
Community pharmacy- Social and preventive pharmacy UNIT 5
How to Manage Your Lost Opportunities in Odoo 17 CRM
How to Manage Your Lost Opportunities in Odoo 17 CRM
victoriia basarab - special aspects of dev ops platform development
- 1. Specific aspects of DevOps platform development Victoria Basarab, Ciklum, Ukraine
- 2. About the speaker: Victoria Basarab Delivery manager in DevOps, Ciklum
- 3. Utopia in DevOps world We build a Platform which: - never breaks down - highly available - scales automatically to meet demand - Infrastructure automation, CI/CD covered with tests - Platform permanently covers all Devs requirements (Product of any nature/ any programing language) and NO SUPPORT NEEDED
- 4. Real DevOps world Case 1: How bad processes transform DevOps into Ops :( DevOps - Supporter, who works on tasks from Backlog following Symptoms: - Backlog of Platform features that need to be implemented mixed up with support activities - SLA policies - 24/7 support
- 5. Kanban outcome for DevOps Platform in 95 % of cases: - No Platform Client - Missed deadlines - Wasted budget Dev DevOps
- 6. Case 2: DevOps Team as R&D center DevOps - cowboy, who works in isolated Scrum Platform Team Symptoms: - DevOps Team isolated from Dev Teams - DevOps team abstracts from the real needs of Devs - No PO/BA role in the DevOps Platform Team - Platform architecture does not cover operational model - Platform stack consist only from Hype technologies
- 7. Isolated Scrum outcome for DevOps Platform: - POC-like Platform Client - Wasted budget Dev DevOps
- 8. Case 3: DevOps Team builds useful Platform DevOps engineer - component owner, who understands Project/Product needs and build solutions which cover them. Symptoms: - Tasks can be added to Platform Backlog by Dev Teams - Dev Teams use Platform on daily basis - Architecture of Platform covers operational model - Platform stack consists from tools that Project requirements
- 9. How does Platform and other software differ? Statement 1: PO in Dev Teams mainly works with functional requirements and DevOps Team mainly works on non-functional stuff. Output: DevOps engineer as a component owner. S/he gathers requirements for appropriate solution within the Dev Teams.
- 10. Statement 2: DevOps toolkit evolves too rapidly Output: Lifetime of DevOps Platform can be 1-2 years, but you should be ready that in some cases it will be 3-5 months. DevOps Platform should be constantly refactored.
- 11. Statement 3: Platform introduction to its end users - Developers Output: Formalized knowledge sharing process. Implementation of some kind of DevOps knowledge checklist - which provide possibility of transfer knowledge and ownership to Dev Teams. Maturity matrix - https://tc-jira.atlassian.net/wiki/spaces/SHIP/pages/817103432/Spartans+- Maturity+matrix
- 12. Summary: We understood that development of DevOps Platform requires balanced and hybrid approach. What Scrumban gives? - Focused, iterative development of Platform - Feedback loop from Dev Teams - Enhanced knowledge transfer
- 13. Contact details: Linkedin - Victoria Basarab Skype - viktoriabasarab Thanks a lot for your attention!