1
00:00:00,000 --> 00:00:03,920
we have something that they call heavy trash pickup you have heavy trash pickup in your neck

2
00:00:03,920 --> 00:00:08,480
of the woods we can call an order and they'll come and pick up a couch or a you know an extra

3
00:00:08,480 --> 00:00:12,900
kit or whatever else we stick on the curb wow that's fancy living i mean you guys have like

4
00:00:12,900 --> 00:00:18,700
composting or you folks have like composting up there right do you have that as well uh no i just

5
00:00:18,700 --> 00:00:25,440
got the usual 15 trash cans or whatever we have to do now for cycling and yard waste and uh it's

6
00:00:25,440 --> 00:00:31,340
too much well that that reminds me i was i was in i was in london last week for uh devops and we'll

7
00:00:31,340 --> 00:00:36,580
get back to the heavy trash uh the heavy trash pickup you know the scintillating topics i was in dev in

8
00:00:36,580 --> 00:00:41,700
london for devops days london and i met an old friend of mine there and we uh of all places he chose to

9
00:00:41,700 --> 00:00:47,180
meet at a whole foods which is which is delightful and interesting it's funny we went in there and i

10
00:00:47,180 --> 00:00:55,060
was like so they have any like uh regional specials or anything and and he said no and so so they actually

11
00:00:55,060 --> 00:00:59,500
did have like i think a uh a type of sausage that was british you know you ever eat like a british

12
00:00:59,500 --> 00:01:04,700
sausage and it tastes a little more organy than uh sausagey i think i read once that there's some

13
00:01:04,700 --> 00:01:09,120
regulations about that but anyways uh so we were at a whole foods and we're done with our meal and then

14
00:01:09,120 --> 00:01:14,140
they of course you know kind of um what was the movie not judged red but what's the one where

15
00:01:14,140 --> 00:01:20,080
fester stallone goes into the future and they've got the three clam system i i i know what you're

16
00:01:20,080 --> 00:01:24,680
talking about yeah yeah so the recycling nowadays is like uh is like a three clam system right

17
00:01:24,680 --> 00:01:29,080
and uh they of course at whole foods they have this and i've i've encountered this elsewhere so

18
00:01:29,080 --> 00:01:33,160
maybe you know the answer richard but if listeners also know the answer so you got

19
00:01:33,160 --> 00:01:38,620
you'll have standard recycling which is straightforward and then there's something

20
00:01:38,620 --> 00:01:43,760
i guess compost right and then they have this other category every now and then you're lucky

21
00:01:43,760 --> 00:01:48,800
and it's just landfill and you're like got it right like whatever doesn't make sense put in there

22
00:01:48,800 --> 00:01:54,100
but then it's at whole foods i forget what it was labeled but it was something like you know

23
00:01:54,100 --> 00:02:00,800
complex recycling or something but but the thing is sometimes you get this three can system and it

24
00:02:00,800 --> 00:02:07,300
doesn't say just like landfill and so i never know what to do with like i just had a brown paper carton

25
00:02:07,300 --> 00:02:13,120
that i had my uh my british sausage and other stuff in it's some lovely tofu they had there and so it's

26
00:02:13,120 --> 00:02:17,500
like covered in food and i don't know do i put that in the recycling or or where do i put that

27
00:02:17,500 --> 00:02:23,120
because like here in austin you're not supposed to not that i would ever do this but you're not

28
00:02:23,120 --> 00:02:27,880
supposed to take a cardboard pizza box and put that in recycling because it's got food on it in theory

29
00:02:27,880 --> 00:02:32,780
right um so like i don't know i don't know i don't know what to do with this three can system if

30
00:02:32,780 --> 00:02:37,740
there's not like a straight up landfill and and there's never there's never a brochure no maybe you

31
00:02:37,740 --> 00:02:41,880
get like a picture on but between hotel showers and recycling there's nothing more humbling to me

32
00:02:41,880 --> 00:02:46,280
where you're just standing there like i'll be at the pivotal office staring there for like 30 seconds

33
00:02:46,280 --> 00:02:50,580
going i don't know where to put this thing in this trash then you just kind of mail it in and stick

34
00:02:50,580 --> 00:02:55,900
it in the the landfill trash but yeah yeah i feel like a terrible person but it's very tricky yeah

35
00:02:55,900 --> 00:03:01,400
so if if anyone is in the uh the waste management business out there you should start having some

36
00:03:01,400 --> 00:03:06,220
brochures with it but you're right about hotel showers man i was i was in the uh you know if you if

37
00:03:06,220 --> 00:03:12,020
you go to london yeah i recommend the uh the sheraton grand park or something it's right there

38
00:03:12,020 --> 00:03:16,900
on uh piccadilly is that how they say that or is that like my arkansas grandmother pronouncing it

39
00:03:16,900 --> 00:03:21,500
and uh it's it's just like the southeast corner of hyde park and some other park it's lovely

40
00:03:21,500 --> 00:03:26,240
not not too pricey but they had one of those european showers where there's it's got the temperature

41
00:03:26,240 --> 00:03:32,020
and then it's got like also the the the handle for the the water and the temperature one you've got

42
00:03:32,020 --> 00:03:37,200
to push a button down and and you set that and then and then the water one i you can tell i had

43
00:03:37,200 --> 00:03:43,220
to figure this out like one way is like your hand wand and the other way is your uh your uh shower

44
00:03:43,220 --> 00:03:49,740
shower as we would call it over here and man what a system no we need a national conversation on

45
00:03:49,740 --> 00:03:53,940
showers i mean how are we allowing every hotel to do this differently have you ever called the front

46
00:03:53,940 --> 00:03:58,600
desk and ask for help i've come close oh no i i don't even i don't even order a pot of coffee in

47
00:03:58,600 --> 00:04:02,720
the morning because i just i don't want to face anyone so i would never do that and then and then

48
00:04:02,720 --> 00:04:06,460
someone comes to your room and you're like do i gotta tip this guy do i tip this person what what

49
00:04:06,460 --> 00:04:11,900
do i do here yeah that's awful my wife tells me and then we'll get back to to heavy trash pickup

50
00:04:11,900 --> 00:04:16,980
my wife tells me that you can order a pot of coffee delivered in the morning and left at your door

51
00:04:16,980 --> 00:04:21,500
which um that sounds like some kind of paradise i just haven't experienced yet

52
00:04:21,500 --> 00:04:26,700
seems like a fire hazard maybe that's just me so the heavy trash pickup i guess if you don't have

53
00:04:26,700 --> 00:04:30,160
this let me just tell you a phenomena that happens that i think is fascinating because it's kind of

54
00:04:30,160 --> 00:04:34,640
like a little game and then we'll get on to some computer stuff but uh so you put all your heavy

55
00:04:34,640 --> 00:04:39,540
trash out and it takes them about a week to come collect it and then the weekend before there's these

56
00:04:39,540 --> 00:04:43,740
big pickup trucks with trailers that come cruising around and they sort through your stuff kind of like

57
00:04:43,740 --> 00:04:49,220
in our mutual friend if you ever read that and uh it's interesting to see what they pick up like we put

