15:00:29 <jpena> #startmeeting RDO meeting - 2019-06-12
15:00:31 <openstack> Meeting started Wed Jun 12 15:00:29 2019 UTC and is due to finish in 60 minutes.  The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:33 <jpena> #topic roll call
15:00:36 <openstack> The meeting name has been set to 'rdo_meeting___2019_06_12'
15:00:43 <jpena> Remember to add any last-minute topic to the agenda at https://etherpad.openstack.org/p/RDO-Meeting
15:00:45 <amoralej> o/
15:00:46 <ykarel> o/
15:00:55 <jpena> #chair amoralej ykarel
15:00:55 <openstack> Current chairs: amoralej jpena ykarel
15:02:39 <baha> o/
15:03:02 <mjturek> o/
15:03:09 <jpena> #chair baha mjturek
15:03:10 <openstack> Current chairs: amoralej baha jpena mjturek ykarel
15:03:51 <jpena> alright, let's start with the agenda
15:03:58 <jpena> #topic Pike is now extended maintenance, time for EOL in RDO
15:04:16 <jpena> amoralej, this is yours ^^
15:04:37 <amoralej> pike was moved to extended maintenance what means that there will be no new releases
15:04:59 <amoralej> although branches can remain opened in some projects
15:05:07 <amoralej> it's up to each project to maintain
15:05:25 <amoralej> so i'd propose to just take it as an EOL from RDO side
15:05:28 <amoralej> as we did for ocata
15:05:40 <amoralej> just, keep the DLRN builder running
15:05:54 <jpena> I'm fine with that
15:05:58 <amoralej> but remove jobs, and references to cloudsig repos
15:06:18 <amoralej> and iirc, when centos-7.7 is published we can retire it
15:06:31 <ykarel> amoralej, with jobs means u mean just cloudsig jobs or also tripleo promotion and upstream jobs also?
15:07:00 <amoralej> well, it's up to them, tbh
15:07:13 <amoralej> as the consume RDO Trunk
15:07:27 <ykarel> yes i asked because i saw some recent changes to stable/pike
15:07:27 <amoralej> i'll send a mail for users
15:07:56 <amoralej> yes, some projects may decide to maintain it with some gating
15:08:19 <amoralej> and if tripleo considers useful to keep promotion pipeline working for it
15:08:42 <amoralej> no problem from my side, i'm afraid that at some point some projects may break
15:09:32 <amoralej> just one to alert other users or operators cloudsig repo is no longer maintained
15:09:54 <amoralej> #action amoralej to send a mail about Pike CloudSIG repos being EOL
15:10:08 <ykarel> yes, for TripleO side, it would be TripleO says pike is unmaintained, then next step would be clearing upstream and promotion jobs
15:10:19 <ykarel> cloudsig can be cleared as there will be no more releases
15:12:04 <jpena> shall we move on to the next topic?
15:12:09 <amoralej> we can also remove pike from all the bots, updating from u-c, automatic promotions to -testing, etc...
15:12:13 <amoralej> ykarel, ^
15:12:37 <ykarel> amoralej, yes
15:13:09 <amoralej> #info tracking pike removal in https://trello.com/c/6e0bVGzK/712-pike-is-em-removal-from-rdo
15:13:28 <amoralej> let's add what we need to do there
15:13:34 <ykarel> ack
15:13:42 <amoralej> jpena, yeah, we can mov on
15:13:58 <jpena> good
15:14:02 <jpena> #topic altarch container discussion
15:14:09 <mjturek> hey!
15:14:22 <mjturek> a  few things to bring up
15:14:49 <mjturek> 1) a patch is up that tags the containers for registry.rdoproject.org https://review.rdoproject.org/r/#/c/20974/
15:15:08 <mjturek> reviews are appreciated
15:15:12 <mjturek> the intent is to have a tag that is <version_hash>_ppc64le
15:15:33 <mjturek> these would be in the same namespace as containers that are <version_hash>
15:15:49 <mjturek> (the ones that are <version_hash> being x86_64 containers)
15:16:18 <mjturek> upon  promotion, the arch portion of the tag would be removed, a manifest would  be created, and we'd upload to dockerhub
15:16:22 <mjturek> all sounding sane?
15:16:27 <ykarel> jpena, may be we may need some storage for ^^ new containres, is that already considered
15:16:52 <jpena> ykarel: yes, we took that into account last time we upgraded storage for registry.rdo
15:17:00 <ykarel> okk cool
15:17:08 * jpena crosses fingers
15:17:34 <jpena> mjturek: that sounds ok to me
15:17:39 <mjturek> 2) jpena has a patch up for adding registry credentials to cico https://review.rdoproject.org/r/#/c/20974/
15:17:50 <mjturek> hasn't moved in a bit so reviews would be appreciated
15:18:04 <mjturek> however, jpena mentioned that there may be a path forward in the meantime
15:18:13 <mjturek> jpena could you elaborate on that?
15:18:32 <jpena> mjturek: yes. While it gets merged, you can work as if it was already. I've manually added that env var to the different jenkins machines
15:18:49 <mjturek> ahhhhhh understood
15:18:52 <jpena> so merging the review will just make things "right" :)
15:18:53 <mjturek> thank you jpena
15:19:08 <mjturek> that makes sense :)
15:19:14 <mjturek> okay I'm good! baha you have anything here?
15:19:29 <ykarel> mjturek, so these containers would be pushed as part of TripleO promotion? will u be adding some jobs as well to test these built containers?
15:19:42 <baha> mjturek: Nope! I'm good
15:19:50 <mjturek> ykarel - we're unclear if that's in our hands or our partners at redhat's
15:19:57 <mjturek> but there will be some minimal testing to start
15:20:09 <ykarel> as i see u running those in ci.centos while tripleo promotion jobs are running in zuul, so u would need some sort of sync
15:20:24 <mjturek> yeah we need to sync up with weshay on that
15:20:28 <ykarel> building containers with same hash
15:20:32 <ykarel> okk good
15:21:29 <amoralej> in rdoinfo we launch jobs in ci.centos.org from jobs in zuul
15:21:38 <amoralej> using a jenkins api token
15:22:12 <amoralej> i'm not sure if the same could be done from a job in the periodic pipeline to create containers for ppc64le
15:22:57 <amoralej> it's kind of hack, but could be useful
15:23:06 <mjturek> amoralej: what about just building daily for now?
15:23:08 <mjturek> is that too often?
15:23:20 <amoralej> no, no
15:23:46 <amoralej> but i understood you need to sync somehow to the jobs running in promotion pipeline
15:23:56 <mjturek> ahhhh right
15:24:17 <amoralej> if just using any of the hashes marked for testing by periodic pipeline is fine for you
15:24:35 <amoralej> then probably you can just use the tripleo-ci-testing symlink
15:24:35 <mjturek> got it
15:24:38 <amoralej> at any time
15:25:13 <mjturek> okay - baha and I will  talk to tripleo folks this week and see what's up
15:25:18 <amoralej> sure
15:27:10 <jpena> next topic?
15:27:15 <mjturek> +1
15:27:40 <jpena> #topic New release of python-sqlalchemy-collectd requires collectd subpackage which is included in opstools
15:28:06 <amoralej> yeah, i was discussing this with mrunge before the meeting
15:28:53 <amoralej> so, while trying to update python-sqlalchemy-collectd to 0.0.4 we hit an issue because it depends on a collectd subpackage which is in opstools, not in rdo
15:29:18 <amoralej> so we were thinking where this package should be, RDO or OpsTools
15:29:39 <amoralej> in any case it will make one to depend on the other
15:29:55 <amoralej> RDO on OpsTools for collectd
15:30:12 <jpena> which packages depend on python-sqlalchemy-collectd?
15:30:13 <ykarel> what needs python-sqlalchemy-collectd
15:30:13 <amoralej> or OpsTools on RDO for python-sqlalchemy, as the version of sqlalchemy in base is too low
15:30:32 <amoralej> ykarel, functional dependency for kolla
15:30:40 <amoralej> to send metrics to collectd
15:30:45 <amoralej> let me look for it
15:30:51 <mrunge> kolla requires both
15:31:22 <mrunge> at least for the collectd container, it used to require centos-opstools
15:31:25 <amoralej> https://review.opendev.org/#/c/659678/
15:31:29 <mrunge> not sure how that is today
15:31:58 <amoralej> mrunge, yes, by today, i'd say that kolla is adding both rdo and opstools in every container build
15:32:09 <amoralej> so i'd say we are safe in that side
15:32:45 <amoralej> i'd say that the main topic here is if python-sqlalchemy-collectd is a pure openstack thing or can be used in others places where opstools are used
15:33:36 <mrunge> it is useful in other places as well, making it probably an opstools thing
15:33:52 <mrunge> I hate to say it, as that will make us add sqlalchemy as well
15:34:20 <amoralej> mrunge, you can crosstag from RDO's build
15:34:24 <mrunge> yes
15:34:39 * amoralej crosses fingers to not break anything
15:34:50 <mrunge> same as for qpid?
15:34:57 <amoralej> yep
15:35:09 <mrunge> we now have the messaging sig
15:35:09 <amoralej> last time for qpid we didn't break :)
15:35:10 <ykarel> so if it's mainly needed by collectd containers, so good to start with adding it to opstools repo
15:35:14 <mrunge> (a year after)
15:35:16 <ykarel> as that seems the primary consumer
15:35:29 <mrunge> ykarel: we have collectd-mysql
15:35:48 <mrunge> no real need for python-sqlalchemy-collectd
15:35:54 <amoralej> ykarel, look at https://review.opendev.org/#/c/659678/ will be added in all of them
15:36:04 * ykarel looks
15:36:13 <amoralej> mrunge, explanation from https://review.opendev.org/#/c/629916/ is
15:36:20 <amoralej> "This allows monitoring of SQLAlchemy connection pool usage."
15:36:47 <amoralej> not sure if collectd-mysql or others can do an equivalent thing
15:36:49 <amoralej> zzzeek, ^
15:36:53 <ykarel> ohhk it's for python-sqlalchemy, so openstack need
15:37:09 <mrunge> collectd-mysql can not do that
15:37:35 <zzzeek> amoralej: hi
15:37:43 <amoralej> mrunge, do you want me to take any action to move on with this?
15:37:48 <zzzeek> mrunge: what are you looking to accomplish
15:37:51 <amoralej> mail somewhere? bz?
15:38:05 <zzzeek> oh....OK
15:38:15 <amoralej> zzzeek, we are thinking in moving python-sqlalchemy-collectd from RDO to OpsTools repo
15:38:31 <zzzeek> python-sqlalchemy-collectd is a thing anywhere somethign that uses SQLAlchemy which is also a rhel package AFAIK might be used
15:38:33 <amoralej> both are consumed by kolla and tripleo
15:39:04 <zzzeek> basically anything that has both sqlalhcemy and collectd available in its scope woudl probably want this too
15:39:08 <amoralej> zzzeek, sqlalchemy in rhel base is 0.9.4 while python-sqlalchemy-collectd requires >= 1.1.0 iirc
15:39:24 <zzzeek> amoralej: rhel8 is 0.9.4 ?
15:39:29 <zzzeek> that woudl be...weird?
15:39:33 <amoralej> zzzeek, we are in centos7 :)
15:39:38 <amoralej> no centos8 yet
15:39:42 <zzzeek> amoralej: ah
15:39:50 <zzzeek> amoralej: then no, you don't need this yet :)
15:40:08 <zzzeek> amoralej: id say it's a centos8 thing
15:40:41 <amoralej> https://review.opendev.org/#/c/659678/ is running with centos7 so we need to provide it
15:40:59 <amoralej> btw, zzzeek version 0.0.3 could be good?
15:41:14 <zzzeek> amoralej: for sqlalchemy-collectd?  0.0.4 is way better :)
15:41:18 <amoralej> 0.0.4 was the one that introduced the requirement on collectd-python
15:41:19 <amoralej> ok
15:41:21 <zzzeek> it's all alpha so it's in deep flux
15:41:26 <amoralej> then we need to manage this
15:44:08 <amoralej> I'll follow up with mrunge about next steps
15:45:03 <amoralej> #action amoralej to follow-up with mrunge about the topic
15:45:58 <jpena> #topic Next week's chair
15:46:06 <jpena> Do we have any volunteer?
15:47:08 <ykarel> i can take it
15:47:29 <jpena> #action ykarel to chair the next meeting
15:47:31 <jpena> thanks ykarel!
15:47:36 <jpena> #topic open floor
15:47:44 <jpena> If there's anything else to discuss, this is the right time
15:48:29 <amoralej> we'll need to start syncing with other sigs about CentOS8 stuff
15:48:46 <amoralej> gfidente, ^ do you have any plan for CentOS8?
15:49:03 <amoralej> plan to rebuild nautilus for centos8 once is available?
15:49:23 <gfidente> amoralej yeah I think we should do that
15:49:30 <mriosfer> :D
15:49:37 <amoralej> ack, those are good news for us :)
15:50:11 <amoralej> gfidente, fyi we plan to release RDO Train on CentOS8, so we'll depend on StorageSIG nautilus builds somehow
15:50:32 <gfidente> amoralej yeah got it
15:51:03 <amoralej> ok
15:51:47 <amoralej> this was it from me jpena
15:52:26 <jpena> anything else?
15:52:37 <jpena> If not, we'll get 5 minutes back for coffee (or tea)
15:54:05 <apevec> or Irish coffee
15:54:37 <jpena> in my case it will be horchata
15:54:41 <jpena> but I digress :)
15:54:45 <amoralej> horchata lol
15:54:56 <jpena> #endmeeting