Bug 1282168
Summary: | [RFE] ability to choose provisioning network and manage network also hypervisor when we deploy in vmware | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Mario Gamboa <mario.gamboa> |
Component: | Provisioning | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED WONTFIX | QA Contact: | Katello QA List <katello-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1.1 | CC: | adprice, bkearney, inecas, mario.gamboa, mhulan |
Target Milestone: | Unspecified | Keywords: | FutureFeature |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-14 18:02:42 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: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 260381 |
Description
Mario Gamboa
2015-11-15 09:05:21 UTC
Mario, can you please check out the networking changes which went into Foreman 1.8 to see if this meets you need. We believe this addresses your concerns with the expception of the actual hypervisor. I would expect you to not want Satellite to choose that, and rather have the virt-fabric select this. Well that is the problem Bryan at this moment i make a test lab i just make 2 hypervisor 1 with 12gb and another one with 32 the was as follow: Create a new vm with 8gb fine goes into the first hypervisor with 12gb of ram Create another vm with 12gb fail no enough memory left mean try again to create in the first hypervisor create a new vm with 3gb fail no enough memory left again is trying to create in the same hypervisor create a new vm with 5gb fail no enough memory left again same issue restart katello-services Try again Create a new vm with 10 gb and now is create in the second hypersor with 32gb without issues create a new vm with 20 gb is created in the second hypervisor with 32gb create a new 3gb vm and fail no enough memory resources mean the satellite is not trying to get the first hypervisor that still have available memory for deploy restart katello-services try again the same test 3gb vm now is success and is created in the first hypervisor for me is looks like the satellite never try to choose by resource the hypervisor is just attach to one at the time and every time i restart katello-services is jumping around and get another one The feature of network is very solid on foreman 1.9 and is really great because also we can use ssh remote command execution but if redhat is going to use 1.8 that fix the issue of network but still until now the problem to choose a hypervisor with resources when need it Mario, we will be shipping 6.2 with foreman 1.11. Do you feel this version of foreman will meet the goal of this RFE? I don't know if with foreman 1.11 solve the issues because is no at this moment available to tell you what i can tell you is with 1.10 is ok for me in the case of the network issue but still doesn't have the option to choose the resource in case the resource is full (hypervisor) and foreman is fail to create a new vm Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you. |