DFM 3.8 on Vsphere 4.0

[hheuze]

Hi Team,

Could you tell me if this configuration is supported ?

DFM 3.8

VSphere 4.0

VM : windows or Linux

Regarding the IMT, it seems to be ok à ESX 3.0.1 minimum release, but nothing about Vsphere.

--> 3063     VMware ESX 3.0.1 is the minimum requirement.

Thanks,

Hugues

[sharaf]

DFM 3.8 is not qualified with VSphere 4.0.

3.8 is qualified with VMWare Infrastructure 3 and 3.5, Standard and Enterprise Editions

DFM 4.0 is being qualified with Vsphere 4.0

[hheuze]

OK thanks.

DFM 4.0 target is frebuary 13th?

Thanks,

Hugues

[sharaf]

Yes its being planned for Mid Feb

[RichardSopp]

Any plans to have the upcoming 3.8.1 release qualified with VSphere 4.0?

[prasads]

Any plans to have the upcoming 3.8.1 release qualified with VSphere 4.0?

No such plans for 3.8.1 release.

[RichardSopp]

Why would you ever not qualify with vSphere 4.0?

I'm assuming 3.8.1 is going to be the next GA version of Operations Manager (historically that's been the case as 3.7.1 is classified as a GA release with 3.8 being FCS).

Why would you not qualify your latest GA version of management software with the "latest" version of vmware? Considering VSphere has been available for download since May 21 2009, its somewhat lazy to not qualify a GA version of your management software with a hypervisor that's been out for over 7 months?

Are there any plans for with your latest round of hypervisor qualification to remove the caveats that VMotion and HA are not supported ( as discussed in http://communities.netapp.com/message/12025#12025)?

[prasads]

3.8.1 is just like any patch release, with bug fixes for 3.8 release.

The difference being it has gone through more QA cycles than any normal patches.

And we don’t normally support any new features in a patch release. Only bug fixes.

4.0 is almost around the corners & expected to go live by mid-Feb (just a few weeks after 3.8.1)

Please be patient.

[RichardSopp]

With the greatest respect, you're missing the point.

Not all NetApp customers will want to upgrade to a new version of OM purely to get support for vSphere hosting of the application. Additionally not all customers want to run the risk of deploying First Customer Ship releases of storage management software.

[adaikkap]

If we add new features doesnt it again become a FCS instead of a .1 release.

Let see if we can break the myth of your statement.

"Additionally not all customers want to run the risk of deploying First Customer Ship releases of storage management software."

with 4.0

Regards

adai

[RichardSopp]

How is testing, validating and then stating you are going to support a new hypervisor version in a .1 release of your application adding new functionality and returning the .1 to a FCS status?

You shouldn't have to make any changes in your application to support a newer release of a hypervisor where you have already qualified previous release.

You just need to spend the cycles qualifying it and thus how is qualification adding new functionality?