58
00:04:49,220 --> 00:04:55,860
three ceiling fans out there and what they did i don't know who they is but what the people did is

59
00:04:55,860 --> 00:05:02,620
they they came and they broke the blades off of the fans and they took the motor unit and i assume one

60
00:05:02,620 --> 00:05:07,660
that's because it fits and two maybe they take the blades off or they just get the copper wire out of

61
00:05:07,660 --> 00:05:13,960
it i don't know it's the uh the scavenging business is fascinating but so far perfectly good tv stand

62
00:05:14,300 --> 00:05:20,840
from ikea no one's taken that i'm looking at it right now yep yep i haven't taken that that that and

63
00:05:20,840 --> 00:05:26,460
some fan blades i mean that's a that's a sad short story right yeah yeah broken fan blades good to

64
00:05:26,460 --> 00:05:32,980
no one wow yeah well uh let's see it's been a while since we recorded you've been traveling a lot

65
00:05:32,980 --> 00:05:38,040
speaking of hotel showers and i think i think uh the last major thing you were at was was the big

66
00:05:38,040 --> 00:05:44,220
old vm world confab that was week before last right that's right in vegas it was only 106 so it cooled

67
00:05:44,220 --> 00:05:50,340
off a bit man i haven't been there in a long time they still doing all right there they got all those

68
00:05:50,340 --> 00:05:56,980
shows yeah all the shows i'll tell you it's b-list uh heaven out there yeah if you've ever had a

69
00:05:56,980 --> 00:06:03,300
career you can get yourself a show yeah huh huh i i've narrowly avoided going to orlando recently too

70
00:06:03,300 --> 00:06:08,200
which i'm happy about but i did orlando and vegas in the month of august i make poor choices

71
00:06:08,200 --> 00:06:14,580
oh yeah it's soupy out there so we we we had some uh some pretty big announcements we haven't really

72
00:06:14,580 --> 00:06:20,840
talked about here so we had the uh pivotal container service pks because i guess you know it's actually

73
00:06:20,840 --> 00:06:25,820
like the pivotal kubernetes service i i don't know it's just funny that's how that's how google yeah i mean

74
00:06:25,820 --> 00:06:31,240
right right google did the same thing so we uh we somewhat copied that and yeah it was a big

75
00:06:31,240 --> 00:06:34,680
announcement i know we'll talk about a little bit later but it was definitely i think the announcement

76
00:06:34,680 --> 00:06:39,900
of the show the things that folks were talking about well afterwards as well so uh yeah great

77
00:06:39,900 --> 00:06:44,200
great way to continue to expand the pivotal portfolio so yeah we'll gab about that in a little bit

78
00:06:44,200 --> 00:06:48,800
yeah yeah and then there was also uh an announcement i think the other the other at least for my

79
00:06:48,800 --> 00:06:55,680
my money speaking of vegas there was also i think vmware continued uh moving its its its what do you

80
00:06:55,680 --> 00:07:04,180
call it vcloud air onto aws which uh which was uh interesting for our area and uh yeah so so i like

81
00:07:04,180 --> 00:07:09,600
we should probably go over that as the main body of stuff but but uh in addition to that i didn't

82
00:07:09,600 --> 00:07:13,340
notice this till uh you were sharing these things earlier but there's actually like two little studies

83
00:07:13,340 --> 00:07:19,460
on topic of kubernetes and container usage i think right the first one is more like an abstract

84
00:07:19,460 --> 00:07:26,400
i briefly looked at the methodology but over there at uh over there at red monk i think uh like uh uh

85
00:07:26,400 --> 00:07:31,980
fintar as as his twitter handle is he uh he gave a summary of a little study they were doing and it

86
00:07:31,980 --> 00:07:35,780
looks like the way that they went over it is they kind of scanned some major companies about who they

87
00:07:35,780 --> 00:07:42,280
were hiring and questions they were asking sort of interest that might be indicative of of bigger use

88
00:07:42,280 --> 00:07:48,940
uh across fortune 100 companies and i was saying that uh that that docker is being has penetration if

89
00:07:48,940 --> 00:07:55,340
you will uh across like i don't know maybe uh 71 percent or so i mean i i love it when there's a 71

90
00:07:55,340 --> 00:08:00,280
percent and but uh you know a little little trailing one there but then definitely that uh there was a

91
00:08:00,280 --> 00:08:06,460
lot of interest about half of people in kubernetes and uh and i think what was he saying that half i i forget

92
00:08:06,460 --> 00:08:12,260
the reading but half of people fortune 100 companies were like indicated there was some kind of

93
00:08:12,280 --> 00:08:17,160
cloud foundry interest i assume that's open source cloud foundry you know inclusive of the various

94
00:08:17,160 --> 00:08:22,800
distros like ours um right and then i guess it was also like he did some summary he didn't go over

95
00:08:22,800 --> 00:08:28,740
all of this it was a very brief post some summary of um of the publicly referenceable people which

96
00:08:28,740 --> 00:08:35,520
i'm i'm uh interpolating is that the right word that maybe he combined together a list of public

97
00:08:35,520 --> 00:08:39,760
references and sort of counted them there that like the majority of them were uh cloud foundry

98
00:08:39,760 --> 00:08:46,380
references but i mean the the main thing i think uh and then there's a second survey from the cff which

99
00:08:46,380 --> 00:08:51,680
i think is a good commentary on this but you know stuff like this is good and helpful but it is like

100
00:08:51,680 --> 00:08:57,720
strictly penetration thinking uh to use that term technically which is to say there's at least one

101
00:08:57,720 --> 00:09:02,720
instance of this happening it doesn't necessarily uh you know and probably more in these companies

102
00:09:02,720 --> 00:09:07,760
obviously but it doesn't necessarily mean like market share and dominance it's just that some

103
00:09:07,760 --> 00:09:14,080
at least one one thing in there is uh is interested in it which as long as long as you have that temper

104
00:09:14,080 --> 00:09:20,420
across it you know because it would be a completely different thing if if we said across fortune 100

105
00:09:20,420 --> 00:09:28,040
companies 71 of them use docker as their core technology for doing everything like that would be a much

106
00:09:28,040 --> 00:09:33,180
bigger statement than uh just right and i think you know you point out clearly nothing this doesn't say

107
00:09:33,180 --> 00:09:38,060
who's in production and i would promise you or i would get almost be close to guaranteeing you that

108
00:09:38,060 --> 00:09:44,300
the cloud foundry usage in production you know dwarfs the others even docker even kubernetes just

109
00:09:44,300 --> 00:09:48,240
because from what we've i think all experienced is that sometimes things stall out as you get closer

110
00:09:48,240 --> 00:09:53,260
to production because of different compliance reviews and things like that that you know kubernetes

111
00:09:53,260 --> 00:09:57,840
is great for incubating some things and obviously pks is about helping you actually run this in

112
00:09:57,840 --> 00:10:02,880
production so as you say it's tough without really digging in and seeing is this one departmental

113
00:10:02,880 --> 00:10:07,960
thing is this an organizational strategy is this what have you i mean goodness i was thinking the

