Writing

You are currently browsing articles tagged Writing.

No Man is an Island

The phrase “No man is an island” is attributed to John Donne, an English poet who lived in the late 1500s and early 1600s. The phrase comes from his Meditation XVII, and was borrowed later by Thomas Merton to become the title of a book he published in 1955. In both cases, the phrase is used to discuss the interconnected nature of humanity and mankind. (Side note: the phrase “for whom the bell tolls” comes from the same origin.)

What does this have to do with IT? That’s a good question. As I was preparing to start the day today, I took some time to reflect upon my career; specifically, the individuals that have been placed in my life and career. I think all people are prone to overlook the contributions that others have played in their own successes, but I think that IT professionals may be a bit more affected in this way. (I freely admit that, having spent my entire career as an IT professional, my view may be skewed.) So, in the spirit of recognizing that no man is an island—meaning that who we are and what we accomplish are intricately intertwined with those around us—I wanted to take a moment and express my thanks and appreciation for a few folks who have helped contribute to my success.

So, who has helped contribute to my achievements? The full list is too long to publish, but here are a few notables that I wanted to call out (in no particular order):

  • Chad Sakac took the opportunity to write the book that would become Mastering VMware vSphere 4 and gave it to me instead. (If you aren’t familiar with that story, read this.)
  • My wife, Crystal, is just awesome—she has enabled and empowered me in many, many ways. ‘Nuff said.
  • Forbes Guthrie allowed me to join him in writing VMware vSphere Design (as well as the 2nd edition), has been a great contributor to the Mastering VMware vSphere series, and has been a fabulous co-presenter at the last couple VMworld conferences.
  • Chris McCain (who recently joined VMware and has some great stuff in store—stay tuned!) wrote Mastering VMware Infrastructure 3, the book that I would revise to become Mastering VMware vSphere 4.
  • Andy Sholomon, formerly with Cisco and now with VCE, was kind enough to provide some infrastructure for me to use when writing Mastering VMware vSphere 5. Without it, writing the book would have been much more difficult.
  • Rick Scherer, Duncan Epping, and Jason Boche all served as technical editors for various books that I’ve written; their contributions and efforts helped make those books better.

To all of you: thank you.

The list could go on and on and on; if I didn’t expressly call your name out, please don’t feel bad. My point, though, is this: have you taken the time recently to thank others in your life that have contributed to your success?

Tags: , , ,

Well, the title kind of says it all—yes, there will be an update to the popular Mastering VMware vSphere 5 book, with new content for the vSphere 5.5 release announced today at VMworld. Availability of the new title is expected in late October or early November, but I believe it’s already available for pre-order on Amazon.

However, this book represents more than just another title in the Mastering VMware vSphere series. It represents a “changing of the guard,” so to speak. In order to understand why, allow me to share with you the story of how my very first book, Mastering VMware vSphere 4, came to be. This is a story that very few people know.

I suppose the story starts in 2008. As a blogger, I’d gained some visibility as a result of my liveblogging at VMworld 2007, and in 2008 I met Chad Sakac. Chad is now a hugely popular figure within the VMware community, but at the time he was “just” the leader of a little-known group within EMC. (This is the group that would later become known as the vSpecialists.) Chad and I chatted, geeked out on some VMware stuff, and became buddies. I didn’t really think too much about the connection; we were just a couple of virtualization geeks making a connection.

Then came early 2009. Chad contacted me, and said he’d been approached about writing a book. Unfortunately, he was unable to write the book; would I be interested in writing it, he asked. Heck yeah! Writing a book had been an item on my bucket list for a really long time. So Chad made the connections to Wiley/Sybex, contracts were signed, and at VMworld 2009 Mastering VMware vSphere 4 was released, quickly becoming a massive hit. I joined Chad’s vSpecialist team in 2010, and remained there for 3 years before transitioning to VMware earlier this year to focus on network virtualization.

