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: lab
Deploying 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
PCE Topology Notifications with OpenDaylight Helium
Helium SR3
OpenDaylight released its third maintenance release for Helium last month. Helium SR3 included a lot of bug fixes across OpenDaylight projects. In this blog, I would like to share my experience with PCE topology notifications available in SR3.
Notifications
The OpenDaylight controller sal-remote YANG model defines the RPC notification subscription service and data change notification constructs. Change-event notification subscription makes it possible to obtain notifications about data manipulations (inserting, changing, deleting) that are done on any specified part of any specified data store with specific scope.
PCE Topology Notifications
PCE topology notification is available in Helium SR3. This feature allows the user to subscribe to a notification stream and listen for asynchronous remote notifications through WebSocket. The changes that get notified are:
Test Setup
The setup has four routers running the IOS XRv 5.3 image, a CentOS 7 VM hosting OpenDaylight Helium SR3, and Packet Design’s SDN Service Assurance Platform acting Continue reading
The HP NFV Report Webinar will feature in-depth insights on real-world NFV use cases like those at Telefonica, what's new with the NFV market, and more. Sign up now!
It's time to sign up for the exclusive 6WIND DemoFriday, featuring insights and analysis to the recently released NFV Report! Register now!
80% of your job in networking is getting you and your co-worker to agree to what the terms mean.
That paraphrase comes from one of my three networking profs in college, from literally 30 years ago. But that statement is still true today. Getting to a shared understanding of what we mean helps in any conversation about networking, and failing to truly understand the terminology can cause problems.
SDN promises many things, but it certainly has a big impact on networking terminology. SDN introduces many new terms, but it also redefines some terms and reemphasizes the underlying concepts behind other long-used terms.
And then there are no terminology police to run around and make us all use terms the same way. It’s enough to drive you crazy!
Today’s post (and possibly a few more) explores some attempts to answer some of the questions about what SDN terms to use and what they mean. In this post, I’ll look at a relatively new Internet RFC: the SDN Layers and Architecture Terminology RFC.
What’s a network? Is it a class A, B, or C network, as defined by IPv4? Any subset of an IPv4 class A, Continue reading
You’re probably living in a bubble (or sleeping on a mat in the data center — remind me to tell you about the sleeping bag I carried in the back of my truck for a while…) if you’ve not heard about the Nokia/Alcatel merger. What’s interesting, from a network engineering perspective, is what this means. To get a better idea, it’s important to consider another story posted this last week.
The white box switching market could see some monumental change within even one year, according to Dell’Oro Group analyst Alan Weckel. That’s mainly because of the rise of hyperscale cloud players — specifically Amazon, Facebook, Google, and Microsoft. Their buying power has grown substantially in the past few years — and white boxes have progressed rapidly during that time, too.
So what does white box have to do with the Nokia/ALU merger? Just about everything, most likely. To better understand, we need to first posit that the world is going software. Not that we won’t have hardware any longer, but rather that the hardware is going to become much less interesting over the next five to ten years as the software used to run the hardware is separated out and Continue reading