You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Microsemi is the steward of Smart Array technology now, they've started down the path of de-branding tools and products (no longer "HP" or "HPE", after all).
The day will come eventually where you'll find a Smart Array in a Dell box (for example). It wouldn't make much sense to leave the current Smart Array plugin as-is when that starts to happen.
Just an FYI that I will take on the responsibility of making the necessary changes here. Please let me know if anyone has any concerns about this going forward. Also, would we want to create a "new" plugin to start, and eventually remove the old "hpsa" plugin branches once we're confident that they're not necessary? Might be the easiest way to migrate away slowly.
The text was updated successfully, but these errors were encountered:
joehandzik
changed the title
De-brand "HP Smart Array" to "Smart Array:
De-brand "HP Smart Array" to "Smart Array"
Nov 9, 2016
I think that sounds like a reasonable plan. I've been tied up in another project lately, but let me see if I can carve out some time to get this done in the next week or two.
Since Microsemi is the steward of Smart Array technology now, they've started down the path of de-branding tools and products (no longer "HP" or "HPE", after all).
The day will come eventually where you'll find a Smart Array in a Dell box (for example). It wouldn't make much sense to leave the current Smart Array plugin as-is when that starts to happen.
Just an FYI that I will take on the responsibility of making the necessary changes here. Please let me know if anyone has any concerns about this going forward. Also, would we want to create a "new" plugin to start, and eventually remove the old "hpsa" plugin branches once we're confident that they're not necessary? Might be the easiest way to migrate away slowly.
The text was updated successfully, but these errors were encountered: