<html><head></head><body><div class="gmail_quote">On 2 May 2017 3:20:28 AM NZST, Brian Bouterse <bbouters@redhat.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div dir="ltr"><div><div>Hi Dagen,<br /><br /></div>For Pulp 3.0.0, the feature set is mostly known with user use cases tracked in a document on the wiki. The doc [0] is written as a minimum viable product so we can deliver something that provides Pulp's core value in a timely manner and then we can add features to it over time. Some notable gaps include no authorization, nodes has been removed, and so have scheduled calls. One notable addition is a legitimate Plugin API to ease the burden for plugin writers adding content support.<br /><br /></div><div>Pulp3 will only use PostgreSQL, which will entirely replace Pulp's usage of mongodb. It's good to hear this will match your standard operating environment.<br /><br /></div><div>In terms of Nagios, I'm more familiar with that as a management system instead of httpd. I'd have to hear more about what you would like in terms Nagios support. In terms of using Nagios for monitoring, the Status API is available in Pulp2 and will also be in Pulp3.<br /></div><div><br /></div><div>There is a developer mailing list called pulp-dev which is where most of the Pulp3 discussion is currently happening. You can join it [1] or read the archives [2]. We also have weekly calls [3] where each week we refine a section of the MVP with more details.<br /><br /></div><div>If you have specific use cases, suggestions, or ideas, please let us know! We would really like some alpha/beta testing, which we hope to be starting soon but we are just a bit early for. Right now making sure the use cases are sound is one of the best ways to contribute.<br /></div><div><br />[0]: <a href="https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Minimum_Viable_Product" target="_blank">https://pulp.plan.io/projects/<wbr />pulp/wiki/Pulp_3_Minimum_<wbr />Viable_Product</a><br />[1]: <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" target="_blank">https://www.redhat.com/<wbr />mailman/listinfo/pulp-dev</a><br />[2]: <a href="https://www.redhat.com/archives/pulp-dev/" target="_blank">https://www.redhat.com/<wbr />archives/pulp-dev/</a><br />[3]: <a href="https://www.redhat.com/archives/pulp-list/2017-April/msg00010.html" target="_blank">https://www.redhat.com/<wbr />archives/pulp-list/2017-April/<wbr />msg00010.html</a><br /><br /></div>-Brian<br /><br /><div class="gmail_extra"><br /><div class="gmail_quote">On Thu, Apr 27, 2017 at 6:38 PM, Dagan McGregor <span dir="ltr"><<a href="mailto:list@sudo.nz" target="_blank">list@sudo.nz</a>></span> wrote:<br /><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br /> <br /> I have been looking at installing Pulp for managing our local rpm repositories and I am curious about what changes are planned or confirmed for Pulp 3.0.<br /> <br /> Our site standard is to run PostgreSQL and Nagios for services wherever possible, having migrated off httpd.<br /> <br /> Will Pulp 3.0 continue using MongoDB or will other databases like PostgreSQL be supported as well?<br /> <br /> And are there any plans to have Nagios support alongside the current httpd?<br /> <br /> I did find a blog article but nothing else mentioned. I am happy to help with some testing if it would be useful.<br /> <br /> Cheers,<br /> Dagan McGregor<br /> <br /> <br /> <br /> ______________________________<wbr />_________________<br /> Pulp-list mailing list<br /> <a href="mailto:Pulp-list@redhat.com" target="_blank">Pulp-list@redhat.com</a><br /> <a href="https://www.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr />/listinfo/pulp-list</a><br /> </blockquote></div><br /></div></div> </blockquote></div><br clear="all">Hi Brian, <br> <br> Thanks for the reply. <br> <br> I had a major brain fade. I meant to say *Nginx support* for web services. <br> <br> As Homer would say, D'oh! <br> <br> I see the current design uses httpd and mod_wsgi. I assume not all features may match with using something like Nginx and uWSGi. <br> <br> It would be nice as an option if possible, if changes are still being considered. <br> <br> I will join the dev list to follow the discussions there. <br> <br> Cheers, <br> Dagan McGregor <br> <br> <br> <br> <br> </body></html>