VSM vCloud Director connector question

Similar Questions

• vCloud connector - cannot copy VAPP vCloud Director to vSphere

  Evening,

  Try to copy a paralytic to vCloud Director on vCenter 5.5 5.6 using vCloud connector 2.7.

  The scenario:

  -vCloud Director fully configured with one Org, an Org vDC and a catalog.

  -The catalog is entirely filled, shared and published.

  -Org and catalog are configured to allow the publication to external organizations;

  -vCenter and vCloud Director have been added to vCloud connector via vSphere Client plug-ins;

  -vCloud plug connector is able to see the entire structures of vSphere and vCD (org records, catalogs, vApps, models, etc.).

  Reproduce the error:

  -Using the vSphere Client, click on the Org vCD;

  -Go to the tab vApps.

  -Select a VAPP off engine;

  -Click on copy.

  -Select Catalog (it is marked as shared and, curiously, unpublished);

  -Select vCenter as the target;

  -Select the clusters, folders, data store, formatting the drive and so on;

  -Power On TIME after deploying (or not, does not matter);

  -Validate (managed);

  -Finishing.

  Task starts and fails in a minute (or less) with the following message:

  "Export OVF has failed. Failure when copying data to the clouds: https://< vcloud_director_fqdn >. Reason: [0e65fbc1-4e04-4924-ae06-c4377dfc97af] there is no catalog in the organization. »

  Looks as vCloud connector, for some reason, is unable to locate the catalog during deployment (although it may be perfectly visible during the Copy Wizard and in his inventory).

  I tried searching for it and can't find anything similar to this error.

  Maybe it s a vCD configuration error, but how would be? I ve already selected all types of option to allow editing of catalogue and sharing, and nothing has changed.

  I published also successfully catalog VCDs to vCloud connector content library, so nothing else makes sense to me.

  Solved.

  Created a new catalog and IS NOT published. Used for the copy. Went well.

• vCloud connector 2.5 - copy the model of vSphere to vCloud Director fails

  Hi all

  I'm trying to make a copy of the model of the private Cloud for vSphere (e.g. my instance of vCenter lab) the vCloud Director private cloud (my instance vCD lab, which is deployed and registered with the same instance of vCenter mentioned above) with vCloud connector 2.5.

  I have deployed the server component of vCC, configured and deployed two nodes of vCC - a to connect to vCenter for private cloud config vSphere and another to connect to the vCloud Director org for the basic cloud vCD config private. Moreover, the vCloud Director is registered to the same instance of vCenter which is used for vSphere cloud.

  I then tried to open a copy of the model from the vSphere cloud node to the node of vCD. The task to export the OVF template will start, and the task of SCR plugin will also display the copy task. This vCD instance also model any TIME if you go to the properties of the VDC organization selected during the SCR copy Wizard.

  After about 18%, the percentage remains stuck there for a little bit before the 'Export OVF Template"task fails with"Operation timed out ". After that, the task indicated in the vCC plugin will fail also later with (OVF Export failed. Null message) and the import of VAPP model in vCD job will fail also - VAPP failure will take upward of space inside the affected storage however profile until I have manually remove the failing through vCD VAPP model object.

  Anyone else having this problem? I've seen this problem on both environments so far: vCenter 5.1 update 1 with vCD 5.1.2 and vCenter 5.5 with vCD 5.5. If the problem seems to be specific to the version of vSphere. The logs generated by server SCR bee all that useful for me to understand what went wrong did not.

  Thank you

  You can consult this KB, if you haven't done so yet:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2078110

  I hope this helps.

• vCloud Director 5.1 install OS Question

  Can I use CentOS instead of Red Hat as the operating system for vCloud Director install?  If yes what the game (if any) would be if I needed VMware support (they even would support me)?

  Thank you for your time.

  Sean

  There is nothing prevents you to install it on CentOS.  During the installation you will be told that you are using an unsupported operating system.

  All the problems that would arise from the use of CentOS instead of RHEL is not support.  We must do better to ensure that it is not a question of use/code, as well a reasonable given the suspicion that the OS is really at fault.

  Strictly speaking, being an employee of VMware, I can't close my eyes go against the recommendations of the platform supported.

  However, in more recent versions, I have not personally seen problems directly related to the operating system.  vCloud is a java-based application and is associated with a specific version of Java that is provided by the installer.  If we use even the system version of Java to create the gap.

  too long, didn't read = you can, but shouldn't.

