The basic conceptual element of vControl is an action: the core indivisible element. Each action performs single operation. For example: starts a VM, creates a snapshot, reboots a host, etc. Another core element is a workflow. Let it be called further  WF, for some shortening. A WF contains an action or a chain of them united with links. Linking defines the execution order of actions inside a WF. Once created and saved a WF becomes a static element. To animate it the job is required. A Job is an essence that is launched on the base of a WF, a job provides  WF execution.

So, we’ve got the following:
- Actions (indivisible, performs single operation);
- WF (contains set of actions with defined execution order);
- Job (runs a static WF).

The development environment for WF creation is called Workflow Studio. It holds action-sets for each Action Pack (AP) and a set of common actions that may work with different resources despite . Actions from different APs, any action combination may be present in one WF. For example - a VMware ESX VM launch, Xen host shutdown, sending a PowerShell script for execution on a VM located on a Hyper-V server, - all mentioned operations may be combined in a one WF and provided by a single job launch.

Next time we’ll create a WF using actions of AP or several of them that you prefer. Any suggestion and requests are welcome

Hi everyone! This is my first, my introductory post.

My name is Igor Kolosov and I’m glad to be a member of vControl team. My position is QA automation engineer.

As long as I’m engaged in product development and testing I’ve decided to help everybody interested in to get acquainted with one of vControl features - Task Automation. I promise to do my best while posting to this blog: I’ll even try to become some kind of guide and to pass useful skills I’ve acquired working with vControl and it’s Task Automation in particular to you.

Task Automation is a remarkable feature, one that may save your time and open the access to a new approach regarding VM managing.
Became a little bit excited? That’s great then!

My next post will be dedicated to the Task Automation essence in the vControl, it’s main points and development environment - Workflow Studio.

Farewell till the next post and good luck to everyone

I am happy to inform you that the trial version of vControl 1.6 is available for download from the official Vizioncore website !

Don’t forget to read Release Notes and Installation and Setup Guide before installing - they content important information for successful installation of vControl.

Hello everyone and welcome to the community site for vControl!

My name is Andrey Smolenko and I am the Lead Systems Engineer for the vControl team. I am responsible for planning, implementation and managing the different virtualization software for our development and QA infrastructures. I will be posting and updating information related to vControl and the virtualization industry in general to this blog.

I would first like to express my congratulations to the Management, Development and QA teams with the first public release of vControl. It’s a great job that has been done and I am really proud and happy to work together with everyone on this great project.

vControl is a multi-hypervisor virtual machine management solution that provides the following features:

· Self-Service provisioning

· Multi-VM control

· Task automation

· High availability

· Virtual infrastructure discovery

The next post will be about the Self-Service provisioning feature, its internal mechanics and related tips. Stay tuned!