An Important Class of IoT Devices

nternet of Things (IoT) refers to a large class of devices that can be sprinkled throughout a region of activity where we'd like the sensors to capture detailed information about the interesting region. The 'region' could be a farmland, a bridge, railroad tracks, structural parts of aircraft, and almost anything where there is interest to understand any measurable activity. The sensors achieve particular value if they are completely passive, i.e., do not require battery or any power that requires manual replenishment. The sensors are able to provide important site-specific data than can then be transmitted over the Internet, stored, analyzed, and harvested for important macro observations that could be gleaned from such data, sometimes also known as Big Data.

Virtual Networking and Clouds.

Recently, in a blog post written by Chris Marino, titled Virtual Networking, It’s Not Just a VLAN…, I came across a beautiful definition of what a virtual network is:

"A virtual network is a network you control that runs on top of another network that you don’t control."

The Action behind Clouds: Cisco's Acquisition of LineSider.

Clouds are good for cloud subscribers, but how can cloud providers offer on-the-fly provisioning such as is expected by the subscribers? Clearly, requests¹ for Infrastructure as a Service (IaaS) at a subscriber level — a certain combination of CPU, networking and storage — must be translated down to device-level, actionable, commands to both physical and virtual devices. And, these commands need to be effected as a single transaction in the cloud provider system. Cisco's intent last week, to acquire LineSider Technologies, brings this matter to the fore.

LineSider's white paper on Network Services Virtualization elaborates on the challenges by bringing out the limitations of point² products of the following types:

1. Configuration Management and Automation Engines
2. Inventory and Capacity Management
3. Network Alarm and Correlation Management

Their OverDrive product "... automatically initiates the creation of the required virtual machines (VMs). As the VMs are coming online the OverDrive virtualization engine defines and deploys the network access and security models across all required infrastructure devices (routers, switches, firewalls) as needed, to deliver the Cloud service to the defined end-users. The entire process is completed in seconds ...". Moreover, "Once the Business Policy is implemented and the Cloud service is active, the access and security models are bound to the end-point resources and persisted in the OverDrive engine."

What is the moral of the story? While it is important to create point technologies for the cloud, it is also important to think about their manageability in an 'end-to-end' scenario: The cloud subscriber is one of the ends, and the cloud provider is the other end, with all the devices in between — physical or virtual — associated with the cloud service in a persistent, auditable, manner.

---

¹Requests for cloud services are equally well applicable to both private enterprise cloud subscribers and public cloud subscribers.

²What were once 'end-to-end' solutions become 'point' solutions in an evolving system.