[Puppet Users] Re: puppet webserver

2009-01-27 Thread Tom D. Davidson
Thank you for your help. BTW, when i said, "...despite the resistance of other web servers..." i meant "existence of other web servers". "Very low resources" in the range of ~32mb RAM. The device to be managed by puppet will optionally run an web service that need .htaccess. I would like the se

[Puppet Users] Puppet && OMA-DM interoperability

2009-02-04 Thread Tom D. Davidson
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

[Puppet Users] Re: Puppet && OMA-DM interoperability

2009-02-04 Thread Tom D. Davidson
> > > 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, thoug

[Puppet Users] Re: Puppet && OMA-DM interoperability

2009-02-06 Thread Tom D. Davidson
> > 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

[Puppet Users] Re: Puppet && OMA-DM interoperability

2009-02-09 Thread Tom D. Davidson
> 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 tre

[Puppet Users] Re: Community: How to deal with attempts at sabotage

2009-03-04 Thread Tom D. Davidson
I do not think rights of free speech matter in this context. What matters is the type of community you want to foster and develop. I think open source communities should strive for openness and transparency. I will not use or ever recommend SugarCRM because of the posts over the vTiger fork of mine