14:00:13 <nishantkr> #startmeeting airship 14:00:14 <openstack> Meeting started Tue Oct 8 14:00:13 2019 UTC and is due to finish in 60 minutes. The chair is nishantkr. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:17 <openstack> The meeting name has been set to 'airship' 14:00:24 <nishantkr> #topic Rollcall 14:00:30 <dwalt> o/ 14:00:37 <howell> o/ 14:00:37 <mattmceuen> o/ GM+GE 14:01:06 <nishantkr> Hello everyone ! so far we have no agenda items, so please add anything you would like to discuss here - https://etherpad.openstack.org/p/airship-meeting-2019-10-08 14:02:01 <mattmceuen> May be a light crowd to go along with our light agenda, a number of folks are travelling or ill today 14:02:20 <nishantkr> yup looks like 14:03:03 <dwalt> you lucked out on your day to host nishantkr ;) 14:03:11 <mattmceuen> #smart 14:03:11 <nishantkr> haha 14:04:24 <nishantkr> since we have no agenda items to discuss specifically, If anyone would like to discuss on what they are working on and would like to share it here then please do, I can go first 14:04:38 <mattmceuen> sounds good to me 14:05:31 <nishantkr> I am working on efforts for Airship to move towards kubernetes 1.16.0 14:05:43 <nishantkr> Here are the PS out there for the same - https://review.opendev.org/#/q/topic:k8s-1.16+(status:open+OR+status:merged) 14:05:44 <mattmceuen> ++ 14:06:07 <mattmceuen> are those ready for some review, nishantkr? 14:06:22 <nishantkr> yup some of them are ready for review 14:06:34 <nishantkr> I am doing another round of testing 14:06:47 <howell> on the same note, k8s-entrypoint is moving to 1.16. I had to push another PS to force the gates to kick off, so its +2's are gone :( 14:06:56 <howell> PS here https://review.opendev.org/#/c/686829/2 14:07:05 <dwalt> do we need to make any changes to the version of Helm we are using for K8s 1.16? 14:07:43 <nishantkr> nope i did not make any changes to helm version and i was able to get a succesfull run of virtual seaworthy 14:07:44 <howell> dwalt: possibly, there was some weirdness with tiller. Let me find the PR 14:07:52 <nishantkr> sounds good howell 14:08:06 <roman_g> o/ 14:08:48 <mattmceuen> o/ roman_g 14:08:52 <roman_g> I remember someone told that docker should be upgraded to use newer k8s 14:08:59 <roman_g> Scott may be 14:09:04 <howell> here we go, not sure if this actually affects us though: https://github.com/helm/helm/pull/6462 14:09:21 <nishantkr> I mostly followed the release notes and deprecated notes for each version starting 1.13 14:09:24 <nishantkr> https://kubernetes.io/docs/setup/release/notes/#deprecations-and-removals 14:10:08 <sthussey> That issue won't affect airship 14:10:09 <dwalt> howell: ah, I see. So we are okay then since we have our own Tiller chart? 14:10:12 <sthussey> As we don't use helm init 14:10:27 <nishantkr> Majority of the changes are related to charts using apiversions which are deprecated and not supported in k8s 1.16 14:10:42 <nishantkr> Along with some kubelet params which are deprecated as well 14:10:46 <dwalt> The only gap I can think of is Airskiff - but we use the OpenStack-Helm minikube scripts. They're also making the transition to K8s 1.16 already. 14:10:50 <sthussey> But we should likely upgrade tiller as any new APIs in 1.15 or 1.16 likely won't be supported in Helm 1.14.x 14:12:15 <sthussey> though it doesn't look like there is a helm 2.x release supporting Kubernetes 1.16 14:12:30 <mattmceuen> hmm that's unfortunate 14:12:35 <nishantkr> I think followed by this change we are also planning to move towards dynamic kubelet config, not sure if anyone has already started working on it 14:12:44 <openstackgerrit> Jagan Mohan Kavva proposed airship/porthole master: Chart/Dockerfile for etcdctl Utility Container https://review.opendev.org/674680 14:13:31 <sthussey> I'm not sure if that is a hard drive to helm 3.x or indicates kubernetes hasn't added any net new API resources since 1.14 14:13:44 <seaneagan> `helm init` was broken for kubernetes 1.16, but airship doesn't use that. I'm not aware of any other issues with e.g. helm 2.14.3 against kubernetes 1.16 that have been raised 14:14:42 <seaneagan> but yeah would need to update tiller for kubernetes 1.16 client lib once that's released 14:15:07 <nishantkr> Yup seaneagan 14:15:23 <nishantkr> Any other questions on this topic? 14:15:24 <sthussey> What is the stance from Airship on components expected to be retired for Airship 2.0? 14:15:38 <sthussey> Sorry, ^ is another topic unrelated 14:16:11 <nishantkr> no problem sthussey, we are going in an adhoc manner today 14:17:09 <mattmceuen> plan is to have an upgrade path and/or migration period where both are supported 14:17:37 <nishantkr> don't think we have discussed about that yet for individual components but there was some discussion around treasuremap and i think we are going ahead with creating separate directories for Airship 2 documents 14:18:02 <sthussey> Someone has inquired about the MAAS chart as an isolated use-case 14:18:18 <jamesgu__> how long do we plan to support airship 1.0 components after 2.0 is released? 14:18:22 <sthussey> But I can't in good conscience recommend they use it if it will go into cold storage in less than 12 months 14:18:34 <mattmceuen> yeah, for treasuremap, there is a plan to create a 2.0 specific directory; and a separate branch for that directory until it gets off the ground 14:19:24 <sthussey> Something like a per-component roadmap may be worthwhile 14:19:44 <sthussey> Around how long things like security fixes, gate maintenance, etc... will go on 14:19:57 <mattmceuen> that's a good point sthussey. If folks are still getting "non-airship" use out of airship widgets, I have no problems with leaving them available (albeit potentially with less support). I think Plan A would be to encourage folks to migrate to Airship 2.0 though, in part or in whole, when the time comes 14:20:14 <mattmceuen> or, working with others to find new homes for projects -- like we did with k8s-entrypoint 14:21:00 <mattmceuen> jamesgu__: I don't think that's been formally determined beyond "only as long as we need to". I think that's still in "cross that bridge when we get to it" territory 14:21:36 <mattmceuen> the idea is to not support two Airships, though, and provide a smooth migration path, so that should minimize the time spent supporting two versions substantially 14:22:12 <sthussey> That only makes since in terms of a monolith. There is no migration path if your use case is 'deploy Canonical MAAS inside Kubernetes' 14:22:20 <mattmceuen> agree 14:22:20 <openstackgerrit> Merged airship/kubernetes-entrypoint master: Bump Kubernetes version to 1.16. https://review.opendev.org/686829 14:22:27 <sthussey> A cluster-api operator using Ironic isn't going to help 14:22:59 <sthussey> I'll just send this fellow to the discussion list, he can work with the directional committees 14:23:13 <nishantkr> yup, thanks for bringing that topic sthussey, it's something we need to discuss and determine formally 14:23:26 <mattmceuen> although I would encourage the maas team to integrate with Metal3 / Cluster API as well to remain a compelling in-k8s provisioner 14:24:39 <nishantkr> ok i do see one agenda item from pramchan 14:24:48 <nishantkr> #topic Any preferred IDE for go airship team uses 14:25:21 <mattmceuen> speaking for the entire team: vim, full stop 14:25:33 * mattmceuen ducks 14:25:41 <nishantkr> haha 14:26:10 <jamesgu__> vim does have a go plugin :-) 14:26:34 <dwalt> I won't throw anything at you for that one mattmceuen :) 14:26:58 <mattmceuen> howell goes the most these days, what do you use howell? 14:27:49 <mattmceuen> in any case though, we don't want to tie airship to any ide in any way shape or form 14:28:27 <howell> as far as vim plugins, I use vim-go and ALE. They work together pretty nicely 14:28:33 <pramchan> Yes I am reviewing your comments 14:28:43 <mattmceuen> awesome 14:28:56 <mattmceuen> maybe I was speaking for the team after all 14:29:16 <openstackgerrit> Jagan Mohan Kavva proposed airship/porthole master: Chart/Dockerfile for etcdctl Utility Container https://review.opendev.org/674680 14:29:40 <nishantkr> anything else you would like to discuss on that pramchan? 14:30:43 <pramchan> Sure any one has any template for airship project for Komodo editor? 14:31:06 <pramchan> For Go specific , I was trying to use 11.1 version 14:32:41 <howell> I've never even heard of that editor, sorry pramchan 14:33:04 <sthussey> goland is pretty popular in general go dev 14:33:06 <pramchan> One more my teams wanted to use Intelli-J for IDE , I just wanted to see what is the best opensource editor besides vimeo or vi-go ALE mentioned above. 14:33:09 <sthussey> not free though 14:33:09 <howell> it seems like the go community has settled on vim, vscode, and goland as he primarty editors 14:34:37 <sthussey> if you want to get really close to go, you can use 'acme' which is the preferred editor of Rob Pike, creator of Go 14:36:00 <pramchan> Thanks then I will settle for one of above what you use, unless Komodo and IntelliJ teams 14:36:16 <howell> warning about acme: it doesn't use a monospace font 14:36:23 <howell> at least, not by default 14:36:40 <mattmceuen> one thing to add to our ad-hoc agenda today: review requests. It's a mix of ones from last week that are still outstanding, plus reiterating the k8s 1.16 PS that were mentioned up above 14:36:40 <pramchan> Decide to justify some compelling reasons to use their tools 14:36:44 <mattmceuen> Requests for review: 14:36:44 <mattmceuen> Leftovers from last week! 14:36:44 <mattmceuen> https://review.opendev.org/#/c/676700/ - Spec: Introduce isogen subcommand for airshipctl 14:36:45 <mattmceuen> https://review.opendev.org/#/c/675851/ - Airshipctl: Add logic to isogen subcommand 14:36:46 <mattmceuen> https://review.opendev.org/#/c/679563/ - Airshipctl: Generate cloud init settings 14:36:47 <mattmceuen> https://review.opendev.org/#/c/685049/ airship/docs Add Ansible code formatting documentation 14:36:48 <mattmceuen> https://review.opendev.org/#/c/683209/ pegleg add support for global encryption 14:36:49 <mattmceuen> New review requests: 14:36:50 <mattmceuen> https://review.opendev.org/#/q/topic:k8s-1.16+(status:open+OR+status:merged) - k8s 1.16 14:36:51 <mattmceuen> https://review.opendev.org/#/c/686829/ k8s-entrypoint to 1.16 14:36:54 <nishantkr> great, thanks pramchan hopefully you got some answers 14:37:21 <pramchan> Did and thanks will use the guidance. 14:37:27 <nishantkr> yup please take out some time and review those PS 14:37:36 <nishantkr> #topic Roundtable 14:37:51 <nishantkr> Anything else someone would like to discuss/share? 14:39:10 <roman_g> I'm "YAML programmer", I have no preference of text editor and can work with pretty much all of those popular ones 14:39:25 <roman_g> /sarcasm 14:39:27 <mattmceuen> lol 14:39:40 <nishantkr> ok good meeting guys from our almost "zero" agenda. 14:39:44 <nishantkr> Thanks for joining 14:39:56 <nishantkr> #endtopic 14:39:57 <roman_g> Thanks everyone :) 14:40:02 <dwalt> thanks nishantkr and team! 14:40:02 <nishantkr> #endmeeting