Re: unblocking the py3 transition

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 8, 2019 at 5:09 AM Jan Fajerski <jfajerski@xxxxxxxx> wrote:
>
> On Thu, Nov 07, 2019 at 08:02:07AM -0500, Alfredo Deza wrote:
> >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
> >concentrate on EPEL8 (CentOS8) is going
> >to be a tremendous help.
> The ceph-volume's (vagrant based) functional tests currently rely a lot on
> centos7 (at least in name, seem like the tests actually download Fedora 22?).

All the tests use official Centos7 machines coming directly from the
centos group in Vagrantcloud:

https://github.com/ceph/ceph/blob/master/src/ceph-volume/ceph_volume/tests/functional/lvm/centos7/bluestore/create/vagrant_variables.yml#L42

Nothing uses Fedora.

> While I'd like to replace this testing infrastructure at some point, it works
> for now and its probably better to move them from Centos7/Fedora22 to Centos8/?.
> However there don't seem to be Centos8 vagrant images. Any pointers as to what
> to use instead?

Like Ken pointed out, the official image is not there yet, once it is
I think we can switch to it. There are community-based images (I
created the bionic ones we use), so that is always
a possibility if there is an urgent need.

> >
> >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
>
> --
> Jan Fajerski
> Senior Software Engineer Enterprise Storage
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx




[Index of Archives]     [CEPH Users]     [Ceph Devel]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux