Hello Shilpa, Thank you for the links provided. To summarize it, they show how to setup a corrosync + pacemaker cluster in action. However, I have to ask for more details on the broader picture. From the scraps I found about masakari-host-monitor and the limitations of the pacemaker/corrosync installations (limited to 16 nodes, there is a specification detailing this somewhere, etc.) I wonder if another solution is actually intended. To give you a better insight where I am atm at: I found that pacemaker-remote (no need for corrosync) should be favored on the nova compute nodes (Someone said so somewhere, maybe Pushkar), because it scales better. This then would presume a pacemaker + corrosync cluster existing to work somewhere else, because pacemaker-remote can't live without (as far as I know). The pacemaker + corrosync cluster does only need to exist without further operational relevance for masakari-host-monitor, though. Having the lxc-container based setup openstack-ansible produces in mind, the setup would then look like: - 3 masakari containers (like os_masakari-install.yaml from OSA already delivers) being extended with the pacemaker + corrosync cluster - n compute nodes with pacemaker-remote installed and configured (to join the preexisting pacemaker + corrosync cluster residing on the masakari-containers) - all the containers and compute nodes talk via the regular management network to each other - adding new compute nodes means only having a local configuration on exactly that new node. There is no need to change configuration on any other part of the system (because pacemaker-remote manages the population of the existence of the new resource). Is this where masakaris pacemaker-based setup would develop to or did I get it completely wrong? Best regards, Ralf -----Ursprüngliche Nachricht----- Von: Devharakar, Shilpa <Shilpa.Devharakar@nttdata.com> Gesendet: Dienstag, 20. August 2019 13:53 An: openstack-discuss@lists.openstack.org Betreff: RE: [masakari] pacemaker-remote Setup Overview Hi Ralf Teckelmann, Sorry for the attachment, instead please refer [1] Masakari team is in process of 'adding devstack support to install host-monitor', please refer community patch [2]. You can refer 'devstack/plugin.sh' [1]: https://urldefense.proofpoint.com/v2/url?u=http-3A__paste.openstack.org_show_760301_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=BT_bkEAenK5jBZ--5hTVqt0GZq12Ij9-q7qGTn86rvk&e= [2]: https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_671200_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=y0pr15KIaa1XPwej0egzCp7mPGDKBLhxN7fhJMDeywM&e=
Hi Ralf Teckelmann,
Sorry resending by correcting subject with appropriate subject.
Thanks with Regards, Shilpa Shivaji Devharakar| Software Development Supervisor | NTT DATA Services| w. 91-020- 67095703 | Shilpa.Devharakar@nttdata.com | Learn more at nttdata.com/americas -----Original Message----- From: openstack-discuss-request@lists.openstack.org <openstack-discuss-request@lists.openstack.org> Sent: Monday, August 19, 2019 10:19 PM To: openstack-discuss@lists.openstack.org Subject: openstack-discuss Digest, Vol 10, Issue 94 Send openstack-discuss mailing list submissions to openstack-discuss@lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddiscuss&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=zXtwRY6Jm3E4Jt2ihjpRJZ8VIwFdTMcuMg0A7eJ9XYA&e= or, via email, send a message with subject or body 'help' to openstack-discuss-request@lists.openstack.org You can reach the person managing the list at openstack-discuss-owner@lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. [tc] weekly update (Mohammed Naser) 2. RE: [masakari] pacemaker-remote Setup Overview (Devharakar, Shilpa) 3. Re: [tc] weekly update (Andreas Jaeger) 4. Re: [all] [tc] [docs] [release] [ptls] Docs as SIG: Ownership of docs.openstack.org (Doug Hellmann) ---------------------------------------------------------------------- Message: 1 Date: Mon, 19 Aug 2019 12:26:48 -0400 From: Mohammed Naser <mnaser@vexxhost.com> To: OpenStack Discuss <openstack-discuss@lists.openstack.org> Subject: [tc] weekly update Message-ID: <CAEs876hqf-R4r9+LZcVbPPLJMEHTs=tPBztJtGqO8-oZvEXLcg@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi everyone, Here’s the update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # Retired projects - Networking-generic-switch-tempest (from networking-generic-switch): https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_674430_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=u1TtWtLxQw9wq6IOi2bbDXtaLl4zt5J-5ckqAjh-5iE&e= # General changes - Michał Dulko as Kuryr PTL: https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_674624_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=KLNfBuQ1X6WkQzI9yyVScUlkVFw91KTNz8ySzC2SK4I&e= - Added a mission to Swift taken from its wiki: https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_675307_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=eZFduAqetS5dHRgx2V93U7dqTvoACzz45DKc2p1tlPI&e= - Sean McGinnis as release PTL: https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_675246_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=1Q2nQef0P-85E1K0QM5nGAtO3BYo8Y3zuMR_XC6L2f0&e= Thanks for tuning in! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. https://urldefense.proofpoint.com/v2/url?u=http-3A__vexxhost.com&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=HxEHZ8J4B5M1r4rAsOa1R9MqRDH-RE3gr663kc2dbVU&e= ------------------------------ Message: 2 Date: Mon, 19 Aug 2019 16:34:26 +0000 From: "Devharakar, Shilpa" <Shilpa.Devharakar@nttdata.com> To: "openstack-discuss@lists.openstack.org" <openstack-discuss@lists.openstack.org> Subject: RE: [masakari] pacemaker-remote Setup Overview Message-ID: <CH2PR12MB4072764F39DDD35C4A8ED158FFA80@CH2PR12MB4072.namprd12.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Hi Ralf Teckelmann, Sorry resending by correcting subject with appropriate subject.
Hello,
Utilizing openstack-ansible we successfully installed all the masakari services. Besides masakari-hostmonitor all are running fine. For the hostmonitor a pacemaker cluster is missing.
Can anyone give me an overview how the pacemaker cluster setup would look like? Which (pacemaker) services is running where (compute nodes, something on any other node,...), etc?
Best regards,
Ralf Teckelmann
Sorry for the late answer... Masakari team is in process of 'adding devstack support to install host-monitor', please refer community patch [1]. You can refer 'devstack/plugin.sh', please note it has IPMI Hardware support dependency. Also PFA 'detailed_steps_on_ubuntu_for_pacemaker_verification.txt' for verification of same carried out on Ubuntu distribution (installed openstack using devstack with Masakari enabled). [1]: https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_671200_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=y0pr15KIaa1XPwej0egzCp7mPGDKBLhxN7fhJMDeywM&e= Add devstack support to install host-monitor Thanks with Regards, Shilpa Shivaji Devharakar| Software Development Supervisor | NTT DATA Services| w. 91-020- 67095703 | Shilpa.Devharakar@nttdata.com | Learn more at nttdata.com/americas -----Original Message----- From: openstack-discuss-request@lists.openstack.org <openstack-discuss-request@lists.openstack.org> Sent: Monday, August 12, 2019 6:30 PM To: openstack-discuss@lists.openstack.org Subject: openstack-discuss Digest, Vol 10, Issue 59 Send openstack-discuss mailing list submissions to openstack-discuss@lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddiscuss&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=zXtwRY6Jm3E4Jt2ihjpRJZ8VIwFdTMcuMg0A7eJ9XYA&e= or, via email, send a message with subject or body 'help' to openstack-discuss-request@lists.openstack.org You can reach the person managing the list at openstack-discuss-owner@lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: [tripleo][openstack-ansible] Integrating ansible-role-collect-logs in OSA (Arx Cruz) 2. [swauth][swift] Retiring swauth (Ondrej Novy) 3. [ironic] Resuming having weekly meetings (Julia Kreger) 4. [masakari] pacemaker-remote Setup Overview (Teckelmann, Ralf, NMU-OIP) ---------------------------------------------------------------------- Message: 1 Date: Mon, 12 Aug 2019 12:32:34 +0200 From: Arx Cruz <arxcruz@redhat.com> To: Jean-Philippe Evrard <jean-philippe@evrard.me> Cc: openstack-discuss@lists.openstack.org Subject: Re: [tripleo][openstack-ansible] Integrating ansible-role-collect-logs in OSA Message-ID: <CAB27Hy1tB0TjEwsvrgeBUF1NFCzDadE58-VR68Qt_=3RKY+fVw@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello, I've started to split the logs collection tasks in small tasks [1] in order to allow other users to choose what exactly they want to collect. For example, if you don't need the openstack information, or if you don't care about networking, etc. Please take a look. I'll also add it on the OSA agenda for tomorrow's meeting. Kind regards, 1 - https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_675858_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=9Ug8vtvllesG65u1zM2vPSsXJH5ti5SXEREhqcY0yQc&e= On Mon, Jul 22, 2019 at 8:44 AM Jean-Philippe Evrard < jean-philippe@evrard.me> wrote:
Sorry for the late answer...
On Wed, 2019-07-10 at 12:12 -0600, Wesley Hayutin wrote:
These are of course just passed in as extra-config. I think each project would want to define their own list of files and maintain it in their own project. WDYT?
Looks good. We can either clean up the defaults, or OSA can just override the defaults, and it would be good enough. I would say that this can still be improved later, after OSA has started using the role too.
It simple enough. But I am happy to see a different approach.
Simple is good!
Any thoughts on additional work that I am not seeing?
None :)
Thanks for responding! I know our team is very excited about the continued collaboration with other upstream projects, so thanks!!
Likewise. Let's reduce tech debt/maintain more code together!
Regards, Jean-Philippe Evrard (evrardjp)
-- Arx Cruz Software Engineer Red Hat EMEA <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=9fthTRCwXnDdzfGnZjUnruRIF0_M0lBiU-Km1_yvqW0&e=> arxcruz@redhat.com @RedHat <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_redhat&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=9bVQh287vYpOKj1zeON_O1ptGLaA9_4TSnIOtTU-oj0&e=> Red Hat <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_red-2Dhat&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=BGPIwp44wmhrC3jMoNkeg10PgA0Rrs7ArToj84yM0oE&e=> Red Hat <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_RedHatInc&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=j9BJvvvSSE2OHcQxAJKNxSG9XF73Z8diAy3RX_HKdjM&e=> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=9fthTRCwXnDdzfGnZjUnruRIF0_M0lBiU-Km1_yvqW0&e=> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Ddiscuss_attachments_20190812_f8492593_attachment-2D0001.html&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=yPrsxJd_tvwRqwudYfjeXxyHPpdTSi6D_QFjreDArEM&e=> ------------------------------ Message: 2 Date: Mon, 12 Aug 2019 12:56:15 +0200 From: Ondrej Novy <novy@ondrej.org> To: openstack-discuss@lists.openstack.org Subject: [swauth][swift] Retiring swauth Message-ID: <CAOO6c=wgDZDRpQboo=_0qZ=fHrfu0rO0w=PaUat9bJduwFiVXw@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, because swauth is not compatible with current Swift, doesn't support Python 3, I don't have time to maintain it and my employer is not interested in swauth, I'm going to retire swauth project. If nobody take over it, I will start removing swauth from opendev on 08/24. Thanks. -- Best regards Ondřej Nový -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Ddiscuss_attachments_20190812_28f563f9_attachment-2D0001.html&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=XRVtgYz3BDJVsjdFsahT3urm29tWmIaoxXEbLaLoaS8&e=> ------------------------------ Message: 3 Date: Mon, 12 Aug 2019 07:55:07 -0400 From: Julia Kreger <juliaashleykreger@gmail.com> To: openstack-discuss <openstack-discuss@lists.openstack.org> Subject: [ironic] Resuming having weekly meetings Message-ID: <CAF7gwdhSWcUbYu0S2QfvjO44Q_5vJr6KTUQE3TRu3UYirqFGmQ@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" All, I meant to send this specific email last week, but got distracted and $life. I believe we need to go back to having weekly meetings. The couple times I floated this in the past two weeks, there hasn't seemed to be any objections, but I also did not perceive any real thoughts on the subject. While the concept and use of office hours has seemingly helped bring some more activity to our IRC channel, we don't have a check-point/sync-up mechanism without an explicit meeting. With that being said, I'm going to start the meeting today and if we have quorum, try to proceed with it today. -Julia ------------------------------ Message: 4 Date: Mon, 12 Aug 2019 12:59:20 +0000 From: "Teckelmann, Ralf, NMU-OIP" <ralf.teckelmann@bertelsmann.de> To: "openstack-discuss@lists.openstack.org" <openstack-discuss@lists.openstack.org> Subject: [masakari] pacemaker-remote Setup Overview Message-ID: <AM6PR04MB47112DF6617442709662B43389D30@AM6PR04MB4711.eurprd04.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Hello, Utilizing openstack-ansible we successfully installed all the masakari services. Besides masakari-hostmonitor all are running fine. For the hostmonitor a pacemaker cluster is missing. Can anyone give me an overview how the pacemaker cluster setup would look like? Which (pacemaker) services is running where (compute nodes, something on any other node,...), etc? Best regards, Ralf Teckelmann -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Ddiscuss_attachments_20190812_e0e36e53_attachment.html&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=LfDCiMW3b3f7og_yLyWiIMY8dG3T_B2ZRjPg75jGTrE&e=> ------------------------------ Subject: Digest Footer _______________________________________________ openstack-discuss mailing list openstack-discuss@lists.openstack.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddiscuss&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=zXtwRY6Jm3E4Jt2ihjpRJZ8VIwFdTMcuMg0A7eJ9XYA&e= ------------------------------ End of openstack-discuss Digest, Vol 10, Issue 59 ************************************************* Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. ------------------------------ Message: 3 Date: Mon, 19 Aug 2019 18:36:01 +0200 From: Andreas Jaeger <aj@suse.com> To: Mohammed Naser <mnaser@vexxhost.com>, OpenStack Discuss <openstack-discuss@lists.openstack.org>, juliaashleykreger@gmail.com Subject: Re: [tc] weekly update Message-ID: <803b9cce-9887-95a5-b257-21f164f5569a@suse.com> Content-Type: text/plain; charset=utf-8 On 19/08/2019 18.26, Mohammed Naser wrote:
Hi everyone,
Here’s the update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository.
# Retired projects - Networking-generic-switch-tempest (from networking-generic-switch): https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.or g_-23_c_674430_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco &r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbP bnITV-ICkTgiy2DwRx3UO8&s=u1TtWtLxQw9wq6IOi2bbDXtaLl4zt5J-5ckqAjh-5iE&e =
The process for retiring is documented here: https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.openstack.org_infra_manual_drivers.html-23retiring-2Da-2Dproject&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=nXUYBv9J2FYcNfWHc2e-39LKUWlvyv1ajFIZAtZjWWM&e= Could you follow those steps to get the system out of Zuul properly, please? Andreas
# General changes - Michał Dulko as Kuryr PTL: https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.or g_-23_c_674624_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco &r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbP bnITV-ICkTgiy2DwRx3UO8&s=KLNfBuQ1X6WkQzI9yyVScUlkVFw91KTNz8ySzC2SK4I&e = - Added a mission to Swift taken from its wiki: https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.or g_-23_c_675307_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco &r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbP bnITV-ICkTgiy2DwRx3UO8&s=eZFduAqetS5dHRgx2V93U7dqTvoACzz45DKc2p1tlPI&e = - Sean McGinnis as release PTL: https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.or g_-23_c_675246_&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco &r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbP bnITV-ICkTgiy2DwRx3UO8&s=1Q2nQef0P-85E1K0QM5nGAtO3BYo8Y3zuMR_XC6L2f0&e =
Thanks for tuning in!
Regards, Mohammed
-- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg GF: Nils Brauckmann, Felix Imendörffer, Enrica Angelone, HRB 247165 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 ------------------------------ Message: 4 Date: Mon, 19 Aug 2019 12:48:40 -0400 From: Doug Hellmann <doug@doughellmann.com> To: Jeremy Stanley <fungi@yuggoth.org> Cc: openstack-discuss@lists.openstack.org Subject: Re: [all] [tc] [docs] [release] [ptls] Docs as SIG: Ownership of docs.openstack.org Message-ID: <740FFC7B-F7F0-427C-95F8-C6D6E8A0FA7E@doughellmann.com> Content-Type: text/plain;charset=utf-8
On Aug 19, 2019, at 10:59 AM, Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2019-08-19 13:17:35 +0000 (+0000), Alexandra Settle wrote: [...]
Doug has rightfully pointed out that whilst the documentation team as it stands today is no longer "integral", the docs.openstack.org web site is. An owner is required.
The suggestion is for the Release Management team is the "least worst" (thanks, tonyb) place for the website manaagement to land. As Tony points out, this requires learning new tools and processes but the individuals working on the docs team currently have no intention to leave, and are around to help manage this from the SIG.
Open to discussion and suggestions, but to summarise the proposal here:
docs.openstack.org ownership is to transition to be the responsibility of the Release Management team officially provided there are no strong objections. [...]
The prose above is rather vague on what "the docs.openstack.org web site" entails. Inferring from Doug's comments on 657142, I think you and he are referring specifically to the content in the https://urldefense.proofpoint.com/v2/url?u=https-3A__opendev.org_opens tack_openstack-2Dmanuals_src_branch_master_www&d=DwIGaQ&c=vo2ie5TPcLdc gWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloS PQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=4VwjzhhaDidxNS aaNi7uzBGmYIylK_5jNk7B73DKhZg&e= subtree. Is that pretty much it? The Apache virtual host configuration and filesystem hosting the site itself are managed by the Infra/OpenDev team, and there aren't any plans to change that as far as I'm aware. -- Jeremy Stanley
Yes, that’s correct. Doug ------------------------------ Subject: Digest Footer _______________________________________________ openstack-discuss mailing list openstack-discuss@lists.openstack.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddiscuss&d=DwIGaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=WXex93lsaiQ-z7CeZkHv93lzt4fdCRIPXloSPQEU7CM&m=ms75peRY0DgZY2AG9eCbPbnITV-ICkTgiy2DwRx3UO8&s=zXtwRY6Jm3E4Jt2ihjpRJZ8VIwFdTMcuMg0A7eJ9XYA&e= ------------------------------ End of openstack-discuss Digest, Vol 10, Issue 94 ************************************************* Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.