introduction to cloudsim
- 2. a type of parallel and distributed system consisting of a collection of inter-connected and virtualized computers that are dynamically provisioned, and presented as one or more unified computing resources based on service-level agreements established through negotiation between the service provider and consumers
- 3. delivers infrastructure(Amazon EC2 , Microsoft Azure, Google App Engine), platform, and software that are made available as subscription-based services in a pay-as-you-go model to consumers. Cloud-based application services include social networking,web hosting, content delivery, and real-time instrumented data processing
- 4. Application types has different composition, configuration, and deployment requirements. Quantifying the performance of provisioning (scheduling and allocation) policies in a real Cloud computing environment for different application models under transient conditions is extremely challenging
- 5. platform for dynamic and flexible application provisioning. expose data center’s capabilities as a network of virtual services (e.g. hardware, database, user-interface, and application logic). Help companies to focus on business values. Exhibit varying demands, supply patterns, system sizes, and resources (hardware, software, network).
- 6. A new , generalized ,and extensible simulation framework that allow seamless modeling , simulation , and experimentation of cloud computing infrastructure and application services. open up the possibility of evaluating the hypothesis (application benchmarking study) in a controlled environment where one can easily reproduce result
- 7. benefits to IT companies (or anyone who wants to offer his application services through clouds) by allowing them to: (i) test their services in repeatable and controllable environment; (ii) tune the system bottlenecks before deploying on real clouds; and (iii) experiment with different workload mix.
- 8. (i) time effectiveness: it requires very less effort and time to implement Cloud-based application provisioning test environment and (ii) flexibility and applicability: developers can model and test the performance of their application services in heterogeneous Cloud environments (Amazon EC2,Microsoft Azure) with little programming and deployment effort.
- 9. (i) support for modeling and simulation of large scale Cloud computing environments, including data centers, on a single physical computing node; (ii) a self-contained platform for modeling Clouds, service brokers, provisioning, and allocation policies; (iii) support for simulation of network connections among the simulated system elements ;
- 10. (iv) facility for simulation of federated Cloud environment that inter-networks resources from both private and public domains. (v)availability of a virtualization engine that aids in the creation and management of multiple, independent, and co-hosted virtualized services on a data center node ,and (vi) flexibility to switch between space-shared and time-shared allocation of processing cores to virtualized services.
- 11. User level : includes applications that are directly available to end-users. Example : Social computing, Enterprise, ISV, Scientific, CDNs, etc. User-Level middleware(Saas):includes the software frameworks, such as Web 2.0 Interfaces (Ajax, IBM Workplace), that help developers in creating rich, cost-effective user-interfaces and Mashups , Concurrent and Distributed Programming, Workflows, Libraries, Scripting , etc.
- 12. Core middleware(Paas):implements the platform-level services that provide run-time environment for hosting and managing User- Level application services. include Dynamic SLA Management, Accounting, Billing, Execution monitoring and management , and Pricing. System Level(Iaas):exist massive physical resources (storage servers and application servers) that power the data centers.
- 13. User Code :exposes basic entities for hosts (no. of machines) and their specification, applications (no. of tasks & their requirements), VMs, number of users and their application types, and scheduling policies. CloudSim simulation layer : modeling and simulation of virtualized Cloud-based data center environments including dedicated management interfaces for VMs, memory, storage, and bandwidth. issues, such as provisioning of hosts to VMs, managing application execution, and monitoring dynamic system state, are handled by this layer. CloudSim core simulation engine.
- 15. Related classes are: CloudSim: This is the main class, which is responsible for managing event queues and controlling step-by-step (sequential) execution of simulation events. FutureQueue: This class implements the future event queue accessed by CloudSim. DeferredQueue: This class implements the deferred event queue used by CloudSim.
- 16. CloudInformationService: A CIS is an entity that provides resource registration, indexing, and discovering capabilities . It supports two basic primitives: (i) publish(): which allows entities to register themselves with CIS and (ii) search():which allows entities such as Cloud Coordinator and Brokers in discovering status and endpoint contact address of other entities. SimEntity: This is an abstract class, which represents a simulation entity that is able to send messages to other entities and process received messages as well as fire and handle events
- 17. CloudSimTags. This class contains various static event/command tags that indicate the type of action that needs to be undertaken by CloudSim entities when they receive or send events. CloudSimShutdown: This is an entity that waits for the termination of all end-user and broker entities, and then signals the end of simulation to CIS. Predicate: Predicates are used for selecting events from the deferred queue. PredicateAny: This class represents predicate that matches any event on the deferred event queue.
- 18. PredicateFrom: This class represents a predicate that selects events fired by specific entities. PredicateNone: This represents a predicate that does not match any event on the deferred event queue. PredicateNotFrom: This class represents a predicate that selects events that have not been sent by specific entities. PredicateNotType: This class represents a predicate to select events that do not match specific tags. PredicateType: This class represents a predicate to select events with specific tags.
- 19. THANKS