VM Storage Policy APIs aka Storage Profile APIs will be available in vSphere 5.5

Comments

1. jorg gray says

   11/22/2013 at 4:34 pm

   A frequently requested feature from customers and partners have been around the Storage Profile APIs and with the upcoming vSphere 5.5 release, it will now be possible to automate the management and consumption of Storage Profiles. http://www.paylessforstorage.co.uk/

   Reply

2. Shahar says

   12/25/2014 at 9:03 am

   hi
   first of all,Thanks, very helpful article.
   However, i tried to connect to the pbm service as suggested (but with c# code).
   I manged to get the token from the ssl service
   I manged to connect with it to the vimService and retrieve the cookie.
   When i tried to connect (Retrieve service) to the pbm service with the cookie, i'm getting "vim25:SecurityErrorr".

   Any ideas?

   Thanks in advanced.
   Shahar

   Reply

   • Kenny says

     01/28/2015 at 11:49 pm

     Did you ever get this to work Shahar? I am having the same issue... been trying for awhile now.

     Reply

     • Shahar says

       01/29/2015 at 10:04 am

       yes, i did...
       the problem was with where I set the cookie.
       my first assumption was:

       _pbmService.CookieContainer = new CookieContainer();
       _pbmService.CookieContainer.Add(cookie);

       However, this is not the only place we need to add the cookie.
       we need to add the cookie to the header.
       to do so, we need to add custom header to the c# class we generate from the wsdl

       see: http://dotnetslackers.com/articles/aspnet/Securing-ASP-Net-Web-Services-with-Forms-Authentication.aspx

       and then use it in our code:
       vcSessionCookieCustomHeader header = new vcSessionCookieCustomHeader();
       header.cookie = cookie.Value;
       _pbmservice.vcSessionHeader = header;

       Reply

       • Kenny says

         01/29/2015 at 2:54 pm

         Thank you very much for the quick reply! and of course the solution!!! I had tried each individually but not together. So happy I can stop banging my head on this... thank you again!

         Reply

       • Kenny says

         01/29/2015 at 5:42 pm

         One more question if have the time, I must be missing something... how are you applying the custom soap header in the class generated from the wsdl? Also, for the cookie being added did you have to change the key from vmware_soap_session to vcSessionCookie as they did in the java samples?

         var pbmService = new PbmService() { Url = url };
         var cookieContainer = new CookieContainer();
         cookie.Name = "vcSessionCookie"; // change from vmware_soap_session to vcSessionCookie
         cookieContainer.Add(cookie);
         pbmService.CookieContainer = cookieContainer;

         var header = new VcSessionCookieCustomHeader();
         header.cookie = cookie.Value;
         pbmService.vcSessionHeader = header;

         public class VcSessionCookieCustomHeader : System.Web.Services.Protocols.SoapHeader
         {
         public string cookie;
         }

         public partial class PbmService : Microsoft.Web.Services3.WebServicesClientProtocol
         {
         public VcSessionCookieCustomHeader vcSessionHeader { get; set; }

         Are you using the SoapHeader attribute? For example...
         [System.Web.Services.Protocols.SoapHeader("vcSessionHeader", Direction = SoapHeaderDirection.Out)]
         public PbmServiceInstanceContent PbmRetrieveServiceContent(ManagedObjectReference _this)

         Thank you!

         Reply

         • feng.zhang says

           07/23/2018 at 10:11 pm

           Hi, did you change the key from vmware_soap_session to vcSessionCookie as they did in the java samples?
           and Are you using the SoapHeader attribute? [System.Web.Services.Protocols.SoapHeader(“vcSessionHeader”, Direction = SoapHeaderDirection.Out)]

           i got vim25:NoPermission for PbmQueryProfile after pbmService.PbmRetrieveServiceContent finished,
           do you have some ideas?

       • Kenny says

         01/29/2015 at 7:27 pm

         I figured it out, thanks for the help. For anyone else that may run across this...

         [XmlRootAttribute(ElementName = "vcSessionCookie", DataType = "string", IsNullable = false)]
         public class vcSessionCookieCustomHeader : System.Web.Services.Protocols.SoapHeader
         {
         [System.Xml.Serialization.XmlTextAttribute()]
         public string cookie;
         }

         Reply

         • Shahar says

           02/01/2015 at 9:55 am

           sorry, i wasn't working the last two days.
           you are right, the XmlTextAttribute() will do the trick.

         • Shahar says

           02/17/2015 at 2:58 pm

           hi Kenny.

           Did you ever get the next exception:
           "the session is not authenticated"

           i tried to reconnect to vim service (and succeeded), and add the new cookie, but it didn't help...

           any thought?

           Thanks
           Shahar.

         • Kenny says

           02/17/2015 at 3:25 pm

           Hi,

           I have not ran across that yet, though I am still developing so haven't had the vSphere(vimservice) session open long enough at this point for the session to time out. Is your session timing out to vSphere and the pbmService session is still active during that time the scenario, or are you opening up a new pbmService after the vSphere session was reconnected?

           Ken

3. Atoka Sema says

   05/02/2015 at 5:54 am

   Hi,

   Thank you for this helpful article. I have couple of questions related to VM Storage Policy that I would like to ask.

   Is there a way to list all the VM Storage Policies using vSphere API?
   As you mentioned, we can do it using VM Storage Policy API, but what I am trying to do is to use vSphere SDK to get the Id of already created profile and assign it to a VM's Virtual Disk.

   Also can we create a VM Storage Policy with Rule-Set using VM Storage Policy API? I don't PbmProfileProfileManager.PbmCreate API taking any Rule-Set related parameter.

   Thanks.

   Reply

4. J Xu says

   03/13/2019 at 1:51 pm

   For vsphere 6.7, the command used should be -

   run.bat ListProfiles --vcurl https://[VC-IP]/sdk/vimService --ssourl https://[VC-IP]/sts/STSService --spbmurl https://[VC-IP]/pbm --username *protected email* --password vmware --ignorecert

   Reply