114
00:10:07,960 --> 00:10:13,080
other day i don't think it's unreasonable to say there's more apps running in pcf in the fortune 100

115
00:10:13,080 --> 00:10:18,240
than there is on amazon now i say that only because some of the largest companies are deploying thousands

116
00:10:18,240 --> 00:10:23,760
of applications to pcf and i don't know if those same numbers go into some of the public clouds i'm making

117
00:10:23,760 --> 00:10:28,680
that up i have no idea but that wouldn't shock me but again it all depends on what level is this production

118
00:10:28,680 --> 00:10:33,520
is this staging is this development are people hacking around you know without digging in but as you say

119
00:10:33,520 --> 00:10:39,060
it's a trend thing and either way it's useful to see yeah and then i think there's a good i mean it seems

120
00:10:39,060 --> 00:10:43,920
like well hopefully the red monk will come out with a more extensive write-up on i mean it was really just

121
00:10:43,920 --> 00:10:49,920
like 500 800 words which is fine but uh there was there was a now that i think of it it's

122
00:10:49,920 --> 00:10:55,900
interesting it was also a summary of a report or at least a second part in an ongoing series from uh

123
00:10:55,900 --> 00:11:01,000
our friends at the cloud foundry foundation and and i think theirs is uh there's no need to really

124
00:11:01,000 --> 00:11:05,940
disclaim or explain their their stuff because they spend a lot of time saying like ah these numbers

125
00:11:05,940 --> 00:11:11,680
are like provisional not provisional but these numbers are representative and they explain uh how

126
00:11:11,680 --> 00:11:16,660
how things are more about penetration and usage and they also look at some other surveys uh from people

127
00:11:16,660 --> 00:11:22,520
like datadog and others but what's interesting about them is is they focus more on uh year over

128
00:11:22,520 --> 00:11:27,920
year growth primarily by looking at people who are evaluating containers and are interested in them

129
00:11:27,920 --> 00:11:33,480
and there is a big uptick in their uh their survey base of i think in 2016 there were there were 31

130
00:11:33,480 --> 00:11:39,860
percent of people there there's that one again not not 35 not 30 31 you don't like round numbers

131
00:11:39,860 --> 00:11:47,100
anyways so there's 30 percent of people evaluating it in 2016 evaluating containers and that's gone up to

132
00:11:47,100 --> 00:11:52,940
42 percent which for a year over year thing is pretty big i mean in uh i think i think in use it just went

133
00:11:52,940 --> 00:11:58,180
from 22 to 25 percent which which is nice i don't know what their margin of error is but you know it's

134
00:11:58,180 --> 00:12:04,120
small enough that it's not like uh you know big bonkers stuff but but that's that's also a good survey

135
00:12:04,120 --> 00:12:09,900
to kind of look at just to uh combine together with the over one and the overall like way i would file

136
00:12:09,900 --> 00:12:19,040
it over is like yet again these containers things seem to be a big deal yeah and and i think i think

137
00:12:19,040 --> 00:12:26,800
this is even more even more so it's being meta about it it's growth over the growth we've seen last

138
00:12:26,800 --> 00:12:32,540
year in surveys saying that they're a big deal if if that makes sense so it's uh it's pretty validating

139
00:12:32,540 --> 00:12:36,820
yeah yeah i mean it's the same reason you know look i think we just saw the new spring boot numbers

140
00:12:36,820 --> 00:12:41,640
were like 22 million or something silly for spring boot downloads and is downloads a good metric no

141
00:12:41,640 --> 00:12:45,840
you know it's not great there's all sorts of edge thing but it's a trend line that says this was up

142
00:12:45,840 --> 00:12:50,640
from a million a couple of years ago clearly there's a trajectory and same with containers same with

143
00:12:50,640 --> 00:12:55,280
cloud foundry same with kubernetes there's a positive trajectory of these cloud native technologies and

144
00:12:55,280 --> 00:12:59,760
that's a good thing and if you're not using those it's time to get a little bit nervous that you're

145
00:12:59,760 --> 00:13:05,420
actually being left behind yeah and then and then so uh did did we announce these new tiles at vm world

146
00:13:05,420 --> 00:13:10,360
or when was that done they were all right around there and so we're you know i think the family

147
00:13:10,360 --> 00:13:17,740
of uh dell tech is starting to integrate a little better so if you look in the pivotal marketplace now

148
00:13:17,740 --> 00:13:23,820
you'll see things for the elastic cloud storage ecs dell boomy vmware wavefront and so if you're a

149
00:13:23,820 --> 00:13:28,500
cloud foundry customer and you like using s3 compatible storage but in your data center then

150
00:13:28,500 --> 00:13:34,640
you're probably already looking at ecs or using it great if you like doing ipazi stuff if we go to

151
00:13:34,640 --> 00:13:39,740
the gartner definitions of things the integration paths like i want to connect sas system a to sas

152
00:13:39,740 --> 00:13:45,160
system b dell boomy is the industry leader for that there's a really actually sophisticated tile

153
00:13:45,160 --> 00:13:49,240
for pcf to actually build out vms with the integration components pretty cool stuff

154
00:13:49,240 --> 00:13:55,120
and then wavefront was something vmware bought back in the spring acquired it and now they've

155
00:13:55,120 --> 00:13:59,380
integrated it's kind of a application performance monitoring some pretty cool correlation capabilities

156
00:13:59,380 --> 00:14:05,680
in there so you can extract data from the pcf nozzle whatever the log regator all that log information

157
00:14:05,680 --> 00:14:10,940
pull it into wavefront do some cool analytics which they actually showed it uh showed off wavefront a

158
00:14:10,940 --> 00:14:16,260
bit at vm world i was pretty impressed so all of those are now tiles so what is what does wavefront do

159
00:14:16,260 --> 00:14:21,920
it's like application performance monitoring so it's looking for data points and helping it pinpoint

160
00:14:21,920 --> 00:14:29,000
problems i know i'm getting it confused with wave maker which was this uh this like in browser rad

161
00:14:29,000 --> 00:14:36,380
application thing from i don't know the late 2000s yeah it was kind of interesting and uh i think i

162
00:14:36,380 --> 00:14:42,320
think man i i want now i should go look this up i i remember i remember someone bought it and maybe

163
00:14:42,320 --> 00:14:50,820
got sold to someone else or good times anyhow so so then uh we you know we we were talking about

164
00:14:50,820 --> 00:14:55,460
scheduling one of our uh security people on to come talk about the uh the equifax data breach

165
00:14:55,460 --> 00:15:00,160
but it was it was i feel like i feel like i feel like well first of all what's what's the summary of

166
00:15:00,160 --> 00:15:06,200
that and then i'll add my uh john madden commentary to it yeah i mean it looks like with equifax which

167
00:15:06,200 --> 00:15:12,740
obviously is a big player in the kind of credit space is that there was giant breach of what's

168
00:15:12,740 --> 00:15:18,700
like 143 something million people might be impacted and some was credit card information some was

169
00:15:18,700 --> 00:15:23,740
personal information definitely not good a lot of information kind of leaking out it's not all real

170
00:15:23,740 --> 00:15:28,100
definitive yet sound like this happened in july and they just announced it here in early september

