| *** chandan_kumar has joined #openstack-climate | 04:20 | |
| *** chandan_kumar has quit IRC | 04:37 | |
| *** chandan_kumar has joined #openstack-climate | 05:06 | |
| *** ddyachkov has joined #openstack-climate | 05:10 | |
| *** ddyachkov has quit IRC | 05:10 | |
| *** Nikolay_St has joined #openstack-climate | 05:14 | |
| *** DinaBelova_ is now known as DinaBelova | 05:59 | |
| *** chandan_kumar has quit IRC | 06:38 | |
| *** chandan_kumar has joined #openstack-climate | 07:04 | |
| *** DinaBelova is now known as DinaBelova_ | 07:08 | |
| *** saju_m has joined #openstack-climate | 07:15 | |
| *** saju_m has quit IRC | 07:20 | |
| *** saju_m has joined #openstack-climate | 07:21 | |
| *** saju_m has quit IRC | 07:26 | |
| *** saju_m has joined #openstack-climate | 07:27 | |
| *** DinaBelova_ is now known as DinaBelova | 07:31 | |
| *** saju_m has quit IRC | 07:49 | |
| *** chandan_kumar has quit IRC | 08:29 | |
| *** DinaBelova is now known as DinaBelova_ | 08:34 | |
| *** chandan_kumar has joined #openstack-climate | 08:37 | |
| *** saju_m has joined #openstack-climate | 08:45 | |
| openstackgerrit | A change was merged to stackforge/climate: Adding tests for sqlalchemy class https://review.openstack.org/72943 | 08:46 |
|---|---|---|
| *** bauzas has joined #openstack-climate | 09:42 | |
| bauzas | morning all | 10:00 |
| bauzas | DinaBelova_: do you have time for discussing the policy thing ? | 10:23 |
| bauzas | DinaBelova_: I'll give a basic -1 for cosmetic things, but the whole patch deserves a discussion :) | 10:24 |
| Nikolay_St | bauzas: are you here? | 10:25 |
| bauzas | Nikolay_St: yep | 10:25 |
| Nikolay_St | bauzas: hi | 10:26 |
| Nikolay_St | bauzas: question about https://review.openstack.org/#/c/74751 | 10:26 |
| bauzas | Nikolay_St: sure | 10:26 |
| Nikolay_St | bauzas: new exception raised by db api. are you sure they should be in manager.exceptions? | 10:26 |
| bauzas | Nikolay_St: well, that's indeed a good question | 10:27 |
| bauzas | Nikolay_St: at the moment, we have 2 places for defining exceptions | 10:27 |
| bauzas | the global exceptions module and the manager one | 10:27 |
| bauzas | Nikolay_St: the thing is, all the DB calls are made from the manager | 10:28 |
| bauzas | Nikolay_St: so, that needs to put in | 10:28 |
| bauzas | Nikolay_St: but the best would maybe to create a new db.exceptions module and put them in | 10:28 |
| bauzas | that thing would require a minor patch on the API side | 10:29 |
| bauzas | at least with API v1 | 10:29 |
| Nikolay_St | bauzas: create db.exceptions will be the best thing | 10:31 |
| bauzas | ok, amending my comment | 10:31 |
| bauzas | but that requires a little fix | 10:32 |
| Nikolay_St | bauzas: and also we need to check that they will be visible for users | 10:32 |
| bauzas | no, they shouldn't | 10:32 |
| bauzas | DB exceptions should be handled by the API | 10:32 |
| bauzas | but not be served to users, for security reasons | 10:32 |
| Nikolay_St | bauzas: oh, get it | 10:33 |
| bauzas | API should only return 4xx or 5xx codes with basic understandable exceptions | 10:35 |
| bauzas | well, after looking at other projects, they even don't raise specific exceptions, but rather kind of generic HTTP exceptions | 10:35 |
| bauzas | like Forbidden, NotFound, etc. | 10:36 |
| bauzas | with a clear message | 10:36 |
| bauzas | but as I'm doing the API v2, I still need to think about it, and propose a patch on a latter way | 10:36 |
| bauzas | Nikolay_St, DinaBelova_: I'm today focusing on proposing a new patchset for API v2 | 10:37 |
| bauzas | so I can move on the Alembic bp by next week | 10:37 |
| *** DinaBelova_ is now known as DinaBelova | 10:40 | |
| DinaBelova | bauzas, hello :) | 10:42 |
| DinaBelova | wok for new patchset for API v2 :) | 10:42 |
| bauzas | DinaBelova: yup | 10:42 |
| DinaBelova | what type of ideas do you have about policy stuff? | 10:42 |
| DinaBelova | :) | 10:42 |
| bauzas | well, I'm just saying this patch is great, but needs to be discussed ;) | 10:43 |
| DinaBelova | bauzas, sure :) | 10:43 |
| DinaBelova | give me your ideas here or in comments | 10:43 |
| DinaBelova | it's just draft now | 10:43 |
| bauzas | because the problem is that in Openstack there is no good practice in terms of policies | 10:43 |
| bauzas | and Nova/others vs. Keystone is really common | 10:43 |
| DinaBelova | bauzas, frankly speaking - yes | 10:44 |
| DinaBelova | I used Keystone type of policies | 10:44 |
| DinaBelova | because it looks better solution for me | 10:44 |
| DinaBelova | and Keystone policies really do their work | 10:44 |
| DinaBelova | except all others, really :? | 10:44 |
| bauzas | so my feeling is : with the respect of what the guys are awesomely doing on Keystone, as we're being under review, is this a good path to follow something not shared by other teams ? | 10:44 |
| bauzas | by under review, I mean people are glancing at Climate, esp. with incubation | 10:45 |
| DinaBelova | bauzas, speaking about policies and Climate at all | 10:45 |
| bauzas | that's a general concern, I assume | 10:45 |
| DinaBelova | I believe we should take best practices | 10:45 |
| DinaBelova | from whatever we can | 10:45 |
| DinaBelova | policies just should work | 10:45 |
| bauzas | DinaBelova: ok, will look at your patch carefully :) | 10:46 |
| DinaBelova | bauzas, I will continue working on it today, so there will be some changes, surely | 10:46 |
| bauzas | DinaBelova: as said, I left the Pecan thing for a long moment, I need to dig into it | 10:46 |
| DinaBelova | but common idea will be the same | 10:46 |
| DinaBelova | bauzas, thanks | 10:46 |
| DinaBelova | bauzas, also I just wanted to ask you some question: when reasonably are you planning to complete working on API v2? | 11:05 |
| bauzas | DinaBelova: I hope by end of the week for the unittests | 11:06 |
| bauzas | that's the main part missing | 11:06 |
| DinaBelova | cool! | 11:06 |
| DinaBelova | it's great | 11:06 |
| DinaBelova | thanks for your efforts :) | 11:06 |
| bauzas | some bugs could still be present | 11:06 |
| bauzas | well, I'm not proud of it, I had no time to work on the patch the 3 previous days | 11:06 |
| bauzas | yesterday, I was ooo | 11:07 |
| bauzas | day-off | 11:07 |
| DinaBelova | bauzas, we'll test it anyway, so that's not a problem | 11:07 |
| DinaBelova | don't worry :) | 11:07 |
| openstackgerrit | Dina Belova proposed a change to stackforge/climate: Fix issue with new python-keystoneclient https://review.openstack.org/74376 | 11:17 |
| bauzas | DinaBelova: dammit, these bytecode files are getting me mad | 11:33 |
| bauzas | DinaBelova: I need to swipe them | 11:33 |
| bauzas | DinaBelova: because of the recent oslo.messaging move :) | 11:33 |
| bauzas | DinaBelova: how do you manage this ? by hand ? | 11:34 |
| DinaBelova | yes | 11:34 |
| bauzas | damn | 11:35 |
| DinaBelova | frankly speaking I just used clean VM :D | 11:35 |
| DinaBelova | that was really radical type of getting rid of them :D | 11:35 |
| bauzas | as the tox venvs are actually egglinks to source code, it generates pyc files on my own machine | 11:35 |
| bauzas | I think I'll just modify the rsync script I'm using | 11:36 |
| bauzas | by saying to not transfer the bytecode files | 11:36 |
| DinaBelova | find . -name \*.pyc -delete ? | 11:36 |
| DinaBelova | :D | 11:36 |
| bauzas | well, -name "*.pyc" please | 11:36 |
| bauzas | that's the most errorproof syntax | 11:37 |
| bauzas | and the one recommended ;) | 11:37 |
| DinaBelova | ;d | 11:37 |
| bauzas | DinaBelova: are you ok with the fact I'll provide a climate-manage db_sync (or something like that) within the alembic bp ? | 11:43 |
| bauzas | DinaBelova: we need to get rid of the DB tables creation from within the manager | 11:44 |
| DinaBelova | bauzas, sure, it's good idea - although why not having two commits? | 11:50 |
| DinaBelova | with that change before alembic | 11:50 |
| bauzas | ok, will do like that | 11:50 |
| bauzas | both will be attached to the same bp | 11:50 |
| DinaBelova | we'll just merge it and that's it | 11:50 |
| DinaBelova | ok | 11:51 |
| openstackgerrit | A change was merged to stackforge/climate: Fix issue with new python-keystoneclient https://review.openstack.org/74376 | 11:56 |
| SergeyLukjanov | bauzas, heh, I'm using ind ./savanna -type f -name '*.pyc' -exec rm {} \; | 12:15 |
| *** pafuent has joined #openstack-climate | 12:25 | |
| *** pafuent has left #openstack-climate | 12:25 | |
| *** pafuent has joined #openstack-climate | 12:25 | |
| *** chmartinez has joined #openstack-climate | 12:31 | |
| bauzas | SergeyLukjanov: thanks, but I'm fine with find, no worries (and btw. it's better to use -delete flag) | 12:39 |
| SergeyLukjanov | bauzas, I'm not sure that it works fine on all platforms | 12:45 |
| bauzas | AFAIK, it does work on Ubuntu/Debian, RHEL/CentOS and BSD | 12:57 |
| bauzas | SergeyLukjanov: :) | 12:57 |
| *** casanch1 has joined #openstack-climate | 12:57 | |
| pafuent | bauzas: Hi. Regarding your comment about api.service modified to handling DB exceptions | 13:04 |
| bauzas | pafuent: sure ? | 13:05 |
| pafuent | bauzas: That should be done in api.utils right? | 13:05 |
| bauzas | uh hold on | 13:05 |
| bauzas | yep, you're right | 13:06 |
| bauzas | in the route() method | 13:06 |
| bauzas | if I remember correctlt | 13:06 |
| pafuent | bauzas: Yes | 13:06 |
| pafuent | bauzas: Thanks | 13:06 |
| bauzas | pafuent: the idea is to handle and obfuscate the DB exceptions | 13:06 |
| pafuent | bauzas: Like ClimateException, right? | 13:07 |
| bauzas | pafuent: hold on | 13:14 |
| pafuent | bauzas: Ok | 13:14 |
| bauzas | pafuent: https://github.com/stackforge/climate/blob/master/climate/api/utils.py#L82 | 13:15 |
| bauzas | pafuent: I'm just saying that if you don't modify this line, it goes into an unexpected error | 13:15 |
| bauzas | pafuent: the idea is to look at also db.exceptions, but remove the traceback info | 13:17 |
| bauzas | for security reasons | 13:17 |
| pafuent | bauzas: Ok, so DB exceptions should be handled by render_error_message | 13:18 |
| pafuent | bauzas: Like the exceptions in manager and common ones | 13:18 |
| *** chmartinez has quit IRC | 13:19 | |
| bauzas | pafuent: exactly, but the subtility is that there is possibility to expose tables information, and that must be hidden | 13:19 |
| pafuent | bauzas: Ok | 13:20 |
| bauzas | pafuent: I don't want having a message like "duplicate entry 'toto' on table 'foo'" | 13:20 |
| bauzas | pafuent: presented to the user | 13:20 |
| pafuent | bauzas: I'll remove the message and retain the name of the exception | 13:21 |
| bauzas | I'm fine with it | 13:28 |
| casanch1 | swann: did you see my comment in this review: https://review.openstack.org/#/c/73363/ | 13:31 |
| *** chmartinez has joined #openstack-climate | 13:48 | |
| *** bauzas1 has joined #openstack-climate | 13:52 | |
| *** bauzas has quit IRC | 13:59 | |
| *** Nikolay_St has quit IRC | 13:59 | |
| *** YorikSar has quit IRC | 13:59 | |
| *** DinaBelova has quit IRC | 13:59 | |
| *** jd__ has quit IRC | 13:59 | |
| *** DinaBelova has joined #openstack-climate | 14:01 | |
| *** jd__ has joined #openstack-climate | 14:01 | |
| *** saju_m has quit IRC | 14:11 | |
| chmartinez | hello all | 14:15 |
| chmartinez | I'm trying to learn about climate-nova.. Does anyone in here knows about how it works, or where can I find information about it? | 14:15 |
| DinaBelova | chmartinez, hello | 14:15 |
| DinaBelova | climate-nova is just repo with nova-related things (like additional nova filters or additional nova api extensions) | 14:15 |
| DinaBelova | they are used for correct climate work with Nova resources | 14:15 |
| DinaBelova | like filtering VMs to run on reserved host when lease starts | 14:15 |
| *** chmartinez_ has joined #openstack-climate | 14:15 | |
| DinaBelova | chmartinez, you here? | 14:15 |
| chmartinez_ | yes | 14:15 |
| chmartinez_ | sorry... Bad connection :( | 14:15 |
| DinaBelova | [18:06:14] <DinaBelova> climate-nova is just repo with nova-related things (like additional nova filters or additional nova api extensions) | 14:15 |
| DinaBelova | [18:06:31] <DinaBelova> they are used for correct climate work with Nova resources | 14:15 |
| DinaBelova | [18:06:52] <DinaBelova> like filtering VMs to run on reserved host when lease starts | 14:15 |
| DinaBelova | so to use these filters/api extensions you only need to set them in nova.conf file after climate-nova installation | 14:16 |
| DinaBelova | like in this example | 14:16 |
| DinaBelova | https://github.com/stackforge/climate-nova/blob/master/etc/nova.conf.example | 14:16 |
| chmartinez_ | nova.conf.examples.. yes | 14:16 |
| *** chmartinez has quit IRC | 14:16 | |
| DinaBelova | extensions written in climate-nova, for example, are used for VM reservation | 14:16 |
| DinaBelova | there are two of them now - to allow reserving VM in user-transparent way | 14:16 |
| *** Nikolay_St has joined #openstack-climate | 14:16 | |
| *** YorikSar has joined #openstack-climate | 14:16 | |
| DinaBelova | like openstack server create ... --hint lease_params="..." ... | 14:16 |
| DinaBelova | and to make all instance creation request reservations by default | 14:16 |
| DinaBelova | so Default_reservation extension was written for Intel use case - where in dev cloud every VM should be reserved for 1 month | 14:16 |
| *** saju_m has joined #openstack-climate | 14:16 | |
| DinaBelova | simply climate-nove does nothing itself - but it's integrated to Nova API / Nova Scheduler to use Climate specific things | 14:16 |
| chmartinez_ | oo.. I see.. | 14:16 |
| chmartinez_ | Do you know if some others modules, like Keystone, have this feature? | 14:16 |
| DinaBelova | it depends on what do you want to do | 14:16 |
| DinaBelova | almost every entry point in every OS service | 14:16 |
| DinaBelova | is configurable | 14:16 |
| chmartinez_ | I'm thinking about the tenant reservation bp.. and how to lease the resources associated to the tenants.. | 14:16 |
| DinaBelova | that should be investigated really | 14:16 |
| chmartinez_ | for instance.. when I create the new "special" tenant, how can intercept that call? | 14:16 |
| chmartinez_ | probably that tenant creation will have some extra parameters that we would use for the feature... I just thinking at loud.. | 14:16 |
| DinaBelova | chmartinez_, you're welcome :) | 14:16 |
| chmartinez_ | :) | 14:16 |
| chmartinez_ | haha | 14:16 |
| chmartinez_ | thanks for the info... I will see what I can find.. | 14:17 |
| DinaBelova | chmartinez_, i dunno for sure, but that might be managed by middleware... | 14:19 |
| *** Nikolay_St has quit IRC | 14:20 | |
| *** YorikSar has quit IRC | 14:20 | |
| DinaBelova | although I'm not sure that list of middlewares is changeable | 14:20 |
| chmartinez_ | OS middlewares.. I see... | 14:20 |
| chmartinez_ | I should read about that... | 14:21 |
| chmartinez_ | forgive me, I just getting started with all of this and there is a lot of things that I don't know :S | 14:21 |
| DinaBelova | chmartinez_, although I'm two years here, I also don't know what to say you about this situation | 14:22 |
| pafuent | bauzas1: This is a sample of the climateclient output | 14:23 |
| pafuent | bauzas1: ClimateDBNotFound: A database error occurred | 14:23 |
| pafuent | bauzas1: Is it ok? | 14:24 |
| DinaBelova | chmartinez_, I meant that maybe you may add your functionality to middleware that's set in keystone-paste.ini file | 14:24 |
| bauzas1 | chmartinez_: I don't understand the thing with Keystone | 14:24 |
| DinaBelova | chmartinez_, but frankly speaking I'm really not sure it's a good idea | 14:25 |
| bauzas1 | pafuent: I'm OK with it | 14:25 |
| bauzas1 | chmartinez_, DinaBelova: which BP are we talking about ? | 14:25 |
| DinaBelova | https://blueprints.launchpad.net/climate/+spec/tenant-reservation-concept | 14:25 |
| DinaBelova | bauzas1, it's also about Intel use case | 14:25 |
| DinaBelova | I mean its further development | 14:26 |
| DinaBelova | even after notification stuff | 14:26 |
| pafuent | bauzas1: Thanks | 14:26 |
| DinaBelova | bauzas1, so here is really discussible moment how to make Keystone behaviour manageable | 14:26 |
| DinaBelova | and configurable | 14:26 |
| DinaBelova | for Nova we have API exts, filters | 14:27 |
| DinaBelova | many things to modify and many entry points to go to | 14:27 |
| DinaBelova | for Keystone situation is not so simple | 14:27 |
| *** saju_m has quit IRC | 14:27 | |
| bauzas1 | DinaBelova: missed that one | 14:28 |
| DinaBelova | bauzas1, it was created some time ago, but it's still in discussion/drafting state 'cause of Keystone specific thngs | 14:29 |
| DinaBelova | like where should I go not to modify Keystone itself but somehow hack its behaviour? | 14:29 |
| *** chandan_kumar has quit IRC | 14:29 | |
| DinaBelova | as I said, for Nova we just can do that without great probplems | 14:29 |
| DinaBelova | problems* | 14:30 |
| bauzas1 | DinaBelova: I'm sorry, but you state that a new tenant should get a lease automatically | 14:30 |
| bauzas1 | DinaBelova: why ? | 14:30 |
| DinaBelova | bauzas1, not all of them | 14:30 |
| DinaBelova | not all new | 14:30 |
| bauzas1 | DinaBelova: and which default values ? | 14:30 |
| DinaBelova | but ones with some specific mark on it | 14:30 |
| chmartinez_ | bauzas1: that is a thing that I will find out | 14:31 |
| DinaBelova | bauzas1, I think here we should ask Intel guys about that | 14:31 |
| DinaBelova | :) | 14:31 |
| chmartinez_ | bauzas1: I will ask Joel about that | 14:31 |
| DinaBelova | chmartinez_, ok, cause that's important | 14:31 |
| bauzas1 | DinaBelova: mmm | 14:31 |
| DinaBelova | cause now it's only idea - discussoble one | 14:31 |
| DinaBelova | discussible* | 14:31 |
| DinaBelova | of how that might be used/implemented/whatever | 14:32 |
| bauzas1 | DinaBelova: chmartinez_: well, I think this BP should be discussed in ML | 14:32 |
| bauzas1 | so people could contribute on it | 14:32 |
| bauzas1 | that's a big one | 14:32 |
| DinaBelova | chmartinez_, may you write mail to dev-ml about that | 14:32 |
| DinaBelova | with all use cases, etc | 14:32 |
| bauzas1 | yes, we need to think about the rationale | 14:33 |
| chmartinez_ | DinaBelova: OK | 14:33 |
| DinaBelova | and with some additional info how do you propose to do that, etc. | 14:33 |
| bauzas1 | that BP is bigger enough to go into a wiki page | 14:33 |
| bauzas1 | and discuss it thru etherpad | 14:33 |
| DinaBelova | cause now, as said, that's idea with much blank moments | 14:33 |
| *** Nikolay_St has joined #openstack-climate | 14:33 | |
| *** YorikSar has joined #openstack-climate | 14:33 | |
| DinaBelova | bauzas1, ++ | 14:33 |
| bauzas1 | like how we did with PR and VR usecases | 14:34 |
| DinaBelova | bauzas1, yes, think so | 14:34 |
| bauzas1 | I totally missed it ... :) | 14:34 |
| DinaBelova | chmartinez_, ok with that? | 14:34 |
| bauzas1 | I see it's targeted for 0.2 | 14:34 |
| bauzas1 | woah | 14:34 |
| DinaBelova | 0.2.x :) | 14:34 |
| DinaBelova | not 0.2.0 :) | 14:34 |
| DinaBelova | :D | 14:34 |
| chmartinez_ | DinaBelova: yes! I will write an email to the ML with this topic | 14:34 |
| bauzas1 | well, if the Intel guys do have time, I'm fine :D | 14:34 |
| DinaBelova | chmartinez_, cool, thanks :) | 14:35 |
| bauzas1 | chmartinez_: thanks, will contribute to it | 14:35 |
| DinaBelova | bauzas1, it will be implemented right when it'll be implemented | 14:35 |
| bauzas1 | from my pov, there are 2 concerns with Climate | 14:35 |
| DinaBelova | and all of us will take part | 14:35 |
| bauzas1 | 1. People could ask for leases | 14:35 |
| bauzas1 | 2. Openstack could use Climate for performing tasks in time | 14:35 |
| bauzas1 | in a timely manner I mean | 14:36 |
| bauzas1 | there is a big concern I'm handling with Gantt people | 14:36 |
| bauzas1 | that's why I've been decomissionned from Climate to Gantt these previous days | 14:36 |
| bauzas1 | I'm taking the point | 14:36 |
| DinaBelova | bauzas1, I see that and sometimes try to participate.... they have much unrelated discussions :( | 14:36 |
| DinaBelova | that make me crazy | 14:37 |
| bauzas1 | DinaBelova: don't worry, I'm on it | 14:37 |
| bauzas1 | DinaBelova: we definitely need to split ourselves in various areas | 14:37 |
| DinaBelova | :D | 14:37 |
| bauzas1 | DinaBelova: the good news is that now, many people know Climate | 14:37 |
| bauzas1 | and they look at it | 14:37 |
| bauzas1 | especially the Solver scheduler subteam | 14:38 |
| DinaBelova | bauzas1, yes, I also tried to post links, etc. | 14:38 |
| DinaBelova | bauzas1, yes | 14:38 |
| bauzas1 | DinaBelova: saw that | 14:38 |
| bauzas1 | DinaBelova: but as said, I'll contribute to Gantt | 14:38 |
| bauzas1 | DinaBelova: I definitely think Gantt could help Climate later on | 14:38 |
| DinaBelova | think so, yes | 14:38 |
| bauzas1 | DinaBelova: and I also definitely think that Climate could help Gantt | 14:38 |
| bauzas1 | the scheduling placement decision is made within the plugins now | 14:39 |
| bauzas1 | that shall be done on a separate Climate service | 14:39 |
| DinaBelova | bauzas1, really via resource managing services, yes | 14:40 |
| bauzas1 | exactly | 14:40 |
| bauzas1 | so, from my POV, virtual instances rely on a Nova hack for placement decisions and deferred booting | 14:40 |
| bauzas1 | that should be managed thanks to a call like this : | 14:41 |
| bauzas1 | Nova (boot) -> Climate(lease) -> Gantt (scheduling) -> Climate -> Nova | 14:41 |
| DinaBelova | ideally - yes, smth like that | 14:41 |
| bauzas1 | because on a deferred way, only Climate knows the future capacity | 14:41 |
| DinaBelova | although that needs to be discussed (i mean just list all pros/cons) | 14:42 |
| bauzas1 | Nova can't assess that the host he picked for the shelving instance will have enough capacity when the lease will start | 14:42 |
| bauzas1 | you got my point ? | 14:42 |
| bauzas1 | for a POC, that's great | 14:42 |
| DinaBelova | yes | 14:43 |
| bauzas1 | but we should hook into Nova much earlier in the booting process | 14:43 |
| bauzas1 | but that requires Nova's approval | 14:43 |
| bauzas1 | and here why I'm acting as evangelist :) | 14:43 |
| bauzas1 | I saw you mentioned Mistral | 14:44 |
| bauzas1 | why not, or Taskflow directly | 14:44 |
| DinaBelova | where exactly mentioned? :) | 14:44 |
| DinaBelova | :D | 14:45 |
| bauzas1 | in the mentioned BP | 14:45 |
| DinaBelova | yes, but that was really Joel, as I remember | 14:45 |
| DinaBelova | anyway | 14:45 |
| DinaBelova | using workflows looks good | 14:45 |
| DinaBelova | but Mistral now is only Mirantis initiative and is not used nowhere | 14:45 |
| DinaBelova | although it's distributed, etc. | 14:46 |
| DinaBelova | as TaskFlow is used in Cinder | 14:46 |
| DinaBelova | so it's accepted to OS technologies stack | 14:46 |
| SergeyLukjanov | taskflow is under oslo program now | 14:46 |
| DinaBelova | SergeyLukjanov, yes, I remember letter in ML | 14:47 |
| DinaBelova | about some new added repos there | 14:47 |
| DinaBelova | so if we'll use some kind of workflows in the *nearest* future - that'll be Taskflow now, but potentially Mistral looks better, imo | 14:48 |
| DinaBelova | *potentially* | 14:48 |
| bauzas1 | DinaBelova: +1 | 14:48 |
| bauzas1 | DinaBelova: the transactional workflow should be handled first in Climate | 14:48 |
| DinaBelova | I believe so, yes | 14:48 |
| bauzas1 | DinaBelova: even if I'm thinking it's worth using an API | 14:48 |
| DinaBelova | we'll look on how to do that anyway | 14:49 |
| bauzas1 | to do that what ? | 14:49 |
| bauzas1 | :D | 14:49 |
| bauzas1 | create a lease upon tenant creation ? | 14:49 |
| DinaBelova | bauzas1, that also | 14:50 |
| DinaBelova | I was speaking about workflows in climate using taskflow/mistral | 14:50 |
| bauzas1 | DinaBelova: workflows are something we thought about it since we spoke about Climate :p | 14:51 |
| DinaBelova | I mean potentionally *using taskflow/mistral* | 14:51 |
| bauzas1 | DinaBelova: yuy | 14:52 |
| DinaBelova | :) | 14:52 |
| bauzas1 | I like the "potentionally" :D | 14:52 |
| bauzas1 | remember the with clauses we put in the plugin code ;) | 14:52 |
| DinaBelova | :D:D:D | 14:52 |
| bauzas1 | well, that doesn't help much :) | 14:53 |
| bauzas1 | we need to think about baby steps | 14:53 |
| bauzas1 | if we speak about Keystone, what kind of Keystone object should/would be deferred upon lease start ? | 14:54 |
| DinaBelova | yeeeeah, that's question, that needs answers right after full list of use cases and user stories | 14:54 |
| bauzas1 | exactly :) | 14:56 |
| bauzas1 | and here is why the email thread :) | 14:56 |
| chmartinez_ | first time writing emails to this mailing list.. Any advices? :) | 14:59 |
| bauzas1 | say hi :D | 15:02 |
| chmartinez_ | hahaa | 15:02 |
| bauzas1 | nah, don't worry, you can take example on the previous threads we opened | 15:03 |
| bauzas1 | don't forget [climate] in the subject please | 15:03 |
| chmartinez_ | yes | 15:03 |
| bauzas1 | just say your motivation | 15:03 |
| bauzas1 | why you think it's important | 15:03 |
| bauzas1 | explain your usecases | 15:03 |
| chmartinez_ | Where can I find one of those threads? | 15:03 |
| bauzas1 | search the ML | 15:03 |
| bauzas1 | you don't get it ? | 15:03 |
| bauzas1 | if not, you can search thru google | 15:04 |
| chmartinez_ | I just suscribed | 15:04 |
| chmartinez_ | OK | 15:04 |
| bauzas1 | all of the threads are logged | 15:04 |
| bauzas1 | and you do have archives | 15:04 |
| chmartinez_ | found it! thanks | 15:05 |
| *** YorikSar has quit IRC | 15:09 | |
| *** YorikSar has joined #openstack-climate | 15:09 | |
| *** chmartinez_ has quit IRC | 15:16 | |
| *** chmartinez has joined #openstack-climate | 15:20 | |
| *** DinaBelova is now known as DinaBelova_ | 15:55 | |
| *** DinaBelova_ is now known as DinaBelova | 15:56 | |
| openstackgerrit | Pablo Andres Fuente proposed a change to stackforge/climate: Adding/Handling DB specific exceptions https://review.openstack.org/74751 | 16:26 |
| *** DinaBelova is now known as DinaBelova_ | 16:31 | |
| *** bauzas1 has quit IRC | 16:46 | |
| *** DinaBelova_ is now known as DinaBelova | 17:12 | |
| *** bauzas has joined #openstack-climate | 17:32 | |
| *** saju_m has joined #openstack-climate | 17:33 | |
| *** saju_m has quit IRC | 17:46 | |
| *** saju_m has joined #openstack-climate | 18:09 | |
| *** saju_m has quit IRC | 18:17 | |
| *** saju_m has joined #openstack-climate | 18:21 | |
| *** saju_m has quit IRC | 18:28 | |
| *** saju_m has joined #openstack-climate | 18:32 | |
| pafuent | bauzas: Are you around? | 19:22 |
| pafuent | bauzas: If you are around, Could you please take a look at https://review.openstack.org/#/c/74751/? | 19:36 |
| pafuent | bauzas: Maybe I could fix any comment in the next 1h 30m | 19:36 |
| DinaBelova | pafuent, please don't worry - if you'll have no time and Sylvain will find smth small, I'll fix it myself without any author changing | 19:55 |
| DinaBelova | and we'll merge it/whatever | 19:55 |
| DinaBelova | pafuent, btw have a good luck tomorrow :) | 19:55 |
| pafuent | DinaBelova: Ok, thanks. | 19:56 |
| pafuent | DinaBelova: Which is the deadline for 2.0? | 20:04 |
| DinaBelova | pafuentŠ± 2.0.0 date is not decided yet - I planned to define some draft version on tomorrow meeting | 20:05 |
| pafuent | DinaBelova: Ok | 20:05 |
| DinaBelova | anyway, 0.1.1 is estimated to midddle of March | 20:06 |
| DinaBelova | so 0.2.0 will be in best case just before summit | 20:06 |
| pafuent | DinaBelova: Ok | 20:07 |
| pafuent | DinaBelova: I just added a 'Merged' for the devstack integration in https://etherpad.openstack.org/p/climate-incubation-status | 20:09 |
| DinaBelova | pafuent, thanks :) | 20:10 |
| pafuent | bauzas: Are you around? | 20:19 |
| bauzas | pafuent: yup | 20:20 |
| pafuent | bauzas: It's regarding https://review.openstack.org/#/c/74751/ | 20:21 |
| bauzas | pafuent: yup, looking at it now | 20:21 |
| pafuent | bauzas: Ok. Thanks | 20:22 |
| pafuent | bauzas: And another thing... | 20:24 |
| pafuent | bauzas: I know I'm insistent with this, but I managed to get a working version of db migrations with alembic. Are you ok if I upload the patch? | 20:24 |
| bauzas | pafuent: yup ? | 20:24 |
| bauzas | pafuent: ^^ | 20:24 |
| bauzas | pafuent: of course ok | 20:25 |
| bauzas | pafuent: but there is another concern I'll address about db synchronization on a separate patch | 20:25 |
| pafuent | bauzas: Ok, no problem. | 20:26 |
| bauzas | I just need to leave, talk to you tomorrow | 20:28 |
| bauzas | pafuent: btz | 20:28 |
| bauzas | pafuent: bye | 20:28 |
| pafuent | bauzas: Bye | 20:28 |
| openstackgerrit | Pablo Andres Fuente proposed a change to stackforge/climate: Support for DB migrations using Alembic https://review.openstack.org/75181 | 20:33 |
| *** chmartinez has quit IRC | 20:52 | |
| *** bauzas has quit IRC | 21:05 | |
| *** Nikolay_St has quit IRC | 21:05 | |
| *** DinaBelova has quit IRC | 21:05 | |
| *** saju_m has quit IRC | 21:05 | |
| *** jd__ has quit IRC | 21:05 | |
| *** f_rossigneux has quit IRC | 21:05 | |
| *** YorikSar has quit IRC | 21:05 | |
| *** pafuent has quit IRC | 21:05 | |
| *** openstackgerrit has quit IRC | 21:05 | |
| *** SergeyLukjanov has quit IRC | 21:05 | |
| *** swann has quit IRC | 21:05 | |
| *** casanch1 has quit IRC | 21:05 | |
| *** f_rossigneux has joined #openstack-climate | 21:07 | |
| *** swann has joined #openstack-climate | 21:07 | |
| *** SergeyLukjanov has joined #openstack-climate | 21:07 | |
| *** openstackgerrit has joined #openstack-climate | 21:07 | |
| *** pafuent has joined #openstack-climate | 21:07 | |
| *** casanch1 has joined #openstack-climate | 21:07 | |
| *** DinaBelova has joined #openstack-climate | 21:07 | |
| *** jd__ has joined #openstack-climate | 21:07 | |
| *** YorikSar has joined #openstack-climate | 21:07 | |
| *** saju_m has joined #openstack-climate | 21:07 | |
| *** pafuent has left #openstack-climate | 21:08 | |
| *** bauzas has joined #openstack-climate | 21:14 | |
| *** Nikolay_St has joined #openstack-climate | 21:14 | |
| *** bauzas has quit IRC | 21:26 | |
| *** Nikolay_St has quit IRC | 21:26 | |
| *** DinaBelova has quit IRC | 21:26 | |
| *** saju_m has quit IRC | 21:26 | |
| *** jd__ has quit IRC | 21:26 | |
| *** f_rossigneux has quit IRC | 21:26 | |
| *** YorikSar has quit IRC | 21:26 | |
| *** openstackgerrit has quit IRC | 21:26 | |
| *** SergeyLukjanov has quit IRC | 21:26 | |
| *** swann has quit IRC | 21:26 | |
| *** casanch1 has quit IRC | 21:26 | |
| *** Nikolay_St has joined #openstack-climate | 22:06 | |
| *** f_rossigneux has joined #openstack-climate | 22:06 | |
| *** swann has joined #openstack-climate | 22:06 | |
| *** SergeyLukjanov has joined #openstack-climate | 22:06 | |
| *** DinaBelova_ has joined #openstack-climate | 22:06 | |
| *** jd__ has joined #openstack-climate | 22:06 | |
| *** YorikSar has joined #openstack-climate | 22:06 | |
| *** Nikolay_St has quit IRC | 22:32 | |
| *** DinaBelova_ has quit IRC | 22:33 | |
| *** jd__ has quit IRC | 22:33 | |
| *** f_rossigneux has quit IRC | 22:33 | |
| *** YorikSar has quit IRC | 22:33 | |
| *** SergeyLukjanov has quit IRC | 22:33 | |
| *** swann has quit IRC | 22:33 | |
| *** openstackgerrit has joined #openstack-climate | 22:36 | |
| *** Nikolay_St has joined #openstack-climate | 22:36 | |
| *** f_rossigneux has joined #openstack-climate | 22:36 | |
| *** swann has joined #openstack-climate | 22:36 | |
| *** SergeyLukjanov has joined #openstack-climate | 22:36 | |
| *** DinaBelova_ has joined #openstack-climate | 22:36 | |
| *** jd__ has joined #openstack-climate | 22:36 | |
| *** YorikSar has joined #openstack-climate | 22:36 | |
| *** Nikolay_St has quit IRC | 22:46 | |
| *** DinaBelova_ has quit IRC | 22:46 | |
| *** jd__ has quit IRC | 22:46 | |
| *** f_rossigneux has quit IRC | 22:46 | |
| *** openstackgerrit has quit IRC | 22:46 | |
| *** YorikSar has quit IRC | 22:46 | |
| *** SergeyLukjanov has quit IRC | 22:46 | |
| *** swann has quit IRC | 22:46 | |
| *** openstackgerrit has joined #openstack-climate | 22:47 | |
| *** Nikolay_St has joined #openstack-climate | 22:47 | |
| *** YorikSar has joined #openstack-climate | 22:47 | |
| *** jd__ has joined #openstack-climate | 22:47 | |
| *** DinaBelova_ has joined #openstack-climate | 22:47 | |
| *** SergeyLukjanov has joined #openstack-climate | 22:47 | |
| *** swann has joined #openstack-climate | 22:47 | |
| *** f_rossigneux has joined #openstack-climate | 22:47 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!