Difference between pages "Funtoo Hosting" and "Hostname"

(Difference between pages)
(Container FAQ)
 
(Hosts case)
 
Line 1: Line 1:
== Funtoo Linux Hosting ==
+
w.i.p
__NOTOC__
+
==Introduction==
__NOTITLE__
+
A hostname is a unique name created to identify a machine on a network. In computer networking, a hostname  is a label that is assigned to a device connected to a computer network and that is used to identify the device in various forms of electronic communication such as the World Wide Web, e-mail or Usenet. Hostnames may be simple names consisting of a single word or phrase, or they may be structured.
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:
+
==Configuration==
 
+
In Funtoo Linux <code>/etc/conf.d/hostname</code> is the only configuration file for setting a hostname. In OpenRC framework <code>/etc/conf.d/foo</code> is the configuration file for a corresponding Init script <code>/etc/init.d/foo</code>.  With the case of hostname, default value in <code>/etc/conf.d/hostname</code> is set to ''localhost'', means when system boots and OpenRC's <code>/etc/init.d/hostname</code> script started a hostname getting only ''localhost'' name. How it looks?  In your shell promt this will look in following way, an example for root:
{{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}}
+
 
+
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|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 <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>.
+
 
+
;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.
+
 
+
{{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.}}
+
 
+
;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 [[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:
+
 
+
# 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.
+
 
+
{{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:  
+
 
+
 
<console>
 
<console>
$ ##i##ssh-keygen -t rsa
+
localhost ~ # ##i## Hello :)
 
</console>
 
</console>
 +
Let's play a bit with a configuration. Open <code>/etc/conf.d/hostname</code> with your favorite editor and set a hostname of your choice.  Below, I will use a real examples  from one of my working test boxes.
 +
<console>
 +
localhost ~ # ##i## nano /etc/conf.d/hostname
 +
</console>
 +
Let's set it to hostname="oleg-stable.host.funtoo.org". Save the file and restart  a hostname service:
 +
<console>
 +
localhost ~ # ##i## service hostname restart
 +
</console>
 +
Now, let's examine our changes, after a restarting a hostname
 +
<console>
 +
oleg-stable ~ # ##i## Hello :)
 +
</console>
 +
== Diving deeper==
 +
Notice, that in above output we seeing a shortened hostname and not a FQDN (Fully Qualified Domain Name). Don't be frustrated. This is  how  default bash promt <code>PS1</code> set. To get nice promts, please, consult http://www.ibm.com/developerworks/library/l-tip-prompt/ <-- this one should be on Funtoo wiki :)
 +
Another way to test our settings is using a '''hostname''' command. Here we will show only  some of it's features. Let's try to execute '''hostname''' command:
 +
<console>
 +
oleg-stable ~ # ##i## hostname
 +
oleg-stable.host.funtoo.org
 +
</console>
 +
Now we see our fully qualified domain name hostname just how we configured it in <code>/etc/conf.d/hostname</code> in above paragraph. To get a short hostname we need to set '''-s ''' (short) argument to hostname command.
 +
<console>
 +
oleg-stable ~ # ##i## hostname -s
 +
oleg-stable
 +
</console>
 +
Good! Hostname offers more then just displaying a system host name but can also set one. Let's try:
 +
<console>
 +
oleg-stable ~ # ##i## hostname foo.bar.baz
 +
oleg-stable ~ # ##i## hostname
 +
foo.bar.baz
 +
</console>
 +
As you can see, we changed a hostname on-the-fly. This is not recommended way.
 +
{{fancywarning|Please, notice that using '''hostname''' command to configure will work temporary for a current session and will be reverted back to a value set in <code>/etc/conf.d/hostname</code> file with next system restart.}}
  
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 got a brief description of a hostname and basic configuration steps its time to reflect another important case, which is directly related to a Funtoo Linux hostname generation, a hosts.
 
+
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. :)
+
 
+
== Policies ==
+
 
+
{{Policies}}
+
 
+
=== VPS Usage Rules ===
+
 
+
{{fancyimportant|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.
+
==Hosts case==
 +
As per man page <code>hosts</code> stands for static table lookup for hostnames and it's configuration file is <code>/etc/hosts</code>.

Revision as of 16:38, February 20, 2015

w.i.p

Introduction

A hostname is a unique name created to identify a machine on a network. In computer networking, a hostname is a label that is assigned to a device connected to a computer network and that is used to identify the device in various forms of electronic communication such as the World Wide Web, e-mail or Usenet. Hostnames may be simple names consisting of a single word or phrase, or they may be structured.

Configuration

In Funtoo Linux /etc/conf.d/hostname is the only configuration file for setting a hostname. In OpenRC framework /etc/conf.d/foo is the configuration file for a corresponding Init script /etc/init.d/foo. With the case of hostname, default value in /etc/conf.d/hostname is set to localhost, means when system boots and OpenRC's /etc/init.d/hostname script started a hostname getting only localhost name. How it looks? In your shell promt this will look in following way, an example for root:

localhost ~ #  Hello :)

Let's play a bit with a configuration. Open /etc/conf.d/hostname with your favorite editor and set a hostname of your choice. Below, I will use a real examples from one of my working test boxes.

localhost ~ #  nano /etc/conf.d/hostname

Let's set it to hostname="oleg-stable.host.funtoo.org". Save the file and restart a hostname service:

localhost ~ #  service hostname restart

Now, let's examine our changes, after a restarting a hostname

oleg-stable ~ #  Hello :)

Diving deeper

Notice, that in above output we seeing a shortened hostname and not a FQDN (Fully Qualified Domain Name). Don't be frustrated. This is how default bash promt PS1 set. To get nice promts, please, consult http://www.ibm.com/developerworks/library/l-tip-prompt/ <-- this one should be on Funtoo wiki :) Another way to test our settings is using a hostname command. Here we will show only some of it's features. Let's try to execute hostname command:

oleg-stable ~ #  hostname
oleg-stable.host.funtoo.org

Now we see our fully qualified domain name hostname just how we configured it in /etc/conf.d/hostname in above paragraph. To get a short hostname we need to set -s (short) argument to hostname command.

oleg-stable ~ #  hostname -s
oleg-stable

Good! Hostname offers more then just displaying a system host name but can also set one. Let's try:

oleg-stable ~ #  hostname foo.bar.baz
oleg-stable ~ #  hostname 
foo.bar.baz

As you can see, we changed a hostname on-the-fly. This is not recommended way.

Warning

Please, notice that using hostname command to configure will work temporary for a current session and will be reverted back to a value set in /etc/conf.d/hostname file with next system restart.

Now that we got a brief description of a hostname and basic configuration steps its time to reflect another important case, which is directly related to a Funtoo Linux hostname generation, a hosts.

Hosts case

As per man page hosts stands for static table lookup for hostnames and it's configuration file is /etc/hosts.