1,764
edits
Changes
Jump to navigation
Jump to search
Line 15:
Line 15: − + − + + + + + + − + − + − * Stefano Fedrigo <aleph AT develer.com>, sometimes _aleph on Freenode (local access, office hours CET)+ − * Develer Infrastructure <it AT lists.develer.com> (local access, office hours CET)+ + + + + − Develer has a 10mbit up/downlink and asks to limit bandwidth usage from hosted services.+ − There is a traffic shaper, but it may have trouble shaping 6to4 traffic.+ + + + + + − + − to it: 2002:5395:9edc::/48. − The tun6to4 interface on bender is assigned the globally visible address 2002:5395:9edc::1.+ − The subnet 2002:5395:9edc:1::/64 of our 6to4 net is assigned to the bridge virbr0, which binds together − several virtual interfaces connected to the libvirt guests. With this network setup, IPv6 routing works − naturally, without the need to add any special routing rules on bender. − The virbr0 bridge is created by libvirt on startup with <code>/etc/libvirt/qemu/networks/default.xml</code>.+ − Libvirt does not yet support assigning IPv6 addresses to bridges, therefore we do this in <code>/etc/rc.local</code>:+ − ip addr add 2002:5395:9edc:1::1/64 dev virbr0 + + + − To automatically configure network and on the gursts, Bender also runs radvd, the IPv6 Routing Advertisement+ − daemon. The contents of <code>/etc/radvd.conf</code> are: − interface virbr0+ − {+ − IgnoreIfMissing on;+ − AdvSendAdvert on;+ − MinRtrAdvInterval 30; − MaxRtrAdvInterval 100; − AdvDefaultPreference low; − AdvHomeAgentFlag off; − − #bernie: subnet 1 of our /48 6to4 on Develer Consiagnet − prefix 2002:5395:9edc:1::1/64 − { − AdvOnLink on; − AdvAutonomous on; − }; − }; + + + + + + + + + + + + + + + + + + + + + + + + + + − == Hosted VMs ==+ − All buildslaves currently run off bender as KVM virtual machines managed by libvirtd. − The machines are not globally addressable on IPv4 and are only reachable by IPv6. The+ − IPv6 address is dynamically configured by radvd to a subnet of the public 6to4 net.+ + + + + − All the VMs are in /srv/images. See the README in the same directory.+ − They have been created with+ + + + + + + + + + + − virt-install --name buildslave-name --ram 512 \+ − --disk path=/srv/images/buildslave-name.img,size=10 − --network network:default \ − --location "mirror-http-address" \ − --extra-args="console=tty0 console=ttyS0,115200n8 serial"
no edit summary
* Ubuntu 20.04.2 LTS
* Ubuntu 20.04.2 LTS
== Location ==
[[Image:BenderRacked.jpg|thumb|320px]]
Hosted by [http://www.develer.com/ Develer]
== Info ==
Owned by Sugar Labs, Inc.
Hosted by Sonic in Santa Rosa, CA
Bender and Papert are two twin KVM hosts bought by Sugar Labs in 2021.
== Admins ==
== Admins ==
* [[User:Bernie|Bernie Innocenti]], _bernie on #sugar Freenode
* [[User:MrBIOS|Alex Perez]], MrBIOS on #sugar Libera.chat IRC network
* [[User:dnarvaez|Daniel Narvaez]], dnarvaez on #sugar Freenode
* [[User:Bernie|Bernie Innocenti]], bernie on #sugar Libera.chat IRC network
== Hosting ==
[[Image:SonicColo.jpg|thumb|320px]]
Hosted by Sonic in Santa Rosa CA
== Network configuration ==
== Network configuration ==
Network configuration is managed via [https://netplan.io/ netplan]. To modify, do:
vi /etc/netplan/bender.yaml
netplan generate
netplan apply
=== IPv4 ===
Bender is globally accessible through public, static IPv4 as well as the 6to4 subnet associated
Bender is globally accessible through a public, static IPv4 address.
Sonic assigned a /28 network to Sugar Labs. IP assignments are managed in our DNS configuration. Search for "Sonico IP pool" in <code>masters/sugarlabs.org.zone</code>.
=== IPv6 ===
IPv6 configuration is a bit weird.
* Public block: 2001:5a8:601:f::/64
* Sonic gateway: 2001:5a8:5:3a::15:0/127
* Transport IP: 2001:5a8:5:3a::15:1/127
The gateway is configured to route all traffic for our netblock to the transport IP, which is currently assigned to bender.
=== Bridges ===
The br0 bridge is created at startup and shared with the virtual machines hosted on Bender. It gives the VMs unfiltered access to the external network. There's no DHCP, all machines must define a static IP configuration, taking care not to stomp onto each other.
There is also a virbr0 bridge created by libvirt on startup from <code>/etc/libvirt/qemu/networks/default.xml</code>. This is a NAT interface and is not meant for VMs directly serving on the Internet.
Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.
Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.
== Virtualization ==
Virtual machines are KVM guests managed with libvirt.
=== Storage ===
All virtual disks come from a pool backed by the main LVM VG:
virsh # pool-define-as nvme-pool logical --source-name nvme-pool
Pool nvme-pool defined
virsh # pool-start nvme-pool
Pool nvme-pool started
virsh # pool-autostart nvme-pool
Pool nvme-pool marked as autostarted
virsh # pool-info nvme-pool
Name: nvme-pool
UUID: 5812819f-b8bf-484e-98fb-2e100fe83df2
State: running
Persistent: yes
Autostart: yes
Capacity: 1.64 TiB
Allocation: 250.00 GiB
Available: 1.40 TiB
Disks assigned to VMs will appear here:
virsh # vol-list nvme-pool
Name Path
-----------------------------------------
aslo1-root /dev/nvme-pool/aslo1-root
aslo1-srv /dev/nvme-pool/aslo1-srv
backup /dev/nvme-pool/backup
Disks can be created, listed and deleted using the vol-* commands:
virsh # vol-create-as nvme-pool testvm-root 20G
Vol testvm-root created
virsh # vol-info testvm-root --pool nvme-pool
Name: testvm-root
Type: block
Capacity: 20.00 GiB
Allocation: 20.00 GiB
virsh # vol-delete testvm-root --pool nvme-pool
Vol testvm-root deleted
Please avoid allocating large VM volumes as image file within the host's root filesystem: they're slow and hard to manage. It's ok to use images for test VMs.