Skip to content

Commit

Permalink
Merge pull request #31 from devopsdays/master
Browse files Browse the repository at this point in the history
sddsd
  • Loading branch information
devopsdaysbh authored Sep 6, 2019
2 parents d74dc0a + e8f4252 commit a916d46
Show file tree
Hide file tree
Showing 135 changed files with 1,141 additions and 75 deletions.
15 changes: 15 additions & 0 deletions content/events/2019-auckland/program.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
+++
Title = "Program"
Type = "program"
Description = "Program for devopsdays Auckland 2019"
+++

<div class = "row">
<div class = "col">
<hr />
If Open Space is new to you, you may be interested in <a href="/pages/open-space-format">more details about Open Space</a>.
<hr />
This year we are also running workshops during the open spaces. These are reflected in yellow on the programme and run during the opens spaces. The numbers for these sessions will be limited based on a first in first served basis.
<hr />
</div>
</div>
10 changes: 10 additions & 0 deletions content/events/2019-auckland/program/brooke-treadgold.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
+++
Talk_date = "2019-10-21"
Talk_start_time = "09:10"
Talk_end_time = "09:45"
Title = "Going back to basics"
Type = "talk"
Speakers = ["brooke-treadgold"]

+++
It is very rarely sufficient to just “automate” existing processes in large organisations because often they are no longer fit for purpose. So whys it so hard to change a process? Why are empathy, influence and risk management so important? Let’s go back to basics and remember what we care about.
16 changes: 16 additions & 0 deletions content/events/2019-auckland/program/cameron-huysmans.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Designing an Enterprise Secrets Management Service using HashiCorp Vault"
Type = "talk"
Speakers = ["cameron-huysmans"]

+++
In the period 2017 through 2019, after nearly thirty years of consolidation around a layered internal IT security model, a major Australian bank shifted its business scope to include the consumption of public cloud technologies to support a significant core of its business operations.

This is a major departure from a historical alignment, where the banks IT systems were physically domiciled within their premises and protected from public or unmanaged ingress by a perimeter DMZ and a host of physical and process controls.

Outright ownership of premises, or lease responsibility for these environments, conferred the most basic human access control to ensure operational security. On top of that, ‘defence in depth’ centred around a layered network security architecture has to date, heavily influenced the attitude to secure operations.

This talk begins by observing the ground rules for the prior state and examines how that prevailing philosophy has been disrupted by a move to the overt consumption of public cloud infrastructure in support of many core banking functions; then it examines how we approach those concerns from the perspective of human and machine user access and the correct attribution of tech accountability and authority across all the banks business operations including cloud, in a more complex business landscape.
15 changes: 15 additions & 0 deletions content/events/2019-auckland/program/cath-jones.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "The Myth of the Senior Engineer"
Type = "talk"
Speakers = ["cath-jones"]

+++

Job descriptions for senior engineers often require people who can “hit the ground running” or “get in and get stuff done”. In this session, I examine the myth around the “senior engineer” and why people can’t just get in and get stuff done. No matter the engineer’s experience level, codebases are more than just code they represent the values and history of a business.

I address this issue through research conducted by Github and Google along with business management academics into Organisational Socialisation within their own companies but also within the open-source ecosystem. I present practical steps that companies can take when hiring to create an engaging experience for senior engineers that have proven benefits for productivity and career development.

I present examples from within Buildkite and other organisations that showcase how this research has been implemented either successfully or unsuccessfully.
20 changes: 20 additions & 0 deletions content/events/2019-auckland/program/charles-korn.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Dockerised local build and testing environments made easy"
Type = "talk"
Speakers = ["charles-korn"]

+++
In 2019 we still struggle with our local build and testing environments. Every developer will be familiar with problems like:

* trying to set up a new project, only to discover that the requirements listed in the readme are out of date, incomplete or no longer available
* trying to set up a new project, only to discover that there are no requirements listed in the readme
* “works on my machine” issues like inconsistencies introduced by slightly different configurations across your machine, your colleagues’ machines and CI
* flaky integration and journey test runs against external dependencies like databases caused by environmental issues
* each project having its own esoteric shell script or makefile used to drive development tasks

