Wednesday, 2018-07-18

*** sthussey has quit IRC00:31
*** marst has quit IRC00:51
*** marst has joined #airshipit01:05
*** vamsis has joined #airshipit01:25
*** vamsis has quit IRC01:29
*** AhmadM has quit IRC02:10
*** roman_g has quit IRC02:29
*** jgu has joined #airshipit02:59
*** vamsis has joined #airshipit03:14
*** vamsis has quit IRC03:27
*** vamsis has joined #airshipit03:43
mattmceuenmarshallmargenau seaneagan https://storyboard.openstack.org/#!/story/2003014 for cfriesen_ 's ask above; can you take a look and give your thoughts?03:48
*** cfriesen_ has quit IRC03:51
mattmceuenAnd please add in any additional pointers into the description for someone to implement it correctly - my armada-fu is not advanced enough to fill that in :)03:55
openstackgerritVan Hung Pham proposed openstack/airship-shipyard master: fix tox python3 overrides  https://review.openstack.org/58345504:42
*** jgu has quit IRC04:56
*** adrianreza has quit IRC04:58
*** d_dej has quit IRC05:09
*** openstackgerrit has quit IRC05:10
*** aagate has quit IRC05:16
*** flaviosr has quit IRC05:16
*** serverascode has quit IRC05:16
*** fdegir has quit IRC05:16
*** b-str has quit IRC05:16
*** portdirect has quit IRC05:16
*** flaviosr has joined #airshipit05:35
*** aagate has joined #airshipit05:35
*** serverascode has joined #airshipit05:35
*** fdegir has joined #airshipit05:35
*** b-str has joined #airshipit05:35
*** portdirect has joined #airshipit05:35
*** vamsis has quit IRC05:37
*** vamsis has joined #airshipit05:40
*** vamsis has quit IRC05:44
*** vamsis has joined #airshipit06:05
*** vamsis has quit IRC06:22
*** cfriesen_ has joined #airshipit06:40
*** vamsis has joined #airshipit06:44
*** cfriesen_ has quit IRC06:45
*** georgk has joined #airshipit06:49
*** goutham has joined #airshipit07:14
*** vamsis has quit IRC07:27
*** vamsis has joined #airshipit08:17
*** vamsis has quit IRC09:02
*** vamsis has joined #airshipit09:07
*** vamsis has quit IRC09:08
*** roman_g has joined #airshipit09:28
*** vamsis has joined #airshipit10:22
*** vamsis has quit IRC10:26
*** eanylin has joined #airshipit10:37
*** vamsis has joined #airshipit11:39
mattmceuenActually cfriesen_ - have you checked out `armada tiller --releases`  for listing releases?  I think it's just armada-managed manifest listing that might be missing - let me know if that's something you need or if releases fits the bill12:08
portdirectIf we were going to list armada manifest managed releases, we probably need armada to start storing state somewhere?12:12
roman_gcfriesen_ is not here atm.12:26
roman_gmattmceuen: is it a bug or feature in irccloud that you and others often reply to persons who are not currently on a channel? )12:27
portdirectroman_g: it's pretty common in openstack12:29
portdirectAs the channels are logged12:29
portdirecthttp://eavesdrop.openstack.org/irclogs/%23airshipit/%23airshipit.2018-07-18.log.html12:29
roman_gGot it. But I'm not sure that one would go to logs and search his/her nickname for mentions.12:30
*** openstackgerrit has joined #airshipit12:30
openstackgerritSmruti Soumitra Khuntia proposed openstack/airship-shipyard master: A new Shipyard status API and CLI  https://review.openstack.org/58215612:30
roman_gportdirect: re: armada to start storing state somewhere - in annotations?12:31
portdirectThat's one possibility12:32
portdirectOr using a crd/configmap12:33
portdirectTheres lots of ways to skin that cat, but this has always been the hurdle that has to be overcome to start getting these features added12:34
portdirectAn alternate would be to have an 'armada get -f template.yaml' type command12:35
portdirectThat would be somewhat analogous to similar kubectl commands12:36
openstackgerritSmruti Soumitra Khuntia proposed openstack/airship-shipyard master: A new Shipyard status API and CLI  https://review.openstack.org/58215612:42
openstackgerritSmruti Soumitra Khuntia proposed openstack/airship-shipyard master: A new Shipyard status API and CLI  https://review.openstack.org/58215612:44
*** sthussey has joined #airshipit13:47
*** eanylin has quit IRC13:55
*** jgu has joined #airshipit14:02
*** jgu has quit IRC14:05
*** jgu has joined #airshipit14:06
*** vrv_ has joined #airshipit14:14
*** vamsis has quit IRC14:26
*** vamsis has joined #airshipit14:28
*** aaronsheffield has joined #airshipit14:33
*** vamsis has quit IRC14:33
seaneaganmattmceuen: I added my thoughts to https://storyboard.openstack.org/#!/story/200301414:40
seaneaganre: cfriesen_'s ask about rollback of whole manifest, that has been discussed, but would similarly require armada to track manifest applications and their releases14:45
sthusseywhat does it mean to rollback a manifest?14:50
portdirectsthussey: https://github.com/kubernetes/helm/blob/master/docs/helm/helm_rollback.md14:50
portdirectthough i think in an airship world, it may make more sense to roll-forward to the previous config...14:51
sthusseymanifest 1 = [chart A(overrides X)], manifest 2 = [chart A(overrides X')]. Apply manifest 1, apply manifest 2, rollback manifest 114:51
sthusseywhat is the end result?14:51
*** vamsis has joined #airshipit14:52
portdirecti dont think thats possible14:52
portdirectyou need to have a revision history in tiller to roll back to14:52
portdirectbut for this to have real world value therea a lot that needs to be acounted for that helm cannot do14:53
portdirecteg potential db migrations etc14:53
*** goutham has quit IRC14:55
*** cfriesen_ has joined #airshipit14:55
sthusseyMostly my point - I'm not sure that since rollback is basically a proxy for helm/tiller functionality today and the manifest construct doesn't exist in helm that 'rollback a manifest' may not have a clear meaning15:20
sthusseyAnd just issuing a helm rollback for every chart resulting from a manifest may not be the right path15:21
*** jgu has quit IRC15:27
*** jgu has joined #airshipit15:27
*** jgu has quit IRC15:31
*** vamsis has quit IRC15:57
*** georgk has quit IRC15:59
*** vamsis has joined #airshipit16:09
cfriesen_sthussey: as I understand it, armada is supposed to manage a set of helm charts with interdependencies and triggers and such.  It seems odd to me that you can "apply" a manifest (which will either do an install or upgrade of the underlying charts) but you can't do the equivalent of helm's list/status/inpect/rollback commands.16:28
cfriesen_if I do an "apply" of a new manifest and it fails, how do I get back to the previously-working state?  Without a manifest rollback I need to keep the previous version of the manifest around in external tooling so I can "apply" it again.16:29
cfriesen_that's doable, but it's different from helm (and armada bills itself as a helm client replacement)16:30
openstackgerritMark Burnett proposed openstack/airship-promenade master: Enable etcd helm test to run on non-ready nodes  https://review.openstack.org/58366116:32
openstackgerritMark Burnett proposed openstack/airship-promenade master: Tolerate unready endpoints for apiserver service  https://review.openstack.org/58366216:32
openstackgerritMark Burnett proposed openstack/airship-promenade master: Fix broken validatedesign endpoint  https://review.openstack.org/58366316:32
openstackgerritMark Burnett proposed openstack/airship-promenade master: Add liveness probe to kube-proxy  https://review.openstack.org/58366416:32
cfriesen_similarly, it seems like I'd need to have external tooling to even keep track of what manifests have been applied since there's no way to list them.16:35
openstackgerritHari proposed openstack/airship-shipyard master: Block site_update if there is no host in MaaS/Dryd  https://review.openstack.org/58366516:46
*** vrv_ has quit IRC17:33
sthusseyno disagreement. will just need to clearly spec out what rolling back a manifest means17:40
*** vamsis has quit IRC18:21
*** felipemonteiro_ has joined #airshipit19:24
*** felipemonteiro_ is now known as felipemonteiro19:24
*** felipemonteiro_ has joined #airshipit19:30
*** felipemonteiro has quit IRC19:33
openstackgerritAhmad Mahmoudi proposed openstack/airship-in-a-bottle master: Updated dev-minimal to deploy behind proxy  https://review.openstack.org/58266519:33
*** felipemonteiro_ has quit IRC19:50
*** felipemonteiro_ has joined #airshipit19:50
*** jgu has joined #airshipit20:01
*** jgu has quit IRC20:02
cfriesen_I tried running the armada deployment scripts in openstack-helm/tools/deployment/armada and I notice that it didn't set up any kubernetes resources (ie requests/limits for cpu/memory).  Is this intentional?  How is it happening given that the openstack-helm charts have default resources in them?  (Or is armada not using those helm charts?)20:09
sthussey@cfriesen_ did you override this default? https://github.com/openstack/openstack-helm/blob/803faedac0866535e84d08bef2ee22f67c447ff5/heat/values.yaml#L101620:12
cfriesen_sthussey: ah, that's probably it.  thanks.20:17
*** vamsis has joined #airshipit20:21
*** jgu has joined #airshipit20:26
*** vamsis has quit IRC20:26
*** felipemonteiro__ has joined #airshipit20:48
*** aaronsheffield has quit IRC20:49
*** felipemonteiro_ has quit IRC20:52
openstackgerritMarshall Margenau proposed openstack/airship-armada master: Wait for jobs to complete  https://review.openstack.org/58373820:55
cfriesen_Starting with my armada-installed openstack-helm, as a test I ran "armada apply /tmp/armada-osh.yaml --set chart:mariadb:values.pod.resources.enabled=true"   This resulted in a new helm release for osh-mariadb with kubernetes resources reserved.  (As expected.)20:59
cfriesen_However, it also resulted in new helm releases for osh-memcached, osh-openstack-ceph-config, and osh-openstack-ingress-controller, and the overall armada call seems to have hung.20:59
*** jgu has quit IRC21:00
cfriesen_what's the bug report procedure?  storyboard story?21:00
sthussey@mattmceuen ^21:02
openstackgerritMarshall Margenau proposed openstack/airship-armada master: Removing dead code.  https://review.openstack.org/58374021:04
*** felipemonteiro__ has quit IRC21:07
*** felipemonteiro__ has joined #airshipit21:07
marshallmargenau@cfriesen_  when armada looks hung, it's usually a result of it waiting on something that wasn't defined quite right in your charts21:11
marshallmargenaui believe it should wait 15 minutes by default unless you specified something different21:12
marshallmargenauthe logs should also show you what namespace and label selectors (including none, which is the most common cause) that it's currently waiting to resolve21:12
marshallmargenauwill defer to @mattmceuen or @mark-burnett on bug report procedure21:13
cfriesen_marshallmargenau: are there logs other than stdout?  the last stdout line is just "2018-07-18 20:26:48.465 24313 INFO armada.handlers.tiller [-] Deleting pod osh-keystone-rabbitmq-test in namespace: openstack"21:16
cfriesen_marshallmargenau: the manifest/charts are untouched from when I initially ran the armada scripts to bring up openstack-helm, the only change should have been to enable resources for mariadb.21:17
cfriesen_and it's been hung for almost an hour21:18
*** felipemonteiro__ has quit IRC21:28
cfriesen_doing ctrl-C and then rerunning the same command seems to now allow it to get further.21:28
cfriesen_looking at the helm charts from the two releases, it looks like the output of "helm get <release> --revision <X>" for the two revisions is functionally identical but reordered slightly.  I suspect this caused something to think it had changed when it actually hadn't.22:15
cfriesen_the above command for the osh-keystone helm release results in a yaml file with 63 docs, and of these six were reordered between the two releases.22:19
cfriesen_For osh-memcached though only the revision number and the release timestamp were different.22:24
openstackgerritBryan Strassner proposed openstack/airship-shipyard master: [WIP] Add redeploy_server processing  https://review.openstack.org/58379323:02
*** vamsis has joined #airshipit23:14
*** vamsis has quit IRC23:18
openstackgerritFelipe Monteiro proposed openstack/airship-pegleg master: Add git and branch revision support to pegleg  https://review.openstack.org/58265223:34

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