<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> On 12/17/2011 01:30 PM, Jim Perrin wrote: <blockquote cite="mid:CALSzgHHN_Kpjj-FPMFhOqFgkezsLcJn7pAmeGwsgHiOwEcP7Yg@mail.gmail.com" type="cite">To follow up on an irc discussion with Jay, I'd like to start a bit of discussion about the development path for the cds portion of pulp. I haven't really found a feature development roadmap or idea/request list for pulp-cds, so I want to see how other users envision the cds working. I'd like to pose a question to the other users on the list to see what they'd like to see built into the cds package, or how they use the CDS. Thoughts and ideas? -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ Pulp-list mailing list <a class="moz-txt-link-abbreviated" href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-list">https://www.redhat.com/mailman/listinfo/pulp-list</a> </pre> </blockquote> At a high-level the vision for the CDS is to grow into a "scalable mirrored proxy" in 2012. So what does that mean??? 1. Horizontally scalable distribution mirror for content. 2. Http Proxy for inbound Rest API traffic; bridging network segments. 3. QPID Proxy (broker) for command & control; single pane of glass. We've started to capture some of the thinking here: <a class="moz-txt-link-freetext" href="https://fedorahosted.org/pulp/wiki/CDS-Public-Cloud">https://fedorahosted.org/pulp/wiki/CDS-Public-Cloud</a> Glad to see this discussion starting. We'll be defining/gathering CDS specific requirements over the next month or so. -Todd </body> </html>