Moderator: Moved to vCloud Director

Hi, yes, using the HTML5 interface resolved the issue! Thanks.

I'm trying to use Publish Subscribe to copy some vApps around.  The 3 smaller vApp templates are fine, but the largest is generating an error.

Just curious to see if anyone has seen this sort of thing.

Source vCD Version: 9.5.0.10264774

Destination vCD Version: 9.7.0.14534864

com.vmware.vcloud.api.presentation.service.BadRequestException: Validation failed for the OVF file you provided: The manifest file is too long.

        at com.vmware.ssdc.backend.services.impl.VAppUploadManagerImpl.performOvfContentValidation(VAppUploadManagerImpl.java:3900)

        at com.vmware.ssdc.backend.services.impl.VAppUploadManagerImpl.handleContentUploaded(VAppUploadManagerImpl.java:3109)

        at com.vmware.ssdc.backend.services.impl.VAppUploadManagerImpl.handleUploadBody(VAppUploadManagerImpl.java:1996)

        at com.vmware.ssdc.backend.services.impl.VAppUploadManagerImpl.handleUpload(VAppUploadManagerImpl.java:1902)

        at com.vmware.ssdc.backend.services.impl.VAppUploadManagerImpl.executeTask(VAppUploadManagerImpl.java:4817)

        at com.vmware.vcloud.backendbase.management.system.TaskActivity$ExecutePhase$1.doInSecurityContext(TaskActivity.java:652)

        at com.vmware.vcloud.backendbase.management.system.TaskActivity$ExecutePhase$1.doInSecurityContext(TaskActivity.java:647)

        at com.vmware.vcloud.backendbase.management.system.SecurityContextTemplate.executeForOrgAndUser(SecurityContextTemplate.java:43)

        at com.vmware.vcloud.backendbase.management.system.TaskActivity$ExecutePhase.execute(TaskActivity.java:654)

        at com.vmware.vcloud.backendbase.management.system.TaskActivity$ExecutePhase.invokeInner(TaskActivity.java:550)

        at com.vmware.vcloud.backendbase.management.system.TaskActivity$TaskActivityBasePhase.invoke(TaskActivity.java:301)

        at com.vmware.vcloud.activity.executors.ActivityRunner.runPhase(ActivityRunner.java:175)

        at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:112)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

        at java.util.concurrent.FutureTask.run(FutureTask.java:266)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)

We are no longer able to create new tenant networks after the 10.0.01 upgrade.  We can create the tenant org and the tenant edges.  But all attempts at a routed network will fail.

In the GUI we see the error "realization failed".   I do see this error in the logs on the nodes.  I have of course opened a ticket with VMWare but we are hoping for a any clues sooner than VMWare support tends to respond to tickets.

Anyone else seeing this?

- The input request is invalid.

- XStream unmarshalling exception; nested exception is com.thoughtworks.xstream.converters.ConversionException:

---- Debugging information ----

cause-exception     : com.thoughtworks.xstream.security.ForbiddenClassException

cause-message       : com.vmware.vshield.vsm.vdn.dto.HardwareGatewayBindingDto

class               : com.vmware.vshield.vsm.vdn.dto.VirtualWireDto

required-type       : com.vmware.vshield.vsm.vdn.dto.VirtualWireDto

converter-type      : com.thoughtworks.xstream.converters.reflection.ReflectionConverter

line number         : 2

class[1]            : com.vmware.vshield.vsm.dto.DataPage

class[2]            : com.vmware.vshield.vsm.vdn.dto.VirtualWiresDto

version             : not available

-------------------------------

-

---- Debugging information ----

cause-exception     : com.thoughtworks.xstream.security.ForbiddenClassException

cause-message       : com.vmware.vshield.vsm.vdn.dto.HardwareGatewayBindingDto

class               : com.vmware.vshield.vsm.vdn.dto.VirtualWireDto

required-type       : com.vmware.vshield.vsm.vdn.dto.VirtualWireDto

converter-type      : com.thoughtworks.xstream.converters.reflection.ReflectionConverter

line number         : 2