• vCloud Director vCloud connector installation

  I try to get vCloud connector installed inside vCloud Director. I deployed a VCC vCC node and server in my network ExternalRouted and I am following http://pubs.vmware.com/hybridcloud/index.jsp to a T.
  Org network gives SCR Server 10.10.1.53 and VCC node 10.10.1.54
  Within the vShield edge apparatus I configure ports as such

  -Screen Shot 2012-02-23 to 2.20.09 PM.png

  -Screen Shot 2012-02-23 at 2.21.33 PM.png

  I can access my vCloud knot web server interfaces and fine, but when I try to register that a node with the server is just completely turns off. The VCC server can ping the SCR node with the NATed IP of 192.168.60.24.
  It is located on this screen and two tracks and leave real quick or he just completely dies. I tried to switch to the Public as well, but it's still doesn't work.

  -Screen Shot 2012-02-23 at 2.24.37 PM.png

  
  If I go to the server and I click the button on Client vSphere or cloud.vmware.com I see this error and that doesn't look good.

  -Screen Shot 2012-02-23 at 2.27.55 PM.png

  
  I have completely open ports in firewall for these two vApps and not *'s everywhere, and it always shows the same errors.

  I was able to complete the vCloud connector install with zero problems when I just did a normal vSphere OVF import save it on my server vCenter. This isn't a problem with the OVFs.

  Thanks for any help.

  I have not tried.  Of course in my setup, my NŒUD is vCloud with a NAT address and which works very well.  It is the SCR is the issue because it needs access to vCenter Server.  You can try to use an external live... or just move right in vCenter

• vRealize device Orchestrator 6.0.3 and vCenter 5.5 5.6 U3/vCloud Director

  Hello world

  I have a few questions on the compatibility between vRO 6.0.3 and vCenter vCloud Director 5.6 and 5.5:

  In vCenter Orchestrator 5.5.2 I plugin to connect the vCO to vCenter (version 5.5.2.1875635):

  

  1. in new vRO 6.0.3 for configuration I can not find this plugin, but when I checked the news of plug-ins I found a plugin vCenter (version vCenter Server 6.0.2.2995112). But how can I connect vRO 6.0.3 vCenter 5.5 (only by the workflow?).

  

  2. a supplementary door on vSphere Web Client integration with vRO. To do this properly first of all I must use SSO authentication mode? It won't work with LDAP authentication?

  3. anyone know if vRO works closely with vCloud Director 5.6? I found 5.5.1.2 plugin, but using this plugin, I can not connect to vCD (in vCO 5.5.2 I have no problem).

  
  

  
  

  
  

  Hello

  (1) Yes, plugin configuration is workflow (this is the approach recommended new plug-ins; the old configuration of Web UI is deprecated and will be removed at some point).

  (2) only the SSO mode is supported; LDAP won't work. Note that the UNIQUE authentication token is acquired in the name of the user logged in vSphere client to Web, so you must make sure that this user has enough permissions to connect to vRO.

  (3) it should be newer versions of this plugin, and compatibility matrix showing which plugin version is compatible with given the vCD. Don't know where it is, however.

