It would be interesting to find out how many recent college graduates in electronics engineering, computer science, or related fields expect to roll out their own silicon startup in the next five years compared to similar polls from ten or even twenty years ago. Our guess is that only a select few now would even consider the possibility in the near term.
The complexity of chip designs is growing, which means higher design costs, which thus limits the number of startups that can make a foray into the market. Estimates vary, but bringing a new chip to market can cost …
Could Algorithmic Accelerators Spur a Hardware Startup Revival? was written by Nicole Hemsoth at The Next Platform.
As part of a project on which I’m working, I’ve been spending some time working with Docker Machine and Vagrant over the last few days. You may recall that I first wrote about using these two tools together back in August 2015. As a result of spending some additional time with these tools—which I chose because I felt like they streamlined some work around this project—I’ve uncovered some additional information that I wanted to share with readers.
As a brief recap to the original article, I showed how you could use Vagrant to quickly and easily spin up a VM, then use Docker Machine’s generic driver to add it to Docker Machine, like this:
docker-machine create -d generic \
--generic-ssh-user vagrant \
--generic-ssh-key ~/.vagrant.d/insecure_private_key \
--generic-ip-address <IP address of VM> \
<name of VM>
This approach works fine if the Vagrant-created VM is reachable without port forwarding. What do I mean? In the past, the VMware provider for Vagrant used functionality in VMware Fusion or VMware Workstation to provide an RFC 1918-addressed network that had external access via network address translation (NAT). In Fusion, for example, this was the default “Share with my Mac” network. Thus, when Continue reading
Last week we released the latest beta for Docker Enterprise Edition. Without a doubt one of the most significant features in this release is providing a single management control plane for both Swarm and Kubernetes-based clusters – including clusters made up of both Swarm and Kubernetes workers. This offers customers unparalleled choice in how they manage both their traditional and cloud native applications.
When we were looking at doing this release we knew we couldn’t just slap a GUI on top of Kubernetes and call it good. We wanted to find areas where we could simplify and secure the deployment of applications onto Kubernetes nodes.
One such area is role-based access control (RBAC). Docker EE 17.06 introduced an enhanced RBAC solution that provided flexible and granular access controls across multiple teams and users. While Kubernetes first introduced a basic RBAC solution with the 1.6 release, in this upcoming release, we extend Docker EE’s existing RBAC support to support Kubernetes primitives.
(If you’re not familiar how RBAC works in Docker EE, please read my blog post from August 2017)
In addition to the five predefined authentication roles in Docker EE (view only, full control, none, etc) there are Continue reading
Despite IPv6, the transfer market for IPv4 addresses is thriving. An Interop ITX expert explains.
J Metz published a great article describing six hard truths not taught in school. As all good things should come in 7-tuples, here’s another one I was told ages ago when I was a young hotshot full of myself:
Professions were created for a reason – they enable people to do the work they’re qualified to do.
Needless to say, it took me decades to fully understand its implications.
Read more ...
The carrier has implemented NetFusion across its entire core.
As we’ve discussed in a previous blog post, it can be difficult to determine whether or not a vendor is truly as open as they claim to be. Sure, your network provider says they support open solutions, but the reality is they take advantage of open networking’s flexible definition to market not-so-flexible networks. How can you be certain that you’re investing in the open network your data center deserves?
Never fear, Gartner is here! Their report on gauging vendors’ openness provides you with five easy questions to help you take a machete to the forest of false advertisement. So, how does Cumulus Networks stack up to these requirements, and how have we maintained our dedication to open networking? Let’s take a look at Gartner’s criteria — we think you’ll find that this open model fits Cumulus like a glove.
We’ve broken down the qualifications for a simple solution into three parts. First of all, managing your network should be easy from the moment it comes online. Cumulus Linux is an operating system that ensures a simple start. A few features that guarantee a confusion-free beginning include:
It supports cloud storage at AWS, Microsoft, and Google, as well as object and file storage.