-
Notifications
You must be signed in to change notification settings - Fork 898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExtManagementSystem: Multiple columns called "Total Memory" #18130
Comments
I'm guessing this is a vmware thing: https://www.vmware.com/support/developer/converter-sdk/conv51_apireference/memory_counters.html Memory Total = Aggregate host machine memory - (VMkernel memory + Service Console memory + other service memory) Then again maybe I'm way off. Can someone confirm? |
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
@agrare can you chime in on this? |
Actually I dont' think this is VMware specific, I think it is just duplicated
And
From So the only difference is one uses |
Makes sense, thanks :) Still, having 2 identical entries in the report menu is suboptimal (even if they do the same thing), any chance we could get rid of one of those attributes? |
Yes absolutely, working on that now |
cc @kbrock |
dropping the delegate makes the most sense |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation. |
ping @kbrock |
going forward with this: introducing a hide_attribute that stores attributes in hidden_attributes. will also tie this into This will be used by MiqExpression.model_details and api: options_serializer.rb |
some virtual attributes are not needed in reporting nor the api. this allows attributes to work for our uses, but not put them into the public api this addresses issues like ManageIQ#18130
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to start using. This allows attributes to still work, but just not be advertised on our public apis (i.e.: report builder and rest api). This allows This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to start using. This allows attributes to still work, but just not be advertised on our public apis (i.e.: report builder and rest api). This allows This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to start using. Now, the attributes are still accessible. So nothing will break. But these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to start using. Now, the attributes are still accessible. So nothing will break. But these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to start using. Now, the attributes are still accessible. So nothing will break. But these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to start using. Now, the attributes are still accessible. So nothing will break. But these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532 Hide deprecated and duplicate attributes Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to start using. Now, the attributes are still accessible. So nothing will break. But these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532 Hide deprecated and duplicate attributes Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to start using. Now, the attributes are still accessible. So nothing will break. But these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532 Hide deprecated and duplicate attributes Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to start using. Now, the attributes are still accessible. So nothing will break. But these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532 Hide deprecated and duplicate attributes Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to start using. Now, the attributes are still accessible. So nothing will break. But these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532 Hide deprecated and duplicate attributes Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised to the customer as attributes to use. After this change, the attributes are still accessible. Just these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532 Hide deprecated and duplicate attributes. Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised to the customer as attributes to use. After this change, the attributes are still accessible. Just these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532 Hide deprecated and duplicate attributes. Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised to the customer as attributes to use. After this change, the attributes are still accessible. Just these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532 Hide deprecated and duplicate attributes. Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised to the customer as attributes to use. After this change, the attributes are still accessible. Just these attributes are no longer advertised on the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532 Hide deprecated and duplicate attributes. Some virtual_attributes are not needed in reporting nor the api. Some deprecated attributes should not be advertised for customers to use. After this change, the attributes are still accessible. So nothing will break, but these attributes are no longer advertised in the public apis (i.e.: report builder and rest api). This allows us to control which parts of our models are exposed. This fixes ManageIQ#18130 This enables ManageIQ#20532
Base a report on Providers (any kind other than performance), and in Available Fields, there is "Total Memory" twice:
This is because one is
total_memory
and the other isaggregate_memory
(both fields onext_management_system
) table.Looks like this boils down to...
even
And that is ends up calling..
Which is because
(
total_memory
gets translated by that:notfound => :titleize
fallback)I guess these 2 fields (
total_memory
andaggregate_memory
) should have distinct descriptions, but I don't know enough about the 2 fields to be able to tell the difference.The text was updated successfully, but these errors were encountered: