Hi, Thanks a lot for your reply.
MCollective is a separate PuppetLabs product that provides remote control of machines configured to respond to it. From what you have said so far, I don't see MCollective being relevant to your problem. On the other hand, I'm still not altogether clear on the nature of the UI you postulate, or of its relationship with Puppet. ---In my setup, there are two applications (applnA and applnB) running on the same host. My requirement is to configure applnB. The configuration values are input to UI and the UI is part of applnA only. On Tuesday, December 16, 2014 8:13:10 PM UTC+5:30, jcbollinger wrote: > > > > On Monday, December 15, 2014 4:54:04 AM UTC-6, glos...@gmail.com wrote: >> >> Hi Felix, >> >> I have not quite got your reply. >> >> This configuration values will apply to the service managed by the puppet >> infrastructure. >> >> What i meant is whether there is any support from puppet to read config >> directly from a UI(this could be a different application) which then >> need to be applied to the config of the service managed by puppet. >> >> > > What does "read config *directly* from a UI" (emphasis added) mean? > Puppet cannot read anything from the system memory belonging to a different > process; no process can without being explicitly wired to perform IPC with > the separate process in question. Your UI can record configuration data > somewhere else where Puppet can read it, however. It might record that > information in a database, as Felix interpreted you to mean, or in a file > somewhere. > > You can access such data via an "external node classifier" (ENC), which is > an external program that you provide, or via Puppet's external-data > subsystem "Hiera". To integrate the data via Hiera you would need to > either put them in YAML format or to find or write an Hiera back-end that > knows how to access them in whatever other form and format you have chosen > for them. > > "The Foreman" and Puppet Enterprise's dashboard programs Felix mentioned > are UIs that provide for recording data about your nodes, and that supply > pre-built ENCs with which to integrate that data with Puppet. There are at > least one or two others. The Foreman is third-party software; the PE > dashboard is integrated with (only) the Enterprise version of Puppet. > > > >> I have not quite understood about MCollective as well. Is MCollective >> agent could be a way out? >> >> > > What trap are you in that requires a way out? > > MCollective is a separate PuppetLabs product that provides remote control > of machines configured to respond to it. From what you have said so far, I > don't see MCollective being relevant to your problem. On the other hand, > I'm still not altogether clear on the nature of the UI you postulate, or of > its relationship with Puppet. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f1a9a7c6-0eda-47a9-b4d1-e542d85c2fe6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