171
00:15:28,100 --> 00:15:33,260
that it happened and you know looks like it may have been tied to unpatched environments but some

172
00:15:33,260 --> 00:15:37,920
of that's going back and forth so again i think it's it's an area for not just doing hot takes on

173
00:15:37,920 --> 00:15:42,380
blaming certain things i think the only thing you blame is equifax for not properly securing their

174
00:15:42,380 --> 00:15:47,300
environment whether they were using bad tech or whether using old tech or whether you're just using tech

175
00:15:47,300 --> 00:15:53,560
wrong it falls on you as a business if you're collecting customer data to protect it and so not good not good

176
00:15:53,560 --> 00:15:58,200
stuff at all yeah yeah so so maybe we'll uh we'll we'll have someone on to talk about that in more

177
00:15:58,200 --> 00:16:03,280
detail and then you know well not in more detail but use that as context to talk about more uh security

178
00:16:03,280 --> 00:16:09,540
things but it is interesting i think uh i think it's the first instance that like my my uh my non-nerd

179
00:16:09,540 --> 00:16:15,340
associates in my life were more up to date on it than i am so whatever whatever notification news

180
00:16:15,340 --> 00:16:20,440
coverage stuff people have you know our our our little society of news has put in place it's it's

181
00:16:20,440 --> 00:16:26,720
effective it's uh it's it's reaching the normals yeah and you know there's one for a lot of us that

182
00:16:26,720 --> 00:16:31,620
you know can yeah can reach close to home because it might impact us all personally with this and you

183
00:16:31,620 --> 00:16:36,540
know patching stuff i think a lot of cios probably woke up today saying our number one priority needs

184
00:16:36,540 --> 00:16:41,420
to be making sure our customer facing internet systems are patched the problem is even if you do

185
00:16:41,420 --> 00:16:45,320
heroics and do all of that in the next week you're gonna have to do it again the week after because

186
00:16:45,320 --> 00:16:50,260
this stuff never stops you have to rethink how you secure enterprise and it'll be a good conversation

187
00:16:50,440 --> 00:16:56,320
for us to have yeah and then uh and then finally there's uh there's some kafka news that you put

188
00:16:56,320 --> 00:17:02,820
in here what's what's that about so kafka released this ksql capability open source streaming sql for

189
00:17:02,820 --> 00:17:07,000
kafka i think they did this at their kafka summit and really the idea is how do you analyze data in

190
00:17:07,000 --> 00:17:12,780
flight so traditional data solutions is kind of the data sits there and your queries always change

191
00:17:12,780 --> 00:17:17,300
right you're issuing different queries against your data in the more complex event processing world it's

192
00:17:17,300 --> 00:17:22,260
always been you actually deploy the query and the data washes over it so the query is kind of static

193
00:17:22,260 --> 00:17:28,200
and the data changes so this is a similar-ish model where you're actually deploying queries and you might

194
00:17:28,200 --> 00:17:31,940
be looking for anomalies you might be looking for different things doing windowing which is cool

195
00:17:31,940 --> 00:17:37,580
saying hey i'm looking for accounts for the next five minutes in like time period stuff so as data flows

196
00:17:37,580 --> 00:17:42,900
through the streaming engine you can actually issue some sql like queries against the data so cool

197
00:17:42,900 --> 00:17:47,680
technology cool capability i think again it just drives home that event-driven architecture and

198
00:17:47,680 --> 00:17:52,840
processing data in real time is clearly something a lot that's on the minds of a lot of tech vendors

199
00:17:52,840 --> 00:17:59,640
but obviously clearly on customers who don't want to just do kind of day after month after analytics they

200
00:17:59,640 --> 00:18:04,640
need to be analyzing this stuff as it happens so you know obviously by the way i prompted you to talk

201
00:18:04,640 --> 00:18:09,540
about that i don't really know much at all about kafka but it does seem like someone needs to do some

202
00:18:09,540 --> 00:18:15,080
surveys about how popular that is because it seems like that's uh that's what is this true that's like the data

203
00:18:15,080 --> 00:18:21,680
thing i don't know what to call this stuff anymore the uh no sql is that is that a thing uh but that's the

204
00:18:21,680 --> 00:18:25,400
thing that there you go that's the thing that like seems to come up the uh the most

205
00:18:25,400 --> 00:18:31,060
pretty much all the time so it seems extremely popular that's fair they have a ton of mind share

206
00:18:31,060 --> 00:18:35,680
in the space i mean there's you know obviously things like rabbit mq can do virtually any pattern you can do

207
00:18:35,680 --> 00:18:40,440
in kafka it's still about messaging and transferring data and real-time processing there's different

208
00:18:40,440 --> 00:18:45,520
architectures of course but the use cases can be very similar or things like amazon kinesis do the

209
00:18:45,520 --> 00:18:50,740
same thing or azure event hub so there's all sorts of things in this space but you know the kafka team

210
00:18:50,740 --> 00:18:56,020
and confluent in general have done a great job of kind of taking up some of the uh the public space and

211
00:18:56,020 --> 00:19:01,820
sharing what's going on here and and how is it is it popular off there in uh dot net microsoft land

212
00:19:01,820 --> 00:19:06,640
or do they have their own analog thing that everyone's everyone's uh all hoot and tooting about

213
00:19:06,640 --> 00:19:11,520
yeah it doesn't really i mean there's brokers and there's endpoints and sdks and things that are a

214
00:19:11,520 --> 00:19:16,020
little dot net friendly but it's traditionally been a more linux centric environment tool and open

215
00:19:16,020 --> 00:19:20,460
source tool so i think that's where you're looking at things that azure offers or microsoft's esb

216
00:19:20,460 --> 00:19:24,700
product enterprise service bus product so i think it's been a little later coming to this actually

217
00:19:24,700 --> 00:19:30,040
microsoft had a complex event process engine stream insight years ago i think it's still technically

218
00:19:30,040 --> 00:19:34,980
around but not maintained that actually did this sort of thing in a neat way and actually shipped

219
00:19:34,980 --> 00:19:40,220
with sql server it was just arguably ahead of its time so microsoft folks are probably catching up to

220
00:19:40,220 --> 00:19:45,640
this versus being uh right on it with things like kafka yeah you're reminding me i i maybe this is like

221
00:19:45,640 --> 00:19:50,300
four or five years ago like there were all all the uh all the big vendors were talking about like

222
00:19:50,300 --> 00:19:55,760
streams and data streams and stuff and and i could never i could never figure out like what the use

223
00:19:55,760 --> 00:20:00,880
cases for it were they would just talk about like how uh how quickly they could consume and do stuff

224
00:20:00,880 --> 00:20:07,980
with streams of data so right you know very popular at the time well yeah so uh so then on to the vm

225
00:20:07,980 --> 00:20:14,200
world stuff so you were actually there you gave a presentation i was how was how was the uh how was the

226
00:20:14,200 --> 00:20:19,660
show how was it that was one of the biggest conferences i've been at had like 23 000 people

227
00:20:19,660 --> 00:20:23,940
or something like that i mean besides dream force which is like a festival and has like 100 000 people

