We can add pulgins to resource to implement our customer resourses

Registered by Jim Jiang

Today when i watch the mail list i saw a project which named echo. It's wiki url is https://wiki.openstack.org/wiki/EHO .
It's use some apis in other projects to build a stack which did the same thing as us
I don't think it's a good ideal to implement a hadoop box in openstack , expecially when we have a project like heat, which will make cloud raise.
We can make a folder like contrib in nova which means plugin to our current resource and make a resource like namenode, datanode as we do in loadbalance resource implement.
If we provide a plugin way to accept others resources more futures will be implemented in our projects rapidly

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Jim Jiang
Direction:
Needs approval
Assignee:
Jim Jiang
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Steven Hardy

Related branches

Whiteboard

(shardy) : We already implement resource plugins, so I believe this BP is invalid?
http://lists.openstack.org/pipermail/openstack-dev/2013-January/004628.html
https://wiki.openstack.org/wiki/Heat/Plugins

(asalkeld): yea I think the way forward is to try get new projects to use heat for
their orchestration. As we get into "integrated" this might become easier.
I am not sure of the reference to nova/contrib?
I would hope that libra uses heat in the future instead of using that as an example.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.