16:00:57 <narindergupta> #startmeeting JOID 16:00:57 <collabot> Meeting started Wed Aug 31 16:00:57 2016 UTC. The chair is narindergupta. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:57 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:57 <collabot> The meeting name has been set to 'joid' 16:01:16 <narindergupta> #info Narinder Gupta 16:03:57 <narindergupta> #topic Agenda 17:04:29 <bryan_att> narindergupta: ping 17:04:40 <narindergupta> bryan_att, hi 17:04:59 <bryan_att> hi, I need to know how to retrieve the nova service password set by JOID 17:05:17 <narindergupta> you can do it in charm 17:05:20 <bryan_att> I am testing Tacker installation and need this so the client can connect 17:05:30 <bryan_att> I need to know how to retrieve the current password 17:05:57 <bryan_att> is it in some configuration file somewhere, or retrievable by juju? 17:06:55 <narindergupta> r u looking for nova service? or keystone? 17:07:13 <bryan_att> nova service user and password, as part of the "services" project 17:07:53 <bryan_att> here is the tacker.conf section I need to update https://www.irccloud.com/pastebin/qj2ZLCsC/ 17:08:11 <bryan_att> (project needs to be "services" per the JOID install) 17:08:32 <bryan_att> I have the other values, e.g. auth URL 17:13:59 <narindergupta> we do not have oproject service 17:14:05 <narindergupta> there is service project 17:14:24 <narindergupta> pbut passwork should be keystone password to talk to api 17:14:48 <narindergupta> not sure whether password set at individual service level 17:15:04 <narindergupta> but i can have a look 17:15:15 <narindergupta> specially for nova cloud controller 17:15:16 <bryan_att> yes, e.g. when creating a new service user you can specify the password for the service user 17:15:33 <bryan_att> the project in joid is called "services" 17:15:47 <bryan_att> https://www.irccloud.com/pastebin/zrGxVrXV/ 17:16:23 <bryan_att> I see in the openstack docs how to set a password, but not how to retrieve the current one 17:16:51 <bryan_att> I will try the admin user password but I doubt if that will work 17:17:34 <narindergupta> bryan_att, i got it in nova.conf under glance section 17:17:55 <bryan_att> where is nova.conf? 17:18:05 <narindergupta> /etc/nova/ 17:18:10 <narindergupta> of nova-cloud-controller 17:18:38 <narindergupta> it shows under glance section 17:18:49 <narindergupta> will that we good enough 17:25:58 <bryan_att> ok, fyi here is the command to retrieve: ssh -x -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no ubuntu@$NOVA_HOST sudo grep -v rabbit /etc/nova/nova.conf | awk "/password =/ { print \$3 }" 17:26:02 <narindergupta> sorry it is part of keystone authentication token 17:26:23 <bryan_att> what does that mean? 17:27:03 <bryan_att> btw, is that value in the conf file the password or the hash of it? 17:27:04 <narindergupta> this means it is looking for rabbitmq password 17:27:24 <bryan_att> what is "it"? 17:27:44 <narindergupta> that is randomly generated for each deployment 17:28:10 <bryan_att> by "it" do you mean the tacker client? 17:28:41 <narindergupta> whoever is executing this statement ssh -x -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no ubuntu@$NOVA_HOST sudo grep -v rabbit /etc/nova/nova.conf | awk "/password =/ { print \$3 }" 17:29:47 <bryan_att> ok, my script will do that; it is ignoring the lines with "rabbit" since there is also a "rabbit_password" field there; I created that command to use in my script to retrieve the password. 17:30:10 <bryan_att> (sorry if that was unclear) 17:30:30 <narindergupta> i thought it is used by some script 17:31:34 <bryan_att> yes, it will be used by the script I am developing to install tacker: https://git.opnfv.org/cgit/models/tree/tests/utils/tacker-setup.sh 17:32:00 <bryan_att> in that script I have to customize tacker.conf for the installation 17:32:49 <bryan_att> trozet does this using a puppet module but I developed a more direct scripted installer since I need to know how tacker works and is installed. 17:34:33 <narindergupta> there is a section in the conf file keystone_authtoken 17:34:49 <narindergupta> i can see uasrename and password there 17:34:59 <narindergupta> along wiht project_name as services 17:36:56 <bryan_att> where is keystone_authtoken? 17:46:38 <narindergupta> that should get as part of keystone i belive 08:05:46 <virginie_> Hi there, I am using opnfv with juju installer, I am trying to deploy opencontrail with juno on trusty platform. When I launch the deploy.sh script, after some minutes, the deployment stops with the following error, "deployment 'trusty-juno-nodes' not found. Available openstack-phase1, peoenstack-pahse2, trusty-mitaka, trusty-mitaka-nodes" Any idea of what I should use for my deployment ? 08:06:33 <David_Orange> virginie_: Hi 08:06:57 <David_Orange> virginie_: Joid is not compatible with Juno 08:07:41 <David_Orange> the C release, is not compatible with juno to be more precise 08:08:24 <David_Orange> but i may be wrong, do you talk about your installation with narinder ? 08:10:21 <David_Orange> virginie_: i never installed the ocl sdn but in my point of view, only the trusty is compatible with C release and OCL 08:11:01 <David_Orange> not trusty, but liberty 08:11:45 <David_Orange> i check the installations with jenkins and let you know what passed the CI 08:22:31 <virginie_> David_orange yes this is the installation I was talking with Narinder 08:22:56 <virginie_> ok so I need to use liberty, I am not sure opencontrail works on liberty 08:23:04 <David_Orange> virginie_: he validate the juno scenario N 08:23:05 <David_Orange> ? 08:24:26 <David_Orange> virginie_: i will check with morgan from functest project what ocl scenario where validated, from a CI perspective, but i dont think the JOID C release is compatible with juno (i am checking that) 08:24:41 <virginie_> ok thanks 08:34:44 <David_Orange> virginie_: i confirm juno is not supported in C release, but was in B release 08:43:06 <virginie_> David_orange: thanks. Ok so I have to install the B release 08:44:23 <David_Orange> virginie_: i am not sure OCL scenario was tested on B release, i will ask morgan at the end of its meeting 08:51:16 <virginie_> I am not sure too.... 08:51:38 <virginie_> so just to recap, it seems that no ocl scenario has been yet tested right ? 08:51:56 <David_Orange> i will check with him at the end of its meeting and we can make a call if you want 08:55:56 <David_Orange> virginie_: morgan confirm what i though, none of the OCL scenario was tested with the CI, but Narinder said he make one pod functionnal 08:56:12 <David_Orange> virginie_: the better will be to check with him 08:56:24 <virginie_> is it possible to exchange by email ? 08:56:33 <David_Orange> sure 08:57:17 <David_Orange> virginie_: i send you my contact by MP 13:28:31 <narindergupta> David_Orange, hi 15:15:35 <David_Orange> narindergupta: hi, how are you ? 15:16:00 <narindergupta> David_Orange, i am fine how are you? How was your vacation? 15:18:54 <David_Orange> narindergupta: i am fine, tired because of my stone work on my house, but it is a good tiredness 15:20:20 <David_Orange> narindergupta: i talk with virginie_ this morning, and i added an item for tomorrow meeting; she would like to have a status on OCL and an idea of next OCL features integration 15:25:24 <David_Orange> narindergupta: i am looking for docs about lxd intergration in joid, for an internal workshop about containers (more oriented on docker, but a lxd perspective can be good) 15:25:38 <David_Orange> narindergupta: do you have something on that subject ? 15:28:07 <narindergupta> David_Orange, internal workshop i have to ask my lxd charm team 15:28:37 <David_Orange> it would be great 15:28:48 <narindergupta> David_Orange, but i also can do it for a bit for a team and virgine also can help as we giled anough knowledge on that 15:29:09 <narindergupta> David_Orange, please let me know what would be good time? 15:30:18 <David_Orange> narindergupta: virginie_ and lxd are 2 separates subject, i did not undestand your lasts lines 15:32:36 <narindergupta> what i am saying is i can also give the internal workship about lxd integration in joid and how to use containers using the stack 15:33:28 <narindergupta> David_Orange, virginie has the working knowledge ok lxd usage in openstack 15:34:59 <David_Orange> usage, pros (and cons :) ) 18:20:23 <bryan_att> narindergupta: ping 18:20:35 <narindergupta> bryan_att, pong 18:21:21 <narindergupta> bryan_att, how are you doing? 18:21:22 <bryan_att> narindergupta: hi, do you know how the values in the heat policy.json file are set? I am running into a permissions issue trying to use heat to create a stack. 18:21:52 <bryan_att> e.g. ""stacks:create": "rule:deny_stack_user"," 18:22:10 <bryan_att> I think the issue could be the settings in that policy file 18:22:33 <narindergupta> bryan_att, i have to check but our team will be doing minium and yardstick and functest are passing in creating stack and using it 18:23:12 <bryan_att> perhaps the settings in the file vary by scenario? 18:23:52 <narindergupta> may be but i do not think so we are changing in heat differently for scenarios though through charm 18:24:14 <bryan_att> can you point me to a specific test that uses a heat stack user? I am trying to get tacker running on OPNFV and having issues with the tacker user as a services project user, getting access to the heat APIs 18:24:39 <narindergupta> bryan_att, do you need policy.json file? 18:24:51 <bryan_att> No, I have that from the heat node. 18:24:56 <narindergupta> ok 18:26:13 <narindergupta> just now looked into charm and could not find any where we are modifying this file in charm 18:26:42 <narindergupta> could be default valued defined in the package 18:26:48 <narindergupta> heat deb package 18:29:15 <bryan_att> Has anyone done work with Tacker on JOID? 18:30:19 <narindergupta> bryan_att, no idea but may be people from openo team and open source mano team might have done it as they are writing plugin for generic vnf provider 18:30:51 <bryan_att> OK, but no work in OPNFV, and no scenario for the SFC project yet on JOID? 18:31:10 <narindergupta> we have SFC with onos in joid currently 18:31:15 <narindergupta> but not with odl 19:13:19 <bryan_att> narindergupta: it seems that heat is trying to use keystone API V3 concepts (the "domain") which is not implemented in Colorado AFAIK - the error is "ERROR heat.common.keystoneclient [req-6d065355-4dbe-417f-a93b-ee32929a8b46 - admin - default default] Domain admin client authentication failed" 19:57:03 <narindergupta> bryan_att, so you need v3 with keystone. 19:57:32 <narindergupta> charm supports it but not sure how to introduce now to opnfv 19:57:47 <bryan_att> narindergupta: not sure why, AFAIK we are using keystone V2 in Colorado 19:58:13 <narindergupta> heat is trying to use keystone API V3 concepts (the "domain") which is not implemented in Colorado AFAIK 19:58:38 <narindergupta> so looks like heat needs v3 with the template you are trying 19:59:06 <narindergupta> to create stack 19:59:56 <bryan_att> so why would this work with Tacker in Apex and not in JOID? 20:00:59 <narindergupta> maybe apex already implemented v3? 20:01:17 <narindergupta> can u check with apex team? 23:49:38 <bryan_att> narindergupta: what other projects are using Heat under JOID? Can you point me to tests/install info for those projects e.g. how they setup their stack users and logs of their tests? 23:59:02 <bryan_att> narindergupta: I'm now sure there is an issue with the Heat installation under JOID. I tried to create a stack using the Horizon UI and got the same "authorization failed" error for the admin user. 04:00:31 <bryan_att> narindergupta: I verified that Heat works in Apex but not in JOID. Need your help to resolve this issue so I can continue work on Tacker. 04:01:10 <narindergupta> bryan_att, i am also not expert in heat need to find people who knows heat 04:01:29 <narindergupta> bryan_att, let me try to find who can help then. 04:01:43 <bryan_att> OK, the charms team that worked on the heat charm should be able to help? 04:01:56 <narindergupta> charmers may not help 04:02:22 <narindergupta> because deployment wise there is no issue and also creating the heat stack works in yardstick 04:02:36 <narindergupta> as well as both rally and functest are passing. 04:03:07 <bryan_att> ok, let me know what I can do to help. I'll get you the relevant openstack config data from Apex, to compare with at least. 04:03:33 <narindergupta> may be we need to include the some heat experts. Also if you can send the steps to reproduce the issue with help. 13:28:57 <narindergupta> hi David_Orange 13:29:58 <narindergupta> David_Orange, you asked me to look into the heat public api issue and i did look into it bur could not find option to use internal URL 13:30:12 <narindergupta> as no such option exist today like other services are. 13:30:24 <David_Orange> narindergupta: hi 13:30:56 <narindergupta> David_Orange, please go through the message and let us know what changes we can make regaring the heat 13:30:57 <narindergupta> ? 13:31:06 <narindergupta> for public API implementation 13:31:12 <narindergupta> on orange pod 13:31:27 <David_Orange> ok, i will make some tests/changes 13:31:38 <David_Orange> and let you know 13:32:20 <narindergupta> David_Orange, sure thanks 14:24:03 <bryan_att> narindergupta: here is the output for the heat failure https://www.irccloud.com/pastebin/eCuB4OP0/ 14:24:40 <bryan_att> narindergupta: here is the heat template I used (works on Apex) https://usercontent.irccloud-cdn.com/file/ctAc8h28/hello-world.hot 14:26:31 <narindergupta> bryan_att, i will see what can i do. 14:26:46 <narindergupta> bryan_att, also will try something simple template as well 14:27:41 <bryan_att> sure, the one I tried is a simple one generated by the Tacker project from a TOSCA template. I installed it successfully on the 0906 Apex deploy, using the Horizon UI. 14:29:46 <narindergupta> bryan_att, i do not experience in heat but when i ran juju command to create the machine and add vnf it works but again i tested like week back 14:30:04 <narindergupta> but lets see what can i do with heat here. 15:35:24 <bryan_att> narindergupta: Found the fix for the Heat issue. I'll create a Jira issue and describe what I did. 15:35:41 <narindergupta> bryan_att, ok 15:36:19 <narindergupta> bryan_att, let me know and i will see how can i accomodate that change 15:37:21 <bryan_att> narindergupta: here is the procedure https://www.irccloud.com/pastebin/y4ub3ohr/ 15:40:54 <narindergupta> bryan_att, as part fo deploy.sh we already setup domain 15:41:02 <narindergupta> why do you need to do again? 15:41:26 <bryan_att> it was not setup in the deployment in my lab. 15:41:38 <bryan_att> or it didn't work 15:42:23 <bryan_att> I deployed on Aug 23 - maybe you fixed that after? 15:43:04 <narindergupta> no no change atfer that. https://gerrit.opnfv.org/gerrit/gitweb?p=joid.git;a=blob;f=ci/deploy.sh;h=dbe0ef97c30d713279520538982db300ea9a91ff;hb=06ccc9f0c3b196831353cd5f5497a0462f8fec57 15:43:14 <narindergupta> line no 158 15:43:45 <narindergupta> do you have console log of deployment by any change 15:43:48 <narindergupta> i can verify 15:44:08 <narindergupta> bryan_att, i think that explains why heat was not working in your case 15:44:46 <bryan_att> let me see if I still have it 15:44:50 <narindergupta> juju action do heat/0 domain-setup basically setup the domain and change the configuration needed 15:45:14 <narindergupta> so no need to define those steps 15:48:48 <bryan_att> https://usercontent.irccloud-cdn.com/file/1NZpVUeg/deploy.log 15:50:39 <bryan_att> ok, let me reclone/redeploy and see if that works. The deployment log is attached. Sure would have been nice to know that juju command was all I needed ;-) 15:58:24 <narindergupta> i can see action was queue up ++ juju action do heat/0 domain-setup 15:58:24 <narindergupta> + status='Action queued with id: e82c98cd-6e38-47c7-89f4-ca6d71ad6721' 15:58:25 <narindergupta> + echo Action queued with id: e82c98cd-6e38-47c7-89f4-ca6d71ad6721 15:58:25 <narindergupta> Action queued with id: e82c98cd-6e38-47c7-89f4-ca6d71ad6721 15:59:00 <narindergupta> if it was not created then may be action issue 16:04:30 <narindergupta> startmeeting JOID 16:04:37 <collabot> narindergupta: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 16:04:55 <narindergupta> #endmeeting