Surgient Success

Hi,

I need some help in Command line interface of VCS.

when I'm passing action arguments like name of the image its throwing error

"There was a problem: 00190011 Unexpected runtime exception thrown by service met
hod invocation.
Object reference not set to an instance of an object".

Where can I see the deployed VM, since in reservation column it’s not deploying. But in GUI there is no option to deploy the serverconfig.

The Surgient GUI only supports the deployment of applications, so you are unable to deploy a server configuration as a stand-alone entity.  You must deploy it as part of an application configuration.  If you only need to use one particular server config, you can define an application configuration that maps soley to that single server configuration. 

As far as the incorrect syntax of your command, it would be helpful if you would include your entire command so that I can see what you are trying to run and perhaps even try it for myself.  I will tell you that any name that contains spaces will need to be placed into quotes (") in order to be properly parsed. 

Thanks,

Jackie.

Hi Jackie, 

    This is the command I'm using

       scheduleddeploymentaction 36 saveas "test"

36 is deployment id , saveas is a action , test is the name and

 Im getting deployment id by scheduleddeploymentlist command

highlighted one is the deployment ID

 Id       Pool            Based On        Begin                            End                              State             Group

37    EsxPool         WinProf           7/1/2009 10:23 AM         7/1/2009 12:12 PM        Starting            36

38    EsxPool         WinXP             7/1/2009 10:30 AM         7/1/2009 12:19 PM         Provisioning     37

Thank you - the new information you have provided is much more helpful towards me helping you solve the problem!  I think the problem in this case is that you are choosing the DeploymentGroup ID, but you are actually saving just a server configuration, for which it wants the ID of the scheduled deployment.  You are likely getting the error because no scheduled deployment with the ID of 36 exists.  Please try your command again with the ID out of the Id column and let me know if that solves your problem.

Thanks,

Jackie.

Hi Jackie,

    Im not saving server configuration,

    Actually first we will create a Virtual Machine in ESX Server or Microsoft Virtual Server, then we will copy the image to  Surgient Library and we will use it for deployment and others purposes.

Similar to that one Im creating a image of the deployed VM, which is deployed using Surgient.

Refer in GUI interfcae after deploying image go to reservation panel and look for saveas button(looks like a floppy) it ll give a window, where we have to enter the name of the new VMDK file , New server configuration , New Application configuartion, then the image will be saved in Surgient library.

Regarding ID, if I use the id which is out of the ID column it is showing  "no scheduled deployment with the ID of 44 exists"

The command that you are using is intended to save the server configuration - I have confirmed this by looking at the backend code.  I find it interesting that you are getting an invalid ID error using the ID out of the ID column given that the ID is coming from "scheduleddeploymentlist", which is intended to show a list of scheduled deloyments and their associated IDs (the ID column).  I have tested this on my system and I only get the error you state if I do truly use an invalid scheduled deployment id. 

 What version of Surgient are you using? 

 If you wish to save an entire configuration, similar to what the GUI is doing, then you will wish to act upon the "deploymentgroup".  You can get a list of those commands using "help deploymentgroup".  You will find a deploymentgroupaction command that contains a "save as".

 Thanks,

Jackie.

Thank alot jackie, its working....

   Then one more help, You have any CLI command usage document.

   In help column there is no description about command, only syntax is there.

The vcsadmin is actually a tool designed for support and while it is used by many customers, it remains officially undocumented because it is technically unsupported.  If you type "help" before any command, it will give you the synatx for the command, but in most instances it assumes enough product knowledge that you can relate back to Surgient terminiology and understand the commands you are looking at or the commands you are looking for.

Were you in the training classes that we held at WiPro last year?  I met so many people that I cannot remember everyone's names.

Jackie.

No, I haven't attened the training.But some of my team mates attened the training.

I have seen you, during the training session but on that time I was working on other module.So I was not able to atten the training.