Zsoldier's Tech Blog

Out-GridView Example Summary: This was kind of a fun exercise and helpful considering the NSX plugin kinda blows, in flash client at least.  Have yet to take a look at HTML5 one that was just released.  Was asked if we could output currently configured DFW rules.  Below you will find what I slapped together.  If it's useful to you too, great.  Also, please feel free give me feedback. It will basically give you the following: Rule Number  This is kind of a guess in that it assumes that rules will pull down from API in the correct order at runtime. Rule ID Rule Name Source Destination Service Ports Action appliedTo This script requires the following powershell modules: vmware.powercli powernsx Script:

Summary: One of the cool things w/ NSX is that you can define vCenter Objects as your source and destination targets in NSX's Distributed Firewall (DFW).  On the surface, great idea.  Under the hood, it is still based on IP source and targets.  Only when you decide upon a default deny/deny rule does this become apparent. Quick and Easy: Make sure VM's are running VMware Tools. VM(s) in question is NOT in NSX Exclusion List ESX Agents (aka NSX Partner Integrations) appear to be in exclusion list by default. ESX Agents do NOT show in NSX Exclusion list UI. Use IP Sets if you are a masochist. or if a vendor provides an appliance w/o tools installed. Honestly, IP Sets make the most sense rather than defining vSphere objects.  The reason?  If you deal w/ something like an appliance that can be deleted and recreated easily, a vsphere object rule would break because the original object no longer exists. Details:

Download the app Summary: I'm lazy , frugal , and easily bored .  When the prospect of going to workout comes up, I want someone to tell me what to do when I'm in the gym @ my random time and track my workouts for trending.  Being frugal, paying for a personal trainer is one thing, then I have to schedule time w/ them (laziness).  Personal trainers do satisfy my easily bored problem though w/ new workouts all the time.  This is where Fitbod, I think, is amazing. Laziness, Frugality, and Boredom Solved!: First Fitbod solves my laziness problem by simply being available 24/7.  I don't need to schedule time to meet a trainer @ a gym to get a good strength training workout. Second, Fitbod solves my frugality problem by simply being free.  Although to access additional secondary functions (not absolutely necessary), I would have to pay a monthly or annual fee.  The in-app purchase is fairly cheap, but I was able to get on the Beta program...

Summary: Having python built in on Mac can cause issues when you try to work python code.  One such issue is that VS Code will consistently complain about pylint missing and will attempt to install.  It'll likely fail every time and also show a nice little warning suggesting to upgrade pip to the latest version.  Slight annoyances, but annoying nonetheless. If you've installed Python 3 using brew based on my last post, then this'll be a helpful continuation. Python: Modules installed with PIP3 on Mac not getting installed? Resolution: It's quite simple. Launch Visual Studio Code Code --> Preferences --> Settings In the right pane User Settings, simply add your preferred python path. "python.pythonPath": "/usr/local/bin/python3" brew places a pointer here for you if you followed my last post. Save You can also set your preferred interpreter on-demand rather than statically setting it in your user settings.  See referen...

Summary: I was essentially just trying to import a module for my python3 installation, but found it was not installed.  Typically, you should be able to install it via PIP (PIP3 in Mac case so it would install to 3.x version instead of built-in 2.x version).  It appears to install fine, but it would not appear in my installed modules when calling help("modules").  Then I noticed the problem... Details So in my case, I had python 2.7 and python 3.5 installed via the standard packages provided by python.org.  Nothing wrong with this and very typical, but my tinkering screwed me because I also use brew package installer.  This likely got my pip3 installation messed up and out of sync w/ standard packages installed.  My pip3 pointer was going to a 3.6 version whereas my python3 pointers were going to 3.5.  So, if not obvious, calling pip3 to install modules would only be good for python 3.6. ls -lh /usr/local/bin pip3 --version Now my unde...