HA! Tonight was a pretty rewarding and humbling experience for myself. I was fortunate enough to lead a team at the VMworld Hackathon. Only, it didn’t start out as I had planned. While I knew that signups for my team was low, I did not expect to go solo. Not one of the folks who signed up for team #SweaterVester showed. One guy even sat down and started to set up his laptop, as we were talking he learned he was at the wrong table….. DOH! lol
The good news (I think) is that I earned a new nickname, ‘The lone Ranger”. The bad news, well there is none. I had a wonderful time. I cannot thank the organizers, participants and judges enough for all of their kind words and support during and after the event. It’s an awesome experience and I wasn’t going to let a lack of participation from other ruin my time!
I started out with some pretty far reaching goals, but quickly adjusted them down to work I believed I could complete during the event. At the end of the night, I was able to demo a brand new working feature to my OpenSource Project XesterUI. It was very rewarding to be able to complete the work in a short amount of time, and be able to demo the work live in front of a fairly intimidating group. I also found about 5 or 6 bugs, but those will have to wait until after VMworld.
If you want to learn more about the project I was working on, you can check out XesterUI on Github. Additionally on Thursday at 11:45 I have a vBrownBag presentation (located in the VMvillage) to talk about more of the features and details that will help you understand what this tool can do for you, your organization, and your vSphere environment.
A Very special thanks to Lily Chang, William Lam, Alan Renouf, and Chris Wahl for their kind words and encouragement this evening. This is by far one of my favorite events at VMworld! Food, Friendly competition, great conversations, and Beer. What more could you ask for?
While I didn’t win 1st place…… I did get to take home two Echo Dots! Which I will put to good use!
Thank you for your patience as I tried to find the lowest price location, that would confirm they could show the fight!
Well, that was much more of a pain in the butt than anticipated! I was a bit shocked at how the MGM can lock down the Strip, not allowing bars/restaurants to air a PPV event. Additionally the MGM properties were charging $300+ per person to watch at their facilities, and would not take reservations for parties, or negotiate prices. Anyway, here are the final details (I will update the eventbrite page as well).
Cost: $150 (At the door, You are responsible to pay your own cover charge)
Includes: Draft beer, rail drinks, You get to watch the fight!
Note! They are not, have not, will not accept Reservations! It is first come first served starting at 5pm(pst). They have made this perfectly clear. So this is more of a gathering, not an event. You do not need an eventbrite ticket, it will not do you any good!
If you are looking for me, I will be wearing the hat below. I imagine I will be the only one with it in Vegas.
By my count, I have about 5 weeks and 2ish days until I hop on a plane for Vegas, and my favorite conference of the year! There are quite a few posts about what first timers should do, where and how to focus your time, etc. And I think I can relate to pieces of all of those blogs. No need for me to link to them, you can search on Twitter or google.
I’ll give you a few of my thoughts and highlight where you can find me this year.
I’m lucky enough in my day job that I get to play with all of the technologies, I’m not just the NSX guy, or the vCenter guy, or the VDI guy. So each year as VMWorld approaches I look at the technology landscape to see:
What interests me (whether it be work related or something freaking cool)
What I can apply to my current role
What sessions apply to 1 & 2
What vendors apply to 1 & 2
What extra curricular activities apply to 1 & 2
Usually I am going in with 1-2 topics in mind. This year is no different and that list includes vSphere Integrated Containers and NSX. Focusing more on VIC for session related activities. I am very interested in road-map items like Windows in the VIC. Hint Hint for anyone who wants to meet up about this, or if there are any VMware folks who would like to talk. I have some use cases that I would love to run down. I will also be spending some time on the VIC HOL’s.
Every year I say to myself: “forget the parties, you are too old, you need sleep” and every year I go home tired, super tired. I really enjoy the entire atmosphere of the event and extra’s. There are so many people you get to meet, ones that are doing similar things, and ones that are doing things you cannot even comprehend! It’s just nice to talk to folks that you can relate to.
OK, enough already, here are my 3 bullet point tips for anyone going.
Wear comfortable shoes.
Say hi to the person next to you.
Be present, and take advantage of each opportunity to grow yourself, intellectually and personally.
And here are my things NOT to do(#siderhouserules):
Don’t take pictures of slides.
Don’t take another persons opportunity, if you sign up, SHOW UP!
Don’t breathe while you are in the men’s room.
I have a few vBrownBag presentations this year! Come watch live! I think it is so cool that these presentations made it into the conference schedule. Huge thanks to the @vBrownBag team, you guys are AWESOME! If you want a live demo on anything I am presenting just shoot me a message or tweet.Where will I be all week? For starters, look for #siderhouserules on twitter. (note, I plan to be at all VMWorld sponsored events):
Monday Night – @vmwarecode Hackathon (no link/details yet)
Tuesday – TBD – Hoping for a TopGolf party!
Wednesday – VMWorld Party
Thursday afternoon – Friday night – Open for some idea’s. Last year Brian Graf led a group of us on a #vHike through Zion National park it was phenomenal! I’m not sure if he is doing something similar or not this year. But I would love to see part of the Grand Canyon this year. So if someone is interested in setting up a trip south, let me know!
I hope everyone enjoys the conference! I need to get back to work on my presentations!
I’ve reached out to several of the sports bars, some of them have responsded back citing they may not know if they can show the fight due to licensing with the MGM and associated properties. I’ll keep you updated.
Original post below.
It’s not what you think! I’m interested in watching the fight somewhere in Vegas the night of Aug 26th. There is no better way to meet some new folks then to get together and watch 2 guys beat each other up. So come out and get VMWorld 2017 started off right!
Check out the event here, and note that I will be updating my blog and the event with updates when an exact time and location are figured out. Let me know if you have any questions/suggestions. You can join the event with the link below:
You do not need a ticket. You do not have to bring a ticket. This is an open community event. I am using the event to track the level of interest for when I reserve space at the final destination. It will be a first come, first served basis the night of the event.
Note, this event is not affiliated with VMWorld or VMware all expenses are the responsibility of the attendee’s. Please drink responsibly.
I attended my first DockerCon last week, here are my final thoughts;
Docker is here to stay! Which is a good thing, but I can see the passion in all of their employees, and they are going to continue to evolve their product line to provide the software development and operations world great tools.
My goals for the conference were to see not only how I can apply this to my everyday life at work, but how I can apply this technology in my open source projects as well. Hopefully I could meet some great resources along the way! Oh, and eat some Brisket, mmmmmmmm brisket!
Likes: This conference was super focused, nothing even the slightly bit not related to containers was mentioned. It was nice to not have any distractions. The staff conference and Docker were extremely nice and helpful! I liked that the vendor expo had extended hours, many times I go to a conference and I am forced to choose between attending sessions or talking with vendors at the expo, I didn’t have to do that at Dockercon, plenty of time for both.
Dislikes: The workshop I signed up for was horrible, we spent the first 30 minutes doing hands on work, and the other 2.5 hours listening to two guys read their slides, it was not very helpful. Overall, I wish there would have been more Windows content, I know its new, but it was lacking. In general I feel like there could have been more sessions. It appeared that all of the “here’s how we did it” sessions were from big huge companies, nothing in the SMB range to compare myself to. My last criticism is that the community theaters were horrible to attend, people were pushing and shoving to get closer, because it was very very difficult to hear. I liked the concept, but the delivery just didn’t work out.
I’m very interested to learn more and test drive VMware’s VIC (vSphere Integrated Containers). Due to the fact that I work with VMware products a lot, it seems like a logical decision. I also like that they are providing a complete solution here, with Harbor, Admiral and the Photon Platform (minus Windows).
Windows has a long way to go. It works, but its not ready for prime time. The images are too large, and the application pool is too low for it to be a versatile and enterprise solution. It may be useful if someone is already running Hyper-V as their hypervisor, but I assume this is not the case for most.
Less is more! I learned quite a bit, however the message that never changed was to continue to reduce the size of the container images! Abby Fuller had a great session on this that kept playing over in my head.
YOU ARE NOT ALONE!
I already updated my Windows images to conserve space. I saved about 1gb on my PowerTools image, and several mb on my Nano Image by following some simple tricks learned in the Abby Fuller session. Check it out on Docker Hub.
Soon Windows will allow you to run Linux and Windows containers at the same time from the same host OS, this is exciting. This will allow me to create a small application on a single host, without having to use a Windows application stack, but use my powershell containers for processing the work.
I also learned how the layers of the Images worked, and that I should avoid leaving files on the layers to conserve space. This forced me to upload some of my modules to the Powershell Gallery to provide easy installation, and a smaller footprint. So that’s kinda cool!
I need to get to it, and start developing a plan to migrate from vm’s to containers!
Last, but not least:
I was worried that I was very behind the curve on Docker, but in talking with quite a few of attendees, it appears we are all in the same boat. There is plenty of help out there and many folks that are in your same situation. Join the community, join the slack channels, and start asking questions. It’s a very helpful and welcoming community, which is very refreshing! Give Docker a test drive and see how it can help your organization run faster and leaner. I encourage everyone to throw a bathing suit on and go ride a whale!
I’ve updated my Windows Docker image to include PowerNSX, PowervRA, and Vester. Why? just because. I’m sure there are folks out there who may want to run and explore with Docker for Windows and Windows containers. So why not use a container that you can apply to your daily tasks as a VMware admin?
You can check out my previous blogs on Docker and PowerCLI to understand how to get your environment setup.
The really cool thing about the Docker container is that you are guaranteed a clean consistent environment each time. And its quick! (Well after the initial download of the container).
Here is the list of available modules in my new Docker Image:
Hi everyone! This idea really stemmed from the VMworld Hackathon Vegas 2016. Yes, it really took me this much time to get this thing put together. I think that the project was initially intended to be used with Pester and NSX. This new project is a user interface that wraps Vester. The hope is that it will expand to other Powershell unit/integration tests, or configuration management tools. I’d love to start playing with PowerNSX and Vester!! The great part about this tool is that you can share a single interface with a team or group of system administrators, not everyone will need to install and run command line tests. I work on a team of 11 folks with varying levels of skills, this tool allows us to share a single interface to inspect our entire vSphere infrastructure, remediate configuration drifts, report on problems, and compare historical data easily.
Right now the project is completely separate project than Vester. Somewhere in the future we will need to determine what the right model will be and whether or not to start integrating the two code bases. At this time there are no code changes needed in order to run XesterUI on top of Vester.
Side note, I do not claim to be a web developer. I have chosen the WAMP stack because it is very easy for a System Administrator to manage, update, and customize. This tool is intended to be functional first, pretty second. I will take any help I can get with making the pages prettier, but I will not sacrifice looks for the ability of a junior or mid level SA to make changes that could help their organization.
Lastly, this is a Beta release. I’m interested to get feedback on whether this will be useful, or improvements and feature requests, nothing is off the table at this point!
TestRun – A set of specified tests that run on specific Targets.
System – A group of Targets, must contain at least one vCenter
Target – A single vSphere entity, vCenter, Host, Cluster, vm, etc.
Queue Manager – Manages the Queue of tests, assigns them to an appropriate TestRun Manager, also aborts cancelled testruns.
TestRun Manager – A process that can execute a TestRun workflow.
Workflow – A wrapper script for Vester.
Database – Collects all of the meta data about the vSphere systems and TestRun results.
User Interface – Set of web pages where you are able to slice and dice the TestRun data, submit TestRuns, Remediate, etc.
How does it work?
XesterUI simply wraps Vester right now. There is a workflow script that is executed by the TestRun Manager. The wrapper script gets test information from the Database, executes Vester specifying the config.json file and whether or not to remediate problems. After the test completes the script parses the XML result file, and imports the TestRun data as records in the Database. Once the data is imported, the user is free to view, sort, and filter the TestRun data.
Setup is not difficult, I’m still working on a deployment script (and better documentation) that will make things fairly simple, until then follow these quick directions (and let me know if you have any problems):
Download and install:
WampServer 2.5 or newer
PowerWamp project (place in c:\openprojects\PowerWamp)
PowerLumber project (place in c:\openprojects\PowerLumber)
XesterUI project (place in c:\openprojects\XesterUI)
Note: The deployment of Components does not have to all be on the same machine. You can deploy the Queue Manager and TestRun Managers to different machines. Not sure the Queue Manager makes sense at this point. Additionally you can install the ‘AMP’ on a linux host, so long as it will have access to a CIFS share where the log files are accessible to all parties. Setting up multiple TestRun Managers could prove to be very useful if you have multiple sites and low WAN speeds.
Status and Results:
Here is a list of the status and results included in the Sample Data. I Highly recommend you use the default ID’s and Text Status/Result. Feel free to change the HTML color though!
The result of an overall TestRun will bubble up from the lowest test case.
A critical result means that the Total number of testcases reported in the XML, did not get inserted into the database.
Pass means that ALL testcases passed, and are accounted for.
Fail indicates that at least 1 test case has failed.
Agent_Error indicates that the system failed somewhere.
From this page you have several options, You can view the TestRun logfile, or Result XML.
All of the TestRun worflow messages will be logged here.
This is the XML produces from Vester/Pester.
There are two options for viewing Testcase results for a specific TestRun. Drilling down by TestSuite, or viewing all Testcases.
Viewing all TestSuites of a TestRun. Failures bubble up.
Viewing all TestCases from a TestRun, sortable, filterable data.
From the TestSuite page, you are able to drill down and view the Testcases:
On most of the UI pages you are able to sort any column and filter on strings. If a test case has failed, you are able to view the stack trace, and are able to resubmit the test with the remediate flag.
Submitting a new TestRun is easy, Click the Systems link, and in the row of the system you’d like to test, enter a TestRun name, specify if you want to remediate, and click ‘Submit TestRun’.
You are also able to view the targets from a specified system or all systems.
Additionally, if you click on a target you have the option to view all previous TestRuns and the results.
Creating a new System and Target are easy, simply fill out the supplied forms.
Only basic information can be entered for a new Target. I’ll work on making this more robust.
Systems are straight forward to add.
Lastly, you can view the Queue Manager and TestRun manager log files from their respective pages. Additionally you can shutdown the Managers. There is a ticket in to be able to start those components. The log files for TestRuns and the manager are stored in ‘c:\XesterUI\component‘ (Queue_Manager, TestRun_Manager, TestRuns\TestName_ID).
View status, logs, and shutdown the Queue Manager
View status, logs, and shutdown the TestRun Manager
Hopefully this gives you an overview of all the features of this tool, and how it can be useful to have all of that data in a searchable/sortable format. Note that Targets do not need to be populated into the DB before you run your first test (with exception of a vCenter). If a target does not exist, it will be created when the XML is being converted and results inserted into the DB.
Build config files on the fly for an individual ‘target’ or groups of ‘targets’.
Mulitple vCenter’s per system.
Ability to create a config.json file by clicking through the web.
Creating a useful exportable report (potentially email reporting).
Ability to abort a test.
vCenter config.json files are more appropriate than ‘System’ config files.
Currently a problem with the SMTP check not returning a vCenter ‘Target’ in the XML. This causes a problem with inserting the data into the DB. I know the Target is a vCenter, but I am not given the Target name. I’ll work on tracking down why that’s missing.
I’m not a security expert. So taking a look at WAMP best practices might be prudent in your environment. I can certainly give you advice, but do your due diligence and make sure you are meeting your organizations goals for security. There are several area’s of this product that could present a security risk. Keep in mind this project is currently in beta, and will continue to grow in maturity over time. Let me know if you have any questions or concerns.