Last night I was searching for a domain name for a new personal project that I would like to kick off. Personally, I don't find searching for a new domain name a fun thing to do. I wanted to see if I could find a domain name which is made up of a combination of words. Some of these include the terms tech, cloud, river, stream, sphere, and many others. As I started my search, I quickly came up with domain names that were already taken. I then decided to look at synonyms for some of these terms. It was at this point that I noticed something peculiar about the word "cloud". This is not a serious post, but just a bit of fun, so check this out:
This blog post has the potential to be a very controversial. I'm sure there will be many in the IT industry who will want to protest against a post like this, but there will also be others who would agree with this post.
Disclaimer: Following a review of the first draft of this article, and after careful consideration, I opted to remove about three paragraphs of text. The three pieces of text outlined some of the current buzzwords that drive some of us mad. It also included an extract of text from a website of a well known international consultancy (and no, it's not the one I work for ;-) ), that quite simply put, is a paragraph entirely formed out of BS buzzwords and phrases. You know, one of those monologues that consist of a lot of fancy buzzwords, but doesn't tell you anything. I decided to remove the text as I don't want this article to look like an attack on any individuals or organisations. I didn't mention any names of persons or organisations in this article, nor did I have any particular names in mind when I was writing the article. However, I am conscious of the fact that some people will be drawing conclusions. Therefore, any conclusions drawn by the reader are their own, and do not necessarily represent truth, or align with my intent with this article. You might also be reading some parts of this article and think "this guy is writing about my organisation!". Well, if you've been around the IT industry long enough, you will know that his issue is everywhere. No, it's not just your company. I'll place a bet that it is in every IT business out there.
Following on from my original vRetreat blog post, I thought it would make sense to report on some of the technical IT discussions that happened on the day, For this blog post, I am going to be focusing on the presentation by Darren Swift from Zerto.
So who and what is Zerto? Well, as started on the "About Zerto" page on their website, "Zerto provides enterprise-class disaster recovery and business continuity software specifically for virtualised datacenters and cloud environments."
In simple terms, Zerto provides hypervisor-level replication and automation with no hypervisor vendor-specific lock-in. It provides continuous replication (no snapshots) of virtual machines between hypervisors and replaces traditional array-based replication solutions that were not built to deal with virtualised environments.
I was honoured to have been invited to attend the inaugural vRetreat event in the UK. The event, arranged by Red-Track Ltd, took place at the Porsche Experience Centre at Silverstone on 27 January 2017, and was attended several well known bloggers and virtualisation community members. The day was made possible by Zerto, Veeam and Cohesity who presented on their respective products and upcoming capabilities within their product suites. This provided ample opportunity for those present to discuss several product features and their possible use cases in the world of hybrid and public cloud infrastructure.
Container technology has been around for quite a while now. Most people would by now have heard about Docker, and a lot of people are using Docker. What about VMware Photon? What’s that? Well again, I’d say that it’s been around for a while, however while people have been raving on about Docker and the container revolution, VMware has been working on their own implementation of container technologies as well as products that utilise and integrate with existing container technologies, such as Docker. At VMworld Europe 2016, VMware announced vSphere 6.5 and one feature that has caught my attention in this release (apart from the long overdue vSphere HTML5 Client) is vSphere Integrated Containers, or simply, VIC. At the moment I’m trying to make sense of all these technologies, how (and if) they fit together and where you would want to use each one.
I have identified an issue in Log Insight 2.5 where alerts passed via email or to vROPS contain the following text in the message:
“Notification event – The worker node sending this alert was unable to contact the standalone node. You may receive duplicate notifications for this alert.”
I also confirmed that DNS resolution and reverse lookup functions are working as expected. I was also able to reproduce this issue successfully in a lab environment, with DNS working correctly.