<html><body>
<p><tt><font size="2">> From: Flavio Percoco <flavio@redhat.com></font></tt><br>
<tt><font size="2">> To: "OpenStack Development Mailing List (not for usage questions)" <br>
> <openstack-dev@lists.openstack.org></font></tt><br>
<tt><font size="2">> Date: 07/28/2015 07:36 AM</font></tt><br>
<tt><font size="2">> Subject: Re: [openstack-dev] [glance] Removing python-swiftclient <br>
> from requirements.txt</font></tt><br>
<tt><font size="2">> <br>
> On 28/07/15 09:15 +0000, Kuvaja, Erno wrote:<br>
> >I do agree, we don’t depend or are cleaning the other clients out <br>
> of the glance<br>
> >dependencies as well and I think swift should not be there either.<br>
> ><br>
> > <br>
> ><br>
> >The default store is filesystem store and if something is depending on the<br>
> >actual store clients it should be either glance_store or deployer (well for<br>
> >example our gate) glance itself should not have hard dependencies for ‘em.<br>
> <br>
> Agreed!<br>
> <br>
> William, would it be possible for you to spend some more time and<br>
> create a single patch that removes all non-required dependencies?<br>
> <br>
> Cheers,<br>
> Flavio<br>
> </font></tt><br>
<br>
<tt><font size="2">This all started when I opened a bug [1] saying we needed to pull out oslo.vmware. Louis quickly threw up a patch [2] to remove that, but it was pointed out that swiftclient falls into the same category. So I created a separate patch to remove swiftclient [3]. Looking over what else is in requirements.txt and running a few searches, it looks like we may also be able to remove greenlet, kombu, and posix-ipc. Does anyone know if any of those (greenlet?) are needed for some reason other than a direct import? In which case I can add a comment to clarify that while I'm removing the others.</font></tt><br>
<br>
<tt><font size="2">I'd originally included the removal of oslo.vmware in [3], but I pulled that out thinking we could go ahead and merge [2] while we were having this discussion. But that didn't seem to fly, so I guess we want to make all these changes together under [3] and abandon [2]? Or should we go ahead and merge [2] while we're figuring out whether to remove greenlet, kombu, and posix-ipc as well under [3]?</font></tt><br>
<br>
<tt><font size="2">Just to be clear, it sounds to me like Flavio and Erno agree we should pull swiftclient out of requirements.txt immediately. I'd like to see a reply from Ian and Louis to round things out, make sure we're all on the same page and we won't be fighting over this in the review...</font></tt><br>
<br>
<tt><font size="2">[1] </font></tt><a href="https://launchpad.net/bugs/1475737"><tt><font size="2">https://launchpad.net/bugs/1475737</font></tt></a><br>
<tt><font size="2">[2] </font></tt><a href="https://review.openstack.org/#/c/203200/"><tt><font size="2">https://review.openstack.org/#/c/203200/</font></tt></a><br>
<tt><font size="2">[3] </font></tt><a href="https://review.openstack.org/#/c/203242/"><tt><font size="2">https://review.openstack.org/#/c/203242/</font></tt></a><br>
<tt><font size="2"><br>
> ><br>
> > <br>
> ><br>
> >- Erno<br>
> ><br>
> > <br>
> ><br>
> >From: William M Edmonds [<a href="mailto:edmondsw@us.ibm.com">mailto:edmondsw@us.ibm.com</a>]<br>
> >Sent: Monday, July 27, 2015 10:42 PM<br>
> >To: openstack-dev@lists.openstack.org<br>
> >Subject: [openstack-dev] [glance] Removing python-swiftclient from<br>
> >requirements.txt<br>
> ><br>
> > <br>
> ><br>
> >python-swiftclient is only needed by operators that are using the swift<br>
> >backend, so it really doesn't belong in requirements.txt. Listing it in<br>
> >requirements forces all operators to install it, even if they're not going to<br>
> >use the swift backend. When I proposed a change [1] to move this from<br>
> >requirements to test-requirements (would still be needed there <br>
> because of tests<br>
> >using the swift backend), others raised concerns about the impact this could<br>
> >have on operators who use the swift backend today and would be upgrading to<br>
> >Liberty. I believe everyone agreed this should not be in <br>
> requirements, but the<br>
> >fact is that it has been, so operators may have (incorrectly) been <br>
> depending on<br>
> >that during upgrades. If we remove it in Liberty, and there are changes in<br>
> >Liberty that require a newer version of swiftclient, how would <br>
> those operators<br>
> >know that they need to upgrade swiftclient?<br>
> ><br>
> >The optional dependencies spec [2] could definitely help here. I <br>
> don't think we<br>
> >should have to wait for that, though. This is an issue we obviously already<br>
> >have today for other backends, which indicates folks can deal with it without<br>
> >an optional dependencies implementation.<br>
> ><br>
> >This would be a new concern for operators using the default swift backend,<br>
> >though. So how do we get the message out to those operators? And dowe need to<br>
> >put out a message about this change in Liberty and then wait until Mitaka to<br>
> >actually remove this, or can we go ahead and remove in Liberty?<br>
> ><br>
> >[1] <a href="https://review.openstack.org/#/c/203242">https://review.openstack.org/#/c/203242</a><br>
> >[2] <a href="http://specs.openstack.org/openstack/oslo-specs/specs/liberty/">http://specs.openstack.org/openstack/oslo-specs/specs/liberty/</a><br>
> >optional-deps.html<br>
> ><br>
> >-Matthew<br>
> ><br>
> <br>
> >__________________________________________________________________________<br>
> >OpenStack Development Mailing List (not for usage questions)<br>
> >Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
> ><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <br>
> <br>
> -- <br>
> @flaper87<br>
> Flavio Percoco<br>
> [attachment "attdy18a.dat" deleted by William M Edmonds/Raleigh/IBM]<br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></tt></body></html>