ANZ Pied Piper

Today I wanted to share a video that my colleague and fellow Avenger Masanori Nakamura has created. He is a presales engineer in Japan and is very knowledgeable with our VxFlex product. DellEMC VxFlex is a software defined storage solution that can be deployed either on a 2-tier or as a a hyperconverged architecture. It is typically consumed through appliances or as a fully integrated rack solution (formerly called VxRack Flex) However, since it is a software defined solution, it can be deployed on top of virtually any IaaS. In this case, Masanori-san deploys it on top of GCP.

In today's post I only wanted to notify the addition of 2 new collections to Project Vision: VPLEX PowerOne The VPLEX collection has been kindly contributed by a colleague in the US, "Ankur Patel". It is very comprehensive and it uses variables so that you can use it against multiple systems by simply selecting different environments The PowerOne collection has only been tested with the Glenn Simulator, not with a real system. Hence you will see the IP address is hard coded as the localhost. Visit the Project Vision repo page in GitHub to retrieve the collections: https://github.com/cermegno/Project-Vision You can see more details on how to get the most out of the collections in this article http://anzpiper.blogspot.com/2019/12/postman-collections-for-dellemc-block.html And finally you can see Project Vision in action in this article http://anzpiper.blogspot.com/2020/01/project-vision-in-action.html

Kubernetes can be hard work. The success of distributions like Openshift, Rancher or PKS is due to the promise of making it easier. Still a large part of the user base (in fact this still has the largest market share of any on-prem Kubernetes distro) choose to deploy plain vanilla Kubernetes to take advantage of the super fast-paced innovation However this is usually a path that leads to long hours trying to figure how to make things work and overcome many problems. This is painful even though the community out there is massive. With this in mind one of my colleagues ( Deepak Waghmare ) took upon himself the task of simplifying and streamlining some of these tasks as much as possible. He created an Ansible collection with several roles. This collection is now published in Galaxy The collection is primarily aiming at the the simplification of the installation of the CSI driver in DellEMC storage arrays. All these arrays follow the same pattern by using Helm, so with a littl

The Ansible community is massive, so it is no surprise that version 2.9 came out with more than 3600 modules. This number keeps growing and it is motivating a change in how modules are distributed in the future. To read more about these changes you can read from Jeff Geerling himself However sometimes still you will come across with either: some functionality that hasn't been implemented on a module or a target for which there are no modules What do you do then? You have a few options: create your own module. This can be done in Python and even if you are not a Python guru you can find many tutorials that don't look intimidating at all you use the "shell" or "command" modules to run some other script if your target can be managed through a REST API then you can use the "uri" module REST API's are the basis for many automation tasks nowadays. An advantage of building automation through the API is that the workflow you build