• Deutsch: Dieses Seite ist noch nicht ins Deutsche übersetzt worden.

YoloColo

The NOC helpdesk team is proud to present to you: The YoloColo! As usual, we provide you with one of the most hacky-looking-while-still-being-better-than-some-actual-DCs housing solutions for your hardware during the event!

Keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHOULD”, “SHOULD NOT” and “MAY” that appear in this document are to be interpreted as described in RFC2119.

Guidelines/FAQ

Will there be a YoloColo?

Probably, but we cannot guarantee it yet. We will update this page once we have confirmation.

When to bring your Server

The YoloColo times are:

  • day 1: 12:00-21:00
  • day 2 & 3: 12:00, 13:00, 18:00, 19:00
  • day 4: 12:00-15:00

The YoloColo closes at 16:00 on day4. Please be in the YoloColo queue before 15:00 so you can get your server in time.

Be at the yolocolo door (Location: To be announced) within the given time ranges for day 1 and 4 or a time point for days 2 and 3. We'll try to service everyone that arrived within the given times on day 1 and 4 - you don't need to be there at the exact moment the range starts. On days 2 and 3 (where a time point is given) we will only work through the queue und then end the shift. If unsure please call the NOC helpdesk before bringing your machine.

If there are no other people waiting outside you might try if the door is open and take a peek inside. You may come in if the helpdesk coordinator is the only person inside. Else make sure they know you are waiting and wait outside until asked to come in.

Location

The location of the colocation is to be announced. Access to the room is only granted

  • in company of a NOC-Helpdesk coordinator
  • one person at a time
  • if all requirements to bring or get your hardware are met (see below).

Please keep build-up times as low as possible and try connecting everything you can ahead of time. We aim for a maximum of around 5 minutes per person. We MAY refuse entry if your equipment looks like it needs a service technician to set it up. We MAY make exceptions for interesting projects. If you believe this applies to your use case you MUST contact us using E-Mail beforehand.

Temperature

TODO

Noise

Please do not bring your wannabe-jet-engine. While it should not be an issue we MAY turn off the most noisy machines if Saal3 gets too loud because of it.

Power

Thanks to team power we can provide you with all the Schuko (CEE 7/3) sockets you could want. Power can fail! Make sure you have backups of important data!

Network

L0/1

Network connectivity will be provided through:

  • 1GBase-T/2.5GBase-T/5GBase-T and maybe 10GBase-T (please use SFP+ instead of 10GBase-T if possible)
  • 1G/10G SFP+, 25G SFP28
  • A handful of 40G QSFP+ and 100G QSFP28 (tell us a good reason why you need it and do not expect to get it! Ideally contact us beforehand via email)

Bring your own DACs/Fiber+Transceivers/cables/... and make sure to bring long ones (ideally in the range of 5m. We can not gurantee a spot right next to a switch!). Every visitor will get an absolute maximum of 5 ports.

L2

You SHOULD configure your server to announce a reasonable hostname as well as contact information via LLDP to facilitate debugging. You SHOULD be able to receive LLDPDUs or know the switchport you are plugged in by other means. You MUST NOT provide the same service on multiple IP addresses.

There will be no LACP trunks.

L3

IP addresses will be provided via SLAAC. Be sure to know your modified EUI-64. There will be a NAT64 gateway. Further information on how to use it will follow.

Here have a quick calculator:

You SHOULD disable Privacy Extensions and Stable Privacy, unless you know how to aquire your address with them enabled. You MUST NOT debug your Server or Network inside of the Colo. If it doesn't work, you MUST retrieve the server, debug it at your table and then bring it back. If you do not want your MAC address to be public information you SHOULD change it to random one with the Locally Administered flag set.

You SHOULD test your SLAAC beforehand! Plug your system into an IPv6-Capable network and check if you get a globally routable ("public") address (one starting with a 2) and that it ends with the last three bytes of your MAC address.
There were many people in the last years that had weird misconfigurations that resulted in "flapping addresses" or just plain non-working IPv6.

The YoloColo prefix is 2001:67c:20a1:1561::/64. There will be no IPv4 this year.

Network Configuration

Generally, expect your system to work out-of-the-box without configuration, if you encounter issues, follow one of the following guides, depending on your network stack. If those don't help or you have a system that is not covered "enable SLAAC on $system" and "disable IPv6 privacy extensions on $system" are search terms that should help you.

sysctl

net.ipv6.conf.all.use_tempaddr = 0
net.ipv6.conf.all.addr_gen_mode = 0
net.ipv6.conf.default.use_tempaddr = 0
net.ipv6.conf.default.addr_gen_mode = 0

systemd-networkd

[Match]
Name=eth0

[Network]
DHCP=no
IPv6AcceptRA=yes
IPv6PrivacyExtensions=no # should be default, but to be safe

ifupdown (/etc/network/interfaces)

allow-hotplug eth0
iface eth0 inet6 auto

Then set the sysctls as shown in section sysctl (if they are not already 0 by default)

NetworkManager

nmcli connection modify "Wired connection 1" ipv6.method auto
nmcli connection modify "Wired connection 1" ipv6.addr-gen-mode 1
nmcli connection modify "Wired connection 1" ipv6.ip6-privacy 0

There might be a public list of all active addresses in this prefix!
If you do not want to "leak" the physical MAC address of your NIC consider changing the MAC to a random one ore use a random address from this prefix and configure it statically (make sure that you still get the default route via router advertisements though).

Traffic from/to WiFi

If your service will cause a metric ton of traffic (looking at you, pixelflut) please consider blocking traffic originating from the WiFi IP ranges.

The WiFi IP ranges are:

  • 2001:67c:20a1:1900::/59
  • 2001:67c:20a1:1964::/64
  • 151.219.192.0/18
  • 151.219.160.0/19
  • 151.219.61.128/25

Physical Integrity

  • Your server MUST NOT be on fire.
  • Your server MUST have a robust chassis. We will stack multiple servers and will not make an exception if your server is housed in a flimsy box.
  • Your server MUST NOT be made from easily flammable material like paper or cardboard.
  • There will be a (possibly conductive) shelf for small devices like NUCs, Raspberry Pis, etc.
  • There might be a rack.

Labeling

Your server MUST be labeled with at least

  • Some way to identify you as the owner (DECT/mail/pubkey/password/dance-pattern/…)
  • Some way of contacting you (Nickname and DECT/mail)

If this information is missing we will hand out the server to the first person that gives us a convincing argument why this is their machine.

Please put this information somewhere where it is easily visible even when multiple machines are stacked on top of each other.

Retrieval

You MUST retrieve your server at the latest on day 4 at 16:00 local time. Any hardware not retrieved in time will be considered a donation. We MAY try to contact you if you did not retrieve your server until then.

Finding other's servers

There will be a page in the public wiki again where you can add your server so others can easily find what you brought. In case you have troubles finding said wiki page it will most likely be linked on the usual "Dating" page.

Contact Us

The NOC Helpdesk is reachable in person or at 1212 via the local telephony network (DECT/GSM/SIP).

Before the event, please contact the NOC/NOCHD via e-mail (this is a ticket system).