Hi,
I'm a beginner on vCO and I would like to create a workflow to deploy template with customization.
My difficulty to use the storage profils and the customization already existing in "customization specification manager"
At the end, I would like a workflow with this step :
1- VM NAME
2- Chose tempate = Win2kxx, RHEL6, etc...
3- Chose Storage profil = Prod, Dev, etc..
4- IP address
5- Backup = Yes or No (if Yes, add NIC2 and give IP address)
During the customization the Windows VM must to be integreat the Domain, may be using an domain admin account in the workflow.
If you are an idea....
Hi!
For the customization specification see htis thread, it includes examples: http://communities.vmware.com/thread/286988
Adding a second NIC will introduce some scriptiong effort, because you have to change a bit more in the customization specification (the number of IP mappings has to match the number of the NICs in the VM).
I recommend to split up the process:
1. Clone the Template, no customization (and no power on)
2. change the new VM's hardare (if necessary)
3. Customize the VM (yes, this can be an extra workflow/task in vCO, it's not exposed in the vSphere Client!)
For Storage Profiles this example might help: http://communities.vmware.com/thread/420938
(depends on your architecture)
In General: Onyx is your friend: http://www.vcoportal.de/2012/05/using-onyx-for-fast-workflow-development/
Cheers,
Joerg
Thank you for this answer.
How to split up the process ?
Hi Jeremie,
Create a workflow which will do each step by itself. Then create a workflow that links all these workflows together.
Cheers,
Dave
Ok thanks.
Is it possible to add text field in the workflow ?
Example : N° of project, comments for additional information, ...
Because I would like to propose my workflow like a form with approvement.
Yes, you can definitely do that. Create some input parameters of type string (or number or boolean) and you can use those to contain the data you require.
Cool but how ?
Open the Orchestrator Client and edit the workflow. Go to "Inputs" and add the parameters.
It might be best if you go through some of the introductory videos on www.vcoteam.info to get an idea on how to work with Orchestrator and creating a basic workflow.
No, it's ok for that but I don't understand "you can use those to contain the data you require"
I want requiered fields, if I create a input parameter I need to use this , if not I have a warning on my workflow.
I am not sure what exactly you are needing here.
Do you want to have your own text on the workflow input (in which case you can place that in the presentation, or create an action which populates an input parameter) or do you want the requester to input the data (in which case it has to be an input parameter).
I need the requester input the data (ex : N° of project) but I need required fields (no empty possible)
Okay, gotcha. Go to Presentation, select your input parameter, go to Properties and add the property "Mandatory Input" and make sure it is "Yes".
Yes, cool, thank you.
Now I would like to send an email with all selections and descriptions (N° of project, VM name, datastore,...) to approver (YES or NO), if YES the workflow play if NO worlflow cancel.
There is an example workflow for that "Example interaction with email".
Base it off that and customise as you need.
Ok thank you
I'm trying to use "Customize, Windows with single NIC and credential" just after my first Workflow "deploy_Template".
My problem is : during the workflow "deploy_Template" the VM Name is a "String" but the workflow "Customize..." need "VC:VirtualMachine", I can't link string and VC:VirtualMachine.
How can I link this workflows ?
If you go through the input parameters for the workflow, you will find the description tells you what the parameter is for.
You are trying to assign your VM name against the input parameter "vm" I assume, which is the "Virtual machine to clone". You are probably wanting to assign it against "name" which is the "New virtual machine name".
http://communities.vmware.com/thread/342686
Try running the "Customize, Windows with single NIC and credential" workflow by itself so that you understand what inputs it expects, then you can set about mapping those from your other workflow.