What’s New for the vSphere Client Developer…

Today, the new version of @VMwarevSphere HTML5 Web Client Fling is out with some fantastic additions to the Developer Center!

What’s New for the vSphere Client Developer…

Today, we’re happy to announce the new version of the vSphere HTML5 Web Client Fling and there are some fantastic additions to the Developer Center! The vSphere Client Developer Center is an area built into the main vSphere console. This is an area where automation specialists, developers, and DevOps teams can get immediate access to


VMware Social Media Advocacy

The Hyperconvergence Of Virtual Machines And…

No platform can be everything to everybody

The Hyperconvergence Of Virtual Machines And…

No platform can be everything to everybody. And while there are plenty of organizations that operate at scale who create their own platforms, often using best of breed components, there are some that – perhaps because of the experience of constantly cobbling together systems into platforms – just do not want to do the experimenting and testing and weaving. They want to buy a platform.


VMware Social Media Advocacy

Moving from a Standard to a Distributed virtual switch

In a critical environment (aka production) when you have to deal with networking is alway dangerous.

In my case, I caught the occasion, moving from a 5.5 environment to a 6.5, to move also from vSS to vDS. I don’t know why it wasn’t installed directly a vDS, but that was the vSphere environment that I found.

At the beginning everything seemed simple: there’s a special function in vDS to migrate all at the same moment – uplinks, vmkernel and VMs. dist01

Well… it didn’t work at the first try. So, again, for 3 times, same incuccess: rollback because host loosing connection with vCenter.

I thought it could depend on the previous installation, so I went forward, upgrading to 6.5. My plans were to try again after upgrade. But the result was exactly the same: loosing connection and rollback.

VMware Support, that I consider among the very best of all the vendors we deal with, came in help. During a webex session we tried again the process using the vSphere tool but it didn’t work, as expected. Then trying to move just 1 of the interfaces (we have 2 uplinks per host) but something strange happened: moving on the vDS the vmK dedicated to management couldn’t talk with vCenter (in the same subnet). Support noticed that teaming method was the default one, and modified it in based on IP Hash.
Roll back, trying again: again failing.

Next test was to set the host in MM, so just moving uplinks and vmk. And again, no success. So, last try, but resolutive one: moving the only management vmk of the host in MM to the vDS. This time it worked! Since no VMs run on it I was free to move the remaining vmk and since connection was alive to the vCenter, taking out of MM (but BE AWARE, manual vMotion). Moving one by one the VMs to the host in the new switch, and it was done. Same operation on the others.

I should thank very very much support, the guy was very competent, collaborative and resolutive.

Every upgrade, especially in a complex environment, is never painless.

I want to report my case, upgrading a vSphere environment from 5.5.0U3a to 6.5

The versions were in the upgrade path, so I went ahead relatively confident.
As described, the complexity of the environment kept me focused on every step, prepared accurately before the whole process.
The environment was a vCenter Server Windows backed, supported by an external SSO (also un Windows) and a MSSQL Express, on a third server.

Following the steps on the official upgrade guide, I downloaded the vSphere 6.5 bundle on a separate server dedicated to migration (as it was, since I wanted to move from Windows to the appliance), and copied the migration files on the vCenter Server and the SSO one.

Starting with SSO, I found a problem. Better “THE” problem: as the migration tool stated, migration wasn’t supported on a vSphere 5.5.0U3 “a” installation.
So I had to change my plans: I would download the last verion of 5.5.0U3 (k), and ugrading the Windows machnes, and then, perform the migration as panned before.
Upgrade on SSO went smoothly,, in short time.

The real pain was on the vCenter Server: the upgrade installation screen gives you a list of the steps to complete for a correct installation. First one was SSO, the one that I did just minutes before.

Then, the critical point: Inventory service. Launching it, I noticed that as first operation the installer uninstalled the existing one. And I wasn’t so concerned, since I thought that it was a normal operation. Of course, taking a snapshot was a great idea, idea that I ignored.
The process continued until the last screen: Installation aborted: read the log files. No more info. Reading the logs, I could only understand that it could be a Java problem, but no more. In an old post, the writer found a solution uninstalling the Java machine and reinstalling from scratch, operation that I did. No result, again install aborted, Reboot of course was the first thing, but it didn’t help.

Now my idea was trying to upgrade, again in the windows machines, to vSphere 6.0.
And again, the SSO (now PSC) upgraded with no problem, instead on the vCenter the upgraded stopped because couldn’t find the Inventory Service. And in this case, installation of the service wasn’t separated, but part of the vCenter upgrade.

At this point the only solution that I had was Global Support, hoping in their help since the environment was in EoS by months (years?) and I’ve to say that they understood the situation and were very collaborative. I had some points to follow in order for them to understand better the situation, together with log analysis.

The WebEx didn’t work: I noticed that the operator was looking for the Inventory Service, that was nomore there.
Final solution that they could offer to me: unistall and reinstall the whole vSphere. But it wasn’t an option: this vCenter was connected to a NSX and a vCloud Director: I couldn’t even imagine what could happen (or, better, yes, I could: a disaster).

All these operations took more or less a week, so even if I snapsotted the machines, now they were too old.
From vExpert Slack I had a very important hint: restore a backup. I know, you’ll think now, it was so easy, and me, too stupid to not think at it, but I was a little bit in panic. I mean, everything was working (except for inventory service, that meant to me a very slow process to open the vCenter) so I was thinking how I could make my best reinstalling everything in the less desruptive mode.