Looking back on this series of events, it’s easy to see that this was a huge opportunity I’d received. So, when it came time to discuss writing the book that would become Mastering VMware vSphere 5.5, I asked myself: “I was just given this opportunity. Can I do the same for someone else? Can I pay this forward?” It was at that point I decided that I would not be the lead author for the next revision; instead, I would pass the torch on to someone else—someeone else who had “Write a book” on their bucket list. I wanted to give someone else the same opportunity I’d been given.

This is why Mastering VMware vSphere 5.5 represents a changing of the guard. This book embodies my decision to pay it forward, to give another worthy individual—in this case, Nick Marshall—the opportunity to do something he really wanted to do. Many of you know Nick; he’s been involved in the VMware community in a number of ways, through support of the vBrownbag Podcast as well as through his work with Alastair Cooke on AutoLab. In addition to that, he’s just a really nice guy, and that counts for something, too. I’m really thrilled that Nick has taken the lead with this book, and I’m really looking forward to seeing where he takes the Mastering VMware vSphere series.

So, if you’re looking for an authoritative reference to the vSphere 5.5 release, I would encourage you to pick up Mastering VMware vSphere 5.5. Nick and I, along with our co-conspirators Forbes Guthrie, Josh Atwell, and Matt Liebowitz, have done our best to produce something that is useful and informative. I hope that you agree.

Tags: , ,

A Short Dry Spell

It’s been a couple of weeks since I published anything here, so I wanted to just provide a brief update. I know that posting something about why I haven’t posted something is…odd, I guess you could say. In any case, a number of factors—some personal, some professional—have contributed to why I haven’t been able to generate some useful new content in the last couple of weeks. Of course, there are blogs that go for months between posts, so a small gap of a couple weeks isn’t really a big deal. After over 8 years (I started blogging in May 2005), I think you can rest assured that I have no intention of shutting down anytime soon.

However, despite this dry spell, I am determined to continue with my Learning NVP blog series (part 1 is here), as a great many people have expressed interest. Fortunately, I made some headway on some blockers that were preventing progress, and that gives me hope for new content soon. I’m also exploring new posts on Puppet, Open vSwitch (OVS), OpenFlow, and—who knows—maybe VMware will have some snazzy announcements at VMworld that will give me new fodder for posts. We’ll see.

So, bear with me as I work through this short bout of writers’ block. I hope to be back soon with some new content. Thanks!

Tags: , ,

Welcome to Technology Short Take #33, the latest in my irregularly-published series of articles discussing various data center technology-related links, articles, rants, thoughts, and questions. I hope that you find something useful here. Enjoy!

Networking

  • Tom Nolle asks the question, “Is virtualization reality even more elusive than virtual reality?” It’s a good read; the key thing that I took away from it was that SDN, NFV, and related efforts are great, but what we really need is something that can pull all these together in a way that customers (and providers) reap the benefits.
  • What happens when multiple VXLAN logical networks are mapped to the same multicast group? Venky explains it in this post. Venky also has a great write-up on how the VTEP (VXLAN Tunnel End Point) learns and creates the forwarding table.
  • This post by Ranga Maddipudi shows you how to use App Firewall in conjunction with VXLAN logical networks.
  • Jason Edelman is on a roll with a couple of great blog posts. First up, Jason goes off on a rant about network virtualization, briefly hitting topics like the relationship between overlays and hardware, the role of hardware in network virtualization, the changing roles of data center professionals, and whether overlays are the next logical step in the evolution of the network. I particularly enjoyed the snippet from the post by Bill Koss. Next, Jason dives a bit deeper on the relationship between network overlays and hardware, and shares his thoughts on where it does—and doesn’t—make sense to have hardware terminating overlay tunnels.
  • Another post by Tom Nolle explores the relationship—complicated at times—between SDN, NFV, and the cloud. Given that we define the cloud (sorry to steal your phrase, Joe) as elastic, pooled resources with self-service functionality and ubiquitous access, I can see where Tom states that to discuss SDN or NFV without discussing cloud is silly. On the flip side, though, I have to believe that it’s possible for organizations to make a gradual shift in their computing architectures and processes, so one almost has to discuss these various components individually, because to tie them all together makes it almost impossible. Thoughts?
  • If you haven’t already introduced yourself to VXLAN (one of several draft protocols used as an overlay protocol), Cisco Inferno has a reasonable write-up.
  • I know Steve Jin, and he’s a really smart guy. I must disagree with some of his statements regarding what software-defined networking is and is not and where it fits, written back in April. I talked before about the difference between network virtualization and SDN, so no need to mention that again. Also, the two key flaws that Steve identifies—single point of failure and scalability—aren’t flaws with SDN/network virtualization, but rather flaws in an implementation of said technologies, IMHO.

