Difference between pages "ZFS Install Guide" and "Funtoo Hosting"

(Difference between pages)
(Genkernel)
 
(Container FAQ)
 
Line 1: Line 1:
== Introduction ==
+
== Funtoo Linux Hosting ==
 +
__NOTOC__
 +
__NOTITLE__
 +
If you support Funtoo Linux, we also want to support ''you'' in your Funtoo Linux adventure. Supporters of Funtoo Linux of at least $15/mo can request a Funtoo Linux virtual container. Here are the configurations currently being offered:
  
This tutorial will show you how to install Funtoo on ZFS (rootfs). This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.
+
{{TableStart}}
 +
<tr class="danger"><th>Price</th><th>RAM</th><th>CPU Threads</th><th>Disk Space</th></tr>
 +
<tr><td>'''$15/mo'''</td><td>4GB</td><td>6 CPU Threads</td><td>50GB</td></tr>
 +
<tr><td>'''$30/mo'''</td><td>12GB</td><td>12 CPU Threads</td><td>100GB</td></tr>
 +
<tr><td>'''$45/mo'''</td><td>48GB</td><td>24 CPU Threads</td><td>200GB</td></tr>
 +
{{TableEnd}}
  
=== Introduction to ZFS ===
+
As you can see, this pricing is well below market rates, and includes fast SSD (solid state disk) storage, one IPv4 address, and lots of bandwidth. We believe that by enabling you to do great things with Funtoo Linux, our community and technology will benefit. So we see this as a win for everyone.
  
Since ZFS is a new technology for Linux, it can be helpful to understand some of its benefits, particularly in comparison to BTRFS, another popular next-generation Linux filesystem:
+
== Container FAQ ==
  
