veyepar: Love thy future self: making your systems ops-friendly

Author(s):	Matt Palmer
Location	Guthrie Theatre CB06.03.28
Date	jan Mon 22	Days Raw Files
Start	15:00	First Raw Start	14:27
Duration	0:25:0	Offset	0:32:42
End	15:25	Last Raw End	15:57
Chapters	00:00 0:16:13
Total cuts_time	24 min.

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

assets release.pdf Love_thy_future_self_making_your_systems_opsfriendly.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

No matter how good your code is, that beautiful system you've built is going to break.  Or someone is going to break it.  Either way, sooner or later, you system going to have problems, and someone will have the job of figuring out what is wrong and how to fix it.  It might be you, if you're in a "DevOps" culture, or it might be some graveyard shift junior sysadmin who got stuck with the pager.

Whoever it is who gets the call, there are a variety of tools and techniques you can apply to your code to make it easier to isolate the location of the fault, determine the cause and identify possible mitigations and fixes.

This talk will go through the basics of why things break, how problems are found and fixed, and the few small changes in how systems and services are developed that can make a big difference to the ease of finding problems, and the time it takes to get a problematic service back on its feet.  If you develop software, you owe it to your future self (or the graveyard shift junior sysadmin) to catch this talk.

Comment:

production notes

2018-01-22/14_27_18.ts Apply: 14:38:05 - 14:40:13 ( 00:02:08 ) S: 14:27:18 - E: 14:57:17 D: 00:29:59 (Start: 647.0) (End: 775.0) show more...

vlc ~/Videos/veyepar/lca/lca2018/dv/guthrie/2018-01-22/14_27_18.ts :start-time=0647.0 --audio-desync=0

	Raw File	Cut List
	14:27:18		seconds: 647.0 Wall: 14:38:05
Duration	00:29:59
	14:57:17		seconds: 775.0 Wall: 14:40:13
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

2018-01-22/14_27_18.ts Apply: 14:40:13 - 14:57:17 ( 00:17:04 ) S: 14:27:18 - E: 14:57:17 D: 00:29:59 (Start: 775.0) show more...

vlc ~/Videos/veyepar/lca/lca2018/dv/guthrie/2018-01-22/14_27_18.ts :start-time=0775.0 --audio-desync=0

	Raw File	Cut List
	14:27:18		seconds: 775.0 Wall: 14:40:13
Duration	00:29:59
	14:57:17		seconds: 0.0 Wall: 14:27:18
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

2018-01-22/15_27_18.ts Apply: 15:27:18 - 15:35:40 ( 00:08:22 ) S: 15:27:18 - E: 15:57:18 D: 00:30:00 (End: 502.606329) show more...

vlc ~/Videos/veyepar/lca/lca2018/dv/guthrie/2018-01-22/15_27_18.ts :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	15:27:18		seconds: 0.0 Wall: 15:27:18
Duration	00:30:00
	15:57:18		seconds: 502.606329 Wall: 15:35:40
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete