Wednesday, 2021-06-16

airship-irc-bot<sirishagopigiri> URGENT 2.1 - Treasuremap review related to #27 issue https://review.opendev.org/c/airship/treasuremap/+/788289 Thank you in advance!11:31
airship-irc-bot<sirishagopigiri> Hi Team, Requesting some reviews on the below PSs related to #280 https://review.opendev.org/c/airship/airshipctl/+/789250 - Needs another +2 and WF +1 Thank you in advance!11:32
airship-irc-bot<sidney.shiba> Wharf URGENT: Treasuremap review related to #135, #137, #128 issues. https://review.opendev.org/c/airship/treasuremap/+/791835. Appreciate if you could prioritize this PS as many other Wharf PSs are depending on this to be merged.12:03
airship-irc-bot<sidney.shiba> After a few rechecks it finally got +1 from Zuul13:19
airship-irc-bot<james.gu> Hello team,  can I please have core reviews on the PS: https://review.opendev.org/c/airship/treasuremap/+/795172, so it can get into 2.1? TIA!14:33
airship-irc-bot<vkuzmin> Hi there, can you review https://review.opendev.org/c/airship/treasuremap/+/796028  This is phase plan for the multi-tenant gating16:57
airship-irc-bot<sean.eagan> The airship/images publishing jobs have been failing due to running out of space on the build VMs: https://zuul.openstack.org/job/airship-images-publish-commit https://zuul.openstack.org/builds?job_name=airship-images-publish-latest  Moving the image builder to its own repo should go a long way to resolving this: https://review.opendev.org/c/airship/image-builder/+/796526 https://review.opendev.org/c/airship/images/+/795131 cc20:34
airship-irc-bot@dm470r  Anything else that can be done in the meantime such as using larger VMs or removing other images?20:34
airship-irc-bot<sean.eagan> or break it up into separate jobs per image (or image group) where each job is only triggered by changes to that image using: https://zuul-ci.org/docs/zuul/reference/job_def.html#attr-job.files20:45
airship-irc-bot<mf4716> how close are we to finishing @dm470r’s two PSs?  @imarijitbose @sirajudeen.yasin, thoughts on using larger VMs?21:00
airship-irc-bot<mf4716> URGENT:  2.1 Dex PS from Sidney.  Requesting TM Core Reviews and WF to unblock several issues:  https://review.opendev.org/c/airship/treasuremap/+/79183521:11
airship-irc-bot<dm470r070> @mf4716 cc @sean.eagan  796526 is ready for review, moves +90% of the image builder code over 795131 just removes the old code from airship/images and fell out of date with master, but is practically done. They can be reviewed and submitted separately, but a third patchset is necessary to sync up any changes that were added to airship/images since the last time I pulled in that code. A current concern of mine and Matt McCuen's is21:23
airship-irc-botsmoothly transitioning work from one repo to another. There are open PS's that will need to be moved (https://review.opendev.org/q/project:airship/images+status:open). So whenever we can definitely say 'This is the day we stop image-builder development in the images repository' is the day the requisite patchsets can be finalized and merged, and work can resume in the airship/image-builder repo.21:23
airship-irc-bot<mf4716> In looking at the active PSs, and open Issues, there are only 2 open issues, with as many open PSs, anticipating one more possibly.  This would be it for the 2.1 commitments, unless something else surfaces.  All other Issues have Future milestones, and the older PSs (>2 weeks w/o updates) would be depreciated.  I.e. this would be a good community topic to gauge, or socialize, timing to cut over as soon as 2.1 commitments are met.21:46
airship-irc-bot<mf4716> *URGENT 2.1:  TM Core & WF needed* on TM166 issue from Vladislav for 'Add Phase Plan for multi-tenant gating'.  This critical PS is needed to support code uplifts and unblock other issues:  https://review.opendev.org/c/airship/treasuremap/+/79602823:47

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!