Thursday, 2018-07-19

*** felipemonteiro has joined #airshipit00:17
*** felipemonteiro has quit IRC00:24
*** felipemonteiro has joined #airshipit00:36
*** felipemonteiro has quit IRC00:57
*** jgu has joined #airshipit01:20
*** vamsis has joined #airshipit01:26
*** vamsis has quit IRC01:31
*** evrardjp has quit IRC01:44
*** evrardjp has joined #airshipit01:49
*** evrardjp has quit IRC02:02
*** evrardjp has joined #airshipit02:08
*** vamsis has joined #airshipit02:16
*** vamsis has quit IRC02:36
*** felipemonteiro has joined #airshipit02:40
*** vamsis has joined #airshipit02:53
*** felipemonteiro has quit IRC02:59
*** vamsis has quit IRC03:02
*** vrv_ has joined #airshipit03:09
*** vamsis has joined #airshipit03:18
*** vamsis has quit IRC03:20
*** vamsis has joined #airshipit03:37
*** roman_g has quit IRC03:44
*** felipemonteiro has joined #airshipit03:47
*** sthussey has quit IRC03:57
*** felipemonteiro has quit IRC04:37
*** felipemonteiro has joined #airshipit04:44
*** felipemonteiro has quit IRC04:55
*** jgu has quit IRC05:00
*** felipemonteiro has joined #airshipit05:01
*** vrv_ has quit IRC05:18
*** fdegir has quit IRC05:29
*** fdegir has joined #airshipit05:29
*** b-str has quit IRC05:29
*** serverascode_ has joined #airshipit05:30
*** aagate has quit IRC05:30
*** serverascode has quit IRC05:30
*** portdirect has quit IRC05:30
*** portdirect_ has joined #airshipit05:30
*** portdirect_ is now known as portdirect05:30
*** b-str has joined #airshipit05:30
*** flaviosr has quit IRC05:31
*** portdirect is now known as Guest7295205:32
*** flaviosr has joined #airshipit05:45
*** aagate has joined #airshipit05:45
*** vamsis has quit IRC05:47
*** felipemonteiro has quit IRC05:56
*** vamsis has joined #airshipit06:08
*** vamsis has quit IRC06:27
*** vamsis has joined #airshipit06:29
*** georgk has joined #airshipit06:53
*** openstackgerrit has quit IRC07:04
*** vamsis has quit IRC07:11
*** goutham has joined #airshipit07:22
*** vrv_ has joined #airshipit07:23
*** vamsis has joined #airshipit07:45
*** roman_g has joined #airshipit08:12
*** goutham has quit IRC08:16
*** goutham has joined #airshipit08:32
*** vamsis has quit IRC08:36
*** vamsis has joined #airshipit08:40
*** goutham has left #airshipit09:31
*** vamsis has quit IRC09:32
*** vrv_ has quit IRC09:32
*** vamsis has joined #airshipit09:37
*** vamsis has quit IRC10:05
*** vamsis has joined #airshipit10:27
*** vamsis has quit IRC10:34
*** vamsis has joined #airshipit10:37
*** georgk has quit IRC10:53
*** vamsis has quit IRC11:06
*** georgk has joined #airshipit11:08
*** vamsis has joined #airshipit11:15
*** vamsis has quit IRC11:17
*** vamsis has joined #airshipit11:19
*** vamsis has quit IRC11:24
*** vamsis has joined #airshipit11:41
*** aaronsheffield has joined #airshipit12:02
*** vamsis has quit IRC12:20
*** vamsis has joined #airshipit12:28
*** aliijaz has joined #airshipit12:29
aliijazhi12:29
aliijazi have develop airship but i cant understand how to access airship GUI or any interfaces12:30
*** ali_ has joined #airshipit12:31
ali_i have develop airship but i cant understand how to access airship GUI or any interfaces12:32
*** vamsis has quit IRC12:38
*** Guest72952 is now known as portdirect12:41
*** vamsis has joined #airshipit12:42
*** ali_ has quit IRC12:43
aliijazanyone here12:46
b-strThe interface to Airship is effectively the Shipyard API (and Keystone). There is no specific Airship GUI.  If you are on the host where you have launched Airship, you can also see some of the results using kubectl to inspect the deployed Kubernetes cluster.12:56
*** sthussey has joined #airshipit12:59
*** aaronsheffield has quit IRC13:19
*** felipemonteiro has joined #airshipit13:26
*** aaronsheffield has joined #airshipit13:27
*** openstackgerrit has joined #airshipit13:34
openstackgerritMark Burnett proposed openstack/airship-promenade master: Fix broken validatedesign endpoint  https://review.openstack.org/58366313:34
openstackgerritMark Burnett proposed openstack/airship-promenade master: Add liveness probe to kube-proxy  https://review.openstack.org/58366413:34
*** felipemonteiro has quit IRC13:35
*** vamsis has quit IRC13:41
*** felipemonteiro has joined #airshipit13:58
*** felipemonteiro__ has joined #airshipit14:15
*** felipemonteiro has quit IRC14:16
*** felipemonteiro_ has joined #airshipit14:16
*** jgu has joined #airshipit14:17
*** jgu has quit IRC14:18
*** jgu has joined #airshipit14:18
*** felipemonteiro__ has quit IRC14:20
roman_galiijaz: did you mean to say that you have installed Airship-in-a-bottle?14:26
*** vamsis has joined #airshipit14:32
*** vamsis has quit IRC14:36
*** vamsis has joined #airshipit14:36
*** vamsis has quit IRC14:38
*** vamsis has joined #airshipit14:38
*** vamsis has quit IRC14:39
*** vamsis has joined #airshipit14:39
*** georgk has quit IRC14:55
*** jgu has quit IRC15:02
*** jgu has joined #airshipit15:04
*** jgu_ has joined #airshipit15:05
*** jgu has quit IRC15:09
*** vamsis has quit IRC15:18
*** vamsis has joined #airshipit15:20
openstackgerritSmruti Soumitra Khuntia proposed openstack/airship-shipyard master: A new Shipyard status API and CLI  https://review.openstack.org/58215615:30
openstackgerritMarshall Margenau proposed openstack/airship-armada master: Wait for jobs to complete  https://review.openstack.org/58373815:40
marshallmargenau@cfriesen_  the armada hang you posted yesterday might actually be related to a bug that i just found and addressed last evening15:56
marshallmargenauit's actually in the PS that openstackgerrit just posted directly above here15:56
*** felipemonteiro_ has quit IRC15:57
*** felipemonteiro_ has joined #airshipit15:58
*** vamsis has quit IRC16:06
openstackgerritHemanth Nakkina proposed openstack/airship-specs master: [WIP] Add Redfish OOB driver to Drydock  https://review.openstack.org/58401516:12
*** felipemonteiro_ has quit IRC16:13
openstackgerritBryan Strassner proposed openstack/airship-shipyard master: [WIP] Add redeploy_server processing  https://review.openstack.org/58379316:17
*** kberger has quit IRC16:23
openstackgerritMarshall Margenau proposed openstack/airship-armada master: WIP - Update Helm version  https://review.openstack.org/58117316:25
openstackgerritMarshall Margenau proposed openstack/airship-armada master: Wait for jobs to complete  https://review.openstack.org/58373816:37
openstackgerritSmruti Soumitra Khuntia proposed openstack/airship-shipyard master: A new Shipyard status API and CLI  https://review.openstack.org/58215616:38
*** vamsis has joined #airshipit16:46
cfriesen_marshallmargenau: will give it a try16:46
*** vamsis has quit IRC16:46
*** vamsis has joined #airshipit16:48
*** vamsis has quit IRC16:52
*** vamsis has joined #airshipit16:55
*** vamsis has quit IRC16:57
cfriesen_marshallmargenau: looks better, it got through a bunch of charts and then seems to have hung here:  http://paste.openstack.org/show/726293/17:08
openstackgerritMerged openstack/airship-maas master: Upgrade the version of kubernetes-entrypoint for UCP helm charts  https://review.openstack.org/58076017:09
openstackgerritMerged openstack/airship-armada master: Removing dead code.  https://review.openstack.org/58374017:14
openstackgerritMerged openstack/airship-promenade master: Upgrade the version of kubernetes-entrypoint for UCP helm charts  https://review.openstack.org/58142417:14
openstackgerritMerged openstack/airship-shipyard master: Make validation process failures more obvious  https://review.openstack.org/58268917:25
*** jgu_ has quit IRC17:29
*** vamsis has joined #airshipit17:34
*** felipemonteiro has joined #airshipit17:35
marshallmargenaucfriesen_: that looks like it could possibly be the one circular dependency that OSH has, between nova, neutron, and libvert17:45
marshallmargenauarmada just merged a PS to try to deal with that a little better, earlier this week... but I don't believe OSH has made the updates yet to take advantage17:45
marshallmargenauthe key there is:  WARNING armada.handlers.k8s [-] "label_selector" not specified, waiting with no labels may cause unintended consequences.17:45
portdirectmarshallmargenau: could you make a ps to help out there :)17:45
marshallmargenauI can17:46
portdirectnice - thanks dude17:46
*** felipemo_ has joined #airshipit17:46
marshallmargenau@portdirect I've been out of the loop... has there been any effort, or will there be any effort to resolve the circular dependency?17:47
marshallmargenauor do we just need to accept that it exists? :)17:47
portdirectwe need to accept it exists :(17:48
portdirectthe three charts are much more tightly coupled than we would like17:48
portdirectbut in essence neutron-agents shoudl come up before libvirt, which is required by nova-compute17:49
portdirectbut at the api level17:49
portdirecttheings like the neutron-metadata proxy rely on nova-metadata17:49
portdirectso all three charts should be deployed at the same time...17:50
marshallmargenaui actually need a little help, i found nova and neutron easily, but not sure where libvert is in the OSH charts17:50
portdirectlibvirt...17:51
portdirecthttps://github.com/openstack/openstack-helm/blob/master/tools/deployment/armada/multinode/armada-osh.yaml#L706-L73017:51
portdirect:)17:51
marshallmargenauah, i was searching libvert, not libvirt :)17:51
marshallmargenauthanks17:51
cfriesen_portdirect: there isn't actually a "requirement" dependency though, it's more of a runtime dependency.17:58
portdirectcfriesen_: correct17:59
portdirectarmada's logic is to wait for all pods to be in a running state, so here thats whats in effect18:00
cfriesen_what's the plan for handling upgrades, where you would normally upgrade the code while keeping the "old" RPC/HTTP versions, then update the config files to use the "new" version once everything is running the new code?  would that be two manifest apply operations?18:00
portdirectyeah - thats how we are applying it atm18:00
*** felipemo_ has quit IRC18:01
portdirectin the very worst case its sometimes a three pass operation18:01
portdirectbut using shipyard workflows we hope to make that as seamless as possible as things mature18:02
*** jgu has joined #airshipit18:02
*** jgu_ has joined #airshipit18:05
*** jgu has quit IRC18:09
cfriesen_there are a couple mentions of "ps" above...not familiar with that usage.18:18
aaronsheffieldPS = Patch Set on https://review.openstack.org18:22
cfriesen_ah, thanks18:29
openstackgerritMark Burnett proposed openstack/airship-promenade master: Enable etcd helm test to run on non-ready nodes  https://review.openstack.org/58366118:29
openstackgerritMark Burnett proposed openstack/airship-promenade master: Tolerate unready endpoints for apiserver service  https://review.openstack.org/58366218:29
openstackgerritMark Burnett proposed openstack/airship-promenade master: Fix broken validatedesign endpoint  https://review.openstack.org/58366318:29
openstackgerritMark Burnett proposed openstack/airship-promenade master: Add liveness probe to kube-proxy  https://review.openstack.org/58366418:29
openstackgerritMark Burnett proposed openstack/airship-promenade master: Remove unused image references  https://review.openstack.org/58405818:29
cfriesen_regarding the issues with "armada apply" making new helm releases for charts that haven't changed (and aren't dependent on the changed chart), what's the process for creating a bug report?  do you have special tags or subject keywords in stories for bugs?18:31
openstackgerritMerged openstack/airship-deckhand master: refactor: Use yaml.add_representer to reduce complexity  https://review.openstack.org/57929618:39
openstackgerritMerged openstack/airship-promenade master: (fix) Update deckhand dependency  https://review.openstack.org/58297018:43
openstackgerritMarshall Margenau proposed openstack/airship-armada master: Wait for jobs to complete  https://review.openstack.org/58373819:09
marshallmargenaui'll poke mark-burnett and mattmceuen for decisions on how to open bug reports, as we don't have a set solution for airship just yet19:17
marshallmargenaubut could you provide some more information into the behavior you're seeing?19:17
mattmceuenhey cfriesen_ --  would be very appreciated if you file bugs when you find them -- please do so through storyboard here: https://storyboard.openstack.org/#!/project_group/8519:22
mattmceuenEach airship project has its own corresponding storyboard project19:22
*** vamsis has quit IRC19:27
cfriesen_mattmceuen: happy to open a story...just wondering if you're putting [bug] in the subject, or setting a "bug" tag, or just leaving the bugs together with the features indiscriminately19:27
mattmceuento be honest I'm still trying to figure out all the best practices around storyboard :)19:28
*** vamsis has joined #airshipit19:29
mattmceuenI don't think we have a convention yet for that.  I think some kind of annotation for a bug would be a good idea -- any opinions guys?19:29
*** Romik has joined #airshipit19:32
cfriesen_personally I think the tag works best, as you can explicitly filter/search stories based on a tag but I don't think you can filter based on keyword in just the title, it looks at the title and description together, and maybe the comments too19:34
marshallmargenauwhatever storyboard supports is fine with me19:44
marshallmargenauif there are actual tags we can use, great... if not, just [bug] in the title is fine to me19:44
Romikcfriesen_ re: where to open bug reports: in OpenStack StoryBoard for all Airship-* (https://storyboard.openstack.org/#!/project_group/85), and in Github issues for the Treasuremap https://github.com/att-comdev/treasuremap/issues.19:45
cfriesen_added this: https://storyboard.openstack.org/#!/story/200303719:46
cfriesen_marshallmargenau: storyboard lets you assign arbitrary tags.  start typing and it'll autocomplete based on what has already been entered, but you can add brand new ones too19:47
*** Romik has quit IRC19:48
*** jgu_ has quit IRC19:53
*** jgu has joined #airshipit19:53
*** vamsis has quit IRC20:23
marshallmargenaugood to know about arbitrary tags!  we're just getting ramped up with it20:25
cfriesen_me too. :)  I'm used to launchpad for other projects.20:32
cfriesen_just opened another bug:  https://storyboard.openstack.org/#!/story/200304020:32
cfriesen_that seems like basic functionality...does airship not delete by manifest?20:34
marshallmargenauah interesting, i believe 'armada delete' was contributed by our friends @powerds0111 and @jayahn20:34
marshallmargenauI'd be interested to hear if they've seen this behavior20:35
marshallmargenauwe, with airship specifically, don't currently use the 'armada delete' functionality20:35
portdirectmarshallmargenau: do we have gating/testing for these functions?20:35
marshallmargenaunope :D20:35
marshallmargenaunot beyond unit testing20:35
marshallmargenauclearly a gap20:35
marshallmargenautrying to take a quick look... thanks so much for running in debug in your bug report, greatly appreciated!20:43
*** jgu has quit IRC20:49
*** aaronsheffield has quit IRC21:25
*** jgu has joined #airshipit21:27
*** jgu_ has joined #airshipit21:28
openstackgerritBryan Strassner proposed openstack/airship-shipyard master: [WIP] Add redeploy_server processing  https://review.openstack.org/58379321:31
*** jgu has quit IRC21:33
cfriesen_when looking at an armada manifest file, is the manifest name only required to be unique within that file?  I see that in opentack-helm all four manifests use "armada-manifest" as the manifest name.21:35
sthusseyIt would need to be unique within the set of YAML documents you give Armada during a given run21:36
cfriesen_you can only specify one manifest per "armada" call, no?21:37
sthusseyYou can provide multiple manifest documents in the set and specify which should be acted upon via `--target-manifest <name>`21:40
sthusseyIf you are using the API, I'd have to look for the specifier for target manfiest21:41
cfriesen_okay...why would you want to do that instead of specifying a single manifest document?  Is it in case you don't know which document contains the manifest in question?21:42
openstackgerritFelipe Monteiro proposed openstack/airship-pegleg master: Add git and branch revision support to pegleg  https://review.openstack.org/58265221:47
jayahnmarshallmargenau: we will follow up bug report.22:06
*** vamsis has joined #airshipit22:26
*** vamsis has quit IRC22:31
cfriesen_in the openstack-helm manifest /tmp/armada-ceph.yaml, the ceph-mon, ceph-osd, and ceph-client chart sections have a lot of duplicated configuration options.  I wonder if it would make sense to allow specifying a "data" section for a chartgroup that could be "included" or referenced by any chart in the group to save on duplication (and possibly errors in copying)22:58
cfriesen_you could associate a name with it, and include/reference it by name in the chart data22:58
*** felipemonteiro has quit IRC23:00
*** felipemonteiro has joined #airshipit23:15
*** felipemonteiro has quit IRC23:20
*** felipemonteiro has joined #airshipit23:24
*** felipemonteiro has quit IRC23:30
*** felipemonteiro has joined #airshipit23:31
*** felipemonteiro has quit IRC23:36
*** AhmadM has joined #airshipit23:41
*** AhmadM_ has joined #airshipit23:44
*** sthussey has quit IRC23:49
*** AhmadM_ has quit IRC23:49
*** AhmadM_ has joined #airshipit23:54
*** jgu_ has quit IRC23:57
*** jgu has joined #airshipit23:58

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