| *** zzxwill has quit IRC | 00:00 | |
| *** sridhar_ram1 has joined #senlin | 00:01 | |
| *** sridhar_ram has quit IRC | 00:03 | |
| *** zzxwill has joined #senlin | 00:06 | |
| *** Qiming has quit IRC | 00:08 | |
| *** zzxwill has quit IRC | 00:20 | |
| *** openstackgerrit_ has quit IRC | 00:23 | |
| *** zzxwill has joined #senlin | 00:24 | |
| *** openstackgerrit_ has joined #senlin | 00:25 | |
| *** zzxwill has quit IRC | 00:41 | |
| *** zzxwill has joined #senlin | 00:42 | |
| *** openstackgerrit_ has quit IRC | 00:48 | |
| *** openstackgerrit_ has joined #senlin | 00:50 | |
| *** zzxwill has quit IRC | 00:52 | |
| *** sridhar_ram1 has quit IRC | 00:57 | |
| *** zzxwill has joined #senlin | 00:59 | |
| *** sridhar_ram has joined #senlin | 01:01 | |
| *** Qiming has joined #senlin | 01:07 | |
| *** zzxwill has quit IRC | 01:13 | |
| *** zzxwill has joined #senlin | 01:18 | |
| *** zzxwill has quit IRC | 01:33 | |
| *** zzxwill has joined #senlin | 01:34 | |
| *** sridhar_ram has quit IRC | 01:35 | |
| *** zzxwill has quit IRC | 01:49 | |
| *** zzxwill has joined #senlin | 01:49 | |
| *** Yanyanhu has joined #senlin | 01:58 | |
| *** zzxwill has quit IRC | 02:00 | |
| *** zzxwill has joined #senlin | 02:12 | |
| *** elynn has joined #senlin | 02:19 | |
| *** zzxwill has quit IRC | 02:24 | |
| *** elynn has quit IRC | 02:25 | |
| *** elynn has joined #senlin | 02:25 | |
| *** zzxwill has joined #senlin | 02:30 | |
| Qiming | hi, guys | 02:39 |
|---|---|---|
| Qiming | during a discussion with some early users, I was answering their questions regarding how authentication is done, how multi-region deployment is performed | 02:40 |
| Qiming | so I was revisiting the api middleware source to make sure I'm talking accurately | 02:41 |
| Qiming | however, I am not feeling comfortable when I saw the trust middleware talks directly to db | 02:41 |
| Yanyanhu | you mean the part about keystone middleware? | 02:41 |
| Qiming | that is the question I want to raise | 02:42 |
| Qiming | should we eliminate direct DB interactions from the API layer | 02:42 |
| Qiming | that will make the architecture much cleaner | 02:42 |
| Yanyanhu | Qiming, this is what we wanted. but didn't find a better way to address problem before | 02:42 |
| Qiming | I want to introduce some "internal" RPC interfaces for trust retrieval and creation | 02:42 |
| Qiming | in the api pipeline, trust comes after the context middleware | 02:43 |
| Qiming | so it is possible to decouple it from db | 02:43 |
| Yanyanhu | hmm, this is feasible. But on potential problem is the API request handling progress could be blocked if engine is busy | 02:44 |
| Qiming | I can look into that if there is no objections on this | 02:44 |
| Qiming | if the engine is busy, you cannot make any progress anyway | 02:44 |
| Qiming | don't believe that is a valid concern | 02:44 |
| Yanyanhu | I mean the pgress inside middleware | 02:44 |
| Yanyanhu | yes, but that's a little bit different | 02:44 |
| Qiming | have to leave for a moment | 02:45 |
| Yanyanhu | anyway, not a serious problem | 02:45 |
| Yanyanhu | ok, ttyl | 02:45 |
| lixinhui | Yanyanhu | 02:50 |
| lixinhui | have you ever meeting this problem | 02:50 |
| lixinhui | octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to instance. Retrying | 02:50 |
| Yanyanhu | no... | 02:51 |
| lixinhui | Once you said some config need to pay attention | 02:51 |
| Yanyanhu | hi, lixinhui, octavia is another lb service in openstack? | 02:51 |
| lixinhui | it is the provider of lb | 02:51 |
| lixinhui | in haproxy driv er | 02:51 |
| lixinhui | I wonder what it is | 02:52 |
| Yanyanhu | oh, I see | 02:52 |
| Yanyanhu | about the configure, I mean the driver type and I can't recall whether there is some authentication related options | 02:52 |
| Yanyanhu | by the driver, it's actually the service provider | 02:53 |
| lixinhui | Difficult here is hard to find real error | 02:56 |
| lixinhui | behind the PENDING-to.... | 02:56 |
| Yanyanhu | yes... | 02:58 |
| Yanyanhu | I remember I used to check haproxy related process or something to ensure it works well | 02:58 |
| Yanyanhu | but can't recall the detail how to check it... | 02:58 |
| lixinhui | okay | 03:00 |
| lixinhui | so you do not use octavia | 03:00 |
| Qiming | sounds like a networking problem? | 03:03 |
| Yanyanhu | lixinhui, yes, I didn't use it before | 03:03 |
| Qiming | after your ha_proxy machine is up | 03:03 |
| Qiming | you can try connect to it manually | 03:03 |
| Qiming | sometimes, it takes time to have the controller realize there are new destination reachable | 03:04 |
| Qiming | sometimes, the security group thing jumps into the way when you try connecting to a VM | 03:04 |
| *** zzxwill has quit IRC | 03:12 | |
| *** zzxwill has joined #senlin | 03:16 | |
| *** elynn_ has joined #senlin | 03:26 | |
| *** elynn has quit IRC | 03:30 | |
| *** gmann has left #senlin | 03:48 | |
| *** elynn_ has quit IRC | 04:01 | |
| *** shu-mutou-AFK is now known as shu-mutou | 04:02 | |
| *** zzxwill has quit IRC | 04:11 | |
| *** zzxwill has joined #senlin | 04:12 | |
| *** zzxwill has quit IRC | 04:33 | |
| *** zzxwill has joined #senlin | 04:51 | |
| *** elynn_ has joined #senlin | 04:56 | |
| *** elynn_ has quit IRC | 05:00 | |
| *** elynn_ has joined #senlin | 05:01 | |
| *** zzxwill has quit IRC | 05:14 | |
| *** zzxwill has joined #senlin | 05:18 | |
| *** sridhar_ram has joined #senlin | 05:23 | |
| *** zzxwill has quit IRC | 05:27 | |
| *** zzxwill has joined #senlin | 05:30 | |
| *** jdandrea has quit IRC | 05:33 | |
| *** heyongli has joined #senlin | 05:39 | |
| *** jdandrea has joined #senlin | 05:40 | |
| *** heyongli has quit IRC | 05:41 | |
| *** heyongli has joined #senlin | 05:41 | |
| *** zzxwill has quit IRC | 05:43 | |
| *** zzxwill has joined #senlin | 05:44 | |
| *** heyongli has quit IRC | 05:46 | |
| *** heyongli has joined #senlin | 05:46 | |
| *** jdandrea_ has joined #senlin | 05:49 | |
| *** jdandrea has quit IRC | 05:50 | |
| *** zzxwill has quit IRC | 05:54 | |
| *** zzxwill has joined #senlin | 05:55 | |
| *** heyongli has quit IRC | 05:56 | |
| *** heyongli has joined #senlin | 05:57 | |
| Yanyanhu | hi, Qiming, I'm considering retore the obsoleted BP of access permission control in Senlin. Since this is not a work that will be done in this cycle, I will mark it as under discussion. | 06:02 |
| Qiming | okay | 06:04 |
| Qiming | Yanyanhu, http://www.gossamer-threads.com/lists/openstack/dev/52819?page=last | 06:06 |
| *** heyongli has quit IRC | 06:06 | |
| *** heyongli has joined #senlin | 06:07 | |
| Yanyanhu | will read it carefully :) | 06:07 |
| Qiming | what we are proposing is actually called "DYNAMIC" RBAC in keystone terms | 06:07 |
| Yanyanhu | yes | 06:08 |
| Qiming | spes from ayoung is here: https://review.openstack.org/#/c/279379/1/specs/backlog/dynamic-policy.rst | 06:08 |
| Yanyanhu | thanks a lot for this clue | 06:10 |
| *** heyongli has quit IRC | 06:17 | |
| *** heyongli has joined #senlin | 06:17 | |
| *** openstackgerrit_ has quit IRC | 06:17 | |
| *** openstackgerrit_ has joined #senlin | 06:18 | |
| *** zzxwill has quit IRC | 06:25 | |
| *** heyongli has quit IRC | 06:27 | |
| *** zzxwill has joined #senlin | 06:28 | |
| lixinhui | Qiming, it should irrelevant to secuity group | 06:33 |
| *** zzxwill has quit IRC | 06:33 | |
| lixinhui | and the loadbalancer instance hide behind and nova can not list it | 06:33 |
| *** zzxwill has joined #senlin | 06:33 | |
| lixinhui | the port id seems right | 06:33 |
| lixinhui | but the error means the ha_procy driver can not connect to the built instance | 06:34 |
| lixinhui | I will search more to see what is the process | 06:34 |
| lixinhui | behind | 06:34 |
| *** shu-mutou is now known as shu-mutou-AFK | 06:46 | |
| *** sridhar_ram has quit IRC | 06:56 | |
| *** zzxwill has quit IRC | 06:58 | |
| *** zzxwill has joined #senlin | 07:07 | |
| *** elynn_ has quit IRC | 07:09 | |
| Qiming | what is the built instance referring to? | 07:10 |
| Qiming | if you cannot list it, try the admin account? | 07:11 |
| lixinhui | admin is the same | 07:14 |
| *** elynn has joined #senlin | 07:14 | |
| lixinhui | the built instance is the loadbaancer imstance in lbaas v2 | 07:14 |
| Qiming | that instance is a VM | 07:16 |
| Qiming | maybe it is in a special project | 07:16 |
| Qiming | lixinhui, this line: http://git.openstack.org/cgit/openstack/octavia/tree/etc/octavia.conf#n141 | 07:18 |
| Qiming | it means the amphora instance may need a security group, but by default it is empty | 07:18 |
| Qiming | that is something you may want to verify | 07:18 |
| Qiming | another possibility, it takes too long to wait for the instance to become reachable | 07:19 |
| lixinhui | it will us ethe default | 07:19 |
| lixinhui | ok | 07:20 |
| Qiming | okay, you have configured your default security group? | 07:20 |
| lixinhui | yes | 07:20 |
| Qiming | great | 07:20 |
| lixinhui | the port it used to ccreate the instance is right one | 07:20 |
| Qiming | the new "default" security group is not blocking any port range, right? | 07:20 |
| lixinhui | en | 07:20 |
| Qiming | okay, that almost eliminates the possibility of secgroup | 07:21 |
| lixinhui | all the samples I searched about lbaas v2 is using octavia | 07:22 |
| lixinhui | so I am seaeching how to check correctness of ha_proxy process | 07:22 |
| Qiming | you got to log into that instance | 07:22 |
| lixinhui | okay | 07:22 |
| lixinhui | let me try to find some clue to do it | 07:23 |
| Qiming | one way to try | 07:23 |
| Qiming | export OS_USERNAME=admin | 07:23 |
| Qiming | then 'nova list --all-tenants 1' | 07:23 |
| Qiming | I didn't try it before | 07:24 |
| lixinhui | ok | 07:24 |
| lixinhui | will try it | 07:24 |
| Qiming | but I really believe the nova instance is created somewhere | 07:24 |
| lixinhui | en | 07:24 |
| *** gongysh has joined #senlin | 07:26 | |
| Qiming | gongysh, hi | 07:30 |
| *** zzxwill has quit IRC | 07:31 | |
| gongysh | Qiming, hi | 07:32 |
| Qiming | hi, we have encountered some LBaaS and octavia problem | 07:33 |
| Qiming | where I believe you are THE expert, :) | 07:33 |
| *** zzxwill has joined #senlin | 07:33 | |
| gongysh | Qiming, no, I have not play with it yet. beyond mime. | 07:33 |
| Qiming | okay, give me a name | 07:34 |
| Qiming | I'll let you go | 07:34 |
| *** zzxwill has quit IRC | 07:38 | |
| Qiming | ??? | 07:38 |
| Qiming | gongysh, ??? | 07:38 |
| * gongysh looking ... | 07:39 | |
| Qiming | among these names: | 07:39 |
| Qiming | Adam Harwellflux.adam@gmail.com | 07:39 |
| Qiming | Bertrand Lallaubertrand.lallau@gmail.com | 07:39 |
| Qiming | Brandon Loganbrandon.logan@rackspace.com | 07:39 |
| Qiming | Doug Wiegleydougwig@parkside.io | 07:39 |
| Qiming | German Eichbergergerman.eichberger@hp.com | 07:39 |
| Qiming | Michael Johnsonjohnsomor@gmail.com | 07:39 |
| Qiming | Stephen Balukoffstephen@balukoff.com | 07:39 |
| gongysh | https://wiki.openstack.org/wiki/Octavia | 07:40 |
| gongysh | Qiming, IRC: #openstack-lbaas | 07:41 |
| Qiming | okay, :) | 07:41 |
| Qiming | you are of no value now | 07:41 |
| * Qiming pulls the trigger ... | 07:41 | |
| gongysh | Qiming, shot dead. | 07:43 |
| Qiming | LOL | 07:43 |
| *** zzxwill has joined #senlin | 07:45 | |
| Yanyanhu | hi, Qiming, just quickly went through the spec from adam young | 07:52 |
| Yanyanhu | it's very helpful for controlling http resource access based on role check | 07:52 |
| Qiming | yep | 07:53 |
| Qiming | it looks like one | 07:53 |
| Yanyanhu | but it's not satisfied enough to meet our requirement | 07:53 |
| Qiming | but as ayoung mentioned | 07:53 |
| Yanyanhu | e.g. control the access to each single entity | 07:53 |
| Qiming | api level or pre-api level access control is still limited | 07:53 |
| Yanyanhu | yes | 07:53 |
| Qiming | it is not touching the resources inside database | 07:54 |
| Yanyanhu | it's understandable | 07:54 |
| Yanyanhu | right | 07:54 |
| Qiming | yes | 07:54 |
| Qiming | so, with that in minde | 07:54 |
| Yanyanhu | so I guess maybe we can have both of them | 07:54 |
| Qiming | s/minde/mind | 07:54 |
| Yanyanhu | definitely | 07:54 |
| Qiming | we can work on the permission thing | 07:54 |
| Yanyanhu | right | 07:54 |
| Yanyanhu | this is what I'm thinking now | 07:54 |
| Qiming | cool | 07:54 |
| Yanyanhu | will try to mix them | 07:54 |
| Yanyanhu | leverage what keystone can provide us as much as possible | 07:55 |
| Qiming | however, I'm not so sure if a per-resource access control is needed | 07:55 |
| Yanyanhu | and implement the function it doesn't provision in Senlin | 07:55 |
| Yanyanhu | will leave for a while | 07:55 |
| Yanyanhu | ttyl | 07:55 |
| Qiming | we may need 'chown', 'chmod' calls | 07:55 |
| Yanyanhu | yea, will further think about it | 07:55 |
| Yanyanhu | yes | 07:56 |
| Yanyanhu | this is what we want | 07:56 |
| Yanyanhu | leave now | 07:56 |
| Yanyanhu | go back later | 07:56 |
| *** zzxwill has quit IRC | 08:02 | |
| *** zzxwill has joined #senlin | 08:03 | |
| Qiming | so ... | 08:05 |
| Qiming | this is one of the quiet weeks where we are not supposed to add new features | 08:05 |
| Qiming | until newton development opens | 08:06 |
| Qiming | I'd like to give testing a higher priority | 08:06 |
| Qiming | e.g. tempest, rally, functiona, stress ... etc | 08:06 |
| Qiming | none of those will break the existing code | 08:06 |
| Qiming | (hopefully) :) | 08:06 |
| Yanyanhu | Qiming, yes, actually I'm now planning to add some functional test for failure cases which can be implemented inside existing framework | 08:16 |
| Yanyanhu | e.g. creating cluster with invalid profile-id | 08:16 |
| Yanyanhu | something like this | 08:16 |
| Yanyanhu | for more complicated cases, or API consistency test, may need new design | 08:17 |
| Qiming | we can start shifting to tempest I think | 08:18 |
| Yanyanhu | you mean shift functional test to tempest? Or using tempest for API test | 08:19 |
| Yanyanhu | I recalled maintaining functional test inside each project individually is recommened? | 08:19 |
| Qiming | at least, api surface test should be done via tempest plugin | 08:20 |
| Qiming | yes, no conflict there | 08:20 |
| Qiming | the code should live in senlin | 08:21 |
| Yanyanhu | I see | 08:21 |
| Qiming | we got some pretty good guidance the other day from a tempest expert | 08:21 |
| Qiming | we can check how it works by looking into congress | 08:21 |
| Yanyanhu | so the difference is where we define the job, devstack gate or tempest? | 08:21 |
| Qiming | for example | 08:21 |
| Qiming | it can be a tox env specified in tox.ini | 08:22 |
| Yanyanhu | ok | 08:23 |
| *** zzxwill has quit IRC | 08:25 | |
| *** zzxwill has joined #senlin | 08:29 | |
| *** zzxwill has quit IRC | 08:37 | |
| openstackgerrit | Qiming Teng proposed openstack/senlin: Add engine service RPC api for credentials https://review.openstack.org/291599 | 08:40 |
| *** zzxwill has joined #senlin | 08:40 | |
| openstackgerrit | Qiming Teng proposed openstack/senlin: Add engine service RPC api for credentials https://review.openstack.org/291599 | 08:45 |
| *** gongysh has quit IRC | 08:46 | |
| *** zzxwill has quit IRC | 08:47 | |
| *** zzxwill has joined #senlin | 08:50 | |
| *** gongysh has joined #senlin | 08:51 | |
| lixinhui | Qiming | 08:56 |
| lixinhui | http://paste.openstack.org/show/490105/ | 08:56 |
| lixinhui | that is the loadbalancer instance | 08:56 |
| lixinhui | but can not ssh it | 08:56 |
| lixinhui | because of lack of router | 08:56 |
| Qiming | okay, checking | 08:58 |
| Qiming | you cannot even ssh to it via 10.0.0.4? | 08:59 |
| Qiming | it has a security group named lb-mgmt-sec-grp | 09:00 |
| Qiming | and the management network is 192.168.0.4 | 09:01 |
| Qiming | you will need a octavia_ssh_key to ssh, after switching to project eb59c8ab580b40c586c5bda06f51c8f8 | 09:01 |
| Qiming | if the ssh is still rejected, you can treat it as a normal SSH problem | 09:02 |
| openstackgerrit | Qiming Teng proposed openstack/senlin: RPC support for credential operations https://review.openstack.org/291614 | 09:04 |
| lixinhui | no reponse too by 10.0.04 | 09:05 |
| Qiming | can you ping it? | 09:06 |
| lixinhui | I can not | 09:07 |
| lixinhui | but sure for management net | 09:07 |
| lixinhui | IP | 09:07 |
| lixinhui | and I can find the key under /etc/octavia/.ssh/octavia_ssh_key | 09:08 |
| *** elynn_ has joined #senlin | 09:09 | |
| *** elynn has quit IRC | 09:10 | |
| Qiming | "but sure for management net" ... what does this mean? | 09:11 |
| Qiming | you can reach it from management network? | 09:13 |
| lixinhui | I can ping through the management net | 09:13 |
| Qiming | then you should log in via management net | 09:13 |
| lixinhui | but ssh faild although I can find the key | 09:13 |
| lixinhui | ssh: connect to host 192.168.0.4 port 22: No route to host | 09:14 |
| Yanyanhu | security group problem? | 09:14 |
| Qiming | you can ping it | 09:14 |
| lixinhui | have done this | 09:14 |
| lixinhui | neutron security-group-rule-create f29c45ff-dfd3-44a3-a1a6-b7716eff9041 --protocol tcp --port-range-min 22 --port-range-max 22 | 09:14 |
| lixinhui | ping workds | 09:15 |
| lixinhui | works | 09:15 |
| lixinhui | f29c45ff-dfd3-44a3-a1a6-b7716eff9041 is the management net | 09:15 |
| Qiming | ssh is giving an inaccurate error message ... | 09:15 |
| Yanyanhu | did you apply this security group when booting up VM? | 09:15 |
| Qiming | what are the first few characters of the octavia_ssh_key file? | 09:17 |
| lixinhui | Permission denied (publickey). | 09:19 |
| lixinhui | http://paste.openstack.org/show/490109/ | 09:19 |
| *** zzxwill has quit IRC | 09:20 | |
| *** zzxwill has joined #senlin | 09:21 | |
| Qiming | okay, that is a private key | 09:22 |
| Qiming | ssh -i /etc/octavia/.ssh/octavia_ssh_key 192.168.0.4 doesn't work? | 09:23 |
| lixinhui | en, same error | 09:23 |
| Qiming | it didn't ask for assword? | 09:24 |
| lixinhui | no... | 09:24 |
| Qiming | okay, the image has disabled password authentication | 09:25 |
| Qiming | do you know the OS installed in the image? | 09:25 |
| lixinhui | bu default it should be ubuntu | 09:27 |
| lixinhui | http://docs.openstack.org/developer/octavia/specs/version0.5/base-image.html | 09:27 |
| Qiming | ssh -i /etc/octavia/.ssh/octavia_ssh_key ubuntu@192.168.0.4 ? | 09:32 |
| Qiming | I think we are creating a lot of problems because the installation and configuration of octavia wasn't complete | 09:33 |
| Qiming | when I tried read the source code of rest_api_driver.py | 09:33 |
| Qiming | I found that octavia is actually doing a REST call | 09:34 |
| Qiming | with a server certificate | 09:34 |
| Qiming | which should be configured in haproxy_amphora section, named 'server_ca' | 09:34 |
| Qiming | that is the only thing required for the REST request | 09:35 |
| lixinhui | ys | 09:36 |
| lixinhui | it is set by default value | 09:36 |
| Qiming | http://docs.openstack.org/developer/octavia/design/version0.5/component-design.html#some-notes-on-controller-amphorae-communications | 09:36 |
| lixinhui | and to avoid the mismatch problem | 09:37 |
| Qiming | how is the server_ca generated? | 09:37 |
| Qiming | any script doing that? | 09:37 |
| lixinhui | I ensure generate the octavia.conf very time now | 09:37 |
| Qiming | but generating octavia.conf doesn't mean the generation of a server_ca | 09:38 |
| lixinhui | opt/stack/octavia/devstack/plugin.sh | 09:39 |
| Qiming | okay, I see | 09:39 |
| *** elynn_ has quit IRC | 09:41 | |
| lixinhui | it is indeed generated with the conf together | 09:41 |
| Qiming | okay, so it is generating certificates | 09:42 |
| *** Yanyanhu has quit IRC | 09:42 | |
| lixinhui | en | 09:42 |
| Qiming | if I were you I will add a LOG.error('%s' % reqargs) at here: http://git.openstack.org/cgit/openstack/octavia/tree/octavia/amphorae/drivers/haproxy/rest_api_driver.py#n241 | 09:44 |
| Qiming | or, at line 242, try catch the exception and print it out | 09:45 |
| Qiming | I really hate this design, which is making the most fragile link very difficult to debug | 09:46 |
| lixinhui | okay | 09:46 |
| Qiming | after you have modified the code | 09:47 |
| *** elynn_ has joined #senlin | 09:47 | |
| Qiming | you don't have to reinstall devstack, alright? | 09:47 |
| Qiming | just kill the octavia service and restart it | 09:47 |
| lixinhui | I see | 09:47 |
| Qiming | also, you may want to try your luck in the #openstack-lbaas channel | 09:49 |
| Qiming | I think such a problem must be among the top 5 in their FAQ list | 09:49 |
| lixinhui | actually | 09:49 |
| lixinhui | there have some one report this bug | 09:49 |
| lixinhui | but no further action there | 09:50 |
| *** elynn_ has quit IRC | 09:52 | |
| lixinhui | thanks | 09:55 |
| lixinhui | I leave some message at the channel hope someone could help | 09:55 |
| lixinhui | the error content is | 09:55 |
| lixinhui | 2016-03-11 17:47:52.794 3785 ERROR octavia.amphorae.drivers.haproxy.rest_api_driver [-] {'url': 'https://192.168.0.5:9443/0.5/plug/vip/10.0.0.5', 'verify': '/etc/octavia/certs/ca_01.pem', 'json': {'subnet_cidr': u'10.0.0.0/24', 'gateway': u'10.0.0.1', 'mac_address': u'fa:16:3e:94:b0:2c'}, 'timeout': (10.0, 60.0), 'headers': {'User-Agent': 'Octavia HaProxy Rest Client/0.5 (https://wiki.openstack.org/wiki/Octavia)'}} | 09:55 |
| *** zzxwill has quit IRC | 09:58 | |
| Qiming | okay | 09:59 |
| Qiming | the above log shows you that the rest api is invoked from the 10 network, not the 192.168 network | 10:00 |
| *** zzxwill has joined #senlin | 10:01 | |
| Qiming | sorry, it is about getting data from 192.168.0.5 | 10:01 |
| Qiming | and the port is now 9443 | 10:01 |
| Qiming | is that port opened? | 10:02 |
| * Qiming is feeling very very very hungry ... | 10:03 | |
| lixinhui | yes | 10:08 |
| *** elynn_ has joined #senlin | 10:11 | |
| *** Qiming has quit IRC | 10:11 | |
| lixinhui | ~$ netstat -nap|grep 9443 | 10:14 |
| lixinhui | (No info could be read for "-p": geteuid()=1000 but you should be root.) | 10:14 |
| lixinhui | tcp 0 0 0.0.0.0:9443 0.0.0.0:* LISTEN - | 10:14 |
| *** elynn_ has quit IRC | 10:20 | |
| *** gongysh has quit IRC | 10:31 | |
| *** zzxwill has quit IRC | 10:35 | |
| *** zzxwill has joined #senlin | 10:38 | |
| *** zzxwill has quit IRC | 10:40 | |
| *** zzxwill has joined #senlin | 10:50 | |
| *** zzxwill has quit IRC | 10:54 | |
| -openstackstatus- NOTICE: Gerrit is going to be restarted due to bad performance | 10:55 | |
| *** ChanServ changes topic to "Gerrit is going to be restarted due to bad performance" | 10:55 | |
| *** ChanServ changes topic to "IRCLog: http://eavesdrop.openstack.org/irclogs/%23senlin/ | Bugs: bugs.launchpad.net/senlin | Review: https://review.openstack.org/#/q/project:openstack/senlin,n,z" | 11:01 | |
| -openstackstatus- NOTICE: Gerrit has been restarted successfully | 11:01 | |
| *** Qiming has joined #senlin | 11:01 | |
| *** zhenguo_ has quit IRC | 12:10 | |
| *** zzxwill has joined #senlin | 12:37 | |
| *** zzxwill has quit IRC | 13:41 | |
| *** zzxwill has joined #senlin | 13:44 | |
| *** Qiming has quit IRC | 13:54 | |
| *** Qiming has joined #senlin | 13:54 | |
| *** lixinhui_ has joined #senlin | 14:16 | |
| *** lixinhui_ has quit IRC | 14:17 | |
| *** zzxwill has quit IRC | 14:55 | |
| *** zzxwill has joined #senlin | 14:57 | |
| *** Qiming has quit IRC | 14:58 | |
| *** Qiming has joined #senlin | 14:58 | |
| *** zzxwill has quit IRC | 14:59 | |
| *** zzxwill has joined #senlin | 15:57 | |
| *** Qiming has quit IRC | 16:11 | |
| *** zzxwill has quit IRC | 16:39 | |
| *** zzxwill has joined #senlin | 16:42 | |
| *** zzxwill has quit IRC | 16:46 | |
| *** zzxwill has joined #senlin | 16:57 | |
| *** zzxwill has quit IRC | 17:23 | |
| *** zzxwill has joined #senlin | 17:31 | |
| *** zzxwill has quit IRC | 17:45 | |
| *** zzxwill has joined #senlin | 17:58 | |
| *** zzxwill has quit IRC | 18:04 | |
| *** zzxwill has joined #senlin | 18:17 | |
| *** zzxwill_ has joined #senlin | 18:31 | |
| *** zzxwill has quit IRC | 18:31 | |
| *** zzxwill_ has quit IRC | 18:38 | |
| *** sridhar_ram has joined #senlin | 18:58 | |
| *** sridhar_ram1 has joined #senlin | 19:01 | |
| *** sridhar_ram has quit IRC | 19:03 | |
| *** sridhar_ram1 is now known as sridhar_ram | 19:49 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!