Sunday, June 18, 2023

2023 Father's Day Reflection: AI Eats the World

Happy Father's Day!

Inspired by a thoughtful post by my Palo Alto Networks' leader Anand Oswal on LinkedIn, I am reminded that Father's Day is not just about fathers, but about all the people who play a pivotal role in the lives of fathers and whom fathers profoundly care for.

I recall a heartwarming moment last year when my mother and I were strolling in Palo Alto. She was thrilled to find an apple next to Steve Jobs' old house, a moment that symbolized how generations find joy differently; her joy in a simple apple mirrored my admiration for Apple's technology.

Now, with AI ushering in a transformative wave, as a father, my thoughts are on the future that lies ahead for the next generations. This AI-driven revolution is both thrilling and daunting, altering societal landscapes, and bringing forth a kaleidoscope of opportunities and challenges.

The immediate concerns, however, lie in the unsettling transition. We’re witnessing a paradigm shift in job markets and grappling with an archaic education system that’s not aligned with the forthcoming realities. It’s crucial we prepare our children for this enigmatic future.

Generative AI based ChatGPT gives away the following strategies to fathers and mothers out there:

  1. Encourage Adaptability: Emphasize the significance of adaptability and continual learning as the quintessence of thriving in a changing world.

  2. Cultivate Critical Thinking: Arm them with critical thinking and problem-solving skills, to navigate challenges resourcefully.

  3. Develop Emotional Intelligence: As AI takes center stage, the human touch and emotional intelligence will differentiate and define us.

  4. Participate in Educational Evolution: Engage with educational bodies to advocate for modern, relevant curricula that keep pace with technological advancements.

  5. Provide Mentorship: Be the guiding light for your children and facilitate access to mentors who can impart invaluable wisdom and experience.

  6. Instill Ethical Responsibility: Enlighten them on the ethical dimensions of technology, fostering a sense of accountability.

Wishing a Happy Father’s Day to all who are tirelessly shaping the future through their loved ones!

Tuesday, August 11, 2015

Larry Page declaring war on both corporate and human aging

52% of the year 2000 Fortune 500 companies no longer exist today -- why?  Just like humans have a life cycles, companies do too -- large companies cannot sustain success without continued innovation.  At the same time, it is extremely difficult for any large companies to keep innovating out of their comfort zones of existing business.


I had an opportunity to lead some of the most exciting cloud products in Cisco's history, yet I know first-hand how challenging (and rewarding!) it is to innovate within a large company.  There is always resource, business model, skillset, toolset, rewarding system, and most importantly mindset conflict between keeping established business happy vs. branching into new product areas.

Historically, "spin-xyz's" are some of the interesting answers for big companies to combat "Innovator's Dilemma".    For instance, Fairchild did a successful "spin-off" and created Intel, Cisco did a nice "spin-in" of Nuova and created a multi-billion dollar compute business from scratch, now Google apparently is trying out a new model, which I am calling it as "spin-up", with the Alphabet vs. Google announcement.

Time Magazine covered Google two years ago when Google started tackling the human aging problem with calico.  What was super amazing 24 hours ago was that Larry Page officially declared war over corporate aging too!!

Tuesday, August 4, 2015

Influence-by-Culture vs. Influence-by-Bureaucracy

One of the largest hi-tech companies on the planet now allows coworkers to see expense reports of each other's.  It is a brilliant move because it is always better to manage by peers than by process/managers, and it is always better to influence by culture than influence by bureaucracy/process.


As a leader, there are two methods to influence the troop:
  1. Influence via culture, lead by example, establish a "social norm", and leverage the bottom-up social control system; Or
  2. Influence via middle management, rely on the management team for practice/policy creation/enforcement, and leverage the "command and control".
These two methods are complementary to each other a great deal, however whenever it is possible, it is often more effective to manage the team via peer pressure (culture), than via command and control (bureaucracy).

When there is a great and cohesive culture, magic will often happen: expense reports will be done right, products will be designed better, and customer satisfaction will be higher too.

Legendary former CEO of IBM Lou Gerstner once said, "it took me to age 55 to figure that out, culture is everything."

Award-winning journalist Bryce Hoffman recorded Ford's turnaround story in his bestselling "American Iron", and he noted once, "The biggest and most important difference between Alan Mulally and his predecessors is that he attacked the root of the problem: Ford's corporate culture."

