Entries by Wei Zhou

,

Host Control Plane Status I CloudStack Feature First Look

Introduction Diving into the ever-evolving world of Apache CloudStack, it is undeniable that its continuous enhancement has led it to become an influential infrastructure management platform. The recent feature addition, ‘Host Control Plane Status’, further refines this powerful tool by extending the hypervisor host control state in the listing of Virtual Machines / VMs (ie. user Instances, Virtual Routers, and System VMs). Specifically, it permits users to evaluate the feasibility of VM lifecycle actions like start / stop / restart / migrate, and to cross-verify the accuracy of VM metrics. Host State and Resource State Each Host in the Apache […]

/by
,

CloudStack Autoscaling I CloudStack Feature Deep Dive

Introduction Apache CloudStack 4.18 introduces the Autoscaling feature, enabling users to allocate and release Instances’ resources automatically. This feature streamlines resource management by dynamically adjusting resources to meet demand, thus ensuring optimal performance and cost efficiency . CloudStack Autoscaling removes any dependency on 3rd party hardware or software solutions. It leverages existing resources, such as the underlying hypervisor and Virtual Router, to gather consumption metrics and, based on user-defined conditions and thresholds, proactively adjust resources to deliver ideal performance and resource consumption. Feature Overview The Autoscaling process in CloudStack involves the creation of an Autoscale VM group, which contains a […]

/by
,

Adaptive Affinity Groups l CloudStack Feature First Look

  In Apache CloudStack, Host Affinity and Host Anti-Affinity refer to the ability to deterministically ensure that a set of Instances run on the same or diverse hypervisor hosts in order to meet specific workload needs. How Affinity Groups Worked Previously Before Apache CloudStack 4.18 there were two types of Affinity Groups: Host Affinity and Host Anti-affinity.   • Host Affinity Host Affinity Groups allow users to specify that a set of Instances should always run on the same hypervisor host. This ensures minimum latency and maximum bandwidth between Instances as there’s no need for the network traffic to leave […]

/by