Tuesday, 2019-02-26

openstackgerritMatt McEuen proposed openstack/airship-treasuremap master: WIP: airskiff: Use global Airship charts  https://review.openstack.org/63521800:19
openstackgerritArun Kant proposed openstack/airship-deckhand master: Adding opensuse image build for deckhand  https://review.openstack.org/63830100:37
openstackgerritArun Kant proposed openstack/airship-deckhand master: Adding opensuse image build for deckhand  https://review.openstack.org/63830100:43
openstackgerritArun Kant proposed openstack/airship-deckhand master: Adding opensuse image build for deckhand  https://review.openstack.org/63830100:51
openstackgerritArun Kant proposed openstack/airship-deckhand master: Adding opensuse image build for deckhand  https://review.openstack.org/63830100:54
openstackgerritArun Kant proposed openstack/airship-deckhand master: Adding opensuse image build for deckhand  https://review.openstack.org/63830100:57
openstackgerritArun Kant proposed openstack/airship-deckhand master: Adding opensuse image build for deckhand  https://review.openstack.org/63830100:58
*** nishant__ has quit IRC02:13
*** roman_g has quit IRC03:19
*** mbologna_ has joined #airshipit07:05
*** mbologna has quit IRC07:06
*** pkaralis has quit IRC08:31
*** roman_g has joined #airshipit08:32
*** georgk3 has joined #airshipit09:29
*** georgk has quit IRC09:30
*** arunkant has quit IRC09:35
*** arunkant has joined #airshipit09:36
*** roman_g has quit IRC09:45
*** mbologna_ has quit IRC10:23
*** mbologna has joined #airshipit10:27
openstackgerritSmruti Soumitra Khuntia proposed openstack/airship-shipyard master: User context tracing through logging  https://review.openstack.org/63387311:38
openstackgerritSmruti Soumitra Khuntia proposed openstack/airship-shipyard master: User context tracing through logging  https://review.openstack.org/63387311:38
*** roman_g has joined #airshipit12:23
*** mbologna_ has joined #airshipit12:26
*** mbologna has quit IRC12:30
*** openstackgerrit has quit IRC12:30
*** dimitris_ has quit IRC13:03
*** hemanth_n has joined #airshipit13:32
*** sgrasley has joined #airshipit13:46
*** michael-beaver has joined #airshipit13:51
*** dustinspecker has joined #airshipit13:54
*** levmorgan has joined #airshipit13:57
mattmceuen#startmeeting airship14:00
mattmceuen#topic Rollcall14:00
openstackMeeting started Tue Feb 26 14:00:55 2019 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: airship)"14:01
mattmceuenHello everyone!14:01
openstackThe meeting name has been set to 'airship'14:01
*** openstack changes topic to "Rollcall (Meeting topic: airship)"14:01
dwalto/14:01
michael-beavero/14:01
mattmceuenHere's our agenda for today - please take a moment to add anthing you'd like to discuss: https://etherpad.openstack.org/p/airship-meeting-2019-02-2614:01
georgk3hi14:01
levmorgano/14:01
portdirect14:01
*** aaronsheffield has joined #airshipit14:01
arunkanto/14:02
b-stro/14:02
roman_go/14:02
mattmceuen#topic Consider what onboarding environment seems the most valuable14:02
*** openstack changes topic to "Consider what onboarding environment seems the most valuable (Meeting topic: airship)"14:02
aaronsheffieldo/14:02
mattmceuenSo this one was sthussey's; unfortunately he's not in today14:03
pas-hao/14:03
mattmceueno/ everyone14:03
*** Nishant_ has joined #airshipit14:03
mattmceuensthussey had brought up a good point that we have a number of different environments that are recommended for onboarding / reference type things14:03
pas-hamy question would also be 'is there a doc describing a dev process'14:04
pas-halike if I need to patch and test14:04
mattmceuenAirskiff14:04
mattmceuenAirship-in-a-bottle local VM14:04
mattmceuenAirship-in-a-bottle multi-VM14:04
mattmceuenTreasuremap - Seaworthy14:04
mattmceuenThere is a little bit of that in the Airskiff documentation, but not much to speak of pas-ha.  I think that's a very good value-add for the docs14:05
pas-halike a path from local repo -> patch -> build new container? -> push it to local docker? -> redeploy?14:05
mattmceuenA "day in the life of a developer" kind of thing14:05
pas-hayes, smth like that14:05
georgk3+114:05
pas-hafiguring that out myself for now14:05
mattmceuen#action mattmceuen to create a storyboard item for documenting the Airship development lifecycle14:06
*** levmorgan_ has joined #airshipit14:06
*** levmorgan has quit IRC14:06
*** mbeierl has joined #airshipit14:07
mattmceuenMy thought is that for the different "things" up above, they are each a combo of a couple different characteristics:14:07
mattmceuen1) a deployment approach14:07
mattmceuen2) a collection of manifests14:07
mattmceuenWhatever else we do, I want to try to align our manifests to one another as much as possible14:07
mattmceuendwalt has a patchset out for example that takes the airskiff manifests and aligns them more closely to the treasuremap globals14:08
mattmceuenI think maintenance of different, segmented manifests sets has been part of the maintenance challenge that sthussey wants to avoid14:09
dwaltThis might be a step back, but as far as lifecycle goes, I usually try to run the component locally before deploying any changes into one of our "development environments (i.e. Airskiff, AIAB)14:09
dwaltFor example, you can run Armada as a local Python project against KubeADM cluster, and it will find Tiller14:09
dwaltDeckhand and Shipyard also support similar dev setups, but they are buried a bit in the docs14:10
mattmceuenPromenade has a great "prom only" test environment, which spins up a 4-node VM cluster and beats it up.  This is what Airship-in-a-Bottle multinode (the tooling) was modeled after14:11
mattmceuenAirship-in-a-Bottle (the manifest set) is something that could be aligned into the treasuremap globals14:11
mattmceuenLet me ask for y'alls opinions -- what do you find valuable amongst these things?  I've heard the opinion that "developers don't tend to use airship single node", but that's the main onboarding path for new folks.   Would AiaB multinode serve that purpose, perhaps even better?14:12
mattmceuenI for one use Airskiff and AiaB multinode for my own work, depending on what I'm working on14:14
roman_gFor professional development people do probably use big bare-metal servers with lots of RAM.14:15
*** dimitris_ has joined #airshipit14:15
roman_gThis is not something to expect to have from those who only want to have a look at Airship14:15
dwaltFor me, it depends on the component. I tend to use Airskiff (single node) for the software delivery components and AIAB multimode in other cases14:15
michael-beaverI for one use the multinode a lot, but I think it is very prohibitive for someone without a dedicated lab14:15
mattmceuenThe nice thing about multinode is that it can deploy a variable number of nodes, based on configs... even perhaps a single node :)14:16
mattmceuenSo that's where my head is at with, we could do more things with less moving pieces if we aligned our manifests together and configured AiaB multinode scripts to be the single-node demo environment as well14:17
mattmceuenAny disagreement with this general sentiment?14:17
levmorgan_Sounds good to me.14:18
georgk3I like the multinode environment a lot, so +114:18
michael-beaverMaybe this is trivial, but another problem with running it is you need a Host OS capable of nested-virt, so windows using virtualbox is a no go ATM, but overall I don't disagree with the sentiment that the multinode gate would help us have less moving pieces14:18
dwalt++ mattmceuen. It'd be a great step moving our development environments closer in-line with our "reference" architecture14:19
mattmceuenCool, let's circle back with sthussey when he's back14:20
*** dimitris_ has quit IRC14:20
mattmceuengood point michael-beaver and we should keep that in mind14:20
mattmceuenwe've also been talking about aligning AiaB manifests to treasuremap for a long time14:20
mattmceuen#action mattmceuen create a Storyboard item for aligning AiaB manifests to Treasuremap14:20
mattmceuenanything else on this topic for now guys?14:21
mattmceuen#topic Ironic driver spec14:22
*** openstack changes topic to "Ironic driver spec (Meeting topic: airship)"14:22
mattmceuenpas-ha and some other folks have been going some work on the spec for adding Ironic support to Drydock:14:22
mattmceuenhttps://review.openstack.org/#/c/613358/14:23
mattmceuenroman_g, you wanted to sync up on that here, right?14:23
roman_gmattmceuen: not really to sync up, but may be we have Hemmanth here?14:25
roman_ghemanth_n:14:25
roman_gIf not, let's move on.14:25
mattmceuenOk.  I need to catch up on the latest discussion in the PS as well; pas-ha & roman_g should we plan to touch on this next week?14:26
roman_gYes. Move to the next week.14:26
roman_gWould also be good to discuss on design call14:26
roman_gprobably14:26
mattmceuenIf there's anything specific we need to grab hemanth_n's attention on we can mailing list it as well14:26
roman_gTrue.14:27
mattmceuenNext up:14:28
mattmceuen#topic Airship talks accepted into the Denver Summit14:28
*** openstack changes topic to "Airship talks accepted into the Denver Summit (Meeting topic: airship)"14:28
mattmceuenSo, we have some Airship talks accepted into the Denver Summit!14:28
mattmceuenUnfortunately, the summit website appears to not be functioning today, so I can't tell you what they all are! :D14:28
mattmceuenSo many great Airship talks that the database crashed perhaps14:29
mattmceuenwill share next time14:29
mattmceuen#topic Design meeting(s) for Docker, Kernel, OS, Security Patches, etc14:29
*** openstack changes topic to "Design meeting(s) for Docker, Kernel, OS, Security Patches, etc (Meeting topic: airship)"14:29
mattmceuenJust wanted to make sure folks were aware that Rodolfo has scheduled a design call later today (and may end up being recurring as needed) to dive deep into the topic of how to best orchestrate heavyweight, low-level changes across Airship sites14:30
*** dimitris_ has joined #airshipit14:30
mattmceuenThings like operating system upgrades, kubelet upgrades, docker, kernel, etc14:30
mattmceuenAs well as simple cluster-wide reboots when needed14:30
georgk3interesting, thanks for the info14:31
roman_ginteresting. not in my calendar14:31
evgenylWhere can I get an invite?14:31
roman_gwill ask. thank you14:31
mattmceuenThe intention has always been for Airship to be able to reprovision hosts in a way that preserves the local data for the running workloads (e.g. VMs)  . This is not quite finished yet, but will allow for e.g. host-by-host or failure-domain-by-domain reprovisionings of the cluster with e.g. a new patched kernel14:32
mattmceuenHowever, that's also a heavyweight operation and there are lighterweight things we can do as well14:32
mattmceuenAnyway - please join if you'd like to discuss more14:32
roman_gGood to have it recorded and published14:33
mattmceuenThe invite should be out on the Mailing List, if you go back to the archives from yesterday or Friday I believe14:33
evgenylOh, sorry, it was in the mailing list, I somehow missed it.14:33
mattmceuenDon't worry evgenyl, I am good at missing all kinds of email14:33
mattmceuenthree and a half hours from now14:33
mattmceuenMoving on:14:33
mattmceuen#topic Divingbell gates are broken in upstream14:33
*** openstack changes topic to "Divingbell gates are broken in upstream (Meeting topic: airship)"14:33
mattmceuenroman_g this is yours, go for it14:34
roman_gPretty much everything is in the description https://etherpad.openstack.org/p/airship-meeting-2019-02-2614:34
roman_gUpdate of Helm from version 2.11.0 to 2.12.1 and then to 2.12.3 broke host and label `overrides:` functionality for the Airship Divingbell.14:34
roman_gThis affects Divingbell development (voting gates not working), and partially other projects like openstack/openstack-helm-infra, which have Divingbell as a non-voting gate14:34
roman_gRoman is looking for an assistance14:34
roman_gIssue in one line: secret contents which is used for the host falling under override is identical to the secret used by default14:35
Nishant_I see a topic dedicated to the overrides issue in openstack-helm meeting today starting 9 AM CST14:35
mattmceuenawesome14:35
mattmceuenYes this is definitely something we need to get fixed ASAP, thank you roman_g for your analysis and summary14:36
roman_gI was offline probably. Will look at the logs.14:36
mattmceuenNope, it's coming up in a half hour :)14:36
roman_gAh, today. Good.14:37
roman_gNishant_: thank you!14:37
mattmceuenShall we see how the discussion goes on the OSH side, and if confirmed to be an OSH issue we can help dev/test as possible?  And otherwise circle back in the chat room roman_g?14:37
roman_gYes, sure. I have a testbed running, and can test easily.14:38
mattmceuensweet14:38
mattmceuen#topic Deckhand & Shipyard - OpenSUSE builds14:38
*** openstack changes topic to "Deckhand & Shipyard - OpenSUSE builds (Meeting topic: airship)"14:38
roman_g    Arun has started to work on building OpenSUSE-based images here: https://review.openstack.org/#/q/status:open+branch:master+topic:airship_suse14:38
roman_g    Does not align good with https://airship-specs.readthedocs.io/en/latest/specs/approved/multi-linux-distros.html we have approved14:38
roman_g#action Need to follow-up with/between Arun and James Gu14:38
mattmceuenWhat is the main difference between the approaches?14:39
roman_gIncomplete approach.14:39
mattmceuenok14:40
roman_gNot distro-independent, no tests, only image build part14:40
arunkantmattmceuen: hi, currently we are working on building images. So adding another variable input to ask for distro flavor and that is used in jobs14:40
roman_garunkant: are those 2 changes complete or WIP?14:41
arunkantroman_g: its work-in-progress, so trying to add check and gate jobs for building images. Is there any specific tests are needed other than adding jobs ?14:41
roman_garunkant: check the spec via the link above. There are other things which need to be done.14:42
roman_gAlso please don't override ubuntu-based :latest with opensuse-based :latest image on quay14:43
arunkantroman_g: Also need clarification where the docs need to be provided for building opensuse images . Is it updated spec or some other doc section ?14:43
roman_gin deckhand and in shipyard docs14:43
roman_gspec is used to discuss implementation, collect feedback14:44
mattmceuenarunkant, can you please give the spec a read, and see if it covers all the bases or if there are any gaps from your perspective?14:45
roman_gCan you reach out to James Gu (SUSE Gmbh.) and may be talk to him on implementation specifics detailed in the spec he wrote?14:45
arunkantroman_g: okay. Will look into docs for those components.14:45
mattmceuenfeel free to shout here in the chat room any time, really awesome to see your work on this, and looking forward to helping.  Thanks for your efforts here14:46
arunkantroman_g: Yes, I work with James Gu so will clarify the details with him.14:46
mattmceuenAnything else on this topic all?14:47
roman_gActually, my top list of what I would love to see in Airship is to see it working on SLES & RHEL (OpenSUSE & CentOS) in addition to Ubuntu.14:47
roman_gSo, thank you for your work, arunkant14:47
arunkantroman_g: will clarify in chat about the image tag question as oepnsuse images uses different tag (opensuse_15_latest)14:47
roman_garunkant: ahha, good.14:48
roman_gmattmceuen14:48
arunkantroman_g: yes that's the plan to make airship components to work with opensuse14:49
mattmceuen++14:49
mattmceuen#topic Patchset reviews requested14:50
*** openstack changes topic to "Patchset reviews requested (Meeting topic: airship)"14:50
mattmceuen    https://review.openstack.org/#/c/615892/ - docs: Add use cases for each of the mutation operations14:50
mattmceuenHooray for docs!14:50
mattmceuenoh that guy's merged already14:50
mattmceuenI should have checked :D14:50
mattmceuenAny other patchsets that folks would like to request some solid review?14:51
mattmceuen#topic Roundtable14:51
*** openstack changes topic to "Roundtable (Meeting topic: airship)"14:51
mattmceuenAny other topics, all?14:51
roman_gNothing. Thank you, Matt.14:53
mattmceuenAlright - thanks everyone for joining us today14:53
mattmceuenHave a great week!14:53
mattmceuen#endmeeting14:53
*** openstack changes topic to "airshipit.org || General Review Dashboard: https://review.openstack.org/#/q/project:%255Eopenstack/airship.*+status:open,n,z"14:53
openstackMeeting ended Tue Feb 26 14:53:55 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-02-26-14.00.html14:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-02-26-14.00.txt14:53
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-02-26-14.00.log.html14:54
*** levmorgan_ has quit IRC14:58
*** michael-beaver has quit IRC14:58
*** DanCrank has joined #airshipit14:59
*** sreejithp has joined #airshipit15:08
*** jamesgu has joined #airshipit15:23
*** jamesgu__ has joined #airshipit15:24
*** jamesgu__ has quit IRC15:24
*** michael-beaver has joined #airshipit15:27
*** hemanth_n has quit IRC15:55
vdrokhey folks, I have a question from one of mirantis' ceph guys, are there any plans to improve the ceph deployment strategy in openstack-helm? One of the things he mentioned was deprecation of ceph-disk for mimic (it seems to be used at least during osd initialization), also maybe using rook instead of bash scripts there currently are?16:08
roman_gvdrok: probably beter to ask in #openstack-helm. It's silent here.16:22
*** michael-beaver has quit IRC16:22
vdrokroman_g: okie, will do16:23
*** sgrasley has quit IRC16:31
*** michael-beaver has joined #airshipit16:38
*** michael-beaver has quit IRC16:39
*** michaelbeaver has joined #airshipit16:39
*** openstackgerrit has joined #airshipit16:50
openstackgerritDrew Walters proposed openstack/airship-treasuremap master: WIP: airskiff: Use global Airship charts  https://review.openstack.org/63521816:50
*** jsun3 has joined #airshipit17:09
*** jsun3 has quit IRC17:17
*** dustinspecker has quit IRC18:02
openstackgerritAnthony Bellino proposed openstack/airship-treasuremap master: Secret rotation and validation  https://review.openstack.org/63569418:22
openstackgerritAlexander Hughes proposed openstack/airship-pegleg master: [WIP] Update pki generation code to make certificate duration configurable  https://review.openstack.org/63941418:40
*** jsun3 has joined #airshipit18:41
*** JosW has joined #airshipit18:43
*** JosW has left #airshipit18:43
openstackgerritAlexander Hughes proposed openstack/airship-pegleg master: Unwrap managed documents before linting  https://review.openstack.org/63868919:42
*** georgk3 has quit IRC20:19
*** georgk33 has joined #airshipit20:19
openstackgerritAlexander Hughes proposed openstack/airship-pegleg master: [WIP] Update pki generation code to make certificate duration configurable  https://review.openstack.org/63941420:34
openstackgerritJared Miller proposed openstack/airship-maas master: Disable tgt service for maas 2.3  https://review.openstack.org/63943220:35
openstackgerritRick Bartra proposed openstack/airship-divingbell master: Run Divingbell containers as unprivileged  https://review.openstack.org/63943520:48
openstackgerritStacey Fletcher proposed openstack/airship-pegleg master: Unwrap managed documents before linting  https://review.openstack.org/63868920:51
openstackgerritStacey Fletcher proposed openstack/airship-pegleg master: Unwrap managed documents before linting  https://review.openstack.org/63868920:51
openstackgerritRick Bartra proposed openstack/airship-divingbell master: Run Divingbell containers as unprivileged  https://review.openstack.org/63943520:55
evgenyldwalt: Hi Drew, I have an uplift job for treasuremap failing (http://paste.openstack.org/show/746301/) so I was wondering if you can help me to understand if it can be possible related to http://paste.openstack.org/show/746301/ which comes with the latest uplift21:13
evgenyldwalt: sorry, second link should be https://review.openstack.org/#/c/618585/ :)21:15
evgenyldwalt: I also looked into the logs of airship-neutron-test pod, rally finished successfully there.21:17
dwaltevgenyl: Hey! It's possible. A timeout of 300, the new default value for Helm tests in Armada, is large enough for most tests. I have observed that the Neutron and Nova tests are a bit longer than average, so setting a timeout value for those might fix this.21:21
dwaltDoes Helm history shows that the actual Helm test did not timeout?21:21
evgenyldwalt: I've just looked into Pod's description, it finished at 19:53:33 and the error in Armada happened at 20:03:49. How do I find this info in helm? Is there some specific command that I can use?21:25
dwaltI think if you do helm history airship-neutron, I think it will indicate if the test itself timed out21:27
dwaltYou'll probably see SUCCESS though, since you said the logs looked clean21:27
dwalterr, DEPLOYED, not SUCCESS21:28
evgenyldwalt: Yes, it looks good http://paste.openstack.org/show/746307/21:28
dwaltYep, that looks good. We can try bumping the timeout value for the Nova and Neutron tests based on the previous upgrade timeout21:29
dwaltIt looks like it used the default wait timeout, so that would be 90021:30
dwaltI would image it doesn't require the whole value of 900, so we can probably tune that down a bit and be safe21:32
evgenylI've just checked and init + ks-users + the test took 302 seconds, I'm wondering though, why does Tiller returns `pods \"airship-neutron-test\" already exists`with status `FAILURE`?21:35
evgenylWhat does happen under the hood?21:35
Nishant_evgenyl: Is this a GF deployment?21:37
evgenylNishant_: Yes, it is.21:38
dwaltevgenyl: I didn't see any Tiller messages in your paste. Where did you see the Tiller message?21:39
Nishant_evgenyl: I have seen similar issue mostly during an upgrade scenario if the pre-upgrade delete hook for test is not enabled. However with automatic test pod deletion change in place that should be cared for already.21:42
evgenyldwalt: Isn't this message in Armada logs a response from Tiller http://paste.openstack.org/show/746311/ ?21:43
dwaltevgenyl: Sorry! I didn't see the whole paste21:43
dwalttest pod deletion should be automated after this patch: https://review.openstack.org/62931321:45
dwaltI'm assuming your uplift includes it21:45
dwaltbut since there is no wait configuration for this chart, no test pods are getting deleted21:46
Nishant_For GF it shouldn't matter as there would be no pods existing21:46
dwaltThe recommended approach here would be to add the proper wait labels to the chart so that Helm tests do not fail on retries21:46
Nishant_dwalt: Agreed.21:54
Nishant_evgenyl: would be good to check in logs if the test pod was ever run earlier during deployment21:55
evgenylNishant_: Yes, it was run at 19:53:16, and there were three more attempts that failed with "already exists" error at 20:00, 20:01 and 20:03.22:04
evgenylSo the suggestion is to add both wait labels and also increase the timeout for the test, is this correct?22:05
openstackgerritRick Bartra proposed openstack/airship-divingbell master: Run Divingbell containers as unprivileged  https://review.openstack.org/63943522:06
Nishant_evgenyl: I didn't follow as to why the test failed initially, if it was due to a timeout issue then maybe increasing the timeout would make sense22:19
evgenylNishant_: The assumption is this is due to a timeout, I checked the containers start and finish times, and it took about 302 seconds to execute airship-neutron-test, but I'm still wondering why Tiller does not show that it failed to deploy the release due to a timeout...22:21
evgenylBy the way, Nishant_ and dwalt, if I add wait.resources.labels, should I delete upgrade.pre.delete? https://github.com/openstack/airship-treasuremap/blob/master/global/software/charts/osh/openstack-compute-kit/neutron.yaml#L197-L20122:23
dwaltevgenyl: Yes, as Armada can automatically delete test pods now using the wait.labels or wait.resources.labels22:24
dwaltalso, if Helm does not show that the test timed out, it's very possible it only timed out on the Armada side22:24
dwaltIn that case, adding a test timeout and the proper wait labels should be a good, permanent solution22:25
Nishant_evgenyl: the existing upgrade.pre.delete hook in the chart is for `job` type, I am not sure if that is being taken care off in the automatic deletion22:35
openstackgerritRick Bartra proposed openstack/airship-divingbell master: Run Divingbell containers as unprivileged  https://review.openstack.org/63943522:41
openstackgerritEvgeniy L proposed openstack/airship-treasuremap master: Uplift Armada and fix neutron configs  https://review.openstack.org/63946222:41
openstackgerritDrew Walters proposed openstack/airship-treasuremap master: WIP: airskiff: Use global Airship charts  https://review.openstack.org/63521822:42
evgenylNishant_: good, point, I will leave it as is for now.22:42
evgenylNishant_: dwalt Can you please let me know if this makes sense? https://review.openstack.org/#/c/639462/1/global/software/charts/osh/openstack-compute-kit/neutron.yaml22:42
Nishant_evgenyl: LGTM22:47
evgenylNishant_: dwalt Alright, thank you guys, really appreciate your help with that, I'm re-triggering the job and we will see if it helps :)22:49
openstackgerritMichael Beaver proposed openstack/airship-armada master: [WIP] Move tiller into Armada POD  https://review.openstack.org/63278823:03
*** sreejithp has quit IRC23:10
openstackgerritGeorg Kunz proposed openstack/airship-in-a-bottle master: [WIP] Configuration for testing DPDK in multi-node AIAB  https://review.openstack.org/63420723:14
*** michaelbeaver has quit IRC23:34
*** jesusaur has quit IRC23:51
*** jsun3 has quit IRC23:52
*** jsun3 has joined #airshipit23:52
*** DanCrank has quit IRC23:53

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