16:05:03 #startmeeting JOID 16:05:03 Meeting started Wed Sep 7 16:05:03 2016 UTC. The chair is narindergupta. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:05:03 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:05:03 The meeting name has been set to 'joid' 16:15:19 #info https://www.irccloud.com/pastebin/y4ub3ohr/ 16:19:03 #info include the directories and files will be removed in D release which we kept it for legacy purpose 17:53:33 narindergupta: ping 17:53:50 bryan_att, hi how are you? 17:54:31 fine, just an issue with JOID deploy, cloned yesterday; tried twice and it ends with a keystone error 17:54:49 https://www.irccloud.com/pastebin/dKStScXQ/ 17:55:01 is it master build or stable ? 17:55:06 Master 17:55:17 Should I be using stable? 17:55:44 it should not matter as both are same 17:55:56 and i am hopinh juju status shows no error? 17:56:03 JuJu status looks fine 17:56:15 this is problem Unable to establish connection to http://api.None:5000/v2.0/tokens 17:56:22 yes 17:56:50 please send meyasml files 17:56:56 bundles.yaml first? 17:57:00 ok 17:57:08 also your labconfig.yaml 17:57:19 https://usercontent.irccloud-cdn.com/file/uCkPZydN/bundles.yaml 17:57:42 https://usercontent.irccloud-cdn.com/file/LuHLdupX/labconfig.yaml 17:59:29 ok in your bundles.yaml we have os-public-hostname: api.None 18:00:17 bryan_att, please send me deployconfig.yaml as well 18:00:33 https://usercontent.irccloud-cdn.com/file/SayJNE6E/deployconfig.yaml 18:09:54 will you please run this command python genBundle.py -l deployconfig.yaml -s os-nosdn-nofeature-nonha > bundles.yaml 18:10:01 and send me bundles.yaml 18:10:26 it looks like some issue in your case while in my case almost similar value no issues 18:10:41 https://usercontent.irccloud-cdn.com/file/73EATKP4/bundles.yaml 18:12:28 bryan_att, in this file looks like everything is ok 18:12:39 somehow your bundles.yaml is wrong 18:12:58 is it generated upon the deploy? 18:13:02 yes 18:13:13 and placed under joid/ci 18:13:22 what generates it? 18:13:45 which option r u using in -f here? 18:14:04 you mean in the deploy command? 18:14:10 yes 18:14:21 ./deploy.sh -o mitaka -s nosdn -t nonha -l attvirpod1 18:14:34 not using -f 18:14:46 that should not add api then 18:15:14 will you please send me console log for deployment? 18:15:18 sure 18:15:37 it seems code is working and manually i verified it 18:15:51 so we need to find out the error which is causing it 18:19:15 https://usercontent.irccloud-cdn.com/file/F1ImkPIr/deploy.log 18:19:49 I see "+ keystone_PUBENDPOINT=api.None" 18:20:26 right after https://www.irccloud.com/pastebin/uCP3LUwt/ 18:21:26 yeah here is the problem python genBundle.py -l deployconfig.yaml -s os-nosdn-none-nonha-xenial_mitaka_publicapi 18:21:33 publicapi should not be added 18:23:19 so I can patch it locally and retry? what do I change? or should I wait for a patch? 18:26:30 bryan_att, do you have deployment.yaml in your local directory? 18:27:12 in joid/ci ? no 18:27:42 bryan_att, ok that was root cause of issue. I will work on it meanwhile please copy that from ~/.juju/ 18:27:59 and cleanup and restart the deployment 18:28:36 ok, maybe this was an issue with how I redployed without redeploying maas I had captured your advice on that on the copper wiki at https://wiki.opnfv.org/display/copper/Joid 18:28:46 https://www.irccloud.com/pastebin/qzoSyyVl/ 18:28:58 is that incomplete? 18:29:15 no its not an issue with reployment with maas 18:29:41 this is issue where deployment.yaml missing from local directory which should get copied if does not exist 18:29:55 ok 18:30:24 it should be deployment.yaml file not envronments.yaml 18:30:38 as environments.yaml file i am copying it anyway 18:30:58 in my instructions on how to redeploy ? 18:32:34 no in my script 18:32:57 i usually copy everything now and your instructions are not needed anymore 18:33:03 as i have patched it 18:33:09 but missed deployment.yaml 18:33:51 ok, so I can redeploy without having to copy anything... i.e. I can just run the deploy command on a clean clone of JOID and it will copy everything as needed. 18:34:32 yes it should 18:34:55 but due to this bug you need to check whether you have deployment.yaml in ~/.juju/ or not? 18:35:14 if not then copy it for now meanwhile i am putting a patch in joid to fix it 18:37:14 yes, it's there. I'll copy and redeploy 18:37:44 yes you can do that 18:37:48 that will fix it 18:37:56 but i am putting a patch 18:38:01 may be just wait 18:38:04 for 5 minutes 18:38:09 then you can reclone 18:40:46 bryan_att, please review https://gerrit.opnfv.org/gerrit/20709 18:42:25 bryan_att, please clone it now and retry 18:43:04 will do 18:45:14 thanks 19:13:54 bryan_att, i think bundles.yaml should be created by now. Will you please check the latest one? 19:17:07 ok, will check soon - at lunch 19:22:48 ok no problem 19:35:55 narindergupta: looks good 19:39:13 cool 23:06:48 narindergupta: it timed out with all the services in state "Waiting for agent initialization to finish" 23:11:37 bryan_att, we need to see why there is no ip address defined. sometime in MAAS dhcp does not find free ip address 23:12:04 please try to log into maas server and checks for /var/log/syslog 23:13:25 what do I look for there? 23:13:37 in maas.log 23:14:51 I see in the MAAS UI that the nodes are in "failed deployment" 23:19:50 The servers have IP addresses, I can ssh to them. 23:20:12 I'll clean and try again. 23:21:12 maybe I forgot to shut them off last time 23:24:05 lets see look for no ip address 23:24:28 i wish i get access to your system and see 23:24:42 failed deployment may be 23:25:15 so you need to release both the servers from maas and run ./cleanup.sh 23:30:44 ok, did that, it's redeploying 23:31:07 We can do a bluejeans session if you have an account there - I've used it with RedHat 13:31:21 David_Orange, hi good morning. 13:32:44 narindergupta: Hi 13:33:28 David_Orange, yeah heat have issues with public apis. And we knows that it is not responding and working with those. 13:33:53 so do we have the action plan or area we can concentrate to get it working? 13:33:58 narindergupta: i will follow my test, i can not understand why it is failing 13:34:14 i will try to remove the unit and reinstall it 13:34:30 maybe the service installation order have an impact 13:35:46 hun that wiered it should not be though 13:36:11 it is only a guess, i will test it now 13:36:50 but if the heat installation need to call some other apis, it may fails because it does not use internal urls 13:37:58 for internal urls i could not options in the heat config. so heat has to modified for that 13:39:24 as you have seen on the doc i sent, it is only a question of performance enhancement to use internal url, with the reverse proxy it will work on all configurations 13:40:00 but we install it at the end, and mybe the heat post install procedure needs to access apis 13:40:22 you mean creating domain setup? 13:40:27 yes 13:40:38 we can check that 13:40:46 or some other scripts 13:40:54 its part of action in charm 13:41:09 it does 13:41:17 oh ok 13:41:30 from keystoneclient.v3 import client 13:41:37 do you want me to avoid it at later stage 13:41:58 avoid what ? 13:42:39 create domain at the end 13:44:51 at the end of the charm ? you can trigger that or not ? 13:45:18 we can not trigger in charm installation since it is an action 13:45:25 and we are using juju 13:45:36 we are using juju-deployer 13:49:53 David_Orange, yes domain-setup uses the api to create the role 13:50:40 narindergupta: i removed heat unit and service, and tried to launch "juju-deployer -c bundles.yaml openstack-phase1" to reinstall it, but i got that: "cannot add unit 1/1 to service "heat": cannot add unit to service "heat": service is not alive'" 13:51:26 can u run juju status heat 13:51:38 it usually takes time to destroy the unit 13:51:59 uju status heat 13:51:59 environment: opnfv-orangepod1-maas 13:51:59 machines: {} 13:51:59 services: {} 13:51:59 networks: 13:52:00 subnet-1: 13:52:00 provider-id: subnet-1 13:52:01 cidr: 192.168.1.0/24 13:52:01 subnet-2: 13:52:02 provider-id: subnet-2 13:52:02 cidr: 192.168.11.0/24 13:52:03 subnet-3: 13:52:15 ok can u run it now? 13:53:52 and run this command juju-deployer -vW -d -t 7200 -r 5 -c bundles.yaml xenial-mitaka 13:54:14 rather than openstack-phase1 as target 13:54:20 ok 13:57:29 this is the rc file heat uses 13:57:31 cat /root/admin-openrc-v3 13:57:31 # Service credentials for Keystone v3 13:57:31 export OS_REGION_NAME=RegionOne 13:57:31 export OS_PASSWORD=P5Sm66VmPNK2WtBmsk6drzZKZFrPwgYjc5ZfcVBf33KrYZYpsPgd7Hc6xnLVCYFq 13:57:31 export OS_AUTH_URL=http://10.6.1.199:35357/v3 13:57:32 export OS_USERNAME=heat-cfn_heat 13:57:34 export OS_TENANT_NAME=services 13:57:36 export OS_PROJECT_DOMAIN_ID=default 13:57:38 export OS_USER_DOMAIN_ID=default 13:57:42 export OS_PROJECT_NAME=services 13:57:44 export OS_IDENTITY_API_VERSION=3 13:58:06 same answer 13:58:07 cannot add unit 1/1 to service "heat": cannot add unit to service "heat": service is not alive', 13:58:20 it should not add unit 13:58:43 it should create new unit of heat 13:59:23 juju deploy heat local:xenial/heat 13:59:52 then we can try the juju-deployer 13:59:55 error: invalid service name "local:xenial/heat" 14:00:43 hun i need to think about it what i tried last time 14:01:23 ok 14:01:38 juju deploy local:xenial/heat 14:02:29 ERROR cannot add service "heat": service already exists 14:02:37 but still got: 14:02:37 juju status heat 14:02:37 environment: opnfv-orangepod1-maas 14:02:37 machines: {} 14:02:37 services: {} 14:02:53 hun looks like clean up few issues then 14:03:33 you are on pod1 right? 14:03:45 yes 14:04:26 ok there are few error in rabbitmq 14:04:43 gateway service is not running says blocked 14:04:53 can you go to byobu 14:05:18 it got an erro on gateway, the public ip was not set 14:05:32 sure 14:05:51 ok i am at byobu 14:07:18 the ip was not set on gateway but did not get an error on jenkins 14:07:20 + juju run --unit nodes/0 'sudo ip a a 10.0.1.4/24 dev br-ex' + juju run --unit nodes/0 'sudo ip l set dev br-ex up' 14:09:19 i think in your lab we do not set ip on external network through MAAS 14:09:25 cani have access to MAAS 14:09:53 currently username password to access site is not working 14:09:57 it set it through openstack.sh 14:10:20 ok i check that 14:10:53 the public ip is set on line 138 of openstack.sh 14:12:21 David_Orange, if you need ip then we can do it through maas itself like we do it for other labs 14:12:44 there is no harm in defining the dhcp on this interface through maas 14:13:10 oh but we do not know the what ip to set for proxy 14:13:20 never mind 14:14:16 yes :) 14:14:23 it needs to be fixed 14:17:51 rabbitmq throwing error on leader status change 14:17:55 can i deploy? 14:18:15 yes 14:18:34 with jenkins ? 14:18:47 yes 14:18:53 good for me 14:20:33 ok redeploying it now 14:21:04 did you shutdown bootstrap node? 14:24:43 was there any change in ssh config 14:24:59 i can connct to qemu through sh keys] 14:28:09 looks like it redeployed yesterday as well 15:01:38 sorry, i was in a meeting. i redeployed it yesterday 15:02:30 David_Orange, ok i have redploy maas as bootstrap had some issue 15:02:42 ok 18:43:11 bryan_att, any update on deployment? 13:15:15 narindergupta: the deploy worked although I had to run the the command manually at the end " ./openstack.sh nosdn attvirpod1 xenial mitaka". I can send you the deploy log if needed. 13:15:54 bryan_att, please send me as deployment should run the openstack.sh 13:16:30 bryan_att, but heat domain set up ran with juju? 13:18:02 https://usercontent.irccloud-cdn.com/file/73LpBM1k/deploy.log 13:18:23 Not sure about the heat domain yet. I haven't run my Tacker test yet. 13:33:20 bryan_att, looks like external network was not created 13:33:22 public endpoint for network service in RegionOne region not found 13:34:20 does juju status shows any error? if not then please check bundles.yaml also. whats the region name? 13:34:24 the net was created when I re-ran the openstack script 13:34:43 RegionOne 13:35:06 No errors in JuJu 13:35:50 ok looks like timing issue. 13:36:24 i can see after juju-dpeloyer completes your timeout of 30 seconds expires 13:36:43 so either i have increase the time out for you here 13:36:51 or find some alternative. 13:37:00 before i runs openstack.sh 13:37:47 will you please run juju action do heat/0 domain-setup 13:37:54 again before you can start tacker 03:02:06 narinder`: ping 03:16:58 Hi! joid guys. I am a yardsticker and I am working on fixing the yardstick CI job failure in joid-os-nosdn-lxd-ha-baremetal-daily-colorado. I have a few questions. I have figured out a raw format image is needed for nova-lxd. What other requirements does lxd scenario needs? Can anyone help? 12:32:42 Narinder Gupta proposed joid: modified the default URL to Boron RC3.5 https://gerrit.opnfv.org/gerrit/21015 12:32:47 A comment has been added to a proposed change to joid: modified the default URL to Boron RC3.5 https://gerrit.opnfv.org/gerrit/21015 12:33:05 A comment has been added to a proposed change to joid: modified the default URL to Boron RC3.5 https://gerrit.opnfv.org/gerrit/21015 12:33:18 A comment has been added to a proposed change to joid: modified the default URL to Boron RC3.5 https://gerrit.opnfv.org/gerrit/21015 12:33:21 Merged joid: modified the default URL to Boron RC3.5 https://gerrit.opnfv.org/gerrit/21015 14:19:33 David_Orange, hi how r u? 14:19:59 Hi narinder, fine and you ? 15:18:55 narindergupta: ping 15:21:05 I have an issue with the JOID deployment of Heat, that is not occuring with Apex. What version of Heat are you deploying? 15:21:08 bryan_att, how are you 15:21:21 fine, just have an issue with Heat. 15:21:27 bryan_att, let me check with charm 15:21:46 bryan_att, let me check 15:22:52 it is 1.6.0 15:23:01 1:6.0.0-0ubuntu1.1 15:23:02 Heat on JOID rejects the stack CP1.properties 'port_security_enabled' flag (Apex Heat accepts this) , resulting in "Resource CREATE failed: BadRequest: resources.CP1: Unrecognized attribute(s) 'port_security_enabled' Neutron server " 15:23:25 OK, let me check with Apex on the version they are deploying. 15:25:27 bryan_att, ok 15:32:12 narindergupta: just a little status on heat, i have to go: i tried your patch https://www.irccloud.com/pastebin/y4ub3ohr/ but i got "message": "You are not authorized to use create." error message, so i will follow my tests tomorrow. FYI i found a bug for heat+publicapi, i will push the patch tomorrow 15:32:45 ok sounds good to me 18:10:46 narindergupta: Apex is deploying Heat version 6.0.1-0.20160820004902.13aaa7e.el7.centos. How does that compare to 1:6.0.0-0ubuntu1.1 ? Both are used in OPNFV Colorado, but I'm seeing differences in behavior. How would I find out what version is in these packages? 18:14:08 Ubuntu heat packages are at lacunhpad https://launchpad.net/ubuntu/+source/heat 18:14:17 narindergupta: Does JOID enable the port_security extension as mentioned in prerequisites section of the Tacker manual installation guide? Step 4: http://docs.openstack.org/developer/tacker/install/manual_installation.html#pre-requisites 18:19:29 bryan_att, by default it is disabled in neutron-api charm 18:20:17 narindergupta: this needs to be the setting - this is what Apex deploys and works. https://www.irccloud.com/pastebin/xOnqwuEI/ 18:20:37 but it is needed you can enable it using juju set neutron-api enable-ml2-port-security=true 18:20:38 "extension_drivers =port_security" at least 18:20:59 by default this feature is false 18:21:29 OK, for Colorado I can do that as part of my tests setup I guess - but for Danube can we enable it by default? It's required for Tacker to work. 18:21:55 And I'd like it to be enabled by default in Colorado if that doesn't break something else. 18:22:16 bryan_att, we need to see the implications on other tests if we enable it. So just made a request in joid and we will enable it in D release 18:22:56 bryan_att, currently C release it would be difficult as we are releasing it soon. 18:23:24 and everything is stable. I can try for experimental basis in master branch though 03:15:07 Hi! joid guys. I am a yardsticker and I am working on fixing the yardstick CI job failure in joid-os-nosdn-lxd-ha-baremetal-daily-colorado. I have a few questions. I have figured out a raw format image is needed for nova-lxd. What other requirements does lxd scenario needs? Can anyone help? 03:47:13 Jing, hi jing as you know LXD is contianer based hypervisor. So all images on the nova should be lxd or lxc based. 03:48:09 and any application or test you run on the container should be same. As after initiating image on nova you should able to ssh into it and run any commands like apt-get install etc etc... 03:49:08 Jing, what else information do you need? As part of LXd deployment installer upload the lxc images for cirros and ubuntu lxd images as well 03:49:18 Jing, what else information do you need? As part of LXd deployment installer upload the lxc images for cirros and ubuntu lxd images as well 03:49:52 please let me know in case you need any specific information on nova-lxd driver and images apart from what i provided 04:12:01 #opnfv-onos 04:33:47 #endmeting 04:34:22 Jing, do you have any other query on joid? 07:19:25 narindergupta: hi, Just for clarity, in lxd we need to used lxc images instead of normal images? What is the difference between them? 16:02:56 arturt: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 16:03:02 #stopmeeting 16:03:15 #endmeeting