class[1]            : com.vmware.vshield.vsm.dto.DataPage

class[2]            : com.vmware.vshield.vsm.vdn.dto.VirtualWiresDto

version             : not available

-------------------------------

Hi All,

Can anyone help me on this topic?

When i use this method getVMWHosts() in vRO It cannot retrieve ESXI hosts from vcloud director and gives the following error

var vcdHosts = System.getModule("com.vmware.library.vCloud.Host").getHosts();

System.log("the hosts are : " +vcdHosts)

entities = new Array();

for each (var vcdHost in vcdHosts) {

    entities = vcdHost.toAdminObject().toAdminExtensionObject().getVMWHosts()

    System.log("the number of host in vcd is : "+entities)

}

Error in (Workflow:vclvmID / Scriptable task (item1)#5) VMWSystemHostRefs NOT found for MYUSERNAME@System. [ fcfdd6e3-ad90-4735-b2b6-fd512b95a578 ] class java.lang.NullPointerException

Thank you

Hi guys,

I'm experiencing an issue when I try to upload a huge ISO media file to a catalog, due to the fact the whole operation is quite extensive in time so I reach some sort of time limit somewhere and I try to figure out which one exactly. All settings defined in vCloud Director Administration/General/Timeouts look good, e.g. big numbers enough, allowing for a transfer or a session to not be interrupted if less than 480 minutes for example.

The problem occurs at the end of the 2nd stage transfer (the import step), once the file is getting moved from /opt/vmware/vcloud-director/data/transfer to the actual location on the NFS storage I use.

That last part of the transfer seems to take more than 60 minutes of time and for me looks like the reason so it doesn't complete successfully. The exact time passed as per the logs is  3,798,255 ms, which means about 63 minutes or just over 60, so the operation fails. Just trying to understand where's that 60 minutes (or other threshold) defined and how I can lift it up a bit.

The exact error message is:

Session has been opened for too long: storage-fabric-activity-pool-1353. Opened since: 3/23/20 3:09 AM

vcloud-container-debug.log.9:2020-03-23 04:12:52,432 | WARN     | storage-fabric-activity-pool-1353 | Conversation                   | Session has been opened for too long: storage-fabric-activity-pool-1353. Opened since: 3/23/20 3:09 AM. [Conversation: 4fb93070-c551-4782-a56d-5bdb25ac6a17, transaction fcec9d60-4029-4fb8-ae41-36b5b8880138, transactionDepth: 1] | requestId=eea900e4-2f7b-444c-9621-bc646909b85e,request=POST https://xxx.somecloud.com/api/catalog/02ef3f7d-21b6-4b3d-8dea-070be42c02ba/action/upload,requestTime=1584929847356,remoteAddress=10.51.39.252:28472,userAgent=Ruby,accept=application/*+xml;version 29.0 vcd=112e34af-125e-4a5e-9b10-4ed45ae72455,task=b92d8d4f-a321-4e12-9889-cb046e2e354e activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:b92d8d4f-a321-4e12-9889-cb046e2e354e) activity=(com.vmware.ssdc.backend.services.impl.CreateMediaActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243) activity=(com.vmware.vcloud.fabric.storage.media.impl.CreateFromImportActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243)

vcloud-container-debug.log.9:2020-03-23 04:12:52,486 | DEBUG    | storage-fabric-activity-pool-1353 | CreateFromImportActivity       | [Activity Execution] Partial failure during Activity execution - Handle: urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243, Current Phase: CreateFromImportActivity$CopyPhase | requestId=eea900e4-2f7b-444c-9621-bc646909b85e,request=POST https://xxx.somecloud.com/api/catalog/02ef3f7d-21b6-4b3d-8dea-070be42c02ba/action/upload,requestTime=1584929847356,remoteAddress=10.51.39.252:28472,userAgent=Ruby,accept=application/*+xml;version 29.0 vcd=112e34af-125e-4a5e-9b10-4ed45ae72455,task=b92d8d4f-a321-4e12-9889-cb046e2e354e activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:b92d8d4f-a321-4e12-9889-cb046e2e354e) activity=(com.vmware.ssdc.backend.services.impl.CreateMediaActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243) activity=(com.vmware.vcloud.fabric.storage.media.impl.CreateFromImportActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243)

vcloud-container-debug.log.9:2020-03-23 04:12:52,503 | DEBUG    | storage-fabric-activity-pool-1353 | CreateFromImportActivity       | [Activity Execution] Finished - Handle: urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243, Current Phase: CreateFromImportActivity$CopyPhase | requestId=eea900e4-2f7b-444c-9621-bc646909b85e,request=POST https://xxx.somecloud.com/api/catalog/02ef3f7d-21b6-4b3d-8dea-070be42c02ba/action/upload,requestTime=1584929847356,remoteAddress=10.51.39.252:28472,userAgent=Ruby,accept=application/*+xml;version 29.0 vcd=112e34af-125e-4a5e-9b10-4ed45ae72455,task=b92d8d4f-a321-4e12-9889-cb046e2e354e activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:b92d8d4f-a321-4e12-9889-cb046e2e354e) activity=(com.vmware.ssdc.backend.services.impl.CreateMediaActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243) activity=(com.vmware.vcloud.fabric.storage.media.impl.CreateFromImportActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243)

vcloud-container-debug.log.9:2020-03-23 04:12:52,503 | DEBUG    | storage-fabric-activity-pool-1353 | CreateFromImportActivity       | [Activity Execution] Phase CopyPhase completed in 3,798,255 ms. - Handle: urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243, Current Phase: CreateFromImportActivity$CopyPhase | requestId=eea900e4-2f7b-444c-9621-bc646909b85e,request=POST https://xxx.somecloud.com/api/catalog/02ef3f7d-21b6-4b3d-8dea-070be42c02ba/action/upload,requestTime=1584929847356,remoteAddress=10.51.39.252:28472,userAgent=Ruby,accept=application/*+xml;version 29.0 vcd=112e34af-125e-4a5e-9b10-4ed45ae72455,task=b92d8d4f-a321-4e12-9889-cb046e2e354e activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:b92d8d4f-a321-4e12-9889-cb046e2e354e) activity=(com.vmware.ssdc.backend.services.impl.CreateMediaActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243) activity=(com.vmware.vcloud.fabric.storage.media.impl.CreateFromImportActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243)

vcloud-container-debug.log.9:2020-03-23 04:12:52,503 | DEBUG    | storage-fabric-activity-pool-1353 | CreateFromImportActivity       | [Activity Execution] Activity completed in 3,798,255 ms. - Handle: urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243, Current Phase: CreateFromImportActivity$CopyPhase | requestId=eea900e4-2f7b-444c-9621-bc646909b85e,request=POST https://xxx.somecloud.com/api/catalog/02ef3f7d-21b6-4b3d-8dea-070be42c02ba/action/upload,requestTime=1584929847356,remoteAddress=10.51.39.252:28472,userAgent=Ruby,accept=application/*+xml;version 29.0 vcd=112e34af-125e-4a5e-9b10-4ed45ae72455,task=b92d8d4f-a321-4e12-9889-cb046e2e354e activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:b92d8d4f-a321-4e12-9889-cb046e2e354e) activity=(com.vmware.ssdc.backend.services.impl.CreateMediaActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243) activity=(com.vmware.vcloud.fabric.storage.media.impl.CreateFromImportActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243)

vcloud-container-info.log:2020-03-23 04:12:52,432 | WARN     | storage-fabric-activity-pool-1353 | Conversation                   | Session has been opened for too long: storage-fabric-activity-pool-1353. Opened since: 3/23/20 3:09 AM. [Conversation: 4fb93070-c551-4782-a56d-5bdb25ac6a17, transaction fcec9d60-4029-4fb8-ae41-36b5b8880138, transactionDepth: 1] | requestId=eea900e4-2f7b-444c-9621-bc646909b85e,request=POST https://xxx.somecloud.com/api/catalog/02ef3f7d-21b6-4b3d-8dea-070be42c02ba/action/upload,requestTime=1584929847356,remoteAddress=10.51.39.252:28472,userAgent=Ruby,accept=application/*+xml;version 29.0 vcd=112e34af-125e-4a5e-9b10-4ed45ae72455,task=b92d8d4f-a321-4e12-9889-cb046e2e354e activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:b92d8d4f-a321-4e12-9889-cb046e2e354e) activity=(com.vmware.ssdc.backend.services.impl.CreateMediaActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243) activity=(com.vmware.vcloud.fabric.storage.media.impl.CreateFromImportActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243)

vcloud-container-info.log:2020-03-23 04:12:52,408 | ERROR    | storage-fabric-activity-pool-1355 | FutureUtil                     | Future /vcd01/media/1992ea7e-8949-46d4-b67d-da866dd13d28/cb937566-3564-419e-8c4f-2cdb1ca9943f/media-37441614-ac3f-4e88-8ee3-d57ba6d170e7.iso failed | requestId=eea900e4-2f7b-444c-9621-bc646909b85e,request=POST https://xxx.somecloud.com/api/catalog/02ef3f7d-21b6-4b3d-8dea-070be42c02ba/action/upload,requestTime=1584929847356,remoteAddress=10.51.39.252:28472,userAgent=Ruby,accept=application/*+xml;version 29.0 vcd=112e34af-125e-4a5e-9b10-4ed45ae72455,task=b92d8d4f-a321-4e12-9889-cb046e2e354e activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:b92d8d4f-a321-4e12-9889-cb046e2e354e) activity=(com.vmware.ssdc.backend.services.impl.CreateMediaActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243) activity=(com.vmware.vcloud.fabric.storage.media.impl.CreateFromImportActivity,urn:uuid 2efd67b4-bcee-45dd-b9b0-6924faca9243) activity=(com.vmware.vcloud.fabric.storage.copy.impl.UploadDatastoreFilesActivity,urn:uuid:4fc243d5-6ef8-4266-957b-63c32b7e44dd)

vcloud-container-info.log:2020-03-23 04:12:52,432 | WARN     | storage-fabric-activity-pool-1353 | Conversation                   | Session has been opened for too long: storage-fabric-activity-pool-1353. Opened since: 3/23/20 3:09 AM. [Conversation: 4fb93070-c551-4782-a56d-5bdb25ac6a17, transaction fcec9d60-4029-4fb8-ae41-36b5b8880138, transactionDepth: 1] | requestId=eea900e4-2f7b-444c-9621-bc646909b85e,request=POST https://xxx.somecloud.com/api/catalog/02ef3f7d-21b6-4b3d-8dea-070be42c02ba/action/upload,requestTime=1584929847356,remoteAddress=10.51.39.252:28472,userAgent=Ruby,accept=application/*+xml;version 29.0 vcd=112e34af-125e-4a5e-9b10-4ed45ae72455,task=b92d8d4f-a321-4e12-9889-cb046e2e354e activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:b92d8d4f-a321-4e12-9889-cb046e2e354e) activity=(com.vmware.ssdc.backend.services.impl.CreateMediaActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243) activity=(com.vmware.vcloud.fabric.storage.media.impl.CreateFromImportActivity,urn:uuid:2efd67b4-bcee-45dd-b9b0-6924faca9243)

Cheers!

Hi,

I have deployed vCloud Director 10.0.1 and NSX-T 2.5.1 versions. I have configured NSX-T according to vCD requirements without any problem.

I have added vCenter and NSX-T to vCloud Director as it should be. ( I've done this many times before...). I have created network pool as GENEVE. NSX-T and vCenter appears as "Connected" on vCloud Director. That means that there is no any misconfiguration.

The problem is ;

I'm trying to create Provider VDC by select Cluster, Network pool, Storage Profile etc.. But, creation process is stucking as "Busy" for hours on end, and vCenter status is changing as "Connecting" on vCloud Director. I can cancel the creation task after the restart of vCD services via SSH. Then, vCenter status is changing as "Connected" after task cancellation.

What am i missing ?

Thanks.

I want to export a list of all vApps and the users with their permissions.

This works:

$CIUser = Get-CIUser -Org "MyOVDC"

$CIPerm = Get-CIAccessControlRule -user $CIUser

$CIPerm

Output:

So now I want to script this to cycle through each vApp and list each user and their permission, so I created this script:

$Report = foreach ($CIUser in Get-CIUser -Org "MyOVDC")

    {

    $CIPerm = Get-CIAccessControlRule -user $CIUser

    New-Object PSOBject @{

        Name = $CIPerm.User

        Entity = $CIPerm.Entity

        AccessLevel = $CIPerm.AccessLevel

        }

    }

$Report | Export-Csv "Report.csv"

But the output is:

Can someone help me to fix my script so that I can get the required output?

Can you share the logs during creation process of PVDC - vcloud-container-debug.log(/opt/vmware/vcloud-director/logs) . Also what is the version of VCSA you are running?

jnivoit: Thanks It works for both adminVApp as well as non Admin -vApp.

Hi,

vCD 10, vRO 7.6

I have created a workflow that creates organizations in vCD. When I run a workflow published in vCD, it is not executing.

Executing Workflow message pops up and nothing happens, like below.

The same workflow running directly on vRO is done correctly and finishes its work by setting up an organization.

Below is the log from the vCD cell during workflow. An error is marked in red,  when I press FINISH and the workflow should be run but nothing happens.

/opt/vmware/vcloud-director/logs/2020_03_31.request.log

10.50.1.1 - - [31/Mar/2020:10:11:47 +0200] "GET https://10.50.1.60/cloudapi/workflows/urn:vcloud:serviceItem:dd9d99ca-e2d5-44bb-8c80-edb170c8126b/presentation HTTP/1.1" 200 5401 "https://vcd.lab.domain.pl/provider/libraries/service-items" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" 309

10.50.1.1 - - [31/Mar/2020:10:11:47 +0200] "POST https://10.50.1.60/cloudapi/workflows/urn:vcloud:serviceItem:dd9d99ca-e2d5-44bb-8c80-edb170c8126b/presentation/instances HTTP/1.1" 200 4806 "https://vcd.lab.domain.pl/provider/libraries/service-items" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" 469

10.50.1.1 - - [31/Mar/2020:10:11:48 +0200] "PUT https://10.50.1.60/cloudapi/workflows/urn:vcloud:serviceItem:dd9d99ca-e2d5-44bb-8c80-edb170c8126b/presentation/instances/02a980fd-e59b-4a03-8c01-a4a19f9af65e HTTP/1.1" 200 4838 "https://vcd.lab.domain.pl/provider/libraries/service-items" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" 572

10.50.1.1 - - [31/Mar/2020:10:11:49 +0200] "GET https://10.50.1.60/cloudapi/vro/servers/urn:vcloud:vroServer:6579939c-41ef-4b23-86b2-8368bacbb524/sdkObjects/vCloud:Host HTTP/1.1" 200 376 "https://vcd.lab.domain.pl/provider/libraries/service-items" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" 124

10.50.1.1 - - [31/Mar/2020:10:11:53 +0200] "GET https://10.50.1.60/api/query?type=adminTask&format=records&page=1&pageSize=50&filter=startDate=gt=2020-03-30T20:11:52.766Z&sortDesc=startDate&links=true HTTP/1.1" 200 1955 "https://vcd.lab.domain.pl/provider/libraries/service-items" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" 15

10.50.1.1 - - [31/Mar/2020:10:11:59 +0200] "PUT https://10.50.1.60/cloudapi/workflows/urn:vcloud:serviceItem:dd9d99ca-e2d5-44bb-8c80-edb170c8126b/presentation/instances/02a980fd-e59b-4a03-8c01-a4a19f9af65e HTTP/1.1" 200 5009 "https://vcd.lab.domain.pl/provider/libraries/service-items" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" 574

10.50.1.1 - - [31/Mar/2020:10:12:00 +0200] "PUT https://10.50.1.60/cloudapi/workflows/urn:vcloud:serviceItem:dd9d99ca-e2d5-44bb-8c80-edb170c8126b/presentation/instances/02a980fd-e59b-4a03-8c01-a4a19f9af65e HTTP/1.1" 200 5009 "https://vcd.lab.domain.pl/provider/libraries/service-items" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" 538

10.50.1.1 - - [31/Mar/2020:10:12:00 +0200] "POST https://10.50.1.60/cloudapi/workflows/urn:vcloud:serviceItem:dd9d99ca-e2d5-44bb-8c80-edb170c8126b/executions HTTP/1.1" 500 11151 "https://vcd.lab.domain.pl/provider/libraries/service-items" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" 359

10.50.1.1 - - [31/Mar/2020:10:12:03 +0200] "GET https://10.50.1.60/api/query?type=adminTask&format=records&page=1&pageSize=50&filter=startDate=gt=2020-03-30T20:12:02.766Z&sortDesc=startDate&links=true HTTP/1.1" 200 1955 "https://vcd.lab.domain.pl/provider/libraries/service-items" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" 16

Local IP vCloud Director is 10.50.1.60, gateway 10.50.1.1. vCloud Director is behind NAT, when I run localy workflow (form the same subnet) everything is the same.

any idea?

Sounds like a bug to me, it usually means we're holding a DB transaction open while processing bytes (which we should not be doing), and then run into the DB transaction timeout.

Hi,

I setup a vdc with lot of VM Sizing Policies in vCD 10.0.0.1

My issue start at 11 computePolicies.

In the HTML5 ui, when I want to create a VM with vdc\Compute\VirtualMachine\NEW VM, strange things happened in content-modal inside the VM Sizing dropdown.

First some policies don't show their description.

Secondly, if you setup some VM Placement Policies , they can appear in the VM Sizing dropdown.

My browser sent 2 queries:

Query 1)      To get the vdc vdcComputePolicyReference array.

               GET /api/vdc/33b1f2d0-39d0-416c-9e67-46941d35f7ad/computePolicies

Query 2)   To get details of  each computePolicies (with vdcComputePolicyReference result) :

          GET /cloudapi/1.0.0/vdcComputePolicies?page=1&pageSize=10&filter=(id==urn:vcloud:vdcComputePolicy:6a3f9a79-ebfb-45b8-b714-8d8786321839,id==urn:vcloud:vdcComputePolicy:518f3d50-9d71-40ac-af79-d39881c1e26a,id==urn:vcloud:vdcComputePolicy:7656d89e-4428-4fff-9c86-13335924a971,id==urn:vcloud:vdcComputePolicy:53e38bda-c60b-4a7a-9968-5503f4ef2c17,id==urn:vcloud:vdcComputePolicy:3e5932b5-dd16-4f81-8106-bf8cde1e7a51,id==urn:vcloud:vdcComputePolicy:e1ca0b16-3760-4ffd-88d2-1170bd0f82c8,id==urn:vcloud:vdcComputePolicy:2e2ecf90-886d-44b5-8b68-07e70b55312a,id==urn:vcloud:vdcComputePolicy:acf9568a-5ba8-4e19-a26b-0e79398178a9,id==urn:vcloud:vdcComputePolicy:b396b08e-ede8-4d65-a9c9-1276e05b182c,id==urn:vcloud:vdcComputePolicy:b7027851-9399-483d-9f96-2db8690f8f8b,id==urn:vcloud:vdcComputePolicy:0cb6b407-1d9a-46cf-b54a-645f98321231)&links=true

     Result:

     {

          "resultTotal":11,

          "pageCount":2,

          "page":1,

          "pageSize":10,

          "associations":null,

I think that angular code miss to follow "page 2" that contains details of other computePolicies.

So these policies don't have description and isSizingOnly attribute value.

Hi there guys, quick question,

does anyone know if possible to find and OVA from rabittMQ or a docker container image of this? or just if there is a procedure to of units/bootstrap scripts in order to create one? in this I would ask like this there is an existing effort of Rabbit MQ ova, or docker image or a systemd container that you know that can be used for a cell of VCD?

any guidance will be very very appreciated by this dog.

thanks, so much in advance!

Had anyone cross with compliance error in vCD 10.0?

Is there any description what would happen when we hit "Make VM Compliant" button?

What hardware settings are being prioritazed vCenter or vCloud Director? What if we have different storage policies onto both of software?

Description of the known issue below:

vCloud Director 10.0 for Service Providers Release Notes

When you change the  reservation guarantee values of a VDC, the existing VMs are not updated accordingly even after a reboot

If you have a flex organization VDC with the system default policy and powered-on virtual machines on that VDC are with the default sizing policy, when you increase the resource guarantee value of the VDC, the resource reservation for the existing VMs is not updated and they are also not marked as non-compliant. The issue occurs also when you convert a legacy VDC allocation model to a flex allocation model and the existing VMs become non-compliant with the new default policy of the flex organization VDC after the conversion.

Workaround:

1. To display the non-compliant VMs in the vCloud Director UI, perform an explicit compliance check against the VMs by using the vCloud API.
2. To reapply the policy and reconfigure the resource reservations, in the vCloud Director Tenant Portal, click Make VM Compliant for a non-compliant VM.

General error:

1. One VM with two disks in different storage policies (Gold and Bronze Storage Policy) both disks in vCenter compliant to SP.

2. When i change the parameters of the VM i get an error:

• One or more exceptions have occurred - The operation failed because no suitable resource was found. Could not find a suitable datastore in hub "moref://95-*-0a/ResourcePool#resgroup-8"; cause(s): There is no usable datastore. Cannot use datastore [vcId=95-*-0a, moref=datastore-19] for subject [type:VIRTUAL_MACHINE, URI:44-*-ac] because the container does not support storage policy Gold Storage Policy.
• Cannot use datastore [vcId=95-*-0a, moref=datastore-214] for subject [type:VIRTUAL_MACHINE, URI:44-*-ac] because the container does not support storage policy Gold Storage Policy. Cannot use datastore [vcId=95-*-0a, moref=datastore-200] for subject [type:VIRTUAL_MACHINE, URI:44-*-ac] because the container does not support storage policy Gold Storage Policy. Cannot use datastore [vcId=95-*-0a, moref=datastore-22] for subject [type:VIRTUAL_MACHINE, URI:44-*-ac] because the container does not support storage policy Gold Storage Policy.

3. Usable datastore in correct storage policies (gold and bronze).

vCloud Director 10, vCenter 6.7.

how to fix this?

Hi all,

Has anybody connected vCD 10 to VMware Cloud Assembly, I currently have a trial but I do not see an option to connect these under cloud accounts. I have seen a video in the learning zone which states this is possible.

Thanks,

Lee

I've seen this behaviour when the pVDC being created spans different vCenter datacenters. Logs showed that NSX-t manager would try to insert some duplicate records into its database and fail. IIRC I had to exclude the second DC nodes from the transport zone (either VLAN or OVERLAY or both) to workaround the problem.

Hi everyone,

I've been trying to create an Edge Gateway (Tier-1 Gateway in terms of NSX-t) in a VDC managed by NSX-t using vCD API (v33.0). I've been experimenting with the request body for quite a while but all my attempts fail with a 500 error and a stackTrace without any meaningful explanation (see nullpointer.err attached for the full trace). vCD debug logs just copy the same message. I'm attaching a request body (modified for nsx-t case) with which I'm able to create an Edge Gateway in a VDC managed by NSX-v without any problem ("edgeGatewayServiceConfiguration" section is skipped purposely as not related).

vCD API documentation does not say anything about the NSX-t case, so I assume this is likely not supported. How do we create edge gateways via API then?

Environment: vCD v10, NSX-t v2.5.1, VCSA v6.5

Hi ,

On vCloud Director 10 you can customize the system branding as well as per tenant .

Check the doc.vmware.com

I'm struggling to change system branding. all GET request works .

PUT requests return error: