14:02:37 <mark-burnett> #startmeeting airship
14:02:38 <openstack> Meeting started Tue Oct  9 14:02:37 2018 UTC and is due to finish in 60 minutes.  The chair is mark-burnett. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:02:41 <openstack> The meeting name has been set to 'airship'
14:02:42 <openstack> b-str: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
14:02:43 <openstack> mattmceuen: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
14:02:44 <mattmceuen> lol
14:02:45 <mark-burnett> Hey all, sorry for the delay
14:03:09 <mattmceuen> this meeting is so started
14:03:21 <mark-burnett> Here's the nascent etherpad for today: https://etherpad.openstack.org/p/airship-meeting-2018-10-09
14:04:31 <aaronsheffield> 0/
14:05:01 <dwalt> o/
14:06:27 <b-str> #topic Representation at OpenStack Foundation Joint Leadership Meeting
14:06:42 <mark-burnett> #topic Representation at OpenStack Foundation Joint Leadership Meeting
14:07:13 <hogepodge> I added that
14:07:32 <hogepodge> There’s a joint leadership meeting at the Berlin summit.
14:07:56 <hogepodge> Airship should send one or two people to represent the project if possible
14:08:00 <portdirect> alanmeadows, mattmceuen and myself will be in berlin
14:08:05 <mattmceuen> +1
14:08:42 <mattmceuen> Thanks for the heads up hogepodge, I can help with that
14:09:01 <hogepodge> Agenda still hasn’t been set, but if someone can reach out to Alan to rsvp that would be great. I’ll also be at that meeting as a foundation rep supporting new projects
14:09:22 <hogepodge> Thanks. Unless there are questions that’s it for me
14:09:46 <mattmceuen> I'll probably have questions after I read it more closely / think about it more :)
14:10:11 <hogepodge> There’s no agenda yet, but it should start forming up soon
14:10:54 <mark-burnett> Ok, let's continue new business
14:11:11 <mark-burnett> #topic WIP tempest plugin for Airship
14:11:52 <mattmceuen> Ah that is mine
14:12:31 <mattmceuen> Just as an FYI (and felipemonteiro probably has more info on this if anyone's interested) -- there is a WIP of a tempest plugin for Airship
14:12:40 <mattmceuen> https://github.com/att-comdev/airship-tempest-plugin
14:13:21 <openstackgerrit> Bryan Strassner proposed openstack/airship-shipyard master: [WIP] Add notes processing to the Shipyard API+CLI  https://review.openstack.org/608087
14:13:24 <mattmceuen> Rick Bartra is the main author; the goal is to get it into openstack infra, but he's thinking it would be wise to get automated gating set up around it prior to / same time as introducing the project to infra
14:13:43 <felipemonteiro> O/
14:13:53 <mattmceuen> I'm told it has 100% coverage of Shipyard APIs so far - so that's an awesome start since that's the front door to airship!
14:14:39 <mattmceuen> That's all I have - @hogepodge does that sound like a good general approach (plan to move into openstack infra when it's possible to gate with it)?
14:15:03 <portdirect> why not move earlier?
14:15:30 <mattmceuen> Mr Bartra would need to be here to share his thoughts :)  he's not in throwing distance, is he felipemonteiro?
14:15:44 <roman_g> Noteworthy Development Items
14:15:50 <roman_g> oops. sorry
14:16:16 <hogepodge> Yes, plus that sets the project up for creating a trademark program with existing tools
14:16:57 <hogepodge> You can make it a non voting job as you develop
14:17:10 <felipemonteiro> mattmceuen: there are some caveats related to the statement "100% shipyard test coverage"
14:17:29 <mattmceuen> to make sure I understand chris - you're saying sooner-into-infra-is-better, then iterate?
14:17:51 <mattmceuen> 99.999% felipemonteiro? :)
14:18:03 <hogepodge> You don’t have to wait. It’s really up
14:18:20 <felipemonteiro> 1) There are two types of tests in that repo: a) API tests and b) RBAC tests
14:18:30 <felipemonteiro> 2) The API tests are nowhere near 100% test coverage
14:18:31 <hogepodge> To you. I’m always in favor of more testing
14:18:53 <mattmceuen> Awesome - I'll pass on that feedback.  I'm with ya.
14:19:22 <felipemonteiro> 3) The RBAC tests approximate 100% coverage, but aren't complete tests insofar as the payloads aren't complete, so the tests coerce exceptions from the API, but consider it a pass so long as 403 isn't raised
14:19:22 <mattmceuen> ahh thanks for the clarification felipemonteiro
14:19:44 <hogepodge> Consult with infra also, they can give good guidance and really like that airship team works with them
14:19:57 <mattmceuen> +1
14:20:11 <mark-burnett> Is there a desire to keep this in its own repo rather than with each project?
14:20:22 <mattmceuen> Ha that was my question to Rick yesterday too
14:20:27 <mark-burnett> I'm not really expressing a particular desire here
14:20:43 <mattmceuen> Turns out the overall direction is consolidating toward separate projects for test plugins, let me get the link w/ justification...
14:20:43 <mark-burnett> Just seems at odds with "each project stands alone", though I know that OS has done various things with tempest in the past
14:20:55 <mark-burnett> Ok, so there's some discussion anyway
14:21:31 <mattmceuen> https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html
14:21:44 <felipemonteiro> I think it should be a separate repo for all Airship components' integration tests, as otherwise you get major cross-repo dependency just to do joint testing. I wouldn't recommend it either as we would want standardization in the test implementation and a separate repo is better for that.
14:22:44 <mattmceuen> Sounds good to me, resident QA Core! :)
14:23:04 <mattmceuen> That's all from me mark-burnett on this - thanks
14:23:21 <mark-burnett> Ok
14:23:25 <mark-burnett> #topic Container Images get built from the same code multiple times
14:23:34 <mark-burnett> I think this is from roman_g
14:23:41 <roman_g> Yes, from me.
14:24:00 <mark-burnett> The short answer is that these are probably "built separately" on the same job, so there isn't duplicate work
14:24:15 <evrardjp> Just a little node based on that title, it could be possible to re-use jobs in different projects ...
14:24:26 <evrardjp> mark-burnett: is airship in the same zuul tenant as openstack for now?
14:24:42 <portdirect> yes
14:25:47 <roman_g> mark-burnett: but it still gets different images to be published.
14:26:04 <roman_g> so is it a bug which needs to be fixed, or it's a feature?
14:26:49 <mark-burnett> Hmm, good question
14:27:22 <mark-burnett> Certainly worth a look
14:27:52 <roman_g> normally I would do "docker build ...:latest; docker tag ...:git-commit-id; docker tag ...:master; docker publish ...:latest; docker publish ...:git-commit-id; docker publish ...:master"
14:28:25 <ethfci_> Hello,    i am stucked at https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html#promenade-bootstrap (can't connect to 127.0.0.1)
14:28:26 <mark-burnett> Sure
14:28:36 <roman_g> the last two "docker publish ..." actually do not run, as docker registry api responds that it already has thise layers, and just adds tag
14:29:14 <mark-burnett> I think we can work on this off-line from the meeting
14:29:31 <roman_g> ok. will Slack you.
14:29:36 <roman_g> next topic
14:30:02 <mattmceuen> ethfci_ thanks for sharing that - probably need to dig into some logs / details, can you please share those after the meeting?
14:30:17 <mark-burnett> #topic Noteworthy Development Items
14:30:31 <mark-burnett> Just a reminder to add notes to the development update: https://etherpad.openstack.org/p/airship-dev-update-2018-10-05
14:30:42 <mark-burnett> I haven't had a chance to work on that actually, so still time to add
14:31:27 <mark-burnett> #topic roundtable
14:31:30 <mark-burnett> Any other topics?
14:31:32 <roman_g> mardim <-- started to work on Ironic driver
14:31:49 <mattmceuen> Hey did we touch on the wiki?
14:31:55 <roman_g> No.
14:32:03 <mattmceuen> And do we have Lindsey here perchance?
14:32:48 <mark-burnett> No, we don't
14:33:03 <mark-burnett> I wasn't sure that anyone else had anything to say atm other than check it out.
14:36:10 <b-str> Anyone have any other topics?
14:36:33 <hogepodge> Yes
14:36:54 <felipemonteiro> I'd like to discuss reintegrating 3rd party CI with Airship
14:37:35 <felipemonteiro> I think that we should properly configure it to take advantage of testing we're doing downstream in Zuul - and that requires publicly reporting the CI results, etc.
14:37:45 <felipemonteiro> In Jenkins*
14:37:56 <hogepodge> In case you missed it, there’s a community meeting on Wednesday morning. jbryce and ttx will be covering new project governance at the Foundation level.
14:38:43 <roman_g> AFAIK there were plans to build voting gates with Zuul (instead of Jenkins) in AF lab. I have no other information on that.
14:39:35 <openstackgerrit> Felipe Monteiro proposed openstack/airship-deckhand master: docs: Elaborate on document layering in documentation  https://review.openstack.org/578554
14:39:57 <mark-burnett> @felipemonteiro I agree with you, it would be great to get that re-integrated
14:40:18 <mark-burnett> We actually have a bunch of the CICD team in St Louis today -- I'll ask them what they think we need to do to move forward with that
14:40:24 <openstackgerrit> Felipe Monteiro proposed openstack/airship-deckhand master: docs: Elaborate on document layering in documentation  https://review.openstack.org/578554
14:40:35 <felipemonteiro> Nice!
14:41:22 <felipemonteiro> I think the main blocker was reporting the results publicly (without needing any bells and whistles to see it)
14:41:30 <mark-burnett> I suspect you're right
14:41:42 <felipemonteiro> And otherwise properly registering airship-ci but that's more paperwork than anything (not a blocker)
14:42:46 <mark-burnett> Ok, anything else?
14:43:32 <evrardjp> none
14:43:51 <roman_g> nothing
14:47:15 <mark-burnett> #endmeeting