Discover and read the best of Twitter Threads about #DevOps

Most recents (24)

The shift-left approach in the software testing world is when testing is performed early on in the lifecycle of the product. But given the growing complexities of products in the market today, we must customize solutions that work for your organization.
In this article, we will discuss a few applied scenarios in shifting left/right, and share how customized approaches for your teams are critical in the success of your test automation efforts.
Read 7 tweets
🎉 I'm super excited to announce that I recently joined Univeris as a Site Reliability Engineer.
I am highly passionate about Site reliability engineering and DevOps engineering, and it's been a wonderful experience working at Univeris, managing infrastructure at a large scale.
Moreover, it's going great learning and implementing in-demand tools and technologies along with their best practices. I'm glad to be a part of this esteemed organization as a part-time engineer.
Read 6 tweets
By now, #DevOps shouldn't be a word you hear in your organization, and if you do, see if you can steer conversation towards specifics:
[A thread of 11, or 9 plus 2 bonuses 😅, plus a bonus bonus]
0) Steve, you love DevOps, why are you doing this, again?

The reason people talk about DevOps in 2021 is that they haven't drilled down into specifics, and they're missing a focal point. It's like GPS giving you directions to your city when you're looking for a bar. Zoom in!
1) A team lexicon

First off, define terms with your team so everyone can speak the same language, and make sure you can share a language with the larger org. When you say value, what does that mean? When we say infrastructure, is that specific enough?
Read 13 tweets
@GremlinInc Certified Chaos Engineering Practitioner (GCCEP)

⭐ Chaos engineering allows experimentation in the production environment to maintain customer trust, build confidence in the system's reliability, resiliency and availability and to avoid unexpected outages.
⭐ Why does @netflix use chaos engineering?
Netflix created Chaos Monkey to test the resilience of its IT infrastructure. It purposely disables any production instance running in Netflix's network to test its resiliency towards the downtime.
Thank you, @GremlinInc, @KoltonAndrus, Matthew Fornaciar, @tambryantbutow, and Andre Newman, for the official certification and workshop on Chaos Engineering.
Read 5 tweets
🎉 I am excited to share that I got selected for yet another scholarship, @SUSE Scholarship program Cloud-Native, by @udacity.

This is my 3rd scholarship with Udacity, and I am super excited to learn in-demand skills that are widely used at enterprises.
⭐ This course will help me to learn:
- Cloud-native application deployment best practices and strategies.
- CI/CD pipeline to structure, package, & release applications to #Kubernetes.
- #ArgoCD for the automatic rollout of the new features to the production environment.
Thank you, #Udacity and #SUSE, for providing such a fantastic opportunity! 💥

#UdacitySUSEScholars #cloud #devops #kubernetes #learning #cloudnative #scholarship #education
Read 4 tweets
🎉 Celebrating 16000+ members!

☁ 𝗘𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 𝗔𝗪𝗦 𝗖𝗹𝗼𝘂𝗱 - A Quora Space dedicated to Amazon Web Services (AWS) for the best answers, news, & tutorials.
🔗 awscloud.quora.com

✨ Want to contribute to the AWS community? Join here:
🔗 bit.ly/quoraaws
🔰 Find my answers on Quora:
🔗 bit.ly/priyankquora

Disclaimer: All product names & logos are the property of their respective owners.

#aws #amazon #awscloud #tutorial #quora #cloud #devops #cloudcomputing #community
@threadreaderapp unroll please
Read 3 tweets
🎉 I'm super excited to announce that I've successfully graduated from @udacity's AWS Cloud Architect Nanodegree.

It was an excellent learning experience to work on several real-world #projects. The program consists of 3+ projects, 100+ lessons, & 100+ hours of intense learning. Image
⭐ 𝗜 𝗵𝗮𝘃𝗲 𝘄𝗼𝗿𝗸𝗲𝗱 𝗼𝗻:
1) Recoverability in AWS
2) Design, Provision, & Monitor AWS #Infrastructure
3) Serverless Architecture
4) IaC using Terraform to provision various #AWS resources
5) Designing a DevSecOps Pipeline
6) Ensuring CIS standards for cloud security
🔖 𝗧𝗼𝗼𝗹𝘀 𝗜 𝘂𝘀𝗲𝗱:
- @awscloud, @HashiCorp's Terraform, @Lucidchart, AWS CloudFormation, AWS Config, AWS Security Hub, AWS Inspector, AWS Guard Duty, AWS Lambda, AWS CLI

