"How to build powerful CI / CD based on GitLab and Docker", Aleksandr Matkovs...Provectus
油
Aleksandr Matkovskiy Head of IT Department lives and works with the motto "Scaling and load balancing is our all!". Therefore, he has 3 sons and dreams to find DEV for his OPS.
You will be able to see how the CI / CD was created and saved our lives. From concept to the final product.
Vladislav Anikin Team Leader & Software Architect, specializing in SAAS flexible and scalable solutions for business. Driving DDD/TDD oriented squad of awesome SOLID developers.
You will be able to see how the CI / CD was created and saved our lives. From concept to the final product.
Chris Homer - Moving the entire stack to k8s within a year lessons learnedDariia Seimova
油
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.
rohit sharma - dev ops virtual assistant - automate devops stuffs using nlp a...Dariia Seimova
油
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 bodyDariia Seimova
油
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.
victoriia basarab - special aspects of dev ops platform developmentDariia Seimova
油
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.
sveta smirnova - my sql performance schema in actionDariia Seimova
油
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 frameworkDariia Seimova
油
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 instanceDariia Seimova
油
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 ciDariia Seimova
油
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 processDariia Seimova
油
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 scienceDariia Seimova
油
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.
4. 12 舒从仂仂于 DevOps
https://devopsfactors.com/
Shared Goals
Communication
Infrastructure as a code
Team structure
Knowledge sharing
Monitoring
CI
CD
Continuous improvement
Incident management
Roadmap
Hype-driven decisions
15. Communication with stakeholders
Be short
Try to find problem not
solution
Brainstorm
Use team power
Business language is hard
Try to get feedback
Build relationships