Result for 0E5A1A7FD871D4EE8DAAE9CE5FAB1488D8EEEF36

Query result

Key Value
FileName./usr/lib/ruby/vendor_ruby/astute/mclient.rb
FileSize6071
MD583D6FDBDE0FA8280016A24FF68C42135
SHA-10E5A1A7FD871D4EE8DAAE9CE5FAB1488D8EEEF36
SHA-2563D5EDBFF761EB995E587C41A9CD78487845A9B59349FEAE38347A7BD086D9CCF
SSDEEP96:I4W/JiyBi+LS7qaI/GZvIaIvJoo4fpGt0OdG9BGzqG1BBGkM0GsH:I7ruflnwJoo4Yt0/9YzLnYbsH
TLSHT191C1751FB917197D43CEC54A766679D35B282857038A1AB434CCC1AC3F1162662FFAE3
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
FileSize134022
MD54D54C2809A46F43BBAC41E50F1E8976C
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
PackageVersion7.0+dfsg1-2
SHA-1701904548CB6AE98556A8E00292B4ABB4766E8CA
SHA-256134E5B2566F16D5206CA4E9E3E55A0CAF46EFDE289F7A3B4034E3B73287F3676