-
Notifications
You must be signed in to change notification settings - Fork 358
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
Add EAP and Wildfly to allowed types for MW topology #2724
Conversation
@miq-bot add_label topology |
the PR LGTM. one thing I'm wondering about though - is MiddlewareServer now still needed here after moving to more concrete eap/wildfly types (and displaying them specifically) that derive from MiddlewareServer? |
should any unitests be adjusted to those specific types? afaik we have some jasmin tests with example json files and other sample inputs that should be updated |
@abonas well the server which has hawkular running on is of MiddlewareServer type, so this one would not be visible in topology. Sure unit tests should include these new classes as well, I'll add them right away. |
77bccd7
to
dd79cad
Compare
Travis fail is relevant to ManageIQ/manageiq#16478 |
@karelhala have you seen my comment above regarding other potential tests that should be updated? |
@abonas sorry, I missed your last comment. I'll check it out, since PR ManageIQ/manageiq#16478 is closed I can now focus on fixing tests. |
dd79cad
to
c1d9428
Compare
@karelhala what's the status of this PR? thanks. |
@miq-bot assign @martinpovolny |
c1d9428
to
020e1ad
Compare
@abonas I am fixing the tests right now. |
803f23d
to
ca5c6d1
Compare
@@ -79,6 +95,14 @@ | |||
"source": "MiddlewareManager1", | |||
"target": "MiddlewareServer1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this link still relevant in the current architecture with eap/wildfly? I mean will we get it on real env? Won't we get only wildfly/eap objects in the json, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well I am not against removing these, however we still use MiddlewareServer for Hawkular server. So Whenever I spin hawkular standalone the server inside it will be of type MiddlewareServer. I tested this with hawkinit and it was still present.
However if you'd were to run hawkular provider on wildfly/eap solely by installing some packages and such (kinda hard to do) it will be of type wildfly/eap.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, as long as it appears then it should be present. the point here is to make sure this reflects a real env.
:kind => "MiddlewareServerEap", | ||
:display_kind => "MiddlewareServerEap", | ||
:miq_id => mw_server_eap.id, | ||
:icon => match(/vendor-wildfly/), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't the icon vendor-eap here?
:target => "MiddlewareMessaging" + mw_messaging.compressed_id.to_s} | ||
{ | ||
:source => "MiddlewareManager" + ems_hawkular.compressed_id.to_s, | ||
:target => "MiddlewareServer" + mw_server.compressed_id.to_s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is not relevant atm, we'll get only eap/wildfly types
:target => "MiddlewareServerWildfly" + mw_server_wildfly.compressed_id.to_s | ||
}, | ||
{ | ||
:source => "MiddlewareServer" + mw_server.compressed_id.to_s, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
like above, I think all MiddlewareServer is not going to appear anymore, unless I got it wrong
a5a25af
to
561db64
Compare
ac6d0f5
to
654a938
Compare
:kind => "MiddlewareServerEap", | ||
:display_kind => "MiddlewareServerEap", | ||
:miq_id => mw_server_eap.id, | ||
:icon => match(/vendor-jboss-eap/), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this the same as above?
https://github.com/ManageIQ/manageiq-ui-classic/pull/2724/files#diff-f32f59cd3f168fe8e6bb029d5b543f20R34
here it's vendor-jboss-eap and there it's just vendor-eap
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, you are correct!
lgtm except for the question about regarding the icon diff in names |
654a938
to
b5d2ae6
Compare
tests are failing but it looks like an env issue? can you rerun them? |
Rerunning travis |
b5d2ae6
to
5962eae
Compare
Checked commits karelhala/manageiq-ui-classic@25a0da6~...5962eae with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0 spec/services/middleware_topology_service_spec.rb
|
@martinpovolny merge please? |
Add EAP and Wildfly to allowed types for MW topology (cherry picked from commit 7e2227a)
Gaprindashvili backport details:
|
Fixes missing EAP and Wildfly item in topology
When there are any providers with EAP or Wildfly server monitored, they were not displayed in topology view. This PR fixes such issue
UI changes
Before
After
Waiting on core
BZ
https://bugzilla.redhat.com/show_bug.cgi?id=1512549