Request #4733

Virtual Router: change capacity of VM when instantiating Virtual Router

Added by EOLE Team over 4 years ago. Updated over 4 years ago.

Status:PendingStart date:08/22/2016
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:-
Pull request:

Description

Hello,

Our virtual router define capacity modification:

CONTEXT = [
  NETWORK = "YES",
  SSH_PUBLIC_KEY = "$USER[SSH_PUBLIC_KEY]" ]
CPU = "0.02" 
DISK = [
  IMAGE_ID = "13884" ]
GRAPHICS = [
  LISTEN = "0.0.0.0",
  TYPE = "VNC" ]
LOGO = "images/logos/linux.png" 
MEMORY = "128" 
NIC = [
  NETWORK = "EOLE",
  NETWORK_UNAME = "nebula" ]
NIC = [
  NETWORK = "academie" ]
NIC_DEFAULT = [
  MODEL = "virtio" ]
USER_INPUTS = [
  CPU = "O|fixed|| |0.02",
  MEMORY = "M|range||128..512|128",
  VCPU = "O|range||2..4|2" ]
VCPU = "2" 
VROUTER = "YES" 

But when instantiating that virtual router template, I can not change the capacity (see instantiate-vrouter.png).

I can't poweroff the virtual router VM to change its capacity:

[VirtualMachineAction] Action "poweroff" is not supported for virtual router VMs

Regards.

instantiate-vrouter.png (29.5 KB) EOLE Team, 08/22/2016 11:45 AM

History

#1 Updated by EOLE Team over 4 years ago

I just realize that the disk operations are missing too.

It may be a feature request instead of a bug.

Regards.

#2 Updated by Carlos Martín over 4 years ago

  • Tracker changed from Bug to Request
  • Subject changed from Virtual Router: unable to change capacity of VM when instantiating Virtual Router to Virtual Router: change capacity of VM when instantiating Virtual Router
  • Category changed from Sunstone to Core & System

Moving this to request

Also available in: Atom PDF