Posts
Modularization
To make things easier to manage, I am modularizing various components of the QuickDep system into these Python modules: libqdcommon, libqdblast, libqdimage, and quickdep.
libqdcommon
This module contains all the common library bits of QuickDep needed in order to successfully call the QuickDep script. Things like profile verification, system integrity, and basic methods.
In addition, libqdcommon will now contain the proposed qd-auth (or qd-sec) logic, and will allow for system-wide authentication and security plugins.
libqdblast
This module contains all the blast-oriented bits of QuickDep, including all the logic needed to partition, deploy images, and perform file system-related tasks
libqdimage
Thirdly, libqdimage negotiates the difficult task of automatically creating images from a base system, as well as QuickDep profiles. This particular module is very early in its development, and requires a lot more work to function properly, but will eventually allow the main QuickDep script to automatically create images, profiles, and store them on the server.
quickdep
This is the master script, which seeks to be as simple,and streamlined as possible. Because all the arduous system checking, profile verification, and random other bits have been removed, it's a very easy-to-follow collection of method calls.
What this means for QuickDep
Hopefully, code will be much easier to manage. This will lead to easier customization of QuickDep for targeted deployments, and potentially increased flexibility when moving from one environment to another. Plus, things get a lot cleaner this way :)
QuickDep's current status
At the moment, the latest version per each revision are: 1.5 (stable), 2.1b (unstable), and 2.5 (modularized-devel).
The latest published version is 2.0 (which has concurrency issues).
1 comments :
As it turns out, it's going to be much simpler to just create a libquickdep, and a quickdep executable.
However, I must say, I'm not really that interested in this particular project anymore, as I'm starting to grow more comfortable with 100% package-based kickstart deployment options.
Post a Comment