In my travels, I am fortunate to see new and interesting innovations, emerging technologies and trends. Of course, the growth of mobile and cloud technologies continues to shape our work and lives. 2014 will be a year that builds on the momentum of these trends, along with IoT, with more connected people, processes data and things than ever before. Here’s my take on the most significant things we’ll see in 2014.
1. Increasing urgency to manage our zettabyte-driven world.
The proliferation of mobile devices, streaming video and explosion of applications has meant that global IP traffic has exploded more than 4x in the past 5 years. IP traffic will again triple over the next 5 years. In 2013, we generated a momentous 1.2 zettabytes of new information and 70 billion apps were downloaded. Wireless traffic will exceed wired traffic and video-on-demand traffic will nearly triple in three years.
I am neither an AC Milan soccer fan nor a connoisseur of haute couture, so it will be no surprise if you wondered what I am doing in Europe’s fashion capital Milan, and that too in the middle of Milan’s wintry January.
Without further ado, I will break the suspense. Yes, I am one of the few, chosen as Cisco Datacenter leads for the Cisco Live Milan event. You may be thinking I have the best job in Silicon Valley, as I hop from Melbourne to London to Milan to cover Cisco Live worldwide, over the years. You are right, I do have an enviable job, bringing together the best of cisco datacenter technologies that help customers achieve more value for their investment, and I also make sure to have some fun in the process. During this event, I will be bringing you real-time excerpts of the action in the show floor, via social media. In this blog, I want to provide all you Datacenter IT and Networking professionals, highlights of various activities we have on the menu.
If like me you are fortunate to attend, I am sure you are looking forward to attend the wall-wall keynotes on Jan 28, hosted by Cisco Executives Rob Lloyd and Rob Soderbery. Rob Lloyd will discuss how Cisco and the ecosystem of Cisco’s partners are uniquely positioned to connect the unconnected with an open standard and an integrated architecture from the cloud to end devices In addition, you’ll have the opportunity to check out the latest innovations in Cisco ACI and Data Center Networking technologies. Let us pick up action at the Cisco Campus and Datacenter area in the World of Solutions.
Cisco ACI demos are at the center of all action in Datacenter switching. .These demos in particular highlight the growing significance of Cisco as a datacenter infrastructure provider. With the successful introduction of Cisco ACI and its seamless integration with Cisco UCS, FlexPod, vBlock, UCS Director etc, we are able to demonstrate why infrastructure matters and its relevance to applications. I strongly encourage you to check out the Cisco ACI-Open Stack demo that highlights the provisioning and orchestration of a multi-tenant cloud environment and virtual applications through Open Stack, as well as showing integration of Open Stack on top of the Cisco APIC interface. Many of you have been eagerly awaiting the integration of L4-L7 services from Citrix, F5 with Cisco APIC, and we have put together a demo that illustrates the set-up and insertion of multiple network services into an application network, and the routing of traffic to the required services and the virtual workload. Other ACI demos include those that showcase Cisco Nexus 9000 platform programmability and Cisco ACI integration with Hyper-v, but in the interest of time, I will let you discover the exciting details of these demos at your convenience. Besides ACI, we have Unified Fabric based demos focusing on Nexus 7k and Dynamic Fabric Automation, VXLAN integration with Nexus switching platforms etc, to illustrate the comprehensive portfolio of switching products from Cisco. You will not be disappointed at the demo floor as the best and brightest engineers from Cisco business units will be available to engage you in technical conversations.
Florida Polytechnic University Vice President and CIO Tom Hull joined Cisco Vice President Pat Finn via TelePresence at the CSN Tech Connection at the College of Southern Nevada on January 15th.
As Florida Polytechnic University’s Chief Information Officer, my job is to ensure the University uses modern and emerging technologies to offer our students experiential learning opportunities. The higher education industry is undergoing a paradigm shift in which technology for teaching and learning is a part of the educational ecosystem and something that students expect. At Florida Poly, we need to use these technologies to give students the best learning experience possible.
Our Vision for the Future
Florida Poly’s vision is to be a bright star in the high-tech corridor we’re building in Central Florida, creating a Silicon Valley-like environment. We’re going to accomplish this vision by building an extremely modern campus (probably the most modern in the United States) with technologically advanced features available to students and faculty. In addition to the features our campus itself will offer, we have applied research, a bright faculty leading advanced programs and higher education partnerships with industry organizations to help us accomplish our mission and vision.
Our university’s architecture will be student-centric, and our technological foundation will be a Florida Poly cloud that includes all emerging technology in the world of higher education. This cloud will be accessible to both students and faculty and will feature a student information system that will provide an easy way for students, faculty and staff to obtain resources. This cloud will also include a virtual library environment that has access to digital databases and research repositories, essentially replacing the traditional library system. Read More »
More and more enterprises are managing distributed infrastructures and applications that need to share data. This data sharing can be viewed as data flows that connect (and flow through) multiple applications. Applications are partly managed on-premise, and partly in (multiple) off-premise clouds. Cloud infrastructures need to elastically scale over multiple data centers and software defined networking (SDN) is providing more network flexibility and dynamism. With the advent of the Internet of Things (IoT) the need to share data between applications, sensors, infrastructure and people (specifically on the edge) will only increase. This raises fundamental questions on how we develop scalable distributed systems: How to manage the flow of events (data flows)? How to facilitate a frictionless integration of new components into the distributed systems and the various data flows in a scalable manner? What primitives do we need, to support the variety of protocols? A term that is often mentioned within this context is Reactive Programming, a programming paradigm focusing on data flows and the automated propagation of change. The reactive programming trend is partly fueled by event driven architectures and standards such as for example XMPP, RabbitMQ, MQTT, DDS.
One way to think about distributed systems (complementary to the reactive programming paradigm) is through the concept of a shared (distributed) data fabric (akin to the shared memory model concept). An example of such a shared data fabric is Tuple spaces, developed in the 1980’s. You can view the data fabric as a collection of (distributed) nodes that provides a uniform data layer to the applications. The data fabric would be a basic building block, on which you can build for example a messaging service by having applications (consumers) putting data in the fabric, and other applications (subscribers) getting the data from the fabric. Similarly such a data fabric can function as a cache, where a producer (for example a database) would put data into the fabric but associates this to a certain policy (e.g. remove after 1 hour, or remove if exceeding certain storage conditions). The concept of a data fabric enables applications to be developed and deployed independently from each other (zero-knowledge) as they only communicate via the data fabric publishing and subscribing to messages in an asynchronous and data driven way.
The goal of the fabric is to offer an infrastructure platform to develop and connect applications without applications having to (independently) implement sets of basic primitives like security, guaranteed delivery, routing of messages, data consistency, availability, etc… and free up time of the developer to focus on the core functionality of the application. This implies that the distributed data fabric is not only a simple data store or messaging bus, but has a set of primitives to support easier and more agile application development.
Such a fabric should be deployable on servers and other devices like for example routers and switches (potentially building on top of a Fog infrastructure). The fabric should be distributed and scalable: adding new nodes should re-balance the fabric. The fabric can span multiple storage media (in-memory, flash, SSD, HDD, …). Storage is transparent to the application (developer), and applications should be able to determine (as a policy) what level of storage they require for certain data. Policies are a fundamental aspect of the data fabric. Some other examples of policies are: (1) time (length) data should remain in the fabric, (2) what type of applications can access particular data in the fabric (security), (3) data locality, the fabric is distributed, but sometimes we know in advance that data produced by one application will be consumed by another that is relative close to the producer.
It is unlikely that there will be one protocol or transportation layer for all applications and infrastructures. The data fabric should therefore be capable to support multiple protocols and transportation layers, and support mappings of well-known data store standards (such as object-relational mapping)
The data fabric can be queried, to enable discovery and correlation of data by applications, and support widely used processing paradigms, such as map-reduce enabling applications to bring processing to the data nodes.
It is unrealistic to assume that there will be one data fabric. Instead there will be multiple data fabrics managed by multiple companies and entities (similar to the network). Data fabrics should therefore be connected with each other through gateways creating a “fabric of fabrics” were needed.
This distributed data fabric can be viewed as a set interconnected nodes. For large data fabrics (many nodes) it will not be possible to connect each node with all other nodes without sacrificing performance or scalability, instead a connection overlay and smart routing algorithms are needed (for example a distributed hash tables) to ensure scalability and performance of this distributed data fabric. The data fabric can be further optimized by coupling this fabric (and its logical connection overlay) to the underlying (virtual) network infrastructure and exploit this knowledge to further optimize the data fabric to power IoT, Cloud and SDN infrastructures.
Special thanks to Gary Berger and Roque Gagliano for their discussions and insights on this subject.
Happy New Year! We’re kicking off the year strong with this very special international episode of Engineers Unplugged. Matthew Yeager (@mpyeager) and Juan Manuel Rey (@reypo) discuss cloud adoption in Europe and how the terms get lost in translation, but maintain a key focus: customers.
**The next shoot is last week of January at Cisco Live in Milan! If you want to be internet-famous, contact me ASAP to talk about being on the show.**
This is Engineers Unplugged, where technologists talk to each other the way they know best, with a whiteboard. The rules are simple:
Episodes will publish weekly (or as close to it as we can manage)