| *** tosky has quit IRC | 00:15 | |
| *** hoonetorg has quit IRC | 01:06 | |
| *** hoonetorg has joined #openstack-trove | 01:20 | |
| *** sapd1 has joined #openstack-trove | 01:41 | |
| *** sapd1 has quit IRC | 03:41 | |
| openstackgerrit | Lingxian Kong proposed openstack/trove master: Fix upgrading instance datastore version https://review.opendev.org/761465 | 06:22 |
|---|---|---|
| *** samueldmq has quit IRC | 08:37 | |
| *** andrein has quit IRC | 08:37 | |
| *** coreycb has quit IRC | 08:38 | |
| *** coreycb has joined #openstack-trove | 08:52 | |
| *** samueldmq has joined #openstack-trove | 08:52 | |
| *** andrein has joined #openstack-trove | 08:53 | |
| *** andrein has quit IRC | 09:11 | |
| *** samueldmq has quit IRC | 09:12 | |
| *** andrein has joined #openstack-trove | 09:13 | |
| *** samueldmq has joined #openstack-trove | 09:14 | |
| *** spatel has joined #openstack-trove | 09:42 | |
| *** spatel has quit IRC | 09:47 | |
| *** e0ne has joined #openstack-trove | 09:50 | |
| *** rcernin has joined #openstack-trove | 09:54 | |
| *** rcernin has quit IRC | 10:01 | |
| *** e0ne has quit IRC | 10:30 | |
| *** e0ne has joined #openstack-trove | 10:33 | |
| *** e0ne has quit IRC | 10:38 | |
| *** e0ne has joined #openstack-trove | 10:56 | |
| *** sapd1 has joined #openstack-trove | 11:13 | |
| *** e0ne has quit IRC | 11:26 | |
| *** tosky has joined #openstack-trove | 12:09 | |
| *** __ministry1 has joined #openstack-trove | 12:49 | |
| *** sapd1 has quit IRC | 12:51 | |
| *** sapd1 has joined #openstack-trove | 13:22 | |
| *** __ministry1 has quit IRC | 13:22 | |
| *** e0ne has joined #openstack-trove | 17:07 | |
| *** sapd1 has quit IRC | 17:35 | |
| *** e0ne has quit IRC | 18:18 | |
| *** rcernin has joined #openstack-trove | 20:57 | |
| *** rcernin has quit IRC | 21:21 | |
| *** rcernin has joined #openstack-trove | 21:21 | |
| lxkong | sorrison, may i know have you successfully run trove functional test (i.e. the command `tox -e trovestack gate-tests`) before? | 21:49 |
| sorrison | no haven't looked into that, I'm using an older version of tempest that I know works for our current ussuri install so I can ensure compatibility with master | 21:51 |
| *** lxkong has quit IRC | 22:39 | |
| *** lxkong_ has joined #openstack-trove | 22:39 | |
| *** lxkong_ is now known as lxkong | 22:40 | |
| openstackgerrit | Merged openstack/trove master: Fix upgrading instance datastore version https://review.opendev.org/761465 | 22:47 |
| openstackgerrit | Lingxian Kong proposed openstack/trove stable/victoria: Fix edit instance action return code https://review.opendev.org/761843 | 23:01 |
| openstackgerrit | Sam Morrison proposed openstack/trove master: Pass availability zone through to volume creation. https://review.opendev.org/761250 | 23:01 |
| sorrison | Hi lxkong, just wondering what the difference is between ACTIVE status and the new HEALTHY status? | 23:12 |
| lxkong | active means the db service is running (container is running), healthy means the db service is functional | 23:12 |
| lxkong | sometimes container is running but function is broken | 23:13 |
| sorrison | so what would ACTIVE mean to a user? it's broken? | 23:13 |
| lxkong | active is inherited from the previous version, most of time, it meant the vm is running | 23:14 |
| sorrison | yeah I'm still just a little confused about the 2 states that would indicate the instance is good | 23:16 |
| sorrison | I thought active meant the service was functional | 23:17 |
| sorrison | from a users point of view they don't care about whether container is running etc. all they care about is if the service is functional and if ACTIVE means it's not functional it's a little misleading I think | 23:19 |
| sorrison | It seems like the status is being used for 2 things. Maybe it should be slit up like octavia provisioning status and operating status? | 23:20 |
| sorrison | or just remove the HEALTHY status and make ACTIVE mean the service is functional and if it's not functional make it something like PENDING or ERROR etc. ? | 23:21 |
| lxkong | let me think about it, HEALTHY status was introduced for some reason, but i forgot what was that. | 23:26 |
| lxkong | provisioning status and operating status is good idea | 23:27 |
| lxkong | the instance status transition in trove was badly designed | 23:27 |
| lxkong | if you take a look at how trove gets the instance status | 23:27 |
| lxkong | it's implemented by mixing db service status, task status and nova VM status | 23:28 |
| lxkong | time for lunch, i will think about that, thanks for the suggestion. Considering we are the first two cloud adopting ussuri (we are in alpha), so i don't mind removing HEALTHY if we have a clear status definition for the users. | 23:30 |
| sorrison | we have ussuri in production now too :-) working well | 23:37 |
| sorrison | our guest have all been upgraded to ussuri too and based on focal images | 23:37 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!