* On Linux, the ZFS code can be updated independently of the kernel to obtain the latest fixes. btrfs is exclusive to Linux and you need to build the latest kernel sources to get the latest fixes.
+
;How do I sign up?: Set up a monthly support subscription via PayPal or credit card on our [[Support Funtoo]] page. Then see the [[#Getting Started|Getting Started]] section below.
  
* ZFS is supported on multiple platforms. The platforms with the best support are Solaris, FreeBSD and Linux. Other platforms with varying degrees of support are NetBSD, Mac OS X and Windows. btrfs is exclusive to Linux.
+
;Do I get root access?: Yes, you get full root access to your container.
  
* ZFS has the Adaptive Replacement Cache replacement algorithm while btrfs uses the Linux kernel's Last Recently Used replacement algorithm. The former often has an overwhelmingly superior hit rate, which means fewer disk accesses.
+
;Can I reboot my container?: Yes, reboot normally and it will come back up.
  
* ZFS has the ZFS Intent Log and SLOG devices, which accelerates small synchronous write performance.
+
;How much bandwidth is ''really'' included?: For most typical uses of your container, this is not something you need to worry about. Our server is on a 100Mbps physical link, which is shared among all containers. Our bandwidth plan is set up so that everyone should have lots of burstable bandwidth, assuming light use at other times. If you have continuous high bandwidth needs, please email me to discuss first.
  
* ZFS handles internal fragmentation gracefully, such that you can fill it until 100%. Internal fragmentation in btrfs can make btrfs think it is full at 10%. Btrfs has no automatic rebalancing code, so it requires a manual rebalance to correct it.
+
;Why is my Portage tree read-only?: A read-only Portage tree is mapped into <code>/var/src/portage</code> and is used by default by all containers. It is automatically updated, so there is no need to run <code>emerge --sync</code>. This saves disk space. There is generally no need to have your own local Portage tree, but if you want to have one, you can remove the <code>PORTDIR</code> setting in <code>/etc/make.conf</code> and run <code>emerge --sync</code>.
  
* ZFS has raidz, which is like RAID 5/6 (or a hypothetical RAID 7 that supports 3 parity disks), except it does not suffer from the RAID write hole issue thanks to its use of CoW and a variable stripe size. btrfs gained integrated RAID 5/6 functionality in Linux 3.9. However, its implementation uses a stripe cache that can only partially mitigate the effect of the RAID write hole.
+
;How do I upgrade the kernel in my VPS?: A virtual container shares a kernel with the host, so you do not have the ability to change the kernel from "inside" the container.
  
* ZFS send/receive implementation supports incremental update when doing backups. btrfs' send/receive implementation requires sending the entire snapshot.
+
;Can I run Docker inside my container?: The OpenVZ development team is the largest code contributor to the Linux Containers kernel code (which is part of Docker,) and we use OpenVZ, but right now it is not possible to run LXC inside an OpenVZ container. This may change with the release of newer OpenVZ kernels based on 3.x.
  
* ZFS supports data deduplication, which is a memory hog and only works well for specialized workloads. btrfs has no equivalent.
+
{{fancyimportant|This next bit of information is important. A number of people have temporarily locked themselves out of their containers by setting up a firewall incorrectly. I plan to develop a firewall management UI that configures a firewall for you to make this step easier. For the time being, please avoid setting up a firewall unless you ''really'' need one.}}
  
* ZFS datasets have a hierarchical namespace while btrfs subvolumes have a flat namespace.
+
;Can I set up my own firewall?: Before you do, please contact me (Daniel) and let me know. I need to flip a few switches in your container to make iptables work properly. Otherwise it will silently fail on stateful firewalls and you may end up locking yourself out of your container.
  
* ZFS has the ability to create virtual block devices called zvols in its namespace. btrfs has no equivalent and must rely on the loop device for this functionality, which is cumbersome.
+
;Can I set up OpenVPN in my container?: Yes, quite a few people do this, but contact me first so I can enable tun/tap devices for you.
  
The only area where btrfs is ahead of ZFS is in the area of small file
+
;Is it okay to host a game server?: Yes, many people do.
efficiency. btrfs supports a feature called block suballocation, which
+
enables it to store small files far more efficiently than ZFS. It is
+
possible to use another filesystem (e.g. reiserfs) on top of a ZFS zvol
+
to obtain similar benefits (with arguably better data integrity) when
+
dealing with many small files (e.g. the portage tree).
+
  
For a quick tour of ZFS and have a big picture of its common operations you can consult the page [[ZFS Fun]].
+
;Is it okay to run Folding@Home, Hentai@Home, or other services that donate CPU power or bandwidth to other services?: No, this is not okay. The CPU and network resources provided to you are for your own use only and are not to be donated to other projects.
  
=== Disclaimers ===
+
;Is it okay to use my container to be a compute-focused server for another Open Source project?: Check with me first. Most of the time, this will be okay, unless CPU and/or IO utilization will be very high and continuous, and thus unsuitable for shared computing resources.
  
{{fancywarning|This guide is a work in progress. Expect some quirks.}}
+
;Is it okay to host commercial efforts on my container?: Yes, this is fine, as long as you assume full responsibility for the quality of service. Funtoo containers are provided with no service level agreements or warranty.
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}
+
== Downloading the ISO (With ZFS) ==
+
In order for us to install Funtoo on ZFS, you will need an environment that already provides the ZFS tools. Therefore we will download a customized version of System Rescue CD with ZFS included.  
+
  
<pre>
+
== Getting Started ==
Name: sysresccd-4.2.0_zfs_0.6.2.iso  (545 MB)
+
Release Date: 2014-02-25
+
md5sum 01f4e6929247d54db77ab7be4d156d85
+
</pre>
+
  
 +
Once you have [[Support Funtoo|signed up for Funtoo Monthly support]], contact me (drobbins@funtoo.org) via email and request a virtual container. You'll need to send me two things:
  
'''[http://ftp.osuosl.org/pub/funtoo/distfiles/sysresccd/ Download System Rescue CD with ZFS]'''<br />
+
# The hostname you'd like for your container. It will be ''something''.host.funtoo.org.
 +
# Attach your SSH public key. I will use this to grant you root access to your container.
  
== Creating a bootable USB from ISO (From a Linux Environment) ==
+
{{Note|I will generally have the container set up within 24 hours of sending email, often much sooner. If you do not hear from me after a day, please re-send email as it may have not made it, or been accidentally marked as spam by Gmail.}}
After you download the iso, you can do the following steps to create a bootable USB:
+
  
<console>
+
== Generating SSH Keys ==
Make a temporary directory
+
To generate an SSH key pair, do this as the user that you'll be using to log in to your container:  
# ##i##mkdir /tmp/loop
+
 
+
Mount the iso
+
# ##i##mount -o ro,loop /root/sysresccd-4.2.0_zfs_0.6.2.iso /tmp/loop
+
 
+
Run the usb installer
+
# ##i##/tmp/loop/usb_inst.sh
+
</console>
+
 
+
That should be all you need to do to get your flash drive working.
+
 
+
== Booting the ISO ==
+
 
+
{{fancywarning|'''When booting into the ISO, Make sure that you select the "Alternate 64 bit kernel (altker64)". The ZFS modules have been built specifically for this kernel rather than the standard kernel. If you select a different kernel, you will get a fail to load module stack error message.'''}}
+
 
+
== Creating partitions ==
+
There are two ways to partition your disk: You can use your entire drive and let ZFS automatically partition it for you, or you can do it manually.
+
 
+
We will be showing you how to partition it '''manually''' because if you partition it manually you get to create your own layout, you get to have your own separate /boot partition (Which is nice since not every bootloader supports booting from ZFS pools), and you get to boot into RAID10, RAID5 (RAIDZ) pools and any other layouts due to you having a separate /boot partition.
+
 
+
==== gdisk (GPT Style) ====
+
 
+
'''A Fresh Start''':
+
 
+
First lets make sure that the disk is completely wiped from any previous disk labels and partitions.
+
We will also assume that <tt>/dev/sda</tt> is the target drive.<br />
+
  
 
<console>
 
<console>
# ##i##sgdisk -Z /dev/sda
+
$ ##i##ssh-keygen -t rsa
 
</console>
 
</console>
  
{{fancywarning|This is a destructive operation and the program will not ask you for confirmation! Make sure you really don't want anything on this disk.}}
+
If you specify a passphrase when prompted, your local private key (<code>~/.ssh/id_rsa</code>) will be encrypted, and ssh will prompt you for this passphrase prior to connecting. If you don't specify a passphrase, then you won't need to enter anything to connect but it you need to be extra careful that you don't allow others to access your private key as it will be immediately useable by them to access any of your accounts.  
  
Now that we have a clean drive, we will create the new layout.
+
The file you will need to send me is <code>~/.ssh/id_rsa.pub</code> or <code>~/.ssh/id_dsa.pub</code> (if you used the <code>-t dsa</code> option with <code>ssh-keygen</code>. This is the ''public'' key... it's safe to send over email since all I or anyone else can use it for is to grant you access to a system via your private key. Just don't send your private key to me. :)
  
First open up the application:
+
== Policies ==
  
<console>
+
{{Policies}}
# ##i##gdisk /dev/sda
+
</console>
+
  
'''Create Partition 1''' (boot):
+
=== VPS Usage Rules ===
<console>
+
Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##+250M ↵
+
Hex Code: ##i##↵
+
</console>
+
  
'''Create Partition 2''' (BIOS Boot Partition):
+
{{fancyimportant|Please read these policies and make sure you understand them. This is not an exhaustive list.}}
<console>Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##+32M ↵
+
Hex Code: ##i##EF02 ↵
+
</console>
+
  
'''Create Partition 3''' (ZFS):
+
The VPS is for '''your personal use'''. No reselling.
<console>Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##↵
+
Hex Code: ##i##bf00 ↵
+
  
Command: ##i##p ↵
+
There is currently no Web panel - these servers will be set up using my own automated tool and you will be provided with ssh access. I can periodically reload VPS images as needed.
  
Number  Start (sector)    End (sector)  Size      Code  Name
+
This service is offered as a thank-you gift to Funtoo Linux supporters as long as sufficient capacity is available, with no warranty for uptime or anything else.
  1            2048          514047  250.0 MiB  8300  Linux filesystem
+
  2          514048          579583  32.0 MiB    EF02  BIOS boot partition
+
  3          579584      1953525134  931.2 GiB  BF00  Solaris root
+
  
Command: ##i##w ↵
+
There are no refunds.
</console>
+
  
 +
While I host several production sites on this infrastructure, you assume all risk for hosting your production services on your VPS.
  
=== Format your /boot partition ===
+
I will make a best-effort-only attempt to provide support via IRC and email, and do not offer 24/7 support for your VPS.
  
<console>
+
'''US-Legal activities only. No spam will be tolerated.'''
# ##i##mkfs.ext2 -m 1 /dev/sda1
+
</console>
+
  
=== Create the zpool ===
+
These VPS systems are intended for funtoo enthusiasts only. I am providing (particularly in the higher-level plans) generous default resource limits with the understanding that the VPS will be used for general Funtoo use and server stuff.
We will first create the pool. The pool will be named `tank` and the disk will be aligned to 4096 (using ashift=12)
+
<console># ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo tank /dev/sda3</console>
+
  
=== Create the zfs datasets ===
+
Compiling with -j(NUM-CPUS+1) is encouraged (this is Funtoo, after all -- I want you to enjoy fast compiles :), but it's not okay to continually max CPU, IO, or network utilization. '''So, no folding@home, massive file sharing, etc. '''
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: <tt>/home</tt>, <tt>/var</tt>, <tt>/usr/src</tt>, and <tt>/usr/portage</tt>.
+
  
<console>
+
I am currently not supporting IPv6 but will look into adding such support if there is enough interest.
Create some empty containers for organization purposes, and make the dataset that will hold /
+
# ##i##zfs create -p tank/funtoo
+
# ##i##zfs create -o mountpoint=/ tank/funtoo/root
+
  
Optional, but recommended datasets: /home
+
'''You are responsible for backups. '''
# ##i##zfs create -o mountpoint=/home tank/funtoo/home
+
  
Optional datasets: /usr/src, /usr/portage/{distfiles,packages}
+
I reserve the right to change plans and pricing in the future.
# ##i##zfs create -o mountpoint=/usr/src tank/funtoo/src
+
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off tank/funtoo/portage
+
# ##i##zfs create -o mountpoint=/usr/portage/distfiles tank/funtoo/portage/distfiles
+
# ##i##zfs create -o mountpoint=/usr/portage/packages tank/funtoo/portage/packages
+
</console>
+
 
+
=== Create your swap zvol ===
+
For modern machines that have greater than 4 GB of RAM, A swap size of 2G should be enough. However if your machine doesn't have a lot of RAM, the rule of thumb is either 2x the RAM or RAM + 1 GB.
+
 
+
For this tutorial we will assume that it is a newer machine and make a 2 GB swap.
+
 
+
<console>
+
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -o volblocksize=4K -V 2G tank/swap
+
</console>
+
{{fancywarning|ZFS swap is not stable and should be used with precautions.}}
+
 
+
=== Format your swap zvol ===
+
<console>
+
# ##i##mkswap -f /dev/zvol/tank/swap
+
# ##i##swapon /dev/zvol/tank/swap
+
</console>
+
 
+
Now we will continue to install funtoo.
+
 
+
== Installing Funtoo ==
+
 
+
=== Pre-Chroot ===
+
 
+
<console>
+
Go into the directory that you will chroot into
+
# ##i##cd /mnt/funtoo
+
 
+
Make a boot folder and mount your boot drive
+
# ##i##mkdir boot
+
# ##i##mount /dev/sda1 boot
+
</console>
+
 
+
[[Funtoo_Linux_Installation|Now download and extract the Funtoo stage3 ...]]
+
 
+
Once you've extracted the stage3, do a few more preparations and chroot into your new funtoo environment:
+
 
+
<console>
+
Bind the kernel related directories
+
# ##i##mount -t proc none proc
+
# ##i##mount --rbind /dev dev
+
# ##i##mount --rbind /sys sys
+
 
+
Copy network settings
+
# ##i##cp -f /etc/resolv.conf etc
+
 
+
Make the zfs folder in 'etc' and copy your zpool.cache
+
# ##i##mkdir etc/zfs
+
# ##i##cp /etc/zfs/zpool.cache etc/zfs
+
 
+
Chroot into Funtoo
+
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l
+
</console>
+
 
+
=== In Chroot ===
+
 
+
<console>
+
Create a symbolic link to your mountpoints
+
# ##i##ln -sf /proc/mounts /etc/mtab
+
 
+
Sync your tree
+
# ##i##emerge --sync
+
</console>
+
 
+
=== Add filesystems to /etc/fstab ===
+
 
+
Before we continue to compile and or install our kernel in the next step, we will edit the <tt>/etc/fstab</tt> file because if we decide to install our kernel through portage, portage will need to know where our <tt>/boot</tt> is, so that it can place the files in there.
+
 
+
Edit <tt>/etc/fstab</tt>:
+
 
+
<pre>
+
# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>
+
 
+
/dev/sda1              /boot          ext2            defaults        0 2
+
/dev/zvol/tank/swap    none            swap            sw              0 0
+
</pre>
+
 
+
== Kernel Configuration ==
+
...wip
+
 
+
== Installing the ZFS userspace tools and kernel modules ==
+
Emerge {{Package|sys-fs/zfs}}. This package will bring in {{Package|sys-kernel/spl}}, and {{Package|sys-fs/zfs-kmod}} as its dependencies:
+
 
+
<console>
+
# ##i##emerge zfs
+
</console>
+
 
+
Check to make sure that the zfs tools are working. The <code>zpool.cache</code> file that you copied before should be displayed.
+
 
+
<console>
+
# ##i##zpool status
+
# ##i##zfs list
+
</console>
+
 
+
If everything worked, continue.
+
 
+
== Create the initramfs ==
+
There are two ways to do this, you can use "genkernel" or "bliss-initramfs". Both will be shown.
+
 
+
=== genkernel ===
+
Install genkernel and run it:
+
<console>
+
# ##i##emerge genkernel
+
 
+
You only need to add --luks if you used encryption
+
# ##i##genkernel --zfs --luks initramfs
+
</console>
+
 
+
== Installing & Configuring the Bootloader ==
+
 
+
=== GRUB 2  ===
+
<console>
+
# ##i##emerge grub
+
</console>
+
 
+
You can check that grub is version 2.00 by typing the following command:
+
 
+
<console>
+
# ##i##grub-install --version
+
grub-install (GRUB) 2.00
+
</console>
+
 
+
Now install grub to the drive itself (not a partition):
+
<console>
+
# ##i##grub-install /dev/sda
+
</console>
+
 
+
You should receive the following message:
+
 
+
<console>
+
Installation finished. No error reported.
+
</console>
+
 
+
You should now see some a grub directory with some files inside your /boot folder:
+
 
+
<console>
+
# ##i##ls -l /boot/grub
+
total 2520
+
-rw-r--r-- 1 root root    1024 Jan  4 16:09 grubenv
+
drwxr-xr-x 2 root root    8192 Jan 12 14:29 i386-pc
+
drwxr-xr-x 2 root root    4096 Jan 12 14:28 locale
+
-rw-r--r-- 1 root root 2555597 Feb  4 11:50 unifont.pf2
+
</console>
+
 
+
=== boot-update ===
+
boot-update comes as a dependency of grub2, so if you already installed grub, it's already on your system!
+
 
+
==== Genkernel ====
+
If your using genkernel you must add 'real_root=ZFS=<root>' and 'dozfs' to your params.
+
Example entry for <tt>/etc/boot.conf</tt>:
+
 
+
<pre>
+
"Funtoo ZFS" {
+
        kernel vmlinuz[-v]
+
        initrd initramfs-genkernel-x86_64[-v]
+
        params real_root=ZFS=tank/funtoo/root
+
        params += dozfs=force
+
}
+
</pre>
+
 
+
After editing /etc/boot.conf, you just need to run boot-update to update grub.cfg
+
 
+
<console>
+
###i## boot-update
+
</console>
+
 
+
=== LILO (Optional if you are using another bootloader) ===
+
Now that bliss-boot generated the lilo.conf file, move that config file to its appropriate location
+
and install lilo to the MBR:
+
 
+
<console>
+
# ##i##mv lilo.conf /etc
+
# ##i##lilo
+
 
+
You should see the following:
+
 
+
Warning: LBA32 addressing assumed
+
Added Funtoo + *
+
One warning was issued
+
</console>
+
 
+
== Final configuration ==
+
=== Add the zfs tools to openrc ===
+
<console># ##i##rc-update add zfs boot</console>
+
 
+
=== Clean up and reboot ===
+
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.
+
 
+
<console>
+
Delete the stage3 tarball that you downloaded earlier so it doesn't take up space.
+
# ##i##cd /
+
# ##i##rm stage3-latest.tar.xz
+
 
+
Set your root password
+
# ##i##passwd
+
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!
+
 
+
Get out of the chroot environment
+
# ##i##exit
+
 
+
Unmount all the kernel filesystem stuff and boot (if you have a separate /boot)
+
# ##i##umount -l proc dev sys boot
+
 
+
Turn off the swap
+
# ##i##swapoff /dev/zvol/tank/swap
+
 
+
Export the zpool
+
# ##i##cd /
+
# ##i##zpool export tank
+
 
+
Reboot
+
# ##i##reboot
+
</console>
+
 
+
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}
+
 
+
and that should be enough to get your system to boot on ZFS.
+
 
+
== After reboot ==
+
 
+
=== Forgot to reset password? ===
+
==== System Rescue CD ====
+
If you aren't using bliss-initramfs, then you can reboot back into your sysresccd and reset through there by mounting your drive, chrooting, and then typing passwd.
+
 
+
Example:
+
<console>
+
# ##i##zpool import -f -R /mnt/funtoo tank
+
# ##i##chroot /mnt/funtoo bash -l
+
# ##i##passwd
+
# ##i##exit
+
# ##i##zpool export -f tank
+
# ##i##reboot
+
</console>
+
 
+
==== Using bliss-initramfs ====
+
If you forgot to reset your password and are using '''bliss-initramfs''', you can add the '''su''' option to your bootloader parameters and the initramfs will throw you into the rootfs of your drive. In there you can run 'passwd' and then type 'exit'. Once you type 'exit', the initramfs will continue to boot your system as normal.
+
 
+
=== Create initial ZFS Snapshot ===
+
Continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant.
+
 
+
To take the snapshot of your system, type the following:
+
<console># ##i##zfs snapshot -r tank@install</console>
+
 
+
To see if your snapshot was taken, type:
+
<console># ##i##zfs list -t snapshot</console>
+
 
+
If your machine ever fails and you need to get back to this state, just type (This will only revert your / dataset while keeping the rest of your data intact):
+
<console># ##i##zfs rollback tank/funtoo/root@install</console>
+
 
+
{{fancyimportant|'''For a detailed overview, presentation of ZFS' capabilities, as well as usage examples, please refer to the [[ZFS_Fun|ZFS Fun]] page.'''}}
+
 
+
== Troubleshooting ==
+
 
+
=== Starting from scratch ===
+
If your installation has gotten screwed up for whatever reason and you need a fresh restart, you can do the following from sysresccd to start fresh:
+
 
+
<console>
+
Destroy the pool and any snapshots and datasets it has
+
# ##i##zpool destroy -R -f tank
+
 
+
This deletes the files from /dev/sda1 so that even after we zap, recreating the drive in the exact sector
+
position and size will not give us access to the old files in this partition.
+
# ##i##mkfs.ext2 /dev/sda1
+
# ##i##sgdisk -Z /dev/sda
+
</console>
+
 
+
Now start the guide again :).
+
 
