On Policy in the Data Center: Congress

By Tim Hinrichs and Scott Lowe with contributions from Alex Yip, Dmitri Kalintsev, and Peter Balland

(Note: this post is also cross-published at RuleYourCloud.com, a new site focused on policy.)

In the first few parts of this series, we discussed the policy problem, we outlined dimensions of the solution space, and we gave a brief overview of the existing OpenStack policy efforts. In this post we do a deep dive into one of the (not yet incubated) OpenStack policy efforts: Congress.

Overview

Remember that to solve the policy problem, people take ideas in their head about how the data center ought to behave (“policy”) and codify them in a language the computer system can understand. That is, the policy problem is really a programming languages problem. Not surprisingly Congress is, at its core, a policy language plus an implementation of that language.

Congress is a standard cloud service; you install it on a server, give it some inputs, and interact with it via a RESTful API. Congress has two kinds of inputs:

  • The other cloud services you’d like it to manage (for example, a compute manager like OpenStack Nova and a network manager like OpenStack Continue reading

PlexxiPulse—Reflections in Networking

2014 was a busy year in networking, and our friend Marcia Savage did a great job of summarizing the industry highs and lows – from ACI to white box switches – this week in a slideshow for Network Computing. It’s definitely worth a read before you head out for the weekend. Check out Marcia’s year end wrap up below as well as other happenings in the networking space this week.

In this week’s PlexxiTube video of the week, Dan Bachman explains how Plexxi incorporates optical transport into datacenter transport fabrics.

Computer Weekly: Cisco is missing the transition to software-defined networks
By Alex Scroxton
Little doubt remains that the future of networking will be defined by software, but market-watchers warn Cisco is missing this move. Cisco’s hardware forms the backbone of most enterprise networks around the world. But this world is changing and many buyers no longer see compute, storage and networking as distinct silos… Software-defined networking (SDN) company Plexxi, which recently appointed former EMC executive Richard Napolitano as its CEO, is one such company looking at the networking industry’s transition from networking towards an application and data-focused world. “We stand today at a transition point in the IT landscape,” says Continue reading

Basic Python Multithreading

The first ‘proper’ Python app I made logged onto a list of devices and pulled out OSPF state. This worked perfectly fine. The app correctly works out whether it can log into a device or not, and waits a few seconds to ensure a device actually responds. The issue is that if I have a […]

Big Switch Chaos Monkey Network Testing

Whenever you build a complex system, you need to test that it works as expected, including properly handling failures. It’s easy enough to do simple component failure testing, but harder to do rapid automated failure tests. Big Switch is showing that it can be done though. Hopefully we can keep improving our testing to pick up some more of the software failures.

Testing is hard

Over the course of my career I’ve built many clustered systems – HP-UX Serviceguard, firewalls, routers, load balancers, RedHat Clusters, etc. Good clusters have redundant everything – servers, power supplies, disks, NICs, etc.

The commissioning process always included testing. We’d go through each of the components, trying to simulate failures. Unplug each of the power cables, the network cables, unseat a hard drive, remove a hot-swappable fan, etc. That would test out the redundant components within each server, and then of course you’d simulate a complete system failure, forcing full failover.

This is all important stuff, but it doesn’t pick up all the failures – e.g. What happens if you’ve got a faulty patch lead, and the link starts flapping? Sometimes a simple failure gets messy when it happens repeatedly over a short Continue reading

phpipam 1.1.010 update released

phpipam 1.1.010 update released with following fixes:

== 1.1.010

Bugfixes:
----------------------------
+ Fixed login fails with LDAP when escape characters are in password;
+ Fixed login not working with spaces in password for AD login;
+ Fixed Ivalid action when adding vlans from subnet popup menu;
+ Fixed custom fields not appearing properly on IP request editing;
+ Fixed Invalid ID error for IP address details on sorting;
+ Fixed warnings if no VLAN search results are present;
+ Fixed test mail not sending;
+ Fixed unable to login if $phpsessname not defined;
+ Fixed unable to login after upgrade;

I apologise for any inconvenience some users experienced with upgrade.

brm

Show 216 – HP & SDN In The Campus – Sponsored

At HP Discover Barcelona 2014, the Packet Pushers had the chance to chat with Heather Giovanni, Craig Mills, and Chris Young about the HP 5400R and SDN in the campus. HP has a full line of switches and routers that some know about, and some just haven’t yet explored. The 5400R is a multi-slot chassis […]

Author information

Ethan Banks

Ethan Banks, CCIE #20655, has been managing networks for higher ed, government, financials and high tech since 1995. Ethan co-hosts the Packet Pushers Podcast, which has seen over 2M downloads and reaches over 10K listeners. With whatever time is left, Ethan writes for fun & profit, studies for certifications, and enjoys science fiction. @ecbanks

The post Show 216 – HP & SDN In The Campus – Sponsored appeared first on Packet Pushers Podcast and was written by Ethan Banks.

CoreOS – Getting your second (and 3rd) host online

Quick note: For the sake of things formatting correctly on the blog I’m using a lot of screenshots of config files rather than the actual text.  All of the text for the cloud-configs can be found on my github account here – https://github.com/jonlangemak/coreos/

Now that we have our first CoreOS host online we can start the cool stuff.  We’re going to pick up where we left off in my last post with our first installed CoreOS host which we called ‘coreOS1’.  Recall we had started with a very basic cloud-config that looked something like this…

image

All this really did was get us up and running with a DHCP address and the base system services running.  Since we’re looking to do a bit more in this post, we need to add some sections to the cloud-config.  Namely, I’m going to configure a static IP address for the host, configure and start etcd, and configure and start fleet.  So here’s what my new cloud config for coreOS1 will look like…

image

So there’s a lot more in this cloud-config.  This config certainly deserves some explaining.  However, in this post, I want to just get Continue reading

3 Ways To Get Started With VMware NSX

Over the past 12 months, VMware NSX momentum has continued to grow, as we’ve added VMware NSXnew platform capabilities, expanded our partner ecosystem, and of course, had more than 250+ customers purchase NSX for deployment. And as interest in VMware NSX has grown with both customers and IT professionals looking to evolve their careers by adding certification in network virtualization, one of the most common questions that we get is “How can I get started with NSX?.”

We understand that there is a strong demand for individuals and organizations to get their hands on the NSX technology. Many of you are working towards your initial VCP-NV certification. Others of you are exploring NSX as a way to improve your organization’s agility and security while reducing overall costs.

Here are three ways individuals and companies can get started with NSX.

Complete NSX: Install, Configure, Manage Training – for individuals on the NSX career path, we offer “NSX: Install, Configure, Manage” training.  We are offering ICM training as part of our On-Demand Curriculum, or you can take a 5-day instructor led course. Here is the detailed course description and class schedule. ICM training is a pre-requisite for VMware NSX certification. Once Continue reading

2014 in review

Looking back at 2014, it feels like a lot of progress was achieved in the past year in both the cloud infrastructure and NFV infrastructure markets. Some of that progress is technical, some is in terms of increased understanding of the key business and technical aspects. This post is my attempt to capture some changes I’ve observed from my particular vantage point.

This December marks the second anniversary of the acquisition of Contrail Systems by Juniper Networks. In the last year the Contrail team managed to deploy the Contrail network virtualization solution in several marquee customers; to solidify the image of the OpenContrail project as a production-ready implementation of the AWS VPC functionality; but, probably, more importantly to help transform attitudes at Juniper (and in the industry) regarding NFV.

In the late 90s and early naughts, the carrier wireline business went through a significant change with the deployment of provider managed virtual networks (using BGP L3VPN). From a business perspective, this was essentially outsourcing the network connectivity for distributed enterprises. Instead of a mesh of frame relay circuits managed by the enterprise; carriers provide a managed service that includes the circuit but also the IP connectivity. This is a service Continue reading

Will I Be Blogging Again?

Dan wrote in with a question:

Hey, I like your site as well… are you going to be doing any more posts? It just seems odd that your last blog post was the analyzation of the site and how it portends to your future work. anyway, good luck

I know it’s tacky to write a blog post about how you’re not writing enough blog posts… but here goes.

Yes, I will be blogging again. And I have lots of content ideas. And I’m actually itching to get back to writing. I’ve been working on something else for the past few months and I decided I couldn’t take that on and blog at the same time. So for now my writing is on hold, however I do see and respond to all comments in the articles and am reachable via email as well.

Thanks to everyone who reads and posts comments. I look forward to writing more posts in the new year!


Copyright Joel Knight. All Rights Reserved.
www.packetmischief.ca

The Resolvers We Use

The theme of a workshop, held at the start of December 2014 in Hong Kong, was the considerations of further scaling of the root server system, and the 1½ day workshop was scoped in the form of consideration of approaches to that of the default activity of adding further anycast instances of the existing 13 root server anycast constellations. This was a workshop operating on at least three levels. Firstly there was the overt agenda of working through a number of proposed approaches that could improve the services provided by the DNS root service. The second was an unspoken agenda concerned with protecting the DNS from potential national measures that would “fragment” the DNS name space into a number of spaces, which includes, but by no means not limited to, the DNS blocking activities that occur at national levels. The third level, and an even less acknowledged agenda, is that there are various groups who want to claim a seat at the Root Server table.

More education needed to realize the Internet of Everything

The Internet of Everything (IoE) is essentially about connections, bringing people, processes, data and things together in unprecedented ways. IoE delivers the right information to the right person (or machine) at the right time, and converts data into intelligence to make better decisions.

Organizations will use the connections made by IoE to transform our work and private lives, creating smarter products and services, more convenience for consumers and new forms of work-life integration. However, in order to capitalize on these connections, organizations will need well-trained staff. Cisco predicts that approximately 220,000 new engineers will be needed globally every year for the next 10 years to keep up with the technological surge of IoE. This is a gap that must be filled if the potential of IoE is to be realized.

To read this article in full or to leave a comment, please click here

iWARP update advances RDMA over Ethernet for data center and cloud networks

The challenge for data center operators selecting a high performance transport technology for their network is striking the ideal balance between acquisition, deployment and management costs, and support for high performance capabilities such as the remote direct memory access (RDMA) protocol.

The iWARP protocol is the open Internet Engineering Task Force (IETF) standard for RDMA over Ethernet, and offers an interchangeable, RDMA verbs-compliant alternative to specialized fabrics such as InfiniBand. iWARP adapters are fully supported within the Open Fabrics Alliance Enterprise software distribution (OFED), with typically no changes needed for applications to migrate from InfiniBand to Ethernet.

To read this article in full or to leave a comment, please click here