So, I proceeded with a restore. The right one was exactly 7 days old, when I uninstalled the seervice. But I also thought that not so many things would change having the DB separated. Maybe networks, so I exported the vDS configuration, but I was also confident having NSX working on it.
That was the key: having a 6.0 PSC, I upgraded also vCenter to 6.0 (of course I didn’t try the 5.5 since it was nonsense, for the version and for the big trouble that made). And everything worked, and also updated because, as stated before, DB was on another server.
From this point migration to 6.5 appliance was really easy.

I want to say thank you once more, to VMware support, very collaborative on a EoS product, and to the vExpert community, that pointed me to the right direction.

I hope this post could help other buddies in my situation.

Titoli di coda…

Ho sempre detestato le mail di commiato inviate a tutti i colleghi indiscriminatamente perché al 90% di essi (se non di più) non interessavano.
Preferisco scrivere un post di questo tipo per tirare una linea tra passato (recentissimo) e presente.

Non voglio semplicemente ricordare e ringraziare “l’Azienda”, si è trattato di un rapporto professionale, quello che ho dato mi è stato retribuito, così come quello che mi è stato retribuito è stato commisurato a quello che ho dato.

Quello che invece resterà indelebile in me sono i rapporti che ho avuto con determinate persone, rapporti non solo professionali.

Vorrei evitare i nomi perchè sono sicuro di dimenticarne qualcuno, ma di due non posso fare a meno di nominarli: Delio e Alessandro, 2 miei responsabili in tempi differenti.

Dal primo ho imparato la pazienza intesa come riflessione piuttosto che impulsività, e l’accuratezza intesa come precisione e programmazione.

Dal secondo, la gestione delle persone, sempre in maniera positiva e propositiva, e la dedizione alla protezione del suo gruppo, nella buona (è facile) e nella cattiva (molto più complicato) sorte.

Questo è il lato professionale, esiste però tutto un ampio aspetto personale che non tratterò qui.

Questa mia esperienza dura ormai da molti anni, ho cambiato diverse casacche restando sempre al mio posto, ho appreso nuove cose, conosciuto persone, imparato a progettare, ho avuto molte occasioni per parlare in pubblico.

Oggi sento che la mia strada deve prendere un’altra direzione. Rimettermi in gioco, continuare a fare errori ma diversi, in un ambiente più snello, con minori risorse ma con l’impagabile vantaggio di poter usare la creatività e l’intuito.

Ringrazio chi mi ha concesso la sua stima, e chi me la sta per concedere.

In bocca al lupo amici, il mondo è piccolo, ci incroceremo presto di nuovo.

 

Migration from VMware NSX for vSphere to NSX-T

Migration from VMware NSX for vSphere to NSX-T

Migration to VMware NSX-T Data Center (NSX-T) is top of mind for customers who are on NSX for vSphere (NSX-V). Broadly speaking, there are two main methods to migrate from NSX for vSphere to NSX-T Data Center: In Parallel Migration and In Place Migration. This blog post is a high-level overview of the above two The post Migration from VMware NSX for vSphere to NSX-T appeared first on Network Virtualization.


VMware Social Media Advocacy

Cloud Assembly VM Guest Management With Ansible…

In this blog post, we focus on Cloud Assembly integration with @Ansible. @VMwareCloud #VMwareCloudManagement

Cloud Assembly VM Guest Management With Ansible…

By Darryl Cauldwell, VMware Solution Architect Advanced Customer Engagement Project Team: Amanda Blevins, Mandy Botsko-Wilson, Carlos Boyd, Darryl Cauldwell, Paul Chang, Kim Delgado, Dustin Ellis, Jason Karnes, Phoebe Kim, Andy Knight, Chris Mutchler, Nikolay Nikolov, Michael Patton, Raghu Pemmaraju vRealize Automation Cloud VMware vRealize Automation Cloud is a product suite comprising of three separate modules,


VMware Social Media Advocacy

Project Pacific – VMworld 2019 Deep Dive Updates

Project Pacific – #VMworld 2019 Deep Dive Updates

Project Pacific – VMworld 2019 Deep Dive Updates

I’m sure most readers will be somewhat familiar with VMware’s Project Pacific at this point. It really is the buzz of VMworld 2019. If I had to describe Project Pacific in as few words as possible, it is a merging of vSphere and Kubernetes (K8s) with the goal of enabling our customers to deploy new, next-gen, distributed, modern applications which may be comprised of container workloads and virtual machine workloads. Not only that, but we also need to provide our customers with a consistent…Read More


VMware Social Media Advocacy

Backed by Research: Certification Results in…

Backed by Research: #Certification Results in Promotions, Raises, and Increased Abilities

Backed by Research: Certification Results in…

If you’ve ever considered becoming VMware certified, you’ve probably already guessed that there are a host of benefits that come with certification. What you may not know is that hard research backs these hunches up. After querying nearly 10,000 credential-holding professionals, Pearson VUE’s 2018 Value of Certification survey found conclusively that earning an industry-recognized certification The post Backed by Research: Certification Results in Promotions, Raises, and Increased Abilities…Read More


VMware Social Media Advocacy

Performance of Apache Spark on Kubernetes…

Performance of Apache Spark on #Kubernetes versus Spark Standalone with a Machine Learning Workload

Performance of Apache Spark on Kubernetes…

Apache Spark is a very popular application platform for scalable, parallel computation that can be configured to run either in standalone form, using its own Cluster Manager, or within a Hadoop/YARN context. A growing interest now is in the combination of Spark with Kubernetes, the latter acting as a job scheduler and resource manager, and The post Performance of Apache Spark on Kubernetes versus Spark Standalone with a Machine Learning Workload appeared first on Virtualize Applications.


VMware Social Media Advocacy