Thursday, 2015-08-27

openstackgerritArthur Berezin proposed stackforge/apps-catalog: This adds a Cloudify Orchestrator to the app catalog, which is capable to launch TOSCA Blueprints.
kzaitsev_mband I'm not really sure what to do about that..00:08
kzaitsev_mbduh it's 3am here, so I'll go to bed, maybe I'll have better ideas tomorrow =/00:08
openstackgerritArthur Berezin proposed stackforge/apps-catalog: This adds a Cloudify Orchestrator to the app catalog, which is capable to launch TOSCA Blueprints.
openstackgerritArthur Berezin proposed stackforge/apps-catalog: Adding Cloudify Orchestrator to the app catalog which capable to launch TOSCA Blueprints.
*** Berezin has joined #openstack-app-catalog00:24
BerezinI just re-submitter a patch
BerezinI'd be happy for a review00:25
kzaitsev_mbhi Berezin I see you have submitted 2 patches00:27
openstackgerritArthur Berezin proposed stackforge/apps-catalog: fixing typo
kzaitsev_mbI see. you're not familiar with how gerrit works, right?00:28
Berezinyep :)00:28
Berezinhow do I submit changes to -1 :)00:29
kzaitsev_mbok. so first of all a review can take some time00:29
kzaitsev_mbso do not expect a lightning-fast review. I guess someone, who is core would have to download the image and see if it's ok, before adding the asset to the catalog00:30
kzaitsev_mb2d — there is no need for 3 commits00:30
docaedoBerezin: I would suggest abandoning 217445 and 217441, and just update your 217429 commit to include the fixes plus add the image in00:30
docaedoand if you have something in progress (i.e. you want to commit, but are still working on it) you can review your own patch and mark it a -1 WIP00:31
kzaitsev_mbexactly — you should abandon 2d and 3d and just update the 1st commit00:31
docaedo(you can also do .. git review +W or something? kzaitsev_mb do you know how to submit for review but mark WIP at the same time?)00:31
kzaitsev_mbmark with -1 WIP or just mention WIP in the 1st line00:32
kzaitsev_mbdocaedo: it's impossible afaik =)00:32
docaedoBerezin: thank you though! it's close, and should be pretty straighforward from here to get the original patch into shape00:32
docaedokzaitsev_mb: ah ok, I thought maybe there was an option in gerrit-review that let you do that00:32
kzaitsev_mbnope =/ it's rather limited00:33
kzaitsev_mbdocaedo: we've found a bug in our KubernetesCluster app — it was actually a simple typo, but the app won't work on a newer murano engine. And there is no way I can think of uploading an update-request. =/00:34
kzaitsev_mbIf i won't come up with some solution for that — may I ask you to update the binary manually tomorrow?00:34
kzaitsev_mbBerezin: do you need any help with editing your commit?00:35
docaedokzaitsev_mb: yes, I think easiest is just a manual update TBH00:35
docaedothe binary store is just plain bad, and I don't think it's worth trying to come up with some complicated process00:36
Berezinkzaitsev_mb: docaedo I'm working on it now :)00:36
docaedobetter to agree it's a short term "get it done" thing, that was essentially a mistake, and we'll fix it later00:36
docaedo(but I'm stepping away to dinner and evening with fam - back later most likely!)00:36
kzaitsev_mbyep, hope we'll be able to solve that during M00:37
kzaitsev_mbBerezin: so do you know how to edit your commit? =)00:37
*** Berezin has quit IRC00:40
*** kzaitsev_mb has quit IRC01:35
*** kzaitsev_mb has joined #openstack-app-catalog01:43
*** Berezin has joined #openstack-app-catalog01:49
*** Berezin has quit IRC01:53
*** kzaitsev_mb has quit IRC01:56
*** Berezin has joined #openstack-app-catalog02:06
openstackgerritArthur Berezin proposed stackforge/apps-catalog: Adding Cloudify Orchestrator to the app catalog. Cloudify Orchstrator is capable of launching TOSCA Blueprints.
openstackgerritArthur Berezin proposed stackforge/apps-catalog: Adding image
*** Berezin has quit IRC02:42
*** Berezin has joined #openstack-app-catalog03:07
*** Berezin has quit IRC03:43
*** kebray has joined #openstack-app-catalog04:59
*** openstackgerrit has quit IRC05:16
*** openstackgerrit has joined #openstack-app-catalog05:17
*** Berezin has joined #openstack-app-catalog07:02
*** Berezin has quit IRC07:09
openstackgerritArthur Berezin proposed stackforge/apps-catalog: Adding Cloudify Orchestrator to the app catalog. Cloudify Orchstrator is capable of launching TOSCA Blueprints.
*** Berezin has joined #openstack-app-catalog07:28
*** kebray has quit IRC07:45
*** Berezin has quit IRC07:55
*** Berezin has joined #openstack-app-catalog08:01
*** Berezin has quit IRC08:15
*** kzaitsev_mb has joined #openstack-app-catalog09:27
*** kzaitsev_mb has quit IRC10:07
*** kzaitsev_mb has joined #openstack-app-catalog11:14
*** kzaitsev1ws has joined #openstack-app-catalog11:53
*** kzaitsev1ws has quit IRC11:53
kzaitsev_mbhey the patches are being merged =)12:23
*** openstackgerrit has quit IRC12:31
*** openstackgerrit has joined #openstack-app-catalog12:32
kfox1111yup. :)12:52
kfox1111docaedo: Oh. Just tried to test out Berezin's patch then realized all my test code is over on the merged assets branch.13:06
kfox1111how far out do you think that is?13:06
*** kebray has joined #openstack-app-catalog14:44
*** kebray has quit IRC15:07
*** kebray has joined #openstack-app-catalog15:34
kfox1111ah. cool. I'll try that out.15:42
*** kebray has quit IRC15:58
docaedokfox1111: I'm digging myself out of things and getting caught up today - regarding single assets file, is the only thing we're waiting for the infra update to make the JSON file? Or also need to change things on the web side as well?16:27
docaedoI haven't looked at 216047 but will shortly16:28
docaedooh man, is it Thursday already??16:53
kfox1111just infra. the plugin and website are all fixed up.16:53
kzaitsev_mbdocaedo: yep =)16:53
kzaitsev_mbtime flys16:53
docaedoI can do that infra patch today, that's easy. We need to merge for app-catalog first a patch that includes the full new path (that v1 path) so I don't have to make the change on the puppet side any more complicated than it needs to be16:54
docaedojust got my calendar reminder for the meeting, but not sure we need it today? guess we can have it, will just be slightly disorganized (and possibly short), unless everyone who is going to meet is already here on the channel16:54
kfox1111we should probably just merge it. then when the assets.json merge hits, it will automatically trigger.16:54
kfox1111I'm still in juno->kilo funland all day so may have to skip it.16:55
kfox1111but a lot of progress. it looks like all the horizon patches are merging now. :)16:55
kfox1111so the plugin should be standalone by liberty.16:55
kfox1111murano support in the plugin for liberty is looking more iffy.16:55
docaedo+1 on merging 216047, I'll take a close look and test myself, if all goes well I'll merge and work on the infra patch to fix as well16:56
kfox1111kzaitsev_mb has a patch that will fix form passing, so basic functionality may work by then. not sure.16:56
docaedoI propose we skip the meeting (though I'll go on the channel and announce it, and check to see if some random people planned to show up wanting to chat)16:56
kfox1111hmm.... do we have manuall access to the web server?16:56
kfox1111without the infra patch in place though, assets.json won't be built initially and the website will fail until its built...16:57
docaedooh - I did not realize the website is now dependent on the JSON file16:58
docaedo(because I have not looked at that patch at all)16:58
kzaitsev_mbwell, it feels like we should wait for infra then16:58
kfox1111yeah. :/16:59
docaedoI can add as part of that patch the JSON file that will be created by the infra patch easily, so will kind of be a one-off manual step (which would be necessary to actually test that patch anyway)17:00
kzaitsev_mbshall we go to #openstack-meeting-3 then?17:00
kzaitsev_mbok, now, that I see I get, why we have to wait17:09
kzaitsev_mbbtw. kfox1111 you can use Depends-On in you patch17:09
kzaitsev_mbyou can add "Depends-On: Ib8211b1f0a00e2d9098c7c0eb0624781fdb212d3" line to
docaedoI would rather go the other way though - I can make the slight change to the app-catalog patch (manually create the assets.json file) and merge it,17:10
docaedootherwise the puppet side gets more complicated (i.e. creating a new directory after checking out the repo, but before creating the JSON)17:11
docaedoand history tells me I'll spend some time explaining why that is necessary17:11
docaedoand then I'll find I chose the less favorable puppet method for creating a directory17:11
docaedoand I'll change it and resubmit17:11
docaedoand then a new person will ask why we are creating a JSON file when we have a YAML17:11
docaedoand then...17:12
docaedoand then...17:12
kzaitsev_mboh docaedo17:12
docaedoBUT if you guys both prefer we handle the creation of the directory via infra patch, I'll concede and work on that17:12
docaedokzaitsev_mb: yes?17:12
kzaitsev_mbMay I ask you to upload a binary for murano app?17:13
docaedoabsolutely, you can share details here or if I need to fetch it from somewhere confidential you can msg me directly17:13
kzaitsev_mb to /apps/io.murano.apps.docker.kubernetes.KubernetesCluster.zip17:13
docaedocool, I'm on it17:13
kzaitsev_mbI'm going to be afk for some time now, will get back in an hour or so.17:17
kzaitsev_mbAnd I do not really have a stong opinion about infra thing, at least not yet )17:18
docaedoOK - RAX says the file is uploaded, but could be a little while before it updates all over their CDN17:18
docaedoI'll put up a patch that does what I propose to 216047 and if there's an objection, we can always revert my patchset :)17:20
*** kzaitsev_mb has quit IRC17:30
kfox1111docaedo: there's a race condition that way. wehn we remove the assets.json back out of git, then if the server ever gets blown away/put back, then the dir is no longer there.17:40
kfox1111the infra patch really should create the dir I think.17:41
docaedoah I see what you're saying, makes sense17:43
docaedowe have a race condition indeed. I can't test (or even try to merge) the infra patch because it expects assets.yaml to exist18:31
docaedoso we need an interim patch that creates the merged assets.yaml before the infra patch can go in18:31
docaedoso why not have the web site continue to pull from the assets.yaml instead of having the web site need the JSON file?18:32
docaedokfox1111: what's in app-catalog has to be basically standalone IMO, and the changes (which are right now transitional). What's in 216047 is dependent on external stuff (infra manifest), for the sake of making it read from a JSON file that doesn't exist yet...18:40
*** Berezin has joined #openstack-app-catalog18:41
docaedosorry that thought was jumbled - I am trying to say while we are transitioning the app-catalog from being just a web site, to something that is useful externally (the horizon plugin), we shouldn't make the website become dependent on something outside the website itself18:42
docaedobecause right now, it's easy/obvious how to pull the repo and run it locally for your own development, etc. But if something outside the repo has to create directories and a JSON file in order to make the repo testable, then it's broken without some manual steps/effort18:43
docaedokfox1111: I know you're in the midst of the upgrade, we can pick this up when you have time again - in the mean time I'll see if I can make something slightly different that would work for me and add review comments18:44
docaedoIn other news though, this merged, yay!
*** Berezin has quit IRC18:50
docaedoI added a comment to 216047 with suggestion for a change that would make it possible to merge this patch :)18:56
*** kzaitsev_mb has joined #openstack-app-catalog19:02
kfox1111docaedo: could do an intermediate one where in infra we merge all the non merged yaml's together to assets.json for testing. then we merge the apps-catalog one, which will have a working website, then we do another infra.19:08
docaedobut that still means the app-catalog repo stops working as a simple flat site19:09
docaedomy question is - why make the website pull from the JSON that is being generated from the YAML anyway when it works just fine directly from the YAML?19:10
kfox1111javascript can natively parse json, not yaml.19:11
kfox1111the runserver test code I added does the generation so that running it locally still works.19:11
kfox1111I updated the wiki too.19:11
docaedoso the intention is to stop using "jsyaml.safeLoad"?19:13
docaedoI get that the runserver test code makes testing locally work, but I'm trying to understand the value of loading assets from the JSON instead of the YAML, that's the part I still don't see the value of19:14
docaedo(also, this still has us in a race condition with infra patch - until we have a merge with assets.yaml in it, the init.pp will fail tests)19:15
docaedo(but if we can merge a version with assets.yaml that does not break the website, the infra patch will pass tests and work)19:16
kfox1111I can try and break up the patches...19:17
docaedowhy does the web site need to load from a JSON file that doesn't exist rather than a YAML file that does?19:17
kfox1111yeah... could split that into 2. do everything but removing the yaml code, then do that in a different patch.19:18
docaedocould be split yes, but why load from JSON instead of YAML?  Is it really ONLY so we can stop using jsyaml.safeLoad?19:19
kfox11113 reasons. 1, json's smaller because yaml19:19
kfox1111s spaced out for human readableness.19:19
kfox11112, json parsing is native to the web browser.19:20
kfox11113, we can update/change the schema of the user changable stuff assets.yaml seperatly then what the website/plugins consume assets.json19:20
kfox1111so, stars for example.19:20
docaedoI don't see any way we include user rating (stars, feedback, etc.) with the current approach, at least no reasonable way.19:22
kzaitsev_mbI'd add, that should we make api dynamic (non-static file) — it would most likely be json19:23
kfox1111thats why having the api seperate from the content allows us to merge in stuff like stars into the api side.19:23
kfox1111kzaitsev_mb: yeah.19:23
kzaitsev_mband this feels like a 1st step there19:23
docaedothis feels to me like serious premature optimization (yaml vs. json size) as well, because we will have to make huge changes in the next few months before the site can handle several hundreds of assets. By then we'll be dynamic and only serving via api whatever the client is asking for19:24
kzaitsev_mbalso. maybe it should be just /api/v1/assets?19:24
docaedoI agree this is the first step there, I'm just stuck on breaking the web site as part of this first step19:24
kfox1111maybe? it leaves us open for assets.something_else if we wanted to support a yaml or something in the future.19:24
kfox1111I should be able to revert just the yaml load. then do that in a follow up patch.19:25
docaedodefinitely would be easy :) my comment has the change you'd need19:25
kzaitsev_mbkfox1111: well, speaking api-wise it should be controlled by Content-Type, I guess19:26
docaedothen we can debate the follow up patch endlessly :)19:26
kfox1111yeah, I see some advantage to it being a get to just /v1/assets...19:27
kfox1111now's the time to decide I guess.19:27
docaedoON that, I'm mainly ambivalent ... to me this seems like pretty short term anyway, for the sake of the horizon plugin and right now it's really only for converting a yaml to json19:29
kfox1111looking at the other project's api, /v1/assets would be more consistant.19:29
kfox1111ok. I'll update it at the same time.19:29
docaedoah yeah that is true, good point19:29
docaedoI'm fine with that expecting just assets, and will adjust the infra bit accordingly19:30
docaedoso is the URL going to become /v1/assets or /api/v1/assets ?19:31
kzaitsev_mbI'd say /api/v1/assets once again to be consistent with other OS projects APIs19:31
kfox1111+1 /api/v1/assets19:32
docaedoroger that19:32
kzaitsev_mbto tell the truth that would make us inconsistent as far as I can tell )19:33
kzaitsev_mbbut — since this is a web site and accessing /index or something makes sense, I'd still say /api/v119:35
kfox1111yeah. we're alittle odd too in that we're providing a website and api on the same endpoint.19:35
kzaitsev_mbWith, say, nova accessing something like /login doesn't make much sence19:36
docaedoyeah I think we can kind of do what we want here since it's basically a pretend API right now, and this won't impact future changes (i.e. if we decide v2 will be served from somewhere else or whatever...)19:36
kfox1111we can also say, / is for humans to see whats in the catalog,19:37
kfox1111and /api is for machines to discover what /api/v*'s are supported.19:37
docaedospeaking of discovery, I need to go discover a lunch, will be back in a bit19:37
openstackgerritKevin Fox proposed stackforge/apps-catalog: Merge asset files. Add v1 API.
kfox1111that one has the changes.19:46
docaedoexcellent :)20:14
*** reed has quit IRC20:16
openstackgerritMerged stackforge/apps-catalog: Merge asset files. Add v1 API.
openstackgerritKevin Fox proposed stackforge/apps-catalog-ui: Update the plugin to use the v1 api.
*** reed has joined #openstack-app-catalog20:21
*** rhagarty__ has quit IRC20:23
*** rhagarty_ has quit IRC20:23
docaedoReview if you have a moment. Runs properly locally, I think it's good to go:
kfox1111extra space? or is my browser rendering odd?20:27
kzaitsev_mbwhat extra space?20:27
kfox1111I'm seeing an extra line, or a wrapped set of spaces after ensure directory in file { "${root_dir}/openstack_catalog/web/api":20:28
*** rhagarty has joined #openstack-app-catalog20:29
kfox1111hmm... doesn't show up in the unified diff though... maybe just a weird browser bug.20:29
kzaitsev_mbI'll checkout the change to check20:29
*** rhagarty_ has joined #openstack-app-catalog20:30
kzaitsev_mbnah, looks like gerrit is not really suited to review long lines20:32
kfox1111yeah. I think its fine.20:32
*** kebray has joined #openstack-app-catalog20:49
docaedoOK first draft of app-catalog big tent application can be found here:
docaedowould love feedback, changes, etc. :)20:57
kfox1111cool. looking...21:02
kfox1111are we not an official project now?21:04
kfox1111so this is a commit message? which repo?21:04
docaedoWe are not official, this is a commit message that will include a change to the projects file in the governance repo21:07
docaedoWill share an example link when I get back to a computer21:08
*** kebray has quit IRC21:09
kfox1111k. was thinking that kind of just happened when it was agreed the big tent was a thing.21:18
kfox1111anything in stackforge was an official project by definition.21:18
docaedoNope :) it's complicated for sure .. but basically it's only official when it's here:
docaedoer, not THERE, bad URL :/ ..21:24
docaedothis is what I meant to paste:
kfox1111ah. ok.21:44
docaedokfox1111: any feedback on the big tent thing? I want to submit today if possible. I feel like it's pretty non-controversial, but want to make sure I'm not just charging off on my own :)22:27
kfox1111sec... looked ok the first time. let me go over it one more time real quick.22:31
docaedook thanks, don't mean to rush you, just trying to get it on the agenda for the next TC meeting22:33
kfox1111Added one tweak, but looks good.22:33
kfox1111yeah, thats a good thing. :)22:33
docaedoexcellent thanks!22:33
docaedonice addition too, thanks. I was going back and forth on how much I wanted to talk about long term plans. Ultimately figured if I get into roadmap stuff there, it opens the roadmap up for debate via the TC. But that addition indicating there's more than just heat, glance and murano is perfect.22:34
docaedo  <-- big tent application22:55
*** Berezin has joined #openstack-app-catalog23:10
*** kzaitsev_mb has quit IRC23:59

Generated by 2.14.0 by Marius Gedminas - find it at!