228
00:20:23,940 --> 00:20:28,160
but never all in the same place so when you're sitting in an announcement you know keynote hall

229
00:20:28,160 --> 00:20:33,560
it's a i don't know like an arena like where they do shows and things and it's you're surrounded by

230
00:20:33,560 --> 00:20:39,200
by 20 000 people watching a stage that was massive and then you know giant show floor for all the

231
00:20:39,200 --> 00:20:44,000
vendors and the usual games and whatever bizarre things happening on a conference show floor but a

232
00:20:44,000 --> 00:20:49,340
good vibe it seemed like there was a uh a different vibe this year than at least some of the media

233
00:20:49,340 --> 00:20:55,140
reports from the last few years of hey is vmware going to survive containers is vmware going to survive

234
00:20:55,140 --> 00:21:00,720
amazon is vmware just dead man walking and instead really walked out of the show going gosh they may

235
00:21:00,720 --> 00:21:04,900
have figured this out like they may have figured out how to play in a cloud world they may have figured

236
00:21:04,900 --> 00:21:10,920
out how to not compete with containers but complement some of that and even showing off some of their

237
00:21:10,920 --> 00:21:15,460
tooling i think some of my visual experience of the vmware tooling is a little old because they were

238
00:21:15,460 --> 00:21:19,260
showing some of the newer capabilities and like that's a good user interface that doesn't look like

239
00:21:19,260 --> 00:21:24,560
a mess at all so it seems like the company's really doing some interesting stuff so it seemed to be

240
00:21:24,560 --> 00:21:28,860
reflected in the show where the vibe was good the people walking around a lot of chatter a lot of

241
00:21:28,860 --> 00:21:34,980
activity people you know sessions were full up to the last day so it was a good show it's vegas

242
00:21:34,980 --> 00:21:39,800
mandalay bay out in the middle of middle of nowhere at the end of the strip but it uh it seemed again

243
00:21:39,800 --> 00:21:45,080
had a great crowd lots of topics you know people covering infrastructure and network and then this

244
00:21:45,080 --> 00:21:49,660
quirky pivotal company talking about apps and continuous delivery and stuff i thought that was a

245
00:21:49,660 --> 00:21:55,740
nice change of pace mandalay bay i haven't been there in a long time i used to go there all the time

246
00:21:55,740 --> 00:22:01,660
that's the one where they have uh they have uh you walking along the hallway to the main conference

247
00:22:01,660 --> 00:22:06,020
center and all of a sudden there's this little uh tex-mex restaurant or mexican restaurant right

248
00:22:06,020 --> 00:22:09,720
like just kind of creeps up on you maybe they don't have that there anymore yeah i think that's right

249
00:22:09,720 --> 00:22:13,780
and i was staying at the mgm for some pivotal meetings so i was walking back and forth because

250
00:22:13,780 --> 00:22:17,860
i make again poor choices and that was like 30 minutes door to door even though they're inside of each

251
00:22:17,860 --> 00:22:22,980
other no it's true so so we i think i think the the the biggest announcement as we're talking about

252
00:22:22,980 --> 00:22:29,580
earlier that we had there was uh was the pivotal container service pks and uh now now now correct

253
00:22:29,580 --> 00:22:33,620
me where i get the my facts wrong but and then i'll have to go back and talk to all those people

254
00:22:33,620 --> 00:22:38,340
at devops days london that i talked to i'll uh i'll have to write them a letter maybe send it to the

255
00:22:38,340 --> 00:22:44,720
authorities over there to distribute but if i got something wrong but basically you got uh essentially

256
00:22:44,720 --> 00:22:49,200
it's the idea of like here's here's a kubernetes distribution i don't know if that's what people say

257
00:22:49,200 --> 00:22:54,780
in the kubernetes word but world but the the current instantiation of it which won't be released till

258
00:22:54,780 --> 00:23:00,940
the end of the year so it's just an announcement of of a thing is that it uses uh the vmware stack

259
00:23:00,940 --> 00:23:05,840
so it's got the nsx networking thing and then uh running on i guess i don't know what they call it

260
00:23:05,840 --> 00:23:11,160
nowadays because but whatever whatever yeah whatever that's what i was gonna say now there you go

261
00:23:11,160 --> 00:23:16,440
whatever v sphere is and i think it has integrations with the v realize like systems management and

262
00:23:16,440 --> 00:23:23,300
monitoring stack but uh essentially the idea is that you use bosch which is the people listening

263
00:23:23,300 --> 00:23:27,460
to this probably know what that is but it's the the configuration management and provisioning and

264
00:23:27,460 --> 00:23:33,300
and in a good way rudimentary health check management like restarting things and making

265
00:23:33,300 --> 00:23:37,380
sure they're healthy and making sure everything's running running like it should it doesn't do you

266
00:23:37,380 --> 00:23:43,680
know like complex apm stuff but whatever uh but it basically uses bosch to deploy and manage the

267
00:23:43,680 --> 00:23:48,440
kubernetes cluster that you have uh with the idea that like if you want to if you want to run containers

268
00:23:48,440 --> 00:23:56,180
and run kubernetes now you can do it in uh in the pivotal cloud foundry stack if you will uh using the

269
00:23:56,180 --> 00:24:03,300
full the full power and functionality of of all the vmware stuff underneath which hopefully means that uh

270
00:24:03,300 --> 00:24:09,200
it's it's reliable and and uh you know that it's it's a reliable distro that we have and then it kind

271
00:24:09,200 --> 00:24:14,240
of fits into the way that most large enterprises want to be managing things uh and using their

272
00:24:14,240 --> 00:24:21,220
existing vmware knowledge and and all of that stuff and so i think i think i think at the you know

273
00:24:21,220 --> 00:24:27,420
to distinguish between existing pivotal cloud foundry we have the uh the elastic runtime which unless you

274
00:24:27,420 --> 00:24:32,540
get a deep dive into pivotal cloud foundry you don't encounter very much but the ert which sounds

275
00:24:32,540 --> 00:24:37,320
highly medical i guess like an er or something or whatever that thing is that checks your heart rate

276
00:24:37,320 --> 00:24:44,240
uh and uh so that is sort of like distinguished as the quote i'm doing air quotes here traditional

277
00:24:44,240 --> 00:24:49,520
pivotal cloud foundry thing that will run alongside that for all of your uh your cloud native applications

278
00:24:49,520 --> 00:24:54,160
and your 12 factor stuff and things like that and then if if you want to run things in more of a

279
00:24:54,160 --> 00:24:59,560
container oriented way or if you know they're they're heavier stateful applications services or

280
00:24:59,560 --> 00:25:04,640
or whatever now there's sort of like this peer to run and so you like got all your bases covered

281
00:25:04,640 --> 00:25:09,040
for the way that you want to run and manage all your uh your various applications and then also

282
00:25:09,040 --> 00:25:15,640
i guess i left off that it runs on uh google's cloud and and by virtue of that i don't have the

283
00:25:15,640 --> 00:25:21,080
laundry list of stuff but it's got the like what five or eight sort of uh various google cloud services

