King

updated

12 years ago

K

King

4 Apprentice

•

1435 Posts

•

4077 Points

0

1422

June 17th, 2014 03:00

VPLEX/VE

Hi

VPLEX/VE has become in GA, but Where can you download document and Virtuak appliance for VPLEX/VE.


Also, is there an evaluation license?


Thanks


  • garyo

    89 Posts

    922

    0

    Posted July 1st, 2014 21:00

    VPLEX/VE is now GA as of June 26, 2014.

    Support Link is here:

    https://support.emc.com/products/34146_VPLEX-Virtual-Edition

    Gary

  • cedricq

    1 Message

    922

    0

    Posted June 25th, 2014 11:00

    I asked the same question to one of my local contacts in France some weeks ago, and the answer is still : VPlex/VE is NOT really in GA. In fact it has been announced, but not yet released. We can hope a real GA by the end of June/first weeks of July.

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    922

    0

    Posted July 2nd, 2014 12:00

    I hope someone will fix service life widget on left side of the page which usually shows date until which product is supported (right now it shows date since when product is GA).

  • garyo

    89 Posts

    922

    0

    Posted July 2nd, 2014 13:00

    Just so you know, it shows like that on the VE page (and VPLEX VS2 page) because there is no end of service dates defined (yet, anyways.)  So it can only show the start.

    Check say the VPLEX VS1 page https://support.emc.com/products/262_VPLEX-VS1 and it's end of primary support is August 31, 2017 and thus the widget shows as one would expect.

    Gary

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    922

    0

    Posted July 2nd, 2014 13:00

    Gary, I'm referring to link in your previous message where link for VE is and not VS1.  If end date is not determined yet, I would expect "date - TBD" format instead of "start date" only to keep it aligned with rest of the support pages by product. I'm quite sure some date can be put there as nowadays lack of end date (which can be changed at later stage) also may indicate lack of clear roadmap.  I personally don't care as this is more or less stepping stone phase for vipr (in my personal view though you can use it as standalone module for sure), but others might care more about it.