Servers/Hardware

  • Correction from the last Technology Short Take—I incorrectly stated that the HP Moonshot offerings were ARM-based, and therefore wouldn’t support vSphere. I was wrong. The servers (right now, at least) are running Intel Atom S1260 CPUs, which are x86-based and do offer features like Intel VT-x. Thanks to all who pointed this out, and my apologies for the error!
  • I missed this on the #vBrownBag series: designing HP Virtual Connect for vSphere 5.x.

Security

Cloud Computing/Cloud Management

  • Hyper-V as hypervisor with OpenStack Compute? Sure, see here.
  • Cody Bunch, who has been focusing quite a bit on OpenStack recently, has a nice write-up on using Razor and Chef to automate an OpenStack build. Part 1 is here; part 2 is here. Good stuff—keep it up, Cody!
  • I’ve mentioned in some of my OpenStack presentations (see SpeakerDeck or Slideshare) that a great place to start if you’re just getting started is DevStack. Here, Brent Salisbury has a nice write-up on using DevStack to install OpenStack Grizzly.

Operating Systems/Applications

  • Boxen, a tool created by GitHub to manage their OS X Mountain Lion laptops for developers, looks interesting. Might be a useful tool for other environments, too.
  • If you use TextMate2 (I switched to BBEdit a little while ago after being a long-time TextMate user), you might enjoy this quick post by Colin McNamara on Puppet syntax highlighting using TextMate2.

Storage

  • Anyone have more information on Jeda Networks? They’ve been mentioned a couple of times on GigaOm (here and here), but I haven’t seen anything concrete yet. Hey, Stephen Foskett, if you’re reading: get Jeda Networks to the next Tech Field Day.
  • Tim Patterson shares some code from Luc Dekens that helps check VMFS version and block sizes using PowerCLI. This could come in quite handy in making sure you know how your datastores are configured, especially if you are in the midst of a migration or have inherited an environment from someone else.

Virtualization

  • Interested in using SAML and Horizon Workspace with vCloud Director? Tom Fojta shows you how.
  • If you aren’t using vSphere Host Profiles, this write-up on the VMware SMB blog might convince you why you should and show you how to get started.
  • Michael Webster tackles the question: is now the best time to upgrade to vSphere 5.1? Read the full post to see what Michael has to say about it.
  • Duncan points out an easy error to make when working with vSphere HA heartbeat datastores in this post. Key takeaway: sometimes the fix is a lot simpler than we might think at first. (I know I’m guilty of making things more complicated than they need to be at times. Aren’t we all?)
  • Jon Benedict (aka “Captain KVM”) shares a script he wrote to help provide high availability for RHEV-M.
  • Chris Wahl has a nice write-up on using log shipping to protect your vCenter database. It’s a bit over a year old (surprised I missed it until now), and—as Chris points out—log shipping doesn’t protect the database (primary and secondary copies) against corruption. However, it’s better than nothing (which I suspect it what far too many people are using).

Other

  • If you aspire to be a writer—whether that be a blogger, author, journalist, or other—you might find this article on using the DASH method for writing to be helpful. The six tips at the end of the article are especially helpful, I think.

Time to wrap this up for now; the rest will have to wait until the next Technology Short Take. Until then, feel free to share your thoughts, questions, or rants in the comments below. Courteous comments are always welcome!

Tags: , , , , , , , , , , , , , ,

In some of the presentations that I give on productivity and efficiency, one of the things I mention is reducing the friction; that is, making processes more streamlined so they’re easier to perform. In this post, I’m going to describe one way I reduced the friction for producing and publishing blog posts using BBEdit, TextSoap, MarsEdit, and some AppleScript.

