All Posts

hello, I made some progress with CSE OVA deployment on my management VLAN. Verified CSE Service status and its active. The first thing i noticed is that system admin service account password showing up in service status which is not good ● cse.service - Cloud Director Container Service Extension Loaded: loaded (/etc/systemd/system/cse.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2022-07-29 09:00:51 UTC; 44min ago Main PID: 1491 (bash) Tasks: 7 (limit: 4693) Memory: 26.4M CGroup: /system.slice/cse.service ├─1491 /bin/bash /root/cse.sh └─1498 /root/vkp -u svc-cse-vcd -p XXXXXXXX -o system -s https://cloud.lab.infra Second i tried creating a new cluster. As part of deployment process a Virtual machine with name EPHEMERAL_TEMP_VM got created and after this i could not see any progress. In CSE Extension, cluster shows in reconciling state. Is it possible to check something in logs at what stage cluster deployment is ?  

hello, I went through provider workflow and under networking pre-req for CSE OVA deployment states: "Provider/system admin can create an Edge gateway, a routed network to connect the container service extension server" It seems that it is expected that CSE Server must be deployed with in an organization in cloud director. However i would like to deploy CSE server in our management area vCenter in a particular VLAN where CSE server can easily connect to VCD load balanced API endpoint.  However when i try to deploy CSE Server in vCenter i dont see any option to specify IP address for CSE Server nor option to specify root password. Is it mandatory to deploy CSE Server in cloud director organization?

Hey Team, can you tell me the login to toubleshoot some staff, root pw? provider workflow i only find "Login to the VM to check if CSE server has started." GET https://{{vcd}}/cloudapi/1.0.0/entityTypes/urn:vcloud:type:vmware:VCDK EConfig:0.5.0 works fine, i try to edit the parameter to my key values but i fail with PUT. if i try the POST he sad allready exists. { "minorErrorCode": "VCD_50006", "message": "[ b849c5a4-0b2b-42cb-8e8d-cad1ffb53bed ] Json processing error.\n - Unexpected character (':' (code 58)): was expecting comma to separate Array entries\n at [Source: (org.apache.cxf.metrics.interceptors.CountingInputStream); line: 116, column: 37] (through reference chain: com.vmware.vcloud.rest.openapi.model.DefinedEntityType[\"schema\"])\n - Unexpected character (':' (code 58)): was expecting comma to separate Array entries\n at [Source: (org.apache.cxf.metrics.interceptors.CountingInputStream); line: 116, column: 37]", "stackTrace": "com.fasterxml.jackson.databind.JsonMappingException: Unexpected character (':' (code 58)): was expecting comma to separate Array entries\n at [Source: (org.apache.cxf.metrics.interceptors.CountingInputStream); line: 116, column: 37] (through reference chain: com.vmware.vcloud.rest.openapi.model.DefinedEntityType[\"schema\"])\n\tat com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:397)\n\tat com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:356)\n\tat com.fasterxml.jackson.databind.deser.BeanDeserializerBase.wrapAndThrow(BeanDeserializerBase.java:1726)\n\tat com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:295)\n\tat com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:156)\n\tat com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:2042)\n\tat com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:1201)\n\tat com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:816)\n\tat org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBodyReader(JAXRSUtils.java:1500)\n\tat org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBody(JAXRSUtils.java:1452)\n\tat org.apache.cxf.jaxrs.utils.JAXRSUtils.processRequestBodyParameter(JAXRSUtils.java:950)\n\tat org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:881)\n\tat org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:215)\n\tat org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:79)\n\tat line 113-116 "serviceAccount": { "type": "object", "required": [ "userOrgName":"system",   best regards

Hi, is there anything special to take care of, when trying to run CSE 3.1.3 and CSE 4.0 beta in parallel on the same Cloud Director Cell? Do we have to consider something special? If it is independent from each other, there should be no problem i guess ...? Anyone tried that? Any hint would be helpful. After using cluster-api/CAPVCD in production with Cloud Director, we would like to thoroughly test the new CSE beta in co-existence with CSE 3.1.3. Thank you! //Marian