DebConf19 on-site requirements
Andy and Paulo had a good discussion at the DebConf video sprint, about
DC19 on-site network and video requirements. It sounds like things are
going to be more complex than a typical DebConf. So I'm wondering if DSA
is willing to get involved in helping with the on-site network.
The accommodation is at a hotel nearby the University. There will be a
bar there and some hack-labs. Although there will also be hack-labs at
the university.
The local team is planning to lease an extra Internet connection for the
hotel for us. We're wondering if point-to-point wifi may be an option
(the hotel is a tall tower, and should have LOS to the campus, 1 block
away).
The university is currently expecting us to use normal university guest
accounts for WiFi. We're pushing back a little bit and suggesting an
SSID exclusively for us, that we can NAT.
Either way, it sounds like we're going to be running our own network in
the Hotel. And possibly our own network at the University.
Notes from Andy & Paulo's conversation
======================================
#1 Can we ‘patch’ network sockets in individual talk rooms so that there
is NO packet switch in the way? I.e patch 1 or 2 sockets by the stage
to the control room? If NOT can we have them on a separate VLAN i.e.
VLANroom1 VLANroom2
#2 Can we have 1 socket from each of the 2 talk ‘control rooms’, a
socket at the back of the video conference room (talk room 2), the
sockets in the rooms below the stage, and a socket for each server to be
placed in the machine room added to VLANdcvideo?
#3 Computing needs:
CPUs for encoding and video-mixing machines need to be from the last 3
years or so. 5-year old i7s don't quite cut it any more.
#3.1 Live video-mixing machines. Need 3 of them. 1 per video-ed talk room.
4core i7 class or better CPU.
4GB RAM
1TB usable storage
1Gbit Ethernet in VLANdcvideo
2x free PCI-E x1 slot (low-profile or full-height)
#3.2 Servers needed for Video team
Either a large server that can be split into several VMs or several
smaller boxes that can be run ‘bare metal’:
Storage & Encoder
4core (8 hyper thread) i7 class or better CPU
10TB usable Storage (RAID1)
> 16 GB RAM
> 4Gibt/s Ethernet in VLANdcvideo
Can be separated into multiple machines if necessary (using old
hardware). 1 storage and multiple encoder nodes.
But then network-connectivity becomes more important, as the encoding
is quite I/O intensive.
Stream Master
3 core (6 hyper thread) i5 class or better
200GB usable storage
> 4 GB RAM
> 1Gbit Ethernet in VLANdcvideo
> 10Mbit Ethernet Internet access with Public STATIC IP (no
blocked ports in or outbound)
Stream Mirror (local video streaming)
2 core (4 hyper thread) i5 class or better
10GB usable storage
> 4GB RAM
> 1Gbit Ethernet in VLANdcvideo
> 1Gbit Ethernet in VLANdc19
Attendee Router (this MAY have been requested by Infra team already)
2 core (4 hyper thread) i5 class or better
10GB usable storage
> 4GB RAM
> 1Gbit Ethernet in VLANdc19
> 100Mbit (>400 Mbit desirable) Ethernet Internet access with
External STATIC IP (no blocked ports in or outbound) - Ideally
this would absorb a /23 (or /24) subnet…
#4 Main & Mini Auditorium setup
- We would like to reposition stage lights
- We will need to set to preset scenes for stage lighting
#5 Main Auditorium
- We do not have exclusive use of the main auditorium during
Debconf!!!!
- Auditorium is being used in the evenings for classical music
concerts
- We will have cable installations that can NOT be moved for the
duration of Debconf / Debcamp
- Between the stage box and the projector (2x Cat5)
- Between the control room dropping down from the balcony and to the
stage camera (1x Co-ax SDI)
- Many cables from the control room on the balcony – including
camera position and cables suspended from the balcony (ambient
mics). Can we ensure that the balcony is NOT accessible during
the concert?
- We will have re-patched the sound desk for our purposes – providing
only channels that we are NOT using are used this would be
acceptable HOWEVER it should be noted that the MASTER fader will not
be connected to the house PA system – it will have been moved to an
Aux or Sub channel!
- We will not be able to reposition lighting / re-patch the projector
once setup until the end of Debconf...
- Be also aware the will place be a lot of additional kit in the
control room (cameras,PCs etc)
It will be a PITA but we can:
- Move the lectern, stage box and associated cabling to the side of
the stage (behind the curtains) providing that we can leave
everything plugged in (power, audio snake, network etc.). We will
need to tape down location markers on the stage so that the kit can
be relocated each morning / evening after the concerts
- Move the stage camera position to the side of the stage (behind the
curtains) providing that we can leave everything plugged in (power,
SDI cable, network etc.) We will need to tape down location markers
on the stage so that the kit can be relocated each morning / evening
after the concerts
Questions arising wrt wider network access for the attendee network
#6 Can all other network sockets in the rooms we will using be
allocated to VLANdc19?
#7 Can we have SSID debconf19 on the WiFi Access points please? Please
can we either leave this totally open or have a simple PSK i.e.
“Polito4DPL”; any device associating with/to this SSID should again
be connected to the VLANdc19.
#8 Can you please lock down the VLANdc19 so that it can not access the
rest of the campus network?
#9 We will segregate provide routing between the VLANdc19 network and
the internet via the Attendee Router described above.
#10 We would like to rent in a wireless radio link to run between the
roof of one of the university buildings and the hotel that we are
using so that we can provide common network in the hotel hack labs.
We would like this to be placed in the VLANdc19.
Thanks Andy for the notes,
SR
Reply to: