The document discusses key topics from a session on build and release engineering, including continuous integration, continuous delivery, and continuous deployment. It defines these terms and lists the main steps and principles associated with each. Specific topics covered include software release principles, configuring management, deployment pipelines, testing approaches, and managing environments and releases of complex systems. The target audience for these concepts is listed as various engineering and operations roles.
Funny stories and anti-patterns from DevOps landscapeMikalai Alimenkou
During last several years DevOps became strong buzzword used almost in every project, team and company. But almost everywhere it is used in very funny and strange context. For example, existing ops guys are renamed to DevOps just to sell them to the client for more money. Or DevOps is used as new job title for some magically powerful person who is able to operate cloud environment and modern infrastructure related tools, leading team of old school ops and participating in management meetings. In this talk I’m going to review all different anti-patterns and bad practices in DevOps landscape using stories from my personal experience as Delivery Manager and independent consultant.
Session Abstract:
Agile framework is based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. It’s a set of values and principles that help teams respond to unpredictability through incremental, iterative work cadences and continuous feedback.
Scrum is the most popular methodology under the Agile umbrella. Scrum emphasizes empirical feedback, team self-management, and striving to build shippable product increments within short iterations.
Kanban is another popular flavor of Agile that focuses on visualizing and managing the flow of work, in order to balance demand with available capacity and remove bottlenecks.
Learning Objectives:
> Gain a broad understanding of the Agile framework
> Discover Scrum and Kanban, the two most widely used Agile methodologies, and see how they can be used in construction industry
> Find out how Scrum and Kanban can be combined to have the best of both worlds (Scrumban)
Agile methodology is a framework for modern software development.
What is the philosophy behind Agile?
How does it differ from traditional project management strategies like waterfall?
What are the stages, meetings, tools, and team roles?
What is Scrum?
Matt Callanan takes the 15 chapters of the famous "Continuous Delivery" book by Jez Humble & Dave Farey and distills it down into 1 hour of convincing arguments, walking through the pieces involved to make it happen including cultural challenges, automated testing, automated deployment & deployment pipelines. Not sure how to get started with DevOps? Finding it hard to convince colleagues & managers that CD is the way forward? Matt has used this presentation to help facilitate enterprise-wide adoption of Continuous Delivery. Slides from a presentation given at DevOps Brisbane March 2014.
Funny stories and anti-patterns from DevOps landscapeMikalai Alimenkou
During last several years DevOps became strong buzzword used almost in every project, team and company. But almost everywhere it is used in very funny and strange context. For example, existing ops guys are renamed to DevOps just to sell them to the client for more money. Or DevOps is used as new job title for some magically powerful person who is able to operate cloud environment and modern infrastructure related tools, leading team of old school ops and participating in management meetings. In this talk I’m going to review all different anti-patterns and bad practices in DevOps landscape using stories from my personal experience as Delivery Manager and independent consultant.
Session Abstract:
Agile framework is based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. It’s a set of values and principles that help teams respond to unpredictability through incremental, iterative work cadences and continuous feedback.
Scrum is the most popular methodology under the Agile umbrella. Scrum emphasizes empirical feedback, team self-management, and striving to build shippable product increments within short iterations.
Kanban is another popular flavor of Agile that focuses on visualizing and managing the flow of work, in order to balance demand with available capacity and remove bottlenecks.
Learning Objectives:
> Gain a broad understanding of the Agile framework
> Discover Scrum and Kanban, the two most widely used Agile methodologies, and see how they can be used in construction industry
> Find out how Scrum and Kanban can be combined to have the best of both worlds (Scrumban)
Agile methodology is a framework for modern software development.
What is the philosophy behind Agile?
How does it differ from traditional project management strategies like waterfall?
What are the stages, meetings, tools, and team roles?
What is Scrum?
Matt Callanan takes the 15 chapters of the famous "Continuous Delivery" book by Jez Humble & Dave Farey and distills it down into 1 hour of convincing arguments, walking through the pieces involved to make it happen including cultural challenges, automated testing, automated deployment & deployment pipelines. Not sure how to get started with DevOps? Finding it hard to convince colleagues & managers that CD is the way forward? Matt has used this presentation to help facilitate enterprise-wide adoption of Continuous Delivery. Slides from a presentation given at DevOps Brisbane March 2014.
Kanban/Scrumban - taking scrum outside its comfort zoneYuval Yeret
Kanban is a way to implement a Lean process, focused on flow, time to
market, and waste removal. Understand the Lean principles behind Kanban, its
relation to Agile/Scrum, and how the two can complement each other into
Scrumban. Understand where Kanban should be considered.
What is Agile Project Management? | Agile Project Management | Invensis Learn...Invensis Learning
( *** PRINCE2 Agile Certification Training: https://bit.ly/2KIz6Oh *** )
( *** AgilePM Certification Training: https://bit.ly/2V3QhMf *** )
This presentation on What is Agile Project Management? explains the need for blending Agile concepts with control and governance of Project Management, also explains how it can be done.
Areas Covered:
1. Need for Agile Project Management
2. Understanding Principles of Agile & Project Management
3. What is Agile Project Management?
4. Difference Between Agile & Waterfall
5. Challenges if Agile Project Management
6. Understanding Agile Frameworks
7. Agile Project Management Career Paths
#AgileProjectManagement #InvensisLearning
Subscribe to our channel: https://bit.ly/3dmqNQS
Click here to check upcoming webinars on Agile Project Manager: https://goo.gl/M9v8oP
About Invensis Learning:
Invensis Learning is a pioneer in providing globally-recognized certification training courses for individuals and enterprises worldwide. We have trained and certified 15,000+ professionals from 50+ courses through multiple training delivery modes.
Invensis Learning provides live online certification training on Agile Project Management, there are two career paths one can opt for.
1. AgilePM certification by APMG: https://bit.ly/2V3QhMf
2. PRINCE2 Agile certification by AXELOS: https://bit.ly/2KIz6Oh
Upon enrolment, you will get lifetime access to a Learning Management System which will contain all class resources like recordings and Ppts, along with access to Agile Project Management webinars.
BECOME A CERTIFIED AGILE PROJECT MANAGER!
For more information please visit our website: https://www.invensislearning.com
Follow Us on:
Facebook: https://www.facebook.com/invensislearn/
LinkedIn: https://www.linkedin.com/company/inve...
Twitter: https://twitter.com/invensiselearn/
When DevOps talks meet DevOps tactics, companies find that Continuous Integration is the make or break point. And implementing CI is one thing, but sustainable CI takes a little bit more consideration. CI is not all about releases, it is also about knowing more about how your software delivery pipeline works, it's weak points, and how you are doing over time.
Join CloudBees and cPrime as we discuss best practices for facilitating DevOps pipelines with Jenkins Workflow and reveal how the workflow engine of Jenkins CI and “Agilecentric” Devops practices together, support complex control structures, shortens the development cycle, stabilizes environments and reduces defects.
Imported from Japan, Kanban is an agile methodology that is gaining a lot of traction. Kanban, or Japanese for signal card, is a process that focuses on transparency and limiting the work in progress. By utilizing Kanban, you can pinpoint the bottlenecks and address them easily. In this session you will learn what Kanban is, how it evolved from its roots in the Toyota Production System (TPS) and lean manufacturing to software development, Kanban’s benefits, and how best to implement a Kanban system. We’ll also discuss when not to use Kanban and how to modify other agile methodologies, such as Scrum, to be used in conjunction with Kanban.
A fair analysis of the Agile Methodology. A quick comparison of Agile and Waterfall to clear up misconceptions about the two. Scalability is a major issue with Agile and is worth considering if you're not a large software company.
Talk about the basic principles and concepts of CI/CD as a set of practices in order to reduce integration errors through automated implementations for testing and deployments as well as the tooling behind this philosophy.
Agile management, or agile process management, or simply agile refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner; an example is its application in Scrum, an original form of agile software development.
Stefan Schmidt, from Samsung Open Source Group's EFL development team, discusses current Enlightenment for Linux Quality Assurance Statistics at the recent EFL Developers Day in Dusseldorf, Germany.
>>Automation of build and release
>>Continuous Integration using ANT and Cruise Control
>>Features of Cruise Control
Using Cruise Control to achieve automation of build and release
>>Metrics, reports and data analysis using Cruise Control
Automated test case execution using EMMA
>>Automated code reviews using PMD
File Can be downloaded from:
http://community.scmgalaxy.com/
Kanban/Scrumban - taking scrum outside its comfort zoneYuval Yeret
Kanban is a way to implement a Lean process, focused on flow, time to
market, and waste removal. Understand the Lean principles behind Kanban, its
relation to Agile/Scrum, and how the two can complement each other into
Scrumban. Understand where Kanban should be considered.
What is Agile Project Management? | Agile Project Management | Invensis Learn...Invensis Learning
( *** PRINCE2 Agile Certification Training: https://bit.ly/2KIz6Oh *** )
( *** AgilePM Certification Training: https://bit.ly/2V3QhMf *** )
This presentation on What is Agile Project Management? explains the need for blending Agile concepts with control and governance of Project Management, also explains how it can be done.
Areas Covered:
1. Need for Agile Project Management
2. Understanding Principles of Agile & Project Management
3. What is Agile Project Management?
4. Difference Between Agile & Waterfall
5. Challenges if Agile Project Management
6. Understanding Agile Frameworks
7. Agile Project Management Career Paths
#AgileProjectManagement #InvensisLearning
Subscribe to our channel: https://bit.ly/3dmqNQS
Click here to check upcoming webinars on Agile Project Manager: https://goo.gl/M9v8oP
About Invensis Learning:
Invensis Learning is a pioneer in providing globally-recognized certification training courses for individuals and enterprises worldwide. We have trained and certified 15,000+ professionals from 50+ courses through multiple training delivery modes.
Invensis Learning provides live online certification training on Agile Project Management, there are two career paths one can opt for.
1. AgilePM certification by APMG: https://bit.ly/2V3QhMf
2. PRINCE2 Agile certification by AXELOS: https://bit.ly/2KIz6Oh
Upon enrolment, you will get lifetime access to a Learning Management System which will contain all class resources like recordings and Ppts, along with access to Agile Project Management webinars.
BECOME A CERTIFIED AGILE PROJECT MANAGER!
For more information please visit our website: https://www.invensislearning.com
Follow Us on:
Facebook: https://www.facebook.com/invensislearn/
LinkedIn: https://www.linkedin.com/company/inve...
Twitter: https://twitter.com/invensiselearn/
When DevOps talks meet DevOps tactics, companies find that Continuous Integration is the make or break point. And implementing CI is one thing, but sustainable CI takes a little bit more consideration. CI is not all about releases, it is also about knowing more about how your software delivery pipeline works, it's weak points, and how you are doing over time.
Join CloudBees and cPrime as we discuss best practices for facilitating DevOps pipelines with Jenkins Workflow and reveal how the workflow engine of Jenkins CI and “Agilecentric” Devops practices together, support complex control structures, shortens the development cycle, stabilizes environments and reduces defects.
Imported from Japan, Kanban is an agile methodology that is gaining a lot of traction. Kanban, or Japanese for signal card, is a process that focuses on transparency and limiting the work in progress. By utilizing Kanban, you can pinpoint the bottlenecks and address them easily. In this session you will learn what Kanban is, how it evolved from its roots in the Toyota Production System (TPS) and lean manufacturing to software development, Kanban’s benefits, and how best to implement a Kanban system. We’ll also discuss when not to use Kanban and how to modify other agile methodologies, such as Scrum, to be used in conjunction with Kanban.
A fair analysis of the Agile Methodology. A quick comparison of Agile and Waterfall to clear up misconceptions about the two. Scalability is a major issue with Agile and is worth considering if you're not a large software company.
Talk about the basic principles and concepts of CI/CD as a set of practices in order to reduce integration errors through automated implementations for testing and deployments as well as the tooling behind this philosophy.
Agile management, or agile process management, or simply agile refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner; an example is its application in Scrum, an original form of agile software development.
Stefan Schmidt, from Samsung Open Source Group's EFL development team, discusses current Enlightenment for Linux Quality Assurance Statistics at the recent EFL Developers Day in Dusseldorf, Germany.
>>Automation of build and release
>>Continuous Integration using ANT and Cruise Control
>>Features of Cruise Control
Using Cruise Control to achieve automation of build and release
>>Metrics, reports and data analysis using Cruise Control
Automated test case execution using EMMA
>>Automated code reviews using PMD
File Can be downloaded from:
http://community.scmgalaxy.com/
The Changing Role of Release Engineering in a DevOps WorldPerforce
There is no denying that DevOps has shaken up the world of developing and deploying software. With all the buzz around new techniques and technologies, it's easy to get lost in the “We deploy hundreds of times a day!” cacophony and all the new tools. The rise of DevOps is revitalizing age-old topics in release engineering and application lifecycle management, and aspects of software delivery that DevOps doesn’t magically solve. If you're responsible for the release engineering function in your organization, see what the new world looks like and which aspects of the industry it’s leaving behind.
Building A Strong Engineering Culture - my talk from BBC Develop 2013Kevin Goldsmith
This is the keynote talk I gave at the BBC Develop conference in London, UK in November of 2013. In it I talk about what I believe makes a strong engineering culture, how to protect it if you have it, and how to fix it if you don't. I use a lot of examples from Spotify (where I am a Director of Engineering). As usual, I go a bit light on the bullets, since I prefer to talk, but I think you can still get the gist of my points.
Taking AppSec to 11: AppSec Pipeline, DevOps and Making Things BetterMatt Tesauro
Slide deck from AppSec California 2016 + some additional slides.
Abstract:
How many applications are in your company’s portfolio? What’s the headcount for your AppSec team? Whatever your situation is, I am sure the numbers are not in your favor. Its not time to find a new career, it's time to up your game. This talk will cover how to take your small merry band of AppSec professionals and scale it up to a virtual army. By taking the best of DevOps, Agile and CI/CD, you can iteratively up your AppSec game over time and begin your ascent out of the security hole you are in.
The talk covers real world experiences running AppSec groups at two different companies. Rackspace with approximately 4,000+ employees and Pearson with 40,000+. Both have an international presence and far more apps and developers that AppSec staff. The talk covers the key principles to speed and scale up AppSec programs using an AppSec Pipeline as well as practical examples of these practices put into use. Start early and begin to buy down the technical security dept which feels inevitable with more traditional AppSec program thinking.
Taking AppSec to 11 - BSides Austin 2016Matt Tesauro
Curious how DevOps, Agile and CI/CD ideas can speed up your AppSec program? Here's how it can be done and an example where it lead to a 5x speed/flow improvement.
Test Automation at the Speed of Agile: Making It Work Every BuildTechWell
Join Danny McKeown, Paychex’s lead test enterprise automation architect, to see how a small tools group supports nearly one-hundred agile teams as they move toward achieving continuous delivery. Take part in the conversation to understand how Paychex is progressing in the third year of its agile transformation. Danny describes how this IT-wide initiative has impacted how the tools group supports so many teams and changed its own practices to provide more timely support. With the goal of increasing velocity, a solid automation strategy has become a powerful enabler. Danny describes how Paychex assesses progress with a maturity lens. Their always-evolving automation framework serves web and mobile team requirements. He shares an HTML5 mini-case study, describing how adopting responsive web changed practices. Embedding quality in multiple daily builds has not come without its challenges, and Danny describes the lessons learned and their next steps. This interactive session will encourage participants to share their experiences as well—so come ready!
A Declarative Approach for Performance Tests Execution in Continuous Software...Vincenzo Ferme
Software performance testing is an important activity to ensure quality in continuous software development environments. Current performance testing approaches are mostly based on scripting languages and framework where users implement, in a procedural way, the performance tests they want to issue to the system under test. However, existing solutions lack support for explicitly declaring the performance test goals and intents. Thus, while it is possible to express how to execute a performance test, its purpose and applicability context remain implicitly described. In this work, we propose a declarative domain specific language (DSL) for software performance testing and a model-driven framework that can be programmed using the mentioned language and drive the end-to-end process of executing performance tests. Users of the DSL and the framework can specify their performance intents by relying on a powerful goal-oriented language, where standard (e.g., load tests) and more advanced (e.g., stability boundary detection and configuration tests) performance tests can be specified starting from templates. The DSL and the framework have been designed to be integrated into a continuous software development process and validated through extensive use cases that illustrate the expressiveness of the goal-oriented language, and the powerful control it enables on the end-to-end performance test execution to determine how to reach the declared intent.
My talk from The 9th ACM/SPEC International Conference on Performance Engineering (ICPE 2018). Cite us: https://dl.acm.org/citation.cfm?id=3184417
What to Do—Develop Your Own Automation or Use Crowdsourced Testing?TechWell
Modern software products tend to have a rich UI that supports many user workflows, all of which need to be covered in testing. Agile organizations quickly discover that manual end-to-end testing neither supports their velocity nor provides respectable regression coverage. A common progression is to move from fully manual testing to record/replay, then to Selenium IDE style tests, then to automation based on Selenium WebDriver, perhaps with a BDD overlay. Daria Mehra has practiced this approach and shares her experience. She compares the Selenium style of automation to an alternative—crowdsourced test execution— which provides all the benefits of test automation, including continuous integration. This approach allows non-coders to express test cases in natural language, avoids the dependency on UI implementation, adds a “human eye” advantage, and provides the ability to massively parallelize tests for fast execution. Learn the pros and cons of end-to-end, UI-based test automation via Selenium compared to crowdsourcing. Find out how you can assess the suitability of these testing approaches for your needs.
A great deal of confusion surrounds the concepts of release automation, continuous integration, continuous delivery, and continuous deployment. Even some industry experts are confused about the differences. How these concepts work progressively to achieve high quality software delivery is generating a lot of discussion and controversy. Bryan Linder defines the methodology, processes, and tools associated with release automation, as well as the differences between its maturity levels. Understand the benefits of more frequent, smaller releases, and the exponential risk generated by large, infrequent releases. Hear highlights of industry case studies that demonstrate the substantial speed, quality, and ROI gains of improving your release automation process. Acquire the insight and motivation needed to take the next step—from wherever you organization is now—toward full release automation. Takeaways include a glossary of terms, a continuous integration tools comparison chart, and a release automation maturity chart.
What is continuous integration?
Building a feature with continuous integration
Practices of continuous integration
Benefits of continuous integration
Introducing continuous integration
Final thoughts
Continuous integration tools
Continuous Automation and its Impact on the CI_CD Pipeline.pdfkalichargn70th171
The CI/CD pipeline ensures software development teams reliably deliver code changes. CI is Continuous Integration, where developers merge code changes into a central repository, followed by automatic builds and tests. CD is either Continuous Delivery or Continuous Deployment, which are practices that automate the delivery of applications to selected infrastructure environments. Continuous Delivery automates the delivery process, while Continuous Deployment automates the production release.
Continuous Delivery in Practice (extended)Tzach Zohar
Extended version of a previously uploaded presentation:
10 practical field-proven tips for building a continuously delivered service, based on Kenshoo's experience with its RTB service - a critical, high throughput, highly available component, serving millions of requests per minute in under 50 milliseconds.
From coding practices to test automation, from monitoring tools to feature A/B testing - the entire development chain should be focused around removing blockers and manual steps between your code and your clients, without ever settling for quality. Join to see what makes our clients and developers happy and effective.
Docker New York City: From GitOps to a scalable CI/CD Pattern for KubernetesAndrew Phillips
Slides from the presentation "From GitOps to a scalable CI/CD Pattern for Kubernetes" at the Docker New York City meetup, by Andrew Phillips. See https://www.meetup.com/Docker-NewYorkCity/events/257539512/
These slides mark the goals that we'd like to accomplish defining a QA team which eliminates the frictions with development teams. How much is achieved? Well, it's on our plans to follow it. But we do not know if we'll be able to make it possible
DevOps Continuous Integration & Delivery - A Whitepaper by RapidValueRapidValue
In this whitepaper, we will deep dive into the concept of continuous integration, continuous delivery and continuous deployment and explain how businesses can benefit from this. We will also elucidate on how to build an effective CI/CD pipeline and some of the best practices for your enterprise DevOps journey.
apidays LIVE New York - Navigating the Sea of Javascript Tools to Discover Sc...apidays
apidays LIVE New York - API for Legacy Industries: Banking, Insurance, Healthcare and Retail
Navigating the Sea of Javascript Tools to Discover Scalable Tools for Continuous Delivery
Menelaos Kotsollaris, Senior Software Engineer
Viki Green, Senior Software Developer at Trulioo
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
A Study of Variable-Role-based Feature Enrichment in Neural Models of CodeAftab Hussain
Understanding variable roles in code has been found to be helpful by students
in learning programming -- could variable roles help deep neural models in
performing coding tasks? We do an exploratory study.
- These are slides of the talk given at InteNSE'23: The 1st International Workshop on Interpretability and Robustness in Neural Software Engineering, co-located with the 45th International Conference on Software Engineering, ICSE 2023, Melbourne Australia
Atelier - Innover avec l’IA Générative et les graphes de connaissancesNeo4j
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Allez au-delà du battage médiatique autour de l’IA et découvrez des techniques pratiques pour utiliser l’IA de manière responsable à travers les données de votre organisation. Explorez comment utiliser les graphes de connaissances pour augmenter la précision, la transparence et la capacité d’explication dans les systèmes d’IA générative. Vous partirez avec une expérience pratique combinant les relations entre les données et les LLM pour apporter du contexte spécifique à votre domaine et améliorer votre raisonnement.
Amenez votre ordinateur portable et nous vous guiderons sur la mise en place de votre propre pile d’IA générative, en vous fournissant des exemples pratiques et codés pour démarrer en quelques minutes.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
E-commerce Application Development Company.pdfHornet Dynamics
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
AI Genie Review: World’s First Open AI WordPress Website CreatorGoogle
AI Genie Review: World’s First Open AI WordPress Website Creator
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-genie-review
AI Genie Review: Key Features
✅Creates Limitless Real-Time Unique Content, auto-publishing Posts, Pages & Images directly from Chat GPT & Open AI on WordPress in any Niche
✅First & Only Google Bard Approved Software That Publishes 100% Original, SEO Friendly Content using Open AI
✅Publish Automated Posts and Pages using AI Genie directly on Your website
✅50 DFY Websites Included Without Adding Any Images, Content Or Doing Anything Yourself
✅Integrated Chat GPT Bot gives Instant Answers on Your Website to Visitors
✅Just Enter the title, and your Content for Pages and Posts will be ready on your website
✅Automatically insert visually appealing images into posts based on keywords and titles.
✅Choose the temperature of the content and control its randomness.
✅Control the length of the content to be generated.
✅Never Worry About Paying Huge Money Monthly To Top Content Creation Platforms
✅100% Easy-to-Use, Newbie-Friendly Technology
✅30-Days Money-Back Guarantee
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
#AIGenieApp #AIGenieBonus #AIGenieBonuses #AIGenieDemo #AIGenieDownload #AIGenieLegit #AIGenieLiveDemo #AIGenieOTO #AIGeniePreview #AIGenieReview #AIGenieReviewandBonus #AIGenieScamorLegit #AIGenieSoftware #AIGenieUpgrades #AIGenieUpsells #HowDoesAlGenie #HowtoBuyAIGenie #HowtoMakeMoneywithAIGenie #MakeMoneyOnline #MakeMoneywithAIGenie
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
2. Main
Agenda
of
this
session
h"p://linkedin.com/in/praneshvi"al
2
3. Key
Takeaways
from
this
session
ì So<ware
Release
Principles
&
its
importance.
ì Not
to
expect
results
from
“Day
1”.
It’s
a
slow
process.
Takes
months
or
at
Lmes
even
years
to
reach
perfecLon
levels.
ì What
is
“ConLnuous
IntegraLon”?
ì Steps
associated
with
“ConLnuous
IntegraLon”?
ì What
is
a
“ConLnuous
Delivery”?
ì Steps
associated
with
“ConLnuous
Delivery”?
ì What
is
a
“ConLnuous
Deployment”?
ì Release
Engineering
Steps.
ì Main
Focus
of
Release
Engineering.
h"p://linkedin.com/in/praneshvi"al
3
4. Key
Takeaways
from
this
session
ì ConfiguraLon
Management.
ì Principles
of
Managing
ApplicaLon
ConfiguraLon.
ì Its
not
just
about
the
tools.
Its
about
the
big
“Cultural
Change”
that
everyone
has
to
go
through
.
ì Release
Engineering
Architecture.
ì Deep
dive
into
commit
/
component
builds.
ì AnL-‐Pa.erns
in
commit
/
component
builds.
ì Aim
of
Deployment
Pipeline.
ì AnL-‐Pa.erns
of
Deployment
Pipeline.
ì Best
qualiLes
of
a
Deployment
Pipeline.
h"p://linkedin.com/in/praneshvi"al
4
5. Key
Takeaways
from
this
session
ì Deployment
on
Large
Scale
ProducLon
Environments.
ì Why
Automated
Deployment
is
an
indispensable
goal
???
ì Deep
dive
into
TesLng
Quadrant.
ì Deep
Dive
into
Automated
Acceptance
Tests.
ì Few
more
Generic
AnL-‐Pa.erns.
ì AdapLon
of
Release
Engineering.
ì Tools
Used
at
each
of
the
stages.
ì Managing
Environments.
ì Managing
Releases
of
complex
systems.
h"p://linkedin.com/in/praneshvi"al
5
6. Key
Takeaways
from
this
session
ì Steps
involved
to
build
a
deployment
pipeline.
ì Everyone
is
an
equal
contributor
to
reach
“ConLnuous
Deployment”
stage.
ì MulL-‐Tenancy
Cloud.
ì MulL-‐Instance
ApplicaLons.
ì Zero
DownLme
Deployment.
ì ExtracLng
the
server
logs.
ì Next
generaLon
tools
in
the
DevOps
world.
ì PreparaLon
for
the
Release.
ì Maturity
of
a
“Deployment
Pipeline”.
h"p://linkedin.com/in/praneshvi"al
6
7. Target
Audience
ì Product
Managers
/
Business
Analysts.
ì Engineering
Managers.
ì Development
Teams.
ì Quality
Engineering
Teams.
ì System
Admins.
ì Service
Engineering
/
ProducLon
Engineering
Teams.
ì On-‐site
Coordinators.
h"p://linkedin.com/in/praneshvi"al
7
8. Software
Release
Principles
&
its
importance.
ì Should
be
Fast
/
Predictable
/
Repeatable.
ì Automate
almost
everything.
ì Keep
everything
in
Version
Control.
ì If
it
hurts,
do
it
more
o<en.
ì Improve
the
quality
of
the
Builds.
Push
the
boundaries
of
test
automaLon
so
that
quality
is
not
compromised.
ì Done
means
the
so<ware
is
released
and
has
reached
the
producLon.
h"p://linkedin.com/in/praneshvi"al
8
9. What
is
Deployment?
ì Run
the
same
commands
in
several
hosts.
ì Install
the
required
so<ware
from
a
central
repository
so
that
the
end
state
of
every
host
is
same.
ì Based
on
the
host-‐type,
install
the
required
packages.
ì End
goal
is
to
bring
all
the
hosts
of
the
respecLve
host-‐type
in
the
same
state.
h"p://linkedin.com/in/praneshvi"al
9
10. What
is
“Continuous
Integration”?
ì Building,
deploying
and
tesLng
the
applicaLon.
h"p://linkedin.com/in/praneshvi"al
10
11. Steps
associated
with
“Continuous
Integration”?
ì Integrate
all
the
components
at
regular
intervals.
ì Binaries
built
only
once
and
used
in
all
the
environments.
ì Execute
Unit
Tests
before
the
packages
are
generated.
ì Deploy
the
latest
packages
onto
an
INT
environment.
ì Run
the
automated
tests,
validate
the
test
results.
ì Track
the
Code
quality
criteria
such
as
staLc
code
analysis,
test
coverage.
ì Deploying
to
other
environments
with
a
pre-‐defined
frequency.
ì Repeat
the
process.
ì It’s
a
pracGce,
not
a
tool
h"p://linkedin.com/in/praneshvi"al
11
12. What
is
a
“Continuous
Delivery”?
ì Building,
deploying,
tesLng,
promoLon
of
the
applicaLon
to
the
next
environment.
ì Image
credit:
h.p://www.axonivy.com/
h"p://linkedin.com/in/praneshvi"al
12
13. Steps
associated
with
“Continuous
Delivery”?
ì Steps
followed
in
“ConLnuous
IntegraLon”.
ì AutomaLc
promoLon
/
deployment
to
other
environments
(QA,
Staging,
Performance
etc…)
upon
successful
execuLon
of
automated
tests.
ì ApplicaLon
is
always
ready
to
deploy
to
producLon
through
a
largely
automated
process.
h"p://linkedin.com/in/praneshvi"al
13
14. What
is
a
“Continuous
Deployment”?
ì Building,
deploying,
tesLng,
promoLon
of
the
applicaLon
to
the
producLon.
ì Image
credit:
Yassal
Sundman
h"p://linkedin.com/in/praneshvi"al
14
15. Release
Engineering
Principles
&
its
importance.
ì Minimize
Cycle
Time
from
check-‐in
to
producLon
push.
ì Everybody
is
responsible
for
the
Delivery
Process.
ì ConLnuous
Improvement.
ì AcLviLes
such
as
SCM,
Release
planning,
Automated
Deployment,
Acceptance
TesLng,
Performance
TesLng
are
NOT
SECONDARY.
ì Generates
no
revenue
Lll
its
in
the
hands
of
the
end-‐users.
ì Customer
SaLsfacLon
through
early
&
conLnuous
delivery
of
so<ware.
h"p://linkedin.com/in/praneshvi"al
15
17. Main
Focus
of
Release
Engineering
ì Build
-‐>
Deploy
-‐>
Test
-‐>
Release
ì Every
single
check-‐in
should
potenLally
be
in
a
releasable
state.
h"p://linkedin.com/in/praneshvi"al
17
18. Configuration
Management
ì Using
Version
Control
and
commit
everything.
ì Check-‐in
the
changes
at
regular
frequency.
ì Use
meaningful
messages
for
every
commit.
ì Managing
Dependencies
(External
Libraries,
Components).
ì Managing
the
Infrastructure
(Consistent
network
topology,
firewall,
OS
configuraLon,
patches
etc...
across
all
the
environments).
ì Managing
the
Environments
&
the
tools
to
be
used
for
the
same.
ì Managing
the
Change
Process.
h"p://linkedin.com/in/praneshvi"al
18
19. Principles
of
Managing
Application
Configuration
ì Good
understanding
of
the
stage
in
which
the
configuraLon
should
be
injected
(Assembly,
Deployment,
Restart
etc…)
ì ConfiguraLon
sefngs
for
the
applicaLon
to
be
in
the
project’s
root
directory.
ì Should
always
be
automated
and
values
checked
into
repository.
ì Use
clear
naming
convenLon.
ì Avoid
Over-‐engineering.
Keep
it
as
simple
as
possible.
ì Ensure
that
the
configuraLon
is
tested
properly
a<er
deployment.
h"p://linkedin.com/in/praneshvi"al
19
20. Release
Engineering
Architecture
ì Its
all
about
building
the
“Build
&
Release”
pipeline.
ì Built
using
Jenkins
or
similar
ConLnuous
IntegraLon
Tools.
ì IllustraLon
of
a
“Delivery
Pipeline”
(Image
Courtesy:
“ConLnuous
Delivery”
by
Jez
Humble
&
David
Farley).
h"p://linkedin.com/in/praneshvi"al
20
21. Deep
dive
into
commit
/
component
builds:
ì Aim:
ì Eliminate
builds
that
are
unfit
for
producLon.
ì Steps:
ì Compile
the
code.
ì Run
a
set
of
commit
tests.
ì Run
Lint
based
tests
or
some
of
the
basic
staLc
code
analysis
tasks.
ì Publish
the
results.
ì Once
above
steps
are
done,
build
the
package
and
upload
the
binary
to
a
centralized
repository.
ì Add
tests
on
an
ongoing
basis.
ì Keep
a
watch
on
the
build
execuLon
Lme
and
opLmize
frequently.
ì Explore
the
‘Pre-‐Commit’
or
‘Pre-‐Flight’
build
opLons
provided
by
some
of
the
CI
tools.
h"p://linkedin.com/in/praneshvi"al
21
22. Anti-‐Patterns
in
commit
/
component
builds:
ì Don’t
check-‐in
new
code
on
a
broken
build.
The
only
fix
that
has
to
go
are
the
changes
that
fix
the
broken
build.
ì Always
run
commit
tests
locally
before
the
commit.
ì Always
wait
for
commit
tests
to
pass
before
next
check-‐in.
ì Developers
who
have
commi.ed
their
code
are
responsible
for
the
build
process
to
succeed.
ì Never
go
home
on
a
broken
build.
ì Time-‐box
during
every
failed
build.
Give
about
10-‐20
minutes
to
fix,
else
rollback
the
changes.
ì Don’t
EVER
comment
failing
tests.
ì Take
ownership
for
all
the
breakages
that
result
from
your
changes
and
fix
them
accordingly.
h"p://linkedin.com/in/praneshvi"al
22
23. Aim
of
Deployment
Pipeline
ì Every
Step
should
be
visible
(Results
in
be.er
collaboraLon).
ì Deliver
useful,
working
so<ware
to
the
users
as
early
as
possible.
ì Early
feedback
(IdenLfy
&
resolve
issues
in
the
early
stages).
ì Enable
teams
to
deploy
&
release
any
version
of
their
so<ware
at
any
point
to
any
of
the
environments.
ì Avoid
last
day
heroics
on
the
release
day.
ì Release
in
small
chunks
(Avoid
“Big
Bang”
release).
ì Should
be
driven
by
tools
&
not
by
sviduals.
ì Ability
for
every
change
to
be
transparent
&
propagate
them
through
the
pipeline.
ì Ability
to
roll-‐back
to
a
previous
stable
state
in
case
of
any
failures.
h"p://linkedin.com/in/praneshvi"al
23
24. Anti-‐Patterns
of
Deployment
Pipeline
ì Manual
Deployment
of
So<ware.
ì Deployment
performed
by
mulLple
teams.
ì The
order
of
steps
are
not
defined.
ì No
proper
“Run
books”
for
failures.
ì Too
much
of
reliance
of
manual
tesLng.
ì CorrecLon
to
the
release
process
during
the
actual
producLon
release.
ì ConfiguraLon
across
all
the
environments
varies
to
a
large
extent.
ì Manual
ConfiguraLon
management
of
ProducLon
Environment.
ì Deployment
to
a
producLon-‐like
environment
is
done
only
development
is
100%
complete.
h"p://linkedin.com/in/praneshvi"al
24
25. Best
qualities
of
a
Deployment
Pipeline
ì Deployments
should
be
automated.
ì Deployments
should
be
done
frequently
(If
possible,
for
every
single
check-‐in).
ì Provide
early
feedback
so
that
the
development
team
can
act
on
the
failures
in
a
faster
way.
ì Good
AutomaLon
Coverage
to
test
early.
ì Should
be
scalable.
ì Should
enable
one-‐click
deployment.
h"p://linkedin.com/in/praneshvi"al
25
26. Deployment
on
Large
Scale
Production
Environments
ì What
are
host-‐types?
ì What
are
recipes
/
cookbooks?
ì Tools
like
Pogo
OR
other
agent
based
deployment
tools.
$
ssh
<target-‐host-‐name>
'whoami;’
praneshv
h"p://linkedin.com/in/praneshvi"al
26
27. Why
Automated
Deployment
is
an
indispensable
goal
???
ì On
most
occasions,
the
deployment
documentaLon
is
outdated.
ì Logging
all
the
steps
in
the
form
of
scripts
is
very
beneficial
for
book
keeping
purposes.
ì Works
seamlessly
if
all
the
steps
are
taken
care
of.
ì Even
non-‐experts
should
be
able
to
deploy
effortlessly.
ì Every
team
using
automated
deployment
scripts
results
in
its
maturity
&
less
prone
to
errors.
ì Take
off
the
dependency
from
the
deployment
expert
and
uLlize
them
for
more
challenging
tasks.
ì Its
fast,
cheap.
Facilitates
in
early
tesLng
&
faster
feedback
cycles.
ì Deployment
Logs
are
auditable
for
future
references.
h"p://linkedin.com/in/praneshvi"al
27
28. Deep
dive
into
Testing
Quadrant
Image
Credit:
Concept
defined
by
‘Brian
Marick’
(Diagram
obtained
from
“ConLnuous
Delivery”
by
‘Jez
Humble’
&
‘David
Farley’.
h"p://linkedin.com/in/praneshvi"al
28
29. Deep
Dive
into
Automated
Acceptance
Tests
ì Aim:
ì Avoid
manual
tests
to
whatever
extent
possible.
ì Steps
to
be
followed:
ì Tests
to
be
performed
in
producLon-‐like
environment.
ì If
sefng
up
environment
is
expensive,
use
a
scaled-‐down
environment.
ì Setup
the
actual
user’s
environment
on
a
grid.
ì Use
Business
language
in
the
scripts
instead
of
technical
jargon
(‘Place
Order’
instead
of
‘Clicking
on
bu.on
XYZ’).
ì Well-‐defined
exit
criteria
for
Pass
/
Fail
of
tests.
ì Don’t
fail
the
test
due
to
minor
issues.
h"p://linkedin.com/in/praneshvi"al
29
30. Deep
Dive
into
Automated
Acceptance
Tests
continued…
ì Steps
to
be
followed:
ì Include
a
few
tests
to
assert
external
systems.
ì If
you
don’t
care
about
a
parLcular
field,
don’t
bother
tesLng
it.
ì These
tests
should
be
run
a<er
every
deployment.
ì Block
the
pipeline
when
there
are
massive
failures.
ì Parallelize
the
tests
to
whatever
extent
possible.
ì Outcome
of
this
step
are
the
so<ware
packages
that
have
fought
against
all
the
tests
&
challenges
like
a
mythical
hero
and
ready
to
take
on
the
world
!!!
h"p://linkedin.com/in/praneshvi"al
30
31. Few
more
Generic
Anti-‐Patterns
ì TesLng
done
on
developer
machines.
ì Service
Engineering
team
hasn’t
even
seen
the
applicaLon
Lll
the
actual
release
date.
ì Installers,
ConfiguraLons
etc…
not
done
Lll
the
release
date.
ì No
collaboraLon
between
development
team
&
SE
teams.
ì Late
setup
of
Staging
Environment.
ì Release
too
many
changes,
unable
to
figure
out
what
caused
the
failure.
ì Changing
the
configuraLons
directly
on
ProducLon
o<en
resulLng
in
disasters.
h"p://linkedin.com/in/praneshvi"al
31
32. Adaption
of
Release
Engineering
ì Change
in
the
mindset
of
the
team
members.
ì All
aspects
of
development,
tesLng,
staging,
producLon
environments
(most
importantly
configuraLon
management)
to
be
managed
through
a
VCS.
ì Integrate
development,
tesLng,
release
teams
as
a
part
of
the
development
process.
ì Manage
the
Infrastructure
to
build
environments
in
no
Lme.
ì Beef
up
the
test
automaLon
coverage
so
that
there’s
not
much
reliance
on
Manual
tesLng.
ì Rehearse
the
release
&
rollback
process
so
that
its
easy
to
do
it
Lme
&
again.
ì Reach
a
stage
wherein
“So<ware
Release”
is
in
self-‐service
mode.
h"p://linkedin.com/in/praneshvi"al
32
33. Tools
Used
at
each
of
the
stages.
ì Version
control
–
Git
ì Build
Tools
–
Ant,
Nant,
MSBuild,
gmake,
Maven,
Buildr,
Psake.
ì Agile
/
Scrum
–
Jira.
ì StaLc
validaLon
–
Coverity,
SonarQube
ì Unit
tesLng
–
junit
ì Test
automaLon
–
Protractor,
Selenium
ì ConLnuous
IntegraLon
–
Jenkins,
Atlassian
Bamboo,
Thoughtworks
Go,
UrbanCode
AntHillPro
ì Deployment
–
Pogo,
Chef
ì Environment
provisioning
–
Puppet,
Chef
ì IAAS,
PAAS
–
AWS,
Azure,
Docker,
Vagrant
h"p://linkedin.com/in/praneshvi"al
33
34. Tools
Used
at
each
of
the
stages.
ì Image
Credit
:
h.p://maestrodev.com
h"p://linkedin.com/in/praneshvi"al
34
35. Managing
Environments
ì No
ApplicaLon
is
an
Island.
ì Poor
ConfiguraLon
Management
results
in
significant
waste
of
Lme,
addiLonal
costs,
tech
debt
etc…
ì Should
always
be
cheaper
to
create
a
new
environment
than
repairing
a
broken
environment.
ì Few
of
the
names
used
for
Environments
ì Development
ì IntegraLon
ì QA
/
TesLng
ì Staging
/
Pre-‐ProducLon
ì Performance
ì Canary
/
Bucket
TesLng
ì ProducLon
h"p://linkedin.com/in/praneshvi"al
35
36. Managing
Releases
of
complex
systems
h"p://linkedin.com/in/praneshvi"al
36
Image
Credit:
Slide
deck
available
at
h.ps://learn.chef.io/
37. Managing
Releases
of
complex
systems
h"p://linkedin.com/in/praneshvi"al
37
OrchestraLon:
ì Automated
arrangement,
coordinaLon,
and
management
of
complex
computer
systems,
middleware,
and
services.
ì Aligning
the
business
request
with
the
applicaLons,
data,
and
infrastructure
ì Deployment
Rhythm
ì Its
about
gefng
the
perfect
configuraLon,
checking
in
these
values
and
automate
the
release
using
these
values.
ì Have
the
right
sequence
of
steps
in
the
configuraLon
file.
ì Have
the
right
kind
of
checks
&
balances
at
every
stage.
ì PracLce
roll-‐backs
in
case
of
issues.
ì Implement
fail-‐safe
methodologies
in
case
of
issues.
ì Build
environments
wherein
the
ProducLon
traffic
can
be
replayed
(Use
of
access
logs
to
simulate
user
acLons).
38. Steps
involved
to
build
a
deployment
pipeline
ì Model
your
value
stream
&
create
a
walking
skeleton.
ì Automate
the
build
&
deployment
process.
ì Automate
unit
tests
&
code
analysis.
ì Automate
Acceptance
Tests.
ì Automate
Releases.
h"p://linkedin.com/in/praneshvi"al
38
39. Multi-‐Tenant
Applications
ì Customers
share
the
same
cloud
plavorm
and
infrastructure
and
their
data
is
commingled.
ì Single
code-‐base
for
the
applicaLon.
ì Upgrades
are
executed
easily
by
the
SaaS
provider.
ì All
the
tenants
are
using
the
same
version.
ì Data
of
different
tenants
is
stored
in
the
same
place,
however,
measures
taken
to
make
it
inaccessible
to
other
tenants.
ì BuckeLze
the
access
based
on
the
IP
Range
/
Cookie
range
/
Header
InformaLon
etc...
ì Toggle
a
Feature
using
configuraLon.
ì Hard
to
maintain
different
versions
for
different
tenants.
h"p://linkedin.com/in/praneshvi"al
39
40. Multi-‐Instance
Applications
ì MulLple
customers
run
their
own
separate
instance
of
an
applicaLon
and
OS
running
on
a
separate
VM.
ì Avoid
comingling
of
data.
ì Develop
&
use
their
own
logical
piece
of
the
cloud
service.
ì Allows
for
greater
flexibility
and
control
of
configuraLon,
customizaLon,
updates
and
upgrades.
ì Ability
to
migrate
instance
to
an
on-‐premise
server,
or
to
another
cloud
hosLng
provider
h"p://linkedin.com/in/praneshvi"al
40
41. Zero
Downtime
Deployment
ì What
is
‘Zero
DownLme
Deployment’?
ì What
is
‘Out
Of
RotaLon’
(OOR)
?
ì What
is
‘Concurrency’
?
ì Colo
(Data-‐Center)
based
deployments.
h"p://linkedin.com/in/praneshvi"al
41
42. Extracting
the
server
logs
ì Standardize
the
logging
messages.
Involves
lot
of
effort
from
the
development
teams.
ì Setup
Splunk
alerts
for
‘FATAL’
errors
in
the
code.
h"p://linkedin.com/in/praneshvi"al
42
43. Next
generation
tools
in
the
DevOps
world
ì Chef
ì Puppet
ì Cfengine
ì Salt
h"p://linkedin.com/in/praneshvi"al
43
44. Preparation
for
the
Release
ì Any
issues
during
the
release,
stop
or
postpone
the
release.
Stability
takes
the
highest
priority.
ì Prepare
Release
Plan
or
Runbook
with
correct
sets
and
if
possible
automate
them.
ì IdenLfy
the
error-‐prone
steps
and
automate
them.
ì Perform
the
drill
for
performing
rolling
back
of
the
releases.
ì Should
be
as
simple
as
selecLng
a
value
and
clicking
a
bu.on.
ì Let
one
team
perform
all
the
releases.
(Too
many
cooks
spoil
the
broth).
h"p://linkedin.com/in/praneshvi"al
44
45. Maturity
of
a
“Deployment
Pipeline”
?
h"p://linkedin.com/in/praneshvi"al
45
ì Image
Credit:
h.p://www.praqma.com/
48. References:
ì Details
about
each
of
the
phases
from
“ConLnuous
Delivery”
by
Jez
Humble,
David
Farley
ì Source
of
some
of
the
generic
images
used
–
“Unknown”.
ì RespecLve
credits
given
to
the
images
used
in
the
same
slide.
ì h.ps://gigaom.com/2014/01/26/mulL-‐tenant-‐or-‐mulL-‐instance-‐cloud-‐lets-‐
do-‐both/
ì h.p://diginomica.com/2013/12/20/mulL-‐tenant-‐mulL-‐instance-‐saas-‐
spectrum/
ì h.ps://msdn.microso<.com/en-‐us/library/hh534478.aspx
ì h.ps://www.youtube.com/watch?v=CE4hLYhfmBE
-‐
Deployment
using
pogo.
h"p://linkedin.com/in/praneshvi"al
48