Author: Frank Denneman (page 1 of 67)

VMware Cloud on AWS – Predictable Capacity Provisioning

In preparation for the VMworld Session LHC2971BU – Managing Your Hybrid Cloud with VMware Cloud on AWS which I’m co-presenting with Emad Younis, I asked the following question on Twitter:

And the number of answers were overwhelming. The stories were a bit underwhelming. Funny to see that we strive to automate every single step in the process. Guys like Alan, Luc, and William help the community to create scripted installs and configuration of the ESXi host. Creating a consistent, human-error free, rapid process. Shaving off valuable time of the time-consuming server provisioning process. Some organizations incorporate the vRealize suite to create a consistent user experience for the entire IT services portfolio. Interestingly enough, the overall lead time seems mostly impacted by internal acquisition processes. To give a few examples:

And the list goes on and on. In most organizations, the procurement process is rigid, well-defined process. However, the lead time of the acquisition process is either unpredictable and inconsistent. The overall message is that it cripples the agility of the IT organization.

IT organizations need to react fast to the business needs. Resource management of current workload is difficult enough, figuring out what to expect in the upcoming months is challenging. Unfortunately, the introduction of new workload does not follow a linear demand curve. To cater the (possible) future needs of the customer, the order is either doubled in size, or onboarding of new workloads is gated. Either impacting the bottom-line of the company or the ability to facilitate IT services properly.

In essence, the CAPEX element of server resource acquisition massively impacts or hinders the execution ability of the IT organization. Strategizing CAPEX\OPEX is not a part of the core focus of many admins and architects, it does affect their means of execution. As demonstrated by the many tweets. With VMware Cloud on AWS, the host resource acquisition process shifts from CAPEX to OPEX. Removing the inconsistent and unpredictable procurement process, allowing for a faster, consistent and predictable method of providing compute, storage and networking resources.

VMware Cloud on AWS (VMC) makes my resource-management heart beat faster. By leveraging the AWS operation model, the SDDC cluster running on the AWS infrastructure is resizable by a click of a button. Right-click on the cluster and select resize.

Just select the number of hosts you want to add and within moments you will get new dedicated physical hardware added to your cluster. Ready to provide the resources your new workloads require. Resize means you can remove the resources as well, which in result your costs will go down as well.

Due to the combined fleet management of AWS and VMC, the new ESXi hosts are fully configured and ready to welcome new workload. All VMkernel and logical networks are automatically configured and made available. The vSAN datastore is automatically expanded with the host-local NVMe flash devices provided by the new hosts. DRS detects the new physical resources and automatically rebalances the cluster, provided the most optimal resource availability.

Elastic DRS and Autoremedation HA allows for an automatize method or adding and removing dedicated hardware resources, but these topics will be covered in a different article.

From a resource management perspective, a mindset shift will happen. VMC allows you to reduce the time spent on infrastructure configuration and management and allows you to focus more on resource consumption. What cluster configuration is required in the upcoming months? What is my burst strategy?

Unfortunately, I can’t go into detail as the service is not released yet. VMworld boasts an exciting line up of VMware Cloud on AWS sessions. I will be hosting a meet the expert on resource management at both VMworlds, sign up if you want to talk more about this exciting new technology

Kindle Ebook Host Deep Dive Available

Funny enough I’ve just published an article announcing the major milestone of 4000 hard copies sold within the first month of release. I just received confirmation that the Kindle e-book version is available at the Amazon Kindle Store. It is scheduled to appear on various Amazon sites. Please check out your local Amazon for the best offer.

Amazon US
Amazon DE
Amazon NL
Amazon UK
Amazon India

The most popular e-book version of the cluster deep dive was Kindle, and therefore we focused on getting the Kindle e-book out as fast as possible. The professionals of Amazon Kindle Direct Publishing created an awesome e-book version. Go check it out.

Host Deep Dive First Major Milestone

Exactly one month ago Niels and I published the VMware vSphere 6.5 Host Deep Dive and it is a major success. Within 30 days we sold over 4000 copies of the book. Building consistent high-performing ESXi hosts remains a strong focus point for the virtual community.

The attention for the book is overwhelming. The hashtag #HostDeepDive felt like it was trending. Tweets from around the world letting us know the book arrived, from Brasil to New Zealand.

The book seems to be a beloved companion during the summer holiday. Christian Mohn and Erik Bussink engaged in a competition to provide us the best vacation shot possible.
Mohn:

Bussink

Brad Tompkins of the VMUG organization joined the party by giving away twenty copies to the audience of the Indy VMUG last week.

Amazon awarded the book with many accolades, being the number one book in the network section and at one point it was in the top 25 of computer books overall. Quite an achievement! The absolute fantastic reviews help a lot. Thank you all for submitting a review!
Due to the popularity of the book, Amazon offered us help with creating an ebook version of the book. They put their professional team to work two weeks ago, and we expect to have it online soon.

Stay tuned!

Virtually Speaking Podcast: Host Deep Dive

Last Friday I had the honor to join Pete Flecha a.k.a. Pedro Arrow and John Nicholson on their always fantastic podcast Virtually Speaking. Together with Niels we talked about what it takes to write a book such as the VMware vSphere 6.5 Host Resources Deep Dive. Thanks John and Pete for having me on again. Check it out.

Exploring the Core Motivation of Writing a Book

