Thursday, 2020-11-05

*** tosky has quit IRC00:14
lxkongbtw sorrison, are you dev or ops? or devops?00:15
sorrisonI'm both00:16
lxkongah ok, may i know how many people in your team is looking after trove?00:17
sorrisonI'm the only one doing dev in trove00:18
sorrisonbut we have other ops/helpdesk that will do that side of thing in trove too, we share00:18
lxkongsorrison: ok, thanks for the info00:19
sorrisonyeah I'm just mainly frustrated as I think all the changes since ussuri are going to make it essentially impossible to upgrade. We are almost at the point where we might have to drop trove or fork it etc.00:19
lxkongit depends on what you need, i can help add things back, either for master or Victoria.00:20
sorrisonussuri works really well for us00:20
lxkongbut it's your call00:20
sorrisonI want to contribute to trove but I think the priorities need to be getting the tests working upstream and making it upgradable00:21
sorrisononce that's done then things like making it use containers etc. could be done but it's really hard with no proper testing in the gate and the removal of all the api tests in trove-tempest-plugin00:22
lxkongi understand, the functional test and tempest test both work on my local. Upstream CI fails because of CI host performance issue, container in a vm in another vm, etc.00:22
lxkonghave you checked the existing tests in trove-tempest-plugin?00:23
lxkongi don't think the current test cases are less than the privious ones00:23
lxkongand the previous ones actually didn't provide many valid tests00:23
lxkongwe are using trove tempest in our scenario test,  which covers instance creation, access, backup/restore, configuration and replication00:24
lxkongwhat other api tests are you looking for?00:24
sorrisonyeah lots missing though00:25
sorrisonwhat was the reason to remove the existing api tests?00:26
sorrisonsorry I'm missing a lot of history here and just trying to catch up00:26
sorrisonSo with upstream CI, do you know what needs to be done to fix the issues?00:37
lxkong> yeah lots missing though00:41
lxkonglooking at https://review.opendev.org/#/c/761472/, i don't think there are *lots* missing00:41
lxkongon the contrary, the current tests can cover more than the tests in that patch00:42
lxkonghttps://review.opendev.org/#/c/761472/1/trove_tempest_plugin/tests/api/database/versions/test_versions.py do you think this test is doing any valid check for the end user?00:43
lxkong> what was the reason to remove the existing api tests?00:43
sorrisonit's all about API compatibility00:44
lxkongbecause those tests were not well organized, and as cloud provider, we do care about the real scenario test, e.g. create a instance and access the mysql00:45
sorrisonI couldn't see tests for restart, update name etc. but I haven't looked through it all yet. it's a bit different to all the other tempest code now so a bit less familiar to me00:45
lxkongand check the data after restoing a db instance00:45
sorrisonyeah they are equally as important00:45
lxkongfor the upstream CI, i've talked with the infra people, there is no workaround at the moment.00:46
lxkongmagnum is having the same issue00:46
lxkongso we have to rely on the test run on the local dev environment00:46
lxkonglike what i did for your reverting flavor API patch00:47
sorrisonyeah ok, could it run as external CI feeding back into gerrit? We can host resources if needed00:47
lxkongi think so. We are hosting CI jobs for cloud-provider-openstack in k8s, but not yet for trove00:48
lxkongjust because of lack of resources00:48
openstackgerritSam Morrison proposed openstack/trove master: Make guest agent api changes backwards compatible  https://review.opendev.org/76127000:49
lxkongbecause there was no other active contributor before, i just run all the test  locally by myself00:50
sorrisonI guess if you're the only one doing anything it is easy to only think about one environment. For the future of trove though it needs to change00:53
sorrisonmost of the sites I know running trove are running older versions so it might not be for a while until operators try an upgrade to newer versions and discover all these issues00:54
lxkongyep, that's what i was trying to explain for all the changes introduced since ussuri00:54
sorrisonbut if you want other people to continue to use trove you're going to have to start taking these things into account00:55
lxkongyou are absulutely right, the thing is, when i contribute to trove at the beginning, after proposing a patch, no one is interested in review00:56
lxkongno reviewers, no discussion in mailing list00:56
lxkongit's hard to get feedback00:56
lxkongif i stopped contribution and maintaining, trove has already been retired00:57
lxkongi was so suprised when you joined and said you are using trove00:58
sorrisonyeah I understand that, it's great to have someone maintaining trove00:58
sorrisonMy fear is the the existing people who are using trove will give up and stop using it so I'm really keen to get it working the way it was in Ussuri. It's a really great piece of software and is a good value add for our users00:59
lxkongbut anyway, like i said, i'm glad people are coming, and i agree we could have things added back or get fixed01:00
lxkongyou are the only one of "existing people" i've known of, besides us01:00
openstackgerritSam Morrison proposed openstack/trove master: Use datastore manager as opposed to name to restrict actions  https://review.opendev.org/76125301:02
sorrisonI think mariadb uses the mysql manager so maybe this could change a little?01:02
lxkongsorry, change for what?01:05
openstackgerritSam Morrison proposed openstack/trove master: Pass availability zone through to volume creation.  https://review.opendev.org/76125001:07
lxkongbtw, i have fixed the revert flavor api patch and started runing test01:07
openstackgerritMerged openstack/python-troveclient master: Fix help message of datastore version upgrade  https://review.opendev.org/76139301:20
openstackgerritLingxian Kong proposed openstack/trove master: Revert "Remove flavor API"  https://review.opendev.org/76106301:31
*** sapd1 has joined #openstack-trove01:41
*** rcernin has quit IRC01:43
*** rcernin_ has joined #openstack-trove01:43
*** spatel has joined #openstack-trove02:10
*** spatel has quit IRC02:11
*** spatel has joined #openstack-trove02:12
*** spatel has quit IRC02:14
*** rcernin_ has quit IRC03:24
*** rcernin_ has joined #openstack-trove03:34
*** rcernin_ has quit IRC03:47
*** sapd1 has quit IRC03:57
openstackgerritLingxian Kong proposed openstack/trove master: Fix upgrading instance datastore version  https://review.opendev.org/76146504:07
openstackgerritLingxian Kong proposed openstack/trove stable/victoria: Revert "Remove flavor API"  https://review.opendev.org/76149004:10
*** rcernin has joined #openstack-trove04:20
openstackgerritSam Morrison proposed openstack/trove master: Make guest agent api changes backwards compatible  https://review.opendev.org/76127004:30
sorrisonlxkong: I think I found another issue relating to flavor API04:51
sorrisonresize isn't working. Get the error Details: {'code': 400, 'message': "Validation error: resize['flavorRef'] '' is not valid under any of the given schemas; '' is too short; '' does not match '^.*[0-9a-zA-Z]+.*$'; '' is not of type 'integer'"}04:51
openstackgerritSam Morrison proposed openstack/trove master: Make guest agent api changes backwards compatible  https://review.opendev.org/76127004:59
*** rcernin has quit IRC05:13
*** rcernin has joined #openstack-trove05:15
lxkongsorrison: can you provide more detail? If using CLI, what's the command? If API, the body?05:26
sorrisonsure one sec, I'm just doing some full tempest runs, mostly looking good, resize and rename are failing so far05:31
sorrisonI've discovered one of the reasons we need the flavor ID is that the flavors that trove uses are private05:35
sorrisonso doing something like `trove resize-instance x db.medium` fails as flavor can't be found05:35
sorrisonOK I figured it out it was a misconfiguration by me, whoops05:40
sorrisonI think the flavor API needs to be restored in full along with docs and tests as it's not something we can remove and is very useful05:41
sorrisonlxkong: are using designate plugin in your env? I think that is broken with a change around instance.address. Just trying to diagnose now05:46
openstackgerritMerged openstack/trove master: Revert "Remove flavor API"  https://review.opendev.org/76106306:03
*** rcernin has quit IRC06:37
*** rcernin has joined #openstack-trove06:50
*** rcernin has quit IRC07:12
*** rcernin has joined #openstack-trove07:33
*** rcernin has quit IRC07:43
*** tosky has joined #openstack-trove08:13
*** hoonetorg has quit IRC08:21
*** hoonetorg has joined #openstack-trove08:26
*** e0ne has joined #openstack-trove10:46
*** sapd1 has joined #openstack-trove13:18
*** congnt96 has joined #openstack-trove14:55
*** sapd1 has quit IRC16:51
*** congnt96 has quit IRC18:17
lxkongsorrison: i am afraid i don't agree that flavor API in Trove is necessary. All trove does is to query flavor from Nova.19:32
lxkongsorrison: do you have any use case that trove flaovr API can do but Nova flavor can't?19:32
lxkongIf you want to limit the flavors can be used by users, just config that in datastore version using`trove-manage datastore_version_flavor_add`19:34
openstackgerritMerged openstack/trove-dashboard master: Fix replica number input type  https://review.opendev.org/76141919:48
openstackgerritLingxian Kong proposed openstack/trove stable/victoria: Use datastore manager as opposed to name to restrict actions  https://review.opendev.org/76166020:01
*** e0ne has quit IRC20:21
*** e0ne has joined #openstack-trove20:37
*** e0ne has quit IRC21:02
*** rcernin has joined #openstack-trove21:27
*** rcernin has quit IRC21:53
*** rcernin has joined #openstack-trove21:55
openstackgerritLingxian Kong proposed openstack/trove master: Fix the functional test related to flavor check  https://review.opendev.org/76167421:57
openstackgerritLingxian Kong proposed openstack/trove stable/victoria: Revert "Remove flavor API"  https://review.opendev.org/76149021:59
*** e0ne has joined #openstack-trove22:03
openstackgerritMerged openstack/trove master: Use datastore manager as opposed to name to restrict actions  https://review.opendev.org/76125322:15
*** e0ne has quit IRC22:17
sorrisonlxkong: There are 2 reasons for the flavor ID, one is if you are using a separate nova/cinder that is not exposed to end users. That is how we used to have trove deployed and there might be other installs set up that way22:25
sorrisonthe second reason is that the flavors that trove users might not be accessible to normal users. This is the case for us where trove uses special private flavors that aren't accessible to normal users22:26
sorrisondoes that make sense?22:26
sorrisonI mean flavor API22:33
lxkongCould both the reasons be solved using `trove-manage datastore_version_flavor_add`?22:50
*** rcernin has quit IRC22:57
*** rcernin has joined #openstack-trove23:01
*** spatel has joined #openstack-trove23:20
*** spatel has quit IRC23:25
openstackgerritMerged openstack/trove stable/victoria: Use datastore manager as opposed to name to restrict actions  https://review.opendev.org/76166023:52
*** tosky has quit IRC23:55

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!