• Cannot access vCloud Director VM console

  Hello

  We´re in the face of a very strange problem when you try to access a console virtual machine via the vCloud Director 5.6 Web Portal.

  Let me describe the environment:

  1 - 2 vCloud Director cells;

  2. load balancer 1;

  3 - 1 VIP for the proxy console; 1 VIP for the web portal;

  4 - certificate of CA-signed 1 with wildcard characters (*. < domain >) instead of certificates 2 ordinary host (http. < domain > and consoleproxy. < domain >).

  5 - the following procedure was used to create the keystore of Java and to be able to import the certificate even twice (each time with a different alias):

  OpenSSL pkcs12 - in /keystore/ < company > .pfx-out /keystore/ < company > .pem

  OpenSSL pkcs12-export - in /keystore/ < company > .pem-inkey /keystore/ < company > .key-out _http.p12 /keystore/ < company > - name "http".

  OpenSSL pkcs12-export - in /keystore/ < company > .pem-inkey /keystore/ < company > .key-out _console.p12 /keystore/ < company > - name 'consoleproxy '.

  keytool - v - importkeystore - srckeystore /keystore/ < company > _console.p12 - srcstoretype PKCS12 - destkeystore /keystore/ < company > .ks - deststoretype JCEKS

  keytool - v - importkeystore - srckeystore /keystore/ < company > _http.p12 - srcstoretype PKCS12 - destkeystore /keystore/ < company > .ks - deststoretype JCEKS

  6 race "keytool-list - keystore /keystore/ < company > .ks - stores JCEKS" shows two aliases in the keystore.

  7 - vCD installer not to complaint about it.

  8 - certificate is loaded correctly when accessing the web portal

  Now the question:

  1 - the gate opens as it should;

  2. each type of action is possible and works very well;

  3. when we open a VM console for the first time, it opens normally;

  4. If we close it and try to reopen, or if we try to open a second console, it won´t open;

  5 - according to the browser:

  5.1 - console remains black. State begins to 'connection '. Changes to "Offline" after a short time;

  5.2 - console remains empty. Status hangs on "Loading"; He sometimes goes to "disconnected";

  6. If restart us the two cells, it begins around (able to open the first console, cannot open the rest);

  7. same behavior if the access using the VIP (with load balancing) or directly (using the internal IP address of cells).

  I ve seen some issues with what seemed like the same problem but no conclusive answer.

  Any help on this would be appreciated.

  Thank you very much.

  The fixed.

  1 - upgrade of vCD 5.6.3 to 5.6.4.

  2 - something with virtual machines, we had deployed for testing. We have erased their and the new have no behavior.

• vCloud Director or vRealize Automation?

  Hello

  I was hoping I could get some advice regarding the choice between vCloud Director and vRealize Automation. We have set up a test environment for vCloud Director however read some articles, it seems that it is a product that reaches the end of life for businesses, but not for service providers.

  So my question is a service provider should us be implementation vCloud Director or vRealize Automation? We do not want to be in a position to migrate off vCloud in a year.

  Any advice would be appreciated.

  Thank you

  Chris

  I can't make any kind of recommendation between the two, because I don't know what you want to do with the products.

  Addressing the availability of the product and the support of it:

  vCloud Director just won't be available to independently purchase and withdrew the license of the Suite from 6.x.  You must purchase the license 5.x to get it (assuming that it is available)... This aspect, if not suite your needs right now until mid-2017 (when vCloud will end support for users of the company).  From 2017, you have to make a decision as to what will replace vCloud or continue to use vCloud Director, even if we will not offer support for it.

  VRealize Automation will meet your needs?  I do not know without knowing your use case and requirements... that is for discussion of a VMware sales representative.

  Apart from all this: VSPP is the VMware service provider program.  A version of vCloud Director will exist for them, but it is precisely for them (members of the VSPP program).  Unless you work for a member of the VSPP program, the statements above concerning vCloud Director are what you think.

  If you are Member VSPP, vCloud Director for the providers of services (5.6.x) is available as the direct vcloud Director 5.5.x successor.  Then by all means we will continue to support these versions, and it can be used to manage resources like a Cloud provider.

  I had a number of people say they are service providers, which is very beautiful.  Be a VSPP means being in a specific program of VMware, which gives access to certain things (which AFAIK is vCloud for Service providers).

  I'm not trying to be harsh or terse here, but I want to just make sure we do differentiation key on what is available to whom and how.

