[Fiware-cloud] Open Call candidates

[Alex Glikson]

All,

While finalizing the backlog and the work plan for the first release & 
sprint, now is the time to create the initial list of gaps that we have 
identified -- those which we believe can not be contained within our team 
(with the current funding level), and hence should potentially be 
targeting the first Open Call.

Here is an initial list -- please, provide your feedback. The deadline is 
EOD Monday (sorry for the short notice).

Virtualization Layer (Resource Management, Object Storage) -- TBD [Andy -- 
can you, please, suggest what would be the impact on the virtualization 
layer of not having the FT team on board? and/or other significant gaps 
that you are aware of -- maybe based on the Epics that we've identified?]
Accounting [Fernando, all -- can you, please, outline the expected scope 
of work here? I assume this GE might subscribe to the Monitoring system, 
keep the records about resource usage in some internal format/repository 
-- per VM, service, account, etc.. maybe also enforce things like resource 
quotas? anything else?]
Monitoring -- TBD, pending availability of the corresponding assets from 
WP6 [Andy -- can you, please, assess the sizing of the work on this GE if 
we go for an open-source stack, based on the assets you've mentioned?]
SelfServices -- Portal
Cloud Edge -- cloud-side management "agent" (Note: still under discussion)
Service Management -- service composition tool (that would allow the 
application developer to easily build the corresponding OVF package)
anything else -- all?

Thanks,
Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20111027/81d88585/attachment.html>