On Mon, 11 Nov 2019, Alfredo Deza wrote: > The more we are looking into this, the more the dependency chain keeps growing. > > One thing I want to emphasize is the *tremendous* amount of > dependencies Ceph has, which makes this a non-trivial task. One > example of this, is that Ceph has a direct dependency on > **three** Python web frameworks: Cherrypy, Pecan, and Flask. > > We surely don't need three. I remember pushing for Pecan usage but > others liked Cherrypy more, and I guess some other group really liked > Flask so that is where we are today. > > This sort of dependency proliferation is a bug and it makes > maintaining the packages (and their dependencies) a consuming and > time-intensive task. > > The three web frameworks is one example, I am sure there are others. > How can we streamline, or reduce this? I did a git grep flask and don't see what is using that one... I don't see the dependency listed either? pecan is used by the restful module. I'm not sure we have many users there or what the long term future for that is.. it may be supplanted by the dashboard's API, in which case pecan could be dropped. OTOH, it's probably the easiest dependency to carry, right? :) sage > > On Thu, Nov 7, 2019 at 2:55 PM kefu chai <tchaikov@xxxxxxxxx> wrote: > > > > > > Le jeu. 7 nov. 2019 à 05:02, Alfredo Deza <adeza@xxxxxxxxxx> a écrit : > >> > >> On Wed, Nov 6, 2019 at 10:11 AM Sage Weil <sweil@xxxxxxxxxx> wrote: > >> > > >> > On Tue, 5 Nov 2019, Sage Weil wrote: > >> > > Hi everyone, > >> > > > >> > > The transition to python3-only is blocked on three missing python packages > >> > > in EPEL7: > >> > > > >> > > - python36-werkzeug: tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1545888 > >> > > - python36-pecan: tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1766839 > >> > > - python36-cherrypy: tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1765032 > >> > > > >> > > In order to get these into EPEL, they need to go into Fedora first, which > >> > > has its own (slow) process. In the meantime, these packages are easy to > >> > > build manually as one-offs (and may already have been built by David and > >> > > sitting in a temporary repo). > >> > > > >> > > To unblock this, what if we require that temporary repo for centos7 > >> > > *master* installs, and add it to the teuthology workers via > >> > > ceph-cm-ansible? The assumption is that by the time we release octopus we > >> > > will have gotten the dependencies in to the appropriate upstream repos. > >> > > That means we have until March 2020... 4 months away. > >> > > >> > Update: > >> > > >> > I just talked to Alfredo and the (current) blocker is cherrypy.. there are > >> > a zillion dependencies and the maintainer doesn't want to pull them in. > >> > > >> > So, the current plan is now to drop centos7 support for octopus. That > >> > should simplify things drastically! > >> > >> Quick update on this, we are working hard on trying to get cherrypy > >> fully available, and we made some progress yesterday. Being able to > > > > > > Alfredo, may I learn what progress it was? As I plan to build the python3-cherrypy package(s) on el7 to understand the efforts to ready its dependencies before moving on after returning home. So i am interested in where we are now. > > > >> > >> concentrate on EPEL8 (CentOS8) is going > >> to be a tremendous help. > >> > >> We will follow Sage's suggestion of getting the packages into a > >> self-hosted repo so that we don't have to wait (weeks!) for packages > >> to become available officially. > >> > > >> > sage > >> _______________________________________________ > >> Dev mailing list -- dev@xxxxxxx > >> To unsubscribe send an email to dev-leave@xxxxxxx > > > > -- > > Regards > > Kefu Chai > _______________________________________________ > Dev mailing list -- dev@xxxxxxx > To unsubscribe send an email to dev-leave@xxxxxxx >
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