284
00:25:21,080 --> 00:25:26,960
that get integrated into it which which you know i would expect that just like we do with pivotal

285
00:25:26,960 --> 00:25:32,280
cloud foundry it would run on other platforms sometime in the future if that makes sense but i think

286
00:25:32,280 --> 00:25:36,860
it uh it sort of fits with the whole uh bent of of what we've been doing with pivotal cloud foundry

287
00:25:36,860 --> 00:25:43,000
which is like here's your centralized way of running your applications and there's various ways now that

288
00:25:43,000 --> 00:25:48,100
you can uh package things up to run into there but it basically just gives you a uh application

289
00:25:48,100 --> 00:25:54,160
platform if you will or platform as we would just say and then runs on all of these uh these multiple

290
00:25:54,160 --> 00:26:01,000
clouds i guess i guess just two at the moment but then nicely it gives you uh uh what would be the

291
00:26:01,000 --> 00:26:05,800
word it gives you as much portability as you could hope for across different types of infrastructure

292
00:26:05,800 --> 00:26:12,220
which uh which which seems like what people want how'd i get did i get that right yeah that's a

293
00:26:12,220 --> 00:26:19,820
shockingly uh well done explanation of it that was good for someone not being there sitting through uh

294
00:26:19,820 --> 00:26:24,780
90 briefings like i've been going through the last months i was that was really well done uh yeah no

295
00:26:24,780 --> 00:26:29,960
well said i think that it's important to go back and though say like why you know is this because

296
00:26:29,960 --> 00:26:35,400
pivotal just missed the boat on other stuff and now we're kind of hat in hand don't gonna

297
00:26:35,400 --> 00:26:39,840
shoot i guess we'll offer kubernetes now but i don't think that's it at all so this came down to

298
00:26:39,840 --> 00:26:44,560
pivotal is good i think we've proven that we're good at industrializing open source meaning making

299
00:26:44,560 --> 00:26:50,520
open source operable secure you know just running cloud founder from the open source repo that's work

300
00:26:50,520 --> 00:26:55,280
right to bundle it to patch it to secure it to deploy it you know most people don't do that they

301
00:26:55,280 --> 00:26:59,680
run a distribution of it that takes care of it like what pivotal does and we do that with spring and

302
00:26:59,680 --> 00:27:04,340
we do that with all these sorts of things to try to make it easier to run open source and so we've

303
00:27:04,340 --> 00:27:10,220
solved a bit of that pivotal you know 12 factor app use case right we've done a good job of that we've

304
00:27:10,220 --> 00:27:16,140
kind of addressed that built a great tool chain but as our customer said look it's also we're running

305
00:27:16,140 --> 00:27:20,500
these other things as you're the survey we talked about above people are starting to run other things

306
00:27:20,500 --> 00:27:24,500
but the maturity of the tooling isn't there and so how do you make it simpler for

307
00:27:24,500 --> 00:27:30,220
gen enterprise to now add something like kubernetes for stateful workloads or other types of apps or

308
00:27:30,220 --> 00:27:35,460
whatever even 12 factor apps doesn't matter how do we make it easier for them to run those and so

309
00:27:35,460 --> 00:27:41,400
taking existing software that we've built like bosch like kubo which builds on bosch like nsx like

310
00:27:41,400 --> 00:27:46,300
google cloud like these pieces wavefront harbor and combine them into a product we're good at that

311
00:27:46,300 --> 00:27:49,740
we've i think we've proven we do well at that so this is more of an exercise of pivotal trying to

312
00:27:49,740 --> 00:27:55,600
make sure that we can eventually run 100 of the apps that you have and not saying that ert isn't

313
00:27:55,600 --> 00:27:59,680
the right choice for a number of apps it is it's still the preferred way to run cloud native apps

314
00:27:59,680 --> 00:28:04,680
but that as you have other types of applications or even as you want to you know have different

315
00:28:04,680 --> 00:28:08,800
divisions who don't use cloud foundry how can i at least have the same operational tool chain for

316
00:28:08,800 --> 00:28:14,400
the whole thing so i'm using bosch i'm using stem cells i'm using all these components whether i'm

317
00:28:14,400 --> 00:28:19,020
using kubernetes or whether i'm using elastic runtime or any of these we're making it easy now

318
00:28:19,020 --> 00:28:24,440
what's been unique here because kubernetes is not an unsolved problem there's whatever 50 different

319
00:28:24,440 --> 00:28:30,020
variations people have done on this i think why google was excited about this work was we're doing

320
00:28:30,020 --> 00:28:35,700
vanilla kubernetes here this is not a distribution of kubernetes this is open source kubernetes that we are

321
00:28:35,700 --> 00:28:41,200
making it easier to operate so it's not draped in customizations that lead to like a six month lag

322
00:28:41,200 --> 00:28:44,900
before the customer actually gets their hands on it because the vendor has to munge it all together

323
00:28:44,900 --> 00:28:51,100
with their stuff and their customizations nope we uh you know sam ramji was on stage from google saying

324
00:28:51,100 --> 00:28:56,920
the thing that's exciting here is this constant compatibility meaning that as kubernetes is updated it gets

325
00:28:56,920 --> 00:29:02,300
into pks and there's virtually no lag so you've got this constant compatibility with something like gke

326
00:29:02,300 --> 00:29:07,520
google's hosted container engine because you're going to constantly be up to date it's not necessarily

327
00:29:07,520 --> 00:29:12,460
something that's been forked or refactored or done anything with so your portability is awesome

328
00:29:12,460 --> 00:29:16,300
you know you're getting access to the latest innovation and you're still getting it operated

329
00:29:16,300 --> 00:29:21,800
at enterprise scale by a company i think you trust to deliver security stuff so all of that i think comes

330
00:29:21,800 --> 00:29:27,080
together why google would be on stage at a vm world event vmware event that's not something that

331
00:29:27,080 --> 00:29:31,980
traditionally happens but i think pivotal and google and vmware are saying we're taking existing products

332
00:29:31,980 --> 00:29:36,560
we're combining them in a cool way and we're solving a legit problem that's unaddressed in the market

333
00:29:36,560 --> 00:29:42,660
by doing something hopefully folks trust pivotal to do yeah yeah you know the the uh uh to go in a

334
00:29:42,660 --> 00:29:48,640
little jag the uh the compatibility thing is interesting i mean it's been that's been you know it's

335
00:29:48,640 --> 00:29:52,240
almost been almost been three years since i worked here and then also when i was covering pivotal

336
00:29:52,240 --> 00:30:00,320
as an analyst a big theme was always uh multi-cloud uh and the um i mean i i guess i guess the the the

337
00:30:00,320 --> 00:30:06,920
negative uh synonym of compatibility is lock-in right like that's that's the thing you're sort of uh

338
00:30:06,920 --> 00:30:12,800
avoiding the when you have compatibility but it is it is sort of like a constant theme and building out

339
00:30:12,800 --> 00:30:20,560
whatever cloud native is cloud native platforms and all of that is is uh and it doesn't apply to all

340
00:30:20,560 --> 00:30:26,720
them but it's this idea that you want to have portability and compatibility of of your application

