vCO5.5: support vCloud Director 5.5?

Similar Questions

• autonomous VMRC console for vcloud Director

  Hello

  I use the stand-alone vmrc available in this link VMware vSphere 5: Private Cloud Computing, server and data center virtualization to open the console vsphere.

  Is it possible to use the vmrc to open vcloud Director console?

  Please help me.

  Thank you.

  Autonomous VMRC is not supported with vCloud Director.

  VMware Remote Console 7.0 Release Notes

  • VMRC does not support vCloud Director, vCloud Air and vRealize of automation of virtual machines.

  Therefore, you should use the console system provided in vCloud Director.

• Error "operations is not supported on the object." when importing .ovf in the vCloud Director 5.5 machine

  I am trying to import a virtual machine (composed of three .mf, hard, .ovf files), when I try to download the VM, it gets downloaded 100% in the catalogs, but gives an error "Cannot create" as condition to the end and when I check the error in detail, it gives me that "operations is not supported on the object.". Checked the Virtaul Center, I get the same error that 'operations is not supported on the object."in the taskbar. Google it a lot but could not find a relevant solution.

  Just for the record I have DRS activated in full auto mode and only in the aggressive State.

  Can someone help me what I can do to remedy the problem.

  There are two parts to the upload.

  5.5 download dialog box represents the progression to the record of transfer vCloud Director of the FVO.  The download method is via the integration of Client plug-in (which uses the OVF tool).

  If the pop-up window can 100% success, I think that the element of the catalogue shows 50% and tries to download files to vCenter/ESXi as an import job.  If the import job fails, then you need to investigate the newspapers of vCenter/ESXi side for more details.

• MCAK for vCloud Director 5.1

  Hello

  We use the most recent MultiCloud since vCloud Director but now look at upgrading to vCenter vCloud Director 5.1.

  I had seen a mention of help soon with version 5.1 of vCD, but did not see if it is available, or in what version it will be.

  Would you be able to give an indication of support for this version, please?

  Kind regards

  Paul

  You should have no problem with the latest version of MCAK vCloud Director 5.1. All the features of the IAC has been verified. What is not yet supported is 5.1 VCD API, so you would not be able to take advantage of the new features of the product/API with the adapter IN VCD (although you can always write your own custom using HTTP requests process to call the new REST API directly).

• What is the smallest model of VAPP available that can be used with vCloud Director?

  Hi all

  I was on the hunt to find the smallest operating system which can be used for demonstration purposes.

  I want to be able to quickly create vApps so a small footprint would be ideal.

  What guys do you use?

  I found this customization for operating system support invited into vCloud Director 5.5 (2058524) | VMware KB

  I always look for a 'micro' distribution that supports customization of comments.

  What is the smallest available?

• 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.

• vCloud Director 5.6

  Hello

  There is a new plug-in for vCloud Director 5.6?

  Thank you

  Hello

  There is no specific vCloud Director Plugin for 5.6 available yet, but the existing plugin 'should' work with 5.6 so the API is backwards compatible.

  Of course, you can't use it to automate the new vCD 5.6 feature.

  If something does not go as planned, I recommend opening a SR with VMware Support.

  See you soon,.

  Joerg

• 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 5.5 device - limits

  Hi all

  Is there any vmware document that specifies the boundaries of the vCloud Director 5.5 device? I know it is trial / PoC and should not be used in a Production Env, but I am interested in a CEP more complex and has been reading here: the vCloud Director unit. VMware vSphere Blog - VMware Blogs limitations:

  Now the vCloud Director device it has some limitations.  As it is only intended for vCloud Director assessments, the scale of the deployment is limited to:

  • A cell of vCloud Director
  • Two vCenter servers
  • 10 VDC organization
  • 100 virtual machines
  • Up to 11 GB of information stored in the database shipped

  Being a former link, I'm sure that is more up-to-date and these limitations have increased, but would like to find something about it.

  I know it supports CentOS, but unfortunately in this PoC I do not have a Windows Server (will also use the vCenter device) and any database.

  Thanks in advance for any comments.

  We produce is no longer the device.  One of the limitations would be so you don't have updates for it.  The limits are generally the same as what you posted.

  CentOS support any really, since the device is produced as a black box.  SuSE or CentOS according to what version it is.  The embedded DB have size limits.

  If you do a CEP more complex, I suggest to use the BIN on CentOS Installer and have at least 2 vCloud Director of cells in a load balanced configuration.  Several cells is something you just can't do with the device.

• vCloud Director 5.5 does not show all comments properties define in EGGS

  Hi all

  I work with a partner who is having a problem after the upgrade to 5.5 VCD

  Problem: vCloud Director 5.5 does not show all comments properties define in the OVA. Same EGGS has worked with vCloud Director 5.1

  Comment: When you create a new TIME by using the model from EGGS, all properties are displayed.

  But even if all of the properties have been shown at the time of the creation, that some have been observed when MISTLETOE was used to view existing comments properties

  Any thoughts?

  Thank you

  Florence

  This is a bug in VCD 5.5.0 and 5.5.1. It will be fixed in 5.5.2. If you can't wait for the fix so there is a /hotpatch. If you file a support request then GSS can give you the /hotpatch

