Result for 04E2E4B0F215E4A487C24437488A3379FA3A3F3E

Query result

Key Value
FileName./usr/lib/ruby/vendor_ruby/astute/provision.rb
FileSize21043
MD52DF63B955C6F398FB448CC302E40C08E
SHA-104E2E4B0F215E4A487C24437488A3379FA3A3F3E
SHA-256A48E918548D5E7F65D0DA6AB94C87F07E90FC99729DEC4BEBC453C1091EB6E99
SSDEEP384:T7SldwRPw+qvZzoqlFQDPY2r7Ar7ZHjo88FTKRzsivRVkvniMDOMTXSSTCyb/CvV:TBwv3+Bwtk8AjSPIw
TLSHT186928637DD5A1DAE03CA80A675CB1553EA6C300746E82A30768ED3E53F062A670F5EF5
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize86434
MD5945D1B5462D708199D3181E14538586A
PackageDescriptionDeployment Orchestrator of Puppet via MCollective For the provisionning, Astute orchestrator collects data about nodes and creates corresponding Cobbler systems using parameters specified in engine section of provision data. After the systems are created, it connects to Cobbler engine and reboots nodes according to the power management parameters of the node. . For the deployment, Astute uses data about nodes and recalculates needed parameters. Calculated parameters are passed to the nodes being deployed by using the nailyfact MCollective agent, that uploads these attributes to the /etc/astute.yaml file of the node. Then puppet parses this file using Facter plugin and uploads these facts into puppet. These facts are used during catalog compilation phase by puppet. Finally catalog is executed and Astute orchestrator passes to the next node in deployment sequence. Fuel Library provides puppet modules for Astute.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameastute
PackageSectionnet
PackageVersion9.0+dfsg1-2
SHA-19B900B284FD04E82871B9BFB25DB4BFB9151BCEB
SHA-25634DFC82CA69C91164383012595CA0F7E334D301981CE4A20BA91FAFE4FEF83A5