• VCloud Director displays do not Vcenter data.

  Hi guys,.

  I installed VCD 5.5, vsheild Manager and vcenter on a single ESXi 5.5 . I am facing problems with VCloud Director.Although I have attached the Vcenter Sucessfully in VCD, vcenter data not poping upward into Vcd. So the list of hosts is empty. No resouce pool are coming in Vcd.

  Here are my questions coming in my mind... I think I might get hurt

  1 then I installed VCD 5.5, vsheild Manager and vcenter on a single ESXi 5.5 host?

  2. is it a problem with the license... Although all of them are allowed until 2015. ?

  3. do I need to manually install the agent Vcd on ESXi... Although I think that this should be done automatically? If yes how to do this.

  Please tell me where I can be wrong.

  I have attached snapshots of Vcenter and VCD. Please review those and help out me

  All responses will be appreciated.

  Thank you

  Tarun Gupta

  You must create a provider vDC for nothing appear.  This requires some DRS to be on (if you don't have it already done) and requires usually two hosts in a cluster.  This is because you need to spend in maintenance mode to install the agent correctly and can vmotion powerd on the VMS of a host while the other prepares.  It's all part of the installation and Administrator's guide.

• VCommander is really a replacement for vCloud Director?

  Hello

  someone said that vMware has bought Embotics vCommander and is to promote the planning is as a replacement for vCloud Director.

  If in the future, there will be no vCloud Director, only vCommander as vCloud 5.5 is the latest version of vCloud Director.

  Can someone shadow light on it if it's true or just a rumor?

  Thank you in anticipation

  Ashish

  vCloud Director goes because there are many common features between vCD and vCAC. And the positioning of these two manufacturers are becoming increasingly difficult. I think that's the only reason why they plan to stop it. And it will always be available to service providers. Not be included in vCloud Suite.

  I don't think that VMware will purchase another product like vCommander and enter in more complex questions of positioning.

• Will vcloud Director 5.5 compatible with vsphere 5.1U1?

  Hey,.

  We vSphere 5.1U1 running in production and we look at vCloud Director 5.5 for the deployment. But VMware does not have a virtual Director 5.1 appliance and we do not want to buy a server, Redhat enterprise server (we could upgrade vSphere 5.1u1 soon, but due the Veem, we cannot now). Since VMware provides the virtual appliance for vCloud Director 5.5, so I got this question that I can't answer in VMware documents:

  Will vCloud Director 5.5 compatible with vSphere 5.1U1?

  Thank you

  / S

  Yes vCloud Director 5.5 is compatible with vSphere 5.1U1.

  Check it out here. VMware product interoperability matrices

  Please consider awarding points when choosing the correct answer.

• vCloud 5.1 Plugin with vCO 5.5 + vCloud Director 5.5: Probable incompatibility?

  Hello

  I found that when you use the following combination vCenter Orchestrator is impossible to enumerate objects vCloud Director below the level of vDC of organization:

  • vCloud 5.5
  • vCO 5.5
  • vCloud Director Plugin for vCO 5.1
  • Logging on to the Organization of the system.

  The following error is reported in the newspapers - I pointed out the relevant sections. What seems to happen is that the following method: com.vmware.vmo.plugin.vcloud.VCloudEntityResolver.getEntityByReference is called, but fails with this exception: com.thoughtworks.xstream.converters.reflection.ObjectAccessException: javax.xml.bind.JAXBElement.name invalid final field. Is there a workaround currently available or a release of out-of-band of the vCloud Director plugin compatible with 5.5?

  Any help beyond "this is an unsupported configuration", and "a compatible plugin will be released later this year" would be appreciated, because we depend on vCO to supply our daily operations.

  Here is the stack complete error in the case of the developers look on this post:

  2013 10-15 10:56:23.021 - 0400 [http-bio-ip-8281-exec-16] ERROR {} [VCloudPluginFactory]

  com.vmware.vmo.plugin.vcloud.VCloudPluginException

  at com.vmware.vmo.plugin.vcloud.VCloudEntityResolver.getEntityByReference(VCloudEntityResolver.java:107)

  at com.vmware.vmo.plugin.vcloud.VCloudPluginFactory.hasChildrenInRelation(VCloudPluginFactory.java:206)

  at sun.reflect.GeneratedMethodAccessor136.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at ch.dunes.vso.sdk.DirectInvoker.invoke(DirectInvoker.java:55)

  at ch.dunes.vso.sdk.SDKDatasourceInvoker.hasChildrenInRelation(SDKDatasourceInvoker.java:136)

  at ch.dunes.vso.sdk.SDKFinder._hasChildrenInRelation(SDKFinder.java:266)

  at ch.dunes.vso.sdk.SDKFinder.hasChildrenInRelation(SDKFinder.java:241)

  at ch.dunes.vso.sdk.ModulesFactory.hasChildrenInRelation(ModulesFactory.java:534)

  at com.vmware.o11n.sdk.EnhancedScriptingSDK.hasChildrenInRelation(EnhancedScriptingSDK.java:104)

  at com.vmware.o11n.service.sdk.SdkModuleServiceImpl.hasChildrenInRelation(SdkModuleServiceImpl.java:66)

  at com.vmware.o11n.service.factory.VcoFactoryFacade.hasChildrenInRelation(VcoFactoryFacade.java:1613)

  at sun.reflect.GeneratedMethodAccessor141.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at com.vmware.o11n.service.security.AccessRightsInterceptor.invoke(AccessRightsInterceptor.java:92)

  at com.vmware.o11n.service.security.AccessRightsInterceptor.invoke(AccessRightsInterceptor.java:83)

  at com.vmware.o11n.service.webremoting.VcoDelegatingWebFacade.invokeOperation(VcoDelegatingWebFacade.java:106)

  at com.vmware.o11n.integration.initialization.VcoFactoryServiceFacadeProxy.invokeOperation(VcoFactoryServiceFacadeProxy.java:86)

  at sun.reflect.GeneratedMethodAccessor119.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)

  at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:196)

  to com.sun.proxy. $Proxy104.invokeOperation (unknown Source)

  at sun.reflect.GeneratedMethodAccessor118.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at org.springframework.remoting.support.RemoteInvocation.invoke(RemoteInvocation.java:205)

  at org.springframework.remoting.support.DefaultRemoteInvocationExecutor.invoke(DefaultRemoteInvocationExecutor.java:38)

  at org.springframework.remoting.support.RemoteInvocationBasedExporter.invoke(RemoteInvocationBasedExporter.java:78)

  at org.springframework.remoting.support.RemoteInvocationBasedExporter.invokeAndCreateResult(RemoteInvocationBasedExporter.java:114)

  at org.springframework.remoting.httpinvoker.HttpInvokerServiceExporter.handleRequest(HttpInvokerServiceExporter.java:73)

  at org.springframework.web.context.support.HttpRequestHandlerServlet.service(HttpRequestHandlerServlet.java:67)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)

  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)

  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

  at net.sf.ehcache.constructs.web.filter.GzipFilter.doFilter(GzipFilter.java:95)

  at net.sf.ehcache.constructs.web.filter.Filter.doFilter(Filter.java:86)

  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)

  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)

  at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:581)

  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)

  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)

  at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:680)

  at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)

  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)

  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)

  at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)

  to org.apache.coyote.AbstractProtocol$ AbstractConnectionHandler.process (AbstractProtocol.java:585)

  to org.apache.tomcat.util.net.JIoEndpoint$ SocketProcessor.run (JIoEndpoint.java:312)

  at java.util.concurrent.ThreadPoolExecutor.runWorker (unknown Source)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (unknown Source)

  at java.lang.Thread.run (unknown Source)

  Caused by: java.lang.reflect.InvocationTargetException

  at sun.reflect.GeneratedMethodAccessor150.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at com.vmware.vmo.plugin.vcloud.VCloudEntityResolver.getEntityByReference(VCloudEntityResolver.java:105)

  ... more than 56

  Caused by: com.thoughtworks.xstream.converters.reflection.ObjectAccessException: javax.xml.bind.JAXBElement.name invalid final field

  at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.validateFieldAccess(PureJavaReflectionProvider.java:149)

  at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:105)

  at com.thoughtworks.xstream.converters.reflection.ReflectionConverter.marshal(ReflectionConverter.java:44)

  at com.thoughtworks.xstream.core.ReferenceByXPathMarshaller.convertAnother(ReferenceByXPathMarshaller.java:36)

  at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:68)

  at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:47)

  at com.thoughtworks.xstream.core.ReferenceByXPathMarshaller.convertAnother(ReferenceByXPathMarshaller.java:36)

  to com.thoughtworks.xstream.converters.reflection.ReflectionConverter$ 1.writeField(ReflectionConverter.java:81)

  to com.thoughtworks.xstream.converters.reflection.ReflectionConverter$ 1.visit(ReflectionConverter.java:59)

  at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:108)

  at com.thoughtworks.xstream.converters.reflection.ReflectionConverter.marshal(ReflectionConverter.java:44)

  at com.thoughtworks.xstream.core.ReferenceByXPathMarshaller.convertAnother(ReferenceByXPathMarshaller.java:36)

  at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:68)

  at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:47)

  at com.thoughtworks.xstream.core.ReferenceByXPathMarshaller.convertAnother(ReferenceByXPathMarshaller.java:36)

  to com.thoughtworks.xstream.converters.reflection.ReflectionConverter$ 1.writeField(ReflectionConverter.java:81)

  to com.thoughtworks.xstream.converters.reflection.ReflectionConverter$ 1.visit(ReflectionConverter.java:59)

  at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:108)

  at com.thoughtworks.xstream.converters.reflection.ReflectionConverter.marshal(ReflectionConverter.java:44)

  at com.thoughtworks.xstream.core.ReferenceByXPathMarshaller.convertAnother(ReferenceByXPathMarshaller.java:36)

  at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:46)

  at com.thoughtworks.xstream.core.ReferenceByXPathMarshallingStrategy.marshal(ReferenceByXPathMarshallingStrategy.java:17)

  at com.thoughtworks.xstream.XStream.marshal(XStream.java:476)

  at com.thoughtworks.xstream.XStream.marshal(XStream.java:466)

  at com.thoughtworks.xstream.XStream.toXML(XStream.java:438)

  at net.sf.beanlib.utils.xml.XmlUtils.toXml(XmlUtils.java:28)

  at net.sf.beanlib.utils.ObjectUtils.deepCopy(ObjectUtils.java:32)

  at com.vmware.vmo.plugin.vcloud.model.ModelHelper.cloneObject(ModelHelper.java:453)

  at com.vmware.vmo.plugin.vcloud.model.Vdc.getInstance(Vdc.java:88)

  ... more than 60

  XStream library must be updated to version 1.4.4 + to make it work with Java 7.

  Try the following (no guarantee that this will work, however)

  1. Stop the server vCO
  2. Locate the plugin files in your deployment of vCO directory (/ app-server/plugins/o11nplugin-vcloud.dar) and save it in a location sure.
  3. Open it with a program that can read zip files (like WinZip, WinRAR, etc.) and go to "lib" folder
  4. There should be a file named 'xstream - 1.x.y.jar'. Most likely, you will see "xstream - 1.3.1.jar' (version 1.3.1)"
  5. You need to replace by ' xstream - 1.4.4.jar' and maybe add a library more - ' xmlpull - 1.1.3.1.jar'. If you can't find these libraries on the Web, I can send them to you by e-mail.
  6. Remove directories temporary tomcat in the vCO directory (/ app-server/work /, / app-server/temp /)
  7. Start the server vCO

  I don't have a working vCloud environment to test, so it cannot work without having to recompile the plugin, but it won't hurt to try.

