简单的跨云环境极其罕见
91% 的高管期待改进“(他们的)公有云环境的一致性”。
应用需要进行现代化改造
68% 的开发人员希望扩大现代应用框架、API 和服务的使用范围。
分散办公模式继续存在
72% 的企业员工正通过非传统环境
办公。
安全性是一项自上而下的顾虑
与安全性、数据和隐私问题相关的风险仍然是首要的多云挑战。
让开发人员能够灵活地使用任何应用框架和工具,以便在任何云上建立安全一致且快捷的生产路径。
将安全性和网络作为内置分布式服务提供给任何云中的用户、应用、设备和工作负载。
一致地运行应用和基础架构,跨云统一监管和洞悉性能和成本。
让您的员工能够从任何设备安全、顺畅地访问企业应用,随时随地高效工作。
跨公有云和电信云、数据中心及边缘环境大规模运行企业级应用和平台服务。
更快地投入生产
在任何公有云或本地 Kubernetes 集群上快速安全地构建和部署。
简化 Kubernetes 操作
大规模构建和运营安全的多云容器基础架构。
与应用开发专家结对
通过对现有应用进行现代化改造和构建创新的新产品来释放价值。
自如地连接和运行
对您的私有和公有云基础架构进行现代化改造,从而减少价值实现时间、降低成本并增强安全性。
更顺畅的数字化体验
以优化方式安全、可靠地在云端和边缘连接应用,为用户提供独有的顺畅体验。
使用跨公有云、数据中心和边缘环境的一致云基础架构大规模运行企业应用。
VMware 研究:多云战略
了解为什么企业发现多云战略对成功至关
重要。
提供有吸引力的体验
把员工放在首位,提供多样设备选择、灵活性以及无缝、一致的高质量体验。
保护现今随处可用的工作空间
通过情景智能和互联控制点来简化向零信任模式的转变。
实现工作空间自动化
通过合规性、工作流和性能方面的智能管理,针对成效而不是任务进行管理。
保护和连接工作负载
通过我们工具中内置的透明度,在应用、用户和实体之间实现一致的安全性和网络连接。
保护 API — 新端点
提高应用速度并集中管理、保护、连接和治理您的集群,无论它们位于何处。
面向未来
获取跨用户、端点和网络的内置威胁情报,以在动态环境中不断改进您的保护。
与 VMware 合作伙伴携手合作
合作伙伴利用他们的专业知识和 VMware 技术交付成果,为我们共同的客户创造非凡价值。
成为合作伙伴
VMware 正携手我们的合作伙伴打造新的多云生态系统,旨在成为客户不可或缺的要素。
Many users of the VMware Academic Software Licensing program ask us about how they can most effectively use vSphere in their classroom, especially given the limitations on license keys provided under the Licensing program. It helps to understand the purpose of the licensing program, and some examples of creative ways to use licenses follow.
The Software Licensing program was created to provide end users — primarily students — with access to VMware’s core products. Most directly that means students can download software for use on their own personal machines, either to enhance their day-to-day computing environment or to learn about VMware’s core enterprise-focused products. The program also supports the installation of VMware software on shared physical infrastructure, but only within certain parameters. Most specifically, the program’s primary purpose is NOT to support the deployment of shared infrastructure using free licenses, in part because the lack of support provided (or available) with licenses places an undue burden on local administrators.
Each student user of the Academic Software Licensing program is entitled to receive one license key per product per year, and users can renew license keys prior to their expiration. License keys for desktop products — Fusion, Workstation, and Player — can only be used on a single system, whereas infrastructure products — VMware vSphere — have a ‘capacity’ value associated with the license key, which entitles the user to enable up to that many physical CPUs (typically 4). The number of CPU cores is irrelevant, vSphere licensing is based upon physical CPUs in a server (sometimes referred to in order to reduce ambiguity as to the number of CPU sockets). The capacity of a single license key can be distributed across multiple hosts, e.g., a 4-CPU key can be used to enable two hosts, each with 2 CPUs.
These constraints on license keys mean that a single user can only create a very small vSphere system using their own license keys. While such a small system should still be sufficient for an individual to demonstrate and learn about all of the core concepts of VMware’s products, teachers may wish to build larger systems for use in the classroom. Although the program is unable to provide additional license keys directly to teachers and administrators for that purpose, there are various creative ways in which a classroom environment can be created and managed while conforming to the license agreement.
The core of the vSphere product is the ESXi hypervisor. ESXi is not installed as an application, onto an existing host operating system. Rather, it is deployed into a ‘bare metal’ environment, usually a physical server, and replaces any other OS on that system (dual booting is possible, but left as an exercise for the reader). Thus it is generally not practical to have students install ESXi onto their own laptops or other personal machines unless students have additional machines at their disposal that can be dedicated to a role as an ESXi host. Some classes do in fact provide each student, or group of students, with a physical server that is assigned to them for the duration of the class; another alternative is to configure a machine to boot ESXi from external media.
An alternative, possibly complementary, approach is to install ESXi into a VM running within one of VMware’s desktop (hosted) virtualization products: Fusion (for Mac OS X systems) or Workstation (for Windows PCs). While this typically imposes some additional virtualization overhead on the ESXi system it provides the user with a much greater degree of flexibility, and, most importantly, allows concurrent use of the standard desktop OS while ESXi is running. However, one caveat is that ESXi requires substantial resources in order to be installed: current versions require 2 CPU cores and 4GB of memory. The vCenter management server, which is typically required to manage ESXi, also requires at least 4GB to be usable, and thus a basic system of one ESXi host and one vCenter server requires 8GB of memory. Most current laptop environments do not provide sufficient physical memory to support that within a hosted environment.
Most of VMware’s products can be activated for a 30-60 day evaluation period. This allows administrators to deploy software to physical (or virtual) servers in advance of the distribution of license keys to those servers. Alternatively, some classes may include the installation of software on servers as the first hands-on step in the class. Subsequently, students access the VMAP Software Licensing portal and download license keys for particular products to be used in their class.
vSphere license keys can be deployed to hosts in two different ways: directly to the ESXi host itself, or managed collectively in the vCenter server. For a very small system, up to 4 physical CPUs, it may be sufficient for students to deploy a single license key per system, but in environments where teachers wish to demonstrate concepts using larger systems, the students should be assigned to teams that can combine their individual license keys. In that manner, a team of 2-4 students can collectively contribute sufficient license keys to enable 8-16 physical CPUs across multiple hosts.