Skip to content
jguiditta edited this page Mar 27, 2013 · 4 revisions

Tim Roadmap

Process / Documentation

Exception Handling Guide

Logging process guide

https://github.com/aeolus-incubator/tim/issues/115

User/Dev Guides

https://github.com/aeolus-incubator/tim/issues/50

Contributer Guides

Technical Debt

Model Validations

https://github.com/aeolus-incubator/tim/issues/50

Add logging through out Tim

https://github.com/aeolus-incubator/tim/issues/116

Error / Exception Handling

https://github.com/aeolus-incubator/tim/issues/103 https://github.com/aeolus-incubator/tim/issues/82

Features

Pull out Conductor Provider/Accounts models into separate gem and include in dummy/example app

Remove Imagefactory Dependence

We are too reliant on Imagefactory and thus Tim's capability is completely dependent on what Imagefactory can and can not do. We should think about factory as just one way we can realise certain features. We could just as easily integrate with DC for certain things, puppet, cfengine, Kiwi and alike...

Builder plugins

We are inherently tied to Imagefactory to handle everything from Building the base OS, package installation and configuration. Builder plugins can still use factory technology to handle much of this. But allow users to use a 3rd party tool such as Puppet or CFEngine to handle package installation and configuration.

Thoughts on How? I'm thinking we can allow the registration of TDL plugins via the API, which will take the form of TDL snippets. In the puppet case for example, the TDL will include all the packages needed for installing a puppet worker, script elements that register the boot service systemctrl. This is post boot config. The same could be done for CFEngine.

Integration with V2V

Windows support

If factory is not able to do this, then I suggest we think about integrating with a tool that can.

Use RABL

https://github.com/aeolus-incubator/tim/issues/38

or https://github.com/rails-api/active_model_serializers

We should tinker a bit with each and see which is a better fit. From a design standpoint, I think the latter may be a better fit (@jguiditta)

Upgrade to Rails 4

https://github.com/aeolus-incubator/tim/issues/76

Renames (Is this still relevant?)

https://github.com/aeolus-incubator/tim/issues/103

Create ImageFactory Client Gem

https://github.com/aeolus-incubator/tim/issues/114

Example Application with UI + API

Create an example App that demonstrates the capabilities of Tim. This could also integrate with DC, to create a very simple but powerful cross cloud management tool.

API Rework

Revisit API, add in any extra pieces such as allowing templates to be queryable. Bits and pieces to make it more usable.

Template Versioning

We should allow the ability for users to update templates and keep versioned copies.

API support for JSON