Bug 1401106
| Summary: | [RFE] Subscription-Intent: Allow a user to express the intent of how a subscription should be used, using a rules based syntax. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Rich Jerrido <rjerrido> |
| Component: | Candlepin | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | jcallaha |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.3.0 | CC: | ajambhul, aperotti, arusso, bbenson, bcourt, bkearney, chorn, daniele, dgross, egolov, gtaylor, jberry86, jcallaha, jdickers, jentrena, khowell, klaas, ktordeur, mlinden, mmccune, momran, mtenheuv, nsamant, pdudley, rchanter, rdixon, rjerrido, smane, smeyer, sokeeffe, vanhoof, vmeghana, wpinheir, yoliynyk |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, PrioBumpField, PrioBumpGSS, PrioBumpPM, SubscriptionExperience |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-02-03 10:21:52 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: | 1296845, 1353215, 1399395, 1476375, 1650573 | ||
|
Description
Rich Jerrido
2016-12-02 20:55:11 UTC
Thinking about this a bit more, this would be a functionality/feature that would be useful as an organizational setting in addition to (or in lieu of) it being an activation key feature. As hosts/consumers can be created via means other than registration via subscription-manager (such as via virt-who or hammer csv), it may make sense to have this logic somewhere that covers all registration methods. *** Bug 1436822 has been marked as a duplicate of this bug. *** *** Bug 1339286 has been marked as a duplicate of this bug. *** *** Bug 1443108 has been marked as a duplicate of this bug. *** *** Bug 1459551 has been marked as a duplicate of this bug. *** *** Bug 1423505 has been marked as a duplicate of this bug. *** *** Bug 1500959 has been marked as a duplicate of this bug. *** *** Bug 1478080 has been marked as a duplicate of this bug. *** *** Bug 1308544 has been marked as a duplicate of this bug. *** "attach qty 2 of $SOME_OTHER SUB." is suitable on some condition but not all. Likely "attach qty needed", having the math done by Satellite, is a common configuration. Some more considerations, please forgive the facts name, this is to explain just the expectation
if type = "hypervisor" and vmware.cluster="vdc_cluster" ( # start of a condition
if ( vmware.cluster_guests_members / vmware.cluster_host_members > 5), attach ( ( "RHEL Premium VDC subscription" or "RHEL Standard VDC subscription" ) and ("Smart Management Premium VDC Subscription" or "Smart Management Standard VDC Subscription" ) ) # mixed variables need to be evaluated. Math operations has to be possible.
else --attach Nil # remove the attached subscription if not matched on the 2nd condition
)
process # keyword to run the above queries not performed still and wait for the results
if type = "guest" and hypervisor.sub = Nil --attach ( ( "RHEL Premium Physical Node subscription" or "RHEL Standard Physical Node subscription" ) and ("Smart Management Premium Physical Node Subscription" or "Smart Management Standard Physical Node Subscription" ) ) # in case of Hypervisor is without a valid subscription, after process keyword
if type = "guest" and hypervisor.sub != Nil --attach ( hypervisor.all_available_subs ) #this will attach all of the available subscriptions that can be inherited from the Host
if type = "physical" --attach ( ( "RHEL Premium Physical Node subscription" or "RHEL Standard Physical Node subscription" ) and ("Smart Management Premium Physical Node Subscription" or "Smart Management Standard Physical Node Subscription" ) ) # simple rules for physical node
###
process is needed otherwise we need 2 round of the attachment of subscription to run.
Example: one Host currently has one subscription, and therefore is potentially need to have the first run to remove the attached subscription and then proceed with the other activities.
*** Bug 1644962 has been marked as a duplicate of this bug. *** *** Bug 1659480 has been marked as a duplicate of this bug. *** Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Note, Simple Content Access and Subscription Watch may help. See https://access.redhat.com/documentation/en-us/subscription_central for more details. |