[rdo-list] Using rh-python35 Software Collection to package python service
by Tristan Cacqueray
Hello folks,
If I understood correctly, SCL (Software Collection) is the main Red Hat
supported solution to have py3 on el7 and el8, so I gave the rh-python35
collection a try to package the zuulv3 services. Here is how it went:
First I added scl-utils-build, rh-python35-build and rh-python35-runtime
to the koji target build groups so that a single buildroot could be used
for scl and non scl packages.
Then I wrote a pip2spec[0] script to render spec file for the 52 missing
dependencies[1]. It collects the sdist url, licence and the last version
of the pip requirements.txt, to render a valid scl spec file. I couldn't
use fedora specs or openstack renderspec because scl is quite intrusive:
* The spec defines only one package, regardless of the python runtime
* The %build, %install and %check section needs to be wrapped using
%{?scl:scl enable %{scl} - << \EOF}
...
%{?scl:EOF}
Lastly for the zuul package[2], this got a bit more tricky:
* The buildroot path are all offsetted with the scl prefix, the confmgmt
needed to be adapted to use the new paths:
/etc/opt/rh/rh-python35/zuul
/etc/opt/rh/rh-python35/sysconfig/zuul
/var/opt/rh/rh-python35/lib/zuul
/var/opt/rh/rh-python35/log/zuul
* The systemd service files also needed to be modified. I first tried to
use the scl command wrapper as documented in the guide, but this spawn
the service in a subprocess which breaks service reload (the SIGHUP is
not sent to the right process). Though a new sysconfig EnvironmentFile
is actually easier to activate the scl:
PATH=/opt/rh/rh-python35/root/usr/bin:/bin
LD_LIBRARY_PATH=/opt/rh/rh-python35/root/usr/lib64
* Finaly, the custom LD_LIBRARY_PATH is a blocker when the service calls
a setuid program. The zuul executor uses bubblewrap to contain Ansible
execution, and this failed with:
error while loading shared libraries: libpython3.5m.so.rh-python35-1.0
cannot open shared object file: No such file or directory
To fix that, I had to create symlink for the libpython3.5m.so* and the
python3.5 directory to /lib64/, which is not ideal because the scl now
affects system wide packages.
TL,DR:
Using SCL is quite an intrusive change, and unless we somehow remove the
scl path prefix, confmgmt needs to be modified to properly configure the
services. Moreover, the rh-python35 comes with a limited set of packages
and many dependencies will need to be packaged too.
Another alternative would be to package a system wide python3 runtime so
that we could keep the fedora spec compatibility, but that sounds like a
difficult path too.
Either way, we will likely lose all the packages that come for free with
the default centos python runtime. Though it may be possible to automate
most of the work to keep them in sync with the upper-constraints...
Best regards,
-Tristan
[0]: https://softwarefactory-project.io/paste/show/822/
[1]: https://softwarefactory-project.io/r/gitweb?p=config.git;a=blob_plain;f=r...
[2]: https://softwarefactory-project.io/r/gitweb?p=scl/zuul-distgit.git;a=tree
7 years, 4 months
Re: [rdo-list] Changes to log URLs for ci.centos.org and review.rdoproject.org (+thirdparty-logs.rdoproject.org)
by David Moreau Simard
Please note that "thirdparty-logs.rdoproject.org" has now been fully
migrated to our log aggregation server, logs.rdoproject.org.
Third party logs will continue to be available under
"thirdparty-logs.rdoproject.org" for backwards compatibility but,
moving forward, new logs should provide the link
"thirdparty.logs.rdoproject.org" instead.
For example:
- (Old) https://thirdparty-logs.rdoproject.org/jenkins-tq-gate-rhos-11-current-pa...
- (New) https://thirdparty.logs.rdoproject.org/jenkins-tq-gate-rhos-11-current-pa...
Let me know if you have any questions.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Wed, Jun 28, 2017 at 11:52 AM, David Moreau Simard <dms(a)redhat.com> wrote:
> Hi,
>
> Please note that log URLs for review.rdoproject.org and some jobs on
> ci.centos.org will soon change.
>
> ci.centos.org logs for weirdo jobs were already using
> logs.rdoproject.org -- this stays true but logs will now be folded
> under "centos.logs.rdoproject.org".
> If you happen to click a link from ci.centos.org that ends up broken
> on logs.rdoproject.org, try and see if the "centos" subdomain is
> missing.
>
> Regarding review.rdoproject.org, in preparation of migrating to the
> RDO cloud infrastructure, we will slowly start moving log aggregation
> from the Swift instance to logs.rdoproject.org.
>
> Right now, the link to the logs (to Swift) are available at the end of
> the Jenkins console log on review.rdoproject.org.
> While not very convenient, we will do the same thing for
> logs.rdoproject.org while we will figure out how to link directly to
> the logs from the gerrit review... hopefully in the near future.
>
> If you have any questions, please feel free to reach out to me.
>
> David Moreau Simard
> Senior Software Engineer | Openstack RDO
>
> dmsimard = [irc, github, twitter]
7 years, 4 months
[rdo-list] Renaming/Moving the mailing lists to @rdoproject.org
by Rich Bowen
It has been proposed that we move the mailing lists (there's three of
them - rdo-list, rdo-newsletter, and rdo-infra-list ) to @rdoproject.org
addresses, and, in the process, split rdo-list into dev(a)rdoproject.org
and users(a)rdoproject.org
The subscriber lists for newsletter and infra would simply be copied
over, since they are broadcast-only.
For the split from rdo-list to dev@ and users@, we would initially
simply copy the subscriber list to both of the new lists, and then
encourage people to unsubscribe from the one that they're not interested in.
The goal of the split is to make the users list more welcoming to
beginner/user type questions, while keeping the high technical level of
the existing dev list.
The goal of moving from @redhat.com is to reemphasize that this is not
just a Red Hat project, and encourage more participation from outside of
Red Hat.
There remains one important question holding up this migration, which is
what to do about the archives. We can:
1) Just leave them where they are now, and start fresh. This is easier,
but potentially "loses" history. (That is, it'll still be there, but
less obvious where to find it.)
2) Migrate all of the archives over to the new list. This is held up by
https://gitlab.com/mailman/hyperkitty/issues/144 which isn't getting a
lot of attention.
2.5) Migrate the archives and just be ok with losing some of the
messages? Doesn't seem ideal, but it's an option, and would get us
moving faster.
Please weigh in if you have an opinion.
--
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity
7 years, 4 months
[rdo-list] [Meeting] [Minutes] RDO meeting (2017-07-12) Minutes
by YATIN KAREL
==============================
#rdo: RDO meeting - 2017-07-12
==============================
Meeting started by ykarel at 15:00:20 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_07_12/2017/rdo...
.
Meeting summary
---------------
* Roll call (ykarel, 15:00:57)
* mass scratch rebuilds script [hguemar] (ykarel, 15:02:43)
* Reminder:
https://review.rdoproject.org/etherpad/p/rdo_low_hanging_fruits and
https://github.com/redhat-openstack/easyfix/issues for "nice to have"
or "easy fix" issues that are not getting addressed (ykarel,
15:08:14)
* Status of pike preparation (ykarel, 15:11:46)
* LINK:
https://trunk.rdoproject.org/centos7-pike-bootstrap/report.html
(amoralej, 15:12:30)
* ACTION: amoralej to check how hard/easy would be to implement
promotion pipeline with dlrn-api (amoralej, 15:20:42)
* Update of CBS automation (ykarel, 15:24:34)
* anyone can propose promotion of CBS tags by sending reviews to
rdoinfo, example https://review.rdoproject.org/r/#/c/7534/
(amoralej, 15:26:00)
* chair for next meeting (ykarel, 15:29:16)
* ACTION: amoralej to chair next meeting (ykarel, 15:29:54)
* open floor (ykarel, 15:30:03)
* LINK: http://ponymail.apache.org/ (rbowen, 15:36:52)
* ACTION: number80 help Duck with mailman3 package (number80,
15:44:27)
Meeting ended at 15:52:27 UTC.
Action items, by person
-----------------------
* amoralej
* amoralej to check how hard/easy would be to implement promotion
pipeline with dlrn-api
* amoralej to chair next meeting
* Duck
* number80 help Duck with mailman3 package
* number80
* number80 help Duck with mailman3 package
People present (lines said)
---------------------------
* amoralej (44)
* Duck (41)
* ykarel (32)
* apevec (32)
* dmsimard (26)
* rbowen (22)
* number80 (20)
* rdogerrit (8)
* openstack (8)
* chandankumar (5)
* jschlueter (2)
* PagliaccisCloud (1)
* rdobot (1)
* snecklifter (1)
Generated by `MeetBot`_ 0.1.4
------------------------------------------------
rdo-list mailing list
rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
7 years, 4 months
[rdo-list] Maintenance: logs.rdoproject.org July 11th 00:00UTC
by David Moreau Simard
Hi,
The logs.rdoproject.org server will undergo a brief maintenance on
July 11th at 00:00UTC (the night between monday and tuesday) for
updates and to bring it up to spec.
There will be brief periods of unavailability as at least one reboot
will be required.
Thanks,
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
7 years, 4 months
[rdo-list] Upcoming meetups, Monday, July 10
by Rich Bowen
The following are the meetups I'm aware of in the coming week where
OpenStack and/or RDO enthusiasts are likely to be present. If you know
of others, please let me know, and/or add them to
http://rdoproject.org/events
If there's a meetup in your area, please consider attending. If you
attend, please consider taking a few photos, and possibly even writing
up a brief summary of what was covered.
If you run a meetup, and are looking for speakers, sponsorship, or swag,
please get in touch with me a couple of weeks ahead of time, and we'll
work something out. Thanks!
--Rich
* Monday July 10 in Fort Collins, CO, US: Cloud Security, managing &
monitoring - https://www.meetup.com/OpenStack-Colorado/events/240675613/
* Tuesday July 11 in Ottawa, ON, CA: It's party time! OpenStack is
turning 7 - https://www.meetup.com/OpenStack-Ottawa/events/240646956/
* Wednesday July 12 in São Paulo, BR: 1° Meetup OpenStack Rio de Janeiro
no Parque Tecnológico UFRJ -
https://www.meetup.com/Openstack-Brasil/events/241193204/
* Wednesday July 12 in Edmonton, AB, CA: It's party time! OpenStack is
turning 7 - https://www.meetup.com/OpenStack-Edmonton/events/240647051/
* Wednesday July 12 in Perth, AU: OpenStack @ Pawsey Supercomputing
Centre - https://www.meetup.com/Perth-OpenStack-Meetup/events/241197865/
* Wednesday July 12 in Athens, GR: 7η επέτειος OpenStack project -
https://www.meetup.com/Athens-OpenStack-User-Group/events/240728736/
* Friday July 14 in Singapore, SG: Introduction - OpenStack powered by
EasyStack -
https://www.meetup.com/OpenStack-powered-by-EasyStack/events/241333537/
* Saturday July 15 in São Paulo, BR: OpenStack Day São Paulo 2017 -
https://www.meetup.com/Openstack-Brasil/events/239812022/
--
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity
7 years, 4 months
[rdo-list] Bootstrapping ppc64le packages
by Josh Boyer
Hello,
My name is Josh Boyer and I'm part of a team working on expanding
architecture support for Openstack. Our team is starting with ppc64le
but we have interest in aarch64 as well.
I'm looking to help bootstrap some of the missing dependency packages
for Pike on ppc64le. I've started with galera and done a successful
scratch build here:
https://cbs.centos.org/koji/taskinfo?taskID=189103
I spoke with Alan briefly and he suggested to build the -3 version
from Fedora master, but that added a dependency on asio-devel which is
also missing on ppc64le in CBS.
A successful scratch build of asio that includes ppc64le is here:
https://cbs.centos.org/koji/taskinfo?taskID=189119
but there is no newer version in Fedora, so the NVR is already present in CBS.
I'm happy to bump the Release in asio and build that, and then build
galera against it, but I thought I would bring the conversation here
before I did anything.
Thoughts?
josh
7 years, 4 months
[rdo-list] Webserver migration next Monday
by Marc Dequènes (Duck)
Quack,
Following what was decided during the RDO meeting the web server is
going to migrate from the dying OS1 to the brand new RDO Cloud. We just
finished preparing the move and, due to the deadline and some planned
vacations, we've decided to do it this next Monday (2017-07-10). It will
start at 12:30 JST and should not take long.
Impacted sites:
- www.rdoproject.org
- ask.rdoproject.org
- docs.rdoproject.org
- dashboards.rdoproject.org
The web builder will be switched to the new host beforehand, so you may
have some delay before changes are published effectively.
Also HTTPS will come once DNS has propagated and the let's encrypt
certificates are regenerated (due to some changes), so expect a short
delay here too.
We'll communicate via IRC, and here when this is over.
Have a nice we.
\_o<
7 years, 4 months