I personally lived through VMware's hyper growth period when we beat software giant Microsoft and grew from a start-up to a multi-billion dollar company.   I was often asked why we were able to build a superior product while Microsoft had lots of smart engineers too, and they had far more resources.

In my opinion, it is because we had a better engineering culture first and foremost -- the peer pressure we had, the social norm we lived by, the engineering day-to-day practice we followed, the laser focus we had in our execution, all of the culture stuff shaped us a great deal to deliver one of the most amazing products of the past decade.

While some "command and control" by middle management/bureaucracy is still necessary to provide scaling as well as check-and-balance, leaders should not forget about the magical wand of "influencing by culture".

PS: Special thanks to Stanford Professor Charles O’Reilly for my learning on culture from him!
PPS: While in theory there is no necessary correlation, but in practice there is a tendency to see more influence-by-culture in an "agile" team and more influence-by-bureaucracy in a "waterfall" team.



Saturday, June 27, 2015

Discrepancy In "Outcome" vs. "Satisfaction"

Most of us had some experiences in interviewing for a job and discussing the financial package with the manager/recruiter in the end.  It is super intriguing to learn how the dialogue itself makes such a tremendous impact to the final happiness level of the candidate ("satisfaction"), than the financial package numbers are able to impact ("outcome").


Non-intuitively at all, studies (*) have shown again and again and again, there is often even a big inversion between "outcome" and "satisfaction".   Higher financial package, more disgruntled employees? What's going on here?

And the million dollar question is how to get the upper hand in this process?

For instance, is it a good idea to make the first move for the salary number?  Conventional wisdom is first-mover loses, which is true in many cases.  But it depends on many many other factors, such as how thorough prep work either party has done, the personality of either party, the expectation of either party, so on and so on...

For another example, is it good idea to discuss the entire package together or discuss different line items seperately (base salary vs. sign-on bonus vs. relo pkg vs. start date vs. stock options vs. ...)?

Job offer negotiation is indeed an art.  I personally hired or attempted to hire hundreds of people into my organization over the years, and I can testify the existence of the "satisfaction/outcome inversion syndrome".  It is amazing for me personally, given my engineering/rationalness oriented mentality!:)

The more profound take-away is that, nothing discussed here is limited to the job offer negotiation.  Rather, it is about our everyday life, every negotiation, and frankly everything.

(*)  This post is about "job offer negotiation satisfaction", NOT "job satisfaction", which is a whole different topic.

Thursday, April 30, 2015

Disruption in Security Industry -- Reflection on RSA 2015

RSA 2015 was one of the best technology conferences I have been to in recent years.   Here are my top 3 observations:



Public admission that "the perimeter is gone".
    • Make no mistake about it, much of the security industry is still selling the "perimeter" boxes at the show big time, but I am impressed by the public acknowledgement nevertheless by the likes of RSA, Cisco, CA about the notion of "the perimeter is gone".
    • Perhaps perimeter's existence is a fallacy to begin with, but it takes a lot of courage from the "traditional" vendors to come forward and admit.
    • “The largest enterprises with the most sophisticated, ‘next-generation’ security tools were not able to stop miscreants from making off with millions of dollars, personal information, and sensitive secrets and damaging reputations,” Amit Yoran, the president of RSA, said in his keynote speech Tuesday.   
    • Amit's statement is profound and reflects the awkward state of the current the enterprise and data center. Disruption in security is about survival for the customers!
Amazing energy and advancing in "cloud security".

    • The energy is definitely moving away from the on-prem solution (remember the days where DPI is the biggest showing off moment not long ago?) but more onto solutions taking care of SaaS, public cloud security etc..  
    • One simply cannot take the on-prem security architecture to the cloud. Disruption in security is about architectural necessity.  
"Security DevOps" ain't just a dream.

    • I would have thought security team is the last one embracing devops/agile but it is safe to say I underestimated the progress so far.
    • Intuit guys blew me away with their learning through DevSecOps. 
    • Silos prohibits sharing and slows business things down. The disruption in security is as much about mentality shift as about technology transformation. 

Sunday, February 15, 2015

Dare Not To Blink