It’s no secret that I’ve become a huge fan of Markdown, the human-readable plain text “markup” format created by Jon Gruber. The vast majority of all my content is now created in Markdown, and then converted to RTF (to share with my Office-using co-workers), PDF (for broader publication), or HTML (for publishing online). Until very recently, my blog publishing process looked something like this:

  1. Write the blog post in Markdown, using TextMate.
  2. Using a built-in Markdown binary in TextMate, convert the Markdown into HTML.
  3. Run the raw HTML through TextSoap (very handy tool) to remove smart quotes and curly apostrophes.
  4. Paste the parsed HTML into MarsEdit for publication to my blog.

While it seems complicated, it wasn’t terribly complicated—but it wasn’t as seamless as it could be. So, I set out to improve the process. The first big change was a switch from TextMate to BBEdit, which is more extensible (and kept up to date by the developer). That change allowed me to do two things:

  • Switch from the built-in Markdown support in TextMate to using a separate (and more up-to-date) MultiMarkdown binary maintained by Fletcher Penny.
  • Introduce an AppleScript (BBEdit has outstanding support for AppleScript) to automate some portion of the process.

My first pass at automating the process just got me back to where I was before—writing Markdown in BBEdit, converting to HTML, cleaning the HTML with TextSoap, and pasting into MarsEdit. Not too impressive, but acceptable, and a process with which I was familiar. I stuck with that process for a while, primarily because it was a known entity. A couple of days ago, though, I asked myself: Can I do better? Can I be more efficient?

So, my second pass at automating the process is much more comprehensive. The AppleScript I wrote as a result of challenging myself to reduce the friction does the following:

  • Takes the Markdown from BBEdit and converts it to HTML.
  • Using the HTML produced by the standalone MultiMarkdown binary, it then calls TextSoap to (in the background) clean the HTML according to a custom cleaner I’d created (the custom cleaner, called “Replace HTML Entities,” just replaces curly quotes and curly apostrophes, which don’t translate well on my site).
  • Creates a new, blank blog post in MarsEdit, into which it pastes the cleaned HTML as the body of the post.

I store the script in BBEdit’s scripts folder, which means I can invoke the script easily from within BBEdit.

Here’s the AppleScript itself (click here if the script doesn’t show up):

Now, I can write my Markdown in BBEdit, invoke the script, and get dropped out to HTML code sitting in a new blog post in MarsEdit. All I need to do to publish the post at that point is supply the metadata (tags, categories, title, excerpt) and click Send to Blog. Done. (I used this process for this post, in fact.) How’s that for reduced friction?

Tags: , , ,

You might have seen that the second edition of VMware vSphere Design was recently released. How would you like to win a free copy?

Starting today (no, this isn’t an April Fool’s joke) and running through April 15, you can enter to win a signed print copy of VMware vSphere Design, 2nd Edition! I’m giving away a free, signed copy of the book to five lucky individuals who enter and win in this book giveaway contest.

Here’s how to enter to win one of the 5 free, signed copies of the book: simply post a comment on this site telling me why you would find this book useful. Yes, that’s it!

There are a few contest rules you’ll want to note:

  • You’ll need to use a valid e-mail address when you post your comment, because if you’re a winner I’ll be contacting you via e-mail to get your shipping information.
  • If I notify you via e-mail that you’ve been selected to win a copy but you fail to respond within 48 hours with your shipping address, I’ll select a new winner in your place.
  • Because I’m paying for the shipping out of my own pocket, I’ll have to limit this contest to continental US residents only. (Sorry folks—my personal budget can’t sustain sending print books worldwide.)

Aside from the limitation to continental US residents only, this contest is open to anyone, so don’t hesitate—enter today!

Tags: , ,