More details: lnkd.in/dCD97Hg
Read 5 tweets
Masterclass in non-violent force being played out right now. Every web developer worldwide is being forced to choose one of the following two options...
A. Provide any amount of services to the Government of the Russian Federation (all branches, departments, joint ventures, etc)
-OR-
B. Use Github
Github is owned by Microsoft. Microsoft is headquartered in the State of Washington (US).
Therefore, you can only do one of these two things. Think it out. This is not a difficult decision. The #devops community knows how this will play out. There is only one feasible choice.
Read 4 tweets
I have created an @awscloud architecture diagram for a social media application with 50,000 single-region users.

It is a part of my 2nd project in @udacity AWS Cloud Architect nanodegree.

#awscloud #architecturedesign #architecture
#cloudcomputing #cloud #devops #aws Image
⭐ 𝗙𝗲𝗮𝘁𝘂𝗿𝗲𝘀 𝗮𝗻𝗱 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹𝗶𝘁𝘆:
- 2 Availability Zones
- VPC with Public & Private Subnets
- CDN: CloudFront hosted with S3 bucket
- Database: Master in AZ1 + Read replica in AZ2
- Web and App servers - load-balanced + Auto-scaling
Let me know what your thoughts are on this.

☁ @PriyankVaghela_ - Follow me to the cloud.
Read 4 tweets
#Reading #DevOps
《DevOps实践指南》第五章·选择合适的价值流作为切入点
绿地项目还是棕地项目,交互型系统还是记录型系统。
谨慎地选择DevOps转型的切入点,在组织的某些领域内进行实验、学习并创造价值,不会给整个组织带来不可逆的后果。同时,通过这种方式,我们能够建立稳固的群众基础。
绿地项目通常是指一些试点项目。
棕地项目是指那些已经服务客户的成熟产品或服务。
棕地项目在转型时可能会面临巨大的阻碍,特别是没有自动化测试,或者紧耦合架构导致团队无法独立开发、测试和部署。
记录型系统的变化速度通常较慢,并且有监管和合规性要求(例如SOX)。高德纳公司称这种系统为“类型1”,侧重于“做得正确”。
交互型系统的变化速度通常较快,因为它需要快速响应反馈,通过实验找到最能满足客户需求的方式。高德纳公司称这种系统为“类型2”,侧重于“做得快速”。
Read 3 tweets
#Reading #DevOps
《DevOps实践指南》第四章·第三步: 持续学习与实验原则
价值流的核心是建立高度信任的文化。每个人都是持续学习者,在日常工作中承担风险;科学的改进流程和开发产品,从成功和失败中积累经验教训,识别有价值的想法。局部经验会快速转化为全局改进,帮助整个组织尝试和实践新技术。
为日常工作的改进预留时间,从而进一步促进和保障学习。
通过不断向系统加压的方式,来强化持续改进。在可控的情况下,甚至通过在生产环境里模拟或者注入故障来增强弹性。
1.建立学习型组织和安全文化
技术价值流中,通过努力打造安全的工作系统,能建立起生机文化的基础。在意外和故障发生时,关注如何重新设计系统,从而防止事故复发,而不是去追究人的问题。
Spear博士认为,消除指责能够有效实现学习型组织,使“组织自我诊断和自我优化,并能熟练地定位和解决问题”。 Image
Read 7 tweets
#Reading #DevOps
《DevOps实践指南》第三章·第二步: 反馈原则
反馈原则使得价值流在从右向左的每个阶段中能够快速、持续地获得工作反馈。
1.及时发现问题
2.群策群力,战胜问题获取新知
3.在源头保障质量
4.为下游工作中心而优化
Steven Spear的论文认为,我们可能无法设计出绝对安全的系统,但以下措施能让复杂系统更安全地工作:
管理复杂的工作,从中识别出设计和操作的问题;
群策群力解决问题,从而快速地构建新知识;
在整个组织中,将区域性的新知识应用到全局;
领导者要持续培养有以上才能的人。
mitsloan.mit.edu/shared/ods/doc…
及时发现问题:
在技术价值流的每个阶段(包括产品管理、开发、QA、信息安全和运维),建立快速的反馈和前馈回路。包括创建自动化的构建、集成和测试,尽早检测出可能导致缺陷的代码变更。
建立全方位的监控系统,快速探测服务的意外情况。度量是否偏离了预期目标,并将监控结果辐射到整个价值流。
Read 6 tweets
#Reading #DevOps
《DevOps实践指南》第二章·第一步:流动原则
本章要描述的第一步工作法,就是建立从开发到运维之间快速的、平滑的、能向客户交付价值的工作流。
1.工作可视化
2.限制在制品数
3.减小批量大小
4.减少交接次数
5.持续地识别和改善约束点
6.消除日常工作中的困境和浪费
工作可视化:
通过这种方式(可视化工作板,如看板和sprint计划板),不仅能将工作内容可视化(能识别工作在哪里流动、排队或停滞),还能有效地管理工作,加速其从左至右的流动。还可以通过卡片从在看板上创建到移动至“完成”一列的时间,度量出工作的前置时间(工单创建后开始,到工作完成时结束)。 可视化工作板,图片来自DevOps Handbook
限制在制品数:
研究表明,即便是完成简单任务,如将各种几何形状分类,当同时执行多个任务时,效率也会显著降低。
技术工作通常是动态的,团队必须要同时满足很多利益干系人的需求,这导致临时安排控制了日常工作。
通过限制在制品数,还能更容易地发现工作中的阻碍。
Read 7 tweets
Where Programming, Ops, AI, and the Cloud are Headed in 2021
Following O'Reilly online learning trends to see what's coming next. oreilly.com/radar/where-pr…

