See How Juniper’s VP of IT Approaches the Business
The network of the future starts with Edward Wustenhoff and his team at Juniper.
In his role as VP of Infrastructure and Platform Services at Juniper Networks, Edward Wustenhoff is working to define and reshape what infrastructure operations means. His team applies their learnings managing the network to help Juniper product teams create a better experience for customers.
Tune into this video to learn how he approaches infrastructure management and defines success — and also why he’s a big fan of Iron Man.
You’ll learn
How Edward defines success when it comes to infrastructure operations
A real-world example of his approach to infrastructure management, and what to look for in the next two videos in this series
Who is this for?
Host
Transcript
0:00 [Music]
0:00 foreign
0:00 [Music]
0:06 vice president of infrastructure and
0:09 platform Services here at Juniper it
0:11 I've done a lot of cool stuff at
0:13 companies like sun Microsystems Netflix
0:15 complete genomics and even served as CTO
0:18 at birthstone
0:19 one thing you should know about Amino
0:21 I'm a big fan of Iron Man particularly
0:24 his Workshop even though he's a handsome
0:26 billionaire
0:27 but his Workshop represents in my
0:29 opinion how the future should look like
0:32 in building new technology
0:34 in the movies we see Tony Stark solving
0:37 complex problems easily visualizing them
0:40 with cool holographs and Building
0:42 Solutions in the snap isn't that
0:44 something we all would want
0:46 but this is important he also has help
0:48 Jarvis his artificial intelligent
0:51 that one runs testing scenarios handling
0:55 time-consuming work and so Ironman can
0:59 you know save the world
1:01 and I believe
1:02 that Workshop is a great analogy on how
1:05 I look at it and it infrastructure
1:09 I bring that attitude into my role here
1:11 at Juniper managing the availability
1:13 security performance economics and
1:16 change also known as aspects of
1:19 infrastructure with disbelief
1:21 a huge part of my job is defining and
1:24 reshaping what infrastructure operations
1:26 really means and so I specifically
1:29 defined this job as managing the aspects
1:31 because it avoids getting into debates
1:34 about whether devops or ITIL is better
1:36 both exist to solve the same thing
1:39 managing availability security
1:41 performance economics and change but
1:44 they do it in entirely different ways
1:46 I also deliberately scope the
1:49 infrastructure as compute storage
1:51 Network and data center Services because
1:54 no matter how you deploy it you know
1:56 private Cloud hybrid Cloud
1:58 do-it-yourself you still have to manage
2:01 the aspects of the page but depending on
2:04 the deployment model there might be a
2:06 different way to do that best
2:09 managing those Services successfully
2:11 always requires a combination of
2:13 Technology people and process so it's
2:16 not either or but sometimes you need
2:19 more people sometimes you need less
2:21 process but preferably you use as much
2:24 technology and automation as you can
2:26 because you avoid errors it just depends
2:29 on what you're managing and where you
2:32 are in the product life cycle
2:35 that is what I do for Juniper and we
2:37 apply our learnings managing Network to
2:40 help the product teams create a better
2:42 experience for our customers
2:44 so how do I define success well my
2:47 mission is to deliver successful
2:49 infrastructure services and for me that
2:51 means services that add value of high
2:54 quality easy to consume and deliver it
2:57 fast and in a timely fashion the key to
3:01 do that is standardizing ensure you can
3:03 force people to use your services by
3:05 edict but if you don't meet those four
3:07 goals you failed
3:10 however when you do meet your four goals
3:12 people will compel to use it even if
3:15 it's not a perfect fit for what they're
3:17 trying to achieve
3:19 this is a good thing because it
3:21 naturally limits the sprawl of custom
3:23 services and helps improve standard
3:25 Services allowing for a frictionless way
3:28 to standardize your service portfolio
3:31 so let me give you an example
3:33 let's say a team needs a database for a
3:37 business defining project
3:39 they are looking at database o but it is
3:42 not a standard service that we are
3:44 currently delivering and it would take
3:46 about a month to build and you know ten
3:48 thousand dollars to buy however we can
3:51 provide our standard database p as a
3:54 service maybe not a perfect fit but it
3:57 does do the job it's of high quality
3:59 easily deployed quickly my experience is
4:03 that 90 95 of the time people will opt
4:06 to use database P because the team is
4:09 not out to build a perfect database it's
4:12 out to deliver value to the business
4:15 of course if the database o does add a
4:18 specific value and is being asked for
4:20 frequently one should consider building
4:22 a standard service for that and now that
4:25 you know a little bit more about me and
4:26 my Approach I'd like to invite you into
4:29 my workshop to see how the team at
4:31 Juniper is using Juniper technology and
4:33 the above principles to create and run
4:36 the network of the future I'll be
4:38 sharing real world examples and how we
4:41 are solving some of our company's
4:43 biggest challenges by creating a more
4:45 sustainable infrastructure dealing with
4:47 public versus private cloud and
4:49 implementing access points across tens
4:52 of thousands of offices
4:54 with that let's make it happen I'll see
4:57 you soon
