[haizea-commit] r578 - trunk/html
haizea-commit at mailman.cs.uchicago.edu
haizea-commit at mailman.cs.uchicago.edu
Mon Feb 16 10:58:59 CST 2009
Author: borja
Date: 2009-02-16 10:58:51 -0600 (Mon, 16 Feb 2009)
New Revision: 578
Removed:
trunk/html/doc_roadmap.html
trunk/html/features.html
trunk/html/features_leases.html
trunk/html/haizea_arch_simplified.png
trunk/html/quickstart_leasegraph2.png
trunk/html/quickstart_leasegraph3.png
trunk/html/quickstart_leasegraph4.png
Modified:
trunk/html/download.html
trunk/html/index.html
Log:
Website updates for TP1.3
Deleted: trunk/html/doc_roadmap.html
===================================================================
--- trunk/html/doc_roadmap.html 2009-02-16 01:44:28 UTC (rev 577)
+++ trunk/html/doc_roadmap.html 2009-02-16 16:58:51 UTC (rev 578)
@@ -1,85 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-
-<head>
-
-<title>Haizea - An Open Source VM-based Lease Manager</title>
-<link href="haizea.css" type="text/css" rel="stylesheet"/>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-</head>
-<body>
-
-<div id="content">
-<div id="logo">
-<a href="index.html"><img src="logo.png" width="450" height="86" border="0" alt="Haizea"/></a>
-</div>
-<div class="topbar">
-<a href="whatis.html">What is Haizea?</a> |
-<a href="features.html">Features</a> |
-<a href="download.html">Download</a> |
-<a href="documentation.html" style="color:black">Documentation</a> |
-<a href="support.html">Support</a> |
-<a href="pubs.html">Publications</a> |
-<a href="credits.html">Credits</a></div>
-<h1>Roadmap</h1>
-
-<p>The next version of Haizea will be TP1.2, due in early August 2008. This version will include the following improvements:</p>
-
-<ul>
-<li>RPC interface so enactment backend can send asynchronous events to Haizea</li>
-<li>Command Line Interface (CLI) to Haizea</li>
-<li>More documentation on how to produce pretty graphs from Haizea simulations</li>
-</ul>
-
-<p>There are several improvements that are planned for upcoming versions (coming out in summer and fall of 2008, exact dates to be determined):</p>
-<ul>
-<li>Support for more types of leases</li>
-<li>Basic server consolidation algorithms</li>
-<li>Decoupling policy decisions from Haizea</li>
-<li>Lease negotiation</li>
-</ul>
-
-<h2>Wish list</h2>
-<ul>
-<li>The slot table data structure is the only part of Haizea that I wish were not implemented in Python. This part of the scheduler becomes a performance bottleneck in the simulations (it's not a problem if you're running Haizea "in real time"). A C/C++ implementation could speed up simulations, and would allow us to more efficiently query the slot table.</li>
-<li>The code to parse the config file is getting unwieldy and should be replaced by something that makes it easier to add new options and document those options.</li>
-<li>Haizea currently saves all the data it collects (accepted/rejected requests, lease statistics, etc.) to a file when Haizea stops running. This is ok for simulations, but not particularly useful when Haizea is running as a daemon. The accounting code has to be rethinked so it can also periodically save information to disk (e.g., with rrdtool)</li>
-<li>Decoupling the notion of "deployment overhead" with "transferring a VM image". Although transferring a VM image is a common way of "setting up" a VM, there are other ways of deploying a VM (such as having a base image installed on all physical nodes and installing packages on them). Ideally, the scheduler should be able to interface with a "deployment overhead" module that will be the "expert" in deployment (however, the scheduler is still in charge of scheduling the overhead, but it consults with the overhead module to determine when the overhead can be scheduled, what nodes are preferable if we want to minimize overhead, etc.). This has been partially done starting with TP 1.1.</li>
-<li>The source code is still in need of some general clean-up and documentation. This is slowly getting done.</li>
-</ul>
-
-<table border="0" align="center">
-<tr>
-<td>
-<div class="back">
-<a href="documentation.html">
-<img src="logo_small.png" width="32" height="35" border="0" alt="haizea"/><br/>
-BACK TO<br/>DOCUMENTATION
-</a>
-</div>
-</td>
-<td> </td>
-<td>
-<div class="back">
-<a href="index.html">
-<img src="logo_small.png" width="32" height="35" border="0" alt="haizea"/><br/>
-BACK TO<br/>HOME PAGE
-</a>
-</div>
-</td>
-</tr>
-</table>
-
-</div>
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4920033-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-</body>
-</html>
Modified: trunk/html/download.html
===================================================================
--- trunk/html/download.html 2009-02-16 01:44:28 UTC (rev 577)
+++ trunk/html/download.html 2009-02-16 16:58:51 UTC (rev 578)
@@ -37,7 +37,7 @@
<h2>Haizea</h2>
-<p>The current version of Haizea is Technology Preview 1.2, released on September 29th, 2008. To install, download <a href="downloads/haizea-TP1.2.tar.gz" onClick="javascript: pageTracker._trackPageview('/downloads/haizea-TP1.2.tar.gz');">haizea-TP1.2.tar.gz</a> and follow the <a href="documentation.html">installation instructions</a>. Haizea is published under the <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License 2.0</a>, a BSD-like <a href="http://www.opensource.org/">OSI</a>-compatible license.</p>
+<p>The current version of Haizea is Technology Preview 1.3, released on February 16th, 2009. To install, download <a href="downloads/haizea-TP1.3.tar.gz" onClick="javascript: pageTracker._trackPageview('/downloads/haizea-TP1.3.tar.gz');">haizea-TP1.3.tar.gz</a> and follow the <a href="documentation.html">installation instructions</a>. Haizea is published under the <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License 2.0</a>, a BSD-like <a href="http://www.opensource.org/">OSI</a>-compatible license.</p>
<h2>SVN repository</h2>
Deleted: trunk/html/features.html
===================================================================
--- trunk/html/features.html 2009-02-16 01:44:28 UTC (rev 577)
+++ trunk/html/features.html 2009-02-16 16:58:51 UTC (rev 578)
@@ -1,48 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-
-<head>
-
-<title>Haizea - An Open Source VM-based Lease Manager</title>
-<link href="haizea.css" type="text/css" rel="stylesheet"/>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-</head>
-<body>
-
-<div id="content">
-<div id="logo">
-<a href="index.html"><img src="logo.png" width="450" height="86" border="0" alt="Haizea"/></a>
-</div>
-<div class="topbar">
-<a href="whatis.html">What is Haizea?</a> |
-<a href="features.html" style="color:black">Features</a> |
-<a href="download.html">Download</a> |
-<a href="documentation.html">Documentation</a> |
-<a href="support.html">Support</a> |
-<a href="pubs.html">Publications</a> |
-<a href="credits.html">Credits</a></div>
-<h1>Features</h1>
-
-
-
-
-
-<div class="back">
-<a href="index.html">
-<img src="logo_small.png" width="32" height="35" border="0" alt="haizea"/><br/>
-BACK TO<br/>HOME PAGE
-</a>
-</div>
-</div>
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4920033-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-</body>
-</html>
Deleted: trunk/html/features_leases.html
===================================================================
--- trunk/html/features_leases.html 2009-02-16 01:44:28 UTC (rev 577)
+++ trunk/html/features_leases.html 2009-02-16 16:58:51 UTC (rev 578)
@@ -1,118 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-
-<head>
-
-<title>Haizea - An Open Source VM-based Lease Manager</title>
-<link href="haizea.css" type="text/css" rel="stylesheet"/>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-</head>
-<body>
-
-<div id="content">
-<div id="logo">
-<a href="index.html"><img src="logo.png" width="450" height="86" border="0" alt="Haizea"/></a>
-</div>
-<div class="topbar">
-<a href="whatis.html">What is Haizea?</a> |
-<strong>Features</strong> |
-<a href="download.html">Download</a> |
-<a href="documentation.html">Documentation</a> |
-<a href="support.html">Support</a> |
-<a href="pubs.html">Publications</a> |
-<a href="credits.html">Credits</a></div>
-<h1>Supported types of leases</h1>
-
-<p>Haizea supports a variety of resource leases. There's a more detailed description of what a lease is in the <a href="whatis.html">What is Haizea?</a> page, and this page just describes the supported types of leases. Throughout this page, let's assume you have a 4-node cluster, and that you want to lease parts of that cluster over time. We'll represent the four nodes over time like this: </p>
-
-<div class="center">
-<img src="quickstart_leasegraph1.png" width="413" height="153" />
-</div>
-
-
-<h2>"Advance Reservation" lease</h2>
-
-<p>An advance reservation, or AR, lease is a lease that must begin and end at very specific times. For example, the following lease starts at 1pm and ends at 2pm:</p>
-
-<div class="center">
-<img src="lease_ar.png" width="402" height="144" />
-</div>
-
-<p>Haizea can schedule this type of lease, which is particularly useful when you need resources at a specific time (for example, to coincide with a lecture, an experiment, etc.)</p>
-
-<h2>Preemptible best-effort lease</h2>
-
-<p>Sometimes, you know you need resources, but you don't need them at a specific time. In fact, you're perfectly content to wait until there are enough resources available for your lease:</p>
-
-<div class="center">
-<img src="lease_be1.png" width="402" height="162" />
-</div>
-
-<p>When you request a best-effort lease, your request gets placed in a queue, which is processed in a first-come-first-serve basis (the queue uses backfilling algorithms to improve resource management). The downside of this type of lease, of course, is that you may have to wait a while until resources are allocated to your lease:</p>
-
-<div class="center">
-<img src="lease_be2.png" width="402" height="162" />
-</div>
-
-<p>Furthermore, your lease may be running a program unattended which can be safely paused for a while (since no one is interactively using the lease resources). By requesting a <em>preemptible</em> lease, you allow your resources to be preempted by higher-priority leases, like advance reservations:</p>
-<div class="center">
-<img src="lease_be3.png" width="402" height="102" />
-</div>
-
-<p>Preemptible best-effort leases are good for running batch jobs, or any non-interactive work. The Haizea paper <a href="pubs.html">Combining Batch Execution and Leasing Using Virtual Machines</a> showed how using the suspend/resume capability of virtual machines allowed AR and best-effort leases to be scheduled together efficiently, overcoming the utilization problems typically associated with ARs.</p>
-
-<h2>Non-preemptible best-effort lease</h2>
-<p>But what if you're willing to wait for your resources to become available, but don't want them to be preempted? (e.g., if you want to use them interactively). Well, it's as simple as requesting a <em>non-preemptible</em> best-effort lease. Once your request makes it through the queue, and your lease is allocated resources, no one is taking them away. </p>
-
-
-<h2>Immediate lease</h2>
-
-<p>In some cases, you may need resources now. As in <em>right now</em>:</p>
-
-<div class="center">
-<img src="lease_im.png" width="402" height="143" />
-</div>
-<p>Furthermore, if you can't get them right now, you're just not interested in anything else the resource provider has to offer. You're not going to request resources in the future, and you're certainly not going to be put on a queue. This is essentially the type of lease that many cloud systems offer (although the definition of "right now" varies wildly). Take into account that an immediate lease may still take a while to setup (VM image deployment, etc.). This type of lease in Haizea may evolve in the future into an "urgent lease", where "right now" really does mean "right now". </p>
-
-<h2>Coming soon</h2>
-
-<p>The following types of leases are coming soon to a lease manager near you:</p>
-
-<h3>Best-effort with deadlines</h3>
-
-<p>In some cases, when you say "best effort", you really mean "best effort, but be reasonable". Sure, you're willing to wait for your resources, but you may need them before a deadline.</p>
-
-<div class="center">
-<img src="lease_deadline.png" width="438" height="232" />
-</div>
-
-<p>For example, let's say you want a 16-node cluster sometime today to run a test program. You're not particularly picky about when you get the cluster, as long as it happens today and you're given sufficient warning of when your lease will be available. In the future, you will be able to tell Haizea that you have a deadline, and Haizea will either get the resources to you by then, or tell you that the deadline is simply unfeasible.</p>
-
-<h3>Negotiated leases</h3>
-
-<p>If you've ever entered into any sort of non-computational lease agreement, you know that agreeing on the lease terms rarely involves the lessor instantly being on the same page as you. Rather, it involves a fair amount of haggling. Besides, if your computational needs are flexible, so should your lease manager (c'mon, are you sure you mean "exactly at 2pm"? maybe you meant to say "at some point this afternoon"?). In the future, you will be able to negotiate your leases with Haizea:</p>
-
-<div class="center">
-<img src="lease_negotiate.png" width="433" height="143" />
-</div>
-
-<p>So, hey, maybe we can't get you that shiny AR you want at 2pm, but how about I get you twice the resources at an off-peak time? I'll even throw in a discount. And free air conditioning.</p>
-<div class="back">
-<a href="index.html">
-<img src="logo_small.png" width="32" height="35" border="0" alt="haizea"/><br/>
-BACK TO<br/>HOME PAGE
-</a>
-</div>
-</div>
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4920033-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-</body>
-</html>
Deleted: trunk/html/haizea_arch_simplified.png
===================================================================
(Binary files differ)
Modified: trunk/html/index.html
===================================================================
--- trunk/html/index.html 2009-02-16 01:44:28 UTC (rev 577)
+++ trunk/html/index.html 2009-02-16 16:58:51 UTC (rev 578)
@@ -24,7 +24,7 @@
<a href="support.html">Support</a> |
<a href="credits.html">Credits</a></div>
<div class="warning">
-<strong>Technology Preview 1.2 has been released</strong> (2008-09-29)<br/> with a <a href="documentation.html">new Haizea manual</a>, command-line and RPC interfaces, support for managing groups of VMs with OpenNebula, <a href="http://phoenixforge.cs.uchicago.edu/haizea">project management at PhoenixForge</a>, and lots of other changes. See the <a href="https://phoenixforge.cs.uchicago.edu/haizea/wiki/Changelog">changelog</a> for more details, or <a href="download.html">download</a> it now.
+<strong>Technology Preview 1.3 has been released</strong> (2009-02-16)<br/> with support for <a href="http://www.opennebula.org/">OpenNebula 1.2</a> and many internal changes that make Haizea more stable. See the <a href="https://phoenixforge.cs.uchicago.edu/haizea/wiki/Changelog">changelog</a> for more details, or <a href="download.html">download</a> it now.
</div>
<p>Haizea is an open-source virtual machine-based lease management architecture (if that sounds like a mouthful, take a look at our <a href="whatis.html">What is Haizea?</a> page). In a nutshell, Haizea is a piece of software that, in combination with the <a href="http://www.opennebula.org/">OpenNebula virtual infrastructure manager</a>, can be used to manage a <a href="http://www.xen.org/">Xen</a> or <a href="http://kvm.qumranet.com/">KVM</a> cluster, allowing you to deploy different types of leases that are instantiated as virtual machines (VMs). Haizea can also be run in simulation, providing a platform for experimenting with scheduling algorithms that depend on VM deployment or on the leasing abstraction.</p>
Deleted: trunk/html/quickstart_leasegraph2.png
===================================================================
(Binary files differ)
Deleted: trunk/html/quickstart_leasegraph3.png
===================================================================
(Binary files differ)
Deleted: trunk/html/quickstart_leasegraph4.png
===================================================================
(Binary files differ)
More information about the Haizea-commit
mailing list