You need a regular NSX license - this license is inclusive of vSphere.
If you are within VCPP, this falls inside of the Advanced SP Bundle (7 point) functionality.
↧
Re: VCD networking
↧
Re: VCD networking
Thanks Daniel.I configured the correct NSX licenses.
When im trying to create isolated network within data center,im getting this error.It seems,we need to configure NSX edge "For deployment of NSX Edge appliance, cluster should be prepared and Ready/GREEN"
Thanks,
Manivel RR
↧
↧
Re: VCD networking
When you configure a static IP pool for this network, it wants to deploy an edge gateway that does DHCP on this isolated network. So you should only specify the network CIDR, name & description and let the other fields empty in the create dialog.
↧
Re: VCD networking
Thanks for your reply.It will be very helpful if you please elaborate this, because still im facing some issues.
I came to know that,when we are trying to use vsphere-port group based,it will not use NSX overlay.
Steps followed:-
1) I created a network pool called "testone" with vsphere-port group based.Before that,I created a port group in vCenter under DVS(for that network pool).
2) When i was trying to create a new organization VDCs called "test2",i selected network pool as "testone".Post that, i was not selected anything like "Configure edge gateway" and then completed the new org.VDC wizard.
3) Logged in as test2 vis org.administrator.
4) When i was trying to "Create an isolated network within virtual data center" i have given network CIDR only(Left static pool as empty) but still Im getting the attached error(Error 2 screenshot).
Note:- I have configured NSX licenses only.Apart from that, i was not configured anything from NSX end(like host preparation etc..)
Thanks,
ManivelR
↧
Container Services Extension (CSE) Cluster deployment fails with "VM is not ready to execute scripts"
Hi
For the last few days, I have tried to set up CSE on vCD. And all in all it has been quite straight forward.
I am running into an issue though I was hoping someone has seen before .
We are using CSE 1.2.7 and vCD9.5
Cluster and master node is being created - but fails in the "initializing cluster" part where it aparently should run customization scripts with the error: Unable to execute scripts.
I looks like vmtools are running as per line 2 - but still not able to run the scripts.
when creating the cluster with vcd-cli :
From cse-debug-log:
19-03-27 12:14:13 | cluster:225 - wait_for_tools_ready_callback | DEBUG :: waiting for guest tools, status: vm='vim.VirtualMachine:vm-5869', status=guestToolsNotRunning
19-03-27 12:14:18 | cluster:225 - wait_for_tools_ready_callback | DEBUG :: waiting for guest tools, status: vm='vim.VirtualMachine:vm-5869', status=guestToolsRunning
19-03-27 12:14:34 | cluster:231 - wait_for_guest_execution_callback | DEBUG :: waiting for process 1224 on vm 'vim.VirtualMachine:vm-5869' to finish (1)
19-03-27 12:14:40 | cluster:231 - wait_for_guest_execution_callback | DEBUG :: process [0, <Response [200]>, <Response [200]>] on vm 'vim.VirtualMachine:vm-5869' finished, exit code: 0
19-03-27 12:14:40 | cluster:363 - execute_script_in_nodes | DEBUG :: about to execute script on mstr-bu7s (vm='vim.VirtualMachine:vm-5869'), wait=False
19-03-27 12:14:40 | cluster:390 - execute_script_in_nodes | DEBUG :: [1230]
19-03-27 12:14:40 | cluster:391 - execute_script_in_nodes | DEBUG ::
19-03-27 12:14:40 | cluster:392 - execute_script_in_nodes | DEBUG ::
19-03-27 12:14:40 | cluster:352 - execute_script_in_nodes | DEBUG :: will try to execute script on mstr-bu7s:
#!/usr/bin/env bash
set -e
while [ `systemctl is-active docker` != 'active' ]; do echo 'waiting for docker'; sleep 5; done
kubeadm init --kubernetes-version=v1.10.11 > /root/kubeadm-init.out
mkdir -p /root/.kube
cp -f /etc/kubernetes/admin.conf /root/.kube/config
chown $(id -u):$(id -g) /root/.kube/config
kubectl apply -f /root/weave.yml
19-03-27 12:14:40 | cluster:358 - execute_script_in_nodes | DEBUG :: waiting for tools on mstr-bu7s
19-03-27 12:14:40 | cluster:225 - wait_for_tools_ready_callback | DEBUG :: waiting for guest tools, status: vm='vim.VirtualMachine:vm-5869', status=guestToolsRunning
19-03-27 12:14:42 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:14:47 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:14:51 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:14:55 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:14:59 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:04 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:07 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:11 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:16 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:20 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:24 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:29 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:33 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:37 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:42 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:45 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:50 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:54 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:15:59 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:02 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:07 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:12 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:16 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:20 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:24 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:28 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:32 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:37 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:41 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:45 | cluster:331 - wait_until_ready_to_exec | INFO :: VM is not ready to execute scripts, yet
19-03-27 12:16:47 | broker:535 - create_cluster_thread | ERROR :: Traceback (most recent call last):
File "/home/cseadmin/.local/lib/python3.6/site-packages/container_service_extension/broker.py", line 479, in create_cluster_thread
init_cluster(server_config, vapp, template)
File "/home/cseadmin/.local/lib/python3.6/site-packages/container_service_extension/cluster.py", line 282, in init_cluster
script, nodes)
File "/home/cseadmin/.local/lib/python3.6/site-packages/container_service_extension/cluster.py", line 361, in execute_script_in_nodes
wait_until_ready_to_exec(vs, vm, password)
File "/home/cseadmin/.local/lib/python3.6/site-packages/container_service_extension/cluster.py", line 334, in wait_until_ready_to_exec
raise CseServerError('VM is not ready to execute scripts')
container_service_extension.exceptions.CseServerError: VM is not ready to execute scripts
↧
↧
Re: VCD networking
Any suggestions?
↧
Re: Configuring Cassandra for vCloud Director 9.1: Empty graphs
Hi,
This query can be performed where ? on vCD Postgress DB ? or on CASSANDRA ?
This query can be used for the vCloud Director database (for example, MS SQL or Postgres) to retrieve the metric configuration settings.
Thanks a lot for sharing this information.
↧
What is best way to migrate vApps to new vCloud Director.
Hi All,
I have two vCloud Director infrastructures as you can see at below.
I created same configuration on new vCloud Director. ( External Network, Organization, OrgVDC, OrgVDC Network bla bla..). Configuration is exactly the same,
I added old vCenter to new vCloud Director and i imported vm using "Import from vSphere" option.
But, is this best way or is there another way to migrate this ? Just i wanted to learn what is best way to migrate existing vApp to new vCloud Director.
* You can think that both environment isolated. There is only 1 Gbit network communication in same datacenter.
↧
Re: What is best way to migrate vApps to new vCloud Director.
1. Utilize the adopt a vCenter/VM function that's been around since 8.20 days. Works great and you can drag/drop into the oVDC RP assuming networking is in place. https://www.paluszek.com/wp/2018/10/23/migrate-vms-and-networking-to-vcloud-director-video-walkthrough/
2. Utilize vCloud Availability for Cloud-to-Cloud or 3.0 (when it's GA here shortly). Provides self-service migration, but does require some minimal downtime (power off and power on). Can be done via the tenant or provider.
-Daniel
↧
↧
Migration to vCD 9.7 appliance
I've been fearing them doing this for a while...while I love the idea of a VA for running vCD I always knew it would be a pain to migrate from an existing CentOS deployment to a VA.
Is this going to be possible with the 9.7 release? Is there a workaround? Seems completely rebuilding and then migrating customers over is just going to be a pain.
↧
Re: How to configure multicell vcd LB certificate
You will need to ensure that cloud-console.domain.com is also using SSL Offload. Depending on what you're using for load balancing, you'll need to ensure that it supports doing SSL Offload for websockets connections.
It's important that the console certificates are valid as browsers such as Chrome will not connect to a websocket with a non-valid/trusted certificate (developer console will show this).
We run this as follows:
1. Run internal CA which has a single certificate on all cells which covers the cell and console FQDNs. You could just as easily use a wildcard in this case. The thing to be careful of is that all cells need to use the same internal certificate as this used to sign material that is sent to the client. If your request to the console went to a different cell to than what received the vCD request, things break.
2. Have a public facing SSL (in our case, LetsEncrypt because short-lived certificates are good) handled by the load balancer.
Hope this helps.
↧
Re: REST API - Struggling to customise a VM at point of deployment
I have the same problema here.
Sad about this is that documentation dont say anything about this error.
I can't rename VM using this call on vCLOUD api.
↧
The parameter is not supported in the current context: VmGeneralParamsType
I'm tryng creating VM on the more simple way, but the body below is throwing this error: "The parameter is not supported in the current context: VmGeneralParamsType"
If I remove VmGeneralParams node, I can create a VM, BUT the name of new VM is the same of vappTemplate (public catalogs).
Body:
<RecomposeVAppParams name="Test vApp Gold" xmlns="http://www.vmware.com/vcloud/v1.5" xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1">
<Description>Test vApp</Description>
<SourcedItem>
<Source name="devel" href="https://vmware.XXXXXX.com.br/api/vAppTemplate/vappTemplate-42d3a075-0e47-4093-a76d-40a5d96ba5d9"/>
<VmGeneralParams>
<Name>AppServer-01a</Name>
<Description>Internal Access</Description>
<NeedsCustomization>true</NeedsCustomization>
</VmGeneralParams>
</SourcedItem>
<AllEULAsAccepted>true</AllEULAsAccepted>
</RecomposeVAppParams>
Thanks,
ale,
↧
↧
Re: Configuring blocking tasks notifications vCD9.1 + vRO 7.3.1
I had this too, unfortunately I can't help as I just gave up on it.
↧
Billing and Usage Reporting with vCD
Hello,
we are currently evaluation vCD. We are a bit confused what's VMware strategy if it comes to billing / usage reporting.
There are a lot of differenty ways (vCenter Chargeback, vRealize Business, vROPs PlugIn...) and no one seems to be the golden way.
Our requirement is to gerenate usage reports for each org / org vdc.
We don't need different pricing models because this will be done in our ERP software.
We'd like to report only the usage of the customers based on "service offerings
Possible service offerings
"1GB RAM/hour in PVDC A"
"VPN Uptime/hour in PVDC B"
"Flash Storage used GB/hour im PVDC C"
...
...
What would be the best solution for this requirement?
Kidn Regards,
Marcel
↧
Re: vCD Extender first config error on ip/ui/mgmt/
I had this issue, I just remove the additional information in the URL and just used "/ui/mgmt/" and it worked fine
↧
Re: vCloud Director Extender getting "Error Code 401 Error in creating VC connection with login scheme : SAML and for user :"
I tried this fix - but it still doesn't work... : vCloud Extender + vCenter Server 6.5(win) +PSC(отдельный)
Has no-one else had this issue ?
At the moment I am dead in the water.
↧
↧
Re: vCloud Director Extender getting "Error Code 401 Error in creating VC connection with login scheme : SAML and for user :"
I think I have fixed it...
There are 2 files on the appliance, so SSH onto it and then find them ....
/opt/vmware/mobility-service/conf/mgrconfig.yaml
/opt/vmware/mobility-service/conf/connconfig.yaml
Within these files change entry in the files to the below
enableVcSsoAuthentication: false
Then restart the service : /etc/init.d/mobility-service restart
This worked a treat for me.
↧
Re: Billing and Usage Reporting with vCD
Hi Marcel,
vROps Chargeback for vCD will be our go-forward strategy for customer-facing showback/chargeback billing. While the solution is still evolving, this provides organization/orgVDC billing policies based on your requirements and also available via the API.
However, this is not based on the provider VDC (pVDC) - it will be all based on the organization VDC. Hope this helps.
-Daniel
↧
Use media from Catalog in VCD
Hi
I am trying to import few OVFs into the VCD's catalog. These OVFs are sharing same media file. Is it possible to upload the media file in advance and then try to upload the OVFs? Will it speed up the process of importing the OVFs and creation of vAPP templates in the catalog?
Please confirm.
We are using VCD 8.20.
Thanks.
Best regards
Kuldeep Sharma
↧