Picasso: A Service Oriented Architecture for Model-based Automation


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Picasso: A Service Oriented Architecture for Model-based Automation
# 1  
Old 02-07-2008
Picasso: A Service Oriented Architecture for Model-based Automation

HPL-2007-50 (R.1) Picasso: A Service Oriented Architecture for Model-based Automation - Singhal, Sharad; Pruyne, James; Machiraju, Vijay
Keyword(s): SOA; model-based automation; service models
Abstract: The increasing costs and complexity of maintaining IT environments has resulted in a focus on both Services Oriented Architectures (SOA) as well as model-based automation. By creating IT functions as modular building-blocks and automating common interaction patterns between them, IT can be made more ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

ARM Based Community oriented to Job

Hi everybody, I write this small news in order to inform you an ARM network has been created around job opportunities and Vocational TRaining for student. This open group is coming together design, hardware software domains on ARM RISC Architecture. With more than 1,500 users from great... (0 Replies)
Discussion started by: ARMBasedGroup
0 Replies
Login or Register to Ask a Question
CONFIG-MODEL-EDIT(1p)					User Contributed Perl Documentation				     CONFIG-MODEL-EDIT(1p)

NAME
config-model-edit - Graphical model editor for Config::Model SYNOPSIS
config-model-edit [options] -model Sshd [ class:Sshd element:Foo ... ] # plugin mode config-model-edit [options] -model Debian::Dpkg -plugin-file dpkg-snippet.pl DESCRIPTION
config-model-edit will provides a Perl/Tk graphical interface to edit configuration models that will be used by Config::Model. Config::Model is a general purpose configuration framework based on configuration models (See Config::Model for details). This configuration model is also expressed as structured data. This structure data is structured and follow a set of rules which are described for humans in Config::Model. The structure and rules documented in Config::Model are also expressed in a model in the files provided with Config::Model::Itself. Hence the possibity to verify, modify configuration data provided by Config::Model can also be applied on configuration models using the same user interface as config-edit. The model editor program is config-model-edit. USAGE
"config-model-edit" will read and write model file from "./lib/Config/Model/models". When you specify a "-model" options, only configuration models matching this options will be loaded. I.e. config-model-edit -model Xorg will load models "Xorg" (file "Xorg.pl") and all other "Xorg::*" like "Xorg::Screen" (file "Xorg/Screen.pl"). Options -model Mandatory option that specifies the configuration model to be edited. -plugin-file foo.pl this option can be used to create model plugins. A model plugin is an addendum to an existing model. The resulting file will be saved in a ".d" directory besides the original file to be taken into account. For instance: $ config-model-edit -model Debian::Dpkg -plugin-file my-plugin.pl # perform additions to Debian::Dpkg and Debian::Dpkg::Control::Source and save $ find lib -name my-plugin.pl lib/Config/Model/models/Debian/Dpkg.d/my-plugin.pl lib/Config/Model/models/Debian/Dpkg/Control/Source.d/my-plugin.pl -trace Provides a full stack trace when exiting on error. -force-load Load file even if error are found in data. Bad data are loaded, but should be cleaned up before saving the model. See menu "File -> check" in the GUI. -dot-diagram Returns a dot file that represent the stucture of the configuration model. "include" are represented by solid lines. Class usage (i.e. "config_class_name" parameter) is represented by dashed lines. The name of the element is attached to the dashed line. -dump [ file ] Dump configuration content on STDOUT or in the specified with Config::Model syntax. By default, dump only custom values, i.e. different from application built-in values or model default values. See -dumptype option for other types of dump -dumptype [ full | preset | custom ] Choose to dump every values (full), only preset values or only customized values (default) -load <cds_file_to_load> | - Load model from cds file (using Config::Model serialisation format, typically done with -dump option). This option can be used with "-save" to directly save a model loaded from the cds file or from STDIN. -load-yaml <yaml_file_to_load> | - Load configuration data in model from YAML file. This option can be used with "-save" to directly save a model loaded from the YAML file or from STDIN. -dump_yaml Dump a model in YAML format -save Force a save of the model even if no edition was done. This option is useful to migrate a model when Config::Model model feature changes. -dir Directory where to read and write model -open-item 'path' In graphical mode, force the UI to open the node specified. E.g. -open_item 'class:Fstab::FsLine element:fs_mntopts rules' LOGGING
All Config::Model logging was moved from klunky debug and verbose prints to Log::Log4perl. Logging can be configured in the following files: o ~/.log4config-model o /etc/log4config-model.conf Without these files, the following Log4perl config is used: log4perl.logger=WARN, Screen log4perl.appender.Screen = Log::Log4perl::Appender::Screen log4perl.appender.Screen.stderr = 0 log4perl.appender.Screen.layout = Log::Log4perl::Layout::PatternLayout log4perl.appender.Screen.layout.ConversionPattern = %d %m %n Log4Perl categories are shown in "LOGGING" in config-edit AUTHOR
Dominique Dumont, ddumont at cpan dot org SEE ALSO
Config::Model, Config::Model::Node, Config::Model::Instance, Config::Model::HashId, Config::Model::ListId, Config::Model::WarpedNode, Config::Model::Value perl v5.14.2 2012-06-22 CONFIG-MODEL-EDIT(1p)