Getting started with Docker on Scaleway / Online Labs C1
---
Our cloud is based on dedicated servers without any software virtualization.
Off-the-shelf servers were not suitable for this vision of the cloud.
Hence, we designed our own hardware during 2 years from our headquarters in Paris and built it in our factory in France.
912 physical servers (3648 cores) + 48 switches + 288 HDD/SSD in a single rack !
Online Labs: http://labs.online.net
2. • Dedicated ARM servers
• Run in the Cloud
• Ultra high-density (912 servers per rack)
• Developed / Made / Running in France
What is Online Labs’ C1 ?
3. 4 true cores
ARMv7 CPU
2GB of RAM
1 Gbit/s network link
SSD storage
C1 Server
4. 1 x C1 node
• 4-cores
• 2Gb memory
• 1Gbps Ethernet
• SSD disk over network
5. =19 x C1 nodes
• 18 compute nodes
• 1 SAN node + 6 disks
• 1 managed switch
• 10gbps connectivity
• serial multiplexer
1 x C1 blade 76 cores
38G ram
6. • 16 blades per chassis
• 3 chassis per rack
• “hot-plug”
• > 2000 leds :)
• 33ºC
= 912 x C1 nodes
3.6k cores
1.8T ram
288 disks
= 48 x C1 blades
= 3 x C1 chassis
1 x C1 rack
7. Mainline Linux v3.17 kernel
armel/armhf linux distributions
Ubuntu (from 14.04) - Fedora 20 - Debian 7 - Gentoo
InstantApps: Docker, Wordpress, Pydio, Owncloud, Ghost
What runs on C1
8. • All features supported
• Storage drivers: AUFS, BTRFS, DeviceMapper
• cgroups, volumes, ports, links
• fig, nsenter, gosu and pipework are installed by default
Docker + C1
9. We ported the distrib images to armhf
The registry doesn’t care about the architecture
Prefixing all our images (armbuild/)
Docker image -> single architecture
12. Port more distribution images: centos, archlinux
Work on trusted builds for ARM images (partial support)
Port a Docker-based PAAS (dokku, flynn, mesos, coreos …)
Work on multi-architecture / cross-platform images
What we are working on
registry.hub.docker.com/armbuild - github.com/armbuild