Hi
user
Admin Login:
Username:
Password:
Name:
Order in the chaos: or lessons learnt on planning in operations
--client
lca
--show
lca2016
--room r1mix 10769 --force
Next: 12 From Commit to Cloud
show more...
Marks
Author(s):
Peter Hall
Location
Costa Hall
Date
feb Tue 02
Days Raw Files
Start
16:15
First Raw Start
16:12
Duration
0:15:00
Offset
0:02:13
End
16:30
Last Raw End
16:42
Chapters
00:00
0:09:25
Total cuts_time
17 min.
https://linux.conf.au/schedule/30337/view_talk
raw-playlist
raw-mp4-playlist
encoded-files-playlist
host
archive
tweet
mp4
svg
png
assets
release.pdf
Order_in_the_chaos_or_lessons_learnt_on_planning_in_operations.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
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
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
Planning can be challenging in any part of IT, but what if you don't know what *might* happen tomorrow, service reliability, load issues, changing user requirements or that special project that you only just heard about and needs to go live Monday. Of course to any systems administrator I'm not explaining anything new. So how we plan in operations? or are we destined to continue like this forever? This talk will look at some of the strategies my team has used to increase happiness, productivity and visibility of the work we are doing. While a lot of what I will talk about would certainly fit in the "good devops practices" bucket, this isn't a devops talk. I will attempt to keep it to actionable items you can start to implement on Monday.
Comment:
production notes
2016-02-02/16_12_47.ts
Apply:
16:22:28 - 16:22:47 ( 00:00:19 )
S:
16:12:47 -
E:
16:22:47
D:
00:10:00
(
Start:
581.0)
show more...
vlc ~/Videos/veyepar/lca/lca2016/dv/r1mix/2016-02-02/16_12_47.ts :start-time=0581.0 --audio-desync=0
Raw File
Cut List
16:12:47
seconds: 581.0
Wall: 16:22:28
Duration
00:10:00
16:22:47
seconds: 0.0
Wall: 16:12:47
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2016-02-02/16_22_47.ts
Apply:
16:23:21 - 16:32:47 ( 00:09:25 )
S:
16:22:47 -
E:
16:32:47
D:
00:10:00
(
Start:
34.968515)
show more...
vlc ~/Videos/veyepar/lca/lca2016/dv/r1mix/2016-02-02/16_22_47.ts :start-time=034.968515 --audio-desync=0
Raw File
Cut List
16:22:47
seconds: 34.968515
Wall: 16:23:21
Duration
00:10:00
16:32:47
seconds: 0.0
Wall: 16:22:47
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2016-02-02/16_32_47.ts
Apply:
16:32:47 - 16:40:46 ( 00:07:59 )
S:
16:32:47 -
E:
16:42:47
D:
00:10:00
(
End:
479.966888)
show more...
vlc ~/Videos/veyepar/lca/lca2016/dv/r1mix/2016-02-02/16_32_47.ts :start-time=00.0 --audio-desync=0
Raw File
Cut List
16:32:47
seconds: 0.0
Wall: 16:32:47
Duration
00:10:00
16:42:47
seconds: 479.966888
Wall: 16:40:46
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
2016-02-02/16_12_47.ts
2016-02-02/16_22_47.ts
2016-02-02/16_32_47.ts
Veyepar
Video Eyeball Processor and Review