Last night was so special, not only because it was Valentine's Day, but also my son lost his first tooth.  To me it was a huge and completely unexpected milestone, because I feel like he, without any signal, suddenly became a "big boy".   I feel like I had not spent enough time with him in his little baby age, and now that stage has gone for good.


Software industry is the same.  Disruption happens super fast around us, and super unexpectedly.  "Software defined everything" moves so fast that no one can possibly claim catching every moment.

The key is to always keep the perspective on the high order bit big picture, reflect frequently on our amazing journey, and dare not to blink our eyes!

Monday, December 8, 2014

Good managers influence; Great leaders inspire!

I watched Simon Sinek's TED talk video of "How Great Leaders Inspire Action" and it immediately reminded me of an unforgettable personal learning experience I have had.



Many years ago, I hired a young engineer into my team.  He became a star player very quickly and delivered amazing results with all the complex problems I threw at him.  When one day he asked me what he could improve, the only thing I was able to tell him was to talk to customers and figure out more customer pain points.

Unfortunately, he resigned before long.  He told me that he was thankful to my great impact to this first job he had but he wanted to work for a company with a household name that his Mom knows.  In case you are laughing -- he was the very first attrition I ever had as a manager!  I don't know about others but I was completely devastated when I lost a person from my team for the first time and not to mention here's a star engineer.  It was truly a big sad deal to me personally!

I finally asked him a question point blank, "what made you to start thinking about a new job?"  He looked at me and said something I would never forget for the rest of my career. "Howie, remember you told me in our 1x1 to spend more time in talking to customers. But I'm just a programmer, I don't understand why it is my job to talk to customers and I'm afraid I could not live up to your expectation.  Just when I felt I was a bit lost, a good friend from Apple called me."

Wow... An engineer became vulnerable for another job because I was merely telling him "what" to do, and apparently did not connect/resonate with him on the "why" in his heart.  As a result, he became less certain and less engaged.   Certainly this experience profoundly changed how I engage with my team for years to come.

Many years later, I am watching Simon's TED talk and like his wisdom so much -- don't hire those people who can do the job but hire those who believe what you believe; inspiring leaders communicate with people on the purpose, belief, and cause first and foremost, and then the tactical "what" and "how".

Had I learned much earlier this one difference between managers who influence ("what" and "how") vs. leaders who inspire ("why"), perhaps there would have been one less devastated person on the planet? :)

Tuesday, September 30, 2014

Anniversary Reflection Chap 2: "Cloud First" Transformation

First off, Cisco's President Rob Lloyd announced today a number of Intercloud related news that my team has been working on last year:
  • Rob announced more than 30 new partners have been added for Cisco's InterCloud platform. The new partners include BT, Deutsche Telekom, NTT, and Equinix, and collectively bring 250 data centers in 50 countries.
  • Rob also announced the General Availability of Intercloud Fabric, a game-changing technology that enables seamless, secure workload mobility between public and private clouds—the foundation for hybrid cloud management. 

Secondly, some more colors about my own Intercloud Fabric engineering journey at Cisco.
  • To the external audience, the both simple and complex problem my team is solving:
    • On one hand, CIOs are unequivocally saying "I want cloud", but on the other hand CSOs are telling CIOs "slow down".
    • Intercloud Fabric is giving the peace of mind, visibility, control, and compliance back to the CSOs/CIOs, so that their journey towards a Hybrid Cloud can truly be accelerated.  A CTO from one of the top Fortune 500 (cannot say the name but it is synonymous to the copy machine) told us, "I can now migrate my data center in 6 months instead of 2 years."
  • To the internal audience, the very transformation my team is going through:
    • Just like a few other very successful hi-tech companies are going through, we would not have gone to where we are today and will not reach where we want to get to next few years without transforming our own engineering team.  
    • It is a challenging but very rewarding exercise.  The priorities and skillset requirements for the engineering tasks are morphing, the user experience expectation is changing very quickly, the R&D model needs to be a lot more "agile", and ultimately a "Cloud First" model.
Lastly, it is a humbling experience to see a semi-skunkworks project grow into the top initiative within Cisco and the entire industry.   This is precisely why I'm so passionate and proud of my team -- they are truly delivering something amazing that is making a profound impact to the entire cloud ecosystem.

Tuesday, September 2, 2014

