State of Dynamic Infrastructure
By stanford on Jul 21, 2008
Well, I just returned from a much needed vacation, and thought it would be nice to capture where I think we are with our Dynamic Infrastructure project. Prior to vacation, we closed the books on the "3.0" release which has some basic capability to link together a service model stored in N(i)2 with the N1SPS provisioning system.
There were several key design principles demonstrated in this release including:
- abstraction of a CMDB (henceforth called a DCRM) as a set of interfaces and abstract classes
- definition of a model map schema that defines how a service model integrates with existing DCRM elements
- definition of tasks and status as a set of interfaces and abstract classes
- definition of a provisioning scenario descriptor schema
- implementation of an N(i)2 DCRM adaptor
- implementation of an N1SPS Provisioning adaptor
The goal was to show a streamlined operator role that minimizes the number of decisions at deployment time by placing them in the service model. The operator can now deploy complex services consisting of many layers of the stack (OS, virtualized OS, app server, application, etc.) while only selecting the proper template, and specifying how many instances to create.
The model contains the structure and operational process necessary to complete the provisioning activity and update the DCRM with the new instance. This is pretty exciting stuff, but there is quite a bit of work ahead...
Just before vacation, I spent a great deal of time discussing DI with customers. The reception shows that we are on the right track.
At this point, the team will probably go back to design mode and work on the next big areas. We haven't quite defined the scope of the next phase, but I suspect some of the big areas will be:
- refactoring / abstracting the provisioning adapter interface
- getting a registration system in place for adapters and working on the comms between them
- creating one or two more reference provisioning adaptors (network and storage come to mind)
- prototyping a solution developer interface that enables easier model development
That's about all I know so far. Now I need to catch up on what the team has been doing while I was out.