A few weeks ago, I was at Cisco Open Source Conference 2013 – a conference hosted by Cisco where we had speakers from IBM, Canonical, Red Hat and Rackspace, among others. I learned a lot, specifically about the evolution of Hadoop and the OpenStack project. As a follow on, I collated different activities around Cisco UCS and OpenStack, which I will share in this blog.
Dr. Dan Frye, Vice President, Open Systems Development, IBM, head of the IBM Linux Technology Center (LTC) gave the keynote address at the conference. It was nostalgic considering the fact that I sat in the same aisle as some of the LTC team members in the IBM facility in Austin, a few years ago. His talk included some fascinating historical anecdotes and three lessons IBM learned about open source software development-
- “Develop in the open” (Don’t try to contribute finished software products, heed to feedback)
- “Don’t reinvent the penguin” (“Scratch your own itch” – interesting phrase to explain the behavior of communities which want to solve the problems at hand and not those perceived to be problems by external entities)
- “Work with the process” (The community process is usually an agile methodology with no assumptions on roadmaps and delivery dates)
These lessons are invaluable in light of the open source projects such as OpenDaylight (no pun intended) and OpenStack that Cisco is now an integral part of. According to Dr. Frye, these newer open source consortiums have the following characteristics:
- Larger number of initial members
- Quick starts
- Relatively large initial budgets
- Often require the commitment of a specified level of FTEs
Chris Wright from Red Hat expanded upon the principles and ethos of open source projects including release early, release often, iterative development and the culture of giving back. He contrasted the Linux kernel development project with the OpenStack project showing the relative speed of projects with the number of developers and commits by release. He gave a fantastic overview of the various Openstack component projects. He also identified two newly graduated projects namely, Ceilometer and Heat in the Grizzly release. I gave a talk on the requirements for the Ceilometer project, and you can find the slide deck on slideshare.
After attending the conference, I looked for projects within Cisco, which used OpenStack or contributed to it. Cisco is a major contributor to the soon to Read More »
Tags: Cisco UCS, Cisco UCS API, OpenStack, quantum, UCSM
On Tuesday May 28, 2013 at 17:30 UTC a massive pharmaceutical-based spam campaign began, using the Subject: header “Only 24 Hours Left to Shop!”. Cisco witnessed volume rates peaking as high as 8 out of every 10 spam messages being sent. The indiscriminate nature of the attack’s recipients suggests that most anti-spam vendors, including Cisco, will have blocked this attack very quickly.
Read More »
Tags: security, spam, TRAC
Cisco Corporate Social Responsibility (CSR) is one of the sponsors of the Social Innovation Summit (SIS) at the United Nations in New York City this week. The summit connects global leaders in the corporate, investment, government, and nonprofit sectors and helps them collaborate to multiply the positive impact they can make in the world. The agenda includes presentations and discussions on key strategies and best practices for creating social transformation.
Cisco’s approach to creating positive social change has long involved collaboration with our partners and peers. By combining the power of human and technology networks, Cisco multiplies impact and helps accomplish extraordinary things, even under the most difficult circumstances.
Read More »
Tags: mobile technology, social entrepreneur, social innovation, social innovation summit, United Nations
In my previous blog, I talked about building out a lab to help with IPv6 integration testing. It cannot be understated how important it is to test any new feature that is going to be deployed on the network. This statement is true independent of the feature involved. In this case, we are talking about IPv6, but we could just as easily be talking about virtualization or BYOD.
So now that we have the lab build up in progress, what’s next? Read More »
Tags: ipv4, IPv6, Lab testing, RIPE
I recently kicked off a series about security and the Internet of Everything, a pivotal topic that starts with the roots of IoE, IoT and M2M, which I explore in more depth in the first post.
Machine-to-Machine connections make up a huge portion of the Internet of Things, both general concepts for the network infrastructures that link physical and virtual objects. These abstractions come together on IoE, making it possible for devices to orchestrate and manage the world we live in, as they become connected entities themselves.
But to fully discuss security on the Internet of Everything, we must first go back to the roots of IoE itself. The technology innovations that employ M2M and IoT were actually spun off from military and industrial supply chain applications. As IP became a more common communication protocol, IoT gained more traction, helped even more by the creation of IPv6 and other advancements in wireless technology. As ever-increasing data is captured and distributed on these networks, more intelligence is generated.
Read my full “Securing the Internet of Everything: An Introduction” blog post to learn more about this embedded intelligence that is a core architectural component of IoT, and how it informs the security for the Internet of Everything itself. And stay tuned! I have more for you to come in this series, including a look into IoE security framework.
Tags: analytics, architecture, internet, Internet of Everything, internet of things, IoE, IoT, ip, IPv6, M2M, Service Provider, sms