Bug 1949762
| Summary: | [RFE] Implement "Boot a VM with an unaddressed port" blueprint | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Michele Valsecchi <mvalsecc> | |
| Component: | openstack-nova | Assignee: | Sylvain Bauza <sbauza> | |
| Status: | CLOSED DEFERRED | QA Contact: | OSP DFG:Compute <osp-dfg-compute> | |
| Severity: | low | Docs Contact: | ||
| Priority: | low | |||
| Version: | 17.0 (Wallaby) | CC: | alifshit, ccamposr, dasmith, egallen, eglynn, jhakimra, kchamart, knoha, mariel, ralonsoh, sbauza, sgordon, stephenfin, vromanso | |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2081254 (view as bug list) | Environment: | ||
| Last Closed: | 2023-04-14 20:18:57 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | Yoga | |
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1266593, 2081254 | |||
|
Description
Michele Valsecchi
2021-04-15 02:41:33 UTC
Hi, thanks for the RFE! We'd like to better understand the use case here, since as you've uncovered yourself thing has a long and storied history, and there are certain things that are already possible. For instance, it is currently possible to boot a VM with a port with a "deferred" IP allocation policy, that assigns the port an IP only *after* the VM has been scheduled onto a compute host. This is mostly used for the "Routed networks" feature [1]. I suspect this is *not* what's being asked here. When you say "IP not directly managed by RHOSP", can you clarify what kind of port that translates to? For instance, it could be an SRIOV VF port connected to a provider network. In addition, if the IP allocation is not being managed bu OSP, then how *is* it being managed, and how (if at all) is that management being exposed to OSP? Thanks in advance for your answers! [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/deploy-routed-prov-networks Thanks for getting back to us. The use case is where the NFV application running on top of RHOSP _has to use_ an IP unknown to Neutron. In this particular case the NFV application has come constrains out of control of the operator in these regards (i.e. vendor limitations, etc). The current workaround is to assign a dummy IP to the port, and then let the NFV application take care of the rest. However, this leads to a situation where the "real IP" used on that port by the NFV application, and what the operator sees from RHOSP layers is conflicting. I've checked the link you've provided, and IIUC using the "deferred" IP policy would still lead to a situation in where the operator has to deal with this "dummy IP" situation. Let me know if the info I provided here are enough to clear up your doubts. Tracked in https://issues.redhat.com/browse/OSPRH-57 |