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

When to bring your Server

The YoloColo times are

  • day 1: 12:00, 14:00, 16:00, 18:00, 20:00
  • day 2 & 3: 14:00-18:00 on request
  • day 4: 12:00, 14:00, 16:00

Be at the yolocolo door ("Empoore Saal1" on the first floor, marked with a YoloColo sign) at the start of one of these times. For day 2 & 3 please call the NOC helpdesk before as there might be no one at the colo.

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 colocation is located in the empore above Saal3. 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

As the room is open to Saal3, the temperature will most likely be above 20°C.

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!)

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 a 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.

There will be no LACP trunks.

L3

IP addresses will be provided via SLAAC. Be sure to know your modified EUI-64.

Here have a quick calculator:

If your SLAAC implementation disables the static address when privacy extensions are enabled, you MUST disable privacy extensions before bringing your server.

Please test your SLAAC beforehand!
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 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 or use a random address from this prefix and configure it statically (this also applies to the link local address! Make sure that you still get the default route via router advertisements though).

Legacy IPv4 addresses will be provided via RFC2322 on paper. Only one IPv4 address per machine! (give us a really convincing argument and you might get more) If you require IPv4 to access your server you MUST configure it before bringing the server into the colocation.

The legacy address range of the colo is not known yet and will be placed here once available.

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
  • the legacy IP range is not yet known

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 labeld 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.

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.

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).