Hi Michael,
I'd summarize the dev activities instead of listing all the changes.
Maybe two lines instead of 45.
Other than that, I'd approve. Feel free to paste it into the incubator
wiki report.
Regards,
Craig
On Oct 9, 2012, at 1:06 PM, [email protected] wrote:
Author: stroucki
Date: Tue Oct 9 20:06:40 2012
New Revision: 1396273
URL: http://svn.apache.org/viewvc?rev=1396273&view=rev
Log:
Start board report for 2012-10
Added:
incubator/tashi/board/2012-10.txt
Added: incubator/tashi/board/2012-10.txt
URL:
http://svn.apache.org/viewvc/incubator/tashi/board/2012-10.txt?rev=1396273&view=auto
=
=
=
=
=
=
=
=
======================================================================
--- incubator/tashi/board/2012-10.txt (added)
+++ incubator/tashi/board/2012-10.txt Tue Oct 9 20:06:40 2012
@@ -0,0 +1,72 @@
+2012-October Tashi Incubator Status Report
+
+Tashi has been incubating since September 2008.
+
+The Tashi project aims to build a software infrastructure for cloud
+computing on massive internet-scale datasets (what we call Big Data).
+The idea is to build a cluster management system that enables the Big
+Data that are stored in a cluster/data center to be accessed, shared,
+manipulated, and computed on by remote users in a convenient,
efficient,
+and safe manner.
+
+Tashi originally encompassed just the tools to manage virtual
machines
+using Xen and QEMU, but has been merged with Zoni, which manages the
+physical aspects of a cluster like power control, network settings
and
+handing out physical machines.
+
+Activities July-October:
+tashi-client: leave ValueErrors which came from incorrect
operations, while converting ones originating from a failure to
perform a proper operation to TashiError
+tashi-client: Don't tell the user about an "exception"; offer help
if a ValueError occurred.
+improve error reporting to the user
+tashi-client: check for permissions when doing destroyMany or
shutdownMany
+qemu: Address race condition on instantiation, where the cleanup
+thread would remove a VM being born. Allow 5 seconds for the launch
of
+the kvm process.
+improve messages given to the user
+Do the trivial addition of setHostNotes for now. "Real Soon Now",
this type of function will be put into an administration tool.
+import Diego Gomes' improvements to detecting guest IP addresses,
and adjust documentation. Thanks Diego!
+replace deprecated with current functions
+now have a dedicated cluster administration client command,
supporting host state and comment changes, user management and
network management. There were removed from the regular tashi client
+qemu.py: Raise EOFError rather than RuntimeError when reading off
the monitor FD
+qemu.py: Handle EOFError in processVmStats to avoid a stack dump
when a VM is exiting
+qemu: replace the fork and shell and head call to get system memory
with a python only solution
+qemu: make logging the same as in other modules
+allow automatic host registration with configuration option
+tashi-client: reraise network exceptions so we can handle them
+database: make sure for new hosts, host structure is fully
initialized
+qemu: make note on hostIds, and the need make sure they match ours
in case we accept a migrated instance
+qemu: set state to running to avoid persistent states of
MigrateTrans from the origin host when the NM restarts
+qemu: we ask for our hostname a lot, lets just do it once
+qemu: force started instances to have my hostId
+nodemanagerservice: correct hostId's when we get info for the CM
+tashi-admin: allow hosts to be reserved for a user
+
+
+In the period from July to October, the project did not ask to make
+another incubating release, but is ready to start the process for a
new
+release incorporating the development efforts of the last 6 months.
+
+Development efforts this period have included providing a separate
+administration client, ...
+
+The project has received code contributions from one non-committer in
+this period. Diego Gomes...
+
+
+Upcoming software goals are
+to investigate what is needed to
+support IPv6, replace RPyC, and to provide the ability to hand out
+server slices (operating system level virtualization). Besides CPU
and
+memory, disk storage should also be a schedulable resource.
+
+The project has a user community, but it is small. Growth mostly has
+happened by word of mouth. To show potential users at large the
utility
+of this project, the author of this report is creating web pages to
+demonstrate how to accomplish distributed computing tasks. Base
images
+of (free) OS installs will be provided to allow new users to get
started
+quickly. Hopefully this will increase visibility of the project.
+
+Items to be resolved before graduation:
+ * Generate more publicity for the project.
+ * Develop members of the user community to submit feature
+ extensions.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
