Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2019-11-22
09:30:38 bauzas btw. are we around Thanksgiving ?
09:30:49 bauzas channel was quiet yesterday
09:35:47 gibi sean-k-mooney: thanks for the bandwidth bug report. efried: thanks for the summary mail. I will dive in
09:37:10 mlycka Hello. What's the opinion on taking another stab https://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/expose-quiesce-unquiesce-api.html?
09:38:19 stephenfin bauzas: I am
09:38:25 stephenfin if that's who you're asking?
09:38:47 bauzas stephenfin: you are what ?
09:39:01 bauzas I was wondering whether it was Thanksgiving period
09:39:11 bauzas (disclaimer, it's absolutely not a thing here)
09:39:13 stephenfin Ah, I read that as are _you_ around
09:39:17 stephenfin whoops
09:39:32 bauzas but I can check the calender
09:39:45 bauzas nope, it's next week
09:39:46 bauzas sorted.
09:48:59 openstackgerrit Alexandre arents proposed openstack/nova master: Do not update root_device_name during guest config https://review.opendev.org/670000
11:59:35 sean-k-mooney melwitt: the non-ironic case is because they were following our scale in docs which direct them to delete the compute service however they skipped step 1 which is remove all instances form the node first. and i guess ensure that all allocations are removed before doing the service delete
12:00:35 sean-k-mooney so they delete the compute service with vms running then the bug got filed to help them fix that and prefereabel keep the vms by migrating them.
12:00:59 sean-k-mooney so its a self inflicted failure
12:04:34 sean-k-mooney efried: gibi: by the way the downstream bug is just the bugzilla for validating support for bandwidth support. i think on ebug is being filed for triplo but we have not filed one for nova yet because i wanted to disucss what we found first to make sure what the behavior should be.
12:04:48 openstackgerrit Surya Seetharaman proposed openstack/nova master: Include removal of ephemeral backing files in the image cache manager https://review.opendev.org/689422
12:04:55 openstackgerrit Lee Yarwood proposed openstack/nova master: Revert "nova shared storage: rbd is always shared storage" https://review.opendev.org/682523
12:04:56 openstackgerrit Lee Yarwood proposed openstack/nova master: libvirt: Rename _is_storage_shared_with to _is_path_shared_with https://review.opendev.org/693337
12:05:18 gibi sean-k-mooney: agree. Right now we need to find a backportable solution (see my mail on the ML about the problems with efried's proposal)
12:05:46 gibi sean-k-mooney: for nova I will create a small spec to add the node uuid filtering capability to os-hypervisors
12:06:01 gibi sean-k-mooney: for neutron I would like to wait for the neutron folks to react
12:06:04 sean-k-mooney efried: gibi this is the downstream bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1463838 fyi but let continue upstream
12:06:05 openstack bugzilla.redhat.com bug 1463838 in openstack-nova "[RFE] Guaranteed minimum bandwidth" [Urgent,On_qa] - Assigned to smooney
12:06:44 sean-k-mooney gibi: am what we need ist to be able to query it by host or hypervior host
12:06:49 sean-k-mooney not by uuid
12:07:28 gibi sean-k-mooney: my bad, yes, we need to be able to filter by service host name
12:07:33 gibi to get the node uuid
12:07:36 sean-k-mooney yep
12:08:07 sean-k-mooney we might be able to do that already we can certenly just do a hypervior show
12:08:24 sean-k-mooney and i think that will accpet the host but i need to check the hypervioru api
12:08:52 sean-k-mooney im still catching up on the mail trhead so ill comment more once i have read it
12:09:47 sean-k-mooney in terms of backport it would need to be backported to train and stein if we did backport a fix
12:10:11 sean-k-mooney but for the sepecific case we found customer should not hit it
12:11:03 sean-k-mooney the might unitll we fix the standalone mode but in a normal tipleo deployment it set the hostname to match the value it sets in the host config option
12:12:01 sean-k-mooney in standalone mode the host os is installed manually and therfor cloud-init does not run and that step is not done
12:12:55 gibi as a side track I filed bug as nova compute fails if the CONF.host is changed after initial deployment https://bugs.launchpad.net/nova/+bug/1853587
12:12:55 openstack Launchpad bug 1853587 in OpenStack Compute (nova) "nova compute fails to update inventory in placement after changing [DEFAULT]/host" [Undecided,New]
12:14:14 sean-k-mooney ya that is basically the same issue not entirely but close enough
12:16:38 sean-k-mooney gibi: ok so we use the host option to create teh compute service recored but the hypervior_hostname for the placement name
12:17:04 sean-k-mooney so changing CONF.host after the fact causes us to creat a new service record and uuid
12:17:12 gibi sean-k-mooney: yepp, which is logical if we have to support more than one hypervisors per service
12:17:32 sean-k-mooney but then when we try to create the RP we get a colission on the hyperviour_hostname right
12:17:39 gibi sean-k-mooney: right
12:17:59 gibi sean-k-mooney: I guess if you need to change CONF.host then first have to cleanup the old service and placement
12:18:45 sean-k-mooney that or if we dont find the service record by host check if its theyer by hypervior hostname and then upstat the host field?
12:19:01 sean-k-mooney not sure that would be right in all cases however
12:19:25 sean-k-mooney draning deleting and recreating seams safer
12:20:46 sean-k-mooney funnily enough we have a customer that want to be able to do a backup and restor of the compute node and potentially chang ethe hostname since there hostnames are determine by the location of the server and they may need to restore to a different host
12:21:23 gibi that sounds fun
12:21:26 sean-k-mooney if they were not still running a pre placement version of openstack they would hit this issue
12:22:16 openstackgerrit Lee Yarwood proposed openstack/nova master: compute: Take an instance.uuid lock when rebooting https://review.opendev.org/673463
12:27:06 openstackgerrit Lee Yarwood proposed openstack/nova master: virt: Provide block_device_info during a rescue https://review.opendev.org/270287
12:27:37 sean-k-mooney gibi: did i mention i also traced how neuton learns what hostname to use in the frist place
12:28:09 gibi sean-k-mooney: I think you did and I also looked at the code with the help of lajoskaton this morning
12:28:26 sean-k-mooney its via the agent report
12:28:39 openstackgerrit Merged openstack/nova master: Specify what RPs _ensure_resource_provider collects https://review.opendev.org/695429
12:28:45 openstackgerrit Merged openstack/nova master: nova-net: Add TODOs for remaining nova-network functional tests https://review.opendev.org/684345
12:29:01 sean-k-mooney so to use the actual hostname we would have to extend the report with a hypervior hostname field
12:29:21 sean-k-mooney then the neutron server could use that if its present
12:29:54 gibi sean-k-mooney: exaclty, which is an RPC change which might not be backportable
12:30:06 gibi hence my reply asking neutron folks about it
12:30:06 sean-k-mooney its not an object change
12:30:21 sean-k-mooney its an unversioned dict of strings field
12:30:37 sean-k-mooney at least it used to be
12:30:52 gibi sean-k-mooney: neutron server still need to have a way to handle old RPC reports from not upgraded agents
12:31:46 sean-k-mooney ya which could be to either first try to look up in placmene by its existing host value.
12:32:10 sean-k-mooney and if it fails then fallback to the full hyperviour list and cache the result
12:32:40 sean-k-mooney normally the CONF.host and hypervior_host will be the same in the libvirt case
12:39:37 openstackgerrit Balazs Gibizer proposed openstack/nova stable/stein: Use admin neutron client to query ports for binding https://review.opendev.org/694665
12:40:30 gibi elod: ^^ fixed your comment
12:40:56 openstackgerrit Balazs Gibizer proposed openstack/nova stable/stein: Use admin neutron client to see if instance has qos ports https://review.opendev.org/694668
12:41:04 elod gibi: thx, looking
12:43:03 gibi oooo ma csovet is fognak ma vagni
12:43:11 gibi az nagyon meno lesz
12:58:02 gibi wrong window obviously
13:44:27 openstackgerrit Merged openstack/nova master: Remove 'os-security-group-default-rules' REST API https://review.opendev.org/686807
13:44:33 openstackgerrit Merged openstack/nova master: nova-net: Remove unused '*_default_rules' security group DB APIs https://review.opendev.org/686808
13:44:40 openstackgerrit Merged openstack/nova master: Remove (most) '/os-networks' REST APIs https://review.opendev.org/686809
14:10:31 openstackgerrit Merged openstack/nova stable/train: Add functional recreate test for bug 1852610 https://review.opendev.org/694544
14:10:31 openstack bug 1852610 in OpenStack Compute (nova) train "API allows source compute service/node deletion while instances are pending a resize confirm/revert" [Undecided,In progress] https://launchpad.net/bugs/1852610 - Assigned to Matt Riedemann (mriedem)
14:35:36 mlycka Hi again, quick question, is there no 'quiesced' state for VMs?
14:42:08 johnthetubaguy mlycka: I don't think there is, but there is a state of snapshotting, or something like that, during which time it might be quiesced
14:44:03 mriedem i think that's when creating a snapshot of an active volume-backed instance
14:44:08 mriedem and only if the driver and image support it
14:44:16 mriedem i.e. qemu guest agent
14:44:37 mriedem https://github.com/openstack/nova/blob/master/nova/compute/api.py#L3213
14:44:45 mlycka Right right...I'm just looking through an older patch which added a new state as part of exposing quiescing/unquiescing in the API. I'm guessing that would still have to be done for that functionality to be implemented.
14:46:53 mriedem i don't see that we even set the task_state on the instance while creating a volume-backed snapshot, which seems bad
14:47:05 mriedem means you could like migrate the server while creating the snapshot
14:47:29 mriedem https://github.com/openstack/nova/blob/991d675675c1c6bb87a2b9d19327e2b4473f6c0b/nova/compute/task_states.py#L34
14:48:56 mriedem we uh don't even have a different server status during a snapshot https://docs.openstack.org/api-guide/compute/server_concepts.html
14:49:44 mriedem anyway, that'd be an extremely latent issue
14:50:24 openstackgerrit Merged openstack/nova stable/train: Add functional recreate revert resize test for bug 1852610 https://review.opendev.org/694545
14:50:24 openstack bug 1852610 in OpenStack Compute (nova) train "API allows source compute service/node deletion while instances are pending a resize confirm/revert" [Undecided,In progress] https://launchpad.net/bugs/1852610 - Assigned to Matt Riedemann (mriedem)
14:51:15 mlycka mriedem: How do you mean latent?
14:56:41 mriedem meaning if it's a bug, it's always been there

Earlier   Later