Cloud software company Avni has shipped its first product.
Anycast networks are a pretty interesting way to fix quite a few issues with networked services that involve needing global spread. One of the interesting things is that a computer cannot really tell (unless it h
The speed and scope of DevOps just broadens the network security problem.
When’s the last time you had the opportunity to learn about a new area of technology? Not just the latest API but something big. With the emergence of open networking, now may be the time to do just that.
Open networking is becoming more wide spread in data centers, partly because of CapEx savings and customer choice from disaggregation of hardware and software. From an operational standpoint, the efficiencies of automating and managing switches like servers may be even more compelling. Those efficiencies – and resulting OpEx savings – are from using a real Linux OS for the network.
As a Linux operating system running network switches, Cumulus Linux presents a learning opportunity for two specific groups of users: network administrators who are new to Linux, and Linux administrators who are new to networking. Open networking represents a radical improvement in network management, but as with most major changes, there’s a learning curve.
Leaving IOS, NX-OS, or JunOS for Cumulus Linux means rediscovering how to perform tasks that network administrators have been doing the same way for years. This often means tweaking existing knowledge to understand where familiar commands Continue reading
Learn how service providers can reposition themselves as “lifelines” to the cloud for enterprise customers.
In this post I’d like to share a couple of things I recently learned about the interaction between cloud-init and OpenStack Orchestration (aka “Heat”). This may be stuff that you already know, but in the interest of helping others who may not know I’m posting it here.
One issue that I’d been repeatedly running into was an apparent “failure” on the part of Heat to properly apply cloud-init configurations to deployed Ubuntu instances. So, using a Heat template with an OS::Nova::Server resource defined like this would result in an instance that apparently wasn’t reachable via SSH (I’d get back Permission denied (publickey)):
resources:
instance0:
type: OS::Nova::Server
properties:
name: cloud-init-test-01
image: { get_param: image_id }
flavor: m1.xsmall
networks:
- port: { get_resource: instance0_port0 }
key_name: labDeploying an instance manually from the same image worked perfectly. So what was the deal?
The first thing I learned was that, in some circumstances (more on this in a moment) defaults to injecting SSH keys (like the key named lab specified in the template) to a user account named “ec2-user”. Ah! I’d been using the default “ubuntu” account specified in Continue reading