HPE and Aruba Networks are merging their businesses. What does this mean for customers?
The post PQ Show 70 – The HPE-Aruba Networks Merger – How Is That Going To Work? appeared first on Packet Pushers.
HPE and Aruba Networks are merging their businesses. What does this mean for customers?
The post PQ Show 70 – The HPE-Aruba Networks Merger – How Is That Going To Work? appeared first on Packet Pushers.
The controller supports transport-to-packet network layers.
A Candlestick Phone (image courtesy of Wikipedia)
Greg Ferro (@EtherealMind) posted a thought provoking article about collaboration in his Human Infrastructure magazine (which you should be reading). He talks about the death of IP Telephony and the rise of asynchronous communications methods like Slack. He’s got a very interesting point of view. I just happen to disagree with a few of his assertions.
Greg’s stance that IP Telephony is dead is a bit pointed to say the least. He is correct that the market isn’t growing. It is also true that a great number of new workers entering the workforce prefer to use their smartphones for communications, especially the asynchronous kind. However, desk phones are a huge part of corporate communications going forward.
IT shops have a stilted and bizarre world view. If you have a workforce that has to be mobile, whether it be for making service calls or going to customer sites for visits, you have a disproportionately large number of mobile users for sure. But what about organizations that don’t have large mobile populations? What about financial firms or law offices or hospitals? What about retail organizations? These Continue reading
The post Worth Reading: Intel & the Data Collector of Things appeared first on 'net work.
Learn from the top NFV PoCs, manage, and orchestrate NFV-based managed services with Versa's January 27th webinar!
I have a rather motley collection of links this week roaming over security, social media, and algorithms. First up is three interesting reads on social media, some of which isn’t very technical, but it’s tangential to technology, so I still get to post them here. Since beginning work in earnest on a PhD in philosophy, I’ve been paying a lot more attention to stories in this realm, and thinking about how these things impact us as people and our culture at large.
First up, a prediction that Facebook is going to die because it’s a “garbage dump.” I’m not a huge user of Facebook, so I really don’t pay attention to what goes on there (which is probably why if you’ve tried to friend me there, I’ve not answered — I rarely look at requests, and almost never approve them).
It’s important for communication channels to keep their signal to noise ratio Continue reading
Although vendor-written, this contributed piece does not advocate a position that is particular to the author’s employer and has been edited and approved by Network World editors.
Most companies now use a range of cloud applications, and uptime performance for those applications is measured by Service Level Agreements (SLAs). These agreements acknowledge that glitches, system crashes and downtime have an enormous impact on business continuity and can adversely affect customer loyalty and churn. Gartner estimates downtime can cost major corporations as much as $100,000 per hour.
To read this article in full or to leave a comment, please click here
After a year of work, we are extremely proud to announce that Ansible 2.0 has been released and is now generally available. This is by far one of the most ambitious Ansible releases to date, and it reflects an enormous amount of work by the community, which continues to amaze me. Approximately 300 users have contributed code to what has been known as “v2” for some time, and 500 users have contributed code to modules since the last major Ansible release.
There are many pitfalls to refactoring software, so why did we decide to tackle such a major project? At the time we started the work on v2, Ansible was approximately three years old and had recently crossed the 1,000 contributor mark. This huge rate in growth also resulted in a degree of technical debt in the code, which was beginning to show as we continued to add features.
Ultimately, we decided it was worth it to take a step back and rework some aspects of the codebase which had been prone to having features bolted on without a clear-cut architectural vision. We also rewrote from scratch much of the code which was responsible Continue reading
After a year of work, we are extremely proud to announce that Ansible 2.0 ("Over the Hills and Far Away") has been released and is now generally available. This is by far one of the most ambitious Ansible releases to date, and it reflects an enormous amount of work by the community, which continues to amaze me. Approximately 300 users have contributed code to what has been known as “v2” for some time, and 500 users have contributed code to modules since the last major Ansible release.
There are many pitfalls to refactoring software, so why did we decide to tackle such a major project? At the time we started the work on v2, Ansible was approximately three years old and had recently crossed the 1,000 contributor mark. This huge rate in growth also resulted in a degree of technical debt in the code, which was beginning to show as we continued to add features.
Ultimately, we decided it was worth it to take a step back and rework some aspects of the codebase which had been prone to having features bolted on without a clear-cut architectural vision. We also rewrote from scratch much Continue reading