May 2019 - dev - Rdo List Archives

Scheduled maintenance of review.rdoproject.org: 2019-06-05 23:00 UTC

by Nicolas Hicher

Hello folks, We plan to upgrade review.rdoproject.org on 2019-06-05 23:00 UTC. We don't expect any downtime during the upgrade process. First we have to upgrade softwarefactory-project.io to upgrade zuul to 3.8.1, then upgrade review.rdoproject.organd ansible.softwarefactory-project.io. Zuul 3.8supports ansible 2.5, 2.6 and 2.7, and after the upgrade, all job will be executed with ansible 2.7, but you could force ansible version on your job by adding in the job definition (note ansible 2.5 will be deprecated soon): - job: ansible-version: 2.5 Let us know if you prefer a different date. -Nicolas, on behalf of the ProdChainInfra Team

7 years

2
1
0 / 0

[ceph] Bringing Ceph to the Netherlands!

by Rain Leander

Come find out why leading enterprises are adopting Ceph, why Ceph is the lowest cost per gig storage solution, and how easy it is to deploy your own Ceph cluster! Event Description CFP is open until June 3rd. Please submit your presentation here. <https://zfrmz.com/E3ouYm0NiPF1b3NLBjJk> A full-day event dedicated to sharing Ceph’s transformative power and fostering the vibrant Ceph community, Ceph Day Netherlands is hosted by Utrecht Media Plaza, the Ceph community, and our friends. The expert Ceph team, Ceph’s customers and partners, and the Ceph community join forces to discuss things like the status of the Ceph project, recent Ceph project improvements and roadmap, and Ceph community news. The day ends with a networking reception, to foster more Ceph learning. -- K Rain Leander OpenStack Community Liaison Open Source Program Office https://www.rdoproject.org/ http://community.redhat.com

7 years

1
0
0 / 0

[Meeting] RDO Meeting (2019-05-29) minutes

by Alfredo Moralejo Alonso

============================== #rdo: RDO meeting - 2019-05-29 ============================== Meeting started by amoralej at 15:01:49 UTC. The full logs are available athttp://eavesdrop.openstack.org/meetings/rdo_meeting___2019_05_29/2019/r... . Meeting summary --------------- * roll call (amoralej, 15:02:00) * Planning for moving RDO Train to CentOS8 has started (amoralej, 15:04:37) * https://review.rdoproject.org/etherpad/p/moving-rdo-to-centos8 (amoralej, 15:04:44) * ACTION: amoralej to check upgrades plans with jistr after CentOS8 is in available (amoralej, 15:16:39) * LINK: https://etherpad.openstack.org/p/upgrades_denver_ptg (fultonj, 15:22:31) * RDO Status mail being sent weekly (amoralej, 15:28:59) * ACTION: amoralej to send RDO weekly status mail every monday morning CET time (amoralej, 15:34:20) * all OpenStack clients have been updated in Fedora Rawhide to Stein releases (amoralej, 15:35:24) * some packages have been removed from Fedora https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o... (amoralej, 15:37:12) * open floor (amoralej, 15:38:33) * ACTION: jpena to chair next week meeting (amoralej, 15:57:26) Meeting ended at 15:59:20 UTC. Action items, by person ----------------------- * amoralej * amoralej to check upgrades plans with jistr after CentOS8 is in available * amoralej to send RDO weekly status mail every monday morning CET time * jistr * amoralej to check upgrades plans with jistr after CentOS8 is in available * jpena * jpena to chair next week meeting People present (lines said) --------------------------- * amoralej (85) * ykarel (31) * jistr (14) * jpena (11) * fultonj (9) * baha (8) * mjturek (8) * openstack (6) Generated by `MeetBot`_ 0.1.4

7 years

1
0
0 / 0

[rdo-users] [Meeting] RDO meeting (2019-05-15) minutes

by YATIN KAREL

============================== #rdo: RDO meeting - 2019-05-15 ============================== Meeting started by ykarel at 15:01:10 UTC. The full logs are available athttp://eavesdrop.openstack.org/meetings/rdo_meeting___2019_05_15/2019/r... . Meeting summary --------------- * roll call (ykarel, 15:02:21) * [ykarel] LBaaS is being retired upstream in Train. We are also retiring it in RDO (ykarel, 15:07:36) * Open Discussion (ykarel, 15:13:40) * chair for next meeting (ykarel, 15:19:21) * ACTION: PagliaccisCloud to chair next week (ykarel, 15:22:14) Meeting ended at 15:23:31 UTC. Action items, by person ----------------------- * PagliaccisCloud * PagliaccisCloud to chair next week People present (lines said) --------------------------- * ykarel (27) * PagliaccisCloud (9) * openstack (6) * rdogerrit (1) * baha (1) * mjturek (1) Generated by `MeetBot`_ 0.1.4 _______________________________________________ users mailing list users(a)lists.rdoproject.org http://lists.rdoproject.org/mailman/listinfo/users To unsubscribe: users-unsubscribe(a)lists.rdoproject.org Regards Yatin Karel

7 years

1
0
0 / 0

Updating and retiring OpenStack packages from Fedora repositories

by Alfredo Moralejo Alonso

