From cboylan at sapwetik.org Mon May 4 20:23:59 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 04 May 2020 13:23:59 -0700 Subject: Team Meeting Agenda for May 5, 2020 Message-ID: <413bf93e-15de-412a-b05e-f3adf33ba83f@www.fastmail.com> We will meet May 5, 2020 at 19:00 UTC in #opendev-meeting with this agenda: == Agenda for next meeting == * Announcements ** Meeting now in #opendev-meeting. Same time and day of week. * 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/update-config-management.html Update Config Management] *** topic:update-cfg-mgmt *** Gerrit on docker updates **** Gerritbot still outstanding todo item. *** Zuul as CD engine **** Deploying Nodepool with containers. **** Reorganizing system-config zuul configs. ** OpenDev *** Progress on Governance changes **** New (old) Service Coordinator * General topics ** Virtual PTG Attendance (clarkb 20200505) *** https://virtualptgjune2020.eventbrite.com Register if you plan to attend. This helps with planning details. ** Trusty Upgrade Progress (clarkb 20200505) *** Wiki updates ** Reviewers plugin for Gerrit (fungi 20200505) *** https://review.opendev.org/#/q/topic:gerrit-plugins+is:open * Open discussion From cboylan at sapwetik.org Fri May 8 21:25:05 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Fri, 08 May 2020 14:25:05 -0700 Subject: June Virtual PTG Planning Message-ID: <2558df92-f9b4-419d-9ab7-084694a5efa9@www.fastmail.com> Hello everyone, I've started to put together some thoughts on what we might discuss during the PTG on this etherpad: https://etherpad.opendev.org/p/opendev-virtual-ptg-june-2020 Feel free to add your thoughts and ideas as well. Once the schedule is published I'll be sure to update the etherpad with details on when and where we are meeting. As we get closer to the event I'll do my best to try and schedule certain topics when interested individuals will be available to discuss them. The time zone problem may make this difficult, but we'll do our best. Clark From Tao.Liu at windriver.com Fri May 8 19:07:22 2020 From: Tao.Liu at windriver.com (Liu, Tao) Date: Fri, 8 May 2020 19:07:22 +0000 Subject: Starlingx/API-Ref review Message-ID: Hi OpenDev support team, The review below stuck at Build failed (promote pipeline). Can you please check the status and let me know how to fix this issue? https://review.opendev.org/#/c/720589/ Thanks Tao Liu, Member of Technical Staff, Engineering,, Wind River direct 613.963.1413 fax: 613.492.7870 skype: tao_at_home 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cboylan at sapwetik.org Fri May 8 21:49:44 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Fri, 08 May 2020 14:49:44 -0700 Subject: Starlingx/API-Ref review In-Reply-To: References: Message-ID: On Fri, May 8, 2020, at 12:07 PM, Liu, Tao wrote: > > Hi OpenDev support team, > > > The review below stuck at Build failed (promote pipeline). Can you > please check the status and let me know how to fix this issue? The promote pipeline only runs after a change has merged. Rechecking a change will not rerun the promote jobs. Typically the best way to handle promote failures is to fix the cause of the failure, then when the fix merges this will run the promote jobs for the fix change updating your artifacts that way. If the fix is made to a different project then we can trigger the promote jobs separately. In this case changes to starlingx/distcloud have landed since those failures and promote jobs have run successfully for them. I think this means we don't need to do anything for this particular case. > > https://review.opendev.org/#/c/720589/ > > > > Thanks From Tao.Liu at windriver.com Fri May 8 22:41:47 2020 From: Tao.Liu at windriver.com (Liu, Tao) Date: Fri, 8 May 2020 22:41:47 +0000 Subject: Starlingx/API-Ref review In-Reply-To: References: Message-ID: Thanks Clark for looking into this. Do you know why StarlingX API Documentation was not updated: https://docs.starlingx.io/api-ref/distcloud/? Although, the review has been merged. Tao -----Original Message----- From: Clark Boylan [mailto:cboylan at sapwetik.org] Sent: Friday, May 8, 2020 5:50 PM To: Liu, Tao; service-discuss at lists.opendev.org Cc: Jeremy Stanley; Camp, MaryX Subject: Re: Starlingx/API-Ref review On Fri, May 8, 2020, at 12:07 PM, Liu, Tao wrote: > > Hi OpenDev support team, > > > The review below stuck at Build failed (promote pipeline). Can you > please check the status and let me know how to fix this issue? The promote pipeline only runs after a change has merged. Rechecking a change will not rerun the promote jobs. Typically the best way to handle promote failures is to fix the cause of the failure, then when the fix merges this will run the promote jobs for the fix change updating your artifacts that way. If the fix is made to a different project then we can trigger the promote jobs separately. In this case changes to starlingx/distcloud have landed since those failures and promote jobs have run successfully for them. I think this means we don't need to do anything for this particular case. > > https://review.opendev.org/#/c/720589/ > > > > Thanks From cboylan at sapwetik.org Fri May 8 23:51:19 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Fri, 08 May 2020 16:51:19 -0700 Subject: Starlingx/API-Ref review In-Reply-To: References: Message-ID: <5580afe8-6a76-4455-91eb-d81b80598637@www.fastmail.com> On Fri, May 8, 2020, at 3:41 PM, Liu, Tao wrote: > Thanks Clark for looking into this. > > Do you know why StarlingX API Documentation was not updated: > https://docs.starlingx.io/api-ref/distcloud/? Although, the review has > been merged. Looks like the api-ref job hasn't run recently on that repo: https://zuul.openstack.org/builds?project=starlingx%2Fdistcloud&pipeline=promote. Looking at the configuration for that job I've found: https://opendev.org/starlingx/zuul-jobs/src/branch/master/zuul.d/project-templates.yaml#L20-L23 which shows that the job will only run if these files are updated: https://opendev.org/starlingx/zuul-jobs/src/branch/master/zuul.d/project-templates.yaml#L8-L15 I think the other changes that have merged don't update those files. The easiest way to address this is likely to merge a change to one of those files. Then if that newer change fails to run properly we can debug that failure. > > Tao > > -----Original Message----- > From: Clark Boylan [mailto:cboylan at sapwetik.org] > Sent: Friday, May 8, 2020 5:50 PM > To: Liu, Tao; service-discuss at lists.opendev.org > Cc: Jeremy Stanley; Camp, MaryX > Subject: Re: Starlingx/API-Ref review > > On Fri, May 8, 2020, at 12:07 PM, Liu, Tao wrote: > > > > Hi OpenDev support team, > > > > > > The review below stuck at Build failed (promote pipeline). Can you > > please check the status and let me know how to fix this issue? > > The promote pipeline only runs after a change has merged. Rechecking a > change will not rerun the promote jobs. Typically the best way to > handle promote failures is to fix the cause of the failure, then when > the fix merges this will run the promote jobs for the fix change > updating your artifacts that way. If the fix is made to a different > project then we can trigger the promote jobs separately. > > In this case changes to starlingx/distcloud have landed since those > failures and promote jobs have run successfully for them. I think this > means we don't need to do anything for this particular case. > > > > > https://review.opendev.org/#/c/720589/ > > > > > > > > Thanks > > From cboylan at sapwetik.org Mon May 11 22:13:34 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 11 May 2020 15:13:34 -0700 Subject: Team Meeting Agenda for May 12, 2020 Message-ID: <3329c930-82f8-48c5-8c3c-90f3f7ef4541@www.fastmail.com> We will meet with this agenda May 12, 2020 at 19:00UTC in #opendev-meeting: == 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/update-config-management.html Update Config Management] *** topic:update-cfg-mgmt *** Gerrit on docker updates **** Gerritbot still outstanding todo item. *** Zuul as CD engine **** Improving testing of services pre deployment to ensure we have minimal checks of some sort beyond "ansible ran" **** Managing container process users/uids **** Zuul configs reorged in system-config. Check if you need to rebase. ** OpenDev *** Progress on Governance changes * General topics ** Virtual PTG Attendance (clarkb 20200512) *** https://virtualptgjune2020.eventbrite.com Register if you plan to attend. This helps with planning details. *** https://etherpad.opendev.org/p/opendev-virtual-ptg-june-2020 PTG planning ** Trusty Upgrade Progress (clarkb 20200512) *** Wiki updates * Open discussion From maryx.camp at intel.com Tue May 12 23:51:33 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Tue, 12 May 2020 23:51:33 +0000 Subject: Starlingx/API-Ref review In-Reply-To: <5580afe8-6a76-4455-91eb-d81b80598637@www.fastmail.com> References: <5580afe8-6a76-4455-91eb-d81b80598637@www.fastmail.com> Message-ID: Hi Clark, I submitted a new review, it was merged and the Zuul promote worked as expected. https://review.opendev.org/#/c/726922/ We still don't know why it failed before, but thanks a bunch for the suggestion on how to kick-start it again. -Mary C. -----Original Message----- From: Clark Boylan Sent: Friday, May 8, 2020 7:51 PM To: Liu, Tao ; service-discuss at lists.opendev.org Cc: Jeremy Stanley ; Camp, MaryX Subject: Re: Starlingx/API-Ref review On Fri, May 8, 2020, at 3:41 PM, Liu, Tao wrote: > Thanks Clark for looking into this. > > Do you know why StarlingX API Documentation was not updated: > https://docs.starlingx.io/api-ref/distcloud/? Although, the review has > been merged. Looks like the api-ref job hasn't run recently on that repo: https://zuul.openstack.org/builds?project=starlingx%2Fdistcloud&pipeline=promote. Looking at the configuration for that job I've found: https://opendev.org/starlingx/zuul-jobs/src/branch/master/zuul.d/project-templates.yaml#L20-L23 which shows that the job will only run if these files are updated: https://opendev.org/starlingx/zuul-jobs/src/branch/master/zuul.d/project-templates.yaml#L8-L15 I think the other changes that have merged don't update those files. The easiest way to address this is likely to merge a change to one of those files. Then if that newer change fails to run properly we can debug that failure. > > Tao > > -----Original Message----- > From: Clark Boylan [mailto:cboylan at sapwetik.org] > Sent: Friday, May 8, 2020 5:50 PM > To: Liu, Tao; service-discuss at lists.opendev.org > Cc: Jeremy Stanley; Camp, MaryX > Subject: Re: Starlingx/API-Ref review > > On Fri, May 8, 2020, at 12:07 PM, Liu, Tao wrote: > > > > Hi OpenDev support team, > > > > > > The review below stuck at Build failed (promote pipeline). Can you > > please check the status and let me know how to fix this issue? > > The promote pipeline only runs after a change has merged. Rechecking a > change will not rerun the promote jobs. Typically the best way to > handle promote failures is to fix the cause of the failure, then when > the fix merges this will run the promote jobs for the fix change > updating your artifacts that way. If the fix is made to a different > project then we can trigger the promote jobs separately. > > In this case changes to starlingx/distcloud have landed since those > failures and promote jobs have run successfully for them. I think this > means we don't need to do anything for this particular case. > > > > > https://review.opendev.org/#/c/720589/ > > > > > > > > Thanks > > From cboylan at sapwetik.org Mon May 18 20:36:21 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 18 May 2020 13:36:21 -0700 Subject: Team meeting agenda for May 19, 2020 Message-ID: <4489a4c6-0143-4c5e-a3a9-b74ad7a6e020@www.fastmail.com> We will be meeting May 19, 2020 at 19:00UTC in #opendev-meeting with this agenda: == Agenda for next meeting == * Announcements ** clarkb out Friday and likely Monday * 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/update-config-management.html Update Config Management] *** topic:update-cfg-mgmt *** Gerrit on docker updates **** Gerritbot still outstanding todo item. *** Zuul as CD engine ** OpenDev *** Progress on Governance changes **** https://etherpad.opendev.org/p/XRyf4UliAKI9nRGstsP4 Email draft for building advisory board. * General topics ** pip-and-virtualenv next steps *** remove from more popular distros (ianw 20200519) *** notify and merge? ** DNS cleanup (ianw 20200519) *** Clearing out old mirrors and lots of old stuff seems to be there *** https://review.opendev.org/728739 : Add tool to export Rackspace DNS domains to bind format *** Should I post the results of the above to a etherpad for group audit (is equivalent of high latency zone xtfr) *** run as backup? ** HTTPS on in region mirrors (clarkb 20200519) *** https://review.opendev.org/#/c/728986/ *** Older debuntu don't come with apt support for ssl/tls but bionic/buster and newer do. *** Can probably switch many users of this via base jobs and they'll never know? ** Scaling Jitsi Meet for Meetpad (clarkb 20200519) *** Last friday we had ~22 concurrent users on a meetpad conference. The tool seemed to hold up. *** the Jitsi Video Bridge (jvb) component is the greatest consume of resources (CPU primarily) *** https://review.opendev.org/#/c/729008/ Starting to poke at running more jvbs. ** Project Renames (clarkb 20200519) *** We've got a single project rename queued and now that OpenStack release is done cost of doing renames is lower *** Do we maybe need to wait for PTG to avoid any impact there as well? *** Maybe we should make sure there are no renames that will show up the day after we do this one too? ** Virtual PTG Attendance (clarkb 20200519) *** https://virtualptgjune2020.eventbrite.com Register if you plan to attend. This helps with planning details. *** https://etherpad.opendev.org/p/opendev-virtual-ptg-june-2020 PTG planning ** Trusty Upgrade Progress (clarkb 20200519) *** Wiki updates * Open discussion From cboylan at sapwetik.org Thu May 21 18:40:31 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Thu, 21 May 2020 11:40:31 -0700 Subject: Forming the OpenDev Advisory Board Message-ID: <9911dd22-d2b4-4683-8a7d-a529117710a5@www.fastmail.com> Hello everyone, I've BCC'd potentially interested parties to ensure they get this email, but didn't CC to avoid putting too much pressure on them if I've gauged potential interest poorly. I'm also sure that this list isn't complete. Please share it with others that may be interested. One of the governance bodies that we've described is the OpenDev Advisory Board [0]. The purpose of this group is to work with the OpenDev admins to ensure that project and resource provider needs are being met. Through this group OpenDev can communicate important updates, manage load on cloud resources over time, and plan for future needs. I'm also hopeful that it can serve as a conduit for our collaborating constituents to find time to help administer OpenDev as well. We would like to welcome both projects consuming OpenDev resources and OpenDev resource providers to join the Advisory Board. The OpenDev admins don't want to prescribe how various groups decide who represents them as what works for OpenStack may not work for Zuul or Vexxhost. I don't expect this will be a large time sink, more that we'll have better communication channels when necessary. Once a participating group has decided who their representation should be, it would be great to have that representative reply to this thread publicly and introduce themselves. This way we'll build a roster over time. For Advisory Board process, I'd like to avoid making it heavyweight and suggest using this mailing list (service-discuss at lists.opendev.org) with a subject tag of [AdvisoryBoard]. That said, I think the Advisory Board can decide if something else would work better for them once we've started to collect a roster here. [0] https://docs.opendev.org/opendev/system-config/latest/project.html#governance Clark From donny at fortnebula.com Sat May 23 00:07:37 2020 From: donny at fortnebula.com (Donny Davis) Date: Fri, 22 May 2020 20:07:37 -0400 Subject: Forming the OpenDev Advisory Board In-Reply-To: <9911dd22-d2b4-4683-8a7d-a529117710a5@www.fastmail.com> References: <9911dd22-d2b4-4683-8a7d-a529117710a5@www.fastmail.com> Message-ID: On Thu, May 21, 2020 at 2:41 PM Clark Boylan wrote: > Hello everyone, > > I've BCC'd potentially interested parties to ensure they get this email, > but didn't CC to avoid putting too much pressure on them if I've gauged > potential interest poorly. I'm also sure that this list isn't complete. > Please share it with others that may be interested. > > One of the governance bodies that we've described is the OpenDev Advisory > Board [0]. The purpose of this group is to work with the OpenDev admins to > ensure that project and resource provider needs are being met. Through this > group OpenDev can communicate important updates, manage load on cloud > resources over time, and plan for future needs. I'm also hopeful that it > can serve as a conduit for our collaborating constituents to find time to > help administer OpenDev as well. > > We would like to welcome both projects consuming OpenDev resources and > OpenDev resource providers to join the Advisory Board. The OpenDev admins > don't want to prescribe how various groups decide who represents them as > what works for OpenStack may not work for Zuul or Vexxhost. I don't expect > this will be a large time sink, more that we'll have better communication > channels when necessary. Once a participating group has decided who their > representation should be, it would be great to have that representative > reply to this thread publicly and introduce themselves. This way we'll > build a roster over time. > > For Advisory Board process, I'd like to avoid making it heavyweight and > suggest using this mailing list (service-discuss at lists.opendev.org) with > a subject tag of [AdvisoryBoard]. That said, I think the Advisory Board can > decide if something else would work better for them once we've started to > collect a roster here. > > [0] > https://docs.opendev.org/opendev/system-config/latest/project.html#governance > > Clark > I am very interested in participating in this advisory board. As one of the smaller(est) providers of opendev infrastructure, I would be elated to represent these smaller providers on this board. -- ~/DonnyD C: 805 814 6800 "No mission too difficult. No sacrifice too great. Duty First" -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcin.juszkiewicz at linaro.org Tue May 26 09:04:35 2020 From: marcin.juszkiewicz at linaro.org (Marcin Juszkiewicz) Date: Tue, 26 May 2020 11:04:35 +0200 Subject: Forming the OpenDev Advisory Board In-Reply-To: <9911dd22-d2b4-4683-8a7d-a529117710a5@www.fastmail.com> References: <9911dd22-d2b4-4683-8a7d-a529117710a5@www.fastmail.com> Message-ID: <225c2afd-c7ee-586c-761a-d74740ea529d@linaro.org> W dniu 21.05.2020 o 20:40, Clark Boylan pisze: > One of the governance bodies that we've described is the OpenDev > Advisory Board [0]. The purpose of this group is to work with the > OpenDev admins to ensure that project and resource provider needs are > being met. Through this group OpenDev can communicate important > updates, manage load on cloud resources over time, and plan for > future needs. I'm also hopeful that it can serve as a conduit for our > collaborating constituents to find time to help administer OpenDev as > well. > > We would like to welcome both projects consuming OpenDev resources and > OpenDev resource providers to join the Advisory Board. The OpenDev > admins don't want to prescribe how various groups decide who > represents them as what works for OpenStack may not work for Zuul or > Vexxhost. I don't expect this will be a large time sink, more that > we'll have better communication channels when necessary. Once a > participating group has decided who their representation should be, it > would be great to have that representative reply to this thread > publicly and introduce themselves. This way we'll build a roster over > time. > > For Advisory Board process, I'd like to avoid making it heavyweight > and suggest using this mailing list > (service-discuss at lists.opendev.org) with a subject tag of > [AdvisoryBoard]. That said, I think the Advisory Board can decide if > something else would work better for them once we've started to > collect a roster here. Thanks for invitation. I am interested in participating in Advisory Board. I work for Red Hat as one of AArch64 (64-bit Arm) developers. Currently assigned to Linaro project where I work on getting AArch64 the first class citizen in OpenStack world. Core developer in OpenStack Kolla project, aarch64 CI jobs maintainer. From cboylan at sapwetik.org Tue May 26 16:17:29 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 26 May 2020 09:17:29 -0700 Subject: Team meeting agenda for May 26, 2020 Message-ID: <2d4e050e-f8c7-4394-bd8f-5d752f757788@www.fastmail.com> We will meet today, May 26, 2020 at 19:00 UTC in #opendev-meeting with this agenda: == Agenda for next meeting == * Announcements ** PTG happening next week. * 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/update-config-management.html Update Config Management] *** topic:update-cfg-mgmt *** Gerrit on docker updates **** Gerritbot still outstanding todo item. *** Zuul as CD engine **** Relying on base playbook (and others like letsencrypt playbooks) to complete successfully on all hosts before modifying subsets of hosts can make it difficult to land updates at times. ** OpenDev *** Progress on Governance changes **** http://lists.opendev.org/pipermail/service-discuss/2020-May/000026.html Advisory Board thread. We have some volunteers already! * General topics ** pip-and-virtualenv next steps *** remove from more popular distros (ianw 20200526) *** notify and merge? ** DNS cleanup (ianw 20200526) *** Clearing out old mirrors and lots of old stuff seems to be there *** https://review.opendev.org/728739 : Add tool to export Rackspace DNS domains to bind format *** Should I post the results of the above to a etherpad for group audit (is equivalent of high latency zone xtfr) *** run as backup? ** HTTPS on in region mirrors (clarkb 20200526) *** https://review.opendev.org/730861 Test ssl with mirrors via base-test *** https://review.opendev.org/730862 Use ssl with mirrors in production if base-test is happy ** Scaling Jitsi Meet for Meetpad (clarkb 20200526) *** Ready to launch a jvb01.opendev.org server and test. ** Project Renames (clarkb 20200526) *** We've got a single project rename queued and now that OpenStack release is done cost of doing renames is lower *** Aiming for June 12, 2020 currently. ** Virtual PTG Attendance (clarkb 20200526) *** https://virtualptgjune2020.eventbrite.com Register if you plan to attend. This helps with planning details. *** https://etherpad.opendev.org/p/opendev-virtual-ptg-june-2020 PTG planning *** Do we want to hold this meeting next week? ** Trusty Upgrade Progress (clarkb 20200526) *** Wiki updates * Open discussion