| *** jamielennox|away is now known as jamielennox | 00:02 | |
| *** zhurong has joined #openstack-barbican | 00:49 | |
| *** jamielennox is now known as jamielennox|away | 01:00 | |
| *** jamielennox|away is now known as jamielennox | 01:10 | |
| *** liujiong has joined #openstack-barbican | 01:22 | |
| *** hieulq has quit IRC | 01:23 | |
| *** hieulq has joined #openstack-barbican | 01:24 | |
| *** zhurong has quit IRC | 01:29 | |
| *** namnh has joined #openstack-barbican | 01:37 | |
| *** dave-mccowan has joined #openstack-barbican | 01:38 | |
| *** zhurong has joined #openstack-barbican | 02:04 | |
| *** dimtruck is now known as zz_dimtruck | 02:31 | |
| *** zz_dimtruck is now known as dimtruck | 02:52 | |
| *** dimtruck is now known as zz_dimtruck | 03:12 | |
| *** zz_dimtruck is now known as dimtruck | 03:34 | |
| *** dave-mccowan has quit IRC | 03:47 | |
| *** dimtruck is now known as zz_dimtruck | 03:54 | |
| *** zz_dimtruck is now known as dimtruck | 04:16 | |
| *** zhurong has quit IRC | 04:25 | |
| *** zhurong has joined #openstack-barbican | 04:34 | |
| *** dimtruck is now known as zz_dimtruck | 04:50 | |
| *** zz_dimtruck is now known as dimtruck | 05:12 | |
| *** dimtruck is now known as zz_dimtruck | 05:27 | |
| *** jaosorior has joined #openstack-barbican | 06:18 | |
| *** zz_dimtruck is now known as dimtruck | 06:53 | |
| *** zhurong has quit IRC | 06:55 | |
| *** zhurong has joined #openstack-barbican | 06:56 | |
| *** zhurong has quit IRC | 06:57 | |
| *** dimtruck is now known as zz_dimtruck | 07:03 | |
| *** pcaruana has joined #openstack-barbican | 07:05 | |
| *** zz_dimtruck is now known as dimtruck | 07:54 | |
| *** namnh has quit IRC | 07:58 | |
| *** dimtruck is now known as zz_dimtruck | 08:04 | |
| *** salmankhan has joined #openstack-barbican | 08:40 | |
| *** zz_dimtruck is now known as dimtruck | 08:55 | |
| *** dimtruck is now known as zz_dimtruck | 09:05 | |
| *** liujiong has quit IRC | 09:52 | |
| openstackgerrit | Nam Nguyen Hoai proposed openstack/barbican-specs master: Specs rolling upgrade for Barbican https://review.openstack.org/472612 | 09:53 |
|---|---|---|
| *** zhurong has joined #openstack-barbican | 09:54 | |
| *** zz_dimtruck is now known as dimtruck | 09:56 | |
| openstackgerrit | Lingyong Xu proposed openstack/barbican master: Fix html_last_updated_fmt for Python3 https://review.openstack.org/472615 | 09:57 |
| *** namnh has joined #openstack-barbican | 10:03 | |
| *** dimtruck is now known as zz_dimtruck | 10:05 | |
| *** zhurong has quit IRC | 10:06 | |
| namnh | jaosorior, are you free? | 10:13 |
| jaosorior | sure, what's up? | 10:14 |
| namnh | can I discuss with you about rolling upgrade for barbican? | 10:15 |
| namnh | jaosorior, | 10:15 |
| jaosorior | lets do that | 10:15 |
| *** daidv has joined #openstack-barbican | 10:15 | |
| namnh | jaosorior, I've just updated a specs about this. https://review.openstack.org/#/c/472612/ | 10:16 |
| namnh | jaosorior, please take a look at it first | 10:16 |
| jaosorior | ok, let me do that | 10:17 |
| namnh | jaosorior, that would be great if the specs get your opinion about what items we need to do for rolling | 10:18 |
| jaosorior | sure | 10:19 |
| jaosorior | I'm reading the spec right now | 10:19 |
| jaosorior | ok, reading through the spec it looks fine. I mean, it's pretty high level. The real detail is in how we handle the indirection bits (which we could easily mess up) | 10:24 |
| jaosorior | namnh: but it looks good! I think it does cover the overall plan. This doesn't cover yet microversions in Barbican, right? | 10:27 |
| namnh | yes, you are right, however Purpose of the spces is to list items what we need to do for rolling. I am considering about three items. 1 implement OVO - 2. RPC version -3. Using trigger to solve problem during upgrade database | 10:29 |
| jaosorior | namnh: right now we don't have a worker that has a clear distinction to only work with the database. Is that going to be addressed as well? | 10:32 |
| namnh | I have not think about that. currently there are barbican-api and barbican-worker that can interact with db. right | 10:34 |
| namnh | ? | 10:34 |
| jaosorior | yeah | 10:35 |
| jaosorior | both do | 10:35 |
| *** zz_dimtruck is now known as dimtruck | 10:35 | |
| jaosorior | namnh: I guess it's not a big deal, probably the easiest thing would be to introduce OVO for database access and just have both processes use it. | 10:39 |
| jaosorior | wouldn't be as clean as we would like it to be, but at least upgrades wouldn't be that big of a hazzle, which is a huge plus | 10:40 |
| *** dimtruck is now known as zz_dimtruck | 10:45 | |
| namnh | For OVO. in my opinion, implement OVO that depends on the architecture of project. i think OVO is used to modify information from database before sending to agents. For example, when nova-compute want to get information from database via nova-conductor then OVO on nova-condutor will modify this info as the expectation of nova-compute. | 10:45 |
| namnh | but in barbican, it does not have service like nova-compute. | 10:46 |
| namnh | so I am considering whether we need OVO or not. | 10:49 |
| namnh | jaosorior, | 10:50 |
| jaosorior | namnh: so... The nice thing about OVO is the "make_compatible" bit. That bit we could use | 10:51 |
| jaosorior | other than that, to take full advantage of it, we would need to change barbican's architecture to have a worker that's specifically handling database operations | 10:52 |
| jaosorior | I don't think the RPCs are really a problem in Barbican. It's mostly database compatibility. | 10:53 |
| namnh | jaosorior, yead, i understood. let me expand my option about this. OVO have good method: "make_object"compatible", that is very useful in case we need to modify info from database before sending this info to agents. is that right. According to current achitecture of barbican, we dont realy need this method. are you ageed with me? | 10:58 |
| namnh | But the method is useful for the future | 10:58 |
| namnh | so you think that we need to implement OVO for Barbican | 10:59 |
| namnh | is that right? | 10:59 |
| namnh | s/ageed/agree | 11:00 |
| jaosorior | I think it could give some benefits. However, if you think we could achieve the same thing without the "make_compatible" method, I'm actually quite open as to what we use. | 11:01 |
| namnh | I agree with you about OVO is usefull for the future. Let me investigate deeply about the usecase of OVO. | 11:07 |
| namnh | can we jump the next topic (upgrade database) | 11:08 |
| namnh | jaosorior, can we jump the next topic (upgrade database) | 11:08 |
| jaosorior | sure | 11:09 |
| jaosorior | So that's what I thought OVO could be useful for. Being a facade for database operations. Eventually making database upgrade easier. | 11:10 |
| jaosorior | well, not database upgrade, but upgrading barbican nodes, while using the same database. | 11:10 |
| namnh | jaosorior, ok, I agree with you about OVO, i means that we need to think about the strategy when the database can be changed in the future like drop column/table or add column/table. | 11:16 |
| jaosorior | exactly | 11:16 |
| namnh | Currenlty, there are two way to solve this: | 11:16 |
| namnh | 1. Only add database, don't allow delete or alter colume or table like nova or neutron | 11:19 |
| namnh | 2. Using trigger like Keystone and Glance | 11:20 |
| jaosorior | can you ellaborate on option 1? | 11:21 |
| namnh | which do you prefer? | 11:21 |
| namnh | in neutron and nova. they have a rule from Mitaka that don't allow column or table in database. they only allow add column or table from N to (N+1) cycle | 11:24 |
| jaosorior | uhm | 11:24 |
| jaosorior | To be honest I prefer option 2. I rather have a more flexible and readable database, than have such a restriction; even if it involves more code. | 11:25 |
| namnh | that why neutron or nova implemented OVO to modify info database to have suitable one before sending to nova-compute. | 11:27 |
| namnh | for option 2. we will have 3 phases: expand, migrate, contract to upgrade database. I am sure I can implement the three one for barbican. But it have a disadvantages is that difficult to test trigger in database. that's why nova did not use trigger to upgrade database | 11:31 |
| namnh | in my opinion, i prefer option 2 | 11:33 |
| jaosorior | lets do that | 11:33 |
| namnh | ok, I will start to do this on next week. At that time, could you help me to review my patchs as main reviewer. | 11:36 |
| *** zz_dimtruck is now known as dimtruck | 11:36 | |
| jaosorior | sure | 11:36 |
| namnh | jaosorior, thank you so much in advance :D | 11:37 |
| jaosorior | no, thank you for this work :D this surely is very useful stuff | 11:37 |
| namnh | let's jump to final topic. | 11:37 |
| namnh | RPC version. | 11:37 |
| namnh | I implemented POC for RPC version on this patch: https://review.openstack.org/#/c/466247/. do I need to say the overall of this iead? | 11:39 |
| namnh | s/overall/overview | 11:39 |
| jaosorior | I'll figure it out, no worries | 11:40 |
| namnh | so that's 3 topics that I would like to discuss with you. | 11:42 |
| namnh | let me sumary: 1. we will implement OVO -- 2. Using trigger to upgrade database -- 3. RPC version. | 11:43 |
| jaosorior | ~right | 11:43 |
| jaosorior | OK, I'll review the RPC version patch as soon as I can | 11:44 |
| namnh | I think that's 3 items that need to implement first to support rolling upgrade. Do you have any considering? | 11:44 |
| jaosorior | The tricky part will be to test rolling upgrades | 11:45 |
| *** dimtruck is now known as zz_dimtruck | 11:45 | |
| namnh | currently, I don't have any idea about this. Do you have any idea? | 11:46 |
| jaosorior | I'm in the same boat; I don't know if any other projects are successfully testing this. Or will we be the first if we do. | 11:48 |
| *** raildo has joined #openstack-barbican | 11:49 | |
| namnh | jaosorior, ok we will think about this later. :) | 11:51 |
| namnh | jaosorior, I think it is enough for today, I have to leave my office, it's so late in my country | 11:52 |
| namnh | jaosorior, thanks for your time to discuss with me. | 11:52 |
| *** noslzzp has joined #openstack-barbican | 11:54 | |
| jaosorior | sure man, no biggie | 11:54 |
| namnh | :) see you on next week | 11:54 |
| *** namnh has quit IRC | 11:55 | |
| *** cpuga has joined #openstack-barbican | 12:22 | |
| *** cpuga_ has joined #openstack-barbican | 12:30 | |
| *** noslzzp has quit IRC | 12:30 | |
| *** noslzzp has joined #openstack-barbican | 12:31 | |
| *** cpuga has quit IRC | 12:34 | |
| *** salmankhan has quit IRC | 12:35 | |
| *** zz_dimtruck is now known as dimtruck | 12:36 | |
| *** jaosorior has quit IRC | 12:37 | |
| *** catintheroof has joined #openstack-barbican | 12:40 | |
| *** dave-mccowan has joined #openstack-barbican | 12:43 | |
| *** catintheroof has quit IRC | 12:45 | |
| *** dimtruck is now known as zz_dimtruck | 12:46 | |
| *** catintheroof has joined #openstack-barbican | 12:46 | |
| *** noslzzp has quit IRC | 13:16 | |
| *** noslzzp has joined #openstack-barbican | 13:19 | |
| *** zz_dimtruck is now known as dimtruck | 13:37 | |
| *** chlong has joined #openstack-barbican | 13:52 | |
| *** dimtruck is now known as zz_dimtruck | 13:53 | |
| *** jaosorior has joined #openstack-barbican | 13:56 | |
| *** noslzzp_ has joined #openstack-barbican | 14:00 | |
| *** noslzzp has quit IRC | 14:01 | |
| *** zz_dimtruck is now known as dimtruck | 14:10 | |
| *** noslzzp_ has quit IRC | 14:17 | |
| *** salmankhan has joined #openstack-barbican | 14:24 | |
| -openstackstatus- NOTICE: The Gerrit service on review.openstack.org is being restarted now to clear an issue arising from an unanticipated SSH API connection flood | 14:55 | |
| *** jaosorior has quit IRC | 15:09 | |
| *** noslzzp has joined #openstack-barbican | 16:13 | |
| *** pcaruana has quit IRC | 16:34 | |
| *** noslzzp has quit IRC | 17:19 | |
| *** salmankhan has quit IRC | 17:52 | |
| *** noslzzp has joined #openstack-barbican | 17:58 | |
| *** noslzzp has quit IRC | 19:05 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/barbican master: Updated from global requirements https://review.openstack.org/472799 | 20:35 |
| *** salmankhan has joined #openstack-barbican | 21:15 | |
| *** dimtruck is now known as zz_dimtruck | 21:25 | |
| *** raildo has quit IRC | 21:39 | |
| *** cpuga_ has quit IRC | 21:46 | |
| *** salmankhan has quit IRC | 21:56 | |
| *** chlong has quit IRC | 21:58 | |
| *** dave-mccowan has quit IRC | 22:06 | |
| *** dave-mccowan has joined #openstack-barbican | 22:07 | |
| *** catintheroof has quit IRC | 22:42 | |
| *** zz_dimtruck is now known as dimtruck | 23:17 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!