From cschum at suse.de Mon Sep 7 02:57:45 2015 From: cschum at suse.de (Cornelius Schumacher) Date: Mon, 07 Sep 2015 10:57:45 +0200 Subject: [Machinery] New release: Machinery 1.12.0 Message-ID: <8382872.eM31ydibvq@endurance> Hi all, we are happy to announce a new release of Machinery. The most significant change is that it speeds up the inspection of unmanaged files quite a bit. This is due to the use of a new method of gathering data on the inspected machine using a helper binary. The fast inspection is only used for a subset of use cases right now. We are working on enabling the others as well. Complete change log: ## Version 1.12.0 - Fri Sep 04 16:51:10 CEST 2015 - cschum at suse.de * The x86_64 machinery-helper is now shipped with machinery. It speeds up inspection of unmanaged-files when the files are not extracted * Fix for unmanaged-file inspector to not mark directories as unmanaged if they only consist managed sub directories You can get the new packages for openSUSE from our home page at http://machinery-project.org or you simply run `zypper up machinery` on your local system. If you have feedback, please let us know. Your Machinery team -- Cornelius Schumacher From AlanR at unix.sh Tue Sep 8 04:48:41 2015 From: AlanR at unix.sh (Alan Robertson) Date: Tue, 8 Sep 2015 04:48:41 -0600 Subject: [Machinery] Assimilation project integration? Message-ID: <55EEBD09.5000300@unix.sh> Hi, Lars Marowsky-Bree suggested that there might be some common ground between the Machinery project and the Assimilation project - http://AssimilationSystems.com (http://assimproj.org). Any thoughts about that? -- Alan Robertson / CTO AlanR at AssimilationSystems.com / +1 303.947.7999 Assimilation Systems Limited http://AssimilationSystems.com Twitter Linkedin skype -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: twitter.png Type: image/png Size: 1418 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: linkedin.png Type: image/png Size: 1141 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: skype.png Type: image/png Size: 1632 bytes Desc: not available URL: From fteodori at suse.com Mon Sep 21 07:22:42 2015 From: fteodori at suse.com (Federica Teodori) Date: Mon, 21 Sep 2015 15:22:42 +0200 Subject: [Machinery] Machinery 1.13.0 is out! Message-ID: <560004A2.70405@suse.com> Dearest Machineriest, Since last release, we introduced you to machinery-helper: The little go inspector that makes inspection way faster than before. In version 1.12.0, machinery-helper was not (yet) handling extracted unmanaged files, but starting from the current release (1.13.0), this limitation is not applying any longer. Give it a try, and see what a difference it makes! This release also comes with an update of the format to version 5, so don't forget to update your existing system descriptions. (Don't worry, machinery will remind you to do so, in case it's needed!) If you are curious to see what version 5 brings, have a look at: https://github.com/SUSE/machinery/blob/master/docs/System-Description-Format.md#version-5 Complete changelog follows: -- ## Version 1.13.0 - Tue Sep 15 18:06:00 CEST 2015 - thardeck at suse.de * Fix: Show `Files extracted` status in `compare --html` when both status are the same (gh#SUSE/machinery#1218) * Fix: Validate port option in the `show`, `compare`, and `serve` commands (gh#SUSE/machinery#1316) * Align output of `machinery config` * Add rpc_pipefs to filtered filesystems (gh#SUSE/machinery#1250) * Handle socket errors for `-i` option * Add `containerize` command to the experimental features * Export of autoyast files is now possible with system descriptions, which have empty repository scopes (gh#SUSE/machinery#1268) * Inspection of unmanaged-files is now also using the faster machinery-helper when the files are extracted * Introduce format version 5 which adds the "environment" scope (see https://github.com/SUSE/machinery/blob/master/docs/System-Description-Format.md#version-5). This scope is a hidden scope which is used internally by Machinery. * Only print binary path if it's not first in PATH (gh#SUSE/machinery#1284) * Do not exclude files with broken UTF-8 filenames anymore We hope you?ll enjoy this release, and please do get in touch with us if you have any feedback or questions. Sincerely, Your Machinery team From cledorze at suse.com Mon Sep 28 08:27:13 2015 From: cledorze at suse.com (christophe le dorze) Date: Mon, 28 Sep 2015 16:27:13 +0200 Subject: [Machinery] How to run it on SLES11SP3 Message-ID: <3C0179F1-BB3E-4C58-A676-76E3DC9FB54E@suse.com> Hello All, I?m looking for a way to use and run Machinery on SLES11SP3. At the beginning i tried to built it from git but failed with ruby2.0 dep, so i tried to find a repo from build.opensuse.org but can?t success to built? What is the best way to build on SLES11SP3 ? The purpose is to recreate an already existing SLES11SP3 (SAPHANA server) hosted in AWS. Thanks for the feedback. Have a nice day`. From tgoettlicher at suse.de Mon Sep 28 08:39:55 2015 From: tgoettlicher at suse.de (Thomas Goettlicher) Date: Mon, 28 Sep 2015 16:39:55 +0200 Subject: [Machinery] How to run it on SLES11SP3 In-Reply-To: <3C0179F1-BB3E-4C58-A676-76E3DC9FB54E@suse.com> References: <3C0179F1-BB3E-4C58-A676-76E3DC9FB54E@suse.com> Message-ID: <5609513B.6070107@suse.de> On 09/28/2015 04:27 PM, christophe le dorze wrote: > Hello All, > > I?m looking for a way to use and run Machinery on SLES11SP3. > At the beginning i tried to built it from git but failed with ruby2.0 dep, so i tried to find a repo from build.opensuse.org but can?t success to built? > > What is the best way to build on SLES11SP3 ? > > The purpose is to recreate an already existing SLES11SP3 (SAPHANA server) hosted in AWS. > > Thanks for the feedback. > > Have a nice day`. Hi Christophe, There is no need to build and install Machinery on the target host. You can run Machinery on a SLES12 machine and make it inspect the SLES11SP3 host remotely if the SLES11SP3 host is accessible via ssh. Just run the following command on your SLES12 machine: $ machinery inspect Please let us know if this works for you. Thanks, Thomas > _______________________________________________ > Machinery mailing list > Machinery at lists.suse.com > http://lists.suse.com/mailman/listinfo/machinery -- SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany