14:00:50 <mattmceuen> #startmeeting airship
14:00:51 <openstack> Meeting started Tue Oct 15 14:00:50 2019 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:54 <mattmceuen> #topic Rollcall
14:00:54 <openstack> The meeting name has been set to 'airship'
14:00:59 <dwalt> o/
14:01:02 <nishantkr> o/
14:01:04 <mattmceuen> Good morning / afternoon / evening everyone!
14:01:04 <dukov> o/
14:01:09 <kskels> o/
14:01:12 <mattmceuen> let's give it just a few minutes for folks to join us
14:01:13 <pramchan> o/
14:01:16 <uzumaki> o/
14:01:28 <mattmceuen> and please add anything you'd like to discuss to the end of our agenda: https://etherpad.openstack.org/p/airship-meeting-2019-10-15
14:01:38 <kirandivekar> o/
14:01:41 <DanCrank> o/
14:01:59 <mattmceuen> We have a lot of new folks here today -- happy to have you!  pramchan, I think you mentioned they're from your team?
14:02:39 <pramchan> yes we have few folks from Delltem and have added questions to ethrpad
14:03:00 <howell> o/
14:03:02 <mattmceuen> fantastic - welcome all
14:03:12 <mattmceuen> ok, let's get started!
14:03:21 <mattmceuen> #topic Moving airship-in-a-bottle remaining items
14:03:33 <mattmceuen> kskels - this is yours, you have the floor
14:03:54 <kskels> oh awesome! it seems it was moved up - but that's great!
14:04:12 <mattmceuen> Yeah sorry - we're waiting on romang for the first topic, I moved it to the end :)
14:04:14 <kskels> there has been many advancements now to airship-in-a-bottle scripts and manifests that is a home for our multinode-gate
14:04:24 <kskels> https://review.opendev.org/#/q/owner:sthussey%2540att.com+status:merged+project:airship/airship-in-a-bottle
14:04:40 <kskels> mostly by scott and they are now by large all merged and some final testing is being done by my team
14:05:21 <kskels> I think it's a good time now to consider moving these scripts to treasuremap and that would then move last peaces from airship-in-a-bottle repo to treasuremap
14:05:41 <kskels> so I would like to discuss if everyone is OK with this, and also if there is anything else important left in the old repo
14:05:56 <kskels> additionally, we would re-brand multinode-gate to virt-seaworthy
14:06:24 <kskels> the site manifests themselves have already been moved https://github.com/airshipit/treasuremap/tree/master/site/seaworthy-virt
14:06:31 <dwalt> I think that's a great idea. Are there any additional jobs we can add to verify some of these changes?
14:06:39 <dwalt> Maybe run the gate setup scrips, etc
14:06:55 <michael-beaver> +1 I would love to get all of that moved out of AIAB
14:07:11 <mattmceuen> agree - thanks for bringing up, kskels.  It was always on our radar to collapse the aiab repo into treasuremap (manifests and tooling) and docs (documentation)
14:07:12 <kskels> right! I would recommend to add the 3rd party Jenkins job similar to our pipelines for Seaworthy/Airsloop and AIAB from treasuremap
14:07:18 <kskels> this would be then 4th pipeline in Foundry
14:07:49 <mattmceuen> but the multinode gate is probably the biggest outstanding effort.  I love the idea of rebranding as seaworthy-virt, since calling everything airship-in-a-bottle has led to confusion
14:08:13 <pramchan> Can some one give us small brief of on Function of AIAB and diff between AIAB & Airskiff, and what is this mutinode gae?
14:08:32 <mattmceuen> Yes, let me try, and talk in "future state" terminology:
14:09:18 <mattmceuen> "airship-in-a-bottle" is a single-node, all-in-one script that you can run in a VM to stand up a airship 1.x genesis node.  It has openstack services on top, and is designed primarily for demo purposes
14:09:55 <kskels> fyi - here are site YAMLs for AIAB - https://github.com/airshipit/treasuremap/tree/master/site/aiab
14:10:25 <pramchan> tanks and now Airskiff
14:10:27 <mattmceuen> "seaworthy-virt" (currently called airship-in-a-bottle multinode) is a multi-node / multi-VM test environment that you can run inside one big containing VM.  It allows for a lot of flexibility in terms of script-based testing, and gets a lot of use by developers as well as CICD pipelines
14:10:54 <mattmceuen> "airskiff" is a lightweight dev/CICD-focused site definition and script, that runs "most of airship 1.x" on top of minikube
14:11:01 <mattmceuen> So airskiff leaves out promenade, drydock, maas
14:11:06 <pramchan> Is seaworthy usable for Airship 2.0?
14:11:15 <mattmceuen> but runs faster and can be used to test the other airship 1 components
14:11:22 <pramchan> I mean seaworrthy-virt
14:11:50 <mattmceuen> the plan for airship 2.0 testability is very similar to seaworthy-virt
14:11:58 <pramchan> Put it simple can any of these tools adapted for Arishp 2.0?
14:12:04 <mattmceuen> In the sense of having "one big VM" inside of which you can run a multi-node airship/k8s cluster
14:12:45 <mattmceuen> Yes, I believe so, but there will be a lot of changes -- they will be similar approaches for sure, but whether we reuse seaworthy-virt scripts or not would take a little thought
14:13:08 <kirandivekar_> Newbie question...Any document which mentions the 1.x to 2.x transition?
14:13:08 <mattmceuen> The manifests themselves for airship 2.0-based virt testing will need to be written from scratch, since they'll all be new
14:13:20 <mattmceuen> not yet kirandivekar_, and great question
14:13:30 <mattmceuen> we're still nailing down the document structure -- ie the "target" of the transition
14:13:51 <mattmceuen> the plan is to have scripting that will do most of the work of converting airship 1 documents to airship 2 documents
14:13:51 <pramchan> OK that helps , then point to thise scripts and we will review wrt vBMC if we can use with airshipctl and ironoc direct bypassing metalkube
14:14:05 <kirandivekar_> Okay, fine.
14:15:00 <mattmceuen> Here is the current scripting for seaworthy-virt:  https://opendev.org/airship/airship-in-a-bottle/src/branch/master/tools/multi_nodes_gate
14:15:37 <mattmceuen> please note that it is not yet called "seaworthy-virt" (since we just decided on that name :)  and is not yet moved into the treasuremap repository
14:15:44 <kirandivekar_> I saw, the spec repo talks about 1.x and 2.x versions. Is there any other repo where the transition is started?
14:16:02 <pramchan> kiran cn you review this and help identify what is sising of "Big VM" in terms of OpenStack neutron flavor
14:16:10 <pramchan> sizing
14:16:19 <mattmceuen> so there is a patchset out to add initial stuff to the v2 branch of treasuremap repo - -that's the first place for the transition
14:16:30 <kirandivekar_> Sure pramchan
14:16:52 <mattmceuen> treasuremap is our "integration" repo, which integrates all the airship 1.x documents (today) via declarative manifests
14:16:59 <pramchan> Matt any idea on current "Big VM" size for Airship 1.0?
14:17:01 <kirandivekar_> Okay, great. Thanks mattmceuen
14:17:33 <mattmceuen> the plan is to have a v2 branch of treasuremap to grow up the new A2.0 docs, and then eventually to move A1.x docs (current master) to a v1 branch, and make v2 the new master.  but that is still a long ways off!
14:19:14 <pramchan> Until then for Airship 2.0 we continue using v2 branch, did I get that right?
14:19:15 <michael-beaver> We usually size them at 24 vCPU, 60 GB, and 200gb storage I think
14:19:45 <kskels> ~300GB disk storage I think but yeah - that's right.
14:19:51 <mattmceuen> hopefully we can reduce that down substantially for Airship 2.0
14:20:09 <mattmceuen> So it can fit inside an openstack-infra zuul-driven VM, which it can't today
14:20:22 <pramchan> Michael super so can we use this as baseline for now? or max requirment call it whichever way
14:20:50 <kskels> additionally, this gate can be run on a bare-metal server (or a powerful VERY linux laptop)
14:21:10 <kskels> which is sometimes very handy during development with using local libvirt/kvm
14:21:18 <pramchan> Is there a Serevr specs for that now and will we need a new server in Zuul gating for this size?
14:21:25 <michael-beaver> Probably yeah, I don't think we are looking to push those requirements any higher
14:22:05 <kirandivekar_> Another newbie question. We are setting up the dev environment with airskiff. Is that okay?
14:22:32 <mattmceuen> pramchan:  I don't think we know how big of a "big vm" we'll need for A2.x yet -- Rodolfo phrased it well I think, we'll need to make 2.0 seaworthy-virt "as small as it needs to be" to fit into zuul infra
14:23:18 <mattmceuen> kirandivekar_: yes for sure!  that is a developer-friendly environment that is in part designed to help people get their feet wet...  airship-in-a-bottle is almost "too easy" from that perspective, it's just one script
14:23:40 <mattmceuen> airskiff is a good way to start seeing what's going on from an airship 1.x deployment perspective
14:23:46 <pramchan> OK is there  currently any limit on Zull Infra, if so is current Big VM is the limit?
14:23:47 <kirandivekar_> Okay, sure
14:25:03 <mattmceuen> pramchan:  there is, but I don't know it off hand -- we may need to research it (unless anyone here knows?)
14:25:56 <mattmceuen> great discussion all - kskels or anyone else, any other discussion on the seaworthy-virt topic?
14:26:04 <uzumaki> will the airskiff devenv work for airshipctl part as well? My understanding is that airshipctl is a purely 2.x thing
14:26:17 <kskels> maybe the last thing to ask to speak up is - https://github.com/airshipit/airship-in-a-bottle/tree/master/deployment_files/site
14:26:29 <mattmceuen> I would not suggest starting with airskiff for 2.x / airshipctl
14:26:31 <kskels> we have moved what we call "demo" in the site
14:26:38 <pramchan> OK please do find and let me know as Airship 2.0 vPOD like testing (airshp2-virt like seaworthy-virt) is needed
14:26:39 <mattmceuen> Probably better to start with airshipctl + minikube
14:26:46 <kskels> is dev/dev-proxy something that is being used by anyone
14:27:04 <kskels> and is that something that we would need to move in future to fully depricate airhsip-in-a-bottle repo?
14:27:21 <pramchan> Yes minikube most our devlopers have installed on their laptops but it does not help in BMC testing
14:27:56 <dwalt> pramchan: is that because it's a single node environment?
14:28:17 <nishantkr> kskels i think scott had changes to remove v1.0 dev from AIAB
14:28:56 <pramchan> not really we need to be able bootsrap muliple nodes for say any underaly or overlay k8s clusters
14:29:03 <kskels> that's great - I have also not heard anyone using that anymore - so I would propose to not move it as I don't see any value it would add right now
14:29:27 <mattmceuen> kskels:  yes I think we can fully deprecate the airship-in-a-bottle repo as soon as we migrate all its stuff to treasuremap and docs
14:30:11 <kskels> awesome! so I will then also put a bit of focus on move effort there to help Alex and get all latest things in
14:30:24 <kskels> so maybe last call for anyone to speak up! :)
14:30:37 <michael-beaver> kskels: I think it would definitely be worth looking into getting seaworthy-virt to work behind a proxy, but I don't think anything in the dev-proxy manifests will help too much with that at this point
14:31:10 <uzumaki> alright, what can we then use as a devenv for working with BMC? for airshipctl that is, suggestions?
14:31:23 <uzumaki> virtual or otherwise
14:31:33 <mattmceuen> pramchan:  pramchan:  I think a combination of the work the dell team has been working on here: https://review.opendev.org/#/c/686389/  combined with a script-based approach (setting up multiple VMs inside a Big VM) like seaworthy-virt does, should do the trick for A2
14:32:09 <mattmceuen> uzumaki:  I'd say give seaworthy-virt a try (in a big VM :) )  and see how it works today -- that will give some good context
14:32:12 <AshuKumar> newbie question : anyone give idea about documentation of "How Airshipctl communicate with Deckhand?"
14:32:24 <mattmceuen> good question with an easy answer!
14:32:38 <pramchan> OK matt we will try seaworthy-virt pointb the link if any
14:32:56 <mattmceuen> it will not -- airshipctl is a new project for airship 2, and deckhand is only for airship 1.
14:33:09 <uzumaki> mattmceuen, i'll check it out
14:33:24 <mattmceuen> Deckhand is essentially replaced by Kustomize (for YAML munging) and apiserver/etcd (for doc storage in cluster) in airship 2
14:34:10 <mattmceuen> pramchan:  seaworthy-virt:  https://opendev.org/airship/airship-in-a-bottle/src/branch/master/tools/multi_nodes_gate
14:34:20 <GarimaM> Please confirm the link to deploy lastest version of Airskiff is correct: https://airship-treasuremap.readthedocs.io/en/latest/airskiff.html#use-airskiff
14:34:20 <pramchan> thanks
14:34:27 <nishantkr> This blog has some good info for Airship 2.0 Arch - https://www.airshipit.org/blog/airship-blog-series-3-airship-2.0-architecture-high-level.html
14:34:47 <AshuKumar> thanks mattmceuen
14:34:54 <kirandivekar_> Thanks nishantkr
14:35:08 <uzumaki> thanks nishantkr
14:35:14 <mattmceuen> GarimaM - yes, I think that's the freshest documentation
14:35:20 <pramchan> next topic : anything we have for RAID in Airship 1.0?
14:35:26 <mattmceuen> please let us know here in the channel or on the ML if you hit any issues!
14:35:38 <shubham_kaushal> Thanks nishankar for sharing link
14:35:45 <mattmceuen> +1 good one
14:36:07 <mattmceuen> #topic     Bios/Raid configurations for ephemeral/target baremetal nodes using airshipctl/redfish/metal3
14:36:16 <GarimaM> Thanks mattmceuen
14:36:31 <mattmceuen> Sure, let's move on to the Bios/Raid item:
14:36:35 <mattmceuen> sure thing GarimaM
14:37:01 <raschid> is seaworthy-virt using metal3/ironic in 2.0?
14:37:28 <openstackgerrit> varagini karthik proposed airship/treasuremap master: [WIP] Integrate postgresql utility container in airship/treasuremap  https://review.opendev.org/688631
14:37:43 <mattmceuen> nope, not yet raschid -- today seaworthy-virt is only geared toward 1.x
14:38:09 <mattmceuen> I'd say let's copy (or rewrite if appropriate) whatever makes sense from seaworthy-virt in the new treasuremap v2 branch
14:38:10 <kskels> in other words - we need to put some work in to adapt seaworthy-virt to v2.0
14:38:21 <uzumaki> agree
14:38:23 <kskels> in some way or form that could be reusing some of the work
14:38:34 <kskels> and then adding some missing parts
14:38:53 <kskels> right now seaworthy-virt is based on libvirt/kvm VMs which has worked well
14:39:05 <uzumaki> with regards to BIOS/RAID configs, do we know if we will use metal3/ironic/redfish? any of these? all of these, in 2.x
14:40:25 <mattmceuen> for BIOS/RAID in 2.x, we will use exactly those three things uzumaki
14:40:54 <mattmceuen> I am not fully clear if it will be metal3->ironic->redfish, or just metal3->redfish for that
14:40:57 <uzumaki> great! any progress yet? who are the guys working on that if any?
14:42:23 <mattmceuen> yes, there have been some ericsson folks from the airship community who have been working toward that; let me find some info:
14:42:29 <nishantkr> most work is currently being done within the airshipctl project, one of the PS related to redfish i see is https://review.opendev.org/#/c/683165/
14:42:47 <howell> As far as metal3 goes, Jerome Brette has been making a lot of progress on generating config. I'll be working with him to get that merged into airshipctl
14:43:01 <uzumaki> howell, good to know!
14:43:10 <mattmceuen> uzumaki:  https://github.com/metal3-io/baremetal-operator/commit/2fc5d88c3e6d31ee8b4ca4bad09b68068a578a6f
14:44:01 <mattmceuen> also for the metal3 dev environment: https://github.com/metal3-io/metal3-dev-env/commit/dca69e0689f4e7c95b5c62cdaedc7c369c302752
14:44:17 <pramchan> Here is what I asked in design call and was told we need not get blocked by 683165 patchset above and continue the work and can rebase it later if some one works on BIOS/RAID/Refish etc.
14:44:30 <uzumaki> Am i right to assume we will ultimately 'add' metal3 BMO to airship 2.x?
14:44:44 <pramchan> yes you are right
14:44:45 <mattmceuen> yep that's right
14:45:42 <uzumaki> got it
14:45:43 <mattmceuen> any other discussion on this one before we keep going, team?
14:46:00 <uzumaki> nothing from me, go ahead!
14:46:09 <mattmceuen> #topic airship approach to integrate BM services like ironic
14:46:14 <pramchan> What systems do we need to use redfish with metal3, is standard k8s dev environment of metal3 suffice?
14:46:15 <mattmceuen> I think we already started on this one :)
14:46:46 <pramchan> Yes lets move on to BM
14:47:36 <mattmceuen> pramchan:  the thing that is needed on top of the "big VM with little VMs" approach is to run virtualized redfish along with that, similarly to this: https://review.opendev.org/#/c/686389/
14:48:11 <kirandivekar_> As deckhand is deprecated, with metal3, any design proposal for this change?
14:48:13 <mattmceuen> I think that^ , along with standard k8s and metal3, should do the trick
14:49:05 <kirandivekar_> Or we will start with design proposal?
14:49:26 <mattmceuen> kirandivekar_:  it's in progress!  good question
14:49:35 <mattmceuen> the gist is this:
14:49:43 <kirandivekar_> Any reference, please?
14:50:10 <mattmceuen> we plan to use kubernetes CRDs for all of our documents used by Airship 2.0
14:50:15 <pramchan> kiran can you add tor bootsrap SIG gdocs
14:50:35 <mattmceuen> the CRDs used for bare metal are the k8s Cluster API, as well as the Metal3 Baremetal API
14:50:48 <kirandivekar_> Okay, fine pramchan
14:51:08 <mattmceuen> So Airship isn't "inventing" any of those docs, but we are collaborating with both those teams to help make sure they contain everything Airship will need
14:51:11 <mattmceuen> https://wiki.openstack.org/wiki/Airship#AIRSHIP_SIG_-_Special_Interest_Meetings
14:51:52 <mattmceuen> We have a weekly design call to define document structure / repo structure (i.e. the new treasuremap site defintions) - SIG YAML - if you'd like to join the discussion
14:52:02 <mattmceuen> they're also recorded (but I think the recordings may expire after a month)
14:52:42 <mattmceuen> what other questions?
14:52:48 <kirandivekar_> Yes, i was part of last SIGYAML, and will continue to join. Thanks
14:52:56 <mattmceuen> perfect
14:53:37 <mattmceuen> ok - romang wasn't able to make it this time, so I'll move his topic to next week's agenda
14:53:59 <pramchan> Rashid did you get your RAID answers with metal3? and good to go
14:54:23 <raschid> Yes we are good to go!
14:55:45 <mattmceuen> #topic Review Requests
14:56:03 <mattmceuen> Here are a number of patchsets - left over from last week!  that could use some review, team:
14:56:07 <mattmceuen> https://review.opendev.org/#/c/676700/ - Spec: Introduce isogen subcommand for airshipctl
14:56:07 <mattmceuen> https://review.opendev.org/#/c/675851/ - Airshipctl: Add logic to isogen subcommand
14:56:07 <mattmceuen> https://review.opendev.org/#/c/679563/ - Airshipctl: Generate cloud init settings
14:56:08 <mattmceuen> https://review.opendev.org/#/c/685049/ airship/docs Add Ansible code formatting documentation
14:56:08 <pramchan> chandra any review requests?
14:56:09 <mattmceuen> https://review.opendev.org/#/c/682050/ - Airship Images: Initial debian based iso builder
14:56:10 <mattmceuen> https://review.opendev.org/#/c/686137/ - Tresuremap v2: Introduce basic directory structure
14:56:11 <mattmceuen> https://review.opendev.org/#/c/682354/ - Airship Images: Add basic CI jobs
14:56:30 <mattmceuen> Yes please, if so paste them here and add them to the agenda as well
14:57:10 <mattmceuen> then with three more minutes:
14:57:16 <mattmceuen> #topic Community Feedback
14:57:40 <mattmceuen> with all our new friends from Dell, especially - what can we do to help you get comfortable in Airship?
14:57:53 <openstackgerrit> Merged airship/treasuremap master: Changed Nova compute endpoint to new version  https://review.opendev.org/686370
14:58:42 <uzumaki> I think the welcome has been great! Have stuff to look at, good content shared today, will let you know if there's anything else. Thanks!
14:59:16 <mattmceuen> Perfect.  We'll be watching here in IRC and on the mailing list for any questions etc you have, and let us know if there's anything else we can help with
14:59:27 <uzumaki> That's great!
14:59:34 <mattmceuen> Any other roundtable items before we adjourn?  Just about out of time
15:00:03 <mattmceuen> Thanks all for joining today!
15:00:14 <uzumaki> Great meeting matt, see you soon!
15:00:16 <kirandivekar_> We are good, thanks mattmceuen
15:00:24 <mattmceuen> have a great week, see you here in the channel till next time
15:00:26 <AshuKumar> Thanks ,got some useful links
15:00:35 <mattmceuen> #topic airshipit.org || General Review Dashboard:  https://review.opendev.org/#/q/project:%255Eairship.*+status:open,n,z
15:00:38 <mattmceuen> #endmeeting