Container Disrupting or Complementing VM?

Virtual Machine (VM) is the first class object within contemporary enterprise data center.  There have been great debates on whether Container "marks the death knell for virtualization" or is at the peak of "Gartner Hype Cycle".



My former VMware colleague Kit Colbert posted an insightful and educational blog on why VM and Container are "better together".  I very much agree with Kit that VM technology is complementing Container technology for now in many use cases, especially for those users who want to enjoy a cutting edge technology without sacrificing enterprise grade manageability/security/ecosystem.

However the billion question still remains -- whether in the long run Container could disrupt VM within Data Center?

Let's first look at VM vs. Windows, as they were "better together" but things have changed significantly.
  • A decade ago, Windows had quite comprehensive management story and far more better IHV/ISV ecosystem; VM/Hypervisor world offered little more than a "cool technology".   VM and Windows were "better together" because majority of the workloads were Windows friendly and VM was a great "passenger seat" tool. 
  • A decade later, VM/Hypervisor has disrupted Windows Server by commanding the "driver seat" in Private Cloud build-up.  Hypervisor is now a strategic data center control point than a "cool technology".
I believe Container has the same potential to disrupt the VM in the next decade just like VM disrupted Windows.
  • From technology perspective, Container has the potential to offer far more computing efficiency and agility. For instance, a few early adopter hosting providers are seeing 10x more density/efficiency in their environment (VM is an overkill for the type of services they provide and VM is in the way to do optimal "bin packing"). 
  • From ecosystem perspective, Container land enjoys some unbelievable developer attention right now.  I was shocked to see 7,000 projects on dockers in less than a year, and that number is already way outdated by the time of this blog. I also see the industry started giving attention to bare metal provisioning (e.g., Project Ironic) too.
  • From enabling new/exciting use case perspective, Container has the potential to allow users to get the better part of both Bare Metal machines and Virtual Machines. VMs offer great mobility, portability, and agility to the server workload today, but applications have lost the direct control and optimal use of the hardware. If the Bare Metal based Container technology can offer the same mobility/portability/agility PLUS the same rich ISV/IHV ecosystem PLUS the fact the new mobile-cloud era applications can take great/real advantage of controlling the hardware directly, then the ubiquitous nature of VM can be challenged at that point.
Obviously a LOT is yet to happen to make the Container disruption closer to real and transform Container from a "cool technology" to an "turnkey solution", we cannot claim the certainty of this disruption at this point.



The other night, my new friend Flo Leibert (CEO/Founder of Mesosphere) showed me his latest toy to help applications to easily specify real computing power needs (cycles, scheduling, locality, etc etc, rather than sandbagging big time in VM provisioning to compensate the virtualization indirection).   It is really hard for me to deny the amazing potential for the application focused Container technology to disrupt the x86 abstraction focused VM technology in the next decade with so much great work out of Docker, CoreOS, Mesosphsere...

The debate on Container will go on with or without my blog, but again the ultimate fate really depends on the execution of the Container industry next few years … :)

Sunday, August 24, 2014

Anniversary Reflection Chap 1: Nexus 1000V "Better Than Better"

I reached my anniversary at Cisco this month.:-)

Thanks to the amazing accomplishment of the 300+ talented engineers in my team, there is so much for me to reflect upon last year's journey.


The first installment of my reflection is on the Nexus 1000V (N1KV) product.  This product has a special position in my heart because I helped to build it up from ground up years ago when I was running the networking product team at VMware.  I will talk about other fantastic products from my team in the next few blogs.

