Friday, 2015-04-17

*** petertr7 has quit IRC00:01
*** mahito has joined #openstack-containers00:01
*** mahito_ has joined #openstack-containers00:04
*** rongze has joined #openstack-containers00:04
*** dims__ has joined #openstack-containers00:04
*** mahito has quit IRC00:05
*** dims_ has joined #openstack-containers00:05
*** rongze has quit IRC00:05
*** rongze has joined #openstack-containers00:06
*** dims__ has quit IRC00:09
*** rongze has quit IRC00:11
*** rongze has joined #openstack-containers00:11
*** rongze has quit IRC00:17
*** sdake has joined #openstack-containers00:20
*** sdake_ has quit IRC00:24
*** MilesDenver has quit IRC00:34
*** Tango has quit IRC00:35
*** Marga_ has joined #openstack-containers00:36
*** kebray_ has quit IRC00:38
*** Marga_ has quit IRC00:41
*** achanda has quit IRC00:51
*** achanda has joined #openstack-containers00:59
*** yuanying-alt has joined #openstack-containers01:12
*** yuanying-alt has quit IRC01:16
*** adrian_otto has joined #openstack-containers01:16
*** rongze has joined #openstack-containers01:26
*** rongze has quit IRC01:30
*** Marga_ has joined #openstack-containers01:37
*** Marga_ has quit IRC01:42
*** adrian_otto has quit IRC01:42
*** erkules has joined #openstack-containers01:43
*** erkules_ has quit IRC01:46
*** harlowja is now known as harlowja_away01:47
*** fangfenghua has joined #openstack-containers01:48
openstackgerritDavanum Srinivas (dims) proposed openstack/magnum: [WIP][NOT READY FOR REVIEW] Functional tests for listing resources and templates  https://review.openstack.org/17353701:50
*** Marga_ has joined #openstack-containers01:53
*** dims_ has quit IRC01:54
openstackgerritJennifer Carlucci proposed openstack/magnum: Add timeout parameter to bay create  https://review.openstack.org/17406101:55
*** Marga_ has quit IRC02:15
*** achanda has quit IRC02:20
openstackgerritMerged openstack/python-magnumclient: Add swarm_token to bay-create call.  https://review.openstack.org/17411602:20
*** achanda has joined #openstack-containers02:22
*** fangfenghua has quit IRC02:30
*** liusheng has joined #openstack-containers02:46
Fang_fenghuaVilobh Meshram?02:48
Fang_fenghuaxx02:48
*** achanda has quit IRC02:49
*** unicell has quit IRC02:54
*** yuanying-alt has joined #openstack-containers03:01
*** yuanying-alt has quit IRC03:05
*** liusheng has quit IRC03:07
*** liusheng has joined #openstack-containers03:07
*** achanda has joined #openstack-containers03:20
*** sdake_ has joined #openstack-containers03:34
*** sdake has quit IRC03:38
*** kebray has joined #openstack-containers03:41
*** kebray has quit IRC03:41
*** kebray has joined #openstack-containers03:46
*** achanda has quit IRC03:52
*** achanda has joined #openstack-containers04:07
*** achanda has quit IRC04:11
*** achanda has joined #openstack-containers04:16
*** achanda has quit IRC04:18
*** achanda has joined #openstack-containers04:21
*** Tango has joined #openstack-containers04:25
*** achanda has quit IRC04:29
*** achanda has joined #openstack-containers04:42
*** yuanying-alt has joined #openstack-containers04:49
*** yuanying-alt has quit IRC04:54
*** openstackgerrit has quit IRC05:21
*** openstackgerrit has joined #openstack-containers05:21
*** oro has joined #openstack-containers05:50
digayuanying: Hi05:54
digagot the issue related testcase failing05:54
*** ashishjain has joined #openstack-containers05:58
ashishjainHello05:58
ashishjainI am really really excited about magnum project :)05:58
openstackgerritMerged openstack/python-magnumclient: Support update a service  https://review.openstack.org/17387406:03
openstackgerritMerged openstack/python-magnumclient: Support update a replication controller  https://review.openstack.org/17388306:04
ashishjainIs there any end user specific documentation available?06:12
ashishjainI only see dev docs06:12
*** Tango has quit IRC06:13
*** oro has quit IRC06:14
sdake_ashishishjain no06:15
sdake_docs will bea major focus for liberty06:16
*** oro has joined #openstack-containers06:16
Fang_fenghuasdake_:Before we create pod should we check the bay is ready?06:17
Fang_fenghuahttps://bugs.launchpad.net/magnum/+bug/144531906:17
openstackLaunchpad bug 1445319 in Magnum "Didn't check bay status beforce create pod" [Undecided,New] - Assigned to FenghuaFang (449171342-q)06:17
Fang_fenghuaI think we should check the bay status before we create pod on it06:18
sdake_check for create_complete yes06:18
Fang_fenghuaOK, I will commit a patch for it06:18
sdake_boy its really hard developing two projects at the same time06:19
Fang_fenghua?06:19
sdake_fang I ptl kolla06:20
sdake_and core on magnum06:20
sdake_15 hour days ftl06:20
Fang_fenghuaI hope i can do much more work here06:21
Fang_fenghuaAlso our team  will work on kolla06:21
Fang_fenghuasdake06:21
sdake_cool06:21
sdake_which team is that06:21
*** oro has quit IRC06:22
Fang_fenghuaNow just i had file some bug on kolla06:22
Fang_fenghuaOther people get ready contribute code06:23
lan_Able men are always busy :)06:24
lan_Fang_fenghua,  I think the bay status should be in "update_complete" or "create_complete" when we create a pod on it..06:24
Fang_fenghuaYes06:25
Fang_fenghuaI had realize it, tks lan06:25
lan_np :)06:27
lan_Fang_fenghua,  for the container create fail issue : https://bugs.launchpad.net/magnum/+bug/144255606:28
openstackLaunchpad bug 1442556 in Magnum "Create container fail" [Critical,Triaged] - Assigned to FenghuaFang (449171342-q)06:28
Fang_fenghua?06:28
lan_Fang_fenghua,  I think it's more like a permission problem.06:28
Fang_fenghuaYes, the perimission problem is easy fix06:29
Fang_fenghuaBut the bug mean we can crate a container out of a bay06:30
Fang_fenghuaI think it's very serious06:30
lan_Yes, the default url for container is "unix:///var/run/docker.sock", I am not sure is it need "root" user to access it?06:32
Fang_fenghuaLan_ Do you think?06:32
Fang_fenghuaFor permission error we can chown of "unix:///var/run/docker.sock" to fix it06:33
digasdake_: Hi06:34
sdake_sifQOUNS MW06:34
digaI think its too late at your location06:34
sdake_wound me that is :)06:35
digabut need someone to help me on this06:35
sdake_feng the bug is already in criticla mode06:35
digaI have added some code in baymodel_create - https://review.openstack.org/#/c/172348/3/magnum/api/controllers/v1/baymodel.py06:35
Fang_fenghuaI konw06:35
sdake_we have 3 weeks to finish our bugs ;)06:36
sdake_better get cracking guys06:36
digabut here are some test cases - https://review.openstack.org/#/c/172348/3/magnum/tests/unit/api/controllers/v1/test_baymodel.py06:36
digaI am solving issues related to this06:37
digado you knwo someone who can help me on the test cases ?06:38
*** yuanying-alt has joined #openstack-containers06:38
sdake_not me sorry :) I am a test case noob06:39
diga:)06:40
*** nshaikh has joined #openstack-containers06:41
*** Kennan2 has quit IRC06:41
*** Kennan has joined #openstack-containers06:42
*** yuanying-alt has quit IRC06:42
lan_Fang_fenghua,  seems like we don't specify the "command" when creating a container.  it the "command" parameter necessary ?06:44
lan_Fang_fenghua,  the error message: Docker API Error : 500 Server Error: Internal Server Error ("No command specified")06:45
Fang_fenghualan_ You mean bug 144256?06:50
openstackbug 144256 in scala (Ubuntu) "upgrade to 2.6.0" [Wishlist,Invalid] https://launchpad.net/bugs/14425606:50
lan_Fang_fenghua,  yes  144255606:51
*** achanda has quit IRC06:53
Fang_fenghualan_ I didn't specify command,but thats not reason i got the error06:54
*** achanda has joined #openstack-containers06:56
sdake_madhuri are you about06:57
madhurisdake_, Hi06:57
sdake_madhuri http://www.projectatomic.io/download/07:01
*** madhuri____ has joined #openstack-containers07:04
*** sdake has joined #openstack-containers07:06
sdakemadhuri fedora 21 only has kubernetes 0.1307:07
madhuri____Yes and v1beta3 is supported in 0.1507:07
sdakewe have to wait until atomic has 0.1507:08
madhuri____Then how would python-k8sclient will go?07:08
sdakesend an email to the project atomic ml07:09
sdakeand ask them when they will have 0.15 k8s07:09
*** sdake_ has quit IRC07:09
sdakeuntil then we will have to stick with 0.11 or we could switch now to 0.1307:09
madhuri____mmm it seems to be a problem07:10
sdakesend email to atomic ml and ask them when07:10
sdakeand we can sort out the details based upon their data07:10
madhuri____Ok I will07:10
madhuri____I am trying to create an image with Kubernetes 0.15 to test my patch07:11
Fang_fenghuaCan we just update k8s version with http://www.projectatomic.io/download/07:12
sdakedownload link only had 0.1307:14
sdakeafter you do an sudo rpm-ostree upgrade07:14
sdakehttp://koji.fedoraproject.org/koji/buildinfo?buildID=62856407:14
sdakeatomic /usr is readonly07:15
sdakeso good luck upgrading ;)07:15
openstackgerritDigambar proposed openstack/magnum: mplemention of Cluster type for baymodel.  https://review.openstack.org/17234807:15
Fang_fenghua:)07:16
ashishjainsdake: Please provide a starting point atleast. How shall I go about start using it07:17
sdakeread the dev quickstart07:18
sdakeit shows how to bring up a full magnum system in devstack or manually alongside devstack07:18
sdakeand how to create baymodels, bays, pods, etc07:18
ashishjainsdake: thanks for this.07:19
ashishjainsdake: Is it absolutely necessary to use kubernetes while using magnum07:19
ashishjainSdake: is it not possible to just use the autoscaling feature of heat07:19
sdakeno you could theoretically use the docker implementation07:19
sdakebut it doesn't work atm07:19
sdakesee 155 long buglist for magnum ;-)07:20
ashishjainsdake: I have been experimenting with docker for quite sometime now. As I understand there are 3 ways currently available to run docker containers07:20
ashishjain1) Use docker driver - you can deploy docker but cannot autoscale 2) User heat docker resource  -yet to try 3) Magnum (CAAS)07:21
sdakeour docker-py calls local docker, rather then the bay docker07:21
sdakethis is a critical bug07:21
sdakethat needs to be fixed07:21
sdakefor scale-out, apmelton is working on swarm support07:22
sdakebut it won't likely make kilo07:22
sdakeso there is a fourth way ;-)07:22
ashishjain:)07:22
sdakeheat also has a compose resource07:22
sdakeso there is a 5th way07:22
ashishjain;(07:22
ashishjainsdake: Currently is it possible to autoscale docker say on cpu_util using any of these 5 ways :)07:23
sdakewe support node count update07:23
sdakebut not automatically07:23
sdakeits manual07:23
sdakeand only goes larger not smaller07:24
ashishjainwe in the sense "magnum"07:24
sdakeand only for kubernetes07:24
sdakeright the magnum code base07:24
sdakesorry my language is imperfect i've been awake for 24 hours07:24
ashishjainoh my07:24
sdakei'll give you 5 more minutes then need to ptfo :)07:24
ashishjain:)..ya let me be very quick that07:24
ashishjainthan*07:25
sdakeits 00:25 hours here07:25
ashishjainso autoscaling(just scale out)  of docker is currently not supported by  any of these 5 modes07:25
Fang_fenghuasdaje Go to bed07:25
Fang_fenghuasdake07:26
sdakeif you use kubernetes to abstract doocker, you get manual scalout07:26
ashishjainokay sdake thanks .... have a a good sleep07:26
sdakehit me up in the morning07:26
sdakei'll spend more time explaining things to you07:26
ashishjainsdake: sure thanks a lot for your generosity07:27
ashishjain:)07:27
sdakeI have about 2000 hours on container tech, so I feel like I've just hit about intermediate skill level07:27
openstackgerritDigambar proposed openstack/magnum: Implemention of Cluster type for baymodel.  https://review.openstack.org/17234807:27
ashishjaincool07:28
sdakebut I dont htink magnum would look all that much different based upon my current experience07:28
sdakeI probably would have chewed off less work tho ;)07:28
sdakenight07:28
*** achanda has quit IRC07:29
*** achanda_ has joined #openstack-containers07:32
*** dims__ has joined #openstack-containers07:33
*** kebray has quit IRC07:36
*** dims__ has quit IRC07:38
*** achanda_ has quit IRC07:40
openstackgerritGrzegorz Grasza (xek) proposed openstack/magnum: Start the conversion to oslo.versionedobjects  https://review.openstack.org/17436607:45
openstackgerritGrzegorz Grasza (xek) proposed openstack/magnum: Move our ObjectListBase to subclass from the Oslo one  https://review.openstack.org/17438607:45
*** mahito has joined #openstack-containers07:46
*** mahito_ has quit IRC07:49
*** erkules has quit IRC07:53
*** erkules has joined #openstack-containers07:53
Fang_fenghua vilobhmm?08:01
*** ashishjain has quit IRC08:03
*** achanda has joined #openstack-containers08:06
digayuanying: Hi08:15
*** ashishjain has joined #openstack-containers08:17
*** unicell has joined #openstack-containers08:19
*** achanda has quit IRC08:20
*** achanda_ has joined #openstack-containers08:22
*** yuanying-alt has joined #openstack-containers08:27
*** sdake has quit IRC08:28
*** yuanying-alt has quit IRC08:32
*** achanda_ has quit IRC08:35
openstackgerritFang Fenghua proposed openstack/python-magnumclient: Add status bay status check when pod create.  https://review.openstack.org/17475908:36
openstackgerritFang Fenghua proposed openstack/python-magnumclient: Add bay status check when pod create.  https://review.openstack.org/17475908:36
*** mahito has quit IRC08:37
Fang_fenghuayuanying?08:41
Fang_fenghuaYuanying?08:42
openstackgerritCedric Brandily proposed openstack/python-magnumclient: Add unittests for magnumclient.v1.client module  https://review.openstack.org/17376108:48
openstackgerritCedric Brandily proposed openstack/python-magnumclient: Remove side effect in get_keystoneclient  https://review.openstack.org/17376408:49
openstackgerritCedric Brandily proposed openstack/python-magnumclient: Delegate magnum url search to url_for method  https://review.openstack.org/17129708:49
*** madhuri____ has quit IRC09:08
*** rongze has joined #openstack-containers09:11
*** rongze has quit IRC09:15
*** rongze has joined #openstack-containers09:15
*** rongze_ has joined #openstack-containers09:26
*** rongze has quit IRC09:26
*** rongze_ has quit IRC09:28
*** rongze has joined #openstack-containers09:28
*** rongze has quit IRC09:29
*** Fang_fenghua has quit IRC10:06
*** yuanying-alt has joined #openstack-containers10:16
*** yuanying-alt has quit IRC10:20
*** diga has quit IRC10:24
*** diga has joined #openstack-containers10:41
*** yuanying has quit IRC10:43
madhuriHi, can anyone tell me when is stack.timeout_mins is None?10:48
madhuriAnd what is the stack state when stack time out expires?10:49
*** dims__ has joined #openstack-containers11:02
*** Marga_ has joined #openstack-containers11:03
*** Marga_ has quit IRC11:03
*** Marga_ has joined #openstack-containers11:04
openstackgerritDavanum Srinivas (dims) proposed openstack/magnum: [WIP][NOT READY FOR REVIEW] Functional tests for listing resources and templates  https://review.openstack.org/17353711:10
openstackgerritMerged openstack/python-magnumclient: Correct mock use in TestCommandLineArgument.setUp  https://review.openstack.org/17459111:20
*** Fang_fenghua has joined #openstack-containers11:21
*** prad has quit IRC11:36
*** ashishjain has quit IRC11:36
openstackgerritFang Fenghua proposed openstack/python-magnumclient: Add bay status check when service create.  https://review.openstack.org/17483111:45
*** julim has joined #openstack-containers11:46
*** prad has joined #openstack-containers11:51
*** prad has quit IRC11:54
openstackgerritFang Fenghua proposed openstack/python-magnumclient: Add bay status check when service create.  https://review.openstack.org/17483111:54
openstackgerritLan Qi Song proposed openstack/magnum: Add command field for container  https://review.openstack.org/17483912:03
*** yuanying-alt has joined #openstack-containers12:04
*** yuanying-alt has quit IRC12:09
Fang_fenghuaCommit got gate-python-magnumclient-docs12:11
Fang_fenghuaFail12:11
openstackgerritLan Qi Song proposed openstack/python-magnumclient: Support pass command field when create a container  https://review.openstack.org/17484112:11
Fang_fenghuabut http://logs.openstack.org/31/174831/2/check/gate-python-magnumclient-docs/4e027ba/12:11
Fang_fenghuais empty12:11
openstackgerritDavanum Srinivas (dims) proposed openstack/magnum: [WIP][NOT READY FOR REVIEW] Functional tests for listing resources and templates  https://review.openstack.org/17353712:14
*** jjlehr has joined #openstack-containers12:16
*** jjlehr has quit IRC12:18
*** rpothier has joined #openstack-containers12:29
*** jjlehr has joined #openstack-containers12:41
*** ashishjain has joined #openstack-containers12:45
*** jjlehr has quit IRC12:47
openstackgerritFang Fenghua proposed openstack/python-magnumclient: Add bay status check when rc create.  https://review.openstack.org/17485512:50
*** Fang_fenghua has quit IRC12:51
*** Fangfenghua has joined #openstack-containers13:16
FangfenghuaLan_13:18
Fangfenghua?13:18
Fangfenghualan_ here?13:18
*** jjlehr has joined #openstack-containers13:23
*** jfarschman has joined #openstack-containers13:29
*** jfarschman is now known as MilesDenver13:29
*** MilesDenver has quit IRC13:29
*** rlrevell has joined #openstack-containers13:30
*** prad has joined #openstack-containers13:35
*** Marga_ has quit IRC13:35
openstackgerritLan Qi Song proposed openstack/magnum: Add command field for container  https://review.openstack.org/17483913:51
openstackgerritLan Qi Song proposed openstack/python-magnumclient: Support pass command field when create a container  https://review.openstack.org/17484113:52
*** yuanying-alt has joined #openstack-containers13:53
dims__ashishjain: can you please explain auto-scaling a bit from the end use point of view? (end user of your system)?13:54
ashishjaindims__:Hi13:54
dims__ashishjain: Is it that the system should be able to add a new VM or baremetal for running Ubuntu/Atomic/Centos with a fresh Docker Daemon and add it to an existing "cluster"? then your user does not care where the docker container is running, just that he/she is able to start a new container as needed?13:55
ashishjaindims__: currently the use case does not require to deploy a new VM with docker daemon on it. But that would be the path in the future.13:56
dims__so what is the current use case?13:56
dims__does end user use Docker Remote API? something else?13:57
ashishjaindims__: currently I am working on a simple use case where I got a Compute with pre-installed docker daemon. Using nova-docker driver and heat autoscaling I deploy a simple docker container13:57
ashishjainand simulate some load.13:57
ashishjaindims__: yes api will be used to automate it.13:58
*** yuanying-alt has quit IRC13:58
dims__heat auto-scaling adds new docker containers?13:58
dims__in the same daemon?13:58
ashishjaindims__: yes you are correct13:58
ashishjaindims__: yes13:58
ashishjaindims__: My compute node has got enough of RAM and CPU to run multiple containers13:59
ashishjaindims__: what I have found out is once I move to docker hypervisor ceilometer does not collect any stats13:59
dims__what triggers do the heat autoscaling look for?13:59
ashishjaindims__: cpu_util14:00
dims__of course, yes, it doesn't14:00
ashishjaindims__: so than autoscaling does not work14:00
ashishjaindims__: and docker-driver just could not be used for a real use case of autoscaling :(14:00
dims__https://blueprints.launchpad.net/ceilometer/+spec/container-monitoring14:00
dims__exactly14:01
dims__ashishjain: so based on cpu you run more of the same exact image? don't know what that gets you14:02
ashishjaindims__: So this may not be available in next few months14:03
ashishjaindims__: the idea is scaling a component/module independently and than plugging it to a load balancer14:03
ashishjainprobably neutron or HA14:03
dims__i mean typically i've seen that if there is a request/reponse time slowing down for a specific application you launch more of that application image with a load balancer in front of it. so your docker deamon may have multiple applications14:04
dims__with multiple images14:04
ashishjaindims__: Yes you are correct14:04
ashishjaindims__: Ultimate goal will be to achieve a micro architecture kind of deployment with openstack and docker.14:04
*** EricGonczer_ has joined #openstack-containers14:05
ashishjainplus definitely load balancer and proxy service as required14:05
ashishjaindims__: do you find it viable and reasonable ?14:05
dims__ashishjain: this is exactly the stuff we are trying to do in Magnum with Nova+Heat+Kubernetes+Flannel etc. (There's a swarm effort in progress as well, instead of kubernetes)14:07
dims__ashishjain: https://blueprints.launchpad.net/magnum/14:07
ashishjaindims__: Ya got to know from container IRC about it today.14:07
ashishjaindims__: thanks for this. But than I am trying to understand where does nova-docker, docker plugin for heat fit  in scheme of things14:09
ashishjaindims__: will those not be used for all these use cases which magnum is solving may be with kubernetes14:11
*** sdake has joined #openstack-containers14:12
FangfenghuaHi sdake14:15
sdakemorning14:15
*** rlrevell has left #openstack-containers14:16
*** rlrevell has joined #openstack-containers14:16
Fangfenghuasdake I didn't got why we not container API.14:16
ashishjainsdake: Good Morning.14:16
sdakefeng me either14:17
*** jfarschman has joined #openstack-containers14:17
*** jfarschman is now known as MilesDenver14:17
sdakemultiple brains designed magnum14:18
Fangfenghua~~14:19
Fangfenghuasdake sorry have typo14:23
Fangfenghua sdake I didn't got why we need  container API.14:24
Fangfenghua:)14:24
sdakeyes me either14:24
sdakeI knew what you meant14:24
sdakemaybe with swarm it will make sense14:24
sdakeapmelton can answer more14:24
sdakebecause swarm is just a thin abstracton over docker14:25
FangfenghuaAutomatic error correction.I think you had a good sleep ;)14:25
apmeltonsdake: Fangfenghua: honestly, it may not be necessary14:27
apmeltonwe could potentially just use pods for swarm14:27
apmeltonsince, if I remember correctly, pods are simple collections of containers14:27
Fangfenghuaright14:28
apmeltonand if someone wants to mess with containers directly, they can do to the swarm api14:28
apmeltonI've gotta run to a meeting though, I'll be back a bit later14:28
sdakeya 7 hours14:30
sdakei'm going to lay in bed for a bit not quite awake14:30
sdakebbi an hour or so14:30
*** Tango has joined #openstack-containers14:30
sdakestill tired14:30
Fangfenghuaapmelton If we just want run container,Why not docker-api directly14:30
apmeltonFangfenghua: because swarm gets us horizontal scaling of capacity14:31
openstackgerritDavanum Srinivas (dims) proposed openstack/magnum: [WIP][NOT READY FOR REVIEW] Functional tests for listing resources and templates  https://review.openstack.org/17353714:31
Fangfenghuaapmelton  I didn't got it14:32
openstackgerritDavanum Srinivas (dims) proposed openstack/magnum: [WIP][NOT READY FOR REVIEW] Functional tests for listing resources and templates  https://review.openstack.org/17353714:32
*** dims__ has quit IRC14:33
Fangfenghuaapmelton We can use docker-pai start container in docker-swam too14:33
*** nshaikh has left #openstack-containers14:34
apmeltonFangfenghua: yes, technically you can swap between a single docker api, and the swarm api without too much trouble14:34
apmeltonthere are a few differences, but for the most part they are interchanagable14:34
apmeltonmeeting is seting now so I gotta drop off14:34
apmeltonstarting*14:35
*** sdake_ has joined #openstack-containers14:47
Fangfenghuasdake I just realize that if we have swarm bay, we need container-api14:49
FangfenghuaWe must use keystone14:49
*** sdake has quit IRC14:50
*** Fangfenghua_ has joined #openstack-containers14:53
*** Fangfenghua has quit IRC14:54
Fangfenghua_My compute going down just now (:14:54
*** yuanying-alt has joined #openstack-containers14:54
*** prad has quit IRC14:57
*** yuanying-alt has quit IRC14:58
*** fangfenghua has joined #openstack-containers14:58
*** prad has joined #openstack-containers15:01
*** Marga_ has joined #openstack-containers15:03
*** dims__ has joined #openstack-containers15:04
*** adrian_otto has joined #openstack-containers15:13
*** dims__ has quit IRC15:22
*** oro has joined #openstack-containers15:23
*** kebray has joined #openstack-containers15:29
*** gose has joined #openstack-containers15:34
*** EricGonczer_ has quit IRC15:38
*** oro has quit IRC15:39
*** EricGonczer_ has joined #openstack-containers15:43
*** PaulCzar has quit IRC15:48
*** ashishjain has quit IRC16:04
*** unicell has quit IRC16:13
*** subscope has joined #openstack-containers16:20
*** dims__ has joined #openstack-containers16:24
*** Fangfenghua_ has quit IRC16:33
*** sdake has joined #openstack-containers16:35
*** sdake_ has quit IRC16:39
*** unicell has joined #openstack-containers16:41
*** unicell has quit IRC16:41
*** unicell has joined #openstack-containers16:42
*** Marga_ has quit IRC16:43
*** yuanying-alt has joined #openstack-containers16:43
*** yuanying-alt has quit IRC16:47
*** Tango has quit IRC16:50
*** dims__ is now known as dimsum__16:50
*** unicell has quit IRC16:57
*** unicell has joined #openstack-containers16:57
*** diga_ has joined #openstack-containers16:57
dimsum__apmelton: why WIP the review? https://review.openstack.org/#/c/174112/16:59
apmeltondimsum__: so it doesn't get merged until I've got every changed up for discovery16:59
dimsum__don't want to merge it and iterate?17:00
apmeltondimsum__: not if it means yet another db migration17:00
dimsum__ah ok17:00
apmeltonI'll have a review up in a bit17:00
*** prad has quit IRC17:02
dimsum__apmelton: any updates from others? jjlehr, diga, joffter17:02
apmeltondimsum__: not yet17:04
*** prad has joined #openstack-containers17:05
diga_dimsum__: I already have started work on 4/5 task17:06
diga_will push the code over the weekend17:06
*** prad has quit IRC17:06
dimsum__thanks diga_17:06
diga_dimsum__: welocome!17:06
apmeltondiga_: if you have any questions over the weekend please use my email17:07
apmeltonI'll be out of town, but will check email periodically17:07
diga_yes apmelton17:07
diga_sure17:07
adrian_ottodiga_: have you asked in IRC for help in resolving the difficulty expressed here http://paste.openstack.org/show/204192/ (for https://review.openstack.org/172348)?17:08
diga_yes17:09
adrian_ottook, and did you find volunteers to assist?17:09
diga_I need help in test case writting for api/test_baymodel17:09
diga_no, not yet17:09
*** prad has joined #openstack-containers17:09
diga_I have asked in the afternoon but nobody is there excluding sdake17:10
adrian_ottoapmelton: any chance you can peek at that and offer diga_ some guidance. I would volunteer myself, but I have to prepare for a presentation coming later today.17:11
diga_s/is/was17:11
apmeltonadrian_otto: sure I'll take a peek17:11
adrian_ottothanks!17:11
apmeltondiga_: do you have the output of the failing tests?17:12
diga_yes17:12
diga_1 min17:12
adrian_ottook, mention my nick if you want my attention back again, I'm going into background mode now17:13
diga_adrian_otto: yes, sure17:13
diga_apmelton: see this - http://logs.openstack.org/48/172348/5/check/gate-magnum-python27/fd231aa/console.html17:13
diga_apmelton: main issue is here - http://paste.openstack.org/show/204192/17:14
*** harlowja_away is now known as harlowja17:17
apmeltondiga_: nothing is really jumping out at me, pulling it down and running the tests locally to poke futher17:25
diga_apmelton: sure17:31
dimsum__diga_: if you comment out the line to call _get_image_data in the baymodel.py post method and hard code baymodel_dict['cluster_type'] to something the test passes. so essentially you need to add a mock for that method17:35
dimsum__diga_: hope that helps17:36
apmeltonthis is that actual exception that's causing issues: http://paste.openstack.org/show/204494/17:37
diga_dimsum__: okay17:37
diga_apmelton: let me go through it17:37
apmeltondiga_: I think what you need to do is mock out the call to clients.glance() and return a mock instead of the actual glance client17:39
diga_apmelton: okay17:40
dimsum__++17:40
apmeltondiga_: here's an example: https://github.com/openstack/magnum/blob/master/magnum/tests/unit/conductor/handlers/test_bay_k8s_heat.py#L47917:41
apmeltonfor heat client17:41
diga_apmelton: yes, got it17:42
*** jjlehr has quit IRC17:42
diga_I need to add  glance client instead17:43
apmeltondiga_: what you may want to do while you're debugging an api function in a test is wrap the api function in a try/except that prints a traceback and reraises the exception17:43
apmeltonotherwise you just get a some what unhelpful exception message17:44
apmeltondiga_: yup17:44
diga_apmelton: yes17:45
*** prad has quit IRC17:45
*** prad has joined #openstack-containers17:46
*** achanda has joined #openstack-containers17:48
diga_apmelton: thanks for your help :)17:49
apmeltondefinitely diga_!17:49
diga_:)17:50
*** Marga_ has joined #openstack-containers17:55
*** rlrevell has left #openstack-containers18:05
*** rlrevell has joined #openstack-containers18:06
*** jjlehr has joined #openstack-containers18:09
*** EricGonc_ has joined #openstack-containers18:14
*** EricGonczer_ has quit IRC18:17
*** diga_ has quit IRC18:18
*** yuanying-alt has joined #openstack-containers18:31
*** yuanying-alt has quit IRC18:36
*** achanda has quit IRC18:46
*** kebray has quit IRC18:49
apmeltonWith out objects, we have lots of fields set as type_or_none, if I do Obj().field_name, for a field_name that is type_or_none, should Obj().field_name be None?18:53
apmeltonwith our objects*18:54
*** achanda has joined #openstack-containers18:56
apmeltonthe problem I'm hitting is that if we don't provide that field_name to an api call, Obj().field_name isn't None, it actually throws an exception18:56
*** kebray has joined #openstack-containers18:59
apmeltonnevermind... I figured out why defaulting was working on baymodel params but not bay params. it's because before bay creation, the baymodel already exists, and is loaded from the database, the bay isn't, so it doesn't have optional params set19:00
*** EricGonc_ has quit IRC19:07
*** EricGonczer_ has joined #openstack-containers19:08
openstackgerritAndrew Melton proposed openstack/magnum: Add Swarm TemplateDefinition  https://review.openstack.org/17411219:11
openstackgerritAndrew Melton proposed openstack/magnum: Add Swarm TemplateDefinition  https://review.openstack.org/17411219:19
openstackgerritAndrew Melton proposed openstack/python-magnumclient: Rename swarm-token to discovery-url  https://review.openstack.org/17501419:21
*** kebray has quit IRC19:34
*** Marga_ has quit IRC19:38
*** subscope has quit IRC19:40
*** achanda has quit IRC19:50
*** funzo has quit IRC19:53
*** jjlehr1 has joined #openstack-containers20:02
*** kebray has joined #openstack-containers20:04
*** jjlehr has quit IRC20:05
*** Marga_ has joined #openstack-containers20:09
*** funzo has joined #openstack-containers20:09
*** Marga_ has quit IRC20:13
*** yuanying-alt has joined #openstack-containers20:20
*** openstackgerrit has quit IRC20:22
*** openstackgerrit has joined #openstack-containers20:22
*** yuanying-alt has quit IRC20:25
*** achanda has joined #openstack-containers20:27
jjlehr1Addind the coe attribute to the BayModel requires making changes to both magnum and python-magnumclient. Does the code for python-magnumclient get linked to the same blueprint as the code for magnum?20:51
*** sdake_ has joined #openstack-containers20:56
*** logan2 has quit IRC20:59
*** sdake has quit IRC20:59
*** logan2 has joined #openstack-containers21:00
-openstackstatus- NOTICE: Gerrit will be unavailable between 22:00 and 23:59 UTC for project renames and a database update.21:04
*** jjlehr1 has quit IRC21:06
*** Marga_ has joined #openstack-containers21:08
openstackgerritMerged openstack/magnum: Implement baylock in conductor for horizontal-scale  https://review.openstack.org/17277321:11
sdake_adrian_otto ping re horizontal scale bp21:12
adrian_otto?21:15
adrian_ottosdake_:  ^^21:15
sdake_sorry wasn't in irc window21:15
sdake_so what else was nede beyon this last patch?21:15
sdake_it looks to me like this last patch lands, and we are good to go21:16
adrian_ottoHonbin's code implements async conductor with baylocks21:16
adrian_ottobut it does not implement sync client21:16
adrian_ottowhat we will need is a python-magnumclient implementation that has a call to create the bay followed by a polling loop to await its result21:17
*** EricGonczer_ has quit IRC21:17
sdake_his latest patch looks synchronous to me21:17
adrian_ottooh, maybe he changed it?21:17
sdake_yes he drastically changed between patch set 4 and 521:18
sdake_patch 4 brought back old nightmares :)21:18
adrian_ottook, I think he was trying to get a naive sync implementation as a first step21:18
sdake_i'll definately test21:18
sdake_I think sync is the way to go21:18
sdake_that is exactly how heat works21:18
adrian_ottoso that at least we could increase the conductor count to get more throughput21:18
adrian_ottobut the conductor would block on a bay operation, right?21:18
sdake_raises an exception21:19
sdake_on the second call to the same bay21:19
adrian_ottook21:19
sdake_(which prints out an error in the client)21:19
adrian_ottothe point where I got concerned was where I realized that the client was not going to get an error if the bay create failed21:20
sdake_that is gone now21:20
adrian_ottoso maybe the more recent patch addresses that using a synchronous approach?21:20
sdake_I will definately test and charactize and update commit log accordingly21:20
adrian_ottook, I think that's a place to start for now21:20
sdake_yup21:20
adrian_ottoand then we can iterate on that to bump up the throughput21:21
sdake_monday21:21
sdake_need to unplug this weekend, my next month is pretty hectic21:21
sdake_how often do we expect bay create operations tho :)21:21
sdake_not very I think21:21
adrian_ottobut at least this way a 2-conductor setup can act on two bays concurrently, right?21:21
sdake_and its not a global lock21:21
sdake_atm, you should be able to create multiple bays with 1 conductor21:21
sdake_but you just can't do two operations on one bay at the same time21:22
adrian_ottono, bay creations will be relatively infrequent for sure21:22
sdake_right so why be concerned about performance there21:22
sdake_more important is that there is no conductor blocking21:22
adrian_ottoideally we'd like a way for the client to block on the second operation, and then proceed when the first completes.21:22
sdake_and the raised exception prevents that21:22
*** openstackgerrit has quit IRC21:23
sdake_i see21:23
adrian_ottowe could do that by enhancing the client, and leaving the conductor code alone.21:23
sdake_so that is "if exception retry" :)21:23
adrian_ottoyes.21:23
*** openstackgerrit has joined #openstack-containers21:23
adrian_ottoup to some sensible limit21:23
sdake_ya that seems like wishlist territory to me for kilo tho21:23
sdake_we have a mountain of bugs to fix21:23
adrian_ottoI'm wrapping up for the afternoon, but will check back in tonight on things21:24
sdake_i wont be working on magnum until monday i suspect21:24
sdake_debugging godawful nova + neutron intreactions in juno21:24
adrian_ottoagreed, I think we have enough to knock out the BP, and just follow up with the wishlist stuff using bug tickets for future21:24
sdake_wfm21:24
adrian_ottook. Enjoy your weekend!21:24
sdake_yar21:24
sdake_you too21:24
adrian_ottotx!21:24
*** adrian_otto has quit IRC21:25
*** sdake has joined #openstack-containers21:25
*** sdake_ has quit IRC21:29
*** rlrevell has quit IRC21:33
*** rlrevell has joined #openstack-containers21:33
*** yuanying-alt has joined #openstack-containers21:36
*** rlrevell has quit IRC21:37
*** yuanying-alt has quit IRC21:41
-openstackstatus- NOTICE: Gerrit is unavailable until 23:59 UTC for project renames and a database update.22:04
-openstackstatus- NOTICE: Gerrit is unavailable until 23:59 UTC for project renames and a database update.22:06
*** ChanServ changes topic to "Gerrit is unavailable until 23:59 UTC for project renames and a database update."22:07
*** sdake_ has joined #openstack-containers22:24
*** sdake has quit IRC22:27
*** daneyon_ has joined #openstack-containers22:28
*** daneyon has quit IRC22:31
*** daneyon has joined #openstack-containers22:32
*** daneyon_ has quit IRC22:32
*** EricGonczer_ has joined #openstack-containers22:35
*** EricGonczer_ has quit IRC22:36
*** EricGonczer_ has joined #openstack-containers22:37
*** EricGonczer_ has quit IRC22:38
*** dboik_ has quit IRC22:41
*** dboik has joined #openstack-containers22:41
*** sdake has joined #openstack-containers22:46
*** sdake_ has quit IRC22:50
*** kebray has quit IRC22:50
*** PaulCzar has joined #openstack-containers22:51
*** EricGonczer_ has joined #openstack-containers22:54
*** achanda has quit IRC22:54
*** vilobhmm1 has joined #openstack-containers22:54
vilobhmm1does this bug still makes sense since now we are part of openstack namespace https://bugs.launchpad.net/magnum/+bug/1419766 ?22:55
openstackLaunchpad bug 1419766 in Magnum "Magnum is already taken by someone else in pypi" [Wishlist,Triaged]22:55
*** achanda has joined #openstack-containers22:56
vilobhmm1sdake, aotto, dimsum_ : ^^22:56
* sdake groans22:57
sdakeno idea22:57
sdakecan you ask on #openstack-infra, they will know what to do22:57
sdakeand add details to the bug log22:57
vilobhmm1i did22:57
sdakeand they said?22:57
vilobhmm1already *details to the log*22:57
vilobhmm1will check with infra guys22:57
vilobhmm1now22:57
sdakeok just read the bug detials22:58
*** MilesDenver has quit IRC23:01
*** dboik has quit IRC23:02
*** rpothier has quit IRC23:03
*** ChanServ changes topic to "OpenStack Containers Team"23:04
-openstackstatus- NOTICE: Gerrit is available again.23:04
vilobhmm1sdake : not sure what is the conclusion in #infra channel23:05
sdakewe need to reach out to the develoepr and ask him if he would give up the project name23:07
sdakehe last uploadedi n 201223:07
sdakesounds like a job for Adrian Otto :)23:08
sdakeits an 805 byte file23:09
sdakeI suspect he probably has abanoded the work23:10
sdakethe more painful approach is a rename23:10
*** achanda has quit IRC23:11
*** sdake_ has joined #openstack-containers23:14
*** funzo has quit IRC23:15
*** achanda has joined #openstack-containers23:15
*** sdake has quit IRC23:17
*** yuanying-alt has joined #openstack-containers23:25
*** yuanying-alt has quit IRC23:29
*** dboik has joined #openstack-containers23:29
*** sdake has joined #openstack-containers23:32
*** sdake_ has quit IRC23:36
*** gose has quit IRC23:49
*** Marga_ has quit IRC23:50
*** dboik has quit IRC23:57

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