| *** lixinhui has joined #senlin | 00:02 | |
| *** lixinhui has quit IRC | 00:07 | |
| *** Qiming has quit IRC | 00:08 | |
| *** lixinhui has joined #senlin | 00:29 | |
| *** lixinhui has quit IRC | 00:34 | |
| openstackgerrit | Merged stackforge/senlin: Getting Started Doc (5) https://review.openstack.org/200801 | 00:49 |
|---|---|---|
| *** lixinhui has joined #senlin | 00:56 | |
| *** jruano has joined #senlin | 01:02 | |
| *** Qiming has joined #senlin | 01:04 | |
| *** Qiming_ has joined #senlin | 01:05 | |
| *** lixinhui has quit IRC | 01:08 | |
| *** Qiming has quit IRC | 01:09 | |
| openstackgerrit | Qiming Teng proposed stackforge/senlin: Remove tox and requirements hacking https://review.openstack.org/201881 | 01:14 |
| *** lixinhui has joined #senlin | 01:24 | |
| *** Yanyanhu has joined #senlin | 01:25 | |
| *** lixinhui has quit IRC | 01:29 | |
| *** Yanyanhu has quit IRC | 01:29 | |
| *** Yanyan has joined #senlin | 01:34 | |
| *** jruano has quit IRC | 01:35 | |
| *** lixinhui has joined #senlin | 01:51 | |
| *** lixinhui has quit IRC | 01:56 | |
| *** lixinhui has joined #senlin | 02:18 | |
| openstackgerrit | Merged stackforge/senlin: Remove tox and requirements hacking https://review.openstack.org/201881 | 02:21 |
| *** lixinhui has quit IRC | 02:27 | |
| openstackgerrit | Merged stackforge/python-senlinclient: Updated from global requirements https://review.openstack.org/201848 | 02:34 |
| openstackgerrit | Merged stackforge/senlin: Updated from global requirements https://review.openstack.org/201849 | 02:43 |
| *** lixinhui has joined #senlin | 02:45 | |
| *** admin__ has joined #senlin | 02:52 | |
| *** lixinhui has left #senlin | 02:52 | |
| *** Qiming_ has quit IRC | 02:55 | |
| openstackgerrit | Yanyan Hu proposed stackforge/senlin: Clean the init progress of some Senlin drivers https://review.openstack.org/201900 | 03:20 |
| openstackgerrit | Yanyan Hu proposed stackforge/senlin: Remove initilization of auth and session attrs in some drivers https://review.openstack.org/201900 | 03:21 |
| *** admin__ has quit IRC | 03:30 | |
| *** lixinhui has joined #senlin | 05:28 | |
| *** Qiming has joined #senlin | 05:59 | |
| openstackgerrit | Cindia-blue proposed stackforge/senlin: enable scheduler_hints when nova server create https://review.openstack.org/201930 | 06:15 |
| Yanyan | hi, Qiming, found the reason of the error that occured during 'list' operation | 06:16 |
| Yanyan | http://git.openstack.org/cgit/stackforge/python-openstacksdk/tree/openstack/resource.py#n815 | 06:16 |
| Yanyan | the 'params' argument is changed in latest patch in sdk | 06:16 |
| Yanyan | https://review.openstack.org/#/c/200308/ | 06:17 |
| Yanyan | seems they made a decision after discussion... | 06:18 |
| Qiming | okay, so we may need to revise our driver code | 06:28 |
| Yanyan | yes | 06:28 |
| Yanyan | will make a change on both driver and client side | 06:29 |
| openstackgerrit | Cindia-blue proposed stackforge/senlin: enable scheduer_hints https://review.openstack.org/201935 | 06:29 |
| Qiming | okay | 06:31 |
| Qiming | have you seen the link shared by Julio? | 06:34 |
| Yanyan | not yet, where did he share it? | 06:34 |
| Qiming | on mailinglist, forwarding it to you all | 06:35 |
| Yanyan | ok, let me have a look | 06:35 |
| Qiming | sending | 06:37 |
| Yanyan | ok, thanks | 06:37 |
| Yanyan | saw the mail in maillist | 06:37 |
| Qiming | the second link doesn't work for me | 06:42 |
| Yanyan | I'm downloading this doc, but very slow | 06:43 |
| Yanyan | will cost about 20mins | 06:43 |
| openstackgerrit | Yanyan Hu proposed stackforge/senlin: Using openstacksdk function call in keystone_v3 driver https://review.openstack.org/201945 | 06:47 |
| openstackgerrit | Yanyan Hu proposed stackforge/python-senlinclient: Using list query arguments as a single dict input parameter https://review.openstack.org/201946 | 06:47 |
| Qiming | Yanyan, with your change ^, we will need to use the master head of openstacksdk? | 06:50 |
| Yanyan | emm, that's true, so I guess we may need to block these patches until sdk provides a new release | 06:51 |
| Yanyan | e.g. 5.1 | 06:51 |
| Yanyan | 0.5.1 | 06:52 |
| Qiming | I cannot recall when, but there was an anncouncement from Brian that they are not accepting new resources to the sdk until they are finishing their 1.0 release | 06:52 |
| Qiming | a 1.0 release sounds like an official one to me | 06:52 |
| Yanyan | ok, so maybe that will be a 'stable' one we want to rely on when we do our own release :) | 06:53 |
| Yanyan | I will finish another patch that revises the query argument usage in other drivers and then block all these three patches until sdk updates its release version | 06:55 |
| openstackgerrit | Yanyan Hu proposed stackforge/senlin: Using openstacksdk function call in keystone_v3 driver https://review.openstack.org/201945 | 07:00 |
| Qiming | this | 07:05 |
| Qiming | is | 07:05 |
| Qiming | interesting | 07:05 |
| Qiming | https://review.openstack.org/#/c/193550/1/reference/new-projects-requirements.rst | 07:05 |
| Yanyan | :) | 07:07 |
| Yanyan | why they remove this constrains | 07:07 |
| Yanyan | constraint | 07:07 |
| Qiming | :) a single contributor project now qualifies | 07:07 |
| Yanyan | haha | 07:07 |
| Yanyan | insteresting :) | 07:07 |
| Yanyan | the one who is PTL, core member and also the only contributor ;) | 07:08 |
| Qiming | yes | 07:08 |
| lixinhui | does openstack connection can provide novaclient equal fucntions? | 07:36 |
| lixinhui | I am checking its support to server_group | 07:36 |
| lixinhui | is in limits | 07:37 |
| lixinhui | but novaclient can support whole server_group calls | 07:37 |
| lixinhui | such as I wanna get one server_group by id | 07:37 |
| lixinhui | I donot know how to reach this by openstacksdk connections | 07:38 |
| openstackgerrit | OpenStack Proposal Bot proposed stackforge/senlin: Updated from global requirements https://review.openstack.org/201964 | 07:40 |
| Qiming | lixinhui, I'm trying to find an email from the mailinglist | 07:50 |
| Qiming | it was sent by Brian | 07:50 |
| lixinhui | okay | 07:55 |
| openstackgerrit | Yanyan Hu proposed stackforge/senlin: Using openstacksdk function call in keystone_v3 driver https://review.openstack.org/201945 | 07:57 |
| Yanyan | hi, Qiming, just realized that we actaully don't need to revise the driver implementation in Senlin service since the change in openstacksdk only influence the interface of resource call but not the function call | 07:58 |
| Qiming | lixinhui, not sure if the 'PUT' or 'PATCH' actions are supported | 07:59 |
| Qiming | it is not well documented | 07:59 |
| Qiming | Yanyan, okay | 07:59 |
| Qiming | that is good news | 07:59 |
| Yanyan | so just proposed a change to keystone driver which is still using resource call for some cases | 07:59 |
| Yanyan | yes :0 | 07:59 |
| lixinhui | qiming? | 08:01 |
| Qiming | yes? | 08:01 |
| lixinhui | what does that mean? | 08:01 |
| lixinhui | should we propose some function add to openstacksdk or | 08:01 |
| lixinhui | just format/request type problem | 08:02 |
| Qiming | we have to do this via sdk | 08:02 |
| Qiming | okay, I found the link: http://lists.openstack.org/pipermail/openstack-dev/2015-July/068802.html | 08:03 |
| Qiming | that is bad news | 08:03 |
| lixinhui | ... | 08:04 |
| Qiming | need to check out their agenda | 08:04 |
| lixinhui | can we drive them? :-) | 08:06 |
| lixinhui | I can move ahead to policy/plugin works for our demo but depend on server_group/scheduler_hints at nova layer | 08:07 |
| Qiming | lixinhui, https://review.openstack.org/201983 | 08:26 |
| Qiming | I don't think pushing them is gonna change anything | 08:27 |
| lixinhui | I see | 08:27 |
| Qiming | Since the email was sent a week ago, I think they are drawing pretty near to their release | 08:27 |
| lixinhui | oh, I did not notice that. | 08:30 |
| lixinhui | anyway, I can try patach way | 08:30 |
| Qiming | yes, you can try this sdk patch and continue the senlin patch | 08:31 |
| Qiming | sigh, network is very slow ... | 08:31 |
| *** jdandrea has quit IRC | 08:32 | |
| openstackgerrit | Merged stackforge/senlin: Updated from global requirements https://review.openstack.org/201964 | 08:37 |
| Qiming | Yanyan, have you solved the tox env problem? | 09:06 |
| Yanyan | Qiming, yes, it is caused by my low virtualenv version | 09:09 |
| Yanyan | each version virtualenv has different pip version | 09:09 |
| Yanyan | so after I updated my virtualenv to 1.3.0, problem is solved :) | 09:10 |
| Yanyan | 1.1.0 virtualenv only support 6.1 version pip | 09:10 |
| Yanyan | sorry, virtualenv 13.0 | 09:10 |
| Qiming | holy shit | 09:12 |
| Qiming | pypi is not accessible | 09:12 |
| Yanyan | ... | 09:12 |
| Qiming | cannot install oslo.utils | 09:12 |
| Yanyan | our network is really poor... | 09:13 |
| Qiming | it was blocked by the firewall | 09:13 |
| Yanyan | great firewall? | 09:13 |
| Qiming | each time after the so called network device upgrade, our network connection becomes more unstable | 09:17 |
| Yanyan | ... | 09:17 |
| Qiming | well, I am not using venv | 09:20 |
| Qiming | but I don't get why tox still run pip 6.1.1, not 7.1.0 | 09:21 |
| Yanyan | ... | 09:21 |
| Yanyan | that's weird | 09:21 |
| Yanyan | I found some other people asked this question, but no answer was given... | 09:21 |
| Yanyan | I searched in bing | 09:21 |
| Yanyan | that tox used incorrect pip version | 09:22 |
| Qiming | which version of tox are you using? | 09:23 |
| Yanyan | let me check | 09:24 |
| Yanyan | I think it's 1.7.0 | 09:24 |
| Qiming | tox --version | 09:24 |
| Yanyan | 1.9.2 | 09:24 |
| Qiming | pbr --version | 09:24 |
| Qiming | pip --version | 09:25 |
| Yanyan | 0.11.0 pbr | 09:25 |
| Qiming | I have updated to 1.3.0 | 09:25 |
| Yanyan | 7.1.0 pip | 09:25 |
| Yanyan | oh, if pbr=1.3.0, I can't run senlin-engine correctly | 09:25 |
| Yanyan | so I always manually downgrade it to 0.11 | 09:26 |
| Yanyan | pbr version conflict will be given if pbr version is 1.3.0 in my env | 09:26 |
| Qiming | ... | 09:28 |
| Yanyan | old problem... | 09:28 |
| Qiming | lifeless gave me an answer on heat channel | 09:35 |
| Qiming | trying | 09:35 |
| Yanyan | so even you don't use virtual env, you still need to update it? | 09:37 |
| Qiming | yes, tox is using it | 09:38 |
| Qiming | 13.1.0 is recommended | 09:38 |
| Qiming | earlier versions won't understand the environment constraints newly added | 09:38 |
| Yanyan | oh, right | 09:38 |
| Yanyan | I forget this part | 09:38 |
| Yanyan | tox will use virtualenv | 09:39 |
| Qiming | now .... | 09:39 |
| Qiming | the last problem, recreating a tox venv for testing, that will take time | 09:39 |
| Qiming | why we were born in this rediculous country ... | 09:39 |
| Yanyan | yes... | 09:39 |
| Yanyan | we can't choose ;p | 09:40 |
| Yanyan | decades ago | 09:40 |
| Qiming | by the way, I'm adding user/project/domain fields to policy object | 09:40 |
| Yanyan | ok | 09:40 |
| Qiming | the reason is that we have actions targeting at them | 09:41 |
| Qiming | and for webhook to work properly, we have to check if the requester is the "owner" of the targeted object or the "admin" | 09:41 |
| Yanyan | right | 09:41 |
| Qiming | and we cannot do this via policy.json, because we don't know which policy scope will be used | 09:42 |
| Yanyan | so actually if an entity can talk with other services, it need these three properties | 09:42 |
| Qiming | maybe we should add these fields to profile as well | 09:42 |
| Qiming | not necessarily | 09:42 |
| Qiming | when a requester A wants to create a webhook targeting a policy, with action 'POLICY_ATTACH' | 09:43 |
| Qiming | I have to check if A is the owner or an admin | 09:43 |
| Yanyan | yes | 09:43 |
| Qiming | this is necessary because we have the "webhooks:create" door widely open | 09:43 |
| Qiming | this has to be done manually | 09:44 |
| Yanyan | actually, when we try to talk with other services to create some extra resources when doing attach_policy, should we use the user/domain/project of policy to do the request? | 09:45 |
| Yanyan | oh | 09:45 |
| Yanyan | the same problem | 09:45 |
| Qiming | no | 09:45 |
| Qiming | you will check the target the poicy is attached to | 09:46 |
| Qiming | usually a cluster | 09:46 |
| Qiming | and use the cluster's user/project/domain info | 09:46 |
| Qiming | actually, we may need to check if the policy and the cluster are owned by the same user before trying the attach operation | 09:47 |
| Yanyan | ok, why we don't use the user info in context? | 09:47 |
| Qiming | not sure we should be so strict in that | 09:48 |
| Qiming | I want to remove context from calls | 09:48 |
| Qiming | context info is bound to a transaction/interaction with the service | 09:49 |
| Qiming | but the object will be owned by certain user/project | 09:49 |
| Qiming | those are immortal info | 09:49 |
| Yanyan | so the context is used to do the top-half authentication while user/domain/project info of the owner will be used in the bottom-half progress | 09:50 |
| Yanyan | the context decided whether a user can access some senlin resources, e.g. policy, cluster | 09:50 |
| Qiming | there is no context, we created it | 09:50 |
| Yanyan | while the owner of cluster decided whether it can talk with nova and create a instance | 09:51 |
| Qiming | we use trust there | 09:51 |
| Yanyan | yes, just currently, it is the context | 09:51 |
| Yanyan | owner user/domain/project + trust_id will be used to create sdk connection | 09:52 |
| Qiming | yes | 09:52 |
| Qiming | we are passing context info everywhere, while we have decided those things should be done with a trust created in the first place | 09:53 |
| Yanyan | yes | 09:54 |
| Qiming | this is making the whole code base a lot difficult to maintain | 09:54 |
| Yanyan | so currently, context will be removed after the request workflow reached engine | 09:54 |
| Yanyan | and the following operations will be done without context | 09:54 |
| Qiming | oh, shit, the mock-1.1.3 hash code is wrong on pypi, another stupid error | 09:55 |
| Yanyan | ... | 09:55 |
| Qiming | the only use of it for us, is to interact with DB | 09:55 |
| Yanyan | yes | 09:55 |
| Qiming | that can be resolved some day I believe | 09:55 |
| Yanyan | so I said after we queried object(cluster, node, policy) back from DB, we don't need context :) | 09:56 |
| Qiming | yes | 09:56 |
| Yanyan | em, if DB don't need it, we can remove it from API layer I guess | 09:56 |
| Qiming | senlin will then operate on behalf of those object owners | 09:57 |
| Yanyan | yes | 09:57 |
| Qiming | that is possible | 09:57 |
| Yanyan | will leave, have a call at 8:00 pm... | 09:57 |
| Qiming | ok | 09:58 |
| *** Yanyan has quit IRC | 10:00 | |
| *** Yanyan has joined #senlin | 10:00 | |
| *** Yanyan has quit IRC | 10:05 | |
| openstackgerrit | Qiming Teng proposed stackforge/senlin: Add user/project/domain to policy objects https://review.openstack.org/202037 | 10:45 |
| *** Qiming has quit IRC | 10:49 | |
| *** openstack has joined #senlin | 11:39 | |
| *** Qiming has joined #senlin | 11:54 | |
| *** Qiming has quit IRC | 12:26 | |
| *** Qiming has joined #senlin | 12:26 | |
| openstackgerrit | Qiming Teng proposed stackforge/senlin: Temporarily unmask nova exception https://review.openstack.org/202088 | 12:41 |
| *** lixinhui_ has joined #senlin | 13:14 | |
| openstackgerrit | Merged stackforge/senlin: Temporarily unmask nova exception https://review.openstack.org/202088 | 13:15 |
| *** jdandrea has joined #senlin | 13:37 | |
| *** lixinhui_ has quit IRC | 14:24 | |
| *** lixinhui_ has joined #senlin | 14:25 | |
| *** Qiming has quit IRC | 16:37 | |
| *** htruta_ has joined #senlin | 21:30 | |
| *** htruta_ has quit IRC | 22:05 | |
| *** jruano has joined #senlin | 22:10 | |
| *** htruta_ has joined #senlin | 22:50 | |
| *** htruta_ has quit IRC | 23:13 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!