Log in to your Red Hat account
Your Red Hat account gives you access to your member profile and preferences, and the following services based on your customer status:
Not registered yet? Here are a few reasons why you should be:
- Browse Knowledgebase articles, manage support cases and subscriptions, download updates, and more from one place.
- View users in your organization, and edit their account information, preferences, and permissions.
- Manage your Red Hat certifications, view exam history, and download certification-related logos and documents.
Your Red Hat account gives you access to your member profile, preferences, and other services depending on your customer status.
For your security, if you're on a public computer and have finished using your Red Hat services, please be sure to log out.Log out
What's the difference between cloud and virtualization?
It鈥檚 easy to confuse virtualization and cloud, particularly because they both revolve around creating useful environments from abstract resources. However, virtualization is a technology that allows you to create multiple simulated environments or dedicated resources from a single, physical hardware system, and clouds are IT environments that abstract, pool, and share scalable resources across a network. To put it simply, virtualization is a technology, where cloud is an environment.
Clouds are usually created to enable cloud computing, which is the act of running workloads within that system.
Cloud infrastructure can include a variety of bare-metal, virtualization, or container software that can be used to abstract, pool, and share scalable resources across a network to create a cloud. At the base of cloud computing is a stable operating system (like Linux庐). This is the layer that gives users independence across public, private, and hybrid environments.
If you have intranet access, internet access, or both already established, virtualization can then be used to create clouds, though it鈥檚 not the only option.
With virtualization, software called a hypervisor sits on top of physical hardware and abstracts the machine's resources, which are then made available to virtual environments called virtual machines. These resources can be raw processing power, storage, or cloud-based applications containing all the runtime code and resources required to deploy it.
If the process stops here, it's not cloud鈥攊t's just virtualization.
Virtual resources need to be allocated into centralized pools before they're called clouds. Adding a layer of management software gives administrative control over the infrastructure, platforms, applications, and data that will be used in the cloud. An automation layer is added to replace or reduce human interaction with repeatable instructions and processes, which provides the self-service component of the cloud.
You鈥檝e created a cloud if you鈥檝e set up an IT system that:
- Can be accessed by other computers through a network.
- Contains a repository of IT resources.
- Can be provisioned and scaled quickly.
Clouds deliver the added benefits of self-service access, automated infrastructure scaling, and dynamic resource pools, which most clearly distinguish it from traditional virtualization.
Virtualization has its own benefits, such as server consolidation and improved hardware utilization, which reduces the need for power, space, and cooling in a datacenter. Virtual machines are also isolated environments, so they are a good option for testing new applications or setting up a production environment.
A practical comparison
Virtualization can make 1 resource act like many, while cloud computing lets different departments (through private cloud) or companies (through a public cloud) access a single pool of automatically provisioned resources.
Virtualization is technology that allows you to create multiple simulated environments or dedicated resources from a single, physical hardware system. Software called a hypervisor connects directly to that hardware and allows you to split 1 system into separate, distinct, and secure environments known as virtual machines (VMs). These VMs rely on the hypervisor鈥檚 ability to separate the machine鈥檚 resources from the hardware and distribute them appropriately.
Cloud computing is a set of principles and approaches to deliver compute, network, and storage infrastructure resources, services, platforms, and applications to users on-demand across any network. These infrastructure resources, services, and applications are sourced from clouds, which are pools of virtual resources orchestrated by management and automation software so they can be accessed by users on-demand through self-service portals supported by automatic scaling and dynamic resource allocation.
|Purpose||Create multiple simulated environments from 1 physical hardware system||Pool and automate virtual resources for on-demand use|
|Use||Deliver packaged resources to specific users for a specific purpose||Deliver variable resources to groups of users for a variety of purposes|
|Lifespan||Years (long-term)||Hours to months (short-term)|
|Cost||High capital expenditures (CAPEX), low operating expenses (OPEX)||Private cloud: High CAPEX, low OPEX|
Public cloud: Low CAPEX, high OPEX
|Scalability||Scale up||Scale out|
|Tenancy||Single tenant||Multiple tenants|
How do I move from virtualization to cloud computing?
If you already have a virtual infrastructure, you can create a cloud by pooling virtual resources together, orchestrating them using management and automation software, and creating a self-service portal for users鈥攐r you can let something like Red Hat庐 OpenStack庐 Platform do a lot of that work for you. But moving from virtualization to cloud computing isn鈥檛 that simple when you鈥檙e bound to a vendor鈥檚 enterprise-license agreement, which might limit your ability to invest in modern technologies like clouds, containers, and automation systems.
The OpenStack® Word Mark and OpenStack Logo are either registered trademarks / service marks or trademarks / service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation or the OpenStack community.