I’ve been phenomenally lucky to be involved in a number of book projects around VMware vSphere. I think that most people probably know me for the wildly popular Mastering VMware vSphere 4 and Mastering VMware vSphere 5 books (released at VMworld 2009 and VMworld EMEA 2011, respectively), but in late 2010/early 2011 I also had the opportunity to collaborate with Forbes Guthrie and Maish Saidel-Keesing on VMware vSphere Design. Even though that book hasn’t sold as many units as the Mastering books, it’s a work of which I’m equally proud. The topic of designing vSphere environments can be difficult to address, but I think we did a pretty good job.

Today I’m excited to announce that Forbes Guthrie and I–along with some support from Kendrick Coleman–have undertaken a revision of that book, to be released as VMware vSphere Design, 2nd Edition.

VMware vSphere Design, 2nd Edition

In addition to a new cover design (nice, huh?), this new version of the book has a new interior as well! The book has been thoroughly updated to include design topics and considerations for vSphere 4, vSphere 5, and vSphere 5.1. In addition to discussing design topics like management, storage, networking, and security, Kendrick contributed content around design considerations for vCloud Director. The updated and expanded content makes this a great resource for anyone who will be designing VMware vSphere environments.

For more information about the book, or to see a list of resellers for the book, visit the publisher’s page.

Thanks, and I think I speak for Forbes and Kendrick when I say that we hope this resource is useful to you!

Tags: , , ,

Shortly after I published Technology Short Take #27, a reader asked me on Twitter how I managed the information that goes into each Technology Short Take (TST) article. Although I’ve blogged about my productivity setup before, that post is now over two years old and horribly out of date. Given that I need to post a more current description of my tools and workflow, I thought I’d take a brief moment to answer the reader’s question. Here’s how I go about building the Technology Short Take articles.

I’ve mentioned before that I have three “layers” of tools: a consumption layer, an organization layer, and a creation layer. I’ll break down the process according to these layers.

The Consumption Layer

This is where I go about actually finding the content that gets pulled into a TST post. There’s nothing terribly unique here; I have a collection of RSS feeds which I subscribe and I get content from people I follow on Twitter. I will also visit various Usenet newsgroups and certain IRC channels (only on irc.freenode.net) from time to time.

If you’re interested in seeing the RSS feeds to which I subscribe, here’s an OPML list of all my subscriptions.

The majority of the content I consume is web-based, so when I find an article that I want to use in a TST post, I’ll save that as a Safari web archive. I wish there was a more platform-independent method, but as yet I haven’t found a good solution. Once I’ve saved a page for future use, then we move into the organization layer.

The Organization Layer

As content is discovered via any of the various consumption layer tools, I then need to get that content “sucked” into my primary organization layer tool. I use a really, really fancy tool—it’s called the file system.

When I save a web page that I’m planning on including in a TST article, I generally save it, by default, to the Desktop. I have a program named Hazel that watches the Desktop and Downloads folders for web archive files, and automatically moves them to a WebArchives folder. From there, I use a couple of saved Spotlight searches to identify newly-created web archives that don’t have a source URL or don’t have any OpenMeta tags assigned. For these newly-created web archives, I use the Spotlight comments field to store the source URL, and I use an application named Tagger to assign OpenMeta tags.

Once a web archive has its source URL and OpenMeta tags assigned, then I have a group of saved Spotlight searches the group files together by topic: virtualization, storage, OpenStack, Open vSwitch, etc. This makes it super easy for me to find web archives—or other files—related to a particular topic. All these saved searches are built on queries involving the OpenMeta tags.

Content will remain here until either a) I use it in a TST article and no longer need it; or b) I use it in a TST article but feel it’s worth keeping for future reference. I might keep content for quite a long time before I use it. Case in point: the Q-tools stuff from Dave Gray that eventually found its way into some of my VMUG presentations was something I found in 2009 (it was published in 2008).

The Creation Layer

After collecting content for a while, a scheduled, recurring OmniFocus action pops up reminding me to write the next TST post. At this point, I go back to my organization layer tools (saved Spotlight searches and content folders) to pull out the various pieces of information that I want to include. I write the post in Markdown using TextMate, building off a skeleton template that has all the content headers already in place.

