to make it easy for people to put information online in a chronological fashion, in the form of short, time-stamped text messages ("entries") with optional HTML markup for presentation, and optional file attachments (images, archives, etc.)
to make it easy for other people to access this information through a Web interface, browse entries, search, download files, and optionally add, update, delete or comment on entries.
Read the rest of Install and configure Elog (Logbook system) on Ubuntu 16.10 Server (670 words)
I saw a question today which was interesting, how do I disable DRS for a single host in the cluster? I thought about it, and you cannot do this within the UI, at least… there is no “disable DRS” option on a host level. You can enable/disable it on a cluster level but that is it. But there are of course ways to ensure a host is not considered by DRS:
I will file a feature request for a “disable drs” on a particular host option in the UI, I guess it could be useful for some in certain scenarios.
"How to disable DRS for a single host in the cluster" originally appeared on Yellow-Bricks.com. Follow me on twitter - @DuncanYB.
Smashed burgers by The Food Lab: Better Home Cooking Through Science (fry sauce was really good), beer by Gigantic Brewing, conversation suggested by Family Dinner Project, family video highlights include drone capturing snow in PDX and the trailer and ending song from Reel Rock 11 and family dance night sponsored by Dodo Delight and Wild Yaks – Paradise.
I’ve started a podcast.
Each episode, I find a smart person somewhere on the planet, and we talk about The Important Thing. I suspect we’re going to wander a bit, but wandering is usually the best part.
I’m just delighted to kick off the first episode1 with Tiff Arment where The Important Thing is pens2. In this first episode, we talk pen origin stories, we dive deep on fountain pens, and, uh, we talk video games, too.http://traffic.libsyn.com/rands/theimportantthing0001.mp3
John was active in the LOPSA community. I saw him at nearly every LOPSA-NJ meeting, where he was active in planning and hosting the meetings. He was also on the board of LOPSA (national) where he will be greatly missed.
John was also a football coach at the school where he worked in the IT department. It was very clear that his coaching skills were something he applied everywhere, including his helpfulness and mentoring at LOPSA.
I had a feeling that when I hugged him at the end of the January LOPSA meeting it might be the last time I saw him. He was recovering from bypass surgery and was looking worn. He was chipper and friendly as always. He was a good guy. Easy to get along with. He kept LOPSA-NJ and many other projects going.
John Boris passed away last night.
I'll miss him.
Info about his service:
In lieu of flowers donations can be made to Camden Catholic high school football program, Cherry Hill, NJ c/o Nick Strom.
In December, about 175 work hours have been dispatched among 14 paid contributors. Their reports are available:
The number of sponsored hours did not increase but a new silver sponsor is in the process of joining. We are only missing another silver sponsor (or two to four bronze sponsors) to reach our objective of funding the equivalent of a full time position.
New sponsors are in bold.
As I get the following question a lot I figured I would share the answer here as well: Can you run all-flash with vSAN 6.2 Standard license? Many of you have seen the change in licensing when 6.5 was introduced. No longer is vSAN licenses based on storage hardware used, spindles or all-flash, you can use the lowest license SKU. Which of course is great for those wanting to use 6.5, but what about those who want to stick to 6.0 U2 aka vSAN 6.2? (This also works for 6.0 and 6.1 of course, but I would highly recommend 6.2 with the latest patches!)
Well there is a way to “downgrade” your license. (I would call it convert myself, but downgrade apparently is the official term for it.) There are 3 simple steps which are described in the following KB, but copied/pasted here for your convenience:
"Can you run all-flash with vSAN 6.2 Standard license?" originally appeared on Yellow-Bricks.com. Follow me on twitter - @DuncanYB.
At this moment, at the beginning of the year, I have eight active big rock projects. The following attributes define these projects:
I bounced from work a little early before the holidays to tackle one big rock project. It was the development of a headcount plan for 2017 along with a supported budget forecast. The work is familiar, I’ve done it many times. This big rock had been on my list for over a month regularly getting pushed each day I couldn’t find time to make progress. With the relative quiet of the holidays, I told myself, “Headcount and budget. Tuesday morning. I’ll make coffee and knock it out before Noon. Two hours. Three tops.”
I started on schedule in the comfort of the Cave, coffee in hand, fired up the necessary spreadsheets, and eleven hours later I was done. Eleven hours. Aside from a small amount of unexpected side research, and a couple of brief breaks, I was heads-down productively crunching numbers for 10+ hours with the benefit of having a crew of talented humans answering my endless questions throughout the day.
Eleven hours. I wasn’t even close with my original estimate, and this is work I’ve done multiple times before. When I shipped off my completed artifacts in the evening, I reminded myself my original plan was to do this big rock at work. I asked myself, “Given the interruptions, meetings, and other corporate curveballs in the office, how long would this big rock have taken?”
My honest answer was an alarming: I would not have finished.
The Illusion of Productivity
I change my productivity system every year or so. I’m in my second year of using Asana. What started out as a convenient and productive way to track my work became what every single productivity system has become to me: yet another inbox.
At some threshold which is entirely dependent on your working style, an inbox is no longer a useful tool. You can’t admit this to yourself because that inbox contains important things and that aggregate importance must be nurtured with daily attention. It must be curated with filter rules, tags, and sub-folders. The result of this constant maintenance is a sense of satisfaction and accomplishment.
You cross the threshold of inbox usefulness when you begin to mistake the act of managing the importance rather than acting on the importance. Speaking as a human who has crossed this uselessness threshold multiple times, I am prepared to declare that I am 100% done with productivity products. There is a better, simpler, and more productive way.
The Mindset of Busy
Let’s go back to my 11-hour headcount project and the assertion that I wouldn’t have finished the work at work. The truth is that I would’ve finished something resembling a headcount plan, but it would’ve looked nothing like what I produced with focused time. In the half-hour slices of time I would’ve found on my calendar to get the work done, I would’ve played the mental game of, “Ok, what can I get done in the next 30 minutes to make me feel as if I’ve made progress?”
This is the Busy Mindset. It is a mindset burdened with a packed scheduled and a long set of tasks, each with a deadline that sure felt reasonable when I committed to them two weeks ago. The Busy Mindset creates a sense of accomplishment by doing the bare minimum to complete a thing. Small or large, important or not, the thing being completed – crossed off the list – is the goal.
There are a great many managers who exist entirely within the Busy Mindset. They tell themselves this state of eternal busy is what a manager does. They’ve convinced themselves that they are leading by example and being seen as busy means the team will better appreciate and internalize the value of busy.
The perceived velocity achieved by being busy is a lie. Velocity is a vector. It is a combination of speed and a given direction provided by strategy. The rapid completion of small tasks might give you speed, but it is a well-defined direction that will give you efficiency, value, and impact. Who cares how quickly you are getting work done if it’s not the right work?
Productivity systems (and most inboxes) weaponize busy. They are designed with as many knobs and dials necessary to provide you with a sense of progression when often all you’ve done is wasted thirty minutes that you could have been spent building.
The Builder’s Mindset
I wrote about the The Builder’s High in early 2014. I talked of the cascading chemical awesomeness provided by your brain when you begin the act of building. Your brain wants to be in this state. It’s designed to be in this state.
When I went back and looked at the work I completed in those 11 hours, I was confused by where all the time went. I had only built two spreadsheets and written a short introductory piece about how to interpret those spreadsheets. The irony is that my original three-hour estimate to get this work done correctly accounted for building two spreadsheets. My estimate was right for just building the final product, but that estimate didn’t account for all the essential pre-work of wandering, researching, and other pre-work activities.
It’s a Silicon Valley joke that you triple all estimates from engineers, but it’s no joke. In fact, it works for any human who provides an estimate for a complex task where any or all of the following conditions are met:
My headcount and budget project involved a half-dozen warm-up spreadsheets to help me understand what happened in 2016 regarding hiring. There were the development and iteration of models to help me forecast what might happen in 2017. Those models needed to be debugged and tested.
The final simplicity of the two spreadsheets and the clarity of guidance on how to use those tools was the result of asking and answering thousands of small questions for myself, finding and cleaning the data, and ultimately designing a tool useful not only for me, but anyone who wanted to understand our headcount and budget plans. You know, another three hours and it would’ve been really good.
Building quality things of substance takes time.
There is never enough time; you are greatly outnumbered by chaotic, beautiful snowflakes, and there is too much to do and too much to know. This is the status quo of management, and without a clear counter-investment in building, you are going to get lost in the busy.
I have a proposal.
You Get One Thing
Here’s what we’re going to do:
This system is not for everyone. This system will be more useful to manager-types who have a deep sense of productivity doom. If you keep asking at the end of the day, “What did I do today?” this system might work. If you aggressively keep your to-do list tidy and regularly updated, but never feel like you’re ahead, I might be able to help.
Please note: This is going to hurt and you are going to get mad at some point. Sorry.
First, you are still going to need a list for your little rock projects, and I highly recommend starting with your favorite text editor. Go through your soon-to-be-obsolete productivity system and write down any small to-dos that you need to remember. These are small projects that you can’t do right now that you need to complete in the next week or two.
You only get ten little rocks on this list. Yeah, 10.
Most of you are like me and have way more than ten items on their list. Like 5x more? Some of those are very important, which means you’ve tagged them IMPORTANT and highlighted them in RED. You have ignored the fact that that this IMPORTANT RED thing has been deferred for two weeks. It is neither important nor red. It exists here because it costs you absolutely nothing to add a thing to your to-do list.
“I can do it! I just need more time!” is the rallying cry of a new manager trying to dig themselves out of a productivity hole. Yes, you can stay late or work weekends, but creating more hours is fixing the wrong part of the equation. You, the leader, signed up for too much and that’s either bad judgment or a lack of strategy. Your time is a finite resource, and unless you value that time correctly, you’re going to invest it poorly.
By constraining the list to 10 little rocks, I am asking you to make hard trade-off decisions regarding what you can and can’t do within a finite list of items. When the list is five times the size, this prioritization is an impossible task because you can’t keep relative priority of 49 other items in your head.
But Rands, that’s why I have this tagging system. I filter by tag first and then I…
Stop stop stop. You are one human being with finite time who can only complete one thing at a time. Your time is immensely precious, and these ten items likely represent at least a week’s work and do not account for the fact that who knows what is going to change in the next 24 hours. Ten items. That’s it.
If you’re having trouble getting to ten, I have suggestions:
I had my fair share of angst as I was culling my list, but in the weeks that I’ve been using this system I’ve realized how many systems surround me that remind me of tasks and commitments. Two inboxes (work and personal), weekly 1:1 meetings with my staff, agenda for all meetings, and every single document where I am listed as an owner of a task.
A natural and usually healthy byproduct of a group of humans working together is process and a defining characteristic of process is to make sure everything knows what we’re doing, why we’re doing it, and who is doing what. It turns out there are inboxes everywhere.
Big Rock Projects
With the little rocks culled from your former productivity system, we are left with the big rock projects. These are not to-dos, but large and complex projects like “Fix marketing.” These items don’t belong here because of the size and complexity. They are buckets of tasks unto themselves. As we learned at the beginning of this piece, I currently have eight of these beasts on my plate.
For the big rock projects, you need to apply the same critical analysis that you performed on the small rocks: can I delegate? How long has it been around? Is it important? Once you’ve done that, here’s the power move: you only get to actively work on one of these a week. There are two major consequences with this approach:
First, for every big rock project that isn’t “the one,” you need to stack rank prioritize the order that you’re going to attack the remaining projects. Next, you need to realign any expectations with external parties regarding those remaining rocks For example, if each of those eight big rock projects on my plate takes a week, the last one on my prioritized list is getting very little attention for at least two months. Pro tip: The act of telling humans your new priorities might reveal new data that will trigger big rock reprioritization.
Second, each week you need to carve off at least five hours to work on this big rock project with sessions no smaller than one hour. This is on your calendar protected time that you can’t reschedule. It’s as important as your 1:1s and your staff meeting. You are going to love this.
An Antidote for Busy
The mindset that emerges from long quiet swaths of vacation is one removed from constant interruptions, endless meetings, cluttered noisy inboxes, and that human who just needs a minute of your time. It is a mindset capable of deeply considered thought, digesting complexity, and building strategy. There are humans who are capable of keeping this mindset while busy, but I am not one of those humans.
However, my job is full of interruptions. I work hard to attend the right meetings and make sure they are valuable for everyone. I am a leader, so I have minutes for everyone. I do not have time for busy, I see little value in being busy, and I most certainly don’t want my team to believe that a busy lifestyle is aspirational.
A common question I get is, should managers still code? A better question is, should managers still build? “Yes”. It doesn’t need to be code and it can happen entirely through the delegation to others, but every manager should have work on their plate that involves long periods of thinking as a daily antidote for busy. We need to be reminded of the healthy mindset that accompanies the act of building.
There’s a valid argument that I’ve just replaced one productivity system with another, but let’s do the math. If we assume that the act of scrubbing your simple little rock list takes an hour for the entire week and that you run with my five hours per week big rock project schedule, then we’re talking six hours per week. That’s 15% of your week devoted to big rock and to-do triage. You’ve still got 85% of your week to fill with little rocks and… whatever it is you do all day.
Think of it like this. Assume the average big rock task takes a week. That seems fair? Some will be longer, others will be shorter. If we carve off two weeks for holidays and assume you complete 80% of your tasks, that means 40 big rock projects came to completion in the next year. Is that more or less big rock projects than what you completed last year? Your answer, like mine, is, “I don’t know, but I was sure busy.”
One big rock project at a time and 10 little rock projects. That’s it. Of course, there is more you need to do, but don’t worry because there are people and inboxes everywhere that are going to remind you of this work. Meanwhile, this approach gives you the gift of focus and it is only when you focus that you truly build.
I have the pleasure to present at three VMUGs in the upcoming months I have never presented at before, heck I never been to those countries even. First coming up is the VMUG in Dubai on the 16th of February followed by two VMUGs in Australia, with the Dutch VMUG in between. Lets see which other VMUGs we can add to that list in the upcoming months.
I will (most likely) be talking about vSAN (what else), if you are interested make sure to register through the VMUG website here: https://www.vmug.com/Attend/Calendar (no details for Dubai yet).
See you there, I will make sure to bring some goodies like stickers and probably shirts (if I can order them in time).
If you forget the root password for an SRX firewall device, you can use the password recovery procedure to reset the root password. This procedure also involves disabling the watchdog functionality to allow the system to properly boot into single-user mode
Procedure to follow
Power on the device by pressing the power button on the front panel. Verify that the POWER LED on the front panel turns green.The device’s boot sequence on your management device appears on the terminal emulation screen.
When the autoboot completes, press the Spacebar a few times to access the bootstrap loader prompt.
In operational mode, disable the watchdog functionality and enter boot -s to start up the system in single-user mode.
The SRX firewall device will start up in single-user mode.
Enter recovery to start the root password recovery procedure.
System watchdog timer disabled.
Enter full pathname of shell or ‘recovery' for root password recovery or RETURN for /bin/sh: recovery
Enter configuration mode in the CLI.
Set the root password.
user@host# set system root-authentication plain-text-password
Enter the new root password.
New password: juniper1
Retype new password:
At the second prompt, reenter the new root password.
If you are finished configuring the network, commit the configuration.
Exit from configuration mode and Exit from operational mode.
Enter y to reboot the device.
Reboot the system? [y/n] y
The start up messages display on the screen.
Once again, press the Spacebar a few times to access the bootstrap loader prompt.
In operational mode, enable the watchdog functionality and enter boot to start up the system.
The SRX firewall device starts up again and prompts you to enter a user name and password. Enter the newly configured password:
(Sourced via the fine humans on Twitter.)
I installed Windows 10 in a Fusion VM recently and figured I would install VMware Tools. After the installation I couldn’t get it running in a proper resolution and I was actually limited to 1152×864. Very frustrating. I tried to solve it but for whatever reason the only thing that worked was:
That fixed it for me, if you had the same problem but a different solution please leave a comment!
"Windows 10 not running in full resolution in VMware Fusion?" originally appeared on Yellow-Bricks.com. Follow me on twitter - @DuncanYB.
I was talking to a VMware partner over the past couple of weeks about challenges they had in a new vSphere Metro Storage Cluster (vMSC) environment. In their particular case they simulated a site partition. During the site partition three things were expected to happen:
The problems faced were two-fold, VMs were restarted by vSphere HA, however:
It took a while before we figured out what was going on, at least for one of the problems. Lets start with the second problem first, why aren’t the VMs killed when the partition is lifted? vSphere should do this automatically. Well vSphere does this automatically, but only when there’s a Guest Operating system installed and an I/O is issued. As soon as an I/O is issued by the VM then vSphere will notice the lock to the disk is lost and obtained by another host and kill the VM. If you have an “empty VM” then this won’t happen as there will not be any I/O to the disk. (I’ve filed a feature request to kill VMs as well even without disk I/O or without a disk.) So how do you solve this? If you do any type of vSphere HA testing (with or without vMSC) make sure to install a guest OS so it resembles real life.
Now back to the first problem. The fact that vSphere HA Component Protection does not kick in is still being debated, but I think there is a very specific reason for it. vSphere HA Component Protection is a feature that kills VMs on a host so they can be restarted when an APD or a PDL scenario has occurred. However, it will only do this when it is:
First one is clear I guess (more info about this here), but what does the second one mean? Well basically there are three options:
So in the case you where you have VMCP set to “Aggressively” failover VMs, it will only do so when it knows hosts are available in the other site or when it does not know the state of the hosts in the other site. If for whatever reason the hosts are deemed as unhealthy the answer to the question if there are healthy hosts available or not will be “No”, and as such the VMs will not be killed by VMCP. The question remains, why are these hosts reported as “unhealthy” in this partition scenario, that is something we are now trying to figure out. Potentially it could be caused by misconfigured Heartbeat Datastores, but this is still something to be confirmed. If I know more, I will update this article.
Just received confirmation from development, heartbeat datastores need to be available on both sites for vSphere HA to identify this scenario correctly. If there are no heartbeat datastores available on both sites then it could happen that no hosts are marked as healthy, which means that VMCP will not instantly kill those VMs when the APD has occured.
"VMs not getting killed after vMSC partition has lifted" originally appeared on Yellow-Bricks.com. Follow me on twitter - @DuncanYB.