<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="https://wiki.lunanode.com/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.lunanode.com/index.php?feed=atom&amp;namespace=0&amp;title=Special%3ANewPages</id>
		<title>Luna Node - New pages [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.lunanode.com/index.php?feed=atom&amp;namespace=0&amp;title=Special%3ANewPages"/>
		<link rel="alternate" type="text/html" href="https://wiki.lunanode.com/index.php/Special:NewPages"/>
		<updated>2026-04-19T05:19:28Z</updated>
		<subtitle>From Luna Node</subtitle>
		<generator>MediaWiki 1.22.5</generator>

	<entry>
		<id>https://wiki.lunanode.com/index.php/Hosted_E-mail</id>
		<title>Hosted E-mail</title>
		<link rel="alternate" type="text/html" href="https://wiki.lunanode.com/index.php/Hosted_E-mail"/>
				<updated>2018-08-10T19:57:57Z</updated>
		
		<summary type="html">&lt;p&gt;Favyen Bastani: Created page with &amp;quot;Our hosted e-mail services allow you to easily set up e-mail on your domains; you can send and receive e-mail either via webmail or IMAPS/SMTPS.  We support multiple user acco...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Our hosted e-mail services allow you to easily set up e-mail on your domains; you can send and receive e-mail either via webmail or IMAPS/SMTPS.&lt;br /&gt;
&lt;br /&gt;
We support multiple user accounts, e-mail aliases, DKIM, and more.&lt;br /&gt;
&lt;br /&gt;
We charge $0.2/mo per GB of storage used (rounded up to the nearest GB and billed hourly) and $0.1 per 1,000 e-mails sent. The first 5,000 e-mails each month and the first 1 GB of storage are free, assuming you use at least $3 credit on other services in the current calendar month. Note that e-mails forwarded to external accounts via aliases are counted as e-mails sent.&lt;/div&gt;</summary>
		<author><name>Favyen Bastani</name></author>	</entry>

	<entry>
		<id>https://wiki.lunanode.com/index.php/Burstable_Resources</id>
		<title>Burstable Resources</title>
		<link rel="alternate" type="text/html" href="https://wiki.lunanode.com/index.php/Burstable_Resources"/>
				<updated>2018-01-04T15:45:30Z</updated>
		
		<summary type="html">&lt;p&gt;Favyen Bastani: /* Burst Points System */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In order to maximize affordability and flexibility, Luna Node General-Purpose and Memory-Optimized virtual machines are assigned a portion of available CPU resources and disk I/O rather than specific dedicated CPU cores or physical disks. Because most application workloads have both periods of high CPU and I/O utilization and periods of low utilization, this maximizes cost savings -- essentially, '''instead of needing to continuously pay for a particular VM's peak utilization, you need only pay for its average utilization'''.&lt;br /&gt;
&lt;br /&gt;
Compute-Optimized virtual machines are assigned dedicated CPU cores.&lt;br /&gt;
&lt;br /&gt;
At a high-level, we assign each VM a baseline CPU and I/O performance. If your VM has periods where its resource utilization is below this baseline, then it collects &amp;quot;points&amp;quot; that it can later use to obtain resource utilization above the baseline.&lt;br /&gt;
&lt;br /&gt;
== Burst Points System ==&lt;br /&gt;
&lt;br /&gt;
'''Baseline performance.''' Each virtual machine has a baseline performance:&lt;br /&gt;
&lt;br /&gt;
* CPU: 100% CPU utilization for every 1.0 CPU-Points specified in the plan (for example, s.half includes 0.2 CPU-Points, and a baseline performance of 20% CPU utilization)&lt;br /&gt;
* Disk I/O: 100 IOPS&lt;br /&gt;
&lt;br /&gt;
'''Burst points.''' The platform keeps track of CPU and disk burst points that each VM has. VMs constantly receive additional burst points corresponding to their baseline performance. They also constantly lose burst points based on actual resource utilization.&lt;br /&gt;
&lt;br /&gt;
* CPU: 1 CPU burst point corresponds to 100% utilization of a core for five minutes. A VM receives the plan CPU-Points every five minutes.&lt;br /&gt;
* Disk I/O: 1 I/O burst point corresponds to 100 IOPS sustained over five minutes. A VM receives 1 burst point every five minutes.&lt;br /&gt;
&lt;br /&gt;
For example, if an s.half VM (which has 0.2 plan CPU-Points) starts with 10 burst points, and then uses 20% of the CPU core for one hour, it will end with 10 burst points. On the other hand, if the VM uses 10% of a core for one hour, it ends with 11.2 burst points (an additional 0.1 points for each five-minute interval), and if it uses 30% of a core for one hour, it ends with 8.8 burst points.&lt;br /&gt;
&lt;br /&gt;
'''Throttling.''' VM resource utilization may be throttled to the baseline performance if it has zero burst points. In some cases, the platform will not throttle the VM, or will throttle it to a level above the baseline performance, if it determines that the system can handle the additional load from the VM.&lt;br /&gt;
&lt;br /&gt;
'''Maximum points.''' There are upper limits on the number of burst points that a VM can accumulate. Once it reaches the limit, the VM burst points will stop increasing:&lt;br /&gt;
&lt;br /&gt;
* CPU: 24 CPU burst points * number of cores (e.g. max of 48 points for a VM with two cores)&lt;br /&gt;
* I/O: 60 I/O burst points&lt;br /&gt;
&lt;br /&gt;
'''Borrowing.''' If a VM runs out of CPU points, and there is another VM on your account in the same region with close to the maximum CPU points, then the system will re-allocate points from the second VM to the first. Thus, the first VM will not be throttled until you no longer have any VMs in the same region with close to the maximum CPU points. I/O points cannot be &amp;quot;borrowed&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
In some cases, you may want to prevent a VM's CPU points from being re-allocated to other VMs even if its points are close to the maximum. To do so, disable CPU utilization lending from the CPU tab.&lt;br /&gt;
&lt;br /&gt;
'''Monitoring points.''' Charts showing CPU points and I/O points over time can be retrieved from the Graphs tab.&lt;br /&gt;
&lt;br /&gt;
== Paying for CPU Performance above the Baseline ==&lt;br /&gt;
&lt;br /&gt;
By default, VMs may be throttled once they run out of CPU or I/O burst points.&lt;br /&gt;
&lt;br /&gt;
To avoid CPU throttling, you can opt to pay for CPU performance above the baseline performance from the CPU tab.&lt;br /&gt;
&lt;br /&gt;
Pricing is $0.0037 per CPU burst point. If your VM runs out of burst points, instead of throttling the VM, the platform will grant the VM one burst point while assessing the charge to your account. If the VM's CPU burst point count never reaches zero, then you will not be charged.&lt;br /&gt;
&lt;br /&gt;
For example, suppose that you use 50% of the two available cores over 30 days on a s.1 VM, which has 0.4 plan cpu-points. Your VM will need an additional 0.6 burst points for every five-minute interval in the month, on top of the 0.4 baseline performance included in the plan. Thus, the VM will use a total of 5184 additional CPU burst points over the 30-day interval, which is equivalent to a $19.18 charge.&lt;br /&gt;
&lt;br /&gt;
== History ==&lt;br /&gt;
&lt;br /&gt;
Before 3 January 2018, we simply had a &amp;quot;fair share usage policy&amp;quot; that stated that CPU and disk I/O are shared, and excessive utilization may result in service suspension. In practice, we would send an e-mail when excessive utilization was detected, and coordinate with the user to either reduce the usage to an acceptable level or upgrade to a larger instance.&lt;br /&gt;
&lt;br /&gt;
We have since deployed an automatic management system that makes this policy much more concrete.&lt;/div&gt;</summary>
		<author><name>Favyen Bastani</name></author>	</entry>

	<entry>
		<id>https://wiki.lunanode.com/index.php/Rescue_Mode</id>
		<title>Rescue Mode</title>
		<link rel="alternate" type="text/html" href="https://wiki.lunanode.com/index.php/Rescue_Mode"/>
				<updated>2017-01-23T17:10:11Z</updated>
		
		<summary type="html">&lt;p&gt;Jason Lee: Created page with &amp;quot;Rescue mode boots your virtual machine with our ubuntu rescue image.  The login for the virtual machine in rescue mode is &amp;quot;rescue/rescue&amp;quot; Once logged in you will be able to mo...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Rescue mode boots your virtual machine with our ubuntu rescue image. &lt;br /&gt;
The login for the virtual machine in rescue mode is &amp;quot;rescue/rescue&amp;quot;&lt;br /&gt;
Once logged in you will be able to mount your virtual machine's disk and perform any operations you may need.&lt;br /&gt;
Once done, click &amp;quot;Unrescue&amp;quot; button to bring the virtual machine out of rescue mode.&lt;/div&gt;</summary>
		<author><name>Jason Lee</name></author>	</entry>

	<entry>
		<id>https://wiki.lunanode.com/index.php/Shelving</id>
		<title>Shelving</title>
		<link rel="alternate" type="text/html" href="https://wiki.lunanode.com/index.php/Shelving"/>
				<updated>2016-09-11T22:57:06Z</updated>
		
		<summary type="html">&lt;p&gt;Favyen Bastani: Created page with &amp;quot;Shelving allows you to deactivate a temporarily unneeded virtual machine so that you only pay for the storage space and assigned IP addresses.  To shelve a virtual machine, si...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Shelving allows you to deactivate a temporarily unneeded virtual machine so that you only pay for the storage space and assigned IP addresses.&lt;br /&gt;
&lt;br /&gt;
To shelve a virtual machine, simply press the Shelve button on the virtual machine details page (you can also use the vm.shelve action from the API). If the instance is not volume-backed, then the shelving process will take some time to complete, as your VM's disk needs to be snapshotted; the time varies for different VM plans, and also depends on how much data you have on the VM.&lt;br /&gt;
&lt;br /&gt;
When you need to reactivate the VM, press Unshelve.&lt;br /&gt;
&lt;br /&gt;
The plan price will not be charged for shelved VMs. Instead, you will be billed for:&lt;br /&gt;
&lt;br /&gt;
* Storage: $0.03/GB/mo (accounted hourly at $0.00004167/GB/hr)&lt;br /&gt;
* IP addresses: $1/IP/mo (accounted hourly at $0.001389/IP/hr)&lt;/div&gt;</summary>
		<author><name>Favyen Bastani</name></author>	</entry>

	<entry>
		<id>https://wiki.lunanode.com/index.php/Application_Templates</id>
		<title>Application Templates</title>
		<link rel="alternate" type="text/html" href="https://wiki.lunanode.com/index.php/Application_Templates"/>
				<updated>2016-07-05T20:08:57Z</updated>
		
		<summary type="html">&lt;p&gt;Favyen Bastani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Application templates allow you to quickly spin up a ubuntu virtual machine with preinstalled software.&lt;br /&gt;
&lt;br /&gt;
We have templates for:&lt;br /&gt;
&lt;br /&gt;
* LAMP stack - Apache, MySQL, PHP&lt;br /&gt;
* LEMP stack - nginx, MySQL, PHP&lt;br /&gt;
* [https://gitlab.com/ GitLab] - web management of git repositories&lt;br /&gt;
* [https://owncloud.org/ OwnCloud] - file synchronization and sharing platform&lt;br /&gt;
* [https://wordpress.com/ WordPress] - blog software&lt;br /&gt;
* [http://dokku.viewdocs.io/dokku/ Dokku] - single-server git-push-to-deploy PaaS&lt;br /&gt;
&lt;br /&gt;
All templates use Ubuntu 20.04 64-bit.&lt;br /&gt;
&lt;br /&gt;
After the VM is provisioned, you will receive an e-mail with details on how to proceed. In general, any login information will be written to /home/ubuntu/application.txt.&lt;br /&gt;
&lt;br /&gt;
== LAMP and LEMP ==&lt;br /&gt;
&lt;br /&gt;
These templates come with basic webserver and database installed. For PHP, mod_php is used for Apache and php5-fpm for nginx.&lt;br /&gt;
&lt;br /&gt;
The web root directory and MySQL root password can be found in /home/ubuntu/application.txt.&lt;br /&gt;
&lt;br /&gt;
We include a script /opt/ssl.py that will set up your webserver to support SSL, and to automatically obtain and renew SSL certificates via Let's Encrypt. To use it, pass the domains that will be served to the script, e.g. &amp;lt;tt&amp;gt;/opt/ssl.py example.com www.example.com&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== GitLab ==&lt;br /&gt;
&lt;br /&gt;
GitLab is a git repository management tool that includes features such as pull requests, issue tracking, and wikis.&lt;br /&gt;
&lt;br /&gt;
After the VM is provisioned, go to http://[VM external IP]/ and enter a password. You will then be prompted to login; the username is &amp;quot;root&amp;quot;, and the password is what you just entered.&lt;br /&gt;
&lt;br /&gt;
== OwnCloud ==&lt;br /&gt;
&lt;br /&gt;
After the VM is provisioned, go to http://[VM external IP]/ and enter the initial account information.&lt;br /&gt;
&lt;br /&gt;
The MySQL login details for both the root database user and the OwnCloud database can be found in /home/ubuntu/application.txt. OwnCloud will be configured to automatically detect the MySQL database, so you do not ordinarily need to use this.&lt;br /&gt;
&lt;br /&gt;
We include a script /opt/ssl.py that will set up your webserver to support SSL, and to automatically obtain and renew SSL certificates via Let's Encrypt. To use it, pass the domains that will be served to the script, e.g. &amp;lt;tt&amp;gt;/opt/ssl.py example.com www.example.com&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== WordPress ==&lt;br /&gt;
&lt;br /&gt;
After the VM is provisioned, go to http://[VM external IP]/ and enter the initial account information and other configuration details.&lt;br /&gt;
&lt;br /&gt;
The MySQL login details for both the root database user and the WordPress database can be found in /home/ubuntu/application.txt. WordPress will be configured to automatically detect the MySQL database, so you do not ordinarily need to use this.&lt;br /&gt;
&lt;br /&gt;
We include a script /opt/ssl.py that will set up your webserver to support SSL, and to automatically obtain and renew SSL certificates via Let's Encrypt. To use it, pass the domains that will be served to the script, e.g. &amp;lt;tt&amp;gt;/opt/ssl.py example.com www.example.com&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== Dokku ==&lt;br /&gt;
&lt;br /&gt;
If you selected an SSH key when provisioning the VM, then Dokku will already be set up with the key. Otherwise, go to http://[VM external IP]/ to configure Dokku.&lt;br /&gt;
&lt;br /&gt;
You can modify the hostname used by Dokku later by editing /home/dokku/HOSTNAME.&lt;/div&gt;</summary>
		<author><name>Favyen Bastani</name></author>	</entry>

	<entry>
		<id>https://wiki.lunanode.com/index.php/Volume-backed_instance</id>
		<title>Volume-backed instance</title>
		<link rel="alternate" type="text/html" href="https://wiki.lunanode.com/index.php/Volume-backed_instance"/>
				<updated>2016-01-01T17:34:33Z</updated>
		
		<summary type="html">&lt;p&gt;Favyen Bastani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The root partition of a virtual machine can be stored on a [[Volumes|volume]] to prevent extended downtime from a hardware failure incident. Upon detection of a failed host node, VMs without local storage will be automatically booted on another host node.&lt;br /&gt;
&lt;br /&gt;
To accomplish this, start by creating a new volume from the [https://dynamic.lunanode.com/panel/volumes Volumes page]. Select the region where you'll be provisioning the VM, a source template, and the desired disk size. If the disk size is equal to or smaller than that of the VM plan that you will use, then you won't be charged for the space; otherwise, each additional GB is $0.03/mo.&lt;br /&gt;
&lt;br /&gt;
Note: if you already have a VM that you want to migrate to be on a volume, then you can take a snapshot of the VM, and then create the volume from the snapshot. Then, preserve the external IP address be de-associating the IP of the old VM and associate it with the new volume-backed VM.&lt;br /&gt;
&lt;br /&gt;
Once the status of the volume is active/available, provision a VM from the volume (simply select the &amp;quot;My Volumes&amp;quot; tab when creating the VM). If you are using a template and are not using SSH keypair authentication, then you also need to check the &amp;quot;Set password via cloud-init&amp;quot; option.&lt;/div&gt;</summary>
		<author><name>Favyen Bastani</name></author>	</entry>

	<entry>
		<id>https://wiki.lunanode.com/index.php/Hardware_specifications</id>
		<title>Hardware specifications</title>
		<link rel="alternate" type="text/html" href="https://wiki.lunanode.com/index.php/Hardware_specifications"/>
				<updated>2016-01-01T17:25:14Z</updated>
		
		<summary type="html">&lt;p&gt;Favyen Bastani: /* Toronto */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The specifications below are for all SSD plans (e.g. s.half, m.1, c.1).&lt;br /&gt;
&lt;br /&gt;
== Toronto ==&lt;br /&gt;
&lt;br /&gt;
We use:&lt;br /&gt;
&lt;br /&gt;
* Dual Xeon E5-2690 v2 CPUs (older hypervisors have Xeon E5-2690 or Xeon E5-2670)&lt;br /&gt;
* Hardware RAID&lt;br /&gt;
* Pure SSD RAID10 storage array&lt;br /&gt;
* 2x10gbps ports, one for VM network and one for the storage cluster&lt;br /&gt;
&lt;br /&gt;
== Montreal/Roubaix ==&lt;br /&gt;
&lt;br /&gt;
We use the same type of hardware in Montreal and Roubaix:&lt;br /&gt;
&lt;br /&gt;
* Dual Xeon E5-2660v3 CPUs&lt;br /&gt;
* Hardware RAID&lt;br /&gt;
* Pure SSD RAID10 storage array&lt;br /&gt;
* 2x10gbps ports, one for VM network and one for the storage cluster&lt;br /&gt;
* OVH Anti-DDoS Pro DDoS mitigation system&lt;/div&gt;</summary>
		<author><name>Favyen Bastani</name></author>	</entry>

	</feed>