Hi
user
Admin Login:
Username:
Password:
Name:
Scaling piuparts.debian.org to multiple architectures
--client
debian
--show
debconf17
--room bo 12482 --force
Next: 1 Managing Debian's RTC services
show more...
Marks
Author(s):
Holger Levsen
Location
Bo
Date
aug Fri 11
Days Raw Files
Start
11:00
First Raw Start
error-in-template
Duration
00:45:00
Offset
None
End
11:45
Last Raw End
Chapters
Total cuts_time
None min.
https://debconf17.debconf.org/talks/121/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Scaling_piupartsdebianorg_to_multiple_architectures.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
Currently piuparts.debian.org only tests Debian amd64. In this BoF we want to discuss how to scale this to multiple architectures and possible how to rewrite the web UI so that it scales with both more architectures as well as with 10 times more suites than it was written for. Basically if you are interested to help by writing a nice(!) webapp, you should attend this BoF. Or to put it differently: if you want to help Debian, but don't know how, this could be your opportunity to contribute to a rather central QA tool in Debian! Scaling piuparts to support multiple architectures could be done using two ways: the dumb and the smart way, where the latter uses a bit less hardware ressources but will require a bit of python coding. Join if you want to help here. (Also, we could start with the dumb way and later switch to the smart way…)
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review