There is a better way! Imagine being able to run your builds and tests quickly, consistently and completely automatically everywhere - on your machine, your colleagues’ machines and on CI - and to onboard new team members in just a few minutes, thanks to the power of Docker. And all this without fiddling around with Docker Compose files or shell scripts.

Come and learn about the technique and see a demo of a tool (recently rated ‘trial’ on the ThoughtWorks Tech Radar) that makes implementing this idea much easier.
26 changes: 26 additions & 0 deletions content/events/2019-auckland/program/corneile-britz.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "A Single Window To Running Your Business"
Type = "talk"
Speakers = ["corneile-britz"]

+++
### Challenge

Most IT environments we deal with contain a great deal of information, logs, and metrics driven by tools such as: * SumoLogic * Splunk * DynaTrace * AppInsights * SCOM * PRTG * something built in-house…

These tools may be useful in isolation, but often results in substantial waste and distrust due to information not being shared between teams and departments. Furthermore, duplication of alerts may be sent by email, text or something else.

Typically these tools are focused on IT metrics, but they need to include business metrics such as revenue flow or call volumes.

### Solution Statement

Metrics and logs are very different with each performing different functions. Recognising that there is not a single tool that can address all the concerns, we focus on combining their strengths.

__*Lets establish central monitoring, and destroy the silos!*__

A central view of the environment enables everyone to view the same source of information based on their individual needs.

In addition to having a single central source of information, we can leverage the same platform to establish a consolidated approach to our alerting requirements. This will result in systems and packages to focus on their original intent without the burden of monitoring and alerting. Through this combination and centralisation, we also enable the organisation to rationalise the needs of the systems, such as storage and compute. By employing this strategy, software developers gain a great deal more freedom, autonomy and ultimately become more efficient and effective.
11 changes: 11 additions & 0 deletions content/events/2019-auckland/program/craig-box.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Teaching Old Servers New Tricks: extending the service mesh outside the cluster"
Type = "talk"
Speakers = ["craig-box"]

+++

Service meshes give you a great set of features “for free”, but only on top of a Kubernetes environment. If you’re not building something brand new, you probably have VMs, physical servers, even mainframes. Why should the start-up kids have all the fun? Let’s add “old infrastructure” to the mesh too.
17 changes: 17 additions & 0 deletions content/events/2019-auckland/program/david-white.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "The 'How' of Culture in DevOps - Improving the Communication"
Type = "talk"
Speakers = ["david-white"]

+++

DevOps = CALMS (where C is for CULTURE)

The biggest problems we face are not technical. They are human.

How do we get our silos talking to each other? eg the Dev Lead and the Ops Lead? Or Sales with Dev before promising a delivery date?

Learn how to communicate to get both partys’ needs met.
11 changes: 11 additions & 0 deletions content/events/2019-auckland/program/everett-toews.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Is GitOps worthy of the [BuzzWord]Ops moniker?"
Type = "talk"
Speakers = ["everett-toews"]

+++

GitOps is about applying the Git workflow to operations. Said another way, it's about applying a developer experience (DX) to ops. Developer experience for APIs, SDKs, CLIs, and docs tend to take up all of the oxygen in the room. However, I propose DX for ops is an idea whose time has come.
15 changes: 15 additions & 0 deletions content/events/2019-auckland/program/gleidson-nascimento.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Packaging OpenShift Origin Kubernetes Distribution (OKD)"
Type = "talk"
Speakers = ["gleidson-nascimento"]

+++

