veyepar: The Open Sourcing of Infrastructure

Author(s):	Elizabeth K. Joseph
Location	Green Theatre CB07.02.25
Date	jan Wed 24	Days Raw Files
Start	14:35	First Raw Start	14:12
Duration	0:45:0	Offset	0:22:35
End	15:20	Last Raw End	15:42
Chapters	00:00 0:07:40 0:37:40
Total cuts_time	38 min.

http://lca2018.linux.org.au/schedule/presentation/59/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive public tweet mp4 svg png

assets release.pdf The_Open_Sourcing_of_Infrastructure.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

In recent years we've been seeing a shift in how infrastructures are being managed with the help of open source tooling and infrastructure software.

Well over a decade ago the LAMP stack broke us free from proprietary infrastructure tooling. With subsequent the rise of open source configuration management systems, websites sprung up so that common configurations, like Puppet modules and Chef recipes, from these systems could be shared between organizations using them in production.

Today, following a rush to cloud, companies are now looking for open source tooling to build cloud-like environments in their own new data centers. Technologies like OpenStack and DC/OS, powered by Apache Mesos, are allowing them to replicate much of the functionality that was previously only available with proprietary, hosted solutions. Taking this one step further, several open source projects and organizations have begun full-scale open sourcing of their infrastructures, allowing other organizations to directly benefit from their Continuous Integration tooling and more. Complete infrastructures have now become open source projects unto themselves, and operations engineers becoming more experienced open source contributors, alongside their developer colleagues.

Join me in look back through the history of why we chose to go with open source, and what it can teach us today as we evaluate building our applications against cloud platforms, APIs and more. I'll explore what questions should be asked before selecting a platform, some of the open source options available, and share examples of what organizations have gained by being very open about how they've built their infrastructure.

Comment:

production notes