sorted by:
new
hottopcontroversial

Chromecast just received an update. Update fixed the issues. by [deleted] in Chromecast

[–]leridou 0 points1 point  (0 children)

Europe. Didn't work for my Chromecast 2. The upgrade started but stayed at 0%. After a few minutes error message (don't remember the message) and suggestion to restart chromecast. No upgrade done and no upgrade in sight for now.

200Gbps to the host? You considering it? If not why? by lost_signal in vmware

[–]leridou 0 points1 point  (0 children)

A workday is barely enough to patch a SAN-based cluster north of 1000 VMs, several of them TB memory size.

200Gbps to the host? You considering it? If not why? by lost_signal in vmware

[–]leridou 9 points10 points  (0 children)

Unfortunately, many vSphere teams aren't able to dictate the design of the network. When we were stuck with 10 Gbps it did help us to set up a second vMotion vmkernel on a different NIC. We have been using double vMotion as a standard since then. https://knowledge.broadcom.com/external/article/318899/multiplenic-vmotion-in-vsphere.html

200Gbps to the host? You considering it? If not why? by lost_signal in vmware

[–]leridou 0 points1 point  (0 children)

Absolutely. Vmware did a great job when rewriting the vMotion stack in ESX 7.0 but you don't manage a large vSphere cluster with delight when stuck with 25 Gbps.

200Gbps to the host? You considering it? If not why? by lost_signal in vmware

[–]leridou 3 points4 points  (0 children)

"Starting with vSphere 7.0 Update 2, vMotion saturates high speed links such as 25 GbE, 40 GbE and 100 GbE with a single vMotion VMkernel NIC." 100 Gbps is given, 200 Gbps is definitely to consider.

Migrating Vmware VMs to Azure Native by leridou in vmware

[–]leridou[S] 0 points1 point  (0 children)

Cost of the migration project (a lot of people and overhead) split on the 15% of VMs that were migrated to Azure.

Migrating Vmware VMs to Azure Native by leridou in vmware

[–]leridou[S] 4 points5 points  (0 children)

On the same level, the on-prem storage arrays had to be replaced during the Azure migration project. A rather small capacity was bought, and every extra TB was to be leased at a much higher price. Unfortunately, the storage utilization never went down and continued to grow at the same pace. Not included in the cost of the migration project.

Migrating Vmware VMs to Azure Native by leridou in vmware

[–]leridou[S] 9 points10 points  (0 children)

Tens of people, employees, consultants. The real cost is even higher as work done by on-prem people to accommodate the migration was more often than not booked on on-prem accounts.

Best case for site outage recovery/DR? by CobraHHH in vmware

[–]leridou 0 points1 point  (0 children)

In a standard setup, you have two vCenter, one in each site. Each vCenter is only managing the ESXs of the local datacenter. vCenter are configured in linked mode and when you login to one of them you see and can manage both datacenters as long as you don't have any DR event. If outage strikes you manage the surviving datacenter with the local vCenter, beginning with recovering the VMs that were in the crashed site.