Below will share some quotes around #DevOps and #Cloud topics from that report. Thread.
The most successful superstream series focused on software architecture and infrastructure and operations. Why? The in-person O’Reilly Software Architecture Conference was small but growing. But when the pandemic hit, companies found out that they really were online businesses.
And if they weren’t, they had to become online to survive. Even small restaurants and farm markets were adding online ordering features to their websites. Suddenly, the ability to design, build, and operate applications at scale wasn’t optional; it was necessary for survival.
Read 21 tweets
🏅10x Cloud Certified with Microsoft Certified: Azure Fundamentals

This exam covers #Azure fundamentals, high-level knowledge and working of cloud services within @Microsoft Azure.

Credly's Badge: lnkd.in/dRJP5_3

#microsoftazure #certification #devops #cloudcomputing
🎯 𝗘𝘅𝗮𝗺 𝗗𝗲𝘁𝗮𝗶𝗹𝘀:
🔖 Code: AZ-900
🔖 No of questions: 40-60
🔖 Passing score: 70% (700/1000)

💡 𝗦𝗸𝗶𝗹𝗹𝘀 𝘃𝗮𝗹𝗶𝗱𝗮𝘁𝗲𝗱:
- #Cloud concepts & Core Azure services
- General security & networking
- Identity, governance, compliance, & SLAs Image
⭐ 𝗥𝗲𝘀𝗼𝘂𝗿𝗰𝗲𝘀:
🔗 Exam details: lnkd.in/dmuQyMU
🔗 Self-paced Training: lnkd.in/drrgCsE
🔗 Free Whizlabs Practice Test: lnkd.in/dN9N-a8
🔗 Pluralsight: pluralsight.com/paths/microsof…

Keep exploring, stay hungry and keep learning! 😊
- @PriyankVaghela_
Read 4 tweets
Good news: It's the last week of February. You made it!

Great news: We have a ton of content for you this week!

23/02 12:30 GMT @AzureishLive
23/02 21:00 GMT @IoTeaLive
24/02 20:00 GMT #AzureishAfterDark
25/02 14:00 GMT @IoTeaLive
26/02 18:30 GMT @jonnychipz #InConvoWith

1/
Tuesday lunchtime, join @lrgulliver @jbjon and @pete_codes from 12:30 GMT as they enter part 3 of their zero-touch CI/CD build in @AzureDevOps. This week, they'll be building out infrastructure with Terraform!

2/
On Tuesday's @IoTeaLive from 9PM GMT, @Pete_codes and @cliffordagius will be talking about 3D printing and PCB design software! You may have seen @pete_codes designing a PCB for the #PicoProducer over the weekend!