+
[[Category:HOWTO]]
+
[[Category:Filesystems]]
+
[[Category:Featured]]
+
[[Category:Install]]
+
 
+
__NOTITLE__
+

Revision as of 21:07, January 15, 2015

Funtoo Linux Hosting

If you support Funtoo Linux, we also want to support you in your Funtoo Linux adventure. Supporters of Funtoo Linux of at least $15/mo can request a Funtoo Linux virtual container. Here are the configurations currently being offered:

PriceRAMCPU ThreadsDisk Space
$15/mo4GB6 CPU Threads50GB
$30/mo12GB12 CPU Threads100GB
$45/mo48GB24 CPU Threads200GB

As you can see, this pricing is well below market rates, and includes fast SSD (solid state disk) storage, one IPv4 address, and lots of bandwidth. We believe that by enabling you to do great things with Funtoo Linux, our community and technology will benefit. So we see this as a win for everyone.

Container FAQ

How do I sign up?
Set up a monthly support subscription via PayPal or credit card on our Support Funtoo page. Then see the Getting Started section below.
Do I get root access?
Yes, you get full root access to your container.
Can I reboot my container?
Yes, reboot normally and it will come back up.
How much bandwidth is really included?
For most typical uses of your container, this is not something you need to worry about. Our server is on a 100Mbps physical link, which is shared among all containers. Our bandwidth plan is set up so that everyone should have lots of burstable bandwidth, assuming light use at other times. If you have continuous high bandwidth needs, please email me to discuss first.
Why is my Portage tree read-only?
A read-only Portage tree is mapped into /var/src/portage and is used by default by all containers. It is automatically updated, so there is no need to run emerge --sync. This saves disk space. There is generally no need to have your own local Portage tree, but if you want to have one, you can remove the PORTDIR setting in /etc/make.conf and run emerge --sync.
How do I upgrade the kernel in my VPS?
A virtual container shares a kernel with the host, so you do not have the ability to change the kernel from "inside" the container.
Can I run Docker inside my container?
The OpenVZ development team is the largest code contributor to the Linux Containers kernel code (which is part of Docker,) and we use OpenVZ, but right now it is not possible to run LXC inside an OpenVZ container. This may change with the release of newer OpenVZ kernels based on 3.x.
Important

