Can you create a blpackage to update these settings and use properties for those values ? then you’d just update the properties in the job.
Thanks for your answer, Bill.
I'm quite new to BSA and don't really get what you want me to do. Yes I can create a blpackage and a corresponding blpackage job. Yes I know how to define new properties in a blapackage and how to update those properties (even with NSH).
What I don't know is, how I can use a blpackage to update properties of a VirtualGuestJob. There is no option to build a blpackage on a VGJ (or any other jobtype for that matter). Could you explain this in more detail, please?
you want to update the existing vgp/vgj w/ new configurations so the next time you deploy it the vm will have more memory/cpu, or you want to update a VM you already deployed w/ this VGP/J and give it more memory/cpu ?
The first case. I want to use the same VGJ with updatet settings to deploy different VMs (one at a time). Processor and RAM were just examples. I'd need to define another name for the VM too, for example, but I thought that would use the same process and didn't mention it here to keep it more simple to understand my intention.
It looks like the 'Virtualization updateVirtualGuestPackage' would do it. you give the vgp id and a xml file w/ the settings and an xml file like you used to create it w/ the settings changes.
But wouldn't that only Change the values in the VirtualGuestPackage which would then be overwritten again by the values in the VGJ when I run it resulting in other values than those that I intended?
Existing VGP has no. of processor = 2 and RAM = 2 GB.
Corressponding VGJ has no. of processor = 4 and RAM = 4 GB.
When I run the VGJ the ne VM will have 4 processors and 4 GB RAM.
Now I update the VGP to no. of processor = 6 and RAM = 6 GB.
I can't change the VGJ so there is still no. of processor = 4 and RAM = 4 GB.
When I run the VGJ again there will be another new VM with 4 processors and 4 GB of RAM.
If you have updated your VGP, then I think you have to create new VGJ to reflect the changes.
That's what i think too and it's the thing that I'm trying to avoid ^^
Make a new vgj ?
Yes, I'm tryying to avoid creating a new VGJ for each VM I deploy. I want to reuse the sam VGJ and just change the necessary values (processor count, RAM, Machinename etc.)