Earlier  
Posted Nick Remark
#openstack-nova - 2018-09-20
06:28:44 openstackgerrit huanhongda proposed openstack/nova stable/ocata: Cleanup RP and HM records while deleting a compute service. https://review.openstack.org/603749
06:29:14 openstackgerrit fupingxie proposed openstack/nova master: Avoid Forcing the Translation of Translatable Variables https://review.openstack.org/603993
06:47:48 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Only update cells' transport_url and database_connection when needed. https://review.openstack.org/603998
06:53:45 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/os-vif master: Add support for Windows network commands https://review.openstack.org/487405
07:38:16 openstackgerrit Brin Zhang proposed openstack/python-novaclient master: Add support changes-before for microversion 2.66 https://review.openstack.org/603549
07:44:23 bauzas good morning
07:45:33 sean-k-mooney good morning :)
07:46:10 gibi good morning folks
08:26:23 openstackgerrit Merged openstack/nova master: libvirt: Drop MIN_LIBVIRT_VHOSTUSER_MQ https://review.openstack.org/565472
08:49:15 kashyap Hey folks, I wonder if anyone here knows Linux systems where only /dev/random exists
08:49:19 kashyap And not /dev/urandom.
08:50:20 kashyap Because I'm considering to add a default 'virtio-rng' device for Nova guests, whic uses /dev/urandom.
08:50:24 kashyap https://bugs.launchpad.net/nova/+bug/1789868
08:50:24 openstack Launchpad bug 1789868 in OpenStack Compute (nova) "RFE: Add a virtio-rng device to Nova instances by default" [Medium,Triaged] - Assigned to Kashyap Chamarthy (kashyapc)
08:52:03 kashyap (If anyone is wondering why '/dev/urandom'? It is non-blocking, and doesn't have the same limitations of `/dev/random`, which is a legacy interface.
09:02:20 openstackgerrit huanhongda proposed openstack/nova stable/ocata: Cleanup the caches when deleting a resource provider https://review.openstack.org/604021
09:13:35 kashyap stephenfin: The last clean up (IIRC) in that series: https://review.openstack.org/#/c/562313/ (libvirt: Drop MIN_LIBVIRT_PARALLELS_SET_ADMIN_PASSWD)
09:30:26 stephenfin kashyap: cool, I'll take a look now
09:34:08 kashyap stephenfin: Thanks; it's not urgent. Just a boring thing to tick off, when you have time
09:51:40 openstackgerrit Yikun Jiang proposed openstack/nova master: WIP: Add nova database migration script(psql version) https://review.openstack.org/604026
09:51:55 openstackgerrit Stephen Finucane proposed openstack/nova master: libvirt: Drop MIN_LIBVIRT_PF_WITH_NO_VFS_CAP_VERSION https://review.openstack.org/565517
09:52:30 kevko_home Hello guys , can i have simple question on you :) ?
09:57:51 openstackgerrit Yikun Jiang proposed openstack/nova master: WIP: Add nova database migration script(psql version) https://review.openstack.org/604026
10:06:34 kashyap kevko_home: Just ask, someone might respond.
10:24:19 openstackgerrit Brin Zhang proposed openstack/python-novaclient master: Add support changes-before for microversion 2.66 https://review.openstack.org/603549
10:47:31 openstackgerrit John Garbutt proposed openstack/nova-specs master: WIP: Spec for API policy updates https://review.openstack.org/547850
10:51:25 gibi bauzas, tetsuro: I managed to re-use the existing ServerMovingTests functional test set to verify the nested allocations during move operations. I found that force livemigrate and every evacuate case are faulty.
10:51:51 gibi bauzas, tetsuro: I will push the patch soon
10:52:16 gibi bauzas, tetsuro: I mean the fault reproduction patch, then I will look at how to solve the problem
10:58:12 openstackgerrit huanhongda proposed openstack/nova stable/ocata: Cleanup RP and HM records while deleting a compute service. https://review.openstack.org/603749
10:58:25 openstackgerrit Ghanshyam Mann proposed openstack/nova-specs master: Spec for API inconsistency cleanup https://review.openstack.org/603969
11:07:40 openstackgerrit Vlad Gusev proposed openstack/nova stable/pike: libvirt: Reduce calls to qemu-img during update_available_resource https://review.openstack.org/604039
11:22:15 openstackgerrit Takashi NATSUME proposed openstack/nova master: Add API ref guideline for examples https://review.openstack.org/604060
11:48:44 kevko_home Guys, i am packaging nova for debian. Current situation is that i have several packages , nova-common , nova-api, nova-placement-api, nova-conductor ...etc
11:48:44 kevko_home Each of package is doing his work, for example nova-common creating database users, etc, and also populating nova db. I have also nova-placement-api and nova-api which are doing same stuff with populating db, nova-placement-api creating database placement , users, grants ..etc ..fill connection in config and run nova-manage api_db sync , same in nova-api create db nova , users , grants, run nova-manage api_db sync.
11:48:44 kevko_home Problem is that i have error when api_database connection is missing in nova-placement-api package, does it mean that nova-placement-api needs both nova_api and placement connection settings filled ? Shouldn't be command separate for nova_api and placement ... something like nova-manage api_db sync , nova-mange api_placement sync ?
11:49:49 openstackgerrit Takashi NATSUME proposed openstack/nova master: Fix missing specifying doctrees directory https://review.openstack.org/604068
11:55:41 bauzas gibi: hola, what's the fault ?
11:58:49 tssurya kevko_home: which release are you using ?
11:58:59 kevko_home tssurya: rocky
11:59:46 tssurya I think in Rocky for a new set-up its something like nova_api DB is the default placement-DB
12:00:28 kevko_home tssurya: does it mean that placement database not needed ?
12:00:47 tssurya https://docs.openstack.org/nova/rocky/configuration/config.html#placement_database.connection
12:01:15 tssurya refer to ^ ,
12:01:20 kevko_home tssurya: i don't think you understand me :)
12:04:51 tssurya there is no seperate DB sync commands as of yet, but probably cdent can help you more
12:05:52 kevko_home tssurya: i have several deb packages , nova-common - create nova db, db user, db grants, set api_database.connection in nova.conf ( questions are answered in debconf ), run nova-manage db sync , nova-api do the same thing with one difference , run nova-manage api_db sync with fill api_database.connection to right value , nova-placement-api same thing with difference that set placement_database.connection value .... everything is
12:05:52 kevko_home work as expected ....but in nova-placement api postinst i have this : http://paste.openstack.org/show/730413/
12:06:38 kevko_home tssurya: so basically , i think nova-manage api_db sync should be splitted to two separate commands for fill api_db and placement_api
12:07:31 kevko_home tssurya: because nova-placement-api and nova-api can run standalone ...why there is sync command which is trying fill both databases if i let's say configuring nova-placement-api only on some server ?
12:08:56 kevko_home tssurya: or add if clauses on CONF.placement_database.connection is not None: else: LOG.warning(''Nova-manage will not run , you have to configure api_database.connection')
12:09:52 kevko_home tssurya: i can send a code to review ..but wanted to discuss this with you guys in nova channel ...
12:10:38 kevko_home tssurya: because if i know , placement will be totally moved into separate project ...but don't know when ..
12:10:57 tssurya its in the transition phase
12:11:21 kevko_home tssurya: and what do you think about my above thinkings ? :/
12:12:19 tssurya looking more into the code..
12:14:29 tssurya kevko_home: okay so you basically want the user to be warned if placement_database.connection is not set ?
12:14:40 tssurya and nova_api.databaseconnection is also not set ?
12:15:01 kevko_home tssurya: yes, something like that ..let me send you diff ..w8 a minute
12:16:36 tssurya well I guess the Rocky documentation deployment (https://docs.openstack.org/nova/rocky/user/placement.html#deployment) states api_db sync command is used for both syncing and if you set placement_db conn it will be used and if you don't set that, it is expected that you set the api_db conn.
12:17:10 tssurya I understand your concern though, and the need for a check seems ok to me,
12:19:32 kevko_home tssurya: something like this http://paste.openstack.org/show/730414/
12:19:41 kevko_home tssurya: ok, i will send a review then
12:22:21 gibi bauzas: sorry I was out grabbing food. The fault is that nova does not consider allocations agains the child RPs during the move
12:22:36 tssurya kevko_home: ack
12:33:32 Kevin_Zheng tssurya Hi
12:33:41 Kevin_Zheng does this bothers CERN?
12:33:43 Kevin_Zheng https://launchpad.net/bugs/1793423
12:33:43 openstack Launchpad bug 1793423 in OpenStack Compute (nova) "Should not read config options while update cells" [Undecided,In progress] - Assigned to Zhenyu Zheng (zhengzhenyu)
12:33:58 Kevin_Zheng or it is made this way
12:36:27 tssurya Kevin_Zheng: we don't use the update_cell command command very often, but what you have reported has always bugged me :)
12:36:52 Kevin_Zheng Ha
12:36:56 tssurya meaning the update_cell command is used for a lot of other stuff than just updating the DB connection and transport_url
12:37:19 tssurya so it is not fair that these two always have to be passed to ensure they don't get over written by the config options
12:39:52 tssurya Kevin_Zheng: although I don't understand your point 2: where you say you can't use nova_
12:39:58 tssurya nova_cell1.conf
12:40:25 tssurya because you need api_database connection,
12:40:39 tssurya for update_cell ?
12:40:50 Kevin_Zheng sorry disconnected
12:41:28 tssurya np, did you get the messages ^ ?
12:41:37 Kevin_Zheng yeah, I saw them
12:41:40 Kevin_Zheng reading
12:41:53 Kevin_Zheng yeas
12:41:55 Kevin_Zheng yeah
12:42:04 Kevin_Zheng we have to update the records in api_db
12:42:27 tssurya ah okay
12:42:34 tssurya yea sorry, got confused
12:43:10 tssurya but now that you mention "up_calls" we have the same problem for nova-manage db archive_deleted_rows
12:43:34 Kevin_Zheng hmm
12:52:36 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Only update cells' transport_url and database_connection when needed. https://review.openstack.org/603998
12:52:54 openstackgerrit huanhongda proposed openstack/nova master: Fix instance delete stuck in deleting task_state https://review.openstack.org/598084
13:04:16 openstackgerrit Vlad Gusev proposed openstack/nova stable/pike: libvirt: Reduce calls to qemu-img during update_available_resource https://review.openstack.org/604039
13:16:42 mnaser there isn't a way to delete a compute node from the db, is there?
13:16:53 bauzas mnaser: by SQL goos ?
13:16:57 mnaser well, without sql
13:17:07 bauzas ah
13:17:10 mnaser nova service-delete deletes the service but the compute node record is still there
13:17:23 mnaser and scheduler complains constantly about 'No compute service record found for host <foo>'
13:17:36 bauzas that's a good point
13:17:49 bauzas compute_node records are automatically populated by the resource tracker

Earlier   Later