Hi, can Puppet have interoperability with OMA-DM? http://en.wikipedia.org/wiki/OMA_Device_Management My purpose would be to use an existing OMA-DM solution to manage the devices but use Puppet to implement the web services on the client side. With Puppet, I do not quite understand how the server side queries the client side capabilities? The OMA-DM process is mature and well documented. I started thinking it is not OMA-DM v Puppet, but OMA-DM && Puppet. Brilliant insights?? thanks, tom On Tue, Feb 3, 2009 at 20:15, Gary <garyyuen@gmail.com> wrote:> > Hello, > > I''ve also had the same issues. One possible way is changing nsswitch > to lookup group info from LDAP. I''ve tried that but haven''t gotten it > working quite right. > > The other way I''m using for now is to specify groups by number. > > Gary > > On Feb 4, 1:50 am, Brian <briandqu...@gmail.com> wrote: > > I''m having a problem that''s very similar tohttp:// > projects.reductivelabs.com/issues/791 > > > > I''m setting up a node as a ldap client, and creating a couple of files > > with group owners that are groups that exist in LDAP. Puppet can''t > > find the group on the first run (when it also configures /etc/ > > ldap.conf and /etc/nsswitch.conf), but I can find it on subsequent > > run''s. > > > > I''m running 0.24.7 (and I looks like #791 was closed in 0.24.6). > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Feb 4, 2009, at 12:27 PM, Tom D. Davidson wrote:> Hi, can Puppet have interoperability with OMA-DM? > http://en.wikipedia.org/wiki/OMA_Device_Management > > My purpose would be to use an existing OMA-DM solution to manage the > devices but use Puppet to implement the web services on the client > side. > > With Puppet, I do not quite understand how the server side queries > the client side capabilities? The OMA-DM process is mature and well > documented. I started thinking it is not OMA-DM v Puppet, but OMA-DM > && Puppet.I''d never seen this before, so at this point Puppet definitely can''t speak OMA-DM. I could see the ability to do so, but someone who was an expert on OMA- DM would need to do the connecting. You''d probably need to push the configs, rather than Puppet''s traditional pull model, though. -- Once...in the wilds of Afghanistan, I lost my corkscrew, and we were forced to live on nothing but food and water for days. -- W. C. Fields --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Tom D. Davidson
2009-Feb-05 05:17 UTC
[Puppet Users] Re: Puppet && OMA-DM interoperability
> > > I''d never seen this before, so at this point Puppet definitely can''t > speak OMA-DM. > > I could see the ability to do so, but someone who was an expert on OMA- > DM would need to do the connecting. You''d probably need to push the > configs, rather than Puppet''s traditional pull model, though.Hi Luke. Im not understating how Puppet communicates. puppetmasterd (server) speaks with the agent (client) using xmlprc (soon to be jason?) over https what is the format of the xml payload? push? from server to client? how does puppetmasterd know of agent capabilities? still working on fitting Puppet in the bigger picture of my project.... thanks for your help. -tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Feb 4, 2009, at 11:17 PM, Tom D. Davidson wrote:> > I''d never seen this before, so at this point Puppet definitely can''t > speak OMA-DM. > > I could see the ability to do so, but someone who was an expert on > OMA- > DM would need to do the connecting. You''d probably need to push the > configs, rather than Puppet''s traditional pull model, though. > > Hi Luke. > Im not understating how Puppet communicates. puppetmasterd (server) > speaks with the agent (client) using xmlprc (soon to be jason?) over > https > > what is the format of the xml payload?Currently xmlrpc over https, and the payload varies but is usually just serialized ruby objects. Future direction is REST-style https, and the payload will vary based on the content-type headers but will usually be either serialized ruby objects or exported objects (e.g., converted to json, so they''re language-agnostic).> > push? from server to client? how does puppetmasterd know of agent > capabilities?Pull, from client to server. And the server does not currently have any way to respond to the client''s features, other than including the client''s facts during the compile process.> > still working on fitting Puppet in the bigger picture of my > project.... thanks for your help.-- Should I say "I believe in physics", or "I know that physics is true"? -- Ludwig Wittgenstein, On Certainty, 602. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Tom D. Davidson
2009-Feb-06 08:51 UTC
[Puppet Users] Re: Puppet && OMA-DM interoperability
> > what is the format of the xml payload? > > Currently xmlrpc over https, and the payload varies but is usually > just serialized ruby objects.ok, right. with Puppet there is not device management tree because the device is abstracted. Instead the payload carries the rescipies?> > push? from server to client? how does puppetmasterd know of agent > > capabilities? > > Pull, from client to server. And the server does not currently have > any way to respond to the client''s features, other than including the > client''s facts during the compile process.FYI OMA-DM is a pull from the client, but there are way around to tell the client to make the pull. Clients facts during compile.... this is at puppetmastered? so the server still needs to know the unique details of each device/client? -tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Feb 6, 2009, at 2:51 AM, Tom D. Davidson wrote:> >>> what is the format of the xml payload? >> >> Currently xmlrpc over https, and the payload varies but is usually >> just serialized ruby objects. > ok, right. with Puppet there is not device management tree because the > device is abstracted. Instead the payload carries the rescipies?The payload for the configuration stage is the result of compilation, and is data-only (no variables, no functions, etc.).> >>> push? from server to client? how does puppetmasterd know of agent >>> capabilities? >> >> Pull, from client to server. And the server does not currently have >> any way to respond to the client''s features, other than including the >> client''s facts during the compile process. > FYI OMA-DM is a pull from the client, but there are way around to tell > the client to make the pull. > Clients facts during compile.... this is at puppetmastered? so the > server still needs to know the unique details of each device/client?The client discovers its facts and pushes them to the server, and the server then uses them to compile the configuration. -- SCSI is *not* magic. There are fundamental technical reasons why it is necessary to sacrifice a young goat to your SCSI chain now and then. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Tom D. Davidson
2009-Feb-09 16:37 UTC
[Puppet Users] Re: Puppet && OMA-DM interoperability
> The payload for the configuration stage is the result of compilation, > and is data-only (no variables, no functions, etc.).I c. So it would be somewhat pointless extending an existing OMA-DM solutions to support Puppet clients. The OMA-DM transfers the device settings in a standardized xml tree.... Im certainly not looking this as weakness - but I clearly had the wrong idea :) thanks, tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---