<div dir="ltr"><div>+1 to option 2, rename of Pulp2 services. <br></div><div></div><div>It's a low risk change for Pulp2, in my opinion, and clear distinction of legacy version. <br></div><div>I also agree with all the mentioned reasons to keep Pulp3 ones unchanged and more importantly without version in the name.</div><div>-0 to make names configurable.</div><div><br></div><div>Tanya<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 5, 2019 at 5:01 PM Ina Panova <<a href="mailto:ipanova@redhat.com">ipanova@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>+1 to rename Pulp2 services. This way we would ensure that the users have upgraded to a minimal version of Pulp 2 before upgrading to Pulp 3. As a suggestion i would not make this change with the next Pulp2 release but whenever we'd be able to tell for sure that this Pulp2.Y version is the version we are supporting the upgrade from.<br></div><div>+1 on Eric's reasoning about being more strict and allow less variation in naming conventions.</div><div>+1 on Eric's point about if renaming Pulp3 services then this will lock services names to Pulp version. <br></div><div><br></div><div>@dana eventually in the discussion on the issue we decided to make only the hyphens change.</div><div><a class="gmail_plusreply" id="gmail-m_-1414178534003705730gmail-plusReplyChip-7" href="mailto:amacdona@redhat.com" target="_blank">@asmacdo</a> <a href="https://pulp.plan.io/issues/4497" target="_blank">https://pulp.plan.io/issues/4497</a> i think this is a dupe of <a href="https://pulp.plan.io/issues/4429" target="_blank">https://pulp.plan.io/issues/4429</a> <br></div><div><div><div><div dir="ltr" class="gmail-m_-1414178534003705730gmail_signature"><div dir="ltr"><br>--------<br>Regards,<br><br>Ina Panova<br>Software Engineer| Pulp| Red Hat Inc.<br><br>"Do not go where the path may lead,<br> go instead where there is no path and leave a trail."<br></div></div></div><br></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 5, 2019 at 3:44 PM Matt Pusateri <<a href="mailto:mpusater@redhat.com" target="_blank">mpusater@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>I like Option2, as long as we do it with and upgrade and we put Doc notes in, I don't see it as a problem.</div><div><br></div><div>Matt P. <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 5, 2019 at 8:48 AM Robin Chan <<a href="mailto:rchan@redhat.com" target="_blank">rchan@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>To clarify, regarding @dana's comment - I wasn't necessarily voting for Option 1. Just pointing out the downside to option 2 wasn't a concern to my knowledge.</div><div><br></div><div>@bherring - we have made changes to pulp 3 service names as @david pointed out. I do agree that making changes to pulp3 names seems to be the least invasive in the short term at first glance. Eric has given us feedback that the previous name change was not distinct enough. However I agree with his observation that specifying "3" won't be a great future proofed solution. I would argue that Option 2 is the "least invasive" in the short term because the lasting impacts would be the most short lived (ironically for the same reasons you noted.)</div><div><br></div><div>@kersom & @bherring - given your concerns about Option 2, can you suggest any variations/names for Option 1 that addresses the concern about longevity of the solution? Do you share Eric's concern regarding Austin's proposal to allow a user to specify? I agree with Eric's concern as I'd prefer that the naming be set to simplify debugging real life issues if there isn't a clear benefit to allowing this to be user specified (to be clear a -0 on Austin's suggestion - would like to hear more thoughts on this.)<br></div><div><br></div><div>-Robin<br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 5, 2019 at 8:19 AM Brian Herring <<a href="mailto:bherring@redhat.com" target="_blank">bherring@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Is one of our goals is to move all possible resources to working on Pulp3? <div><br></div><div>If so, I am going to agree with Kersom on the basis that it seems strange to make changes to a product we are attempting to sunset and should be making minimal changes.</div><div><br></div><div>Do we know all the impacts that changing service names in Pulp2 would have on Pulp2 yet? If we have and are still making changes to Pulp3, doesn't it make more sense to make those changes there when the product has yet to be launched?<br><div><br></div><div><div><div><div dir="ltr" class="gmail-m_-1414178534003705730gmail-m_-4850291410063520808gmail-m_5169652062944535112gmail-m_8399812168774962669gmail_signature"><div dir="ltr"><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span>BRIAN</span> <span>HERRING</span></p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>QUALITY ENGINEER - PULP QE</span><span style="color:rgb(170,170,170);margin:0px"></span></p><p style="font-family:overpass,sans-serif;margin:0px;font-size:10px;color:rgb(153,153,153)"><a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" target="_blank">Red Hat <span><br><br></span></a></p><span style="font-family:overpass,sans-serif;font-size:10px;margin:0px;color:rgb(153,153,153)"><p style="margin:0px">100 East Davie Street</p></span><span style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"></span><span style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"><p style="font-size:10px;margin:0px;color:rgb(153,153,153)">Raleigh, NC, 27601</p></span><span style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"></span><p style="font-family:overpass,sans-serif;margin:0px 0px 6px;font-size:10px;color:rgb(153,153,153)"><span style="margin:0px;padding:0px"><a href="mailto:bherring@redhat.com" style="color:rgb(0,136,206);margin:0px" target="_blank">bherring@redhat.com</a> </span> <span>M: <a href="tel:+19193238427" style="color:rgb(0,136,206);font-size:11px;margin:0px" target="_blank">+19193238427</a> </span> <span>IM: <span>bherring</span></span></p><table style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium" border="0"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"><img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></a></td></tr></tbody></table></div></div></div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 4, 2019 at 1:44 PM Kersom <<a href="mailto:kersom@redhat.com" target="_blank">kersom@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I do not think we should names in Pulp 2. Since this can cause impacts that we do not know. This will increase the amount of time that we will spend working on Pulp 2, changing, fixing, testing. At this point less changes in Pulp 2 is what I think we should do.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 4, 2019 at 1:10 PM Dana Walker <<a href="mailto:dawalker@redhat.com" target="_blank">dawalker@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>As I understand the discussion on 4497, it was to be hyphens *in addition to* a name change, but you're right @ehelms that I only see the hyphen change.</div><div><br></div><div>I'm +1 on @rchan's suggestion that the change take place in pulp2.</div><div><br></div><div>Also given the migration and complexities with support, I agree with @ehelms that custom configuration of these names would be problematic, so I'm -0 on this unless we have a compelling user story for needing the customizability (assuming we are making the change to the service names in pulp2 ourselves).</div><div><br></div><div>--Dana</div><div><br></div><div><div><div dir="ltr" class="gmail-m_-1414178534003705730gmail-m_-4850291410063520808gmail-m_5169652062944535112gmail-m_8399812168774962669gmail-m_1436359569295102806gmail-m_-8008353953902707300gmail_signature"><div dir="ltr"><div>
<p style="font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span>Dana</span> <span>Walker</span></p>
<p style="font-weight:normal;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>Associate Software Engineer</span><span style="font-weight:normal;color:rgb(170,170,170);margin:0px"></span></p>
<p style="font-weight:normal;margin:0px;font-size:10px;color:rgb(153,153,153)"><a style="color:rgb(0,136,206);font-size:10px;margin:0px;text-decoration:none;font-family:overpass,sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span><br><br></span></a></p>
<table border="0"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"> <img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></a> </td>
</tr></tbody></table>
</div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 4, 2019 at 1:06 PM Dennis Kliban <<a href="mailto:dkliban@redhat.com" target="_blank">dkliban@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>I agree with @rchan that we will require users to upgrade to a minimal version of Pulp 2 before they can upgrade to Pulp 3. <br></div><div><br></div><div>We should just rename Pulp 2 services in a future release of Pulp 2. <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 4, 2019 at 11:31 AM Eric Helms <<a href="mailto:ehelms@redhat.com" target="_blank">ehelms@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Howdy,<div><br></div><div>In some migration of Pulp 2 to Pulp 3 cases, both will need to be ran side-by-side on the same box. Given that pulp workers and pulp resource manager are the same concept in both, this leads to their systemd resources being named the same (or in today's case so slightly different enough you can't tell them apart). </div><div><br></div><div>I'd like to propose a change to the service names to facilitate this situation.</div><div><br></div><div><br></div><div>Option 1: Include Pulp version in Pulp 3 services</div><div><br></div><div>Example: pulp3-resource-manager</div><div><br></div><div>Pro: Explicit naming and understanding of new services.</div><div><br></div><div>Con: This locks services names to Pulp version, which will be odd with semantic versioning if 4 or 5 comes along.</div><div><br></div><div><br></div><div>Option 2: Re-name Pulp 2 services to pulp2-</div><div><br></div><div>Example: pulp2-resource-manager</div><div><br></div><div>Pro: Explicitly identifies pulp2 services, easy to retro-fit by users onto their setups or through RPM releases.</div><div><br></div><div>Con: Requires users to have upgraded to at least a particular Pulp2 version to migrate to Pulp 3 (this may be required anyway). </div></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>