15:00:56 <gagehugo> #startmeeting openstack-helm
15:00:57 <openstack> Meeting started Tue Dec  8 15:00:56 2020 UTC and is due to finish in 60 minutes.  The chair is gagehugo. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:58 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:00 <openstack> The meeting name has been set to 'openstack_helm'
15:01:14 <gagehugo> #link https://etherpad.opendev.org/p/openstack-helm-weekly-meeting agenda
15:01:16 <gagehugo> o/
15:01:32 <lamt> \o
15:01:43 <miniroy> o/
15:01:47 <stevthedev> yo
15:02:05 <sangeet> \o/
15:03:47 <cliffparsons> o/
15:04:13 <gagehugo> lets get started
15:04:20 <gagehugo> #topic Dec meetings
15:04:47 <gagehugo> This will likely be the last meeting for Dec, with several people out due to holidays
15:05:22 <gagehugo> So I was planning on canceling the 15, 22, 29 meetings
15:05:38 <reddy1> o/
15:05:40 <sangeet> ok
15:05:40 <gagehugo> Is that ok with everyone?
15:05:43 <stevthedev> I can't believe we're at the year end already
15:05:53 <cliffparsons> +1
15:06:03 <reddy1> +1
15:06:49 <gagehugo> The year flew by
15:07:27 <miniroy> +2
15:08:06 <gagehugo> I'll send out an email then cancelling the rest of the year's meetings
15:08:07 <stevthedev> Sounds good though. The next time we'll be chatting here will be 2021 :)
15:08:10 <megheisler> +1
15:08:19 <lamt> +1
15:08:22 <gagehugo> #topic remove older OS releases
15:08:37 <gagehugo> #link https://review.opendev.org/c/openstack/openstack-helm/+/760059
15:09:23 <gagehugo> lamt has graciously made a change to remove the older EOL releases for openstack from our gate testing that came from discussions at the PTG
15:10:02 <gagehugo> However, we also mentioned bumping the chart versions, likely a major chart bump, to signify to end users that we no longer officially support those older releases
15:10:28 <gagehugo> s/major chart/major version number/
15:10:54 <stevthedev> across all of the os charts?
15:11:11 <sangeet> Where are planning to bunp the version? in Charts.yaml?
15:11:13 <gagehugo> Yes, all of them that follow the release schedule
15:11:26 <gagehugo> We still have things like Ocata which is quite old
15:11:45 <gagehugo> heck, we still gate against Rocky which is EoL already lol
15:13:22 <gagehugo> yes, Charts.yaml
15:13:37 <gagehugo> Chart.yaml
15:13:43 <sangeet> :)
15:14:04 <gagehugo> Any thoughts?
15:14:23 <miniroy> so we need some sort of "freeze" period so all the charts can be updated?
15:14:29 <miniroy> and rebase all the open ps after?
15:14:45 <sangeet> https://github.com/openstack/openstack-helm/blob/23c51ce928aaeaa9795b7798dd723fdab1fa4d99/keystone/Chart.yaml#L17 change this to "version: 1.1.3" or "version: 1.0.0"
15:14:48 <sangeet> for example
15:15:41 <gagehugo> I would say 1.1.3 or 0.2.3
15:16:09 <sangeet> Why do we need to do for all the charts .. should we we not be doing only for openstack components?
15:17:19 <reddy1> Updating at a lot of places may not be practical
15:17:20 <sangeet> Never mind "gagehugo: Yes, all of them that follow the release schedule" I got the answer
15:20:00 <gagehugo> Yes, only the openstack services
15:20:53 <gagehugo> If anyone is using osh for older releases they can have a version to pin to
15:22:10 <sangeet> I am wondering when will we change the next majto version? Are going to follow everytime a new stable Openstack release is released? If that is the case then we should increase the majto version to 7 becasue the first code was writen for Ocata
15:22:49 <sangeet> Just a thought .. I am ok with increasing the version by one only
15:23:15 <gagehugo> I think the main idea was to signify things osh supported rather than follow the OS release schedule, but if we do this route it may end up being that
15:24:23 <gagehugo> I'd say just one version increment
15:24:32 <sangeet> sure
15:25:29 <miniroy> or maybe just update the wiki?  https://wiki.openstack.org/wiki/Openstack-helm
15:26:52 <gagehugo> we should do that as well
15:27:23 <miniroy> something similiar to this?  https://docs.openstack.org/puppet-openstack-guide/latest/install/releases.html
15:27:27 <miniroy> just to be consistent I guess
15:27:46 <gagehugo> basically some form of release notes I guess
15:27:53 <gagehugo> but yes
15:28:27 <miniroy> so do we get to come up with some fancy release name of our own?  :)
15:30:08 <sangeet> Name of major hurricanes
15:30:11 <gagehugo> nope
15:31:24 <gagehugo> If no one is really opposed to it, then I guess we can move forward with that
15:31:33 <sangeet> I am good with changing the release
15:32:22 <miniroy> let's go with "Nike"..... per https://en.wikipedia.org/wiki/Victoria_(name)
15:32:43 <gagehugo> haha
15:32:48 <gagehugo> #topic Open Discussion
15:34:39 <gagehugo> Does anyone have anything else to discuss this week?
15:36:40 <lamt> Fixed - https://review.opendev.org/c/openstack/openstack-helm/+/760059
15:37:27 <sangeet> I think I agree with lamt has done in above PS
15:39:08 <miniroy> so we need that release note and force/enforce everyone to rebase their open ps after
15:39:41 <sangeet> Should Hcart mini version increase be enforced here as we do of Infra?
15:40:01 <sangeet> *Chart andnot Hcart
15:40:34 <lamt> the linter script enforces it
15:41:09 <sangeet> is it doing for opensatck-hlem repo also? I am not sure
15:41:11 <miniroy> ok so the linter script will run again before merge then?
15:41:23 <miniroy> or maybe I am over-thinking it
15:41:25 <miniroy> just do it
15:41:32 <miniroy> Go Nike!
15:42:45 <lamt> when do you bump the minor version?
15:43:15 <sangeet> Infra requires it everytime you try to add a new PS
15:43:23 <sangeet> Sorry I meant micro version
15:43:46 <sangeet> I do not know when we would increase minor version
15:47:34 <lamt> any thoughts on when the minor version should be bumped?
15:47:45 <lamt> or we just updated the major and patch version only?
15:49:20 <gagehugo> I was wondering for your ps if we just bump the minor version
15:49:21 <sangeet> We can update the major and patch version only untill we come up with the need of minor version to be changed.
15:49:35 <sangeet> to 0.2.0?
15:49:37 <gagehugo> and maybe when/if we ever move to helm3, bump the major
15:49:40 <lamt> then the question is when do we bump the major version :D
15:50:00 <gagehugo> or maybe when kubernetes 2 comes out
15:50:05 <lamt> lol
15:50:41 <miniroy> I think this change is "major" enough to warrant a major version change
15:52:12 <miniroy> so when helm3 is ready, we should bump it up again as we would likely be dropping/freezing support for older releases
15:52:40 <gagehugo> My thoughts were we will likely bump this 2x a year if we end up following the OS release schedule
15:54:13 <gagehugo> and IMO minor versions are easier to bump
15:54:47 <miniroy> that makes sense, let's just roll with it then
15:55:24 <gagehugo> and we're not really making "major" changes to the charts themselves, simply using the version bump to signify we no longer support X release of openstack
15:57:15 <gagehugo> We can discuss further in Tin's ps, we're about at time
15:57:36 <gagehugo> Hope everyone stays safe and has a happy holidays and happy new year
15:57:51 <gagehugo> #endmeeting