IMO, the existing project implementation isn’t a good example (looks like the requirements were incomplete).
From: Will Stevens <wstev...@cloudops.com<mailto:wstev...@cloudops.com>> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> Date: Monday, August 25, 2014 at 11:20 AM To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> Subject: Developing for Project Support Hey All, I have had a quick look around at some of the different implementations and I am seeing that projects in CS seem to be handled as 'special' accounts. The API calls have fields like 'projectid' and such, but those details are not saved into the DB, the only thing that happens in the DB is a new project account ID is added to the db for that element (think, networks, instances, etc...) If I want to extend the functionality of an existing piece of code which does not support projects to also support projects, do you know of any specific examples in the code that are good implementations which I should be using as a good example to follow for adding project support? Thanks, *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_
