Monday, 2017-10-09

*** tongl has joined #openstack-lbaas00:50
*** sanfern has quit IRC01:40
kongrm_work: no, i didn't make any changes for now01:44
kongrm_work, the lb operating_status (without any listeners configured) will be changed to ONLINE by health_manager01:45
kongbut we could remove that assertion01:46
openstackgerritLingxian Kong proposed openstack/octavia-tempest-plugin master: Create scenario tests for loadbalancers  https://review.openstack.org/48677501:50
kongrm_work: i submitted a new pachchset to remove that line01:50
*** yamamoto has joined #openstack-lbaas01:51
openstackgerritWei Li proposed openstack/octavia master: change db relationship to manytomany for lb and amphora  https://review.openstack.org/50806001:56
*** yamamoto has quit IRC02:05
*** tongl has quit IRC02:20
*** yamamoto has joined #openstack-lbaas02:24
*** yamamoto has quit IRC02:30
*** atoth has quit IRC02:32
*** leitan has quit IRC02:38
*** yamamoto has joined #openstack-lbaas02:41
*** sshank has joined #openstack-lbaas03:09
*** yamamoto has quit IRC03:18
*** yamamoto has joined #openstack-lbaas03:31
*** yamamoto has quit IRC03:42
*** yamamoto has joined #openstack-lbaas03:47
*** links has joined #openstack-lbaas03:50
*** yamamoto has quit IRC03:51
*** yamamoto has joined #openstack-lbaas04:00
*** sanfern has joined #openstack-lbaas04:20
*** avtar_ has joined #openstack-lbaas04:36
*** eezhova has joined #openstack-lbaas04:40
*** krypto has joined #openstack-lbaas04:50
*** krypto has quit IRC04:50
*** krypto has joined #openstack-lbaas04:50
*** yamamoto has quit IRC05:02
*** yamamoto has joined #openstack-lbaas05:03
*** yamamoto has quit IRC05:08
*** eezhova has quit IRC05:19
*** yamamoto has joined #openstack-lbaas05:39
openstackgerritTong Liu proposed openstack/octavia master: L7 policy API-REF update for result codes  https://review.openstack.org/50857505:39
*** yamamoto has quit IRC05:41
*** gcheresh_ has joined #openstack-lbaas05:41
*** yamamoto has joined #openstack-lbaas05:45
*** yamamoto has quit IRC05:48
*** gcheresh_ has quit IRC05:48
*** spectr has joined #openstack-lbaas05:54
*** gcheresh_ has joined #openstack-lbaas06:02
rm_workkong: i'm not sure if that's right? I thought we would leave it OFFLINE until it actually had members06:04
rm_worki'll look at the code more closely on Monday06:04
*** cody-somerville has joined #openstack-lbaas06:05
*** cody-somerville has joined #openstack-lbaas06:05
rm_workin practice it looked like it was staying in OFFLINE forever (in devstack) since it wouldn't move on to create a listener or pool or etc06:05
*** gcheresh_ has quit IRC06:21
*** cody-somerville has quit IRC06:28
*** cody-somerville has joined #openstack-lbaas06:28
*** cody-somerville has quit IRC06:28
*** cody-somerville has joined #openstack-lbaas06:28
*** rcernin has joined #openstack-lbaas06:40
*** yamamoto has joined #openstack-lbaas06:49
*** krypto has quit IRC06:55
*** krypto has joined #openstack-lbaas06:55
*** yamamoto has quit IRC06:58
*** krypto has quit IRC07:07
*** pcaruana has joined #openstack-lbaas07:08
*** krypto has joined #openstack-lbaas07:08
*** krypto has quit IRC07:08
*** krypto has joined #openstack-lbaas07:08
*** krypto has quit IRC07:15
*** krypto has joined #openstack-lbaas07:17
*** krypto has quit IRC07:58
*** krypto has joined #openstack-lbaas07:58
*** ianychoi has joined #openstack-lbaas07:59
openstackgerritOpenStack Proposal Bot proposed openstack/neutron-lbaas-dashboard master: Imported Translations from Zanata  https://review.openstack.org/50955508:17
*** eezhova has joined #openstack-lbaas08:20
*** krypto has quit IRC08:24
*** krypto has joined #openstack-lbaas08:25
*** krypto has quit IRC08:25
*** krypto has joined #openstack-lbaas08:25
*** ianychoi has quit IRC08:26
*** sanfern has quit IRC08:27
*** krypto has quit IRC08:35
*** krypto has joined #openstack-lbaas08:35
*** sanfern has joined #openstack-lbaas08:36
openstackgerritOpenStack Proposal Bot proposed openstack/octavia-dashboard master: Imported Translations from Zanata  https://review.openstack.org/51033508:38
*** slaweq_ has joined #openstack-lbaas08:48
*** salmankhan has joined #openstack-lbaas08:51
*** salmankhan has quit IRC08:55
*** salmankhan has joined #openstack-lbaas08:57
*** salmankhan has quit IRC09:05
*** salmankhan has joined #openstack-lbaas09:15
*** krypto has quit IRC09:26
*** krypto has joined #openstack-lbaas09:26
*** yamamoto has joined #openstack-lbaas09:29
*** krypto has quit IRC09:34
*** krypto has joined #openstack-lbaas09:34
*** krypto has quit IRC09:34
*** krypto has joined #openstack-lbaas09:34
kongrm_work: in my devstack environment, the lb (without any listeners/members) will be online after creation09:43
*** sanfern has quit IRC09:48
rm_workweird09:50
rm_worki'll try again in the morning09:50
rm_workbut, it did need to be removed anyway, because it really does have nothing to do with waiting on config09:50
rm_work* waiting to send more config09:50
rm_workthough it might be useful for a *traffic* test, before actually starting to send traffic -- i am going to see if that solves my problem with waiting for actual traffic readiness in the failover stuff i was working on09:51
*** eezhova has quit IRC09:52
*** sanfern has joined #openstack-lbaas09:58
kongrm_work: yeah, i already removed that assertion09:59
*** gcheresh_ has joined #openstack-lbaas10:11
*** eezhova has joined #openstack-lbaas10:29
*** eezhova_ has joined #openstack-lbaas10:34
*** eezhova has quit IRC10:36
*** gcheresh_ has quit IRC10:48
*** sanfern has quit IRC10:53
*** yamamoto has quit IRC11:03
*** yamamoto has joined #openstack-lbaas11:34
*** yamamoto has quit IRC11:39
*** gcheresh_ has joined #openstack-lbaas11:42
*** leyal has quit IRC11:47
*** leyal has joined #openstack-lbaas11:49
*** gcheresh_ has quit IRC12:05
*** leyal has quit IRC12:11
*** leyal has joined #openstack-lbaas12:11
*** yamamoto has joined #openstack-lbaas12:23
*** leitan has joined #openstack-lbaas12:37
*** chlong has quit IRC12:37
*** catintheroof has joined #openstack-lbaas12:43
*** sanfern has joined #openstack-lbaas12:45
*** sanfern has quit IRC12:57
*** KeithMnemonic has joined #openstack-lbaas13:39
openstackgerritChenghui Yu proposed openstack/neutron-lbaas master: Fix usage of method ensure_dir  https://review.openstack.org/50293213:44
slaweq_johnsom: hello, can You take a look at https://review.openstack.org/#/c/509708/ ?13:48
slaweq_thx in advance13:48
*** krypto has quit IRC13:52
*** krypto has joined #openstack-lbaas13:53
*** links has quit IRC14:03
*** eezhova_ has quit IRC14:03
*** sanfern has joined #openstack-lbaas14:06
*** chlong has joined #openstack-lbaas14:08
*** chlong_ has joined #openstack-lbaas14:21
*** spectr has quit IRC14:30
*** jniesz has joined #openstack-lbaas14:55
*** links has joined #openstack-lbaas14:56
*** eezhova has joined #openstack-lbaas14:59
*** krypto has quit IRC15:14
*** chlong has quit IRC15:22
*** chlong_ has quit IRC15:22
*** eezhova has quit IRC15:29
*** eezhova has joined #openstack-lbaas15:38
*** krypto has joined #openstack-lbaas15:43
*** krypto has quit IRC15:43
*** krypto has joined #openstack-lbaas15:43
*** catintheroof has quit IRC15:48
*** eezhova has quit IRC15:52
*** Alex_Staf_ has joined #openstack-lbaas15:56
*** Alex_Staf has quit IRC15:57
*** armax has joined #openstack-lbaas16:02
*** chlong_ has joined #openstack-lbaas16:16
*** chlong has joined #openstack-lbaas16:16
*** avtar_ has quit IRC16:30
*** krypto has quit IRC16:30
*** krypto has joined #openstack-lbaas16:31
*** krypto has quit IRC16:31
*** krypto has joined #openstack-lbaas16:31
*** pcaruana has quit IRC16:32
*** sshank has joined #openstack-lbaas16:39
*** sshank has quit IRC16:42
*** rcernin has quit IRC16:49
*** sshank has joined #openstack-lbaas16:51
*** csomerville has joined #openstack-lbaas16:53
*** cody-somerville has quit IRC16:56
*** JudeC has joined #openstack-lbaas16:57
*** links has quit IRC16:58
*** harlowja has joined #openstack-lbaas17:01
*** tongl has joined #openstack-lbaas17:30
*** salmankhan has quit IRC17:37
openstackgerritMerged openstack/octavia master: L7 policy API-REF update for result codes  https://review.openstack.org/50857517:43
*** eezhova has joined #openstack-lbaas17:57
*** leitan has quit IRC18:02
*** leitan has joined #openstack-lbaas18:02
*** krypto has quit IRC18:05
*** leitan has quit IRC18:07
*** pcaruana has joined #openstack-lbaas18:11
*** eezhova has quit IRC18:15
*** gcheresh_ has joined #openstack-lbaas18:27
*** leitan has joined #openstack-lbaas18:31
*** eezhova has joined #openstack-lbaas18:43
*** eezhova has quit IRC18:52
*** gcheresh_ has quit IRC19:07
*** sshank has quit IRC19:19
*** aojea has joined #openstack-lbaas19:25
KeithMnemonicxgerman , johnsonm do either of you know if there are or were any limitations in creating pools in parallel for a given LB19:29
*** csomerville has quit IRC19:29
*** cody-somerville has joined #openstack-lbaas19:30
*** cody-somerville has quit IRC19:30
*** cody-somerville has joined #openstack-lbaas19:30
nmagneziKeithMnemonic, IIRC, creating a pool in a given loadbalancer will move that loadbalancer to PENDING_UPDATE state until it's done creating it. So generally speaking, as long as your loadbalancer is on PENDING_UPDATE you cannot modify it19:33
KeithMnemonicthat is what they are seeing ;-)19:34
KeithMnemonicIf two pools are created in parallel, one request receives "Invalid state PENDING_UPDATE of loadbalancer resource xzy".19:34
KeithMnemonicthanks nmagnezi19:35
nmagneziKeithMnemonic, so that behavior is expected :)19:35
nmagnezinp KeithMnemonic19:35
*** sshank has joined #openstack-lbaas19:41
*** sshank has quit IRC19:44
johnsomYeah, they will get a 409 HTTP status code.19:45
rm_worktwo of any object, yeah19:47
rm_workliterally exactly one change to a LB at a time is permitted19:47
*** sshank has joined #openstack-lbaas20:05
*** sshank has quit IRC20:10
*** sshank has joined #openstack-lbaas20:15
*** pcaruana has quit IRC20:18
*** armax has quit IRC20:26
*** armax has joined #openstack-lbaas21:21
*** leitan has quit IRC21:28
*** leitan has joined #openstack-lbaas21:28
*** sshank has quit IRC21:31
*** sshank has joined #openstack-lbaas21:31
*** leitan has quit IRC21:32
johnsomOk, e-mail sent out about the new meeting time and place (this channel at 20:00 UTC Wednesday).21:37
xgerman_+121:39
*** aojea has quit IRC21:42
*** chlong_ has quit IRC21:59
*** chlong has quit IRC21:59
*** sshank has quit IRC22:29
*** sshank has joined #openstack-lbaas22:39
openstackgerritAdam Harwell proposed openstack/octavia master: Add availability_zone to the amphora record  https://review.openstack.org/51022522:47
*** catintheroof has joined #openstack-lbaas22:47
*** jniesz has quit IRC22:50
kongjohnsom: do you think it makes sense that contain the amphora role in vms name? e.g. 'amphora-<amphora-id>-master'22:56
kongcurrently, the only way to figure out the amphora role is to query the database22:57
kongour operators want to get that information directly from the cli22:57
kongand also the lb id22:58
kongor may store such information in vm metadata?22:59
johnsomkong Not really.  Note that the amphora change roles autonomously, so we don't know who is the current master at any one time.  The database record is for how we configure those VMs, not the current state of the amphora22:59
konghmm...yeah23:00
johnsomIt's part of our layers of high availability.  They can failover without the control plane running if they need to.23:01
johnsomUnfortunately keepalived doesn't give us an easy way to query it either to see what it's current state is.23:02
johnsomWe were talking about that with one of the developers at the PTG in Denver.23:02
kongjohnsom: so there is no direct way to know who is master?23:02
kongeven from inside the amphora?23:02
johnsomNo reliable way.  You can try to parse the syslog,  you could send it a signal and parse a text file (can't remember if that worked or not), or you could try to use the notify scripts to write out a status file.  But otherwise there isn't a way to know.23:04
kongi thought it was done by health_manager...23:04
johnsomHealth manager is another layer of HA above that.  It does failover by rebuilding the instance if the failure requires it.23:05
johnsomkeepalived (master/backup) fails over in a second or two.  Health manager failover takes 30 seconds up to 10 minutes depending on your cloud and nova performance.23:06
kongok, the second question, how about including lb id in the vm name or metadata or tag?23:07
johnsomThe amphora ID is in the VM name23:08
kongi mean, the lb id23:08
kongthe ops want more information without querying directly from the db, if the information is easy to set by octavia23:10
johnsomI guess it could be added to the instance metadata.  I guess we just haven't had a use case for it since we track by amphora (LBs will have one or more amphroa)23:10
kongthe problem is we could only get amphora inforamation from database, which is what the ops want to avoid23:11
johnsomYes, we intentionally hide that information.23:11
johnsomkong You can now get that information via the Admin API: https://developer.openstack.org/api-ref/load-balancer/v2/index.html#list-amphora23:13
*** tongl has quit IRC23:14
johnsomThat said, if there is a good use case for adding the lb ID to the nova instance, I don't think it would be hard to do.23:14
kongjohnsom: hmm...it's in Queeen :-(23:15
johnsomYep.  So would adding it to the metadata....23:15
kongok, will leave it for now. I think the amphora api is what we want. Even if i can contribute to add lb id to vm's metadata, the feature will be still be avalable in Queen23:17
kongjohnsom: thanks. maybe we have to talk to db for now23:17
johnsomYeah, or do a local patch...23:18
kongjohnsom: hah, yeah, will consider that23:18
kongour policy is upstream first :-)23:18
johnsomGood policy.23:18
johnsomThe OpenStack stable branch policy says no backported features only bug fixes, so they sometimes conflict.  Others just run master.... grin23:19
kongyeah, i know. need a lot of testing if we want to backport some feature to stable branch, unless it could bring much benifit to the business23:20
johnsomQueens Milestone 1 release comes out in a week or two if that helps you at all23:23
kongwill evaluate it and discuss with ops23:24
*** sshank has quit IRC23:41

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