Postman collections for DellEMC block storage

Today I will be discussing the details and artefacts of Project Vision. This new Avengers' project leverages Postman's import collection capabilities to provide sample API calls. For more details about the IaC Avengers initiative you can read this other article:

This first release Project Vision provides API examples for the following products:

PowerMaxXtremIOUnityVxFlex (formerly ScaleIO)
The next release will also include a collection for SC (formerly Compellent)

The goal of the project is to help customers of these products to automate day 1 and day 2 operations by looking at handy examples. API reference guides can sometimes be many hundred pages long and take considerable effort to understand. So by looking at some of the most common operational examples one can kickstart coding efforts. Each collection has been built to provide sample calls in these areas:

Gather system and hardware informati…

Configure VxFlex / ScaleIO API with Python

Today I wanted to share with you my contribution to a project I have been working on within the IaC Avengers team. By the way, the Avengers team is an initiative that we have created internally at DellEMC in APJ to create materials and workshops to help customers of our traditional block storage products to fast-track their automation journey. Internal IT teams are under pressure to transform the way their enterprise infrastructure is delivered to the business to match the agility and self service capabilities that their internal customers experience in public cloud. The mission of the IaC Avengers team is to help customers in that journey

The project I am referring to today was dubbed "Project Rocket", like the Racoon in the Avengers movies ... indeed, by choosing Avengers as the team name, we get access to almost unlimited cool project names, specially after the "Endgame" movie!

Project Rocket was a prototype that set dynamic per VM IO limits in VxFlex (formerly…

Getting started with the Kubernetes CSI driver

The purpose of this post is to provide an introduction to “Kubernetes CSI” with examples you can use to build your own projects. Before we start, if you need to build your own Kubernetes cluster to follow along this write up you can follow these instructions. The files for this blog post including the “simplog” Python code are in the “CSI” folder of this GitHub repository

Prior to CSI, Kubernetes provided in-tree (ie as part of the core code) plugins to support volumes but that posed a problem in that storage vendors had to align to the Kubernetes release process to fix a bug or to release new features amongst other problems.

CSI (Container Storage Interface) is a standard for exposing arbitrary block and file storage systems to containerized workloads on Container Orchestration Systems (COs) like Kubernetes. Using CSI, third-party storage providers such as DellEMC can write and deploy plugins exposing new storage systems in Kubernetes withou…

Electronic Nose - eNose

In the previous article I provided details on VeeFarm which was one of the best projects we saw in ANZ Pied Piper 2019 edition and one of the best projects in the history of the program. The program inspired me and others to work together to showcase a great idea and the Pied Piper program itself during our presales conference.

An idea I suggested to enhance VeeFarm was an electronic nose that could be used to detect the optimal ripening of the produce to advise the owner that it is the right time to pick it up the produce. This is an idea I had in the backburner for a while but never found the time to work on. Vee gave me the perfect excuse.

The electronic nose, or eNose for short, is a custom PCB that hosts a range of gas sensors. For the proof of concept, I used the cheap MQ sensors. These are designed mostly for hobbyists and makers and they barely cost $1 per sensor. As one could expect, tweaking and calibrating these sensors it is even harder than the most expensive counterpart…


2019 has been another very hectic year and part of that has been the Pied Piper program again. This year I have run the program at Australia first and then in Japan. In both locations there was a phenomenal vibe and great feedback. During the Australian session we changed the curriculum to learn the new skills required to develop the ASDAC Service Dog app as a team.

We postponed the remaining topics that were not relevant to the app for a month and only then kicked off the traditional personal project competition. The consequence was that that we saw less projects than usual as participants found it hard to remain engaged in spite of their normal commitments. But the projects we got were some of the most mature projects ever, given that at that stage the surviving participants were seasoned in many areas

For example, we saw Jonas Werner’s project, which was the best project of all time. He completed a project so vast that he had to break it down into 4 loosely related discrete projec…

Service Dogs App

I have recently published the following repo in GitHub

This repo contains the code produced by the students of the Pied Piper program that took place in Sydney in June 2019. A total of 14 students from Australia, New Zealand and Japan participated in the program and contributed their code to this project

The Pied Piper program The Pied Piper program goal is to educate DellEMC pre-sales across APJ and Greater China regions in the various technologies that are fuelling the digital transformation such as Cloud Native apps, Agile, DevOps, IoT and analytics/AI. What makes this program different is that engineers learn by doing (approximately 85% of the 5-day workshop is hands-on). By focusing on doing instead of just listening or reading the learning outcomes are much greater

The program gets its name from the Sillicon Valley TV series that portraits a group of young guys in California that found a start-up called Pied Piper. In order to lear more…

Installing Kubernetes in CentOS 7 with no previous experience

Lately I have been working with Kubernetes during the preparation of a new course. In the past, when I needed a Kubernetes cluster I used one of the cloud providers. GCP is specially good for Kubernetes but my trial account run out. Besides, this course requires me to do some things with VMware, so I had to create my own environment a few times in the lab on top of vSphere. During this time, I couldn’t find any other references that worked for me 100% so I decided to write this article with the few tricks that I have learnt

A word of caution, during this process you will be doing things like lowering the security of your virtual machines so that the cluster installs more easily. So please do use this procedure only for development environments and at your own risk
To understand what you are doing it helps to be a little bit familiar with the Kubernetes architecture. You are going to need one Virtual Machine for every not you want in your cluster. There are two types of nodes: Masters…