341
00:30:26,720 --> 00:30:31,720
choices and i shouldn't say application choices of where you're running your applications and

342
00:30:31,720 --> 00:30:37,220
obviously as i was kind of alluding to earlier you know if you depend on something that's only

343
00:30:37,220 --> 00:30:42,560
available in a platform or some particular way that uh that you configure to it or use it then you've

344
00:30:42,560 --> 00:30:46,800
got to worry about that it's not always like you can just drag and drop something i don't even know

345
00:30:46,800 --> 00:30:51,480
if there is a drag and drop interface somewhere there probably is for a fancy demo but you know

346
00:30:51,480 --> 00:30:58,000
those are always mildly ridiculous demos like that's gonna happen um but uh yeah i got i got my itel

347
00:30:58,000 --> 00:31:03,400
change request and now i'm gonna use a mouse to drag and drop it and then close the ticket but amazing

348
00:31:03,400 --> 00:31:11,800
um but it is it is like you know it makes me think that or sort of reflect on a general principle or i

349
00:31:11,800 --> 00:31:17,440
wonder if this is a principle of if you're kind of like a a planner type to go back several episodes

350
00:31:17,440 --> 00:31:21,960
whatever it is an enterprise architect is nowadays it seems like you would have a principle and you

351
00:31:21,960 --> 00:31:26,620
would say like all right this period we're in there's a whole lot of different options of things to do

352
00:31:26,620 --> 00:31:30,940
but we got to choose something right like we've got to modernize how we do our application platform

353
00:31:30,940 --> 00:31:36,980
so because there's so many choices out there what we want to do is maximize our our options for moving

354
00:31:36,980 --> 00:31:42,220
to different platforms in the future so we want to have maximum compatibility right like maybe we'll

355
00:31:42,220 --> 00:31:46,080
be running everything in google or maybe azure will have a container service or maybe we'll run it

356
00:31:46,080 --> 00:31:51,020
on premise but we want to make sure that however packaging things up we'll be able to move around

357
00:31:51,020 --> 00:31:56,100
as much as possible which seems like a good principle and and you know it'd be easy to say

358
00:31:56,100 --> 00:32:00,100
you always want to do that but there's probably many situations where you don't always want to do

359
00:32:00,100 --> 00:32:07,400
that like for example uh the late 2000s where vmware basically wins and you're like well i guess

360
00:32:07,400 --> 00:32:12,780
i'll make everything into vmware images and you know it seems like essentially you uh you settle down

361
00:32:12,780 --> 00:32:18,060
of uh you know on on what it is you want to do but at this period if you're doing some sort of

362
00:32:18,060 --> 00:32:22,860
application development based on container stuff then uh you want to have sort of like maximum

363
00:32:22,860 --> 00:32:28,980
compatibility it is and and i think i think with our stack and and then also by nature with uh with a

364
00:32:28,980 --> 00:32:34,160
google stack or a vmware stack and and and working back to stuff we've already announced you know a

365
00:32:34,160 --> 00:32:39,660
microsoft stack i think i think people should have pretty good feels about the compatibility across

366
00:32:39,660 --> 00:32:46,260
those uh across those different pools of air of ecosystems if you will uh that's right to cover your

367
00:32:46,260 --> 00:32:51,800
basis there so then then also like i mean you know i know uh i know because you're always tweeting about

368
00:32:51,800 --> 00:32:56,060
how excited you are about it like you and i and other people read the sort of the sort of weekly

369
00:32:56,060 --> 00:33:01,420
field reports and man like there is there's like a lot of interest for this thing only being out two

370
00:33:01,420 --> 00:33:06,800
weeks like i didn't go through and search for uh instances of pks not like i would report them out

371
00:33:06,800 --> 00:33:12,240
here but uh yeah like there was a lot of people who uh wanted to get briefed or have been briefed you

372
00:33:12,240 --> 00:33:18,540
know customers and prospects we have at large organizations so it is it's uh you know like

373
00:33:18,540 --> 00:33:24,840
obviously for if you listen to my other podcast software defined talk like these container things

374
00:33:24,840 --> 00:33:28,960
have been a big deal for a while and and kubernetes and everything so obviously there's interest but

375
00:33:28,960 --> 00:33:34,620
there's uh even more interest uh out there in the field than than i would expect there to be and

376
00:33:34,620 --> 00:33:39,540
part of that i think is you know uh it's a testament to how many people out in the field we have

377
00:33:39,540 --> 00:33:44,800
engaging all the time pivotal people but still there's a huge pull for it which uh it'll be it'll

378
00:33:44,800 --> 00:33:49,700
be nice over the next six months even if not longer to see see how uh how this stuff pans out and i

379
00:33:49,700 --> 00:33:55,700
think i think what's what's particularly interesting so like one of the things i i've i've i like about

380
00:33:55,700 --> 00:34:00,060
about being at pivotal is you get to go talk to these large organizations and just see what they're

381
00:34:00,060 --> 00:34:05,520
doing with with all with all this technology and it'll be it'll be fun to see what they do with uh

382
00:34:05,520 --> 00:34:10,540
with kubernetes and containers and how they divide things out and and it's uh it's a good what do they

383
00:34:10,540 --> 00:34:16,600
call it in economics a natural experiment of how uh how this technology gets used but yeah there's tons

384
00:34:16,600 --> 00:34:21,900
of interest yeah it's been now i've been following that as well and what's been interesting too is it comes

385
00:34:21,900 --> 00:34:26,060
from a lot of our existing customers who say look this is more workloads we can run with you now we like

386
00:34:26,060 --> 00:34:30,940
the model we like the pivotal way and and now you give us more choices and it's also candidly come

387
00:34:30,940 --> 00:34:36,180
from a number of places that didn't really click with cloud foundry elastic runtime and then back in

388
00:34:36,180 --> 00:34:40,100
going yeah you know we like this idea to be able to use straight up kubernetes without all the

389
00:34:40,100 --> 00:34:44,880
accoutrements and instead just operate it at scale in a way that doesn't require a 50 person operations

390
00:34:44,880 --> 00:34:50,260
team that sounds really appealing so coming from lots of different dimensions it's exciting stuff i mean

391
00:34:50,260 --> 00:34:54,980
it's not unrealistic that 12 months from now no one makes more revenue from kubernetes than people

392
00:34:54,980 --> 00:35:00,840
like it just that's not out of the realm of possibility we'll have to save that up save that

393
00:35:00,840 --> 00:35:05,140
up for a predictions episode come uh december or something yeah there you go that sounds good

394
00:35:05,140 --> 00:35:10,760
yeah uh yeah no no it is interesting it's sort of like uh it's like you got the automatic transition

395
00:35:10,760 --> 00:35:16,420
and you got the stick transition you choose whichever one you like i uh i that's right i always choose

396
00:35:16,420 --> 00:35:19,880
automatic because i don't know how to drive that other one although here they have paddles nowadays

397
00:35:19,880 --> 00:35:25,720
which uh you know paddle shifting which that sounds like more my speed so to speak maybe that would

398
00:35:25,720 --> 00:35:30,460
work you use those the first day you buy the car and then you never use them again yeah that's right

