Techniques for instantiating and configuring projects
View Patent ↗Techniques for project management instantiation and configuration are provided. A master project includes policy directives that drive the dynamic instantiation and configuration of resources for a project. The resources are instantiated and configured on demand and when resources are actually requested, in response to the policy directives.
1. A system, comprising:
a master project managing service implemented in a machine-accessible and readable medium and to process on a machine; and
a virtual project definition implemented in a machine-accessible and readable medium and to be interpreted by the master project managing service;
wherein the master project managing service is to interpret the virtual project definition to manage a master project having a plurality of stages associated with its lifecycle, wherein each stage is associated with a different processing environment, and wherein the master project managing service in response to directives and policies associated with the virtual project definition initially deploys some resources associated with the master project when the master project is initiated in an initial stage of the lifecycle and delays deploying other deferred resources associated with the master project until permitted to deploy those deferred resources in response to the policies.
2. The system of claim 1 , wherein the virtual project definition includes nested virtual project definitions for sub projects that are independent of the master project.
3. The system of claim 2 , wherein at least one nested virtual project definition is hidden from a user's view with a masked code or reference within the virtual project definition, and when deployed sub project resources used are not accessible to or viewable by the user.
4. The system of claim 2 , wherein the master project managing service recognizes that some of the nested virtual project definitions are associated with already instantiated and configured resources for some of the sub projects and immediately makes the already instantiated and configured resources available to the master project when the policies permit.
5. The system of claim 2 , wherein the master project assembles the sub projects and their sub project resources for use within a particular stage and provides access to a number of the sub project resources from the particular stage when those sub project resources are located in different stages of the lifecycle.
6. The system of claim 2 , wherein the master project in response to the policies deploys each of the sub projects in a variety of different stages for the lifecycle and when directed by the policies re-assembles the sub projects as the master project accessible within a particular stage, wherein the particular stage is determined by the policies of the virtual project definition for the master project.
7. A system, comprising:
a project lifecycle management service implemented in a machine-accessible and readable medium and to process with the first processing environment of the network; and
a master project definition implemented in a machine-accessible and readable medium and to be interpreted by the project lifecycle management service;
wherein the master project definition includes nested project definitions or references to independent sub projects, the master project definition also defining, via the nested project definitions, a single master project having multiple stages in a lifecycle of that master project, and wherein the project lifecycle management service is to monitor activities of a first principal within the first processing environment with respect to the master project definition to determine when some or each of the independent sub projects are to be configured and made available to the first principal in the first processing environment.
8. The system of claim 7 , wherein the project lifecycle management service is to also monitor other events associated with the independent sub projects, some of the events communicated from other processing environments.
9. The system of claim 7 , wherein at least one nested project definition associated with a particular sub project is unavailable and not viewable by the first principal.
10. The system of claim 9 , wherein the particular sub project has resources that automap, configure, and instantiate to the first processing environment according to policy defined in the master project definition.
11. The system of claim 7 , wherein the sub projects appear to the first principal to be present for access within the first processing environment even when some of the sub projects are not yet configured and available for use within the first processing environment.