1 01:00:00,133 --> 01:00:06,199 Hello and welcome! This is VCD Roundtable Ep. 53. 2 01:00:07,466 --> 01:00:12,300 And a lot has happened in the VMware Cloud Provider space, 3 01:00:12,466 --> 01:00:16,233 not only that we had, I think, one of the largest Challenge 4 01:00:16,366 --> 01:00:19,699 Days in Sweden last week -- 5 01:00:19,699 --> 01:00:20,466 no, this week. 6 01:00:21,633 --> 01:00:24,666 But also quite a few announcements 7 01:00:24,866 --> 01:00:28,666 from VMwareby Broadcom around products, licensing, 8 01:00:29,099 --> 01:00:33,233 packaging, and also some announcements 9 01:00:33,233 --> 01:00:34,833 we are going to make at the end 10 01:00:34,833 --> 01:00:36,766 regarding some upcoming events. 11 01:00:37,066 --> 01:00:41,900 But before we get to that, Sascha, do you want to start? 12 01:00:43,633 --> 01:00:44,066 I can. 13 01:00:45,566 --> 01:00:45,766 Hello. 14 01:00:47,666 --> 01:00:49,800 Yes, welcome also from my side. 15 01:00:50,233 --> 01:00:52,033 Maybe you can mute yourself. 16 01:00:52,633 --> 01:00:52,833 Yes. 17 01:00:53,166 --> 01:00:53,366 OK. 18 01:00:54,166 --> 01:00:55,333 Welcome also from my side. 19 01:00:56,166 --> 01:00:58,666 Yeah, we had a great week with the Challenge Days 20 01:00:58,766 --> 01:01:01,099 in Scandanavia, a lot of new 21 01:01:01,099 --> 01:01:03,366 inputs from the service providers, 22 01:01:03,966 --> 01:01:06,166 some parts we want to talk about later, 23 01:01:06,599 --> 01:01:10,466 so also some hints about some new features 24 01:01:10,466 --> 01:01:11,533 and how they work. 25 01:01:11,900 --> 01:01:14,366 And with that, Matthias. 26 01:01:16,199 --> 01:01:20,966 Yeah, curious to hear all the news, Toby. 27 01:01:21,466 --> 01:01:21,666 You? 28 01:01:22,500 --> 01:01:24,066 Yes, also the same for me. 29 01:01:24,300 --> 01:01:26,666 Hello and welcome to Ep. 53. 30 01:01:27,533 --> 01:01:29,099 So back to Sascha. 31 01:01:31,933 --> 01:01:36,066 Yes, so with that, as a topic 32 01:01:36,066 --> 01:01:38,266 for this episode of the VCD Roundtable, 33 01:01:39,366 --> 01:01:42,233 we will cover a bit of what's new, 34 01:01:42,233 --> 01:01:45,133 what's changing in the service provider 35 01:01:45,233 --> 01:01:49,033 program, and what's interesting to 36 01:01:49,033 --> 01:01:51,333 know, what we want to share with you. 37 01:01:51,366 --> 01:01:54,966 So Monday and Tuesday, we had 38 01:01:54,966 --> 01:01:58,233 the Challenge Days in Stockholm. 39 01:01:58,933 --> 01:02:01,699 And there was one interesting topic. 40 01:02:02,000 --> 01:02:05,166 We got a few requests on how it works, 41 01:02:05,233 --> 01:02:09,500 and nobody finds how does it work in the user interface 42 01:02:09,666 --> 01:02:12,433 or in the Cloud Director interface. 43 01:02:12,766 --> 01:02:18,633 And this is a VM placement on guest OS base. 44 01:02:19,566 --> 01:02:22,233 So that means we have a lot of 45 01:02:22,233 --> 01:02:27,133 vendors who are in need or products that 46 01:02:27,133 --> 01:02:29,199 need to be licensed on the host space. 47 01:02:30,566 --> 01:02:32,666 And a lot of service providers 48 01:02:32,666 --> 01:02:37,133 started to select or create 49 01:02:37,666 --> 01:02:40,366 affinity rules at the vCenter level. 50 01:02:41,233 --> 01:02:45,300 But the problem is, if we create it on the vCenter level, 51 01:02:45,433 --> 01:02:47,966 we had problems every time in 52 01:02:47,966 --> 01:02:49,466 combination with Cloud Director. 53 01:02:50,400 --> 01:02:52,666 And now we have this feature 54 01:02:52,666 --> 01:02:55,033 with the last Cloud Director version 55 01:02:55,233 --> 01:02:58,266 that we can create policies that 56 01:02:58,266 --> 01:03:01,900 replace VMs on dedicated hosts based 57 01:03:02,166 --> 01:03:03,433 on the guest OS. 58 01:03:05,766 --> 01:03:06,933 Yes, Matthias? 59 01:03:10,566 --> 01:03:13,466 I would not say with the latest VCD version 60 01:03:13,666 --> 01:03:15,233 that features there since-- 61 01:03:17,633 --> 01:03:19,033 I don't know, 10.4, 10.3? 62 01:03:21,266 --> 01:03:21,900 Okay, yeah. 63 01:03:23,400 --> 01:03:24,066 Just saying. 64 01:03:24,466 --> 01:03:25,166 Yeah, sure. 65 01:03:25,633 --> 01:03:28,366 But again, a lot of-- 66 01:03:28,366 --> 01:03:30,233 Maybe it just appeared within the community. 67 01:03:30,866 --> 01:03:32,966 Yes, so a few service providers searched for it. 68 01:03:33,033 --> 01:03:37,633 And it's only possible to configure it over API. 69 01:03:39,000 --> 01:03:40,433 So that's the point. 70 01:03:41,266 --> 01:03:42,733 Have you found it in the 71 01:03:42,733 --> 01:03:44,933 interface on Cloud Director? 72 01:03:45,633 --> 01:03:45,833 Really? 73 01:03:47,033 --> 01:03:48,666 So maybe you can share where it is. 74 01:03:48,666 --> 01:03:49,633 It's a placement policy. 75 01:03:50,266 --> 01:03:51,666 So maybe a misunderstanding. 76 01:03:52,733 --> 01:03:53,633 Maybe it's a misunderstanding. 77 01:03:53,933 --> 01:03:55,533 But in the end, you just 78 01:03:55,533 --> 01:03:58,766 create these DRS groups in vSphere. 79 01:03:59,333 --> 01:04:00,599 And then you grab those groups 80 01:04:00,599 --> 01:04:02,766 and map it in the cloud director UI 81 01:04:02,766 --> 01:04:04,433 in the service provider context. 82 01:04:05,066 --> 01:04:08,866 Then you can publish those placement policies to a tenant. 83 01:04:09,733 --> 01:04:11,099 And then you just use it. 84 01:04:11,500 --> 01:04:13,833 That's how you place a virtual machine to a DRS group. 85 01:04:14,366 --> 01:04:16,333 And that has a DRS rule. 86 01:04:17,333 --> 01:04:19,866 Then the virtual machine is placed on the resepctive host 87 01:04:19,866 --> 01:04:20,566 group. 88 01:04:22,066 --> 01:04:25,866 Yes, but the feature means now that you 89 01:04:25,866 --> 01:04:28,900 can place virtual machines automatically 90 01:04:29,633 --> 01:04:30,833 based on guest OS. 91 01:04:31,466 --> 01:04:34,166 So if you have selected Windows, for example, 92 01:04:34,766 --> 01:04:37,800 all Windows virtual machines will be placed on dedicated-- 93 01:04:37,800 --> 01:04:39,666 sources. Ahh, so that's the misunderstanding. 94 01:04:40,000 --> 01:04:44,300 So you're talking about an automated placement. 95 01:04:44,833 --> 01:04:45,033 Yes. 96 01:04:45,599 --> 01:04:45,800 Yes. 97 01:04:47,599 --> 01:04:49,866 Because of licensing and so on. 98 01:04:50,366 --> 01:04:54,933 So maybe it was there before, but I don't know. 99 01:04:56,133 --> 01:04:58,066 As Matthias has just heard, we're talking 100 01:04:58,066 --> 01:04:59,566 about two different flavors. 101 01:04:59,566 --> 01:05:02,900 So the first flavor is just to have a normal VM placement 102 01:05:03,000 --> 01:05:06,099 policy, which has been there since 10.3 103 01:05:06,966 --> 01:05:12,466 It was there in VCD, where you as a customer can select, 104 01:05:12,933 --> 01:05:15,333 that you would like to utilize this placement policy. 105 01:05:15,333 --> 01:05:18,199 And then my VM gets placed on cluster number APC, whatever. 106 01:05:18,733 --> 01:05:22,566 Or inside the cluster of a particular group of hosts. 107 01:05:23,066 --> 01:05:24,133 But what is new-- 108 01:05:24,533 --> 01:05:28,933 and this is what Sascha is referring with 10.6.1-- 109 01:05:29,500 --> 01:05:33,466 is now-- and this is only available via the API. 110 01:05:34,333 --> 01:05:37,199 If the customer selects, for example, Windows, 111 01:05:37,866 --> 01:05:40,400 automatically the VMs gets placed 112 01:05:40,400 --> 01:05:42,733 on the host, which are entitled for Windows licensing. 113 01:05:43,866 --> 01:05:47,066 At the end, we are still talking about the same it is. 114 01:05:47,066 --> 01:05:49,900 A DRS-based group, host group, and VM group. 115 01:05:50,433 --> 01:05:56,400 But now, with 10.6.1 VCD can do this automatically 116 01:05:56,566 --> 01:06:00,500 without doing any interference from a service provider 117 01:06:00,800 --> 01:06:03,633 or from the customer itself 118 01:06:03,633 --> 01:06:07,900 just based on the OS you selected. 119 01:06:10,533 --> 01:06:12,733 Get a little amendment, and it's 10.6.1. 120 01:06:13,599 --> 01:06:14,400 10.6.1, OK. 121 01:06:15,500 --> 01:06:16,733 Not 10.6.1.1. 122 01:06:17,366 --> 01:06:17,566 OK. 123 01:06:20,366 --> 01:06:20,566 Good. 124 01:06:21,533 --> 01:06:23,933 So what else is new? 125 01:06:23,966 --> 01:06:29,733 So yeah, maybe let's start with 126 01:06:29,733 --> 01:06:31,933 the newest information about 127 01:06:31,933 --> 01:06:33,566 the new pricing guide. 128 01:06:33,933 --> 01:06:38,166 There is new information about download quantity 129 01:06:38,633 --> 01:06:40,166 of license keys. 130 01:06:40,566 --> 01:06:41,266 What does it mean? 131 01:06:43,000 --> 01:06:47,333 So they are-- yeah, for a long time, and in the contract, 132 01:06:47,333 --> 01:06:52,433 there was a maximum limit of license keys you can or you 133 01:06:52,699 --> 01:06:55,833 should create per contract. 134 01:06:55,833 --> 01:06:57,833 It was limited on the commits. 135 01:06:58,933 --> 01:07:01,066 But this was never executed in the past. 136 01:07:03,366 --> 01:07:05,066 And now there is-- 137 01:07:05,633 --> 01:07:08,000 or there comes a message that you 138 01:07:08,000 --> 01:07:12,666 can have a maximum of 200% of license keys 139 01:07:13,533 --> 01:07:14,699 regarding your commit. 140 01:07:15,366 --> 01:07:19,000 That means, for example, if you have 2,000 license keys-- 141 01:07:19,666 --> 01:07:21,966 2,000 calls in a commit, you can 142 01:07:22,000 --> 01:07:26,233 create a maximum of 4,000 license keys on that contract. 143 01:07:28,400 --> 01:07:31,066 Then that will become interesting for a lot of service 144 01:07:31,066 --> 01:07:32,266 providers who are running a 145 01:07:32,266 --> 01:07:35,766 lot of hosts in maintenance mode 146 01:07:35,866 --> 01:07:40,233 or non-active and try to use them as an overage. 147 01:07:42,033 --> 01:07:45,433 So that's one very interesting point here. 148 01:07:47,500 --> 01:07:51,966 And in the last weeks, there was the message 149 01:07:52,133 --> 01:07:59,233 that they will go down to 125% -- the max you can create and 150 01:07:59,233 --> 01:08:00,800 download. 151 01:08:01,433 --> 01:08:04,266 But that looks like this has changed again, 152 01:08:04,566 --> 01:08:08,933 because this information with the 125% is removed. 153 01:08:08,933 --> 01:08:11,466 And also in the pricing guide, they only 154 01:08:11,566 --> 01:08:13,366 mention now the 200%. 155 01:08:15,699 --> 01:08:18,066 So let's see what happens there. 156 01:08:18,466 --> 01:08:20,066 But if you need more license 157 01:08:20,066 --> 01:08:21,533 keys, maybe you can create them. 158 01:08:21,733 --> 01:08:24,766 So the limit will be active in the next days. 159 01:08:27,666 --> 01:08:29,866 That's one important new topic. 160 01:08:30,966 --> 01:08:31,933 The other topic is-- 161 01:08:31,933 --> 01:08:32,966 I think the latest email communication 162 01:08:33,166 --> 01:08:36,399 was today regarding this topic you just mentioned. 163 01:08:36,666 --> 01:08:39,133 I think the last email I received about that was today. 164 01:08:39,133 --> 01:08:40,500 So they're constantly sending 165 01:08:40,500 --> 01:08:42,100 out emails over and over and over. 166 01:08:42,866 --> 01:08:43,066 Yes. 167 01:08:44,266 --> 01:08:48,033 And with that, also the announcement today, 168 01:08:48,833 --> 01:08:51,133 usage meter 9 is out. 169 01:08:53,133 --> 01:08:56,333 That means you have -- as aservice provider have now -- 170 01:08:56,333 --> 01:09:00,633 90 days to upgrade your usage meters. 171 01:09:03,133 --> 01:09:05,133 That means it's very easy. 172 01:09:05,333 --> 01:09:06,699 There is an upgrade process. 173 01:09:07,333 --> 01:09:10,966 The only important topic, if you upgrade your usage meter, 174 01:09:11,433 --> 01:09:17,966 you need to create a token in the new portal, in the VCF 175 01:09:18,066 --> 01:09:23,300 portal, and need to enter this token in your usage meter 176 01:09:24,366 --> 01:09:26,866 when you're deploying the update. 177 01:09:28,033 --> 01:09:28,666 That's important. 178 01:09:29,699 --> 01:09:32,833 Also, for new usage meters, you need 179 01:09:32,833 --> 01:09:36,766 to first deploy the usage meter. 180 01:09:36,766 --> 01:09:39,899 You will get the ID like before from the usage meter. 181 01:09:39,933 --> 01:09:42,733 You can enter it in your VCF portal. 182 01:09:43,966 --> 01:09:47,033 Then you will-- or then you can create the token 183 01:09:47,033 --> 01:09:48,366 or must create the token. 184 01:09:48,733 --> 01:09:52,466 And the token must be placed manually in the usage meter. 185 01:09:52,766 --> 01:09:55,466 Again, that's so a connection can be established. 186 01:09:57,466 --> 01:10:01,633 And with the new usage meter, there are some parts 187 01:10:01,633 --> 01:10:03,166 you need to take a look at. 188 01:10:03,166 --> 01:10:05,433 So first of all, please make sure 189 01:10:05,433 --> 01:10:08,733 that you have new license keys deployed on your systems, 190 01:10:09,066 --> 01:10:12,566 because only the new license keys can be measured. 191 01:10:14,433 --> 01:10:17,833 And the new usage meter is now has the feature 192 01:10:18,000 --> 01:10:23,733 that the usage meter can meter also vDefend Firewall. 193 01:10:26,066 --> 01:10:30,466 And as we all know from the different contact tracks, 194 01:10:31,266 --> 01:10:34,833 until a few days ago, I think it was Monday or Tuesday 195 01:10:35,066 --> 01:10:37,866 when the new pricing guide was released. 196 01:10:38,433 --> 01:10:43,833 So before, there were no or there were no add-ons 197 01:10:44,199 --> 01:10:46,066 or no overage for add-ons. 198 01:10:47,300 --> 01:10:49,033 So you needed to go with a commit 199 01:10:49,033 --> 01:10:51,199 if you wanted to go with vDefend firewall. 200 01:10:52,266 --> 01:10:56,233 And there is now an exception for vDefend (NSX vDefend) 201 01:10:56,500 --> 01:11:02,166 So you can go now on demand with Distributed Firewall 202 01:11:02,333 --> 01:11:04,333 and Gateway Firewall and also 203 01:11:04,333 --> 01:11:05,899 with advanced threat protection. 204 01:11:07,899 --> 01:11:12,366 On the first view, that's a benefit for all 205 01:11:12,366 --> 01:11:14,933 of the service providers who want to try it. 206 01:11:15,733 --> 01:11:18,300 There's also the information coming out now 207 01:11:18,433 --> 01:11:23,800 that it is counted on host-based 208 01:11:24,500 --> 01:11:29,466 no longer on cluster-based like it was before. 209 01:11:31,033 --> 01:11:34,033 But that also means, please, before you 210 01:11:34,133 --> 01:11:37,966 deploy your new usage meter, please check your systems. 211 01:11:38,466 --> 01:11:41,300 If Distributed Firewall is enabled, 212 01:11:42,633 --> 01:11:45,533 If you're running a user-created 213 01:11:45,633 --> 01:11:52,600 Firewall, because if you deploy the new usage meter, 214 01:11:53,100 --> 01:11:55,733 running Distributed Firewall, have no license, 215 01:11:56,699 --> 01:11:58,533 it will be metered now. 216 01:11:58,533 --> 01:12:01,466 And you have to pay the overage for that 217 01:12:03,033 --> 01:12:03,933 for the list price. 218 01:12:05,333 --> 01:12:06,866 So that's very important to know. 219 01:12:07,533 --> 01:12:09,766 So yeah, please check it beforehand. 220 01:12:12,933 --> 01:12:15,933 And additional to that with the hosts, 221 01:12:16,833 --> 01:12:19,233 so on the host-based Distributed Firewall, 222 01:12:20,166 --> 01:12:24,233 so you can apply Distributed Firewall 223 01:12:24,366 --> 01:12:26,466 and pin Distributed Firewall 224 01:12:26,466 --> 01:12:28,300 to specific hosts in a cluster. 225 01:12:29,766 --> 01:12:33,333 So if you have only a small amount of customers 226 01:12:33,533 --> 01:12:38,133 who want to create or want to test or use Distributed 227 01:12:38,266 --> 01:12:41,266 Firewall, you are now able to use this feature 228 01:12:43,300 --> 01:12:47,199 and license only the hosts for Distributed Firewall 229 01:12:47,800 --> 01:12:49,366 you want to have. 230 01:12:56,166 --> 01:12:58,199 One thing I would like to add, especially 231 01:12:58,500 --> 01:13:01,766 on the NSX side, please ensure that you really 232 01:13:01,866 --> 01:13:04,666 have only new license keys. 233 01:13:05,433 --> 01:13:09,000 The legacy keys will not be metered in the correct way. 234 01:13:09,233 --> 01:13:11,000 This is also clearly documented already. 235 01:13:11,566 --> 01:13:13,666 The old license keys or the legacy keys 236 01:13:13,800 --> 01:13:16,899 will not be metered in the right way, which then 237 01:13:16,899 --> 01:13:19,766 can lead to a massive overage. 238 01:13:20,566 --> 01:13:22,366 So please ensure that you really are 239 01:13:22,366 --> 01:13:25,566 going to utilize the new NSX license keys. 240 01:13:26,533 --> 01:13:29,033 And if you have the add-ons like vDefend, 241 01:13:29,233 --> 01:13:31,300 then utilize the add-on license keys. 242 01:13:31,533 --> 01:13:32,766 But please get rid-- 243 01:13:33,966 --> 01:13:35,933 before you really switch to 244 01:13:35,933 --> 01:13:38,933 the new usage meter to version 9, 245 01:13:39,466 --> 01:13:41,966 please get rid also of the old NSX license keys. 246 01:13:42,800 --> 01:13:46,133 That's really an important topic in the documentation. 247 01:13:51,199 --> 01:13:55,600 Yes, and with that, take a look at Distributed Firewall 248 01:13:56,066 --> 01:13:57,666 and add-ons threat protection. 249 01:13:58,033 --> 01:14:01,666 Work together with your sales team 250 01:14:01,833 --> 01:14:04,666 and create packages out of it. 251 01:14:04,666 --> 01:14:07,133 Because now it becomes really interesting for you 252 01:14:07,866 --> 01:14:09,233 to sell it to your customers. 253 01:14:09,566 --> 01:14:12,466 Also, if you have only a small amount of customers 254 01:14:13,000 --> 01:14:14,899 who want to start with Distributed Firewall, 255 01:14:15,600 --> 01:14:18,000 but security comes more and more important. 256 01:14:19,566 --> 01:14:23,833 And with that, you are now able to start 257 01:14:24,199 --> 01:14:25,633 with a small amount of hosts. 258 01:14:31,800 --> 01:14:39,266 I think it's overall very important to just keep an eye 259 01:14:39,266 --> 01:14:42,933 on all these timelines which are now showing up, especially 260 01:14:43,133 --> 01:14:43,633 in Europe. 261 01:14:43,633 --> 01:14:46,033 They fall in the summer season. 262 01:14:46,800 --> 01:14:51,733 So keep in mind that there are now additional timelines 263 01:14:51,966 --> 01:14:54,666 or something like that going to come for usage meter. 264 01:14:56,266 --> 01:14:58,866 Because that directly also influences new releases 265 01:14:58,866 --> 01:15:00,366 from Broadcom and other things. 266 01:15:00,899 --> 01:15:03,466 And the time frame they now provided 267 01:15:03,633 --> 01:15:07,300 is longer than what the contract actually said, 268 01:15:07,333 --> 01:15:10,333 because that was 14 days originally in there. 269 01:15:10,566 --> 01:15:13,266 So that would have been a much bigger stunt for everybody. 270 01:15:14,766 --> 01:15:17,033 Also, I don't think Sascha mentioned 271 01:15:17,199 --> 01:15:19,699 that there is documentation which came out 272 01:15:19,766 --> 01:15:22,600 from Broadcom on how to handle 273 01:15:22,600 --> 01:15:25,666 the offline bundles and stuff 274 01:15:25,666 --> 01:15:28,899 like that for VCF 5.2. 275 01:15:29,466 --> 01:15:31,266 For VCF 9, there should be a better solution 276 01:15:31,266 --> 01:15:32,366 for service providers. 277 01:15:32,833 --> 01:15:33,566 We will see. 278 01:15:34,166 --> 01:15:37,500 But for 5.2, it is now clearly documented 279 01:15:37,733 --> 01:15:41,266 how you should provide these offline bundles and everything 280 01:15:41,399 --> 01:15:43,433 else to your customers. 281 01:15:45,033 --> 01:15:49,233 And we can only strongly encourage you to really review 282 01:15:49,433 --> 01:15:49,733 that. 283 01:15:50,066 --> 01:15:55,366 Even after discussions, it's like Broadcom 284 01:15:55,566 --> 01:15:57,699 said again and again very, very clearly, 285 01:15:57,966 --> 01:16:04,800 it is not allowed to provide user accounts to the Broadcom 286 01:16:04,833 --> 01:16:06,766 portal to sub-CSPs. 287 01:16:07,533 --> 01:16:10,333 Even if you are basically three providers together 288 01:16:10,533 --> 01:16:13,166 under one contract, only the one under the contract 289 01:16:13,166 --> 01:16:15,166 is allowed to access the 290 01:16:15,166 --> 01:16:17,366 Broadcom portals, the Broadcom software 291 01:16:17,666 --> 01:16:19,800 downloads, do the license management, 292 01:16:19,800 --> 01:16:20,633 and everything else. 293 01:16:21,533 --> 01:16:25,000 Any other usage is a violation of the partner contract 294 01:16:25,199 --> 01:16:26,533 and the license agreement. 295 01:16:27,566 --> 01:16:31,333 And we did not only have the change 296 01:16:31,466 --> 01:16:35,433 of choosing between CSP and resale, this 297 01:16:35,433 --> 01:16:38,800 is directly also related to, let's say, 298 01:16:38,800 --> 01:16:40,333 misbehavior from partners. 299 01:16:40,966 --> 01:16:45,066 So even if you think that you can actually still do that, 300 01:16:45,633 --> 01:16:48,133 better be sure to really, really clarify that. 301 01:16:49,166 --> 01:16:52,899 I don't want to see you in a situation where you run 302 01:16:53,066 --> 01:16:55,366 into any serious issues with Broadcom 303 01:16:55,466 --> 01:17:00,433 because from what is heard, they are not actually 304 01:17:00,433 --> 01:17:02,666 going to joke around on these items. 305 01:17:03,500 --> 01:17:06,399 So make sure that you follow that. 306 01:17:06,399 --> 01:17:08,699 There is a Knowledge Base article describing all of that 307 01:17:08,699 --> 01:17:10,333 and how to do all of these things. 308 01:17:10,800 --> 01:17:14,066 And for 9, it hopefully should be different. 309 01:17:16,433 --> 01:17:20,533 We also heard during our event on Monday and Tuesday 310 01:17:20,766 --> 01:17:23,233 that there is a potential 311 01:17:23,233 --> 01:17:28,266 chance that VCF 9 might get a new VCD 312 01:17:28,399 --> 01:17:32,466 version on top of it, but only to make VCF 9 work. 313 01:17:33,933 --> 01:17:35,733 But again, the big, big question is, 314 01:17:35,966 --> 01:17:38,300 with the announcement that VCF in the future 315 01:17:38,300 --> 01:17:39,600 is not going to be-- 316 01:17:41,066 --> 01:17:44,133 VCD or VCD is not going to be the multi-tenant solution 317 01:17:44,399 --> 01:17:46,333 moving forward, starting with 9. 318 01:17:47,166 --> 01:17:50,066 The big question is really is whether you are going to do-- 319 01:17:50,633 --> 01:17:53,833 or whether you are going to want to combine these. 320 01:17:54,666 --> 01:17:57,566 However, with all the changes in VCF 9, 321 01:17:57,566 --> 01:18:00,666 we said that in the last two days in Stockholm very, very 322 01:18:00,766 --> 01:18:02,733 clearly again and again, it makes sense 323 01:18:02,800 --> 01:18:05,833 besides moving yourself to 5.2 point whatsoever, 324 01:18:07,066 --> 01:18:10,399 to also make sure that your internal teams are all 325 01:18:10,466 --> 01:18:11,366 trained already. 326 01:18:11,933 --> 01:18:13,633 Start training on VCF 9. 327 01:18:13,633 --> 01:18:16,333 There are so many substantial changes in the infrastructure 328 01:18:17,166 --> 01:18:19,633 that it is good to actually get going on that one 329 01:18:19,633 --> 01:18:23,166 so that you are prepared if your customers demand anything 330 01:18:23,366 --> 01:18:24,233 from the perspective. 331 01:18:24,733 --> 01:18:28,733 So that is good to know as well. 332 01:18:29,833 --> 01:18:31,066 So what else do we have? 333 01:18:31,366 --> 01:18:32,366 Any other news, Matthias? 334 01:18:37,066 --> 01:18:39,433 We have a lot of rain currently in Vienna, 335 01:18:39,666 --> 01:18:41,233 but no, the weather changes. 336 01:18:41,733 --> 01:18:42,966 This is the news I have. 337 01:18:44,166 --> 01:18:46,433 So that means you have a lot of clouds in Vienna. 338 01:18:47,399 --> 01:18:48,066 Yeah, no. 339 01:18:48,066 --> 01:18:50,366 ... 340 01:18:50,366 --> 01:18:51,033 They're all gone. 341 01:18:51,366 --> 01:18:52,733 No backup, no restore. 342 01:18:55,066 --> 01:19:01,066 Maybe one more topic on news. 343 01:19:02,066 --> 01:19:05,833 So... 344 01:19:06,600 --> 01:19:06,766 Okay. 345 01:19:07,333 --> 01:19:10,433 So Tanzu Mission Control is back. 346 01:19:11,199 --> 01:19:15,600 So service providers for tenants of service providers. 347 01:19:15,866 --> 01:19:18,133 So you can deploy again Tanzu Mission Control 348 01:19:18,266 --> 01:19:19,300 self managed. 349 01:19:20,000 --> 01:19:22,233 That's included now in VCF. 350 01:19:23,699 --> 01:19:28,333 So that will be maybe for a few customers 351 01:19:28,600 --> 01:19:33,300 a real benefit to manage the Kubernetes environment. 352 01:19:35,366 --> 01:19:39,033 And it's again unclear what happens with TKGM. 353 01:19:39,300 --> 01:19:41,000 So in the last newsletter, they clearly 354 01:19:41,033 --> 01:19:44,066 mentioned that Broadcom will continue 355 01:19:44,333 --> 01:19:49,966 TKGM in the Telco Cloud Platform for Telco customers. 356 01:19:51,633 --> 01:19:55,000 But CSP customers are not mentioned there. 357 01:19:55,633 --> 01:20:00,066 So maybe we get some more information in the next days 358 01:20:00,233 --> 01:20:03,233 or week what happens with TKGM for service providers, 359 01:20:03,500 --> 01:20:05,533 especially for the CSE customers. 360 01:20:06,366 --> 01:20:09,966 What we heard is that will be supported for all 361 01:20:09,966 --> 01:20:12,566 of the service providers who 362 01:20:12,566 --> 01:20:15,133 used it before in the old model. 363 01:20:16,366 --> 01:20:19,033 But yeah, there is nothing in there written currently. 364 01:20:19,433 --> 01:20:21,899 So let's take a look. 365 01:20:23,033 --> 01:20:27,033 And what's also new in the new pricing guide 366 01:20:27,233 --> 01:20:33,533 is that data services, they were included before in VCF. 367 01:20:35,133 --> 01:20:37,133 And they are still included for everyone 368 01:20:37,133 --> 01:20:39,233 who used data services with VCF. 369 01:20:39,966 --> 01:20:43,233 But everyone who starts now with data services, 370 01:20:43,233 --> 01:20:47,366 it's no longer included and needs to be licensed per core. 371 01:20:50,800 --> 01:20:51,933 Is this or is it not a good idea. 372 01:20:52,133 --> 01:20:52,533 I don't know. 373 01:20:53,166 --> 01:20:55,966 Depending on the view for the CSPs, no. But for the 374 01:20:55,966 --> 01:20:59,366 shareholders maybe, let's see. 375 01:21:00,533 --> 01:21:00,733 Yeah. 376 01:21:01,566 --> 01:21:04,866 One thing here to add, Sascha, you mentioned it. 377 01:21:05,100 --> 01:21:08,133 TMC is now part of VCF. 378 01:21:09,533 --> 01:21:13,966 On the other hand, TMC as in SaaS application will go away. 379 01:21:13,966 --> 01:21:16,433 So for those who are still 380 01:21:16,433 --> 01:21:20,666 utilizing TMC hosted by Broadcom, 381 01:21:21,266 --> 01:21:24,633 please be aware this solution will go away. 382 01:21:25,266 --> 01:21:29,266 So you need to figure out how you can migrate your hosted 383 01:21:29,333 --> 01:21:33,133 TMC to a local installed TMC. 384 01:21:40,966 --> 01:21:41,133 Good. 385 01:21:41,566 --> 01:21:47,666 I think that was a lot of news from the VCSP program 386 01:21:48,000 --> 01:21:50,000 for another week. 387 01:21:51,433 --> 01:21:53,633 Just as a wrap up, I mean, we are going 388 01:21:53,733 --> 01:21:58,533 to come together with a group of our AI specialists team 389 01:21:58,600 --> 01:22:00,566 here in Dubai next week 390 01:22:00,566 --> 01:22:02,500 together with VMware and Broadcom. 391 01:22:02,500 --> 01:22:05,300 We have trainers from the US and the UK and everything else 392 01:22:05,333 --> 01:22:09,066 fly in so that we have a two days AI workshop. 393 01:22:09,333 --> 01:22:11,366 We are then going to head over to Bonn 394 01:22:11,366 --> 01:22:13,066 for the Service Provider Summit. 395 01:22:13,866 --> 01:22:17,666 Going to hold a keynote and workshop during that event. 396 01:22:18,600 --> 01:22:21,866 And then we are going to be at GITEX in Berlin. 397 01:22:23,366 --> 01:22:28,666 The following week and then we are off to Palo Alto 398 01:22:29,366 --> 01:22:30,766 for the first week of June. 399 01:22:31,233 --> 01:22:34,433 So if you are a service provider or if you are working 400 01:22:34,533 --> 01:22:38,866 for a service provider, if you want to also experience 401 01:22:39,000 --> 01:22:41,833 Challenge Days, if you want to actually be part 402 01:22:41,966 --> 01:22:45,333 of the ArchitectureThink Tank, then this 403 01:22:45,433 --> 01:22:48,333 will be a very, very special edition this year. 404 01:22:49,533 --> 01:22:52,233 Based on the invite by Broadcom, we 405 01:22:52,333 --> 01:22:55,933 will most likely we are clarifying the last couple 406 01:22:55,933 --> 01:22:56,899 of things tonight. 407 01:22:57,333 --> 01:23:00,366 But it looks like we will run both events 408 01:23:00,666 --> 01:23:01,966 on the Broadcom premises. 409 01:23:02,266 --> 01:23:04,100 We will have support from the BU's, 410 01:23:04,100 --> 01:23:05,266 but they will not change the 411 01:23:05,266 --> 01:23:06,966 generic format of our sessions. 412 01:23:07,600 --> 01:23:11,233 They just want to actually be able to network with you 413 01:23:11,399 --> 01:23:13,433 and actually get to know the service providers 414 01:23:13,633 --> 01:23:14,600 a lot better. 415 01:23:15,466 --> 01:23:18,733 So for those who were the last couple of months, 416 01:23:18,733 --> 01:23:22,133 as always saying, "it's so hard to get hold of these people" 417 01:23:22,233 --> 01:23:24,766 -- this is your chance, your opportunity. 418 01:23:26,733 --> 01:23:29,233 If you want to join these events, please ping us. 419 01:23:29,233 --> 01:23:30,666 It's still four weeks out. 420 01:23:31,699 --> 01:23:36,533 Monday, Tuesday, Challenge Days, Wednesday, Thursday 421 01:23:37,233 --> 01:23:39,133 is the Architecture Think Tank, I think 422 01:23:39,133 --> 01:23:41,933 we have a certain cap in number of people. 423 01:23:42,133 --> 01:23:45,966 And I'm expecting the remaining seats to go pretty fast. 424 01:23:46,399 --> 01:23:50,133 So if you want to join in, let us know as quickly as possible 425 01:23:50,366 --> 01:23:53,133 so that we get your seats reserved. 426 01:23:54,533 --> 01:23:56,033 And then we are going to be back in Dubai 427 01:23:56,066 --> 01:23:57,933 for another Challenge Days mid of June. 428 01:23:58,266 --> 01:24:00,933 So also, if you really want to have dry heat then, 429 01:24:01,266 --> 01:24:04,966 humid heat, then there's a place to be. 430 01:24:06,033 --> 01:24:08,766 We will definitely have above 30 degrees Celsius. 431 01:24:09,033 --> 01:24:12,333 There is a high chance for over 40 degrees Celsius outside. 432 01:24:12,333 --> 01:24:14,466 So if you enjoy that, that is definitely 433 01:24:14,633 --> 01:24:16,066 the place for your Challenge Days. 434 01:24:17,933 --> 01:24:20,300 That being said, thank you for participating. 435 01:24:20,333 --> 01:24:22,800 Thank you for joining in. 436 01:24:22,800 --> 01:24:24,500 If you have any questions or anything else, 437 01:24:24,500 --> 01:24:27,266 feel always free to ping us or join one of our communities. 438 01:24:28,333 --> 01:24:29,966 With that being said, I'm out. 439 01:24:30,566 --> 01:24:30,766 Sascha? 440 01:24:32,666 --> 01:24:33,600 Yes, thank you. 441 01:24:33,966 --> 01:24:35,766 And see you at one of the Challenge Days 442 01:24:35,766 --> 01:24:37,699 or the Architecture Think Tank. 443 01:24:37,933 --> 01:24:42,166 Or maybe if you are on GITEX or at the Service Providers 444 01:24:42,166 --> 01:24:44,666 Summit, ping us and let's it together. 445 01:24:46,899 --> 01:24:47,100 Toby? 446 01:24:47,766 --> 01:24:48,766 Yeah, thanks for joining. 447 01:24:49,033 --> 01:24:50,766 See you in the next episode. 448 01:24:51,033 --> 01:24:52,566 See you in one of the next events. 449 01:24:53,600 --> 01:24:53,933 Matthias. 450 01:24:55,833 --> 01:24:56,300 Thanks, everyone. 451 01:24:56,466 --> 01:24:56,833 Take care. 452 01:24:57,033 --> 01:24:57,566 See you around.