Cisco acquires Skyport Systems to bolster its hybrid cloud positioning

For today’s IT professional, hybrid clouds are a fact of life and will be for years to come. Digital businesses need to have an agile infrastructure foundation, which the cloud provides.However, rarely does one size fit all when it comes to cloud options. Some workloads are ideally suited for public cloud services, while others make more sense to go in a private cloud. With some apps, though, part of it runs in the traditional data center and part runs in a public cloud, such as Amazon Web Services (AWS), Microsoft Azure or Google Cloud Platform. There are also apps that run in a private data center but then need to connect to a SaaS application.To read this article in full, please click here

Episode 20 – Cloud Connectivity

The flexibility of cloud infrastructure has had a significant impact on the way that organizations build out their infrastructure, but the industry is continuing to learn just how complicated connecting to cloud resources can be.  In this episode of Network Collective we take a look at the challenges around cloud connectivity and talk about some ways to do it well.


Miguel Villareal
Guest
Scott Wheeler
Guest

Jordan Martin
Co-Host
Eyvonne Sharp
Co-Host


Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/

The post Episode 20 – Cloud Connectivity appeared first on Network Collective.

Energy Giant Eni Starts Investing In Supercomputers Again

Energy is not free, not even to energy companies, and so they are just as concerned with being efficient with their supercomputers as the most penny pinching hyperscaler or cloud builder where the computing is the product.

Like the other major oil and gas producers on Earth, the last few years have not been easy ones for Ente Nazionale Idrocarburi, the Italian energy major that employs 33,000 people and operates in 76 countries worldwide and now has the distinction of having the most powerful supercomputer in the energy sector – and indeed, among all kinds of commercial entities in the

Energy Giant Eni Starts Investing In Supercomputers Again was written by Timothy Prickett Morgan at The Next Platform.

Responding to Readers: How are these thing discovered?

A while back I posted on section 10 routing loops; Daniel responded to the post with this comment:

I am curious how these things are discovered. You said that this is a contrived example, but I assume researchers have some sort of methodology to discover issues like this. I am sure some things have been found through operational mishap, but is there some “standardized” way of testing graph logic for the possibility of loops? I trust this is much easier to do today than even a decade ago.

You would think there would be some organized way to discover these kinds of routing loops, something every researcher and/or protocol designer might follow. The reality is far different—there is no systematic way that I know of to find this sort of problem. What happens, in real life, is that people with a lot of experience at the intersection of protocol design, the bounds of different ways of finding loop free paths (solving the loop free path problem), and a lot of experience in deploying and operating a network using these protocols, will figure these things out because they know enough about the solution space to look for them in the first Continue reading

Call for Nominations now open for Rob Blokzijl Award

In remembrance of Internet Pioneer, founder and Chair of RIPE for 25 years, Postel Award recipient, and friend, Rob Blokzijl the RIPE NCC set up the “Rob Blokzijl Foundation”. The foundation recognises those who made substantial and sustained technical and operational contributions to the development of the Internet in the RIPE NCC service region, or supported or enabled others with the development of the Internet in the RIPE NCC service region.

The Rob Blokzijl Award will be awarded for the first time during RIPE 76 in May 2018. This is a Good Thing on so many levels.

The call for nominations is now open. The deadline is 16 March 2018 23:59 UTC.


Image credit: Olaf Kolkman

The post Call for Nominations now open for Rob Blokzijl Award appeared first on Internet Society.

Could Algorithmic Accelerators Spur a Hardware Startup Revival?

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.

HPE partners with Portworx for easier Kubernetes deployment

Hewlett Packard Enterprise (HPE) has partnered with Kubernetes container vendor Portworx to provide a reference configuration for enterprises to launch stateful container workloads on Kubernetes.Containers are a lightweight form of virtualization, where just what is needed is loaded rather than the full operating system like in a virtualized environment. Docker was the first with containers, but it has been steamrolled by Kubernetes, which was developed by Google. Google just had way more resources to bring to bear than Docker, a startup that has relied on venture funding.Also on Network World: Will containers kill the virtual machine? One of the big changes as containers have evolved is adopting the stateful condition. Initially they were stateless, meaning the data was erased from memory when the container was shut down at the completion of its workload. Stateful applications, on the other hand, are services that require retention of data, usually through a connection to a back-end database so they have persistent storage.To read this article in full, please click here

An Update on Using Docker Machine with Vagrant

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

Role-based Access Control for Kubernetes with Docker EE

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