Issue #1484 has been updated by Sonny Cook.
It seems that the term 'resource' is used to refer to different things at the same time here. That coupled with my newness will likely lead me to be frequently confused. If I understand correctly, following are the potential uses we might encounter in this discussion. * Rest resource - something accessed from a rest interface. Largely irrelevant excepting apart from the fact that we are using Rest. * Manifest Catalog Resource - maps to Puppet::Resource and represents the generic interface to a logical catalog resource * RAL Catalog Resouce - maps to Puppet::Type and implements (what appears to be) a lot of non-reversable 'instantiation' logic Currently the xmlrpc hanlder addresses instances of Puppet::Type and marshalls them using (apparently deprecated) TransObject and TransBucket. Objects of type Puppet::Resource already know how to marshall/unmarshall themselves for transmitting the catalog around via Rest, so if that is what we are looking at doing, it should be fairly simple. From talking to Ethan, however, it seems that the objects of type Puppet::Resource only form a subset of the eventual set the catalog will have for Puppet::Type. This seems like it would be insufficient, then. It seems like you want to expose Puppet::Type to the Rest resource interface in order to get resources in and out of the RAL catalog. Is this it, or am I misunderstanding? ---------------------------------------- Refactor #1484: The 'resource' handler needs to be refactored to use the Indirector and REST http://projects.reductivelabs.com/issues/1484 Author: Luke Kanies Status: Accepted Priority: High Assigned to: Luke Kanies Category: plumbing Target version: Rowlf Affected version: 0.24.7 Branch: Currently, there's an xmlrpc Resource handler that can provide information on resources and modify them. This class needs to be refactored entirely to use the Indirector instead of being tied to XMLRPC. Most likely, the bits that talk to the RAL need to moved to a terminus type, and then we need a new Resource class that provides a simple model for resources. Hopefully, this class can be a model for how to integrate all of the different Resource models we have. Once the class exists, it needs to be able to use REST for communication. Backward compatibility isn't important here, because we'll just keep the xmlrpc handler around. I think the only code that uses this class is the 'ralsh' executable. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
