Revision as of 10:31, 2 February 2011 (view source) Tvainio (Talk | contribs) (→Application Framework) ← Older edit		Revision as of 10:32, 2 February 2011 (view source) Tvainio (Talk | contribs) (→Common) Newer edit →
Line 51:		Line 51:
	| Data Transfer Objects		| Data Transfer Objects
	| Taxonomy thereof. Pythonic APIs		| Taxonomy thereof. Pythonic APIs
-	| Completed (Awaiting review)	+	| Done
	|-		|-
	| TestDefinition		| TestDefinition

---

Revision as of 10:32, 2 February 2011

Contents 1 Release 0.8 unstable 1.1 Application Framework 1.2 Common 1.3 Server 1.4 Worker 1.5 Plugins 1.6 Usability Issues 1.7 Other Problems 2 Scheduled for 0.9 Release 2.1 Organisation, maintenance and upgrades 2.2 Conductor 2.3 Server 3 Not scheduled items 3.1 Security

Release 0.8 unstable

Application Framework

Feature	Description	Status
Configuration	Single configuration file and format,	Done
Plugins	Runtime discoverable mechanism, with clear usage model	Done
Exceptions	An understandable exception handling model. Documented	OTS 0.9
Logging	A coherent distributed logging system	Done
Upgrade Capability	Worker version management	OTS 0.9
Function call	Conductor should be function call not a process	OTS 0.9
Properties	Merge from 0.1 branch	Done
Exceptions, regression	Check that all relevant exceptions from 0.1 are in place	Done

Common

Feature	Description	Status
Data Transfer Objects	Taxonomy thereof. Pythonic APIs	Done
TestDefinition	Removed

Server

Feature	Description	Status
High Level API	Client facing interface	Awaiting review
Hub	High level procedural code	In Progress
Disambiguation Datamodel	Clear persistence and data management	In Progress (Persistence parameters separated out)
Distributor	Opaque Data Transfer	Completed
Default Options	Mapping of Default Options to SW product	BROKEN. Default device options are not handled correctly. see options_factory unit tests
XMLRPC	Add XMLRPC interface	Completed
Allocator	API for custom Task allocation	Awaiting review
Publisher Plugins	API and demos for 3rd party Publisher Plugins	Completed
Input Plugin	Incorporate and mark as deprecated	Not started It should be possible to implement this as a publisher. Reporting tools can handle getting target package information.
Allocator Entry Point	Add appropriate extension point to allocator to allow custom distribution	Awaiting merge
Parallel Testruns	Trigger the same testrun on multiple targets	In Progress

Worker

Feature	Description	Status
Integrate Conductor		Full tool chain running

Plugins

Feature	Description	Status
BIFH Plugin	Client facing interface	In Progress (Spike completed awaiting review)
Reporting Plugin	Clear separation between test tool and reporting	In Progress (First pass API. Stubbed demo)
Email Plugin	Email Plugin for Publisher API	Requires system tests
QA Reports Plugin	Publisher plugin for Meego QA Reports tool	done

Usability Issues

Feature	Description	Status
Unittests run as sudo	Queue size API calls	Fixed
Developer Installation out-of-the-box	Make as easy as possible. Clear instructions.	Awaiting review
API Documentation	All component APIs documented	In Progress
You Tube Video	Instruction Video	In Progress

Other Problems

• A testrun with invalid sw_product executes a testrun with sandbox-values. An error should be raised and no testrun should be executed.
• Exceptions are not handled and they hit the xmlrpc. request_sync() should always return PASS/FAIL/ERROR. nothing else.
• Incompatible worker version leaves worker in an unknown state and does not report the problem clearly.

Scheduled for 0.9 Release

Organisation, maintenance and upgrades

• Component reorg (Assess a better representation of Components in code layout. Check impact on deployment)

• Better unittest harvester (perhaps setup.py test)

• Evaluate status of dependencies (AMQP 1.0, minixsv supports Python 2.5, setuptools versus distribute etc)

Conductor

• Python APIs

• API stability

• 6Pack integration

• Automated reboot

Server

• Remove InputPlugin

• Lower level extension points on Result File Parsing

• 6Pack Integration

Not scheduled items

Security

• HTTPS XML-RPC

• AMQP connection using SSL encryption

• OTS server and worker working in user mode

• Define firewall settings for OTS server and worker

• User authentication and access rights

• Test request DDoS filter