This next bit of information is important. A number of people have temporarily locked themselves out of their containers by setting up a firewall incorrectly. I plan to develop a firewall management UI that configures a firewall for you to make this step easier. For the time being, please avoid setting up a firewall unless you really need one.

Can I set up my own firewall?
Before you do, please contact me (Daniel) and let me know. I need to flip a few switches in your container to make iptables work properly. Otherwise it will silently fail on stateful firewalls and you may end up locking yourself out of your container.
Can I set up OpenVPN in my container?
Yes, quite a few people do this, but contact me first so I can enable tun/tap devices for you.
Is it okay to host a game server?
Yes, many people do.
Is it okay to run Folding@Home, Hentai@Home, or other services that donate CPU power or bandwidth to other services?
No, this is not okay. The CPU and network resources provided to you are for your own use only and are not to be donated to other projects.
Is it okay to use my container to be a compute-focused server for another Open Source project?
Check with me first. Most of the time, this will be okay, unless CPU and/or IO utilization will be very high and continuous, and thus unsuitable for shared computing resources.
Is it okay to host commercial efforts on my container?
Yes, this is fine, as long as you assume full responsibility for the quality of service. Funtoo containers are provided with no service level agreements or warranty.

Getting Started

Once you have signed up for Funtoo Monthly support, contact me (drobbins@funtoo.org) via email and request a virtual container. You'll need to send me two things:

  1. The hostname you'd like for your container. It will be something.host.funtoo.org.
  2. Attach your SSH public key. I will use this to grant you root access to your container.
