Ready-Made Environment A is hosted by Virtual Server A and Ready-Made Environments is hosted by Virtual Server B. Virtual Servers A and B are hosted by Hypervisor A, which is part of a hypervisor cluster. An automated scaling listener intercepts cloud consumer requests and automatically invokes the on-demand generation of additional instances of ready-made environments, as required.A self-service portal and a usage and administration portal are also available to cloud consumers. The self-service portal can be used to request the provisioning of a new ready- made environment. Any cloud consumer that has already had a ready-made environment provisioned can configure and view information about that ready-made environment via the usage and administration portal.Cloud Consumer A accesses Ready-Made Environment A to work on the development of a new cloud service (1). Cloud Consumer B accesses Ready-Made Environment B to test a recently completed application comprised of three cloud services (2). Cloud Consumer C accesses the self-service portal to request the creation of a new ready-made environment(3).The cloud provider is required to perform an emergency maintenance outage on a cloud storage device used by all ready-made environments. The unplanned outage takes two hours. During this period, Cloud Consumers A and B are unable to access Ready-MadeEnvironments A and B and Cloud Consumer C receives an error when submitting a request to create a new ready-made environment.After the maintenance outage is over, Cloud Consumers A and B encounter the following problems:-> Cloud Consumer A is unable to recover session data that was kept in memory for an extended period, prior to the time of the outage.-> Cloud Consumer B has no access to Virtual Server B, which was moved toHypervisor B during the maintenance outage. When Cloud Consumer B attempts to ping Virtual Server B, the request times out.Even though Cloud Consumer C is able to lo
Ready Made Envi 1 (82.32 KiB) Viewed 82 times
A. A combination of the Load Balanced Virtual Server Instances and Synchronized Operating State patterns can be applied to establish a system capable of deferring state across multiple cloud storage devices, each located on a different virtual server. The Elastic Disk Provisioning pattern can be applied to persist virtual server configuration data across hypervisors so that connectivity is preserved whenever a virtual server is relocated to a different hypervisor. The Zero Downtime pattern can be a
B. The Elastic Disk Provisioning and Cross-Storage Device Vertical Tiering patterns can be applied to establish a cloud architecture that supports a set of cloud storage devices, each with different tiers that cloud consumers can choose to scale to The Synchronized Operating State pattern can be applied in combination with the Hypervisor Clustering pattern to avoid further virtual server and ready-made environment connectivity problems. The Redundant Storage pattern can be applied so that if a clou
C. The Service State Management pattern can be applied to establish a system that can persist session data in a database. The Persistent Virtual Network Configuration pattern can be applied to centralize the configuration data necessary for virtual servers to remain accessible after they have been relocated to different hypervisors. The Storage Maintenance Window pattern can be applied to establish a system that allows cloud storage devices to be maintained without causing outages.
D. None of the above.
Join a community of subject matter experts. Register for FREE to view solutions, replies, and use search function. Request answer by replying!