Difference: CloudSchedulerRequirements (2 vs. 3)

Revision 32009-06-02 - dpb

Line: 1 to 1
 
META TOPICPARENT name="VirtualizationProjectHome"

Cloud Scheduler Requirements

Line: 31 to 31
 
    • Specifically, the cloud scheduler will determine how many of what type of VMs should be running at what location in the cloud.
    • The cloud scheduler will send instructions to clusters on the cloud in order to create and destroy VMs (and possibly pause VMs or move VMs to different cluster locations) in order to change the cloud environment.

Added:
>
>

Design Requirements

(Describe what standards the intended system should meet. How, and in accordance with what standards or guidelines, will the scheduler be built?)

  • [Potential]: The scheduler will be built into a VM running in the cloud.
  • [Potential]: The initial scheduler prototype will be built in Python, Perl, or another suitable "simple but powerful" language.
 

Client Requirements

(Any suggested requirements from clients of the intended system. These may fit into other categories as well.)
Deleted:
<
<


The following requirement categories are more formal, and will only be filled in as necessary.
 

Performance Requirements

(Describe the performance constraints on the intended system. How fast / with how many resources should the scheduler function?)
Changed:
<
<

Design Requirements

(Describe what standards the intended system should meet. How, and in accordance with what standards or guidelines, will the scheduler be built?)
>
>
 
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback