| *** sridhar_ram has quit IRC | 00:18 | |
| *** sridhar_ram has joined #openstack-heat-translator | 00:33 | |
| *** spzala has quit IRC | 00:35 | |
| *** spzala has joined #openstack-heat-translator | 00:35 | |
| *** spzala has quit IRC | 00:40 | |
| *** spzala has joined #openstack-heat-translator | 01:02 | |
| *** sridhar_ram has quit IRC | 01:25 | |
| *** vishwanathj has joined #openstack-heat-translator | 01:30 | |
| *** tbh has joined #openstack-heat-translator | 02:19 | |
| tbh | spzala, ping | 02:47 |
|---|---|---|
| spzala | hi tbh: | 02:47 |
| tbh | spzala, have you checked the mail regarding the output of POST request? | 02:48 |
| spzala | nope, just seeing it now | 02:49 |
| spzala | sorry missed it, seems like you sent it today | 02:49 |
| spzala | thanks for that mail, please give me a minute ..reading it | 02:50 |
| tbh | spzala, sure | 02:51 |
| spzala | well so it looks great to me as you said earlier | 02:51 |
| spzala | 1)If status_code== 201, then send one more GET request to fetch stack details and display in table. | 02:52 |
| spzala | 2)Else print the whole content. | 02:52 |
| spzala | I was worried about time delay but seems like that's not the case | 02:52 |
| spzala | so I am totally fine with the approach you are taking | 02:53 |
| spzala | so for code other than 201 we will display the output right away (as you provided snippet for 400 code) | 02:53 |
| spzala | and if it's 201 then we will go for GET one more time and display output | 02:54 |
| spzala | I think once you have that change, let's have them merged so that if anyone wants to play with it, they can | 02:55 |
| spzala | and if run into any error or per any feedback we make changes if needed | 02:55 |
| tbh | spzala, sure, will do that | 02:56 |
| spzala | Awesome!! Thanks tbh: | 02:59 |
| tbh | spzala, np | 02:59 |
| *** bobh_ has quit IRC | 03:55 | |
| *** sridhar_ram has joined #openstack-heat-translator | 04:25 | |
| *** sridhar_ram1 has joined #openstack-heat-translator | 04:28 | |
| *** sridhar_ram has quit IRC | 04:30 | |
| *** tbh has quit IRC | 04:48 | |
| *** vishwanathj has quit IRC | 04:53 | |
| *** sridhar_ram1 has quit IRC | 05:26 | |
| *** spzala has quit IRC | 05:35 | |
| *** spzala has joined #openstack-heat-translator | 05:36 | |
| *** spzala has quit IRC | 05:40 | |
| *** Sanchita_ has joined #openstack-heat-translator | 06:17 | |
| *** piyush has joined #openstack-heat-translator | 06:18 | |
| Sanchita_ | hi | 06:19 |
| Sanchita_ | I am facing the issue while trying to create the setup using heat | 06:20 |
| Sanchita_ | heatclient.exc.HTTPBadRequest: ERROR: Property error: : resources.node:0-0-9:server.properties.flavor: : 'OpenStackComputeShell' object has no attribute '_discover_extensions' | 06:20 |
| *** piyush has quit IRC | 06:28 | |
| *** spzala has joined #openstack-heat-translator | 06:37 | |
| *** spzala has quit IRC | 06:42 | |
| *** spzala has joined #openstack-heat-translator | 08:38 | |
| *** spzala has quit IRC | 08:44 | |
| *** tbh has joined #openstack-heat-translator | 09:11 | |
| *** Sanchita_ has quit IRC | 09:17 | |
| openstackgerrit | Mathieu Velten proposed openstack/heat-translator: Support ansible, python and puppet scripts. Currently hardcoded by looking at the extension. https://review.openstack.org/299827 | 09:39 |
| openstackgerrit | Mathieu Velten proposed openstack/heat-translator: On block device attachment, ignore device (unsupported) and mountpoint (badly supported) properties. https://review.openstack.org/299828 | 09:39 |
| *** tbh has quit IRC | 09:50 | |
| *** tbh has joined #openstack-heat-translator | 09:51 | |
| *** tbh has quit IRC | 10:30 | |
| *** spzala has joined #openstack-heat-translator | 13:12 | |
| *** bobh_ has joined #openstack-heat-translator | 13:21 | |
| *** spzala has quit IRC | 15:20 | |
| *** spzala has joined #openstack-heat-translator | 15:20 | |
| *** spzala has quit IRC | 15:25 | |
| *** spzala has joined #openstack-heat-translator | 15:46 | |
| *** shangxdy has joined #openstack-heat-translator | 15:59 | |
| *** shangxdy_ has joined #openstack-heat-translator | 15:59 | |
| spzala | Hi all | 16:00 |
| bobh_ | o/ | 16:00 |
| spzala | topol: bobh_: shangxdy: | 16:00 |
| shangxdy_ | Hi,spzala | 16:00 |
| shangxdy_ | Hi, bobh | 16:00 |
| bobh_ | shangxdy_: hello | 16:01 |
| spzala | We really don't have much in agenda today but we can start with it, | 16:01 |
| spzala | bobh_: and shanxdy: are here so it's perfect :-) | 16:01 |
| spzala | https://bugs.launchpad.net/tosca-parser/+bug/1564415 | 16:01 |
| openstack | Launchpad bug 1564415 in TOSCA Parser "nfv-tosca definition is inaccurate." [Undecided,New] | 16:01 |
| spzala | bobh_: shang has opened it. | 16:02 |
| shangxdy_ | I just submit a bug | 16:02 |
| spzala | shangxdy: thanks for reporting it | 16:02 |
| shangxdy_ | yeah | 16:02 |
| shangxdy_ | to bobh, how do you think about it? | 16:02 |
| bobh_ | shangxdy_: trying to bring it up now - launchpad is slow today | 16:03 |
| spzala | Seems like a minor one but might be needed change | 16:03 |
| bobh_ | shangxdy_: we had a lot of discussions around this - technically you are correct, but if we map a VDU to a software component there is no mapping int he NFV spec to a compute | 16:03 |
| spzala | bobh_: :-) | 16:04 |
| bobh_ | shangxdy_: the examples in the NFV spec document are not implementable - if you were to do exactly what the spec says you would have a software component and no place to run it | 16:04 |
| spzala | (my :-) was on slow launchpad, I ran into slow network this morning too) | 16:04 |
| shangxdy_ | I know it, I have the idea before. | 16:05 |
| bobh_ | shangxdy_: there is also no logical connection between the VNF definition and the VDU definition | 16:05 |
| bobh_ | shangxdy_: I think VNF should have a container to reference a collection of VDUs, but that doesn't exist | 16:06 |
| shangxdy_ | vdu must be host on compute, its a logical entity,not a compute. | 16:06 |
| bobh_ | shangxdy_: so we had to modify the implementation of the spec to something that would actually work | 16:06 |
| bobh_ | shangxdy_: I agree, but there is nothing in the spec that mentions that or shows any examples | 16:06 |
| shangxdy_ | It mentions in the ETSI specification of MANO | 16:08 |
| shangxdy_ | Actually, VUD is a deployment entity of one or moreVNFC | 16:08 |
| bobh_ | which isn't mentioned in the TOSCA spec at all | 16:09 |
| bobh_ | the whole thing is a bit of a mess | 16:09 |
| bobh_ | lots of documents talking about what SHOULD be and no implementations | 16:09 |
| *** sridhar_ram has joined #openstack-heat-translator | 16:10 | |
| bobh_ | shangxdy_: you can talk with sridhar_ram about it - he is on the NFV Profile committee | 16:10 |
| bobh_ | sridhar_ram: see #link https://bugs.launchpad.net/tosca-parser/+bug/1564415 | 16:11 |
| openstack | Launchpad bug 1564415 in TOSCA Parser "nfv-tosca definition is inaccurate." [Undecided,New] | 16:11 |
| shangxdy_ | yes, It not mentions explicit, but the etsi mentions it | 16:11 |
| shangxdy_ | HI, sridhar_ram? | 16:12 |
| bobh_ | I'm not sure that spzala wants to support anything that's not in the NFV spec? | 16:12 |
| spzala | just my two cents, if tosca nfv profile doesn't have it then current definition in tosca-parser for NFV seems good. | 16:12 |
| bobh_ | spzala: :-) | 16:12 |
| spzala | bobh_: was about to give input on that :-) | 16:12 |
| bobh_ | spzala: great minds.... | 16:12 |
| spzala | bobh_: :-) yup, great minds think alike | 16:13 |
| spzala | to me, shangxdy: 's concern is real but it needs to be addressed in the tosca nfv spec first | 16:13 |
| shangxdy_ | THere is a example in nfv spec, you can have a glimps | 16:14 |
| bobh_ | I agree it's a concern and sridhar_ram was going to address it in the spec | 16:15 |
| bobh_ | or try to anyway | 16:15 |
| spzala | shangxdy: bobh_: something was added in spec lately then? | 16:17 |
| shangxdy_ | In another word, if vdu is derived from compute, it will not have the requirement of host, which is also type of compute. | 16:18 |
| bobh_ | spzala: sridhar_ram was going to request that the spec be changed so that VDU derives from Compute instead of SoftwareComponent | 16:18 |
| spzala | bobh_: Oh, I see. Thanks for helping understand it. | 16:18 |
| spzala | I was looking at the spec and found what shangxdy is saying. So, | 16:18 |
| shangxdy_ | yes, the wd03 will be published soon. | 16:19 |
| bobh_ | spzala: I don't particularly care either way, but the spec as it stands is vague and the examples cannot be implemented | 16:19 |
| spzala | shangxdy: honestly, in TOSCA simple profile also when we find something while implementation | 16:19 |
| spzala | we go with the correct practical approach and provide feedback to TC for making a change in spec | 16:19 |
| * sridhar_ram wandering in... | 16:19 | |
| spzala | we have also talked that Spec should be driven by actual implementation | 16:20 |
| shangxdy_ | :) | 16:21 |
| spzala | bobh_: I am with you on it. Shangxdy: bug is 100% valid per current spec, but I would wait on making any changes | 16:21 |
| spzala | shangxdy: hopefully Spec will make the change | 16:22 |
| sridhar_ram | shangxdy_: spzala: the next version is in two-week final review phase in OASIS. | 16:22 |
| spzala | shangxdy: :-) | 16:22 |
| bobh_ | spzala: probably a good candidate for a point release on the spec, which means we need an enhancement to support point releases on extensions...nothing like making more work for myself | 16:22 |
| sridhar_ram | shangxdy_: spzala: It will be out soon, so hang in there ! Please don't "fix" the bug ;-) | 16:22 |
| bobh_ | sridhar_ram: it's a feature not a bug :-) | 16:23 |
| shangxdy_ | Ok, we will check it again when the wd03 published. | 16:23 |
| spzala | sridhar_ram: hi, thanks | 16:23 |
| spzala | shangxdy_: yup, prefect | 16:23 |
| sridhar_ram | bobh_: exactly .. we are going to be bleeding edge in Tacker, fixing things that doesn't make sense in implementation. OASIS TOSCA values such feedback cycle. | 16:24 |
| sridhar_ram | welcome to the new world of making standards work :) | 16:24 |
| bobh_ | sridhar_ram: I can see the agument for VDU as a software component, but it wasn't described well | 16:25 |
| shangxdy_ | To sridhar_ram, can you relay me the draft of latest version? | 16:25 |
| spzala | sridhar_ram: :) yup, and it's good ..if you can't implement, it can't be a standard | 16:25 |
| sridhar_ram | spzala: exactly ! | 16:25 |
| sridhar_ram | shangxdy_: is your employer a member of OASIS ? If yes, I can send a pointer for you to download from OASIS | 16:26 |
| shangxdy_ | Sorry, I am not. | 16:26 |
| sridhar_ram | shangxdy_: then, if you don't mind hang in there for a week or so please. Will send a email to openstack ML once it gets released | 16:27 |
| shangxdy_ | ok, thanks. | 16:29 |
| spzala | Nice, so we are good on this topic I suppose | 16:29 |
| spzala | shangxdy_: bobh_: ? | 16:30 |
| bobh_ | spzala: I'm good | 16:30 |
| sridhar_ram | bobh_: now, I thought we had challenge in describing datatypes of type "map" and some complex datatypes. This needs fix in tosca-parser ? | 16:30 |
| bobh_ | sridhar_ram: not sure if a fix is needed or if we're just not writing them properly | 16:30 |
| shangxdy_ | In fact, i have already found some fault in nfv spec, some are grammar error, some are about format. | 16:31 |
| bobh_ | sridhar_ram: I want to debug the error and then ask spzala for his opinion | 16:31 |
| sridhar_ram | bobh_: make sense. If the spec need to be "fixed up" we can do that as well.. though it will go into the next rev CSD04 | 16:32 |
| shangxdy_ | support complex datatypes, it's good. | 16:32 |
| spzala | bobh_: sounds good | 16:33 |
| spzala | shangxdy: for the bug, I have added a comment summarizing our discussion but please feel free to add your comments as needed :-) | 16:34 |
| shangxdy_ | yeah, no problem:) | 16:34 |
| spzala | shangxdy_: :) | 16:35 |
| spzala | So anything else for today's meeting? It's open-discussion :-) | 16:35 |
| spzala | I am planning to have tosca-parser PyPI 0.5.0 release next week | 16:36 |
| spzala | we have fixed good numbers of bugs, improved tests and added loadbalancer support .. good candidate for a point release | 16:37 |
| spzala | just FYI, other than that nothing else from me | 16:37 |
| spzala | if nothing else, we can call it a meeting? :-) | 16:38 |
| bobh_ | spzala: I might try to get a change in - I'll see how much time I have | 16:38 |
| *** shangxdy_ has quit IRC | 16:38 | |
| bobh_ | spzala: I want to rework how the extensions are loaded | 16:39 |
| spzala | sridhar_ram: thanks for joining in discussion today. bobh_: shangxdy_: good discussion | 16:39 |
| spzala | bobh_: sure | 16:39 |
| *** shangxdy_ has joined #openstack-heat-translator | 16:39 | |
| spzala | I was planning to have release on Monday but can push it by a day (or more if you need), otherwise we can have those changes in 0.6.0 | 16:40 |
| bobh_ | 0.6 is probably fine | 16:40 |
| spzala | bobh_: OK, perfect. This will give us a time for 0.5.0 release of heat-translator around Austin summit time i.e. by end of Mitaka release cycle | 16:41 |
| sridhar_ram | spzala: sure, tacker 0.3.0 released today. Thanks for the support! Couldn't have done w/o you and bobh_ help ! | 16:41 |
| spzala | so then we can start Newton cycle with 0.6.0 | 16:41 |
| spzala | sridhar_ram: you are welcome and thank you! bobh_ is awesome :) | 16:42 |
| spzala | alright then thanks again for joining today's meeting and bye for now !! | 16:42 |
| bobh_ | bye | 16:43 |
| shangxdy_ | bye everyone:) | 16:43 |
| spzala | shangxdy: must be late for you. good night! | 16:43 |
| spzala | bye :) | 16:43 |
| shangxdy_ | I go to sleep now:) | 16:44 |
| spzala | shangxdy_: :-) yup good idea | 16:44 |
| spzala | I will go for lunch ;) | 16:44 |
| shangxdy_ | have a good lunch:) | 16:45 |
| spzala | :) thanks | 16:45 |
| shangxdy_ | bye, all! | 16:45 |
| spzala | bye | 16:46 |
| *** spzala has quit IRC | 16:46 | |
| *** spzala has joined #openstack-heat-translator | 16:47 | |
| *** spzala has quit IRC | 16:51 | |
| *** spzala has joined #openstack-heat-translator | 16:52 | |
| *** spzala has quit IRC | 16:57 | |
| *** shangxdy_ has quit IRC | 16:59 | |
| *** shangxdy has quit IRC | 16:59 | |
| *** spzala has joined #openstack-heat-translator | 17:04 | |
| *** spzala has quit IRC | 17:09 | |
| *** spzala has joined #openstack-heat-translator | 17:16 | |
| *** spzala has quit IRC | 17:20 | |
| *** spzala has joined #openstack-heat-translator | 17:30 | |
| *** spzala has quit IRC | 17:34 | |
| *** sridhar_ram is now known as sridhar_ram_afk | 17:37 | |
| -openstackstatus- NOTICE: Job failures for missing traceroute packages are in the process of being fixed now, ETA 30 minutes to effectiveness for new jobs | 17:48 | |
| *** spzala has joined #openstack-heat-translator | 17:49 | |
| *** spzala has quit IRC | 17:54 | |
| *** sridhar_ram_afk is now known as sridhar_ram | 17:55 | |
| *** spzala has joined #openstack-heat-translator | 18:01 | |
| *** spzala has quit IRC | 18:06 | |
| *** spzala has joined #openstack-heat-translator | 18:12 | |
| *** topol has joined #openstack-heat-translator | 18:14 | |
| *** spzala has quit IRC | 18:30 | |
| *** spzala has joined #openstack-heat-translator | 18:31 | |
| *** openstackgerrit has quit IRC | 19:03 | |
| *** openstackgerrit has joined #openstack-heat-translator | 19:04 | |
| -openstackstatus- NOTICE: Any jobs which erroneously failed on missing traceroute packages should be safe to recheck now | 19:54 | |
| *** topol has quit IRC | 20:09 | |
| *** sridhar_ram1 has joined #openstack-heat-translator | 20:14 | |
| *** sridhar_ram has quit IRC | 20:15 | |
| *** sridhar_ram1 has quit IRC | 20:29 | |
| *** spzala has quit IRC | 20:37 | |
| *** topol_ has joined #openstack-heat-translator | 20:56 | |
| *** spzala has joined #openstack-heat-translator | 21:04 | |
| *** spzala has quit IRC | 21:09 | |
| *** bobh_ has quit IRC | 22:02 | |
| *** sridhar_ram has joined #openstack-heat-translator | 22:27 | |
| *** bobh_ has joined #openstack-heat-translator | 23:15 | |
| *** bobh_ has quit IRC | 23:17 | |
| *** sridhar_ram has quit IRC | 23:34 | |
| *** bobh_ has joined #openstack-heat-translator | 23:38 | |
| *** bobh_ has quit IRC | 23:38 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!