Note

I will generally have the container set up within 24 hours of sending email, often much sooner. If you do not hear from me after a day, please re-send email as it may have not made it, or been accidentally marked as spam by Gmail.

Generating SSH Keys

To generate an SSH key pair, do this as the user that you'll be using to log in to your container:

$ ssh-keygen -t rsa 

If you specify a passphrase when prompted, your local private key (~/.ssh/id_rsa) will be encrypted, and ssh will prompt you for this passphrase prior to connecting. If you don't specify a passphrase, then you won't need to enter anything to connect but it you need to be extra careful that you don't allow others to access your private key as it will be immediately useable by them to access any of your accounts.

The file you will need to send me is ~/.ssh/id_rsa.pub or ~/.ssh/id_dsa.pub (if you used the -t dsa option with ssh-keygen. This is the public key... it's safe to send over email since all I or anyone else can use it for is to grant you access to a system via your private key. Just don't send your private key to me. :)

Policies

Privacy

We will not, under any circumstances whatsoever, give out or sell your information to anyone.

We use only companies which practice secure processing of online funds so that you, as a client or supporter, can be assured that your private information will be safe and secure.

Refunds

For Funtoo Monthly Support, if you wish to change your support level or cancel your support, simply contact us and we will apply the changes to take effect before the next billing cycle. Monthly Support is non-refundable.

