Tuesday, 2019-04-09

openstackgerritTin Lam proposed openstack/airship-armada master: Fix an Armada wait error  https://review.openstack.org/65055701:16
*** sthussey has quit IRC01:51
*** debugger_io has quit IRC01:56
openstackgerritRahul Khiyani proposed openstack/airship-maas master: [WIP]Maas: Add pod/container security context            - deployment-ingress-errors.yaml            - deployment-maas-ingress.yaml  https://review.openstack.org/63920001:59
*** roman_g has quit IRC02:29
*** licanwei has joined #airshipit02:40
openstackgerritRahul Khiyani proposed openstack/airship-maas master: [WIP]Maas: Add pod/container security context            - deployment-ingress-errors.yaml  https://review.openstack.org/63920003:15
*** prabhjot has quit IRC03:51
*** kaspars__ has joined #airshipit04:22
*** jamesgu has quit IRC06:14
*** kaspars__ has quit IRC06:48
*** roman_g has joined #airshipit07:39
*** happyhemant has joined #airshipit07:48
*** aojea has joined #airshipit08:03
*** bh526r has quit IRC08:04
*** debugger_io has joined #airshipit08:42
*** debugger_io has quit IRC09:50
*** debugger_io has joined #airshipit10:12
*** debugger_io has quit IRC10:15
*** debugger_io has joined #airshipit10:16
*** debugger_io has quit IRC10:18
*** debugger_io has joined #airshipit10:24
*** debugger_io has quit IRC10:28
*** debugger_io has joined #airshipit10:39
happyhemanthello folks, i was trying to deploy horizon on kubernetes cluster with openstack. when I tried to deploy horizon I get some strange error I dont have an idea what is it exactly may be some one is familier with this and help me to solve my issue help will be mich appreciated. thanks  https://www.irccloud.com/pastebin/FM7brR5B/10:44
*** arunkant has joined #airshipit12:31
*** openstackgerrit has quit IRC12:44
*** bh526r has joined #airshipit12:51
*** sthussey has joined #airshipit12:58
*** mbeierl has joined #airshipit13:02
*** debugger_io has quit IRC13:02
*** debugger_io has joined #airshipit13:06
*** openstackgerrit has joined #airshipit13:14
openstackgerritMerged openstack/airship-armada master: Fix an Armada wait error  https://review.openstack.org/65055713:14
*** debugger_io has quit IRC13:16
*** debugger_io has joined #airshipit13:17
*** aaronsheffield has joined #airshipit13:21
openstackgerritMerged openstack/airship-armada master: End user logging for audit traceabilty  https://review.openstack.org/63812413:22
*** prabhjot has joined #airshipit13:25
openstackgerritSean Eagan proposed openstack/airship-armada master: Introduce v2 docs  https://review.openstack.org/64824613:29
*** ab2434_ has joined #airshipit13:42
*** debugger_io has quit IRC13:58
*** sgrasley__ has quit IRC14:02
*** sgrasley has joined #airshipit14:02
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: [WIP] Various fixes to Spyglass to resolve tox errors  https://review.openstack.org/64876414:10
*** kaspars__ has joined #airshipit14:12
dwalthappyhemant: o/ Do you have any additional logs from Armada? Looking for anything that shows it quitting unexpectedly during a previous deployment14:13
openstackgerritSean Eagan proposed openstack/airship-armada master: Introduce v2 docs  https://review.openstack.org/64824614:14
*** prabhjot has quit IRC14:15
kaspars__@kranthikirang when MAAS node is enlisted via PXE it will download some ubuntu package and will require proxy.14:15
kaspars__Usually as PXE network doesn't have direct access to internet, you can use combination of proxy, as well as MAAS in-built proxy that should make it work14:15
kaspars__https://github.com/openstack/airship-maas/blob/master/charts/maas/values.yaml#L17314:16
happyhemantdwalt: all works fine for me but if i tried to redeploy manifest it gives me this strange error :(14:16
*** michael-beaver has joined #airshipit14:17
kaspars__you will need a) proxy_enabled: true, peer_proxy_enabled: true, proxy_server: "http://your-proxy-here.com:8080"14:17
kaspars__for MAAS chart/overrides14:17
happyhemantdwalt: I dont have other logs except these  https://www.irccloud.com/pastebin/t9Re8qQg/14:19
dwalthappyhemant: Do you have Tiller deployed in your cluster or are you using the Tiller that runs in the Armada pod?14:20
openstackgerritDimitrios Markou proposed openstack/airship-treasuremap master: [WIP] Integrate VIPs in airship-seaworthy  https://review.openstack.org/65043214:20
happyhemantdwalt: yes i have it  https://www.irccloud.com/pastebin/UmiUezmQ/14:21
happyhemantit si deplpyed in my cluster14:23
happyhemantit is deployed in my cluster*14:23
dwalthappyhemant: michael-beaver did a lot of the work to implement this and recently told me that each lock should have  a ten minute timeout. Can you try to run armada apply again to see if armada ignores the existing lock?14:31
sthussey@happyhemant did you ctrl-c out of an Armada apply operation?14:31
dwaltIf a previous Armada quit unexpectedly, it could leave an orphan lock14:32
happyhemantsthussey: yes i did that  dwalt: yes i experiance this timout thing but if i want to redeploy manifest it doesnt work i can not redeploy it again as it is giving same error14:35
sthusseyYou'll need to manually delete the Armada Lock CR in kubernetes14:35
happyhemantsthussey: to be honest i dont know how to delete could you please tell me ?14:36
sthussey@michael-beaver do you have a quick reference for that?14:38
michael-beaverif you run `kubectl get locks` does it come up with anything?14:38
michael-beaverAnd like dwalt was mentioning, if there is an orphan lock, the full lock expiration time is set to a default of 10 minutes, so if a lock is over 10 minutes old when armada starts it will go ahead and remove it before continuing14:40
happyhemantmichael-beaver : `kubectl get locks` no it give me no resources found. I tried to metion namespaces too but no results14:41
happyhemantmichael-beaver : yeah I know about 10 min timout but I chnaged some parameters in `amrada-osh.yaml` file and tried to redeploy it but same error is popping up all the time as i am trying since from last one hour14:43
openstackgerritLakshmi Prasanna Goutham Pratapa proposed openstack/airship-promenade master: Add Liveness/Readiness probe to calico-etcd.  https://review.openstack.org/64556114:45
happyhemantmichael-beaver : so finally after almost one hour it worked for me  I can able to redploy without deleting or chnaging anything14:45
*** lemko has joined #airshipit14:45
michael-beaverSo it finally went through? My only thought is that there is/was an armada out there that was continuing to update the lock as it was continuing to do something, as otherwise the old lock being there shouldn't matter14:47
michael-beaverSo if it is working now, what does `kubectl get locks --all-namespaces` do for you?14:48
lemkoTheses locks in armada look interesting.14:51
happyhemanthttps://www.irccloud.com/pastebin/DZMTcD9J/14:52
happyhemantmichael-beaver: this is what i get now https://www.irccloud.com/pastebin/IN0iAKKB/14:54
michael-beaverAwesome! well it looks like it was able to override the previous lock. Just to follow up on what sthussey was saying, in order to manually delete it you should be able to run `kubectl delete locks -n kube-system locks.armada.process.lock`14:56
portdirectmichael-beaver: how do you enable locks in a cluster?14:58
portdirecti know somewhat tangental to the above, but I dont seem to have that resource type in my clusters?14:59
portdirecthttps://www.irccloud.com/pastebin/IFbduB9D/14:59
portdirectdwalt ^15:02
michael-beaverWith the newest version of Armada it is enabled by default15:04
dwaltportdirect: michael-beaver: it's a custom resource definition, right? I think in order to add one to your cluster, you'd have to create an API document for the resource https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#create-a-customresourcedefinition15:06
openstackgerritRahul Khiyani proposed openstack/airship-maas master: Maas: Add pod/container security context       - deployment-ingress-errors.yaml  https://review.openstack.org/63920015:06
happyhemantdwalt: michael-beaver:  sthussey: thanks alot guys for help its working fine now :)15:08
sthusseyThe Armada chart creates the CRD15:08
michael-beaverdwalt: For the case of Armada, it uses the K8s API to create the CRD so it can get acquire the lock in the bootstrapping phase of genesis15:09
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: [WIP] PEP-8 code styling and linting  https://review.openstack.org/64969215:14
*** jamesgu has joined #airshipit15:15
mattmceuenHi all -- here's the agenda for our meeting in a half hour: https://etherpad.openstack.org/p/airship-meeting-2019-04-0915:27
mattmceuenPlease add anything you'd like to discuss today15:27
portdirectsthussey: looks like armada itself creates it: https://github.com/openstack/airship-armada/commit/48920224cc3f70bf1414839de65837fffbfebb6815:39
portdirectpretty cool michael-beaver15:39
sthusseyEven better15:39
portdirectit would be really nice to pull some of this into its own thing - k8s locks would really have huge value across the spectrum15:41
*** michael-beaver has quit IRC15:42
*** levmorgan has joined #airshipit15:43
*** michaelbeaver has joined #airshipit15:48
mattmceuen#startmeeting airship16:00
openstackMeeting started Tue Apr  9 16:00:42 2019 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: airship)"16:00
openstackThe meeting name has been set to 'airship'16:00
mattmceuen#topic Rollcall16:00
*** openstack changes topic to "Rollcall (Meeting topic: airship)"16:00
mattmceuenGM / GE everyone!16:00
dwalto/ gm!16:01
michaelbeavero/ GM16:01
mattmceuenHere's the agenda for today: https://etherpad.openstack.org/p/airship-meeting-2019-04-0916:01
seaneagano/16:01
levmorgano/16:01
mattmceuenlet's give it a couple mins for folks to trickle in and add items to the agenda16:01
*** michaelbeaver has quit IRC16:01
arunkanto/16:01
mfuller_o/16:01
*** michaelbeaver has joined #airshipit16:02
*** shauno_ has joined #airshipit16:02
*** jezogwza has joined #airshipit16:02
mattmceuenhey everyone thanks for joining16:02
*** jamesgu__ has joined #airshipit16:03
mattmceuenok, let's get started16:03
mattmceuen#topic How do manage Roadmaps for Airship16:03
*** openstack changes topic to "How do manage Roadmaps for Airship (Meeting topic: airship)"16:04
mattmceuenRodolfo wanted to discuss this one -- from the agenda16:04
mattmceuen    How does Roadmap items / features relate to storyboard or patchsets or labels16:04
mattmceuen    How do roadmap features relate to treasuremap Monthly Tags16:04
mattmceuenAll yours jezogwza16:04
jezogwzaOk, originlly when we started we used milestones in git to drive definition of features and or milestone releases for the project. Doesnt seem we are doign that anymore16:05
jezogwzaJust wondering how we get back to something that allows us to build automation for the treasuremap , and release notes, etc that we can get behind16:06
mattmceuenExcellent topic16:06
mattmceuenAs dwalt and myself scraped a ton of git logs to handcraft some release notes, this is near to my heart ;-)16:07
jezogwzaDo we know how other projects approach this?16:07
sthusseyThere are several systems for turning the git history into release notes16:07
openstackgerritRahul Khiyani proposed openstack/airship-maas master: Maas: Add pod/container security context       - deployment-ingress-errors.yaml  https://review.openstack.org/63920016:08
mattmceuenThe OpenStack standard-ish way is to use the OPenStack Reno project -- https://docs.openstack.org/reno/latest/16:08
*** shauno_ has quit IRC16:09
mattmceuenBut I'd be interested in a value comparison among choices16:09
mattmceuenAnyone have substantial experience (or opinions) on this?16:09
*** shauno_ has joined #airshipit16:09
dwaltI see that there is a sphinx extension for the openstack-reno one, that's a bonus16:10
mattmceuenI did try setting up Reno once for OSH, but it never merged :))16:10
* mattmceuen the extent of matts experience16:11
dwaltmattmceuen: do you still have a link to that patch? Would be interested in taking a look at how it's set up16:11
jezogwzaThat reno sounds interesting, how however that doesn't solve for Feature management/Roadmap ‌etc. But it could be at least part of that puzzle.16:11
sthusseyI think to get real value you'd first need better upstream tracking of defects and enhancements16:11
mattmceuenYep: https://review.openstack.org/#/c/563481/16:11
mattmceuenAgree sthussey16:11
sthusseyGenerally any of these systems are about turning metadata in commit messages into links to existing artifacts16:11
mattmceuenLet's start there16:11
sthusseyhttps://github.com/github-tools/github-release-notes16:12
mattmceuenSo one thing we make hit-or-miss use of so far is using the "Story:" and "Task:" metadata in our commits16:12
mattmceuenThose drive story lifecycle in storyboard if you use 'em16:12
jezogwzaSeems reasonable to start with choosing one of this tools as our next step.16:14
sthusseyhttps://blogs.sap.com/2018/06/22/generating-release-notes-from-git-commit-messages-using-basic-shell-commands-gitgrep/16:14
mattmceuenSince kaspars__ is driving monthly releases of Treasuremap (and therefore, of "packaged" airship) does it make sense to start targeting/tracking scope in storyboard for these releases?16:14
jezogwzaI was hoping along with his monthly tags, we could at least delivery an understandig of what change between tags16:15
mattmceuen++16:15
sthusseyIt will be non-trivial to generate that documentation16:15
mattmceuenMonthly release notes will make Summittime release notes easy :)16:15
sthusseyAs his tagged 'release' is an integration of lots of pieces16:15
sthusseySo either his release notes will just be 'Upgraded Airship-Drydock to x.y.z'16:16
sthusseyOr he'll need to start pulling in all the changes for all the pieces being integrated16:16
mattmceuenYeah, it will take some transitive data gathering to make that meaningful16:16
jezogwzaCould it be that each project can generate its own, and treasuremap just collects.16:16
*** shauno_ has quit IRC16:16
seaneaganwe also don't even have x.y.z for airship components yet16:16
mattmceuenThe other option is to track scope / monthly releases in storyboard, and let that drive things-- storyboard tying it together directly, rather than the treasuremap integration per se16:17
jezogwzaWell it could be ok to start with Dydock : ps 1.. 10, Promenade psn..m, etc16:17
jezogwzaIts better than nothing16:17
sthusseyI would start with a commit message standard to contain the information that should go in the notes16:18
sthusseybecause that is going to be the foundation of anything else16:18
mattmceuenThe little I know about Reno:  it uses a file full of metadata in the project, and then as "changelog worthy" changes are made, the file is appended to as part of the came commit16:19
mattmceuenJust a different spin on the commit message approach16:19
sthusseyI prefer the mechanism of just turning commit msgs into release notes16:19
sthusseyFor a commit that should be omitted, that can be declared in the commit msg16:20
sthusseyBy default all commits should be accounted for in the release notes IMO16:20
*** shauno_ has joined #airshipit16:20
mattmceuenI suggest let's let this topic rest for today - think about it, select some potential tools / approaches, and revisit in a couple weeks.  Agree?16:20
jezogwzaAgree16:21
sthusseySure16:21
dwaltSounds like a plan16:21
mattmceuenOk cool.  I'll go out of order on the agenda slightly to make this a segueway then16:21
mattmceuen#topic Airship PTG agenda16:21
*** openstack changes topic to "Airship PTG agenda (Meeting topic: airship)"16:21
mattmceuenhttps://etherpad.openstack.org/p/airship-ptg-train16:21
mattmceuenI took an initial stab at an agenda for the PTG16:22
mattmceuenThe PTG will be extra short this year, but there will be forums and things at the Summit proper, so I expect some convo to happen ahead of time16:22
mattmceuenPlease add in anything you'd like to discuss to the agenda, and then the things that we fit into our day-and-a-half  of focused discussion will be prioritized based on what needs the most discussion, and who's able to be there & what they want to discuss16:23
*** debugger_io has joined #airshipit16:23
mattmceuenThe segueway bit is that I took a stab at laying out our big rocks of post airship 1.0 roadmap scope16:23
*** jezogwza has quit IRC16:24
mattmceuenI'm sure I missed some things so please add them in if so16:24
*** shauno_ has quit IRC16:24
mattmceuenI will plan to do a comparison between storyboard and that list to get them trued up a bit, as I know that's not all outlined in storyboard yet16:24
mattmceuenHeads up that our PTG meeting time is Friday afternoon and Saturday morning and afternoon16:25
mattmceuenIf you have to cut out early please make a note in the etherpad so we prioritize things that need to be discussed on Friday with folks that will be there16:25
mattmceuenThat's all I have on that topic, anything else?16:25
mattmceuenOk, moving on:16:26
mattmceuen#topic Proposed additional project:  airship-governance16:26
*** openstack changes topic to "Proposed additional project: airship-governance (Meeting topic: airship)"16:26
*** shauno_ has joined #airshipit16:27
mattmceuenWe want to post a draft formal Airship governance document, so that we can iterate on discussion and fine tuning it16:27
mattmceuenWe need a place to push a patchset :)16:27
*** shauno_ has quit IRC16:27
mattmceuenOpenStack and Starling-X both have their own dedicated governance repos (links in agenda) and that seems to me to be a reasonable approach16:27
mattmceuenAs previously discussed we should get some quorum here before creating any new airship repos16:28
mattmceuenAre you all ok with that approach for managing governance docs?  Or better ideas?16:28
mattmceuenThe value of a separate repo is 1) opportunity to limit the +2'ers down the road, 2) the repo won't change as frequently as other documentation16:29
mattmceuenPlease vote with +1 or -116:29
dwalt+116:29
michaelbeaver+116:29
*** debugger_io has quit IRC16:30
jamesgu__+116:30
arunkant+116:30
mattmceuenThanks guys - I will count that as "timeboxed unanimous" :)16:31
mfuller_+116:31
mattmceuenHope to get draft governance in front of y'all in short order16:31
mattmceuen#action mattmceuen to submit request to create airship-governance repo16:31
mattmceuen#action mattmceuen to review storyboard content against proposed roadmap scope in the PTG etherpad16:32
mattmceuenok, moving on:16:32
mattmceuen#topic Multi-distro spec : How to get final inputs and approval16:32
*** openstack changes topic to "Multi-distro spec : How to get final inputs and approval (Meeting topic: airship)"16:32
mattmceuenthanks for refreshing this arunkant16:32
mattmceuenhttps://review.openstack.org/#/c/643106/16:33
arunkantSo looks like there are number of comments on suggestion and seems to be agreement on most of topics .16:34
mattmceuenAgree16:34
mattmceuenFor folks who have given this a review already - let's give it a final review today16:34
arunkantokay..so can we target this to be reviewed and possibly approved by end of this week ?16:35
mattmceuenI think we should aim for that target  - let's get this done16:35
arunkantokay..thanks16:36
mattmceuenanything else on the multi-distro topic today folks?16:36
mattmceuenok - moving on:16:37
mattmceuen#topic What is the recommended approach to Tempest testing in an Airship deployed site?16:37
*** openstack changes topic to "What is the recommended approach to Tempest testing in an Airship deployed site? (Meeting topic: airship)"16:37
mattmceuenmfuller_ raised this16:37
mattmceuenI think this is a multifaceted question mfuller_16:38
mattmceuenAre you thinking along the lines of testing Airship itself via Tempest, or testing a deployed OpenStack on top of Airship?16:38
mfuller_The latter, sorry I should have been more specific16:38
mattmceuenNo worries, I think they're both good questions ;-)16:39
mattmceuenSo yeah, the helm test flag on OSH components to use tempest is more geared around "helm test" type scenarios - smoke testing or ensuring the widget got deployed right16:39
mattmceuenThere is also a Tempest helm chart that OSH has that can be used for more full-suite Tempest validation16:40
mattmceuenI'm not a Tempest expert, but I think the guys in #openstack-helm can probably point you to resources on how to get this started16:40
mattmceuenSo that is to say, "standalone chart" and "helm test" both have their place side by side16:41
mfuller_My experience so far with the run_tempest flag has been mixed. Since it can be enabled per chart, I was expecting the tests would only require that service to be available, but even for services like glance, it requires a compute endpoint to already be defined and running16:41
mfuller_However, if I instead wait until all OpenStack services are running, I've then run into an issue with the default roles that are created in keystone. The tempest verifier expects 'Member' to be there, but there's only 'member'16:43
mattmceuenug16:43
mfuller_and a duplicate role error occurs16:43
mfuller_So I wasn't sure if going this route was the best approach16:44
mattmceuenI know that's something that had been dealt with in the past; I thought the OSH team had ironed those things out -- possible that a few remained hidden though. I believe the problem may have been that some of the Members changed to members (or vice versa) in some openstack release IIRC16:44
mattmceuenI suggest you bring up that error in #openstack-helm and see if some of the tempest wizards there are already aware and have advice, or, if that's news16:45
mfuller_Are there plans to implement a global chart for tempest in treasuremap?16:45
mattmceuenI don't think there are plans now, but I don't see why it couldn't be added16:46
mattmceuenWould you be able to collaborate on that mfuller_?16:47
mfuller_Sure, absolutely, with the caveat that my chart authoring skills are still very green ;)16:48
mattmceuenAs the airship team knows the manifest parts well, but less experience with the tempest parts16:48
mattmceuenPerfect collaboration then :)16:48
mattmceuen#action mattmceuen to create Storyboard story to track adding Tempest to Treasuremap16:48
mattmceuenthanks for bringing that up16:48
mattmceuen#topic Roundtable16:49
*** openstack changes topic to "Roundtable (Meeting topic: airship)"16:49
mattmceuenAny other topics you's like to discuss today?16:49
jamesgu__matt: this may have been discussed previously... the airship services has its own htk definition, and osh services uses a common one. what's the reasons behind the difference?16:50
dwaltI don't think roman_g is here, but does anyone know what items are outstanding for the transition to opendev?16:50
mattmceuenjamesgu__:  I think the only difference is that they were assembled by different teams.  There are pros/cons both ways16:51
jamesgu__we had a case (at leaast temporarily) we need to use a different version of htk between openstack services.16:51
mattmceuenjamesgu__: in particular, the OSH comonents are all integrated together very frequently with OSH-Infra, so it pushes a little more toward the "keep it simple" approach as there's less likelihood of getting one version of HTK that is not compatible with all OSH charts16:52
jamesgu__the use case we have is to upgrade/update a openstack service16:53
mattmceuenjamesgu__: OTOH Airship is a collection of different projects, each of which may need to be pinned to a particular HTK due to compatibility reasons (e.g. recently a HTK upgrade impacted divingbell only)16:53
jamesgu__right, I was wondering if the osh global charts in airship could build in the same flexbility of different htk chart versions.16:54
mattmceuenSince it's all configuration-driven, I think that based on operator needs it's totally fine to have more than one HTK definition for an OSH setup when warranted16:54
mattmceuenkaspars__ or evgenyl, do you have an opinion on that?16:54
mattmceuendwalt:  I haven't heard any updates.  Happen to know when roman_g is back?16:55
mattmceuenjamesgu - can I add this as a topic for next week's meeting and get folks to think about it before then?16:56
jamesgu__yes absolutely. thanks!16:56
*** shauno_ has joined #airshipit16:56
mattmceuen#action mattmceuen get some thoughts on splitting out HTK pins for OSH in TM16:56
kaspars__I agree, in my view each component should have it's own HTK (e.g. nova, keystone) - but good to hear from OSH team more16:56
mattmceuenThat's exactly what I'm thinking too kaspars__, good to see what their lessons learned are16:57
mattmceuenCouple minutes left, any last topics to bring up?16:57
mattmceuenIn that case -- thanks everyone for a great meeting16:58
mattmceuenAppreciate your time and thought16:58
mattmceuenhave a good week.16:58
mattmceuen#endmeeting16:58
*** openstack changes topic to "airshipit.org || General Review Dashboard: https://review.openstack.org/#/q/project:%255Eopenstack/airship.*+status:open,n,z"16:58
openstackMeeting ended Tue Apr  9 16:58:41 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-04-09-16.00.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-04-09-16.00.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-04-09-16.00.log.html16:58
*** shauno_ has quit IRC17:00
openstackgerritMerged openstack/airship-pegleg master: Increase coverage threshold of tox tests to 87%  https://review.openstack.org/65092517:05
openstackgerritFelipe Monteiro proposed openstack/airship-pegleg master: Refactor: Consolidate catalog/catalogs engine directories together  https://review.openstack.org/65133117:07
openstackgerritFelipe Monteiro proposed openstack/airship-pegleg master: Refactor: Consolidate catalog/catalogs engine directories together  https://review.openstack.org/65133117:16
openstackgerritMerged openstack/airship-pegleg master: PKI Cert generation and check updates  https://review.openstack.org/63941417:18
*** michaelbeaver has quit IRC17:31
*** michael-beaver has joined #airshipit17:34
openstackgerritAlexander Hughes proposed openstack/airship-pegleg master: Update validity checks and docs of PKI functions  https://review.openstack.org/65133617:35
openstackgerritAlexander Hughes proposed openstack/airship-pegleg master: Update validity checks and docs of PKI functions  https://review.openstack.org/65133617:36
*** debugger_io has joined #airshipit17:43
*** happyhemant has quit IRC18:38
openstackgerritEvgeniy L proposed openstack/airship-in-a-bottle master: Fix broken Nova and Neutron deployment  https://review.openstack.org/65100218:53
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: [WIP] PEP-8 code styling and linting  https://review.openstack.org/64969219:10
openstackgerritArijit Bose proposed openstack/airship-in-a-bottle master: [site update] Adding gate set up  https://review.openstack.org/64679619:13
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: Resolves Bandit 101 errors from misusing asserts  https://review.openstack.org/65097719:14
openstackgerritMerged openstack/airship-in-a-bottle master: Fix broken Nova and Neutron deployment  https://review.openstack.org/65100219:21
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: Refactors CLI to match style of Airship CLIs  https://review.openstack.org/64945219:29
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: Refactors CLI to match style of Airship CLIs  https://review.openstack.org/64945219:31
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: [WIP] Revise CLI documentation  https://review.openstack.org/65013719:33
openstackgerritDimitrios Markou proposed openstack/airship-treasuremap master: [WIP] Integrate VIPs in airship-seaworthy  https://review.openstack.org/65043219:37
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: [WIP] Revise CLI documentation  https://review.openstack.org/65013719:38
*** jamesgu has quit IRC19:46
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: Resolves Bandit 101 errors from misusing asserts  https://review.openstack.org/65097719:47
openstackgerritRick Bartra proposed openstack/airship-drydock master: Add CIDR validation for MAAS  https://review.openstack.org/64878119:51
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: [WIP] Remove flask yaml-editor from Spyglass  https://review.openstack.org/65099319:58
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: [WIP] Remove flask yaml-editor from Spyglass  https://review.openstack.org/65099319:59
openstackgerritRick Bartra proposed openstack/airship-drydock master: Add CIDR validation for MAAS  https://review.openstack.org/64878119:59
openstackgerritRick Bartra proposed openstack/airship-drydock master: Add CIDR validation for MAAS  https://review.openstack.org/64878120:05
*** jamesgu has joined #airshipit20:06
*** aojea has quit IRC20:19
openstackgerritSean Eagan proposed openstack/airship-armada master: Fix log message  https://review.openstack.org/65137520:24
*** debugger_io has quit IRC20:32
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: [WIP] Various fixes to Spyglass to resolve tox errors  https://review.openstack.org/64876420:32
*** lemko has quit IRC20:44
openstackgerritDimitrios Markou proposed openstack/airship-treasuremap master: [WIP] Integrate VIPs in airship-seaworthy  https://review.openstack.org/65043220:47
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: Various fixes to Spyglass to resolve tox errors  https://review.openstack.org/64876420:48
openstackgerritIan Pittwood proposed openstack/airship-spyglass master: [WIP] PEP-8 code styling and linting  https://review.openstack.org/64969220:51
openstackgerritScott Hussey proposed openstack/airship-promenade master: (apiserver) [WIP] support key rotation  https://review.openstack.org/63193520:59
openstackgerritLev Morgan proposed openstack/airship-pegleg master: Fix multiple I/O issues in cert generation  https://review.openstack.org/64367821:28
openstackgerritAnthony Bellino proposed openstack/airship-divingbell master: [WIP] Initial Ansible Daemonset  https://review.openstack.org/64053921:47
openstackgerritArun Kant proposed openstack/airship-shipyard master: Adding opensuse support in image building of airflow and shipyard  https://review.openstack.org/63622921:47
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: [wip] Add sloop type and airsloop site  https://review.openstack.org/64919521:54
openstackgerritArun Kant proposed openstack/airship-deckhand master: Adding opensuse image build for deckhand  https://review.openstack.org/63830122:28
*** ab2434_ has quit IRC22:33
openstackgerritArun Kant proposed openstack/airship-shipyard master: Adding opensuse support in image building of airflow and shipyard  https://review.openstack.org/63622922:35
openstackgerritArun Kant proposed openstack/airship-deckhand master: Adding opensuse image build for deckhand  https://review.openstack.org/63830122:37
*** aaronsheffield has quit IRC23:10
openstackgerritArun Kant proposed openstack/airship-armada master: Support armada to run on opensuse image leap15  https://review.openstack.org/63732723:17
openstackgerritArun Kant proposed openstack/airship-pegleg master: Support pegleg to run on opensuse leap15 image  https://review.openstack.org/63949523:21
openstackgerritArun Kant proposed openstack/airship-pegleg master: Support pegleg to run on opensuse leap15 image  https://review.openstack.org/63949523:21
*** bh526r has quit IRC23:50

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!