[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
howtos:slackware_admin:slackware-arubacloud [2018/02/13 12:39 (UTC)] – draft 2 andrixnet | howtos:slackware_admin:slackware-arubacloud [2020/05/17 22:07 (UTC)] (current) – [Importing Slackware VM image into ArubaCloud] andrixnet | ||
---|---|---|---|
Line 2: | Line 2: | ||
====== Install Slackware on a CloudVPS by ArubaCloud ====== | ====== Install Slackware on a CloudVPS by ArubaCloud ====== | ||
- | ArubaCloud offers excellent low-cost VPS services, starting at 1 € / month //(at least when this article | + | ArubaCloud offers excellent low-cost VPS services, starting at 2.79 € / month //(updated May 2020; was 1€/month in feb. 2018, see ArubaCloud |
- | This article refers to installing Slackware on [[https:// | + | This article refers to installing Slackware on [[https:// |
- | You can request a free trial [[https:// | + | |
- | //**This guide does not cover Cloud Pro or other services by ArubaCloud.**// | + | //**This guide does not cover Cloud Pro or other services by ArubaCloud**// |
===== Prerequisites ===== | ===== Prerequisites ===== | ||
Line 15: | Line 14: | ||
* a FTP hosting space with several GB of available space and reasonable speed. | * a FTP hosting space with several GB of available space and reasonable speed. | ||
* VMware Player on your computer and at least as much free space as the CloudVPS virtual HDD | * VMware Player on your computer and at least as much free space as the CloudVPS virtual HDD | ||
- | * a Live CD such as SLAX | ||
===== Initialization ===== | ===== Initialization ===== | ||
Line 23: | Line 21: | ||
- load credit into your account (free trial voucher or purchase credit) | - load credit into your account (free trial voucher or purchase credit) | ||
- create VPS based on predefined OS template | - create VPS based on predefined OS template | ||
- | This guide has been written using an **Ubuntu | + | This guide has been written using an **Ubuntu |
+ | (//updated May 2020//) | ||
===== Information gathering ===== | ===== Information gathering ===== | ||
Line 29: | Line 28: | ||
Having the VPS up and running, and after receiving your access credentials, | Having the VPS up and running, and after receiving your access credentials, | ||
- | * HDD size | + | * HDD size and layout |
* Public IP (of the VPS), including netmask, gateway | * Public IP (of the VPS), including netmask, gateway | ||
Line 35: | Line 34: | ||
Log in to the CloudVPS using SSH. | Log in to the CloudVPS using SSH. | ||
- | < | ||
- | < | ||
- | < | ||
+ | Show IP and netmask (write it down): | ||
+ | < | ||
+ | Show default gateway (write it down): | ||
+ | < | ||
+ | Show nameservers (write it down): | ||
+ | < | ||
+ | Show disk layout (write down the total disk size in blocks): | ||
+ | < | ||
+ | Install **ncftp** package: | ||
+ | < | ||
+ | Optimize disk by overwriting all free space with zeros (helps with compression): | ||
+ | < | ||
+ | ===== Export an image of the Aruba created server ===== | ||
+ | <note important> | ||
+ | Perform it if you want to play at home with the Aruba generated server</ | ||
+ | |||
+ | < | ||
+ | |||
+ | Make sure you have enough free space in your FTP account. This will take up several GB of data. | ||
+ | < | ||
+ | <note tip>This may take a while, even hours, depending on the available bandwidth between Aruba' | ||
+ | |||
+ | //It is a rather dirty trick, but it works.// The template contains only a bare-bones installation with minimal services running. You may check and see if there is any background daemon that might write much to the disk and stop it, but other then a few log entries, there isn't anything worth mentioning. | ||
+ | |||
+ | <note warning> | ||
+ | |||
+ | You can use this image to make tests on your local VMware Player, and also as a test for the FTP transfer. You need either a Linux Live CD or a running virtual machine with an installed Linux that includes **// | ||
+ | |||
+ | ===== Slackware virtual machine ==== | ||
+ | |||
+ | **Create your own, local, virtual machine** with VMware Player. | ||
+ | * Start Vmware Player | ||
+ | * Create new virtual machine | ||
+ | * "I will install the operating system later" | ||
+ | * Choose " | ||
+ | * Name it (ie. aruba_slack) | ||
+ | * **Maximum disk size: same as VPS HDD size (in GB)**; store as single file | ||
+ | * proceed to finish. | ||
+ | |||
+ | **Modify the virtual machine** you just created as follows: | ||
+ | * Memory = 1GB | ||
+ | * Processors = 1 core | ||
+ | * CD/DVD = use ISO image (select slackware64-14.2-install-dvd.iso locally), connected at power-on | ||
+ | * Network adapter = NAT, connected at power-on | ||
+ | * Sound card = REMOVE | ||
+ | * Printer = REMOVE | ||
+ | |||
+ | **Start the virtual machine.** | ||
+ | * Enter the console (click in the VM display area) | ||
+ | * Proceed to install Slackware as you would on a physical server with the same characteristics of your cloud server. //There are no exotic hardware or settings.// | ||
+ | |||
+ | <note tip>For example, you could use a single partition for both system and data, and a small partition (ie. 1-4GB) for swap. Or you could use about a partition for the system, a partition for swap, a partition for data. //Your choice// | ||
+ | |||
+ | <note tip>For a server installation you might want to skip KDE, T, TCL, X, XAP, XFCE package series</ | ||
+ | |||
+ | <note tip> | ||
+ | |||
+ | < | ||
+ | |||
+ | During the configuration phase, assign the proper hostname, but set it to obtain IP address via DHCP.</ | ||
+ | |||
+ | After the first start of your fresh Slackware installation, | ||
+ | |||
+ | I'll leave additional software for later, to minimize the data transfer. | ||
+ | |||
+ | ===== Exporting Slackware VM image ===== | ||
+ | |||
+ | Make sure you have enough free space in your FTP account. This will take up several GB of data. | ||
+ | |||
+ | **In your Slackware virtual machine:** | ||
+ | |||
+ | * Stop all unneccesary services (inetd, | ||
+ | * Optimize disk by overwriting all free space with zeros (helps with compression, | ||
+ | < | ||
+ | |||
+ | * Export disk image | ||
+ | < | ||
+ | |||
+ | <note tip>This may take a while, even hours, depending on the available bandwidth between your computer and the FTP server.</ | ||
+ | |||
+ | //It is a rather dirty trick, but it works.// | ||
+ | |||
+ | <note warning> | ||
+ | |||
+ | ===== Importing Slackware VM image into ArubaCloud ===== | ||
+ | |||
+ | With the above step completed without error, you can proceed to inject the image into the ArubaCloud VPS. | ||
+ | |||
+ | * Log in to your ArubaCloud Control Panel. | ||
+ | * Go to "Cloud servers" | ||
+ | * If your VPS is turned off, turn it on and wait until startup is completed (see progress indicator) | ||
+ | * Under " | ||
+ | * Open the recovery console. You'll get to see your server' | ||
+ | * log in to your server, as root | ||
+ | * __ALTERNATELY you could ssh into it. Also use this method if you encounter problems with recovery console key-mappings.__ | ||
+ | * check running processes and stop any unnecessary daemons (cron, acpid, atd, fail2ban, rsyslog, open-vm-tools) | ||
+ | * **you must also disable swap memory.** | ||
+ | * run the following command: | ||
+ | |||
+ | < | ||
+ | <note tip>This may take a while, even hours, depending on the available bandwidth between Aruba' | ||
+ | |||
+ | <note warning> | ||
+ | |||
+ | **IMMEDIATELY after it finished successfully: | ||
+ | * Go to "Cloud servers" | ||
+ | * Under " | ||
+ | <note warning> | ||
+ | |||
+ | Start your Slackware ArubaCloud server: | ||
+ | * Go to "Cloud servers" | ||
+ | * Under " | ||
+ | * wait for it to start (//if it takes apparently too long reload the page. Apparently sometimes the UI doesn' | ||
+ | * Under " | ||
+ | * Open the recovery console. You'll get to see your server' | ||
+ | * log in to your server, as root | ||
+ | * run netconfig to set up the network according to ArubaCloud IP settings (//your wrote them down earlier//) | ||
+ | * just to make sure everything works properly, reboot your machine. | ||
+ | * restart the recovery console after reboot | ||
+ | * check that everything is ok | ||
+ | * check that you can log in remotely | ||
+ | <note important> | ||
+ | |||
+ | **Now you have a running Slackware64-14.2 in an ArubaClould VPS.** | ||
+ | |||
+ | ===== Additional configuration ===== | ||
+ | |||
+ | Since it runs under VMware hypervisor, it is useful to have the VMware-tools installed. I recommend you install the open-source version from Slackbuilds: | ||
+ | |||
+ | After your install the package and start the tools, you can verify that it works properly by: | ||
+ | * Go to "Cloud servers" | ||
+ | * Under " | ||
+ | |||
+ | This is the normal shutdown procedure initiated at the request of the hypervisor, received by open-vm-tools and performed in the guest OS to obtain a clean system shutdown. | ||
+ | |||
+ | The "Force switch off" is equivalent to pressing the power button on a physical computer. | ||
+ | |||
+ | **Enjoy your Slackware VPS!** | ||
====== References ====== | ====== References ====== | ||
- | * [[https:// | + | |
+ | | ||
+ | * [[https:// | ||
====== Sources ====== | ====== Sources ====== | ||
Line 53: | Line 189: | ||
<!-- Authors are allowed to give credit to themselves! --> | <!-- Authors are allowed to give credit to themselves! --> | ||
- | * Originally written by [[wiki: | + | |
<!-- * Contributions by [[wiki: | <!-- * Contributions by [[wiki: | ||
<!-- Please do not modify anything below, except adding new tags.--> | <!-- Please do not modify anything below, except adding new tags.--> | ||
<!-- You must remove the tag-word " | <!-- You must remove the tag-word " | ||
- | {{tag> | + | {{tag> |