Hi, We have started working on synchronizing OpenStack clients from Stein release into Fedora rawhide official repos. The goal is not only updating it in fedora but also removing non required openstack packages on Fedora and automating the process as much as possible. An initial analysis of the packages that we can remove from Fedora shows that following ones can be safely retired: python-ceilometermiddleware python-keystonemiddleware python-os-win python-oslo-vmware python-oslo-sphinx python-pycadf python-oslo-cache python-cursive python-castellan python-oslo-rootwrap python-oslo-middleware python-oslo-policy python-oslo-reports python-oslo-privsep python-taskflow python-automaton python-microversion-parse python-reno python-osprofile python-oslo-messaging python-oslo-service python-oslo-concurrency I also have doubts about if we should maintain in Fedora: diskimage-builder python-hardware python-gnocchiclient Any opinion about it? I'm documenting the work related to this in https://review.rdoproject.org/etherpad/p/fedora-clients-sync If you have questions or think that retiring these packages from Fedora repos may cause any problem, please let me know on #rdo freenode channel or using RDO mailing lists. Best regards, Alfredo

7 years

4
5
0 / 0

Retiring neutron-lbaas and neutron-lbaas-dashboard

by Alfredo Moralejo Alonso

Hi, As explained in [1], Neutron LBaaS was deprecated in Queens and has been finally retired in Train [2]. Following this change, RDO will retire neutron-lbaas and neutron-lbaas-dashboard next weeks so anyone depending on them both from packaging or deployment side should get rid of it. To make transition smoother from RDO, we are pinning both projects to the last commit before removal and will keep the packages in RDO Trunk repos for some time (i'd say a couple of weeks) [3]. If anyone has any objection or question about this, please let us know in this mailing list or #rdo channel in freenode. Best regards, Alfredo [1] https://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation [2] https://review.opendev.org/#/q/topic:retire_neutron-lbaas+(status:open+OR... [3] https://review.rdoproject.org/r/#/c/20683/

7 years

1
0
0 / 0

[Meeting] RDO meeting (2019-05-08) minutes

by Javier Pena

============================== #rdo: RDO meeting - 2019-05-08 ============================== Meeting started by jpena at 15:00:31 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_05_08/2019/rdo... . Meeting summary --------------- * roll call (jpena, 15:00:36) * request to update to puppet 6 in RDO:- https://trello.com/c/isJkCzYZ (jpena, 15:05:29) * LINK: https://etherpad.openstack.org/p/RDO-Meeting (fultonj, 15:05:45) * puppet 6 will need to wait until centos 8 is available, can do some pre-work in Fedora (jpena, 15:06:43) * ACTION: ykarel to propose pr to update puppet in fedora (amoralej, 15:16:56) * ACTION: amoralej to update puppet in fedora stabilized repo once is built in fedora (amoralej, 15:17:19) * ceph/ansible post-update follow up (jpena, 15:18:33) * ppc64le container uploads (jpena, 15:30:30) * LINK: https://ci.centos.org/job/tripleo-upstream-containers-build-master-ppc64l... ? (amoralej, 15:32:03) * LINK: https://centos.logs.rdoproject.org/tripleo-upstream-containers-build-mast... is the most recent build log, for example (baha, 15:33:03) * LINK: https://trunk.rdoproject.org/centos7-master/deps/latest/ (ykarel, 15:37:52) * ACTION: jpena to check potential alternatives for the RDO registry (jpena, 16:15:44) * chair for the next meeting (jpena, 16:17:17) Meeting ended at 16:18:41 UTC. Action items, by person ----------------------- * amoralej * amoralej to update puppet in fedora stabilized repo once is built in fedora * jpena * jpena to check potential alternatives for the RDO registry * ykarel * ykarel to propose pr to update puppet in fedora People present (lines said) --------------------------- * amoralej (57) * jpena (52) * ykarel (32) * tonyb (19) * fultonj (18) * weshay (18) * mwhahaha (15) * baha (14) * fmount (7) * openstack (7) * Vorrtex (4) * rdogerrit (3) Generated by `MeetBot`_ 0.1.4

7 years, 1 month

1
0
0 / 0

[ptg] Interviews at PTG Denver

by Rain Leander

Hello all! I'm attending PTG this week to conduct project interviews [0]. These interviews have several purposes. Please consider all of the following when thinking about what you might want to say in your interview: * Tell the users/customers/press what you've been working on in Rocky * Give them some idea of what's (what might be?) coming in Stein * Put a human face on the OpenStack project and encourage new participants to join us * You're welcome to promote your company's involvement in OpenStack but we ask that you avoid any kind of product pitches or job recruitment In the interview I'll ask some leading questions and it'll go easier if you've given some thought to them ahead of time: * Who are you? (Your name, your employer, and the project(s) on which you are active.) * What did you accomplish in Rocky? (Focus on the 2-3 things that will be most interesting to cloud operators) * What do you expect to be the focus in Stein? (At the time of your interview, it's likely that the meetings will not yet have decided anything firm. That's ok.) * Anything further about the project(s) you work on or the OpenStack community in general. Finally, note that there are only 40 interview slots available, so please consider coordinating with your project to designate the people that you want to represent the project, so that we don't end up with 12 interview about Neutron, or whatever. I mean, love me some Neutron, but twelve interviews is a bit too many, eh? It's fine to have multiple people in one interview - Maximum 3, probably. Interview slots are 30 minutes, in which time we hope to capture somewhere between 10 and 20 minutes of content. It's fine to run shorter but 15 minutes is probably an ideal length. See you SOON! [0] https://docs.google.com/spreadsheets/d/1xZosqEL_iRI1Q-A5j-guRVh6Gc8-rRQ6S... -- K Rain Leander OpenStack Community Liaison Open Source and Standards Team https://www.rdoproject.org/ http://community.redhat.com

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

dev May 2019