SAN JOSE, Calif. and San Francisco – March 24, 2015 – Taos, a national provider of infrastructure services, announced today the creation of an alliance partnership with Digital Realty Trust, Inc. (NYSE: DLR). The alliance allows Taos to customize solutions that combine premier data center space with services and expertise in architecting and managing hybrid clouds. Digital Realty’s global presence and commitment to success made for a seamless and complementary partnership. With no overlap in services, the alliance allows each organization to deliver a comprehensive, robust infrastructure solution.
Geeky + bccs,
I just finished reading “The Innovators” by Walter Isaacson: http://www.amazon.com/dp/147670869X/. You might know the author from his biographies of Albert Einstein and/or Steve Jobbs. I really enjoyed this book and recommend it, particularly for anybody with any interest in technology, especially computer and communication technologies.
Much of the book focuses on teams that complimented each other. Just to share one anecdote that surprised me – all the earliest programmers were women. It seems this “tradition” started because all the early “calculators” were women – seemingly a low prestige profession.
This past week, I had the honor of being invited to speak at SaltConf 2015. I additionally was asked to serve on a panel that discussed using multiple configuration management systems in the same environment.
The panel got me thinking about what DevOps in 2015 means (from a technical sense; the cultural shifts and methodologies will have to wait for another blog post someday!). I believe I’ve narrowed it down to four primitives, which I term the Four Horsemen of DevOps. Since I was at SaltConf, I was naturally thinking in terms of Saltstack. It struck me that each one of these four primitives is served rather well by various Saltstack components.
Like most consultants who’ve been in the game for more than a year or two, I periodically receive opportunities to “convert” to being a full time employee, either with our clients or from third parties who’ve heard of me through the grapevine. It’s always flattering, I always appreciate the gesture, and I always politely decline the offer.
Why? On the face of it, this doesn’t make a whole lot of sense. As a consultant, I generally don’t get the chance to gain equity in my clients. Compensation generally takes the form of cash rather than an ownership stake, and as for the rest of the typical fringe benefit suite? Forget it! As a consultant, I frequently find myself sitting next to the printer breathing toner. (“Sorry about that, it was the last available seat we had…”)
Historically, operating systems in the UNIX and UNIX-like family have not only been incredibly stable, but have also been trailblazers in technology. Some have been more renowned for using what’s become tried and true– as well as being slow moving targets that are easier to support. Those in the latter category have at times had a fear of change when seemingly too sudden or divergent from their current standing, but change isn’t always bad. Sometimes it’s just simply that: change, and in the case of SysV Init, the change has been a long time coming.
It’s the beginning of a New Year, time to make those New Year’s resolutions: lose weight, eat more vegetables, write that novel, travel to Europe, get that colonoscopy, etc. But as we all know, doing new things is hard; perhaps stopping things we are already doing is easier, a sort of Anti-Resolution. So I propose these anti-resolutions for IT professionals in 2015:
Stop generating non-actionable alerts: How many alerts have you ignored or deleted from your inbox today? “Alert Fatigue” is a common operations malady. Not only does it waste time and attention, but could drown out relevant alerts that need real attention. This is one of the easiest anti-resolutions: just turn them off.
Stop asking stupid security questions: Commonly used as an attempt to reduce password reset requests or as a cost-saving substitute for multi-factor authentication, security questions fail because people are no better at remembering the answers than their passwords. “What was the name of your first pet?” is a question I would have a hard time answering the first time, let alone later when I needed to reset my password.
Exchange 2013 Native Data Protection relies on built-in high availability features to protect the mailbox data, without the use of traditional backups when deployed and configured correctly.
However, here is my question. Without using a traditional backup, is just using the built-in HA in Exchange 2013 enough to satisfy data restore and disaster recovery requirements? When determining if Exchange 2013 allows you to move away from traditional point-in-time backups, we should consider the cost of end-user downtime and data loss when attempting to recover from a disaster using the existing backup infrastructure, in addition to include hardware and license costs associated with the traditional backups.
In the aftermath of the past year’s publicized security incidents such as the Target malware, Home Depot hack and now Sony Entertainment’s troubles, we continue to be reminded that technology is only one part of the play. On the stage we also have others such as the users, other businesses, management and system administrators. All play a part in the opera of business, but one area can accelerate or destroy a performance quickly.
Think of technology as the stage, lights and props for a play. They may have been purchased or created to fill a particular need in the play. However while where they are placed, how and when they are used is usually set in the script, it is the stage manager or director who creates the flow and works to ensure the pieces are where they are needed and when.
All too often, we either accidentally check yes to install a program or even install a program on purpose, only to have it start at every logon. This can be a waste of resources and in one case caused me numerous headaches. One time, I initiated a wsus offline install of updates. It did the installs but then began to start at each start-up causing a reboot, it would go through this loop and not stop. I ended up having to manually stop the process on each boot up. As you can see, this can be quite annoying.