What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
An infrastructure for cloud computing on big data. Tashi has been incubating since 2008-09-04. Shepherd notes: rvs: Tashi looks completely dormant at this point. Despite my repeated on-list and off-list emails it appears that I couldn't find anybody to compile a report. The only discussion that resulted from my attempts is captured over here: http://markmail.org/thread/mveeuubf2fcdmgcw Personally I think we need to figure out a path to *some* kind of a resolution here. I don't think Tashi benefits from being an incubator project and we need to figure out how to get it to a different trajectory.
An infrastructure for cloud computing on big data. Tashi has been incubating since 2008-09-04. Three most important issues to address in the move towards graduation: 1. 2. 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? How has the project developed since the last report? Date of last release: Signed-off-by: [ ](tashi) Matthieu Riou [ ](tashi) Craig Russell Shepherd notes:
An infrastructure for cloud computing on big data. Tashi has been incubating since 2008-09-04. Three most important issues to address in the move towards graduation: 1. 2. 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? How has the project developed since the last report? Please check this [ ] when you have filled in the report for Tashi. Signed-off-by: Matthieu Riou: [ ](tashi) Craig Russell: [ ](tashi) Shepherd notes:
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 from October to December:
In the period from October to December, 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.
This period was dedicated to testing and performance testing of the system.
Minor updates to the code include adding support for sub-domains
within Tashi. Also some bug fixes to the recently imported code from
a collaborator. Next efforts will be to more tightly integrate the
physical and virtual aspects of the system as well as create a front
end UI.
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.
(no signoffs)
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: 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, allowing addition of users and networks, and host reservations and availability for scheduling. The project has received code contributions from one non-committer in this period. Diogo Gomes provided support for deriving the IP addresses of guests automatically, without having to scan the subnet. Thanks Diogo! Additional stability and user experience improvements were also committed. 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. Signed-off-by: mfranklin
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. In the period from April to July, 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 this period. Development efforts this period have included making user actions display assurance messages via the client in case of successful operations, extending the SQL database backend to support all Instance and Host fields that are already recorded via the alternative "pickled" backend. The primitive scheduler gained additional resilience to refrain from scheduling load on hosts that are down transiently. The node manager service now tries to ensure that undelivered messages to the cluster manager are resubmitted regularly. Virtual machine migration was revised to ensure stale state wasn't being shadowed by new data, only to reappear when the migrated VM was shut down. The code underwent a complete automatic analysis, fixing several issues. Furthermore, a few other minor additions, fixes and documentation updates were made. The project has received code contributions from two non-committers in this period. MIMOS via Luke Jing Yuan have contributed "convertz" to the code base, a utility to convert a VM image to an image deployable to a physical machine provisioned by Zoni. Alexey Tumanov of CMU provided a communications timeout wrapper to handle the problem of threads hanging forever, trying to communicate over a broken network connection. Upcoming software goals are to separate the client into an administrative and a user interface, 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. Signed off by mentor: Shepherd: Jukka Zitting
Tashi has been incubating since September 2008. The Tashi project aims to build a software infrastructure for cloud computing on massive internet-scale data sets (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. In the period from January to April, the project had received permission to publish a release. Shortly thereafter, a further release was approved, incorporating several bug fixes detected during deployment of the first release and from Jira reports. In the process of making our first release, contact to two of our three mentors was re-established. The third mentor has not been heard from (also in other parts of Apache) for quite a while. We obtained sufficient administrative access to Jira to manage our problem reports. Development efforts this period have mainly been in adding resilience to Tashi components, as well as returning more helpful messages in case of errors. Some parts of the code base that were relevant only to Thrift have been removed. Upcoming software goals are to investigate what is needed to support IPv6, considering replacement for RPyC and providing the ability to hand out server slices (operating system level virtualization). 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 will apply some of the advice posted to general@apache.incubator.org, as well as create web pages demonstrating the project's utility, provide sample VM images and disseminate other information relating to the deployments close to him. He will also urge others to make similar information publicly available. One of our users has requested the creation of a private branch for his team to work on. Perhaps this will result in a valuable feature addition to the project. Items to be resolved before graduation: - Generate more publicity for the project. - Develop members of the user community to submit feature extensions. Signed off by mentor:
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.
Development activities have included:-
* Accounting server has been added to the codebase
* Primitive scheduler changes
* bug fixes
* Add support for user choice of dense packing or not
* Guard against starting more than one VM with
persistent disk
* Client changes
* Check syntax of user commands
* Add support for querying available images
* Add support for querying image size
* Add support for copying of images
* QEMU VMM changes
* bug fixes
* Reserve some memory for the host itself
* Make scratch location configurable
* Live migrations take a long time, eliminate
some timeout values
* Cluster manager changes
* bug fixes
* Reduce network traffic
* Move accounting functions to new accounting server
* Branched off new stable version and release candidate
* Audit compliance with Incubator policies
The project is still working toward building a larger user and development
community. User groups have been identified in Ireland, Slovenia and Korea,
Malaysia, as well as the United States.
Items to be resolved before graduation:
* A stable branch exists which could be a release candidate, but
the codebase is large and test hardware is currently in
short supply. We are confident that the code in the stablefix
branch will work if running QEMU emulation, Pickle or sqlite
data storage, primitive scheduler. Xen, other data stores and
schedulers have not been tested recently.
* Develop community diversity (Committers currently at Telefonica,
Google and CMU)
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 has previously encompassed just the tools to manage virtual
machines using Xen and KVM, but is gaining the facility to hand out
physical machines as well.
Development activities have included:-
* Zoni has been merged into the mainline code trunk
* Additional capability added to Zoni
* Implement hint to influence scheduler packing policy
* Reject incorrect arguments to tashi-client to prevent
unintended defaults from being used
* Migrated to rpyc version 3.1
* Add "free capacity" info function to Tashi
* Support for auto creation of zoni tftp boot menus
* Fixed deadlocks in clustermanager
* Rewrite CM to concentrate decay handlers into one spot
* Use Linux LVM for local scratch space creation
* VMM is now authoritative to what is running
* Retry deploying held VMs at a later time
The project is still working toward building a larger user and development
community. User groups have been identified in Ireland, Slovenia and Korea,
Malaysia, as well as at Georgia Tech.
Items to be resolved before graduation:
* A stable branch exists which could be a release candidate, but
the codebase is large and test hardware is currently in
short supply. We are confident that the code in the stablefix
branch will work if running QEMU emulation, Pickle or sqlite
data storage, primitive scheduler. Xen, other data stores and
schedulers have not been tested recently.
* Should have example accounting code (data is kept, but
interpretation is currently manual)
* Develop community diversity (Committers currently at Telefonica,
Google and CMU)
2011-July 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 has previously encompassed just the tools to manage virtual
machines using Xen and KVM, but is gaining the facility to hand out
physical machines as well.
Development activities have included:-
* Refactor primitive scheduler to be less convoluted
* Ensure that an old CM handle expires to not talk to a dead CM
* Use virtio networking by default for performance
* Enable config option for Miha Stopar's auto host registration
* Clean unused and untested modules from stable branch
* Reduce VM startup time when using scratch (old sparse files)
* Conversion of sparse file scratch space to Linux LVM2
* Work on migrating VMs between hosts
* Resource usage messages sent to clustermanager for accounting
The project is still working toward building a larger user and development
community. User groups have been identified in Ireland, Slovenia and Korea,
as well as at Georgia Tech. CMU usage is growing as other groups hear about
the availability of the resource. Intel has restructured its research
division and folded some operations into adjoining academic sites.
Items to be resolved before graduation:
* A stable branch exists which could be a release candidate, but
the codebase is large and test hardware is currently in
short supply. We are confident that the code in the stablefix
branch will work if running QEMU emulation, Pickle or sqlite
data storage, primitive scheduler. Xen, other data stores and
schedulers have not been tested recently.
* Should have example accounting code
* Develop community diversity (Committers currently at Telefonica,
Google and CMU)
2011-April 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 has previously encompassed just the tools to manage virtual
machines using Xen and KVM, but is gaining the facility to hand out
physical machines as well.
Development activities have included:-
* Importing bug fixes from CMU deployment
* Don't display exceptions if failure is expected
* Validate fields and clean invalid instance entries
* Eliminating inconsistent state between node and cluster manager
* Allow hosts to be soft powered off via ACPI
* Refactor primitive scheduler to be less convoluted (ongoing)
* Define a stable branch for tested code
* Example support for dynamic scratch space disks
* Enforce designated copy-on-write data filesystem for Qemu
The project is still working toward building a larger user and development
community. User groups have been identified in Ireland, Slovenia and Korea,
as well as at Georgia Tech. CMU usage is growing as other groups hear about
the availability of the resource. Intel has restructured its research
division and folded some operations into adjoining academic sites.
Items to be resolved before graduation:
* A stable branch exists which could be a release candidate, but
the codebase is large and test hardware is currently in
short supply. We are confident that the code in the stablefix
branch will work if running QEMU emulation, Pickle or sqlite
data storage, primitive scheduler. Xen, other data stores and
schedulers have not been tested recently.
* Scratch space integration would be desirable, accounting
integration is probably a necessity
* Develop community diversity (Committers currently at Telefonica,
Google and CMU)
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 has previously encompassed just the tools to manage virtual machines
using Xen and KVM, but is gaining the facility to hand out physical machines
as well.
Development activities have included:-
* fix for xen root declaration (necessary if using external kernel)
* parameterize xen root disk declaration
* implement Miha Stopar's fix to improve handoff during migration
* implement Miha Stopar and Andrew Edmond's patch to register and
unregister hosts, and improve locking of resources
* allow use of virtio disks under qemu
Richard Gass has created a branch to work on the physical machine
reservation
component (zoni-dev):-
* allow physical machine registration
* add integration with Apache web server for control
* add facilities for DNS/DHCP registration of physical resources
* make changes to Zoni DB layout (convert some tables to InnoDB)
* add initial infrastructure hardware (switch and PDU)
* demonstrate initial VM usage reports (shame-tashi)
* add logging to infrastructure hardware controllers
* add abstraction layer for hardware controllers
* add debug console to zoni
* add DNS/DHCP key creation functions
* add physical to virtual cluster manager service
* add primitive agent to keep minimal amount of machines powered
on and scale up from there
* allow zoni-cli to talk to hardware directly
The project is still working toward building a larger user and development
community. User groups have been identified in Ireland, Slovenia and Korea,
as well as at Georgia Tech. Several suggestions provided by users at those
sites have been implemented in the head.
Items to be resolved before graduation:
* Prepare and review a release candidate
* Develop community diversity (currently Intel and CMU committers)