SCIF 2.0 Spec

1.1 History and Overview of the Project

In early 2007, Microsoft began working on a project called the “OSD Integration Kit”, which was designed as a development jump-start effort to help OEM partners quickly create integrations for bare metal server deployment. As it progressed, the code became more of a framework – a set of vendor-neutral extensions written to the Configuration Manager SDK, but extensible and customizable to provide uniqueness for each vendor adopting it.
Four OEMs (Dell, HP, IBM and Sun) adopted the integration code, provided testing, end-user documentation, and their own unique capabilities. Each has shipped at least one revision of their product based on the integration kit, and plan to continue further revisions and further enhancements based on these integrations. The development jump-start has become something the OEMs are relying on to deliver base product capabilities with Configuration Manager, as well as differentiation now and in future revisions.

The first version of the integration kit was written on-the-fly without much process, formal planning, or vision toward maintaining the code base as a real framework, potentially integrated with multiple System Center products. As it moves toward the next major revision, it become an inflection point in the design and use of the product and deserves a new name – the System Center integration Framework (aka SCIF – pronounced “skiff”). It also requires major restructuring to provide better documentation, testability, and linkage with current and future System Center integration interfaces.
Though the Framework is a new name, and the processes designed around developing the new version are more structured and involve more planning and strategy around the future, the basic principles are the same:
  • The Framework is a community-based shared-source project designed to help developers (both partners and customers) integrate with System Center products.
  • The Framework is a collection of assemblies and other code provided in C#, VBScript, Powershell, and potentially other languages, with full source code available, that allows developers not only an easy way to write integrations to System Center, but a way to “reverse engineer” the Framework source code to understand how best to write their own code that works directly with System Center APIs and SDKs.
  • The Framework augments (not duplicates) existing APIs and SDKs with practical examples, sample applications, starter kits and Visual Studio add-ons, and fully-functional integrations.
  • The Framework also includes numerous other utility classes that help the developer handle XML, CAB files, logging, exception handling, and more.

Last edited Aug 28, 2009 at 12:59 AM by rhearn, version 1

Comments

No comments yet.