I'm curious if anyone out there uses (or does not use!) a workflow where they might have some packages or repos that are for different levels of workflow. For instance, seperate environments for "devel", "Q/A" (test), "stage", or "production" -- having at least two levels, but maybe more? In other words, is there an app that you develop that needs to be deployed to different levels of servers as it passes various checkpoints? (What tools and processes are involved in those checkpoints?) If you have setups like this, how do you manage them with Cobbler and other tools? What is your workflow, or do you have one? Thanks! --Michael _______________________________________________ cobbler mailing list cobbler(a)lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler

In other words, is there an app that you develop that needs to be deployed to different levels of servers as it passes various checkpoints? (What tools and processes are involved in those checkpoints?) If you have setups like this, how do you manage them with Cobbler and other tools? What is your workflow, or do you have one?

Hello Michael DeHaan <mdehaan(a)redhat.com&gt; writes: > I'm curious if anyone out there uses (or does not use!) a workflow > where they might have some packages or repos that are for different > levels of workflow. Yes. I have developed for our needs an application to handle a workflow of packages during their qualification. > For instance, seperate environments for "devel", "Q/A" (test), > "stage", or "production" -- having at least two levels, but maybe > more? We have 4 levels: - integ: barely tested but should work - qa_ready: functional test done - pre_release: most QA tests done, may be shipped to customer with some restrictions (early access) - release (aka production). > In other words, is there an app that you develop that needs to be > deployed to different levels of servers as it passes various > checkpoints? (What tools and processes are involved in those > checkpoints?) Packages are tested before entering the "integ" level mostly by rpmlint and some custom tools to enforce our policy. Integration team is responsible of creating a package set that represent a major functionality or a product. Once these package sets are created, they can be promoted to qa_ready is decided by integration team (all packages will follow the promotion of a package set). Promotion to pre_release or release is decided by QA or project manager. A promotion can be done by a command line or by a web interface. Notifications are sent by mail to notify people about the package and package set evolution in the infrastructure. I have presented this "package infrastructure" to French Perl Workshop [1] in June. They provides some details on the workflow and tools. Fortunately for most of you the slides [2] are in English. > If you have setups like this, how do you manage them with Cobbler and > other tools? What is your workflow, or do you have one? Ahem, interaction with Cobbler is not done yet, but is definitely on our radar screen. Feel free to send comments or questions. Hope this helps [1] http://conferences.mongueurs.net/fpw2009/ (French) [2] http://journeesperl.fr/fpw2009/slides/hp_pkg_infra.pdf (English) -- Dominique Dumont "Delivering successful solutions requires giving people what they need, not what they want." Kurt Bittner irc: domidumont at irc.freenode.net ddumont at irc.debian.org _______________________________________________ cobbler mailing list cobbler(a)lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler