> We made a messy cloudstack API already, and it's hard to get rid of it, as a > lot > of clients((UI/marvin/jcloud, other cloudstack bindings)) are using this APIs > already. > We shouldn't make the mistake again, assuming that only AgentManager will > use this agent APIs. >
First, I don't think making things REST automatically makes it not messy. For example, I don't see how REST would make VM any simpler than the start vm command today because startvm command already contains a vm resource in it. Second, this is the southbound api not the northbound. I generally think our northbound api is a few magnitude messier than the southbound api. I think it makes sense to have full fledge REST APIs for full fledge services. The hypervisor resources are not really full fledge services. --Alex
