Mentionsy

Names mentioned in the modern world of VCF 9.

Names mentioned in the modern world of VCF 9.

Names mentioned in the modern world of VCF 9.

Names mentioned in the modern world of VCF 9.

Names mentioned in the modern world of VCF 9.

Ultimately, for the last couple of years I've been working for what now is the VCF business unit, which before the merger was actually part of the storage and availability team.

Więc, kiedy rozmawiamy o VCF, to jest wielka rzecz w ostatnich kilku, myślę, że można powiedzieć, kilku latach, ponieważ, wiesz, VCF 9, tzn.

prawdziwy VCF, tak?

Wszyscy go teraz nazywają, ponieważ to był VCF 5 i wszyscy mówili, że to jest platforma, ale teraz z VCF 9 to jest prawdziwy, prawdziwy związek, prywatny cloud, prawdziwa platforma prywatnego cloudu.

We can call it a storage platform, it's not vSAN anymore, it's a storage platform, part of the VCF.

Do you see that with the recently added to the VCF stack as included, let's say, the platform for AI platform and the storage platform, do you see their attraction?

As I mentioned, if you look at vSAN itself as a storage platform, of course it's fully integrated with VCF and with vSphere in general, so any workload can benefit from it.

Now the storage platform in VCF, generally vSAN, have capability of object.

After I've had a conversation with the various teams, I'm guessing going forward it will be called VCF, Native S3 Object Storage, because it is very much a service that needs to run on top of VCF itself, because for instance, in order to enable it, it will require VCF automation, because that will provide that multi-tenancy layer that customers will expect.

If you look at the platform itself and you look at some of the use cases, I think of course for us there are various use cases that could be very interesting, but they could be as simple as backup and recovery, whether that is for the VCF components itself or maybe for, let's say, Kubernetes cluster.

If you look at the platform as well, and just to explain to those who are not familiar with it, with VCFA, of course, as you mentioned, that is the multi-tenancy layer, and when I explained it during the presentation, I could also notice there were some people looking at me like, yeah, but I don't, I mean, I have a provider administrator or an infrastructure administrator, but I don't have tenants and I don't have, well, I have a user that needs to access it, but there's nothing in between the user and myself.

Now, with VCFA, although we provide the option to have multiple persona, that is an infrastructure administrator that could be a line of business owner who manages the whole project and all of the resources that are part of the project and then at the end you have a developer that accesses a particular service, you don't necessarily need to have all of those.

Use VCF A, but you primarily use the APIs, of course.

You can fully do so and fully instantiate S3 object storage on top of the VCF platform using that API.

As you mentioned, it's part of VCF-A and the capabilities that it provides will allow you to have separate networks, to have separate tenants, to have separate users, set up security for all of those different components.

As you can imagine, with S3 object storage, as it is going to be orchestrated through the VCFA platform, of course, all the multi-tenancy aspects that apply to VCFA will automatically apply to S3 object storage as well.

And not just for vSAN, by the way, that also applies to any storage system that is connected to VCF.

Poza wszystkim, o czym rozmawialiśmy, jak stworzyliśmy architekturę, w VCF 9 mamy również obszar operacyjny, który jest obligatoryjny.

Wersja 9 to wielki krok naprzód, to na pewno, z VCF 9.

It's so integrated with the VCF platform that starts to be platform itself that's using vSAN under it, right?