N1KV has 10,000 customers already and last year my team gave a complete facelift for this product, mainly focusing on simplicity, scalability, and SDN functionality.


  • Awesome operational simplicity is achieved by abstracting out tons of traditional networking operational complexity into simple "container" like workflow.
    • Customers can now leverage Virtual Switch Update Manager (VSUM) to install or upgrade N1KV with a few mouse clicks without having to read pages and pages of manual, and better yet the new process is a lot less error prone.
    • Customers can also leverage Virtual Application Container Services (VACS) to set up application centric network policies with a few mouse clicks too, without having to learn all the Cisco product details including N1KV, VSG, PNSC, CSR 1000V, how all of them work together, how to install and configure them individually, etc etc..  Instead, admins can truly "do more with less" and have a peace of mind even when dealing with complex network add/remove/change requirements.
  • Scalability of N1KV has got a huge boost too. 
    • Some of the world's largest private cloud build-outs have already been leveraging N1KV but some of them want to run 1K+ ports on each physical server, and some want to have 10K+ ports per (VSM) controller domain.  We now have solutions to support this kind of scale.
    • More importantly, we support the above large scale while supporting full N1KV switching and security features.  This level of "full feature" scalability is unmatched by any other products in the market even though they might advertise similar or even higher scale numbers for the vanilla case.
  • Richer SDN functionality.
    • Customers can now extend ACI policies to vSphere hypervisor which is a big deal to many of the ACI adopters.  
    • When other products in the industry started to implement micro-segmentation in a virtualized environment, we have already advanced our product to the next generation so that the micro-segmentation applies to both virtual and physical workloads in a seamless manner.  
On top of the simplicity, scalability, and functionality, my team have also expanded the same vSphere N1KV product to cover KVM/OpenStack and Hyper-V land too so that customers can now manage the virtualized data center networking with heterogeneous hypervisor types under one consistent tool.  We are going to land N1KV in the container land next! :)

Exciting time for N1KV technology and exciting time for SDN industry as well!!

-howie
PS:  I'm looking forward to talking about this product family with customers, partners, and analysts this week at VMworld in San Francisco.

Tuesday, May 27, 2014

First "Hardware-less" Cisco Live

When Cisco's EVP/CDO Pankaj Patel finished the final keynote speech at Cisco Live last week, I could not help telling him that it is the first Cisco Live without any "boxes" on keynote stage! :)



I was one of the original then-VMware persons who brought up the concept of Cisco being a "network mainframe" company.   Let me say one thing however: it is actually an amazing accomplishment for both IBM and Cisco to be able to deliver complex computing and networking functionality and make the technology to "just work" in a mainframe form factor.   The only question is what's next after achieving this "mainframe status"?

Imagine if IBM had evolved S/360 mainframe into something that is easy to use, pay-as-you-go, flexible to access from anywhere, available and intuitive to be used by more than the elite few IT'ish folks, with open API and an open ecosystem, would IBM have lost the king of computing title quickly?  Today's "cloud" is essentially a large scale S/360 PLUS all the flexibility and XaaS "enhancement". IBM got trapped in the "innovator dilemma" unfortunately.

Cisco, on the other hand, is motivated to re-invent itself despite the tremendous success thus far.  Cisco's willingness/motivation to disrupt itself is a reason I joined Cisco last summer.  I'm glad that I am able to help to drive some of the most exciting new technologies highlighted at Cisco Live, including ACI and Intercloud.  Also happy to see that Cisco articulated a balanced, not a religious, approach between hardware vs. software, custom ASIC vs. merchant ASIC, on-prem vs. off-prem vs. hybrid cloud.

There is still a long way to go, for Cisco and the entire networking industry, to deliver comprehensive Cloud and SDN era networking benefits, but I was certainly excited to sit in a "hardware-less" keynotes audience. :)

Saturday, April 12, 2014

flipping mission critical infrastructure vs. swapping mobile phones

Goldman issued a very interesting report this week on SDN battle between Cisco and VMware.  There is one thing I like the report and one thing I "dislike" it (personal view point only, absolutely no representation of my employer):


  • I like the linkage that Cisco ACI vs. VMware NSX is like iPhone vs. Android-Phone.  
    • For one thing Cisco has owned "IOS" for decades but kidding aside, Cisco (ACI) provides customers an integrated vertical seamless solution.  VMware (NSX) provides customers more choice in hardware but nothing end-to-end from networking solution perspective.
    • My Cisco colleagues often remind me networking protocols are open for decades, from Ethernet to BGP.  It is very true, but unfortunately the perception on the street is Cisco is a closed solution company.  I am hopeful that the recent intro of the OpFlex policy model and work in open source community including OpenStack will help to change the perception.
  • I hope the assumption that "Cisco will garner about 30% market share in its SDN infrastructure software served addressable market by 2018" is not true however.  Why not 60% or more for Cisco?  
    • There will continue to be differentiation in hardware, but I cannot imagine Cisco will be the dominant networking company if it only has 30% of the SDN market shares 5 years from now.  There is frankly a tremendous amount of work Cisco needs to do to get out of the comfort zone of selling boxes, starting from having a sense of paranoia.
    • It is a huge uphill battle VMware needs to fight in order to convince enterprise customers to swap infrastructure just like some of them flipped Apple's iPhone to Samsung's Galaxy, because the switch cost and potential damage is too high.
