Istio, mTLS and the OSI layer

I have been playing a lot with Istio and recently tested mTLS encryption. The test, which I describe in this post, really materialized the OSI layer in front of my eyes. which is always interesting how new stuff can dust off your old basic knowledge.

The entire concept of service mesh and Istio is exciting and revolutionary in my view… but just like any new groundbreaking tech, it takes a few cycles to realize how it manifests beyond the papers, blogs and theory, at least for me. So, as I usually do, I share my experiences on this blog and in my sessions with other in the thought that if I can help even one person understand it better I have achieved my goal.
read more

Only I have the solution! and it is…

We live in a truly hyped era. Kubernetes, Docker, Istio, Serverless, PaaS, CaaS, FaaS you name the buzzwords, these words draw all the attention of the Dev/IT worlds, interstingly enough only a small percentage of organizations actually employ these technologies today, in production or even at all.

Like any new tech there are a barriers of knowledge and investment to get in, weighing the cost of moving to these platforms vs the pain it solves is hard to quantify. For each one of these trends and more that I may have forgotten, there is a group of followers who see these solutions as the be-all-end-all solution for every problem conceivable: read more

Going For The Double

I can’t believe i’m writing this post, I have achieved a second VCDX certification (or as it’s being referred to in the community a 2X ūüôā ). This time the design was for cloud (CMA) and it came just one year and some change¬†after I became a VCDX DCV.

Just being a VCDX was a long time career aspiration of mine and I am so grateful I was able to work on the second one.

Short disclaimer – Since I am a VCDX panelist¬†I am forbidden¬†from mentoring¬†candidates through their VCDX process or giving out advice on the design itself, this is so¬†that I won’t¬†give anyone¬†an unfair advantage. I’ll keep this post about my personal experience towards achieving the double and keep the advice about the process.

For this round I again worked with my partner from the first design Mr. Agustin Malanco (@agmalanco) where we designed a vRealize automation (vRA) on top of the previous DCV design.

When we created the DCV design (which was factious just like this one) we intentionally designed it with cloud as  the next phase in mind. This is actually a recommended approach being discussed through the VCDX workshops as well, if you can create the first one planning ahead for the second do it.

That doesn’t mean it wasn’t a lot of work, hell yeah it was!

We spent nights and weekends for about 4 months, working out the design decisions, figuring out our process and installing the system to validate it and create the install guide.

So, here are a few words of advice for anyone going for double :

  • If possible,¬†when¬†you are designing¬†the first VCDX, plan ahead and build the foundation for the second and perhaps even the third.
  • In most cases when you are going for a second VCDX you only need to submit a design, there is no defense though there might be a phone interview that the reviewer will want some¬†clarifications. That means your design¬†will likely to be reviewed very¬†carefully. Make sure your documentation is top notch. Remember, there is no second chance to defend it, after submission that’s it. note:
    • If your first VCDX was for non-vSphere NSX design if you submit for either CMA/DCV/DT design as your second you will need to defend again.
    • For top notch documentation refer to a¬†previous VCDX article I wrote about the subject here.
  • If this is a fictitious design or partially fictitious validate the design by installing it in the lab.
  • This advice is true for the second VCDX as well as the first, if you can work in a team. It worked very well for me and Agustin.
  • read more