More than a week ago Niels and I released the VMware vSphere 6.5 Host Resources Deep Dive and the community has welcomed it with open arms. The book is finding its way across the globe, from Argentina to New Zealand. To see the massive amounts of tweets praising the books brings us pride and joy.

Over the last couple of days, I have received many inquiries what it takes to write a book and if I could provide some hints and tips. I thought it might be an interesting blog post. Three questions you need to ask yourself

  1. What is my core motivation for wanting to write a book?
  2. What are you willing to give up for pursuing this goal?
  3. Do I have the platform to launch the book and capture and maintain the attention of the book/brand?

Core motivation
The first question you need to ask yourself is why exactly you want to write a book? An answer often heard is not money or fame. It’s typically a charitable cause, such as to educate the community or a stepping-stone for one’s career.

The last reason is by far the most likely one that will provide you the return on investment. People respond differently to you once they found out that you wrote a book. It shows dedication, it hints at mastery of a subject, it differentiates you from the rest. Nay-sayers will automatically point to the option of self-publishing, but they forget that the leading word in self-publishing is SELF. You have to do it all by yourself.

If money is your answer, then I need to burst that bubble. The chances are that the same amount of time spent working at the local supermarket will be more profitable. What I’ve learned with publishing five books, is that the creation of a single page takes approximately 90 minutes.

The sole exercise of writing 300 to 500 words does not take 90 minutes. It’s the second-guessing, the formatting and the phrasing that takes a lot of time. Once you write something down, thoughts will start to flow; they will lead to more questions, they will lead to second-guessing your initial idea. This leads you back to vendor collateral, academic papers, or testing in your lab. And you will hit writer’s block.

90 minutes is a good number to work with when you are in the planning phase of the book. We wrote 569 pages. 569 pages times 90 minutes equals 51210 minutes. That is 853,5 hours.

Money
This number leads to additional questions. But first, let’s answer the money question, this intertwines with the platform question.

How many books does one sell? Duncan and I sold over 75.000 copies of the vSphere clustering deep dive series. I know that the early Bible of virtualization; VMware ESX Server, Advanced Technical Design Guide by Scott Herold and Ron Oglesby sold approximately 30.000 copies. Both are exceptions to the rule. Most successful self-published books sell between 500 and 1500 copies. Let’s say you earn 5 dollars per book, and you sell 1500 copies, you receive 7500 dollars before tax. If you spend 700 hours on the book, you will make a little over 10 dollars an hour.

Self-publishing books provide more revenue to the author than using a publishing house. Published books by VMware Press or any other publisher house will get you into bookstores. Unfortunately, this will eat into your royalties.

Deadline
Those 700 hours need to come from somewhere, and because you are writing a tech book, you are bound to the time limit of the software version. It doesn’t make sense to publish a book about the previous version of the software, so you typically have one year of writing. If you have a day-time job, you need to spend times in the weekend and evening hours. Let’s say you keep the weekends for your friends and family and household chores. That leaves you with five evenings to write. If you write 3 hours a night, that means you are spending 233 consecutive workdays to write your book. Question yourself whether you or your loved ones will have this stamina?

What are you willing to give up
So that brings me to the second question, what are you willing to give up. I’m not saying divorce your spouse, but if you want to keep your family happy, you need to get the hours from something else. Gym time, drinking time, game time or sleep time. Typically all of the above, because sometimes you will get sick, or other responsibilities will get in the way. Going back to question one, is this worth the ˜10K you probably make? When you want to use it as a stepping stone for your career, the money is just a nice bonus.

Platform
If you want to educate the community, or you want to get more exposure, then you need to have a platform already in place. This platform can be a successful blog, a popular Twitter account or you are a regular on a podcast. Due to the maturity of this particular industry (virtualization) you need to be a regular in the community to have people accept your wisdom. There are a lot of people sharing their knowledge, some not always as correct as they believe. So ask yourself, why would anyone want to buy your book? Why should he believe you? Are you seen as an authority on a particular subject by the community? Just getting a book out and expect people will buy it because of the subject is, unfortunately, a thing of the past. There are a lot of books about virtualization on Amazon and people need an extra level of confirmation before they spend their money.

Find your niche and share your knowledge! But, before spending a lot of time on writing a book and getting disappointed by the sales result ask yourself. Am I an authority on a certain topic and does the community share the same perception? A book can certainly help built this image. But in general, people already need to understand that you know what you are talking about. How can you become one? Publishing articles on your blog or LinkedIn will help. Appear on podcasts such as Virtually Speaking Podcast or vBrownbag. And speak! Speak a lot at local and neighboring VMUGs. Hone your skill, so that you can shine at VMworld.

You need to harvest that popularity and keep riding that wave. That’s why you need to have that platform. Otherwise, it will be a short 15 minutes of fame. Popularity has a momentum. People will forget, and the attention to your new book will soon be pointed at another new thing. You need to provide a platform that can maintain that momentum. Write about the book, publish sections of the book on your blog, speak about it in podcasts. This allows you to create better and bigger things after your first book, maybe a second one.

As with everything in life, nothing is self-contained. It’s always intertwined with other elements. This blog post is not to discourage you from writing a book, but hopefully, helps you prepare to launch a successful book. There is a lot of work that needs to be done before releasing your knowledge in the form of a book. Don’t let my words discourage you. To paraphrase Nike: Just don’t quit!

Older posts

© 2017 frankdenneman.nl

Theme by Anders NorenUp ↑