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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---