Contact

To change your subscription, or if you have any questions regarding your subscription, please contact Daniel Robbins at drobbins@funtoo.org.

VPS Usage Rules

Important

Please read these policies and make sure you understand them. This is not an exhaustive list.

The VPS is for your personal use. No reselling.

There is currently no Web panel - these servers will be set up using my own automated tool and you will be provided with ssh access. I can periodically reload VPS images as needed.

This service is offered as a thank-you gift to Funtoo Linux supporters as long as sufficient capacity is available, with no warranty for uptime or anything else.

There are no refunds.

While I host several production sites on this infrastructure, you assume all risk for hosting your production services on your VPS.

I will make a best-effort-only attempt to provide support via IRC and email, and do not offer 24/7 support for your VPS.

US-Legal activities only. No spam will be tolerated.

These VPS systems are intended for funtoo enthusiasts only. I am providing (particularly in the higher-level plans) generous default resource limits with the understanding that the VPS will be used for general Funtoo use and server stuff.

Compiling with -j(NUM-CPUS+1) is encouraged (this is Funtoo, after all -- I want you to enjoy fast compiles :), but it's not okay to continually max CPU, IO, or network utilization. So, no folding@home, massive file sharing, etc.

I am currently not supporting IPv6 but will look into adding such support if there is enough interest.

You are responsible for backups.

I reserve the right to change plans and pricing in the future.