399
00:35:30,460 --> 00:35:36,680
both of my cars have those in it and uh it is kind of a weird vestigial feature it's it's like that

400
00:35:36,680 --> 00:35:41,300
second gear thing like what is that for like when you're driving across the rockies or something i don't

401
00:35:41,300 --> 00:35:47,820
know that does remind me i had dinner with uh with with uh that friend of mine in london and his

402
00:35:47,820 --> 00:35:54,360
how old was his kid 14 they said that uh he got to go on the closed track as a 14 year old and drive

403
00:35:54,360 --> 00:36:01,020
a ferrari which is kind of interesting that they have that going on wow yeah i'll have to look at to

404
00:36:01,020 --> 00:36:05,000
see if they have that for my seven year old my daughter just turned four maybe she qualifies

405
00:36:05,000 --> 00:36:11,520
bring some fun books well then also we mentioned just just to mention it just to mention it briefly

406
00:36:11,520 --> 00:36:17,880
before we close out also uh also vmware completed moving it's uh it's v it's v cloud air stuff to aws

407
00:36:17,880 --> 00:36:23,160
so there's yet another option if you want to run your your vmware stuff on aws they have that they

408
00:36:23,160 --> 00:36:27,960
have that finished out did you did you see anything about that while you were at the show yeah i mean

409
00:36:27,960 --> 00:36:31,760
they've still got the v cloud network i think of partners some of this was the v vmware cloud

410
00:36:31,760 --> 00:36:38,800
management thing the vmc on aws saying how do i manage aws as well as my on-prem vmware assets

411
00:36:38,800 --> 00:36:43,020
and so they showed off some really actually impressive demonstrations of building out these

412
00:36:43,020 --> 00:36:47,400
environments managing them connecting them you know this was did not look like a superficial

413
00:36:47,400 --> 00:36:51,980
integration this looked like legitimate multi-cloud provisioning and management so if you care about

414
00:36:51,980 --> 00:36:56,500
that from an infrastructure perspective if you're still kind of managing infrastructure versus apps

415
00:36:56,500 --> 00:37:01,240
which is probably most people uh it looked pretty compelling and if you're amazon this is a

416
00:37:01,240 --> 00:37:07,440
great way to start pulling in some of those workloads that might not have been on a fast path or fast

417
00:37:07,440 --> 00:37:12,840
track to aws and if you're vmware all of a sudden you have a legitimate way to actually stripe

418
00:37:12,840 --> 00:37:17,280
management across multiple infrastructure environments which frankly most in the multi-cloud

419
00:37:17,280 --> 00:37:22,480
space haven't really done in a great way so you know i i saw this fairly compelling and it's done

420
00:37:22,480 --> 00:37:26,200
and i think it's just available in oregon so i guess they're just trying it out on those those

421
00:37:26,200 --> 00:37:32,120
characters but it'll expand to other regions over these coming months just available in oregon that

422
00:37:32,120 --> 00:37:36,680
is a part i read that was uh that was kind of funny but you know you experiment with it and expand it

423
00:37:36,680 --> 00:37:43,520
out it's it's a new way of stuff well uh i think that i think that's it for our coverage here i think

424
00:37:43,520 --> 00:37:48,820
uh it'll it'll be fun it'll be fun ongoing we'll have we're going to uh schedule the um what would you

425
00:37:48,820 --> 00:37:56,000
call it the product manager the uh the product person uh cornelia from pks at some point to come

426
00:37:56,000 --> 00:38:00,500
talk with us some point soon about that so we'll get more details on it and uh by that time we'll

427
00:38:00,500 --> 00:38:04,720
see how much more interest there are and things fleshed out there but but that'll be good so as

428
00:38:04,720 --> 00:38:10,940
always this has been Pivotal Conversations if you want to go browse previous episodes find the rss feed

429
00:38:10,940 --> 00:38:17,000
for this the best place to go is soundcloud.com slash Pivotal Conversations with no space you can

430
00:38:17,000 --> 00:38:22,840
also usually about every thursday if uh if i'm doing my job correctly we form we post a formal version

431
00:38:22,840 --> 00:38:29,220
with full show notes and everything over at pivotal.io slash podcast which you can find and there's just a

432
00:38:29,220 --> 00:38:34,960
little little uh thing uh you know we're coming up on uh december where we have our SpringOne platform

433
00:38:34,960 --> 00:38:40,560
i think i think we're kind of close i think maybe the cfp closed a couple weeks ago or last week or

434
00:38:40,560 --> 00:38:46,180
something or maybe it's closing now sometime it did just close there you go as always on i'm on top of

435
00:38:46,180 --> 00:38:51,540
these things but uh the the sessions are looking pretty good and there's even some debates over which

436
00:38:51,540 --> 00:38:56,180
sessions to have some little some little uh cfp fighting going on which which is encouraging

437
00:38:56,180 --> 00:39:02,140
but if you're interested in that you should check it out at uh spring io that spring io spring spring

438
00:39:02,140 --> 00:39:08,740
one platform.io and uh you can use the code s1p200 underscore Coté because every now and then you

439
00:39:08,740 --> 00:39:14,180
should revisit the underscore character to get as you you might guess two hundred dollars off uh and

440
00:39:14,180 --> 00:39:20,280
the uh the price jumps up i think on the 17th or 18th so if you're listening to this this uh

441
00:39:20,280 --> 00:39:24,140
week of september jump on now and the main stage is looking amazing we're putting it together right

442
00:39:24,140 --> 00:39:27,940
now the number of customers speaking the spring presentations it's really going to be uh

443
00:39:27,940 --> 00:39:32,560
be something special so it's time to book it yeah it will it will be nice and i think there's

444
00:39:32,560 --> 00:39:37,020
there's some uh there's all sorts of tracks going on i got the devops track that i'm helping out with

445
00:39:37,020 --> 00:39:42,900
continuous integration and there's the uh i think it has some title like the transformation track but

446
00:39:42,900 --> 00:39:46,920
it's like have all the business manager people come talk about how they change their organization

447
00:39:46,920 --> 00:39:51,420
over and of course you've got spring and cloud foundry and things like that and there'll probably be

448
00:39:51,420 --> 00:39:56,880
uh you know several sessions about pks and other things like that so it'll be chock full of good

449
00:39:56,880 --> 00:40:01,940
stuff over there at musconi west if i if i remember i don't know if it's right because i think someone

450
00:40:01,940 --> 00:40:06,940
told me they're redoing north and south so you're you're over there in the west area nice crisp cool

451
00:40:06,940 --> 00:40:12,240
weather and also uh if you if you uh catch this in time i'm going to be at several devops days i'll be

452
00:40:12,240 --> 00:40:18,740
in latvia next week and then kansas city and uh at nashville some other places uh that that i'm not

453
00:40:18,740 --> 00:40:24,980
remembering but uh you definitely check out uh over there at devopsdays.org pivotal people will be out

454
00:40:24,980 --> 00:40:29,100
at many of them if you're interested in talking more about these topics and with that we'll see

455
00:40:29,100 --> 00:40:30,760
everyone next time bye bye
