Adriana Villela
Principal Developer Advocate at Dynatrace
Toronto, Canada
Actions
Adriana Villela is a Principal Developer Advocate, helping companies achieve reliability greatness through Observability, SRE, & DevOps practices. Previously, she managed a Platform Engineering team & an Observability Practices team at Tucows. Adriana has worked at various large-scale enterprises, as an individual contributor and leader, including Bank of Montreal, Ceridian, and Accenture. Adriana is a blogger, host of the Geeking Out Podcast, CNCF Ambassador, and HashiCorp Ambassador.
Area of Expertise
Topics
How to Nomadify Your Kubernetes Manifests
Why should Kubernetes have all the fun? This talk walks developers through the process of converting Kubernetes manifests to Nomad job specs. I’ll cover how to translate Kubernetes manifests to Nomad jobspecs, how to get services to talk to each other using Consul, and how to expose services using Traefik. I’ll also demonstrate these topics using the OpenTelemetry Demo App.
Observe Thy CI/CD Pipelines with OpenTelemetry
We implement Observability for our applications and systems so that we can gain insight into problems as they occur and resolve them as quickly as possible; however, despite the need for it, there has been a lack of movement in Observability for CI/CD pipelines. CI/CD pipelines are part of the crucial backbone that runs our applications. We rely on them to build and deploy our applications, so it can be extremely frustrating when they start failing or behaving in unexpected ways – and we have no way to observe them.
In this session, Adriana Villela and Reese Lee will share how to unlock the superpowers of Observability for your CI/CD pipelines: why it’s needed, what makes a pipeline observable, how to do it with OpenTelemetry, as well as what additional supporting tooling is needed and available to make it happen. You will also learn about the challenges that we must overcome in order to have truly observable pipelines.
Translating failures into SLOs
Downtime is hard and we can definitely be proactive about failure by following practices like Chaos Engineering and SLOs. But how do you translate failure to SLO? What learnings should you leverage from the incidents you’ve been through? How can you turn a bad thing (something like an outage or downtime) into a good thing (information you have to prevent or mitigate future outages)?
Keeping your engineers happy: The Case for Self-Service Tooling
As the technology industry has evolved, the way we build applications has become more complex. We now require many moving parts to develop, test, and deploy our applications within our organizations. Developers like doing things themselves, and prefer not having to rely on a team to provision things for them. It is often time-consuming, and they often find themselves wishing that they could do it themselves, or they find themselves trying to do it themselves and skipping security requirements.
This is why it’s super exciting to see a movement toward self-serve provisioning coming from platform engineering teams. One of the main themes in platform engineering is to codify all the things. While these teams have already typically automated provisioning tasks, they often find themselves in a position whereby they are flooded with user provisioning requests from ticketing systems, which are often manually fulfilled.
This bottleneck becomes a huge waste of everyone’s time. It’s a waste of developers’ time because they are blocked as they wait around for the request to be fulfilled. It’s a waste of the platform engineer’s time, as they could be using that time to improve things such as system reliability.
In this talk, Adriana and Ana discuss the importance of self-service provisioning tooling to help bring order and peace of mind to developers and platform engineers alike!
Empowering Users Through Platform Engineering: Unleashing the Potential of Self-Service Tooling
Over the past two decades, the software industry has witnessed a transformative shift in how organizations operate. Among the newer manifestations is the emergence of Platform Engineering (PE). In 2023, there exists a widespread desire to address the question: “DevOps vs SRE vs Platform Engineering?” But must it be an either-or scenario?
DevOps initially prioritized collaboration, while SRE incorporated customer impact and reliability. As companies grew and faced increased complexity, SRE teams expanded to ensure reliable online experiences. Platform Engineering (PE) builds on DevOps and SRE, focusing on customer-centricity and considering developers as internal customers.
This talk gives an overview of Platform Engineering and explores the benefits of prioritizing self-service tooling. Witness a live demo combining CNCF projects and other open-source tools to create a reliable platform that ensures customer satisfaction, both internally and externally.
Adriana Villela
Principal Developer Advocate at Dynatrace
Toronto, Canada
Actions
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top