OpenShift Origin project (https://github.com/openshift/origin) is the source of OpenShift, the popular Enterprise Kubernetes distribution. But, how do this software gets packaged and released?

This ignite talk will explain how the CentOS community structures the SIGs - Special Interest Groups, what automation is used to build and test packages and how the packages are released.

Finally, we will explain how you can collaborate with the community and the release of packages.
9 changes: 9 additions & 0 deletions content/events/2019-auckland/program/jane-miceli.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "TBA"
Type = "talk"
Speakers = ["jane-miceli"]

+++
11 changes: 11 additions & 0 deletions content/events/2019-auckland/program/joel-wiramu-pauling.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Why Bare Metal still maters"
Type = "talk"
Speakers = ["joel-wiramu-pauling"]

+++

With the move to cloud service providers. Baremetal seems far from the minds of the active Devops practitioners mind. However on-prem is still important and cloud can still be a place where dragons reside.
15 changes: 15 additions & 0 deletions content/events/2019-auckland/program/joshua-king-workshop.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "How I Failed My Way to Success with Azure DevOps"
Type = "talk"
Speakers = ["joshua-king"]

+++

Some people learn by reading. Some by watching videos. Apparently I learn by failing and head-desking.

Learn how I super charged my Ops tooling with the power of CI/CD pipelines using Azure DevOps and avoid the mistakes I made along the way.

While my tooling is PowerShell based, my aim is to show how easy it can be to leverage Azure DevOps services for almost any use case.
19 changes: 19 additions & 0 deletions content/events/2019-auckland/program/joshua-king.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Don't Reinvent the Wheel, Just Realign It"
Type = "talk"
Speakers = ["joshua-king"]

+++

More than ever, time to market can make or break business initiatives and your ability to quickly deliver quality tooling is critical.

Yeah, I know: It is fun to wade into a new project and build something from nothing. We know what we need to know to get the job done, and surely no one else could have done a better job of it … right?

The reality is that you’re probably reinventing a wheel.

Using existing PowerShell modules, .NET libraries, and APIs, can help you build your own tools much faster. This frees you up to focus on the specifics of your problem rather than the underlying, time-consuming, foundation.

Be the time efficient, tool building hero your organization needs, not a speed bump!
13 changes: 13 additions & 0 deletions content/events/2019-auckland/program/julie-gunderson.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "You Can't Buy DevOps"
Type = "talk"
Speakers = ["julie-gunderson"]

+++

As the DevOps movement continues to see momentum, many organizations still don’t know where to start. A common misconception is tooling will make you “DevOps”, while tools can give you software that will allow you to automate or continuously deliver or monitor, alone they won’t get you to necessary processes to take advantage of the benefits DevOps has to offer. In this talk attendees will learn why it’s the people that matter most and how to leverage DevOps best practices along with processes to make the most out of your DevOps journey.

Being a champion in the DevOps world means going beyond the win and by delving deeper into the team/organizational structure and culture, thereby identifying outlying issues beyond tools, and then working with others to embrace necessary change that lead to defined results. This talk will lay the groundwork for individuals and/or teams who are looking to transform and adopt DevOps.
20 changes: 20 additions & 0 deletions content/events/2019-auckland/program/kiwi-ingenuity.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Kiwi Ingenuity - Kiwi’s can Overcome Tough Problems In DevOps"
Type = "talk"
Speakers = ["allen-geer", "michael-harrod"]

+++

Kiwi Organisations face specific challenges when adopting DevOps enabled New Ways of Working. In this plenary talk, we will review some of the common problems we are encountering adopting DevOps practices across several large Kiwi Organisations. We will discuss what these problems are, how they affect the DevOps culture and transformation, and provide some suggestions for how both leaders and team members can work to overcome them.

### Topics

* Comparing and Contrasting Culture in the United States vs New Zealand
* Kiwi Scale
* Teaching an Old Kiwi New Tricks
* Competitive Forces and Monetising Kiwi Toil
* Kiwi DevOps Models

14 changes: 14 additions & 0 deletions content/events/2019-auckland/program/laura-bell.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Securing the systems of the future"
Type = "talk"
Speakers = ["laura-bell"]

+++

The future of technology is exciting, innovative and fast paced. The systems we develop today are solving some of the biggest challenges of our age. How will security fit into this new world? How can you bring security into systems that are unlike anything we've built before?

Moving us from the importance of basic security hygiene to the emergence of threat in machine learning and autonomous systems, In this talk we will explore how we secure the future and why sometimes we need to learn from our history to do so.

19 changes: 19 additions & 0 deletions content/events/2019-auckland/program/liz-hubertz.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "FontOps: Serverless Architecture & the Future of Font Processing"
Type = "talk"
Speakers = ["liz-hubertz"]

+++

How does a font file go from a designer’s laptop to being used in the wild on the web, in applications like Photoshop, and on a user’s laptop? This process requires an entire team of designers, font experts, and you guessed it - devops people!

This year, the Adobe Fonts team embarked on a project to modernize our font processing pipeline: The way a font gets validated for quality before it can be used in the wild. To build this system, we had to work with some interesting constraints:

* Individual validators may be integrated from anywhere, by any developer, at any time. They might even be open source software, or pieces of software submitted by teams outside of Adobe.
* We need to minimize dependencies and domain-specific knowledge, since not all font experts are also devops experts
* We need an easy way to track, within an individual font asset, which overall version of the pipeline was used for processing, as well as the version of each component that was used within that pipeline

In the end, we decided on an interconnected system of lambdas, stitched together using an AWS step function with deployment automated through a series of Jenkins pipelines. The result was a pretty cool, easy-to-use system that processes at 1K (Fonts Per Minute!)
15 changes: 15 additions & 0 deletions content/events/2019-auckland/program/mandi-buswell.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "What are Kubernetes Operators and Why do I care"
Type = "talk"
Speakers = ["mandi-buswell"]

+++

Automation and collaboration are key elements to successful DevOps. Cultural change being the most important tool in your toolkit, but we all know that technology that supports teams to work collaboratively and to automate everything support the cultural change and the ways of working necessary for successful DevOps.

We already have CI/CD tooling and container technology so what’s next? Have you heard about Kubernetes operators? You may have heard people mentioning them, you may have heard people talk about how significant they will be in the next wave of growth in container workload management - but why and what does that mean for DevOps - just another flash in the pan or are these operator thingys really going to change the landscape and excel us into productive, collaborative teams that delivery value more readily and more easily for our business and customers.

In my ignite talk I’ll attempt to demystify these operators and share why DevOps teams should care.
15 changes: 15 additions & 0 deletions content/events/2019-auckland/program/piyush-verma.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Software/Site Reliability of Distributed Systems"
Type = "talk"
Speakers = ["piyush-verma"]

+++

Underneath all products, whether your code or a service that you connect to, there will be a disk, a network, a CPU, or a Memory that will fail. The talk considers a sample and straightforward product and evaluates the depths of each failure point, impact, cost, and changes need to overcome these.

Every product either dies a hero or lives long enough to hit Reliability issues. While you go about fixing this, What is the cost, both in terms of effort and business lost, of failure and how much does each nine of reliability cost?

The talk considers a sample and straightforward product and evaluates the depths of each failure point. We take one fault at a time and introduce incremental changes to the architecture, the product, and the support structure like monitoring and logging to detect and overcome those failures.
17 changes: 17 additions & 0 deletions content/events/2019-auckland/program/shahid-iqbal.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Kubernetes, Azure & .NET - what's it all about?"
Type = "talk"
Speakers = ["shahid-iqbal"]

+++

Everyone seems to be talking about Kubernetes with companies seemingly tripping over themselves to support or adopt it.

In this talk we’ll introduce Kubernetes, discuss the key concepts of the platform, it’s high level architecture and how to get a Kubernetes cluster up and running in minutes in Azure.

We’ll talk about and demo deploying .NET applications to Kubernetes and we’ll finish with a discussion of the future where you can deploy both legacy and modern .NET applications to the same platform.

If you’re interested in Kubernetes and you’re not a .NET developer this session still has something for you
17 changes: 17 additions & 0 deletions content/events/2019-auckland/program/srdan-dukic.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
+++
Talk_date = ""
Talk_start_time = ""
Talk_end_time = ""
Title = "Implicit trust agreement in Learning Organizations"
Type = "talk"
Speakers = ["srdan-dukic"]

+++

The push for automation in our daily work brings up a moral dilemma of sorts, namely whether or not we have a responsibility to let people know that the work is being performed by code.

This dilemma has parallels to the early days of Lean/TPS where workers were encouraged to find improvements to the production systems even if it meant that the resulting efficiencies would lead to a lack of demand for skills. This talks looks at the implicit agreements made between the organization and workers where one committed to ensuring that employees would have work as long as there was a commitment to learning/retraining.

It is hoped that this talk inspires open discussion and thought around investment and motivation in learning and training.

See: https://hbr.org/2008/06/the-contradictions-that-drive-toyotas-success https://www.theatlantic.com/technology/archive/2018/10/agents-of-automation/568795/
Loading

0 comments on commit a916d46

Please sign in to comment.