16:05:41 <narinder> #startmeeting JOID
16:05:41 <collabot> Meeting started Wed Jun  7 16:05:41 2017 UTC.  The chair is narinder. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:05:41 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:05:41 <collabot> The meeting name has been set to 'joid'
16:05:52 <narinder> #info Narinder Gupta
17:17:35 <narinder`> durschatz: hi Dave good afternoon
17:17:54 <narinder`> hope we are good for OPNFV event
23:37:55 <fenar> https://www.irccloud.com/pastebin/Vs5XlWfl/
22:38:32 <ruijing1> hi, anyone in opnfv summit?
00:02:32 <narinder> ruijing1, me durschatz jmorgan1 bryan_att are here. what about you?
02:51:54 <yibo> Hi, I'm Yibo Cai from ARM. We're planning to deploy OPNFV on ARM with Joid. We see there's plan to support ARM64 on Joid and want to know the current status and what we can help. Thanks.
12:22:05 <czechnology> Hi, would anyone have hint for me with JOID install please?
12:22:09 <czechnology> I have successfully performed the MAAS deployment and now I'm attempting to deploy opnfv with ./deploy.sh
12:22:15 <czechnology> However, the script hangs on this task:
12:22:26 <czechnology> juju.cloudconfig userdatacfg_unix.go:410 Fetching agent: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz <[https://streams.canonical.com/juju/tools/agent/2.2.0/juju-2.2.0-ubuntu-amd64.tgz]>
12:22:34 <czechnology> Even before that, I get errors about failed connection attempt:
12:22:39 <czechnology> juju.provider.common bootstrap.go:497 connection attempt for 192.168.10.152 failed: /var/lib/juju/nonce.txt does not exist
12:22:44 <czechnology> Interestingly, manually connecting to the host works ok:
12:22:47 <czechnology> ubuntu@jumphost:~$ ssh ubuntu@192.168.10.152
12:22:57 <czechnology> Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-79-generic x86_64)
12:23:00 <czechnology> ...
12:23:03 <czechnology> ubuntu@bootstrap:~$ cat /var/lib/juju/nonce.txt
12:23:06 <czechnology> user-admin:bootstrap
12:23:09 <czechnology> Any ideas what could be wrong? Thanks!
00:55:59 <ruijing1> hi, narindergupta
00:56:17 <ruijing1> I didn't see you in onpfv summit. did you attend the summit?
04:19:09 <ruijing1> hi, hw_wutianwei
04:19:30 <ruijing1> I am trying to insert auth key in vagrant+k8s
04:20:54 <ruijing1> sorry. I post to wrong place.
01:14:09 <hw_wutianwei> ruijing: hi, I don't understand what you mean.
01:42:49 <ruijing> Hi, hw_wutianwei. just ignore it. I post to wrong place.
01:54:08 <ruijing> I narinder
01:54:38 <ruijing> I am trying to work with yardstick to enable k8s & yardstck
01:55:21 <ruijing> some progress:
01:55:52 <ruijing> 1. we plan to use nodecontext instead of heatcontext to run yardstick in k8s
01:56:40 <ruijing> 2. installer to predeploy yardstck & vnf and insert auth key for vnf
01:56:53 <ruijing> 3. yardstick get basic information and run test case.
01:58:30 <narinder> ruijing, thats nice we have few vnf based on kubernetes and one of intern is trying to onboard.
01:58:49 <narinder> i think we will have end to end story soon
01:59:11 <narinder> ruijing, also what does predeploy yardstick means?
01:59:39 <narinder> ruijing, i thought they are docker images and just need to download and run
02:00:15 <ruijing> for openstack, yardstick can use heat to automatically create vm
02:00:42 <ruijing> but for k8s, yardstick cannot use heat to create container in k8s.
02:01:16 <ruijing> in short term, yardstick use nodecontext. it means installer can download and run vnf before yardstick run.
02:01:58 <ruijing> in long term, yardstick will develop k8scontext and automatically create container by k8scontext.
02:02:58 <ruijing> I have some vagrant env and work with yardstick team. if everyting is ok, we we move vagrant script to joid.
02:03:50 <ruijing> for E release, we plan to enable yardstick ping.
02:04:14 <ruijing> more cases are enabled in future release
02:21:40 <narinder> ruijing, ok sounds good
02:49:38 <ruijing> hi, narinder. do you have idea why joid-k8-nosdn-lb fails?
02:50:05 <ruijing> I assume it is jenkins enviorment issue
04:48:29 <narinder> ruijing, thats true k8 deployment passes but functest and yardstick should be disabled but runs and after failure stucks
12:40:09 <OPNFV-Gerrit-Bot> Narinder Gupta proposed joid: modified to enable the virtual install.  https://gerrit.opnfv.org/gerrit/36237
14:14:44 <OPNFV-Gerrit-Bot> Narinder Gupta proposed joid: modified to enable the virtual install.  https://gerrit.opnfv.org/gerrit/36237
15:40:43 <OPNFV-Gerrit-Bot> Narinder Gupta proposed joid: modified to enable the virtual install.  https://gerrit.opnfv.org/gerrit/36237
16:32:03 <OPNFV-Gerrit-Bot> Narinder Gupta proposed joid: modified to enable the virtual install.  https://gerrit.opnfv.org/gerrit/36237
16:39:34 <OPNFV-Gerrit-Bot> Narinder Gupta proposed joid: modified to enable the virtual install.  https://gerrit.opnfv.org/gerrit/36237
17:03:31 <OPNFV-Gerrit-Bot> Narinder Gupta proposed joid: modified to enable the virtual install.  https://gerrit.opnfv.org/gerrit/36237
17:13:30 <OPNFV-Gerrit-Bot> Merged joid: modified to enable the virtual install.  https://gerrit.opnfv.org/gerrit/36237