Manual:CHR AWS installation: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
Line 8: Line 8:
== Installation steps (long)==
== Installation steps (long)==


* Resize the image. After RouterOS is installed it will be much harder to change the available size
* Resize the image before installing the RouterOS. Amazon AWS minimal image size is 1GB. After RouterOS is installed it will be much harder to change the available size, the following command will increase the image size by 940MB
   qemu-img resize chr-6.34rc21.img +940M
   qemu-img resize chr-6.34rc21.img +940M
* Import the image as a volume on your AWS. As a return you will get the volume ID.
* Import the image as a volume on your AWS. As a return you will get the volume ID.
Line 23: Line 23:


* Now you can launch instance from your AMI.
* Now you can launch instance from your AMI.


== Alternative installation ==
== Alternative installation ==

Revision as of 08:08, 18 December 2015

Tools required

To get CHR RouterOS running on Amazon AWS cloud at this moment, there are certain steps that you have to do to get this working from scratch.

  • Virtual management software that works with ISOLINUX booter/installer on CHR image (KVM, VirtualBox or VMWare Workstation, VMWare Fusion, Hyper-V these tools are interchangeable);
  • Tool to resize the image file prior the installation as default image is 64MB of size and in some cases, more storage is required (qemu-img, VMWare built-in tool, VirtualBox external tool);
  • AWS API tools installed and configured (ec2-*).

Installation steps (long)

  • Resize the image before installing the RouterOS. Amazon AWS minimal image size is 1GB. After RouterOS is installed it will be much harder to change the available size, the following command will increase the image size by 940MB
 qemu-img resize chr-6.34rc21.img +940M
  • Import the image as a volume on your AWS. As a return you will get the volume ID.
 ec2-import-volume chr-6.34rc21.img -f raw -s 1 -b <bucket> -o <AKIAEXAMPLELALALA> -w <SECRETACCESSKEY > -z eu-west-1a

It is possible to follow the progress of the import.

 ec2-cancel-conversion-task <task id>
  • Create snapshot. Correct volume ID will be availabe when previous command ends or from your AWS account
 ec2-create-snapshot vol-e3c74810
  • Register AWS image as an AMI ec2-register -n CHR -s snap-a664a48e -d "6.34rc21" -a x86_64 --virtualization-type hvm
 ec2-register -n CHR -s snap-a664a48e -d "6.34rc21" -a x86_64 --virtualization-type hvm
  • Now you can launch instance from your AMI.

Alternative installation

  • On your AWS EC2 switch over to Ireland cluster and look up AMI ID ami-fce6448f
  • copy it over to cluster of your choice
  • Launch instances