I know my Android geek friends may laugh at me but I am a big Apple iOS fan as I have the peace of mind that someone else has thought through the end-to-end story, user experiences, and tested a heck out of it.  This is why I appreciate SDN products that e2e physical and virtual networking troubleshooting and visibility is designed in on day 1.

Sunday, February 2, 2014

From "Cisco Networkers" to "Cisco Live"

I just returned from Cisco Live Milan last week.  The previous time I attended the conference was in summer 2007 when I was representing VMware and the conference was still called "Cisco Networkers".


There has been a sea change in the conference:
  • 6 years ago at the solution exchange floor, most I saw were switches/routers and SNMP based network management software; 6 years later I saw some complete data center management stack, including end to end compute, network, storage, and management stack.
  • 6 years ago there was a first ever session on "virtualization", which was given by Jacob Jensen, then VMware's networking product manager who is currently running Nexus 9000 product; 6 years later, virtualization and cloud are part of the DNA of this conference.  Among many other things, the InterCloud product announcement showcased Cisco's ability to be thought leader in the cloud era.  
Networking is still an element of the conference obviously but it is no longer "THE" element.  Now I can see why the conference was renamed from "Cisco Networkers" to "Cisco Live".

Saturday, November 9, 2013

OpenStack Hong Kong 2013

I attended OpenStack conference for 2 days this week.  I have to say I was really impressed by the momentum behind OpenStack: 3,000 energetic people from 50 countries came all the way to Hong Kong! It smells like VMworld in the early days. :)




















Based on my experiences with OpenStack code base and various discussions with folks in HK, my assessment is OpenStack is still far away from the "prime time", despite so many companies went on stage touting their production deployment.   In my opinion, a lot of people use OpenStack because it is the only game in town for what they want to do -- I don't believe there is an equivalent commercial product. 

People often treat vSphere as the commercial alternative, but I look at OpenStack to vSphere just like NoSQL to Oracle -- OpenStack is solving a fairly different use case and targeting very different audience.  Just like Oracle was never designed for scale-out database, vSphere was not designed for the level of scale-out current OpenStack users want.

For those who put OpenStack in any serious deployment, they must have invested tremendous Dev cycles for the deployment.  So in a way, if you add up the Dev investment, it is not saving money, not today!  They use OpenStack as a framework not a turnkey solution, and build/modify things according to what their own needs.  The base distribution is not quite "complete" at this point, for instance, among other things, the it does not have an installer today and the TripleO project is targeted for 2014.

Finally, I believe the availability of the source code, the relatively meritocracy based community with lots of passion, and the momentum/sexiness of the brand name do give people a lot of imagination on the potential. I suspect by the end of 2014, we will see OpenStack distribution with enough bells and whistles for those who cannot afford to invest their own "Dev" cycles.

Wednesday, August 7, 2013

Software Defined Job Move

News always travels fast on SDNCentral and virtualization.info.  I started at Cisco this week and will manage all of Cisco's Cloud Networking and Services Group engineering team and execution.

I'm tremendously excited about this new journey for two reasons:
  1. Network virtualization is getting mainstream and Cisco is one of the key players in this transition.  I see Cisco offer some unique technical domain expertise, deep physical and virtual integration, broad product portfolios and ecosystem partnership, and solid presence with the customer.  
  2. I'm joining a team that I have collaborated closely from my VMware tenure and I've known a lot of folks here well, from engineers to executives.  I have a lot of confidence in what this team can accomplish and I also anticipate to learn a lot out of this journey.

Thanks to an extremely talented team at Big Switch Networks where I spent two years and learned a great deal from each person there.  Thanks to good wishes sent from former co-workers at BSN and VMware and other industry friends.   Networking industry is at an interesting time and our passion in bettering it is absolutely worthwhile.

I'm looking forward to contributing my energy and experiences at Cisco, learning new things everyday, and collaborating with folks both inside and outside Cisco on this worthy cause.