• vCloud Director

  I have just deployed vCloud Director and I set up a port-supported network group pool and he attributed to my Org vDC. I created a paralyzed man with a unique virtual machine, but when I try to turn it on, I get the error below. When I look at the virtual machine, it is connected to the external network. No idea why I can't use the port group supported network I created. ?

  Impossible to deploy the 'VM Network(urn:uuid:3a661866-3556-4747-9216-0c3dd17bec3e)' network.

  com.vmware.vcloud.net.InadequateNetworkBackingException: network pool assigned to this VDC has not all the available networks. Please contact the system administrator.

  -com.vmware.vcloud.net.InadequateNetworkBackingException: network pool assigned to this VDC has not all the available networks. Please contact the system administrator.

  -Pool network assigned to this VDC has not all the available networks. Please contact the system administrator.

  Thank you

  Scott

  org network is like a network of the VAPP/VM can connect to.

  If you do an org network, create a vApp and attach the virtual machine directly to the org network.

  However, if you have only 1 group of ports in the pool of network... you get ONLY 1 network (org or vapp) not both.

  In almost all cases I've seen, they do not use a Port supported group pool... VXLAN or vCNI are the most common options.  for most since a single vLAN = 1000 + networks.

  If you wanted a network to the 'outside world' remove your network pool (separate from the org vdc after all are deleted), create an external network to the system (via the port group)... make an external network in the Organization related to System.  then put a virtual machine on the network it will directly in the external network.

  having a pool of network could do an extra layer.  like having a local network with a gateway to the outside world.

• Cannot create a subscription to notifications vCloud Director (Server.setCustomProperty routine-cursor)

  Hello

  I'm having a problem when you use the workflow of subscription vCloud Director notification.

  When you try to add an AMQP broker using the workflow ' To create a subscription for notifications vCloud Director ' I get the error messages: "Value can not be supported by the custom property".

  The broker and the recipient are created.

  After doing some research, I see that the error occurs at the end of the workflow to the 'Set prop' custom task scriptable during the procurement of:

  If (routingKeyAtt! = null) Server.setCustomProperty (subscription, "routingKey", routingKeyAtt);

  No idea why I can't set this specific CustomProperty?

  no idea who to work around this problem?

  Thank you!

  All - I've updated the package of Notifications for 5.1 file found here: vCloud Director 5.1/5.5 blocking tasks and notification using AMQP package -please try this version, it should now allow the subscription as well as adding custom properties successfully create.

  UPDATED March 11, 2014: update to "Create a vCloud Director notifications subscription" workflow for working with vCloud Director 5.5. The change IS backward compatible with vCloud Director 5.1.

• 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.

• Cannot create the vCloud Director VDC

  Hi all

  Need help with my proof of concept of vCloud implementation Director. running on 5.1 vCloud Director unit. Just to give you an idea, I followed the VMware vCloud Director 5.1 Assessment Guide that we find on the VMware Web site.

  Note: My setup does not contane VXLAN although we have the network VLAN supported to improve network performance.  Of the vExpert mentioned to create a dummy VXLAN right in the vCloud Director and I'm not sure how to do this in vCloud Director console. (I noticed a default VXLAN is already created, I understand vCloud 5.1 has this feature is enabled by default)

  Installation succeeded in creating the Org VDC failed with error 'cannot create the VDC' found this disabling and re activation will release the Red 'X' I think it's false positive because it shows us that everything is perfect even if we get an error message in the logs ' status: error "and with" details: Internal Server Error' find the home images below.

  
  

  " In any case when it comes to download media after having created the catalogue for Org VDC we get the error message cannot complete the operation because the current organization VDC"Demo-Org-VDC"is disabled or is not ready '.

  I also noticed that we get an error message on vcenter Server vcloud (cell) cannot create the folder name already exists check the last my vcenter Server error message.

  also attached the logs in the images below.

  I found two post, which there is not yet of resolution and the other said its solved but does not have the fix.

  Any help to point me in the right direction will be appreciated.

  I will be happy to provide you with newspapers if necessary.

  Thank you

  Ibrahim

  I was not talking about data warehouses.  I refer to the view in the vSphere Client.

  Open the vSphere Client... and go to the computers view models and virtual (c# = Home button at the top, then models and virtual computers)

  In this perspective, there is a number of record Blue icons. Make sure that none have the same name as you describe.

  This is directly related to the error message in the client image vSphere that you took in the original post "cannot create folder. "PNG"

  vCloud produces an error because of something that happens in vCenter.

• 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.