3/
Read 8 tweets
#Reading #DevOps
"不管我们做出怎样的尝试,事情似乎总是变得越来越糟糕——面对日新月异的市场竞争,我们不再能够快速响应,也无法为客户提供稳定、可靠的服务。我们最终因此失去了市场。"——《DevOps实践指南》
所以DevOps一定程度上会加重内卷?“掌握”了DevOps的团队效率会更高,迭代速度更快,导致“没掌握”DevOps的团队加班加点?DevOps拯救世界🤣
#Reading #DevOps
“DevOps基于精益、约束理论、丰田生产系统、柔性工程、学习型组织、安全文化、人员优化因素等知识体系,并参考了高信任管理文化、服务型领导、组织变动管理等方法论。把所有这些最可信的原则综合地应用到IT价值流中,就产生出DevOps这样的成果。”
Read 5 tweets
#frontend engineers: What is your dream CI/CD pipeline? 🥰

Here is what we have at @contrahq 👇👇👇
precommit and prepush #git hooks are used to catch issues before they are pushed upstream.

* precommit runs only on staged files (takes few seconds)
* prepush runs #eslint #typescript and unit tests (takes up to 20 seconds)

Every time a commit is pushed:
1) We build a #docker image & bundle cypress and other development dependencies. This allows us to run all subsequent tasks using the same Docker image.

It is fast. Takes 2-4 minutes. 🏎
Read 10 tweets
Werner Vogels @Werner AWS re:Invent Keynote is coming up now.

Will be tweeting cool updates from his talk, so follow along!

#AWS #startups #AWSreInvent #reInvent2020 #cloud #CloudComputing #technology
By now, I mean in 40 minutes 😂...jumped the gun a bit.

But feed is up now and there will be a performance w/ DJ Shiftee and then AWS DeepRacer Championship Cup Finale starting shortly.

Werner's talk is 11 AM EST / 8 AM PST.
This DeepRacer final is pretty tight...
Read 42 tweets
Excited for my first re:Invent and getting ready for the @ajassy keynote coming up!

reinvent.awsevents.com

#awsreinvent #AWS #cloud
Loving the opening music act 🎸
Zach Person is the musician playing, so awesome...

Here is his Instagram - instagram.com/zachperson/
Read 75 tweets
Potentially unpopular opinion on the tech industry.

We're already good enough at doing.

#devops, #nocode, #agile are all mainly focused on building things better and faster.

That's not the bottleneck anymore. We should switch our focus to what comes before and after

\1
What comes before?

Context and Situation - WHY are we doing this?

and after?

Learning and Improvement - how are we going to get better over time?

\2
Agile practices were born into a time where building and shipping was a lot harder and more time consuming than it is now. The tech landscape also moved much slower.

A couple of hours every two weeks is no longer the right balance between execution and reflection.

\3
Read 7 tweets
Navigating the cloud and #DevOps horizon is hard, things are moving quickly.

ThoughtWorks recommends HOLD on handwritten AWS CloudFormation in #TechRadar 2019 edition. Building a complex infrastructure in essentially huge YAML text file is doomed to fail thoughtworks.com/radar/tools/ha…
You could thought that Templating in YAML is a solution here, but it's also on HOLD in #TechRadar 2019 by @thoughtworks thoughtworks.com/radar/techniqu…

The same about templating in JSON, because YAML is JSON actually. Better to use real programming language instead. The dev in #DevOps
So Terraform is the ADOPT in #TechRadar 2019 and "sensible default" that addresses the shortfalls of AWS CloudFormation as stated here:
thoughtworks.com/radar/tools/ha…

There are other options listed, including troposphere, sceptre, Stack Deployment Tool and Pulumi. Not sure if endorsed.
Read 8 tweets
A big help would be for the community to attract pen aka penetration testers to @thorchain_org.

Basically go to white hacker communities and invite them to break ChaosNet.

The faster we find major bugs / holes, the better.
2/ Individuals with such skills usually know:

#CyberSecurity
#Pentesting
#DevOps

There’s various networks out there which welcome related communities ie Reddit etc
@THORChainHammer bounty-thorchain-attack
Read 3 tweets
We've just launched new #DevOps content at cloud.google.com/devops today! There's an updated quick check to recommend which capabilities you should work on, and write-ups of new capabilities from the State of DevOps Report. More here: medium.com/@jezhumble/tak…
The quick check tool now recommends capabilities to prioritize in order to improve your performance against the four key metrics: devops-research.com/quickcheck.html Image
There's a new homepage for the DORA research program where you can explore the capabilities we've identified that drive improved performance, read State of DevOps Reports, and see solutions for many of the capabilities we've identified: devops-research.com/research.html
Read 13 tweets

Related hashtags

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!