-Howie
PS: Opinions on this blog does NOT represent my current (or former) employer.

Sunday, May 19, 2013

OpenDaylight


On April 15,  Gartner released a report titled "OpenDaylight Project Casts Cloud Over SDN Deployment".   Mark Fabbi and Joe Skorupa highlighted the following: "The OpenDaylight Project will likely delay the adoption of enterprise software-defined networking solutions and stifle innovation from smaller, SDN-focused startups with open SDN-based applications and related capabilities."




One month later on May 15, Cisco called out its "leadership in the OpenDaylight project" in the quarterly earning call.

Some people compared OpenDaylight with OpenStack.  Was Gartner telling us that OpenStack was formed to combat incumbents while OpenDaylight was formed to combat start-ups?  Interesting time for both incumbents and start-ups.

Sunday, May 5, 2013

Traditional Network Vendors Advancing Switching

In the past few days, I've seen a lot of new product announcement from the switch vendors.  I am pasting a few Network World article links below as they cover the news quite well.  My overall impression is as follows:

  • Progress is impressive, but still very much a "speeds and feeds" game.  Density is ever more important in the "flat network" era.  Overall, the big differentiation is on the HDN not SDN.
  • When it comes to SDN, OpenFlow and OpenStack are important part of their story
  • HP finally has a virtual switch story with its 5900v after Cisco Nexus 1000V and IBM 5000v roll-out.  This is about 4-5 years behind the first mover.

Happy to hear your thoughts too?  Have a nice weekend,

-howie



Arista: http://www.networkworld.com/news/2013/050113-arista-269279.html
    . "The 7500E is a 30Tbps, 14 billion packets/sec non-blocking switch housed in the same 11 RU chassis as the 7500. Densities per chassis are 1,152 10G, 288 40G or 96 100G Ethernet."
    . $10k for each 100G!

HP: http://www.networkworld.com/news/2013/043013-hp-sdn-269254.html
    . "HP also unveiled a virtual switch to run under server hypervisors. The FlexFabric Virtual Switch 5900v supports the IEEE's Ethernet Virtual Bridging -- a.k.a. "VEPA" -- standard for offloading some switching capabilities from the server to a physical switch. The 5900v is optimized for VMware environments and supports mobility and management of network policies for virtual machines
configured through VMware hypervisors."
    . FlexFabric 5,900 ToR, added VEPA
    . FlexFabric 11,908 aggregation switch, 64 40G, OF1.3, 768 10G and
256 40G, TRILL/SPB
    . FlexFabric 12,900 core

Brocade: http://www.networkworld.com/news/2013/043013-brocade-data-center-269231.html
    . vRouter from Vyatte and OpenStack Plug-in

Juniper: http://www.networkworld.com/news/2013/032513-juniper-sdn-268073.html
    . EX9200 based on MX technology/asic, Juniper's 40/100G play (likely will limit Juniper's QFabric data center switch to 10G-only)

    . Separately they announced JunosV based on Contrail technology, leveraging XMPP.  Juniper is pushing XMPP into Open Daylight as well.

Cisco's Insieme Business Unit (no public announcement yet):
   . a fixed 36x40 Gigabit Ethernet (GbE) device;
   . a modular devices supporting 288 40G;
   . a modular devices supporting 576 40G;
   . a SND controller supporting those fabric switches

Saturday, April 20, 2013

SDN Career

In the last 3 months alone, about 1,000 engineers sent us their resumes.  As the VP Engineer, it is a humbling experience with many world class talents interested in changing the network world with us together.

I was at Open Network Summit exhibit last week.  I ran into quite some Cisco or Juniper engineers who literally took vacation and paid the conference out of their own pockets just to observe the SDN industry first hand and evaluate their career options.



So what's the ground truth I'm telling the candidates and what should SDN job candidates out there want to know whichever company they have interests?

1) SDN: Hype or Real?

It is a complete hype for those who think SDN is curing cancer; and it is completely real for those who have come to realization the status quo networking technology is a mainframe technology.  For others, it is somewhere in between.

Honestly don't even waste your time in agonizing on "whether" SDN will make it, it is going to happen no matter what.  One may argue which particular established or start-up company is going to lead it.


