From cboylan at sapwetik.org Mon Oct 7 22:36:22 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 07 Oct 2019 15:36:22 -0700 Subject: [OpenStack-Infra] Agenda for Team Meeting on October 8, 2019 Message-ID: <084db888-4efe-4897-bd84-558053086f1b@www.fastmail.com> We will meet on October 8 at 19:00UTC in #openstack-meeting with this agenda: == Agenda for next meeting == * Announcements * Actions from last meeting * Specs approval * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev * General topics ** Trusty Upgrade Progress (clarkb 20191008) *** Wiki updates ** static.openstack.org (ianw,corvus,mnaser,fungi 20191008) *** Review spec: https://review.opendev.org/683852 *** Sign up for tasks at https://etherpad.openstack.org/p/static-services *** https://etherpad.openstack.org/p/openstack-org-dns ** CentOS 8 (clarkb 20191008) *** Do we need to consider pushing projects to switch labels when 8 is available? *** We continue to have glean + NetworkManager + Red Hat distro problems on ipv6 only clouds. **** https://review.opendev.org/#/c/686474/3 **** https://review.opendev.org/#/c/686749/5 ** PTG Planning (clarkb 20191008) *** https://etherpad.openstack.org/p/OpenDev-Shanghai-PTG-2019 *** http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009733.html Strawman schedule * Open discussion From paye600 at gmail.com Sat Oct 12 14:02:55 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Sat, 12 Oct 2019 16:02:55 +0200 Subject: [OpenStack-Infra] Bug: incorrect HTTP headers on Rackspace CDN S3 used by OS Infra Message-ID: <2102FB5F-2936-41CE-AAB7-9A621FD503A2@gmail.com> Hello team, I’m experiencing problems accessing certain content served by Rackspace CDN S3 used by OS Infra, and looking for help to get problem resolved. Here are 2 URLs: [0] and [1]. When requested with the headers & parameters listed below [2], – first one returns "zlib compressed data” with HTTP response headers [3] – second one returns “gzip compressed data”, inside which there is "zlib compressed data”, and HTTP response headers are listed here [4] As you may see, for the second URL with “docs/“ in the end Rackspace CDN encodes content twice (first with deflate and then with gzip) and adds two sequential “Content-Encoding” headers. Instead, I believe, it should be adding just one “Content-Encoding: gzip, deflate” header, listing encoding applied to data in order of application of those encodings to the data. RFC 7231 section 3.1.2.2 [5] says: If one or more encodings have been applied to a representation, the sender that applied the encodings MUST generate a Content-Encoding header field that lists the content codings in the order in which they were applied. Demo script to get URLs and see difference if published here: http://paste.openstack.org/raw/783267/ . Mozilla, for an example, also agrees that there should be just one header, listing two or more encodings in a sequence they are applied to the content – [6]. Practically, I’ve get error “Safari can’t open the page “…". The error is “can not decode raw data” (NSURLErrorDomain:-1015)”, and can not see contents of the page. I have raised the question on #openstack-infra at Freenode, and got confirmation that everything works fine in Firefox. Then I’ve tried to call Rackspace, but they were unable to register my request until I provide them with some PIN code and client details, which obviously I didn't have. So I call for your support and assistance, or may be directions on how could I get the problem resolved. I may have overlooked if this problem has been raised some one else earlier and already in progress of being resolved. Please, let me know if that is the case. Thank you. [0] https://2365c1d014187c3ae706-2572cddac5187c7b669ab9398e41b48d.ssl.cf5.rackcdn.com/687536/4/check/openstack-tox-docs/eb49c40/ [1] https://2365c1d014187c3ae706-2572cddac5187c7b669ab9398e41b48d.ssl.cf5.rackcdn.com/687536/4/check/openstack-tox-docs/eb49c40/docs/ [2] > Host: 2365c1d014187c3ae706-2572cddac5187c7b669ab9398e41b48d.ssl.cf5.rackcdn.com > User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.2 Safari/605.1.15 > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: en-us > Accept-Encoding: gzip, deflate, br [3] < Content-Encoding: deflate [4] < Content-Encoding: deflate < Vary: Accept-Encoding < Content-Encoding: gzip [5] https://tools.ietf.org/html/rfc7231#section-3.1.2.2 [6] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding Best regards, — Roman Gorshunov AT&T, Airship From fungi at yuggoth.org Sat Oct 12 14:29:37 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Sat, 12 Oct 2019 14:29:37 +0000 Subject: [OpenStack-Infra] Bug: incorrect HTTP headers on Rackspace CDN S3 used by OS Infra In-Reply-To: <2102FB5F-2936-41CE-AAB7-9A621FD503A2@gmail.com> References: <2102FB5F-2936-41CE-AAB7-9A621FD503A2@gmail.com> Message-ID: <20191012142937.axkiqe64rkjqrrd7@yuggoth.org> On 2019-10-12 16:02:55 +0200 (+0200), Roman Gorshunov wrote: > I’m experiencing problems accessing certain content served by > Rackspace CDN S3 used by OS Infra, and looking for help to get > problem resolved. [...] After some lengthy discussion, this workaround was implemented: https://review.opendev.org/688154 Any logs uploaded there for build which began after it merged at 22:02 UTC should no longer exhibit this behavior with browsers which are unable to correctly combine multiple list-type headers as allowed by IETF RFC 2616 section 4.2: "Multiple message-header fields with the same field-name MAY be present in a message if and only if the entire field-value for that header field is defined as a comma-separated list" https://tools.ietf.org/html/rfc2616#section-4.2 Note that while what the Rackspace CDN is doing may be atypical, it's allowed by accepted Internet standards. If the source code for your Web browser is readily available, then it may make sense to assist its maintainer community in resolving their lack of complete HTTP support. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From paye600 at gmail.com Sat Oct 12 14:50:59 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Sat, 12 Oct 2019 16:50:59 +0200 Subject: [OpenStack-Infra] Bug: incorrect HTTP headers on Rackspace CDN S3 used by OS Infra In-Reply-To: <20191012142937.axkiqe64rkjqrrd7@yuggoth.org> References: <2102FB5F-2936-41CE-AAB7-9A621FD503A2@gmail.com> <20191012142937.axkiqe64rkjqrrd7@yuggoth.org> Message-ID: <5B1BED6B-FAB1-4C78-9D59-984B663D1913@gmail.com> Hello Jeremy, Thank you very much for the reply and all your OpenStack Infra team for the solution you have built! I appreciate your help here and on IRC. Everything seems to work for me now (new URLs). My best wishes for you. — Roman Gorshunov > On 12 Oct 2019, at 16:29, Jeremy Stanley wrote: > > On 2019-10-12 16:02:55 +0200 (+0200), Roman Gorshunov wrote: >> I’m experiencing problems accessing certain content served by >> Rackspace CDN S3 used by OS Infra, and looking for help to get >> problem resolved. > [...] > > After some lengthy discussion, this workaround was implemented: > > https://review.opendev.org/688154 > > Any logs uploaded there for build which began after it merged at > 22:02 UTC should no longer exhibit this behavior with browsers which > are unable to correctly combine multiple list-type headers as > allowed by IETF RFC 2616 section 4.2: > > "Multiple message-header fields with the same field-name MAY be > present in a message if and only if the entire field-value for > that header field is defined as a comma-separated list" > > https://tools.ietf.org/html/rfc2616#section-4.2 > > Note that while what the Rackspace CDN is doing may be atypical, > it's allowed by accepted Internet standards. If the source code for > your Web browser is readily available, then it may make sense to > assist its maintainer community in resolving their lack of complete > HTTP support. > -- > Jeremy Stanley > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra From cboylan at sapwetik.org Mon Oct 14 21:50:07 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 14 Oct 2019 14:50:07 -0700 Subject: [OpenStack-Infra] Infra Team Meeting Agenda for October 15, 2019 Message-ID: <8ad4c397-4b7e-47cf-bd31-792e13d99b5e@www.fastmail.com> We will meet at 19:00UTC on October 15, 2019 (tomorrow) in #openstack-meeting with this agenda: == Agenda for next meeting == * Announcements ** OpenStack Release this Week (20191015) * Actions from last meeting * Specs approval * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev * General topics ** Trusty Upgrade Progress (clarkb 20191015) *** Wiki updates ** static.openstack.org (ianw,corvus,mnaser,fungi 20191015) *** Review spec: https://review.opendev.org/683852 *** Sign up for tasks at https://etherpad.openstack.org/p/static-services *** https://etherpad.openstack.org/p/openstack-org-dns **** Brought this up with the OSF and they had no initial concerns though jbryce said he wouldn't get to review it until this week. ** CentOS 8 (clarkb 20191015) *** Do we need to consider pushing projects to switch labels when 8 is available? *** zbr is updating the configure-mirror role to support CentOS 8 *** We believe that the NetworkManager issue has been tracked down and fixed (thank you ianw) **** The issue that prevents ipv4 from being configured is related to glean up'ing the interface between NetworkManager starts. We stopped glean from doing this. **** The issue that prevented ipv6 from being configured was related to our RA solicit delay value. Which we've removed. ** PTG Planning (clarkb 20191015) *** https://etherpad.openstack.org/p/OpenDev-Shanghai-PTG-2019 *** https://www.openstack.org/ptg/ schedule can be found here under the schedule tab. * Open discussion From clclchen at cn.ibm.com Wed Oct 16 03:02:49 2019 From: clclchen at cn.ibm.com (Ling LL Chen) Date: Wed, 16 Oct 2019 11:02:49 +0800 Subject: [OpenStack-Infra] OpenStack CI environment issues Message-ID: Hi Dear, This is Linda from IBM Storage cinder team and we need to set-up the OpenStack CI environment with puppet-master/jenkins/nodepool/zuul. But we hit lots of errors during the installation which followed by the guide "https://docs.openstack.org/infra/openstackci/third_party_ci.html". This guide is too old which used the ubuntu 14.04, while our operation system is ubuntu 18.04. And here is my questions: 1. Do you have any new updated guide or documents of how to set-up OpenStack CI environment on ubuntu 18.04 or ubuntu 16.04? 2. Do you have the manually step by step guide to install OpenStack CI environment? 3. Even we changed the OS to ubuntu 16.04, we still hit the errors as below: Error: /Stage[main]/Jenkins::Job_builder/File[/etc/jenkins_jobs/config]: Could not evaluate: Could not retrieve information from environment production source(s) file:/etc/project-config/jenkins/jobs Error: /Stage[main]/Nodepool/File[/etc/nodepool/elements]: Could not evaluate: Could not retrieve information from environment production source (s) file:/etc/project-config/nodepool/elements Error: /Stage[main]/Nodepool/File[/etc/nodepool/scripts]: Could not evaluate: Could not retrieve information from environment production source (s) file:/etc/project-config/nodepool/scripts Error: /Stage[main]/Openstackci::Nodepool/File [/etc/nodepool/nodepool.yaml]: Could not evaluate: Could not retrieve information from environment production source(s) file:/etc/project-config/nodepool/nodepool.yaml Warning: /Stage[main]/Jenkins::Job_builder/Exec[jenkins_jobs_update]: Skipping because of failed dependencies Error: /Stage[main]/Zuul::Server/File[/etc/zuul/layout]: Could not evaluate: Could not retrieve information from environment production source (s) file:/etc/project-config/zuul Regards, Chen Ling(Linda,陈玲) ------------------------------------------- Cloud Storage Solutions Development (CSSD) IBM System SRA troubleshooting wiki: https://apps.na.collabserv.com/wikis/home?lang=en-us#!/wiki/W9c4e08533b49_46bf_b9ee_e46fb712a085/page/SRA%20Troubleshoting Tel: (8621)6092-8292 Ext:28292 Address: 3F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai 201203, China ------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From cboylan at sapwetik.org Thu Oct 17 18:58:20 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Thu, 17 Oct 2019 11:58:20 -0700 Subject: [OpenStack-Infra] OpenStack CI environment issues In-Reply-To: References: Message-ID: <695b5e0e-e0db-4dd6-967e-bb0ed3a1695f@www.fastmail.com> On Tue, Oct 15, 2019, at 8:02 PM, Ling LL Chen wrote: > Hi Dear, > > This is Linda from IBM Storage cinder team and we need to set-up the > OpenStack CI environment with puppet-master/jenkins/nodepool/zuul. > > But we hit lots of errors during the installation which followed by the > guide "https://docs.openstack.org/infra/openstackci/third_party_ci.html > ". This guide is too old which used the ubuntu 14.04, while our operation system is ubuntu 18.04. These guides have historically been maintained by people like you running Third Party CI systems. Unfortunately, in recent years I don't think that any has been working to keep them up to date. The Infra team did write a spec to provide guidance to anyone willing to help produce update documentation, https://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3-3rd-party-ci.html This isn't a guide itself though and instead documentation of what we think is needed to help guide volunteers on producing the documentation. It would be excellent if the projects requiring third party CI helped to drive this work. > > And here is my questions: > 1. Do you have any new updated guide or documents of how to set-up > OpenStack CI environment on ubuntu 18.04 or ubuntu 16.04? We don't have guides specific to third party CI but Zuul does have documentation for setting up a Zuul v3 CI system: https://zuul-ci.org/docs/zuul/admin/quick-start.html https://zuul-ci.org/docs/zuul/admin/zuul-from-scratch.html > > 2. Do you have the manually step by step guide to install OpenStack CI > environment? > > 3. Even we changed the OS to ubuntu 16.04, we still hit the errors as below: > > Error: > /Stage[main]/Jenkins::Job_builder/File[/etc/jenkins_jobs/config]: Could > not evaluate: Could not retrieve information from environment > production source(s) file:/etc/project-config/jenkins/jobs > > Error: /Stage[main]/Nodepool/File[/etc/nodepool/elements]: Could not > evaluate: Could not retrieve information from environment production > source(s) file:/etc/project-config/nodepool/elements > > Error: /Stage[main]/Nodepool/File[/etc/nodepool/scripts]: Could not > evaluate: Could not retrieve information from environment production > source(s) file:/etc/project-config/nodepool/scripts > > Error: > /Stage[main]/Openstackci::Nodepool/File[/etc/nodepool/nodepool.yaml]: > Could not evaluate: Could not retrieve information from environment > production source(s) file:/etc/project-config/nodepool/nodepool.yaml > Warning: /Stage[main]/Jenkins::Job_builder/Exec[jenkins_jobs_update]: > Skipping because of failed dependencies > Error: /Stage[main]/Zuul::Server/File[/etc/zuul/layout]: Could not > evaluate: Could not retrieve information from environment production > source(s) file:/etc/project-config/zuul > > Regards, > > Chen Ling(Linda,陈玲) I think the ideal here would be for someone (or some group) to work through setting up a Zuulv3 using Zuul's documentation and the infra spec as guidance then use that to produce an up to date guide on setting up third party CI systems. Clark From scott.little at windriver.com Thu Oct 17 19:14:38 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 17 Oct 2019 15:14:38 -0400 Subject: [OpenStack-Infra] Please delete tag 2.0.1 Message-ID: Tag 2.0.1 should point to c89aeff3401fa37ca679bf170cd2f239a51b639f in repo opendev.org/starlingx/manifest . The current 2.0.1 tag was pushed in error.  Please delete the 2.0.1 tag from opendev.org/starlingx/manifest so that I can push the correct tag. We realize the challenges of re-writing a tag, and will be informing our users of the change and the manual steps to fix their repos. Thanks, Scott Little  (on behalf of the StarlingX team) -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Thu Oct 17 21:15:01 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 17 Oct 2019 21:15:01 +0000 Subject: [OpenStack-Infra] Please delete tag 2.0.1 In-Reply-To: References: Message-ID: <20191017211500.ttx5gkgv6gjm6jdp@yuggoth.org> [Cc'ing because it seems you're not subscribed, apologies for any duplicate copies you may receive] On 2019-10-17 15:14:38 -0400 (-0400), Scott Little wrote: > Tag 2.0.1 should point to c89aeff3401fa37ca679bf170cd2f239a51b639f in repo > opendev.org/starlingx/manifest . > > The current 2.0.1 tag was pushed in error.  Please delete the 2.0.1 tag from > opendev.org/starlingx/manifest so that I can push the correct tag. > > We realize the challenges of re-writing a tag, and will be informing our > users of the change and the manual steps to fix their repos. To recap the discussion from #openstack-infra on Freenode, doing this will leave Zuul and Nodepool repository caches in an inconsistent state from the official copy in Gerrit due to Git not communicating changes for tags. While it sounds like the CI jobs currently applied to or relying on the starlingx/manifest repository do not take any action on nor generate any artifacts from its Git tags, we would still need to perform cleanup under maintenance to wipe and replace Git caches on the following servers for consistency: 12 Zuul executors 8 Zuul mergers 3 Nodepool image builders This must be done with their respective services offline to force them to re-clone the repositories without erroneous tags when they start. Just as a reminder, these systems are designed with the assumption that Git tags won't be deleted or replaced because Git itself provides no mechanism for a client to discover that this has happened. Given the amount of manual effort involved, please consider alternatives such pushing a tag with a new (slightly higher) version number. While deleting that tag is something we *can* do, we need to know that the effort is justified, and not simply the OpenDev sysadmins taking on more work to save someone else from doing (perhaps a smaller amount of) work instead. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From dtroyer at gmail.com Thu Oct 17 22:02:36 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 17 Oct 2019 17:02:36 -0500 Subject: [OpenStack-Infra] OpenStack CI environment issues In-Reply-To: <695b5e0e-e0db-4dd6-967e-bb0ed3a1695f@www.fastmail.com> References: <695b5e0e-e0db-4dd6-967e-bb0ed3a1695f@www.fastmail.com> Message-ID: On 10/17/19 1:58 PM, Clark Boylan wrote: [...] > I think the ideal here would be for someone (or some group) to work through setting up a Zuulv3 using Zuul's documentation and the infra spec as guidance then use that to produce an up to date guide on setting up third party CI systems. I have been helping on setting up a more-production-quality Third Party CI at Intel recently, it is our intention to thoroughly document the process after it is running and we have learned the hard lessons of how to do it. In short I am taking this approach: * Install Gerrit (not strictly necessarily needed for testing upstream reviews but we want it for other reasons) from the upstream Gerrit Dockerfile I am also following along the current work that OpenDev/Infra are doing in this area. * Use Windmill[0] as the basis for installing the Zuul stack. This was fairly straightforard to get processes running, much of our time has been in understanding how to configure the components properly starting with our original Quick-Start-based setup. dt [0] https://opendev.org/windmill/ -- Dean Troyer dtroyer at gmail.com From fungi at yuggoth.org Fri Oct 18 14:40:34 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 18 Oct 2019 14:40:34 +0000 Subject: [OpenStack-Infra] Please delete tag 2.0.1 In-Reply-To: <20191017211500.ttx5gkgv6gjm6jdp@yuggoth.org> References: <20191017211500.ttx5gkgv6gjm6jdp@yuggoth.org> Message-ID: <20191018144033.husjxqehr3nnbcbe@yuggoth.org> [Cc'ing because it seems you're not subscribed, apologies for any duplicate copies you may receive] On 2019-10-17 21:15:01 +0000 (+0000), Jeremy Stanley wrote: > On 2019-10-17 15:14:38 -0400 (-0400), Scott Little wrote: [...] > > The current 2.0.1 tag was pushed in error. Please delete the > > 2.0.1 tag from opendev.org/starlingx/manifest so that I can push > > the correct tag. [...] > Given the amount of manual effort involved, please consider > alternatives such as pushing a tag with a new (slightly higher) > version number. [...] Based on http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006579.html it seems you settled on pushing a new 2.0.1b tag. Thank you for taking our workload into consideration, so we can better focus on other aspects of system maintenance and improvements. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From scott.little at windriver.com Fri Oct 18 18:10:25 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 18 Oct 2019 14:10:25 -0400 Subject: [OpenStack-Infra] Please delete tag 2.0.1 In-Reply-To: <20191017211500.ttx5gkgv6gjm6jdp@yuggoth.org> References: <20191017211500.ttx5gkgv6gjm6jdp@yuggoth.org> Message-ID: <8fc65e5c-8766-4536-073b-e1fc73b55e4c@windriver.com> We'll create a 2.0.1b tag for the manifest. We withdraw or request for tag deletion. Thanks,  Scott On 2019-10-17 5:15 p.m., Jeremy Stanley wrote: > [Cc'ing because it seems you're not subscribed, apologies for any > duplicate copies you may receive] > > On 2019-10-17 15:14:38 -0400 (-0400), Scott Little wrote: >> Tag 2.0.1 should point to c89aeff3401fa37ca679bf170cd2f239a51b639f in repo >> opendev.org/starlingx/manifest . >> >> The current 2.0.1 tag was pushed in error.  Please delete the 2.0.1 tag from >> opendev.org/starlingx/manifest so that I can push the correct tag. >> >> We realize the challenges of re-writing a tag, and will be informing our >> users of the change and the manual steps to fix their repos. > To recap the discussion from #openstack-infra on Freenode, doing > this will leave Zuul and Nodepool repository caches in an > inconsistent state from the official copy in Gerrit due to Git not > communicating changes for tags. While it sounds like the CI jobs > currently applied to or relying on the starlingx/manifest repository > do not take any action on nor generate any artifacts from its Git > tags, we would still need to perform cleanup under maintenance to > wipe and replace Git caches on the following servers for > consistency: > > 12 Zuul executors > 8 Zuul mergers > 3 Nodepool image builders > > This must be done with their respective services offline to force > them to re-clone the repositories without erroneous tags when they > start. Just as a reminder, these systems are designed with the > assumption that Git tags won't be deleted or replaced because Git > itself provides no mechanism for a client to discover that this has > happened. > > Given the amount of manual effort involved, please consider > alternatives such pushing a tag with a new (slightly higher) version > number. While deleting that tag is something we *can* do, we need to > know that the effort is justified, and not simply the OpenDev > sysadmins taking on more work to save someone else from doing > (perhaps a smaller amount of) work instead. From cboylan at sapwetik.org Mon Oct 21 21:53:35 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 21 Oct 2019 14:53:35 -0700 Subject: [OpenStack-Infra] Team Meeting Agenda for October 22, 2019 Message-ID: We will be meeting on October 22, 2019 at 19:00UTC in #openstack-meeting with this agenda: == Agenda for next meeting == * Announcements * Actions from last meeting * Specs approval * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev * General topics ** PTG Planning (clarkb 20191022) *** https://etherpad.openstack.org/p/OpenDev-Shanghai-PTG-2019 *** https://www.openstack.org/ptg/#tab_schedule PTG Schedule ** Trusty Upgrade Progress (clarkb 20191022) *** Wiki updates ** static.openstack.org (ianw,corvus,mnaser,fungi 20191022) *** Review spec: https://review.opendev.org/683852 *** Sign up for tasks at https://etherpad.openstack.org/p/static-services *** https://etherpad.openstack.org/p/openstack-org-dns * Open discussion From cboylan at sapwetik.org Mon Oct 28 22:55:40 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 28 Oct 2019 15:55:40 -0700 Subject: [OpenStack-Infra] Meeting Agenda for October 29, 2019 Message-ID: <01d5ac96-7c52-4885-9f75-a0e53281cc9f@www.fastmail.com> We will meet in #openstack-meeting at 19:00UTC on October 29, 2019 with this agenda: == Agenda for next meeting == * Announcements ** Summit and PTG next week. Meeting on November 5 Cancelled. * Actions from last meeting * Specs approval * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev * General topics ** Graphite update (clarkb 20191029) *** Retention for stats.timers reduced. Files updated and rechowned. ** PTG Planning (clarkb 20191029) *** https://etherpad.openstack.org/p/OpenDev-Shanghai-PTG-2019 *** https://www.openstack.org/ptg/#tab_schedule PTG Schedule ** Cleaning up OpenSuse 150 images (clarkb 20191029) *** The 150 images in nodepool were replaced by the 15 images. Need to update jobs so that we can remove the 150 images. *** https://review.opendev.org/#/q/topic:use-opensuse-15 ** Trusty Upgrade Progress (clarkb 20191029) *** Wiki updates ** static.openstack.org (ianw,corvus,mnaser,fungi 20191029) *** Review spec: https://review.opendev.org/683852 *** Sign up for tasks at https://etherpad.openstack.org/p/static-services *** https://etherpad.openstack.org/p/openstack-org-dns * Open discussion