Friday, 2017-02-10

*** kevinz has joined #openstack-zun00:54
*** yuanying has quit IRC01:12
*** yuanying has joined #openstack-zun01:13
*** zhurong has joined #openstack-zun01:13
*** yanyanhu has joined #openstack-zun01:31
*** zhangjl has joined #openstack-zun01:32
*** zhangjl1 has joined #openstack-zun01:51
*** zhangjl has quit IRC01:52
*** zhurong has quit IRC01:52
*** zhangjl1 has quit IRC01:59
*** zhangjl has joined #openstack-zun01:59
*** zhurong has joined #openstack-zun02:12
*** zhurong has quit IRC02:25
*** zhurong has joined #openstack-zun02:28
*** zhurong has quit IRC02:38
*** kevinz has quit IRC02:48
*** kevinz has joined #openstack-zun02:49
*** zhurong has joined #openstack-zun02:52
*** harlowja has quit IRC02:53
*** zhurong has quit IRC02:59
*** lakerzhou has joined #openstack-zun03:01
*** sudipto_ has joined #openstack-zun03:02
*** sudipto has joined #openstack-zun03:02
lakerzhouhi~ Sudipto, regarding NUMA, I talked with a telco customer recently. They use CPU pinning without any sharing. They also use NUMA, because some VNFs request 30+ cores.03:18
sudipto_lakerzhou, hi you are saying NUMA restriction is not good?03:19
lakerzhouwe probably need to think about customer 's request.03:20
sudipto_lakerzhou, it's easy to remove that restriction...but the data structure should account for NUMA. While you can ask for a non numa based cpuset if you like.03:21
sudipto_So while coding, i will keep it in mind that NUMA isn't quite the restriction for dedicated...03:21
sudipto_however we will support a case where we are able to even provide cpusets/memory from a NUMA node, if requested.03:22
sudipto_does that sound ok to you?03:22
lakerzhouI am trying to confirm with you, if you know some NUMA request from NFV application. With the customer, we mainly talked about placement issue with NOVA.03:23
sudipto_placement == not having enough NUMA nodes available for a request?03:24
lakerzhouBut I don't have much insight about NUMA requirement from NFV application.03:24
lakerzhouthey complain about nova scheduler resulting non-optimal placement, because  30+ core with NUMA setting often ends up low cpu utilization03:26
sudipto_hmm...guess that problem needs further investigation.03:27
lakerzhouI can clarify the NUMA requirements with NFV vendor, but it may take long time to get feedback.03:27
sudipto_Ok, what i am saying is - from zun, we will provide the flexibility03:28
sudipto_if they want to do NUMA - they can, if they don't want to do that - they can still use it.03:28
*** diga has quit IRC03:31
lakerzhouI think there are two aspects of NUMA: 1. some applications require all CPUs from one NUMA node to gain high performance. 2. Some applications require NUMA awareness, so that all CPUs don't have to come from same NUMA node. The application has intelligence to efficiently  use CPU resources.03:33
lakerzhouthis is my understanding from reading. I can confirm this with NFV vender03:34
sudipto_lakerzhou, #2 don't think applies in the container's case.03:35
sudipto_#2 is when you would want to have NUMA awareness of the host's topology inside the guest.03:35
sudipto_In case of containers, there isn't a topology inside the container...03:36
lakerzhouAnyone has issue with "zun create"? --image option is new. It seems not working with my devstack environment.03:37
lakerzhousudipto_, good to know. My readings are based on VM not containers.03:37
lakerzhousudipto_, are you saying there is no NUMA topology support for container?03:38
sudipto_lakerzhou, you can say - a container should be on getting it's cpus from 1 NUMA node, but you can't create a NUMA topology like VMs' - experiments in the VM world have shown that if you can mock the NUMA topology of the host, inside the virtual machine - it results in better performance. But note that VMs are full fledged operating system...i am not sure if that case applies in case of containers.03:41
lakerzhousudipto_, I need to read more about NUMA for containers.03:55
*** pksingh has joined #openstack-zun03:58
lakerzhouHi pksingh~, I have a question about the new --image option in zun create.04:01
pksinghlakerzhou: Hello04:01
pksinghlakerzhou: Good Morning, yes please tell me04:01
lakerzhoupksingh, in my devstack environment, the newly created container stays in unknown state.04:02
openstackgerritSudipta Biswas proposed openstack/zun master: Introduce os-capability parsing  https://review.openstack.org/43092004:02
pksinghlakerzhou: any specific error04:03
lakerzhou this is command I used: zun create --name test --command "ping -c 4 8.8.8.8" -i cirros04:05
lakerzhouI don't see any error during creation. but let me dig more.04:05
pksinghlakerzhou: ok let me check if i can reproduce it04:05
lakerzhoupksingh: thanks,04:06
*** hongbin_ has joined #openstack-zun04:08
lakerzhoupksingh: 2017-02-09 21:55:14.888 ^[[01;31mERROR zun.image.glance.driver [^[[01;36mreq-c7c58cfc-42f0-4d30-8343-a0c96ba20a1d ^[[00;36madmin admin^[[01;31m] ^[[01;35m^[[01;31mImage cirros was not found in glance^[[00m04:11
lakerzhoupksingh: found the error in log, but the container state is still unknown.04:12
pksinghlakerzhou: give me 10 minutes,04:13
lakerzhoupksingh: sure. no rush04:13
*** sudipto has quit IRC04:16
*** sudipto_ has quit IRC04:16
pksinghlakerzhou: its working on my side04:19
pksinghlakerzhou: could you please paste your compute service logs04:19
pksinghlakerzhou: please paste at http://paste.openstack.org/ and provide the link04:20
lakerzhousure, is there other command or configure change that I should run before using the image?04:20
pksinghlakerzhou: your command is perfectly fine04:21
pksinghlakerzhou: i think '-i' option is for interactive mode, its not for image. image is positional parameter,04:22
lakerzhouhttp://paste.openstack.org/show/598333/04:24
lakerzhou  -i <image>, --image <image>04:24
lakerzhoulet me try again with --image04:24
pksinghlakerzhou: you dont need to put --image , just put image name at last04:27
mkrailakerzhou: --image option is removed from zunclient04:27
*** shu-mutou has joined #openstack-zun04:27
lakerzhoumkrai: when did it removed? I got error without "-i" or "-image".04:31
mkraiWhat is the error lakerzhou ?04:31
pksinghlakerzhou: i think your devstack environemnt is not updated, it looks like an older one04:31
lakerzhouerror: argument -i/--image is required04:32
lakerzhoulet me update my devstack environment first04:33
lakerzhoupksingh: can you please share your local.conf?04:34
pksinghlakerzhou: sure04:34
mkrailakerzhou: you can just update the zun only04:35
mkraiand restart the zun services rather then doing restack04:35
lakerzhouthis is only config related to zun in my local.conf: enable_plugin zun https://git.openstack.org/openstack/zun04:37
mkraithat's enough I guess04:38
lakerzhoumkrai: how do I update zun, from devstack?04:39
pksinghlakerzhou: my conf is at http://paste.openstack.org/show/598334/04:39
mkraicd /opt/stack/zun; git pull04:39
mkraiand then restart zun-api and zun-compute04:40
pksinghlakerzhou: mkrai , i did it today. go to /opt/stack/zun, do 'git pull' and 'python setup.py install'04:40
pksinghmkrai: 'python setup.py install' is necessary because of image_driver bp04:40
mkraiyes but not if we are running it second time or so04:41
*** adisky_ has joined #openstack-zun04:42
*** sudipto has joined #openstack-zun04:42
*** sudipto_ has joined #openstack-zun04:42
pksinghi think you need to install due to https://github.com/openstack/zun/blob/master/setup.cfg#L67, if your previous code dont have this entry04:43
lakerzhouThanks pksingh and mkrai04:43
sudipto_pksingh, hongbin if you guys think this code: https://review.openstack.org/#/c/430920/ is alright, i will move ahead with the other patches.04:44
pksinghlakerzhou: please update pythonzunclient to, i think there you dont need to 'python setup.py install'04:44
pksinghsudipto_: will look in to it in next one hour04:45
hongbin_sudipto_: LGTM04:45
sudipto_hongbin_, ok pksingh sure.04:45
*** hongbin_ has quit IRC04:49
*** yasemin has quit IRC04:57
*** diga has joined #openstack-zun05:01
*** janki has joined #openstack-zun05:07
*** jchhatbar has joined #openstack-zun05:29
*** janki has quit IRC05:30
*** yasemin has joined #openstack-zun05:36
*** trinaths has joined #openstack-zun05:58
*** jchhatbar_ has joined #openstack-zun06:03
*** jchhatbar has quit IRC06:05
*** jchhatbar_ is now known as janki06:18
*** pksingh has quit IRC07:51
*** pcastets has joined #openstack-zun08:09
openstackgerritfeng.shengqin proposed openstack/python-zunclient master: Support the command "zun top"  https://review.openstack.org/42397408:14
openstackgerritSudipta Biswas proposed openstack/zun master: Introduce os-capability parsing  https://review.openstack.org/43092008:33
*** prameswar has joined #openstack-zun08:38
openstackgerritfeng.shengqin proposed openstack/python-zunclient master: Support the command "zun top"  https://review.openstack.org/42397408:59
*** yanyanhu has quit IRC09:08
openstackgerritfeng.shengqin proposed openstack/zun master: Support the command "zun top"  https://review.openstack.org/43219809:21
openstackgerritKevin Zhao proposed openstack/zun master: Add test cases for attach and resize  https://review.openstack.org/43220409:33
*** lakerzhou has quit IRC09:47
openstackgerritNamrata proposed openstack/python-zunclient master: Add more container related test  https://review.openstack.org/43222110:06
openstackgerritNamrata proposed openstack/python-zunclient master: Add OSC commands functional test  https://review.openstack.org/43222210:06
*** kevinz has quit IRC10:10
*** openstackgerrit has quit IRC10:18
*** zhangjl has quit IRC10:21
*** jchhatbar has joined #openstack-zun10:59
*** janki has quit IRC11:01
*** trinaths has quit IRC11:23
*** jchhatbar_ has joined #openstack-zun11:26
*** jchhatbar has quit IRC11:28
*** diga has quit IRC11:31
*** jchhatbar has joined #openstack-zun11:47
*** jchhatbar is now known as janki11:48
*** jchhatbar_ has quit IRC11:50
*** sudipto has quit IRC12:09
*** sudipto_ has quit IRC12:09
*** janki has quit IRC12:19
*** adisky_ has quit IRC14:09
*** sudipto has joined #openstack-zun14:10
*** sudipto_ has joined #openstack-zun14:10
*** sudipto_ has quit IRC15:08
*** sudipto has quit IRC15:08
*** dims_ has quit IRC15:28
*** dims has joined #openstack-zun15:33
*** dims has quit IRC15:55
*** dims has joined #openstack-zun15:55
*** dims is now known as Guest1240615:56
*** prameswar has quit IRC16:00
*** jwcroppe has joined #openstack-zun16:01
*** Guest12406 has quit IRC16:05
*** dims_ has joined #openstack-zun16:24
*** sudipto_ has joined #openstack-zun16:29
*** sudipto has joined #openstack-zun16:29
*** harlowja has joined #openstack-zun17:05
*** harlowja has quit IRC17:05
*** harlowja has joined #openstack-zun17:05
*** openstackgerrit has joined #openstack-zun17:12
openstackgerritMerged openstack/zun master: Introduce os-capability parsing  https://review.openstack.org/43092017:12
sudipto_hongbin, mkrai thanks for the reviews. I will get some code written over the weekend for the generic host_capabilities methods. Also maybe will start drafting the resource provider objects.17:37
sudipto_hongbin, if you could do the schema design, that would be awesome...whenever you find sometime.17:38
*** pcastets has quit IRC17:47
*** sudipto has quit IRC18:16
*** sudipto_ has quit IRC18:16
openstackgerritMerged openstack/zun master: Updated from global requirements  https://review.openstack.org/43191318:35
openstackgerritHongbin Lu proposed openstack/zun master: Spec for Kuryr integration  https://review.openstack.org/42588322:21
*** catintheroof has quit IRC23:03
*** catintheroof has joined #openstack-zun23:04
*** catintheroof has quit IRC23:08
*** jwcroppe has quit IRC23:34
*** jwcroppe has joined #openstack-zun23:35
*** jwcroppe has quit IRC23:39

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!