2) VMware's acquisition of Nicira: good or bad?

It is both a blessing and curse frankly.  It is a blessing because customers started questioning HDN way more than before.  It is a curse because the huge price tag artificially fast forwarded the customer expectation on SDN industry maturity by 2-3 years.  VMware was able to develop and mature its technology a decade ago without much distraction from the crazy press and blogsphere world, whereas everyone is watching closely the "VMware for the Networking" companies.

For now, the "fast forwarding" has not helped the industry in general.  It created misleading perception on the stage the industry is in, how mature the economic model is, how soon the liquidation event shall happen, and when customers are ready to adopt it in mass.


3) Open Daylight Consortium: good or bad?

The "Open" part is good, assuming the consortium lives up to its meritocracy promise, as it gives Big Switch Networks and everyone an opportunity.  The "Consortium" is naturally suspicious as historically there have been more failure than not in 90% of the "Consortium".  Finally the "light" naming must be perfect, especially after Big Switch has set the de facto standard by launching two SDN "lights" earlier ("Floodlight" and "Switch Light"). :-)

Overall it is not yet the time to make any judgment.  My colleague Jason Matlof said recently, "We are cautiously optimistic, with an emphasis on cautious.”


4) Who are the players in this space?


Mostly importantly, we are at the beginning of the SDN journey, the "lead" by anyone today is not meaningful yet.  The team that has the best talent, approach, and execution focus will earn the winning in the future.  That said, a few thoughts on some of the obvious players:
  • Cisco is the indisputable leader in networking technology but now has to react to SDN.  Dave Ward shared Cisco's perspectives on OpenFlow and SDN in a fairly technical and thoughtful way lately.  Then there is also Insieme.  Given the proven track record of MPLS team, Insieme will get both internal mind share and external market share.   Insieme is not a start-up and it is a Cisco BU with special purpose and special treatment.  The employees sit in the same Cisco cubicles, drink the same tap water, have access to the same code, employee directory, and bug system, have the same customer account.  They will deliver a differentiated HDN solution with a nice SDN angle.
  • VMware pioneered in overlay networking in the past decade (Akimbi's Network Fencing, Nicira's NVP, and VMware's DVS, VXLAN, vCNI) and they fundamentally want to absorb as much networking functions to the server land as possible.  It is a very logical strategy given VMware is fundamentally a server  infrastructure company and the key thing to watch out is how much they leverage from the legacy networking partners.  Too much and too little won't accomplish their mission.
  • The aspiration Big Switch has is to bridge the server and networking domains and keep CCIEs relevant but in a different way.  Few SDN pure players have the similar ambition to own an end to end stack from applications, to SDN Controller, all the way to virtual and physical switching stack.

Tuesday, October 2, 2012

SDN Myth? My take ...


As usual, I enjoy reading my friend Matthew Palmer's thought provoking blog quite a bit!  Matt listed 5 myths and here is my take:



1) In theory everyone should have a controller, yet it is a bit like saying HP/IBM/Dell etc server companies in theory need an OS too.  In practice, customers look for a controller that is not the single point of failure, not a single point of performance bottleneck, and providing additional/clear value than the status quo physical switch embedded stack.

2) At the end of the day, what matters is how the Open Source project is governed not just how it is licensed.  People are always willing to pay for value but what they don't want is a vendor lock-in scenario where the dominant player can literally name the price.

3) I agree to an extent, at least for the ones Matt and I often talked about. :)  I think we should set the expectation appropriately at the first place: network virtualization use case in particular is an exciting journey for both customers and vendors but we are at the very beginning of it as an industry.

4) The goal for a start-up is to have a solid product with indisputable value prop, VC should take care of cash flow issue for them, so positive or not should not be a concern at all for those who have a good product.  I don't know whether big companies want cash flow positive for their SDN P&L? Probably not either, it is too early.

5) I think the most important thing is we need to look at the big picture of why people are moving. Talent shift from one generation of hi-tech companies to another for technology transition.
Just like people left SGI/DEC for Google/VMware at the turn of the century, we are seeing people leaving from previously top engineering organization to the "next Google/VMware".  Big Switch Networks benefited tremendously from this talent migration shift given the networking industry needs a transformation desperately and many top engineers are hungry to make a big impact in this SDN journey.