LSW CloudStack 2018-08-08

 Enhancements for Leaseweb CloudStack Private Cloud on Aug 8, 2018.

CloudStack Private Cloud is available in London DC

Our customers can buy CloudStack Private Cloud of all sizes in our London data center. 


Specify next hop in VPC gateways now

You can now specify next hop in VPC gateways. A next hop is the next router to which a packet is sent from any given router as it traverses a network on its journey to its final destination 

Our CloudStack Private Cloud, customers can now specify the next hop in VPC gateways. 


How to set up next hop 

Perform the following steps to set up the next hop of static route in VPC: 

  1. Login to CloudStack dashboardgo to the left panel, and select “Network”.

  2. Using instructions at Leaseweb Knowledge base, create a VPC.

  3. Select the VPC, and under Router, use the link “Private gateways” to navigate to the detail screen of private gateways.

  4. Next to “Details” tab, there is a "Static Routes” tab for specifying CIDR of destination network, routes and actions as it appears on the screenshot below. Use the “Next Hop” field to add next hop of static route in the VPC.

Specify specific qemu machine type in resource tags

As a part of our continuous improvement and up-to-date security maintenance, we upgraded all hypervisors with latest OS. This upgrade caused licensing issues of third party software (as it was bound to CPU type) to some of our customers. 

After the analysis, our engineering team found that the previous version of the CPU type was PC-1.2. 

1.  root@node11:~virsh dumpxml i-25-1419-VM |grep machine 

2.      <type arch='x86_64' machine='pc-1.2'>hvm</type> 

New version of OS
 contains pc-i440fx-2.5 CPU type. 

1.  root@node01:~virsh dumpxml i-3231-15268-VM|grep machine 

2.      <partition>/machine</partition> 

3.      <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> 

if our CloudStack Private Cloud customers want to start their VM with a different QEMU machine type, they can specify  machine type via VM resource tags with 'StartCommand', so it can start the VM with desired QEMU machine type. Use tag name: vm.machine.type  

How to start VM with specified QEMU machine type

Perform the following steps to start a VM with specified QEMU machine type: 

  1. Login to CloudStack dashboardgo to the left panel, and select “Instances”.

  2. Select the VM you want to start with specified QEMU type.
  3. Scroll down to the bottom of “Details” tab, and use the Key/Value in the Tags section to add “vm.machine.type” as displayed in the image.
  4. Press the play icon (with caption ‘Start Instance’) to start the VM.

Both PAYG and Flat Fee in the Customer portal menu

If you are using PAYG or Flat Fee CloudStack Private Cloud, you can manage them all under one page accessible via the Customer portal menu. 

Knowledge Base updates 

We have revised a list of Knowledge Base articles and updated them with the latest information.  

Check them out and let us know if something is still missing: 

Bug fixes 

Here are the most important fixes and additions: 

  • Improvement - Dashboard of public IPs now includes only the used public IPs instead of all IPs 

  • Improvement  Display of meaningful error messages while creating or starting a VM 

  • Improvement - Start and end IP addresses are now mandatory for guest networks 

  • Improvement - Force stop router while restart network/VPC with cleanup 

  • Improvement - Prevent CloudStack from creating duplicate volume when a VM is restored 

  • Fix - In case of any network change in VR, remote access VPN is not affected 

  • Fix - Fixed issues while removing VM snapshots in Error state 

  • Fix - Update user-data (or base64 string) from CloudStack UImax length of Base64-encoded userdata is increased from 32KB to 64KB 

  • Fix - Fixed GRE protocol to work with Ubuntu 16.04 

  • Fix - Fixed clock issues in Windows 2012 VMs 

  • Fix - NICs without public IP address is not removed on VR, which lead to VR migration failure; now fixed.