{"id":2315,"date":"2012-06-05T12:05:30","date_gmt":"2012-06-05T16:05:30","guid":{"rendered":"http:\/\/chriscolotti.us\/?p=2315"},"modified":"2012-06-12T16:00:26","modified_gmt":"2012-06-12T20:00:26","slug":"how-to-handle-some-vcloud-director-challenges","status":"publish","type":"post","link":"https:\/\/chriscolotti.us\/vmware\/how-to-handle-some-vcloud-director-challenges\/","title":{"rendered":"How To Handle Some vCloud Director Challenges"},"content":{"rendered":"

The other day I was sent a link to a 9-slide deck titled “Life before and after vCloud Director”, put\u00a0together by someone I do not know that takes time to point out some specific challenges with vCloud Director, mostly with networking and vShield Edge. \u00a0From what I have learned this deck was\u00a0previously\u00a0circulated and has recently re-surfaced. \u00a0It tries to explain that datacenters after vCloud Director are “Extremely Fragile” due mainly to the fact we use vShield Edge. \u00a0As a vCloud person myself I felt a bit obligated to address some of these for some of you in a more structured approach. \u00a0Some of the noteable points that are presented as “facts” in the slides are as follows:<\/p>\n