On Jan 31, 2012, at 1:52 PM, Ryan Lane wrote: >> Sorry for the slow response on this. There has been a lot to do for e-3. In >> any case, here are my thoughts on the subject. I am really not convinced >> that configuration management needs to be part of nova at all. This is >> stuff that should be built on top of nova. We have a bit of work to do >> cleaning up and improving metadata to make this type of thing easier, but I >> don't see any big needs for this to be in nova. A horizon plugin that >> handles this seems like it would be much more interesting. >> > > Then cli users can't use this, and other web frontends can't use it > and everyone would very likely implement it differently. My hope was a > consistent interface for this kind of stuff, so that users would be > able to use this at different providers, and so that libraries could > implement this consistently. > > - Ryan
Sounds like it could be its own openstack project with its own standard api. The scope of nova has the potential to get quite unwieldy, and I think we should make sure to keep it lean and mean. There is already quite a bit of stuff in that really should be a separate service. Nova does provide some really cool libraries and code for making services easily, but we should separate all of that stuff into openstack-common so that new services can use it. There is some prior art for putting stuff in nova and pulling it into its own project later: see melange and nova-volume for example, but I think as the project grows that is going to become more and more difficult. Vish _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
