dcdesignmyths1

Reducing risk & faster deployment of services

RELIABILITY - The answer to the automation question is always reliability. Speed of ops doesn't matter, if you're only speeding up problems.

The objectives of IT should not change. Automation is a how. Not a why. It lets us deliver more reliable and secure services so that work can be done.

We should be focusing on automation's benefits in ensuring closed-loop real-time predictive remediation of system, network, and applciation issues before they become showstoppers.

Automation should be used to reduce the operational burden. To allow the ops team to automate the day to day tasks

As always, the answer depends. The equipment would need to be capable of some sort of IP Fabric features, I imagine. Perhaps EVPN VXLAN as that's the way the industry is going. Legacy also means applications, keep in mind. We need to bring forward legacy in all pillars.

It depends on how you define legacy. Legacy could be as simple as connectivity BMS servers to your network and extending there connectivity via a gateway to a cloud service

Does that answer your question?

We have clients with their core applications still running to legacy systems of more than 20 years old if more. Therefore for those clients we have first to move them from their local network to a virtual network and then upgrade to cloud.

Yeah, totally, which is why EVPN VXLAN helps us bridge that gap between legacy and future. We can handle layer 2 applications with the scalability of a layer 3 infrastructure

You need a coherent approach for both underlay and overlay

Software Defined Networking will become more the norm. In order to have one way to manage things we need to abstract in both the public and private cloud. #multicloud

The trend to multicloud is driving the trend toward software-defined data centers that can flexibly span private and public clouds, with seamless movement of data, apps, and workloads between them behind a virtualization layer.

More things to work together as many new solutions to bring together,

really invormative interview@plburris

The definition of multiple-cloud will need to change to include private clouds at the end. This will be especially true for IoT instances.

Beyond connectivity, enterprise networking will leverage orchestration, visibility and security as they move to #multicloud

@dfloyer Agree... once one begins to think about the implications of multicloud, one starts to recognize how broad the changes might be

They think it's simpler than it is

They believe everyone is already using SDN and Public Cloud

part of the misunderstanding is that it needs to be a total forklifting of current equipment. Which should be totally untrue.

Brand new will fix when there's a lot of existing to interoperate with.

There's also a belief that applications don't need to change or don't need to be a part of the change. Really all of the DC silos need to go through a transformation and hopefully a collaboration!

The greatest myth is that the only purpose of a network is to move data. The purpose is to manage the connection of data to people and things.

They believe a single vendor can solve all of their problems. In fact, Multicloud is Multivendor

@dfloyer Great point, David. We so often forget what's behind the purpose of the data center. Good to keep the human element in mind.

That the network is always getting in the way, slowing down new services deployments - it doesn't have to right?

The top myth of enterprise networks is that they exist to manage connections among servers, databases, and applications. In fact, they exist to ensure service levels to sustain knowledge worker productivity 24x7.

The second myth is that the cost of moving data is trivial. Moving data is expensive. Moving large amounts of data takes a long time. In general, it is easier and cheaper to move the compute to the data.

@jameskobielus We actually consider that to be really important. Thinking about things like customer satisfaction and application responsiveness is really important.

@dfloyer Especially when it comes to public cloud! We need to be very careful when designing for our multicloud futures.

good stuff dude, thanks alot !! @alamontagne