• vCO5.5: support vCloud Director 5.5?

  Hey guys,.

  the matrix compatibility there is no vCD version which is declared compatible with the latest version of vCO. Is this a bug in the matrix (haha) or in fact a question of fact?

  It's really important to know, because we are currently planning an upgrade of our cloud infrastructure all at the most recent 5.5 product range and, if there is no vCD which is supported by vCO 5.5 we go to 5.1 (or even at all).

  
  

  Thank you

  Igor
  

  There is a vCloud Director 5.5 plugin for the vCO in the making. It will be released later this year.

  Kind regards

  Christophe.

• vCloud Director 5.1 and Leasetimes

  Hi community

  I have 2 questions about Leasetime in vCloud Director.

  -What is sending mail to lease? is this configurable?

  -is it possible to configure this leasemail send not only the owner of VAPP, but also to the people whose configuration is shared?

  Best regards

  MIC

  Hi mic.

  in the web console, it is on the upper right of your screen a link called "Preferences". There you can set the date of the email alert.

  I think that you can't configure it with the web console, you send the email to the user more. But with the vCloud APi, you can get users, the TIME shared with.

• Invalid accept header with PHP SDK 5.1 against 1.5.1 vCloud Director

  In PHP 5.1 SDK samples do not work against 1.5.1 vCloud Director?  Any code that I am trying to write with PHP 5.1 SDK really will work against my vCD 1.5.1?  Or it will fail as the samples?  Is there something I can do for samples and all this work?

  My question seems very similar to http://communities.vmware.com/message/2142668#2142668.  I've had some success with the SDK 1.5 samples against my 1.5.1 vCloud Director.  But when I've upgraded to the PHP 5.1 SDK, all I could get was "invalid accepts header" messages, like this:

  PHP Fatal error: Eception exception 'VMware_VCloud_SDK_Exception' with the message "POST ". https://vCloud.mydomain.edu/API/login failed, return code: 400, error: <? xml version = "1.0" encoding = "UTF-8"? >
  

  " < error xmlns =" http://www.VMware.com/vCloud/v1.5 "stackTrace =" com.vmware.vcloud.api.rest.handlers.exceptions.BadRequestRestApiException: invalid application accepts the header

  at com.vmware.vcloud.api.rest.common.handlers.ErrorHandler.getBadRequestApiException(ErrorHandler.java:71)

  at com.vmware.vcloud.api.rest.common.handlers.ErrorHandler.errorBadRequest(ErrorHandler.java:44)

  at sun.reflect.GeneratedMethodAccessor11639.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

  at java.lang.reflect.Method.invoke(Method.java:597)

  at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:173)

  at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:89)

  at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:133)

  to org.ap in /home/bob/lib/vcloudPHP-5.1.0/library/VMware/VCloud/ServiceAbstract.php on line 178

  After changing VCLOUD_API_VERSION in library/VMware/VCloud/Constants.php of 5.1 to 1.5, I get this:

  PHP Fatal error: Eception exception 'VMware_VCloud_SDK_Exception' with the message "POST ". https://vCloud.mydomain.edu/API/login failed, return code: 401 error,:, request data:
  ' in /home/bob/lib/vcloudPHP-5.1.0/library/VMware/VCloud/ServiceAbstract.php:178
  Stack trace:
  #0 home/bob/lib/vcloudPHP-5.1.0/library/VMware/VCloud/Service.php(114): VMware_VCloud_SDK_Service_Abstract-> message ('https://vcloud...) "(, 200) "
  #1 home/bob/lib/vcloudPHP-5.1.0/samples/login.php(78): VMware_VCloud_SDK_Service-> login ('vcloud.mydomain...', Array, Array)
  #2 {hand}
  lifting in /home/bob/lib/vcloudPHP-5.1.0/library/VMware/VCloud/ServiceAbstract.php on line 178

  A standard API call seems to work:

  curl - test id = true u scripty@system h ' Accept: application / * + xml; " version 1.5 =" https://vCloud.mydomain.edu/API/sessions
  

  Enter password for the user "scripty@system": Home

  
  

  HTTP/1.1 200 OK

  Date: Wednesday, November 28, 2012 17:43:56 GMT

  x vcloud-authorization: rxpTQIswdd15HNz + hZku6BCutGljF5VLUrt0M8x + IGI =

  Set-Cookie: vcloud-token = rxpTQIswdd15HNz + hZku6BCutGljF5VLUrt0M8x IGI plus; Guarantee; Path = /.

  Content-Type: application/vnd.vmware.vcloud.session+xml;version=1.5

  Date: Wednesday, November 28, 2012 17:43:56 GMT

  Content-Length: 1009

  
  

  <? XML version = "1.0" encoding = "UTF-8"? >

  " < session xmlns =" http://www.VMware.com/vCloud/v1.5 "user = org"scripty' = 'System' type="application/vnd.vmware.vcloud.session+xml' href =" https://vCloud.mydomain.edu/API/session/ "" xmlns: xsi = " http://www.w3.org/2001/XMLSchema-instance " xsi: schemaLocation = " http://www.VMware.com/vCloud/v1.5 http://vcloud.the.usg.edu/api/v1.5/schema/master.xsd" > "" "

  "" < link rel = "low" type="application/vnd.vmware.vcloud.orgList+xml" href = " https://vCloud.mydomain.edu/API/org/ "/>

  "" < link rel = "low" type="application/vnd.vmware.admin.vcloud+xml" href = " https://vCloud.mydomain.edu/API/Admin/ "/>

  "" < link rel = "low" type="application/vnd.vmware.admin.vmwExtension+xml" href = " https://vCloud.mydomain.edu/API/admin/extension "/>

  "" < link rel = "low" type="application/vnd.vmware.vcloud.query.queryList+xml" href = " https://vCloud.mydomain.edu/API/query "/>

  "" < link rel = "entityResolver" type="application/vnd.vmware.vcloud.entity+xml" href = " https://vCloud.mydomain.edu/API/entity/ "/>

  < / session >

  Version switching in gross 1.5 to 5.1 API call causes the accept header message invalid, which is not surprising, now that I became familiar with the format and the requirement to accept header.
  For example, can code samples from the SDK 5.1 actually work against 1.5.1 API?
  Thank you!!!

  Hello

  PHP Fatal error: Eception exception 'VMware_VCloud_SDK_Exception' with message "POST https://vcloud.mydomain.edu/api/login failed, return code: 401 error,:, request data:"

  [Rajesh] Seems to me like a problem of password username. As it clearly says 401.

  After changing VCLOUD_API_VERSION in library/VMware/VCloud/Constants.php of 5.1 to 1.5, I get this:

  [Rajesh] SDK users should not change the code in the library. This is a bug with the SDK for not allowing users to change the version of API through the library (connection method accepts the version as well) rather than change in the library.
  Kind regards
  Rajesh Kamal.