vault backup: 2025-01-19 21:14:51

3 files changed, 0 insertions, 28 deletions

diff --git a/3 resources/openstack/Creating ports.md b/3 resources/openstack/Creating ports.md
deleted file mode 100644
index 90223bf..0000000
--- a/3 resources/openstack/Creating ports.md
+++ /dev/null
@@ -1,4 +0,0 @@
-#openstack #port
-
----
-Creating a port with a fixed IP requires admin privileges. It is not sufficient to have an RBAC policy that shares the network with a tenant.
\ No newline at end of file
diff --git a/3 resources/openstack/Libvirt pmsuspended.md b/3 resources/openstack/Libvirt pmsuspended.md
deleted file mode 100644
index 4749c76..0000000
--- a/3 resources/openstack/Libvirt pmsuspended.md
+++ /dev/null
@@ -1,6 +0,0 @@
-#openstack #libvirt
-
----
-Encountered a guest running some desktop image that sleeps and puts libvirt domain in state pmsuspend.
-
-Openstack does not sync power states in this case so the nova instance is still ACTIVE.
\ No newline at end of file
diff --git a/3 resources/openstack/Nova live migration volume.md b/3 resources/openstack/Nova live migration volume.md
deleted file mode 100644
index 8b37f67..0000000
--- a/3 resources/openstack/Nova live migration volume.md
+++ /dev/null
@@ -1,18 +0,0 @@
-#openstack #nova #live-migration #volume
-
-
----
-Table cinder.volume_attachment, contains which volume_driver. target_lun `(<n>)` here maps to `dm-<n>`.
-Luns are not unique across pod, each node has a target_lun 2 and thus dm-2 connected.
-
-os-brick is responsible for connecting volumes;
-if connection_info it receives contains target_iqns, target_luns etc it will not do a scan and just returns those. 
-`@see os_brick/initiator/connectors/iscsi.py`
-
-`nova/virt/libvirt/driver.py -> def _connect_volume` does attaching of volumes using os-brick. Driver exposes some methods that do this and are called elsewhere: `swap_volume`, `attach_volume`, `pre_live_migration`. 
-
-`pre_live_migration` is called by `nova/compute/manager.py`
-
-So in `nova/compute/manager.py` there is a function that does the rollback, and it rollbacks bdm's and deletes volume attachments before it calls `rollback_live_migration_at_destination` which in turn makes an attempt at deleting the actual volume attachment to the node. But at that point all objects have been rollbacked already so it has invalid information.
-
-If the code in new versions of openstack isn't any different i'll just make a bug report and see what they come up with.