UNIDAD II ALIMENTOS Y DIETA
2.7. LEYES DE LA ALIMENTACIÒN
This topic identifies the aspects of cloud computing services and solutions.
© 2012 Cisco and/or its affiliates. All rights reserved. DCUCD v5.0—#-20
Benefits: • Scalability • On-demand availability • Efficient utilization • CapEx to OpEx • Pay-per-use model Challenges: • No standard provisioning • No standard metering and billing • Limited customer control
• Security
• Offline operation
Flexibility
Cost
Cloud computing offers several benefits but also introduces some challenges or drawbacks that are not present in the current IT deployment model.
The benefits are the following:
n Scalability: When needed, the service provider can easily add resources to the cloud.
n On-demand availability: When needed, the customer gets resources (if available) upon
request.
n Efficient utilization: Sharing the physical resources among many customers and using the
well-known service provider model enables even higher utilization of the infrastructure resources.
n Capital expenditures (CapEx) to operating expenses (OpEx): Instead of buying and
owning the equipment, the customer rents the resources when needed and releases them when no longer needed. This arrangement effectively reduces the CapEx.
n Pay-per-use model: Because the equipment and resources are not owned by the customer,
the costs are only paid for when really required. This model enables a pay-per-use and pay- as-you-grow operational model for the customers.
The current drawbacks of cloud computing are the following:
n Lack of standardized provisioning solutions.
n Lack of standardized metering and billing mechanisms and applications.
n Limited control from the customer perspective—the customer effectively does not know where the resources are and has no control over how they are used.
n When applications and services are running in the cloud, the customer heavily relies on the service provider for security and confidentiality enforcement. For some customers who are bound by government directives and legislation, a public cloud is not possible.
n Having applications and services run in the cloud can increase business process
dependency on network connectivity. Furthermore, for such applications and services, the customer exclusively relies on the high-availability policies of the service provider for continuous IT operation.
© 2012 Cisco and/or its affiliates. All rights reserved. DCUCD v5.0—#-21
• Start simple and move to an advanced model over time • Compare between models with different reporting options • Ensure that model aligns with organizational requirements • Flexible costing options, mix and match between models
Costing Model Description Utilization-based
costing
Variable costs based on actual resources used Allocation-based
costing
Variable costs based on time of allocating resources
Fixed costing Fixed cost for an item
Com
pl
ex
ity
Service providers or internal IT have a key building block for delivering IT as a service: the infrastructure. Thus there is a need to meter resources offered and used, including broadband network traffic, public IP addresses, and other services such as DHCP, NAT, firewalling, and so on.
Service providers must create a showback or charge-back hierarchy that provides the basis for determining cost structures and delivery of reports. The main difference between charge-back and showback is that charge-back is used by service providers to charge for the cloud resources used, whereas the showback is used by the internal IT to meter and report on physical resource usage.
Multiple cost models provide flexibility in measuring costs. Three basic cost models are typically used:
n Fixed cost: Specific per-VM instance costs, such as floor space, power and cooling,
software, administrative overhead, or licenses. These aspects either cannot be metered, it is too complicated to properly meter the usage, or the usage does not change through time.
n Allocation-based costing: Variable costs per virtual machine based on allocated resources,
such as the amount of memory, CPU, or storage allocated or reserved for the virtual machine.
© 2012 Cisco Systems, Inc. Cisco Data Center Solution Architecture and Components 1-111
Cost models can be combined in a cost template, making it easy to start with a simple charge- back model and align with organizational requirements. Typically, the final cost comprises multiple elements.
© 2012 Cisco and/or its affiliates. All rights reserved. DCUCD v5.0—#-22
Virtualized Multitenant Infrastructure Operational Management Business Services
Front Office Portals Orchestration and Automation
Cloud Services
Resource Management
Any cloud solution is based on the following high-level framework:
n Multitenant virtualized infrastructure: The basis for the solution is the resources
combined in a multitenant virtualized infrastructure, which combines all the elements of the data center solution, with some extensions outside of the data center that are appropriate for the given cloud solution.
n Operational management: The vital part of the framework is the operational
management, which enables the owner of the cloud infrastructure to internally maintain and operate it.
n Resource management: The resource management is the middleware between the
infrastructure and the customer front-end systems. It provides the elements with which the infrastructure components and resources are managed, as well as the necessary API for the front end and the integration with customer-side management systems.
n Business services: The business services define the way in which the cloud services are
sold and managed from a customer-facing side.
n Front office portals, orchestration and automation: These are the customer-facing front-
end systems through which the customer, by the means of self-service and self- provisioning, uses the cloud solution, chooses among the available services from the catalog, selects the service level management, and so on.
n Cloud services: The cloud services are the services that the customer— IT administrator,
© 2012 Cisco and/or its affiliates. All rights reserved. DCUCD v5.0—#-23
Validated Designs
Pooled Storage
Configuration Management
Unified Network Fabric Unified Compute Virtualization Hypervisors Resource Management Operations Management Service Desk Financial Management
Orchestration and Automation Cloud Front Office
Client and Tenant Management Service Catalog Management Self Service Customer Portal Service Level Management
IaaS PaaS SaaS
Business Processes
Workflow Integration
Service
Provisioning Task Automation
Element Managers API Integration
Availability Management Fault Management Security Management Performance Management Change Management Capacity Management Configuration Management Inventory Management Billing Chargeback Metering Problem Management Incident Management
The architectural framework points to the differences between managed and cloud-based solutions. Cloud computing adds a large number of management applications and services, which include orchestration and self-provisioning portals accompanied by the service catalogs and service level management.
© 2012 Cisco Systems, Inc. Cisco Data Center Solution Architecture and Components 1-113
Summary
This topic summarizes the primary points that were discussed in this lesson.
© 2012 Cisco and/or its affiliates. All rights reserved. DCUCD v5.0—#-24
• Cloud computing provides on-demand resources in a pay-as-you-grow and self-service way.
• The foundation for cloud computing includes centralization, virtualization, standardization, and automation.
• The selected cloud model is governed by trust level.
• IaaS, PaaS, and SaaS have different responsibilities demarcation. • Cloud billing model can be based on fixed cost, resources allocated, or
real-time utilization.
• The cloud solution framework is based on the data center architecture.
References
For additional information, refer to these resources:
n http://www.cisco.com/web/solutions/trends/cloud/index.html
n http://www.cisco.com/web/solutions/trends/cloud/cloud_services.html#~CiscoCollabCloud n http://www.nist.gov/itl/cloud/index.cfm