Using the saved searches I described above, I’ll search through my content to see what I want to include in the TST post. When an item is included in a TST blog post, I’ll write my thoughts about the article or post, then grab the source URL from the Spotlight comments to make a hyperlink to the content. If the content is useful and informative, I might keep it around; otherwise, I’ll generally delete the saved web archive or bookmark file. I repeat this process, going through all my saved content, until I feel that the TST post is sufficiently full of content.

Then, because it’s all written in Markdown, I convert the post to HTML and actually publish it to the site using the excellent MarsEdit application. TextMate makes this incredibly easy with just a few keystrokes.

And that’s it! That’s the “mystery” behind the Technology Short Take articles. Feel free to post any questions or thoughts you have about my workflow and tools in the comments below. Courteous comments are always welcome.

Tags: , ,

Every now and then, it’s kind of fun to look back at the content that I’ve generated in my 7 years of blogging here (soon to be 8 years). With that in mind, here are some “posts from the past” for early December.

4 Years Ago (Early December 2008)

Installing the VI Power Documenter
Continuing the FCoE Discussion

3 Years Ago (Early December 2009)

What is SR-IOV?
Snow Leopard, Time Machine, and Iomega ix4-200d

2 Years Ago (Early December 2010)

VLAN Trunking Between Nexus 5010 and Dell PowerConnect Switches
Using Device Aliass on a Cisco MDS

1 Year Ago (Early December 2011)

Some Initial MPLS Reading
Examining VXLAN
Revisiting VXLAN and Layer 3 Connectivity

Tags: , ,

The funny thing about technology is that there is rarely one answer that fits all situations. This is the root of the reason behind the all-too-familiar IT answer, “It depends.” Rarely is this challenge more evident than when trying to write a book that is applicable to as broad an audience as possible. The challenge is compounded when the topic of your book is a large, complex suite of software like VMware vSphere.

As an author, you want to provide information that is helpful, yet at the same time you know that you simply cannot provide the “right” answer for all the possible readers out there. And you also know that you simply don’t have enough pages or enough time to discuss every single potential factor that might play into how a particular technology should be deployed or configured. As an author, you rarely have the time and page count to go as deep as you’d like. (There are exceptions—the HA/DRS clustering deep dives are good examples.) So, you try to take a balanced approach, making fairly broad recommendations that will apply to the largest group of individuals in the most common set of circumstances or situations.

Because you know you can’t provide the “right” answer for all possible situations and environments, you also know that there will be individuals for whom the book isn’t as helpful as it is for others. Perhaps their particular environments have circumstances that aren’t common, or perhaps their functional requirements drive their vSphere environment in directions most organizations don’t go. That’s fine—that’s the whole reason “It depends” is such a popular answer.

As a result, I can’t say that I was terribly surprised when someone on Twitter pointed me to this Spiceworks thread criticizing some broad RAID recommendations that I made in Mastering VMware vSphere 5. As I’ve already stated, it’s impossible (in my opinion) to provide the “right” recommendations for every possible user in a relatively-mainstream IT book such as Mastering VMware vSphere 5. What did surprise me, though, was that the thread was surprisingly vitriolic, focusing more on me personally than on the recommendations themselves (“Mr Lowe…should not be spreading his ignorance” and “I’ve seen some stuff he’s written and I’m none too impressed”). That’s a shame—it would have been so much more helpful for other Spiceworks community members and the virtualization community as a whole if the thread had focused more on providing “better” RAID recommendations than what I included in the book.

So, I’d like to take this opportunity to issue a call to the storage experts out there (which I am not, and have said that on numerous occasions) to chime in and provide what they think are the “best” RAID recommendations or storage configurations to support a VMware vSphere environment. Keep in mind the challenges I described earlier—you need recommendations that are broadly applicable to many users, many environments, many situations. Please add your thoughts in the comments below, and—where applicable—please provide any relevant affiliations or disclosures. All courteous comments are welcome!

(Full disclosure: I do work for EMC, although this is not an EMC blog and “Mastering VMware vSphere 5″ was not sponsored or supported by EMC in any way. I speak only for myself.)

Tags: , , ,

« Older entries