This topic has been closed for comments
第1/2页
+9
你好John,
Do you have any information on the upgrade process? Are we looking at a rather simple One-Click? Also, will we be able to use Nano-server, and if so is the process the same as an normal One-Click upgrade?
亲切的问候
Do you have any information on the upgrade process? Are we looking at a rather simple One-Click? Also, will we be able to use Nano-server, and if so is the process the same as an normal One-Click upgrade?
亲切的问候
+1
大家好,
你好乔恩,
Windows Server 2016 RTM关于群集安装的任何更新?
我们有一个NX-3000,我们希望使用最后一个Windows Server操作系统重新安装一个集群。
Can we have some documentation about fresh install ?
After a crash we have previously need full reinstall cvm with a nutanix support operator and it's not a OneClick process .
非常感谢您的宝贵帮助。
Hava a nice day.
问候。
你好乔恩,
Windows Server 2016 RTM关于群集安装的任何更新?
我们有一个NX-3000,我们希望使用最后一个Windows Server操作系统重新安装一个集群。
Can we have some documentation about fresh install ?
After a crash we have previously need full reinstall cvm with a nutanix support operator and it's not a OneClick process .
非常感谢您的宝贵帮助。
Hava a nice day.
问候。
+1
你好乔恩,
Thanks for your prompt reply.
Sounds Bad for my team.
当我阅读兼容性指南时,我可以看到:
Windows Server 2016 RTM已发布Oct12,是10月12日 + 3个月?
您认为2017年1月会很好吗?
如果您有有关时间表的任何信息,我得到了:)
Thanks you so much Jon
Have a nice day.
问候。
Thanks for your prompt reply.
Sounds Bad for my team.
当我阅读兼容性指南时,我可以看到:
- Microsoft Major/Minor版本(如2012 R2)得到了立即支持,质量保证在软件发布日期后的90天内有资格
Windows Server 2016 RTM已发布Oct12,是10月12日 + 3个月?
您认为2017年1月会很好吗?
如果您有有关时间表的任何信息,我得到了:)
Thanks you so much Jon
Have a nice day.
问候。
请记住,Windows 2016通常是一个很大的更新,并且在架构上进行了许多更改(例如Nano等)。
The general thinking is we're going to try to get a Tech Preview out in the first 90 days, so people can start using it in non-production settings. Full support may take a little longer than that, simply because we want to get it right for production setups, rather than rush it in.
这种思想与我们要交谈的大多数客户也是如此,因为其余的生态系统都不匆忙(例如备份供应商,抗病毒,监测剂和其他相关代理商)需要先赶上。
The general thinking is we're going to try to get a Tech Preview out in the first 90 days, so people can start using it in non-production settings. Full support may take a little longer than that, simply because we want to get it right for production setups, rather than rush it in.
这种思想与我们要交谈的大多数客户也是如此,因为其余的生态系统都不匆忙(例如备份供应商,抗病毒,监测剂和其他相关代理商)需要先赶上。
+7
当Asterix 5.0可用时,我们是否有时间范围?
does it has any fixes for Hyper-V
如果我们现在要在3个节点群集上部署2012R2,我们是否可以通过从群集中提取节点,重新成像到2016年并再次加入群集来升级到2016年?
does it has any fixes for Hyper-V
如果我们现在要在3个节点群集上部署2012R2,我们是否可以通过从群集中提取节点,重新成像到2016年并再次加入群集来升级到2016年?
RE Hyper V upgrade
TBD,我会在他们的最初2美分的情况下向工程询问
RE Asterix Release Date
十个目标是接下来的30天或更短。我的感觉是,这将是“青少年”名称的一天,但仍然是TBD。它是一个大型,大的发行版,因此有很多非工程作品需要同时排队。
重新修复了Hyper-V
与任何版本一样,我们一直在修复和增强事物,您是否想要针对Hyper-V进行固定/增强的特定内容?
TBD,我会在他们的最初2美分的情况下向工程询问
RE Asterix Release Date
十个目标是接下来的30天或更短。我的感觉是,这将是“青少年”名称的一天,但仍然是TBD。它是一个大型,大的发行版,因此有很多非工程作品需要同时排队。
重新修复了Hyper-V
与任何版本一样,我们一直在修复和增强事物,您是否想要针对Hyper-V进行固定/增强的特定内容?
+7
“ Tenative Target是接下来的30天或更短的目标。我的感觉是,这将是“名字”的“青少年”的一天,
那是十一月的“青少年”还是十二月的“青少年”?
Nothing in particular for hyper-v but wodnering how we will be able to upgrade to 2016 with a 3 node cluster. 2016 has a rolling upgrade feature but we would still be missing out on some features like REFS etc as the cluster storage would have already been formatted.
http://myvirtualcloud.net/?p=8310
希望第2部分将具有一些特定于V的特定功能
我们还可以搬到AHV进行新的设置,但即使这样,我们也会为我们带来挑战:
A 3 tier infrastrucure has it downside but I can't see how this would be possible with a 3 nodes nutanix cluster (Actually even with more nodes)
RIght now we have 3 Servers running Hyper-v and on a Power outage, after 30 minutes, we live migrate all VMS from one server and then shut it down to give us more runtime, after another 30 minutes, the same scenario happens until there is only 20-30 minutes left and then all vms are turned off and the last server is then shut down as well. When power is restored, all servers are then powered up and re-balanced automatically without me having to ping a Server or Storage. Doing this with CVM would be suicide i reckon...
那是十一月的“青少年”还是十二月的“青少年”?
Nothing in particular for hyper-v but wodnering how we will be able to upgrade to 2016 with a 3 node cluster. 2016 has a rolling upgrade feature but we would still be missing out on some features like REFS etc as the cluster storage would have already been formatted.
http://myvirtualcloud.net/?p=8310
希望第2部分将具有一些特定于V的特定功能
我们还可以搬到AHV进行新的设置,但即使这样,我们也会为我们带来挑战:
- 使用我们的Veeam备份服务器执行备份的能力
- using our APC UPS to shutdown the servers cleanly (Still haven't find an easy and documented way to do that from an APC UPS)
A 3 tier infrastrucure has it downside but I can't see how this would be possible with a 3 nodes nutanix cluster (Actually even with more nodes)
RIght now we have 3 Servers running Hyper-v and on a Power outage, after 30 minutes, we live migrate all VMS from one server and then shut it down to give us more runtime, after another 30 minutes, the same scenario happens until there is only 20-30 minutes left and then all vms are turned off and the last server is then shut down as well. When power is restored, all servers are then powered up and re-balanced automatically without me having to ping a Server or Storage. Doing this with CVM would be suicide i reckon...
RE Asterix Date
我看到你开了我的幽默笑话。在内部,我们正在瞄准11月的月份,但这是一个非常非常大的发行版,因此我们希望正确地进行。
RE Hyper-V 2016
我已经将其转发给我们的PM for Hyper-V,因此他可以更详细地回应CC雷蒙
Here's my 2 cents: Keep in mind that Hyper-V 2016 is an absolutely massive new release from Microsoft, which will fundamentally have different considerations for how Nutanix integrates. There are many things to consider; however, the largest is Microsoft's DDA, which is their version of PCI Passthrough.
As you might know, Nutanix uses direct PCI Passthrough of the SAS controller on ESXi, AHV, and XenServer. Hyper-V does not have this same capability in 2012 R2, so we take a different approach currently. We've been clamoring for PCI passthrough for years, to standardize the disk connectivity approach between all four hypervisors we support, and Microsoft is now allowing this in 2016.
也就是说,与ESXI和AHV不同,它不仅是一个简单的传递,还需要访客OS内核来支持启用DDA的设备,因此我们不得不修补这些设备,这需要一些资格时间。
这只是我们必须努力正确启用2016年的一个低悬挂示例。
RE Hyper-V specific features
您在寻找具体的东西吗?还是要系统做今天不做的事情?我很乐意代表您调查或倡导,请告诉我。
re veeam + ahv
过去,我们谈到了这一点,球在Veeam的法庭上。
RE APC + AHV
APC需要做一些工作来增强其PowerChute网络关闭产品,这确实是这样做的最好方法。我会请我们的联盟人们看看我们是否已经与他们合作。
RE Shutdown sequence
Yes, that would be a challenge with Nutanix (or most SDS products), as in your 3 node cluster, its N+1, so you'd be able to do that with one node, then the whole thing would need to be gracefully shutdown.
我看到你开了我的幽默笑话。在内部,我们正在瞄准11月的月份,但这是一个非常非常大的发行版,因此我们希望正确地进行。
RE Hyper-V 2016
我已经将其转发给我们的PM for Hyper-V,因此他可以更详细地回应CC雷蒙
Here's my 2 cents: Keep in mind that Hyper-V 2016 is an absolutely massive new release from Microsoft, which will fundamentally have different considerations for how Nutanix integrates. There are many things to consider; however, the largest is Microsoft's DDA, which is their version of PCI Passthrough.
As you might know, Nutanix uses direct PCI Passthrough of the SAS controller on ESXi, AHV, and XenServer. Hyper-V does not have this same capability in 2012 R2, so we take a different approach currently. We've been clamoring for PCI passthrough for years, to standardize the disk connectivity approach between all four hypervisors we support, and Microsoft is now allowing this in 2016.
也就是说,与ESXI和AHV不同,它不仅是一个简单的传递,还需要访客OS内核来支持启用DDA的设备,因此我们不得不修补这些设备,这需要一些资格时间。
这只是我们必须努力正确启用2016年的一个低悬挂示例。
RE Hyper-V specific features
您在寻找具体的东西吗?还是要系统做今天不做的事情?我很乐意代表您调查或倡导,请告诉我。
re veeam + ahv
过去,我们谈到了这一点,球在Veeam的法庭上。
RE APC + AHV
APC需要做一些工作来增强其PowerChute网络关闭产品,这确实是这样做的最好方法。我会请我们的联盟人们看看我们是否已经与他们合作。
RE Shutdown sequence
Yes, that would be a challenge with Nutanix (or most SDS products), as in your 3 node cluster, its N+1, so you'd be able to do that with one node, then the whole thing would need to be gracefully shutdown.
I sent him and the PM team an email to get some clarification on this one. I'll bet "yes", but again, this is a massive massive massive shift on Microsoft's part, I have a feeling this is going to be tricky. Looking forward to what Engineering pulls off.
word from product management is that yes, this is the plan to support rolling upgrades from 2012 to 2016. Since the feature isn't done yet, we'll have to wait a bit to see exactly what that looks like
+7
我也是!
特别是如果必须将容器格式化为“一开始”的参考!我认为不可能从NTFS升级到REF,而不会销毁群集,因此我们为什么也在等待。
Now if AHV had VEEAM support we wouldn't be waiting
特别是如果必须将容器格式化为“一开始”的参考!我认为不可能从NTFS升级到REF,而不会销毁群集,因此我们为什么也在等待。
Now if AHV had VEEAM support we wouldn't be waiting
重新文件系统
嗯,什么?该容器现在不使用NTF格式化,也不是任何其他Windows文件系统,因此即使我们愿意,我们也无法使用Refs格式化。
The container is presented, from a protocol perspective, with SMB3. The actual formatting on the filesystem is invisable to windows.
就像从运行XFS或ZFS文件系统的Linux框或类似的内容中进行SMB共享,协议和基础文件系统不会耦合在一起。
RE Veeam
您的句子相反...更像Veeam获得了AHV的支持,让您阅读您的内容。简而言之,我们在等他们,而不是相反。
嗯,什么?该容器现在不使用NTF格式化,也不是任何其他Windows文件系统,因此即使我们愿意,我们也无法使用Refs格式化。
The container is presented, from a protocol perspective, with SMB3. The actual formatting on the filesystem is invisable to windows.
就像从运行XFS或ZFS文件系统的Linux框或类似的内容中进行SMB共享,协议和基础文件系统不会耦合在一起。
RE Veeam
您的句子相反...更像Veeam获得了AHV的支持,让您阅读您的内容。简而言之,我们在等他们,而不是相反。
+7
理解!我认为该容器是作为存储到Windows群集的存储空间的,我们需要将其格式化!这是有道理的,只要Nutanix将支持集群升级升级,那么我们就不必再等待时间并部署2012 R2并升级了。如果我们这样做,与2016年完整安装相比,我们会缺少从升级到2012 R2的任何功能吗?
它作为存储群呈现给群集,但其SMB3卷,而不是需要格式化的块设备。
至于升级等,尚未定义,我们知道我们要支持滚动升级,但是正如我在先前的一篇文章中提到的那样,我们尚未完成2016年的工作,因此我们将有更多的清晰度去那里。
至于升级等,尚未定义,我们知道我们要支持滚动升级,但是正如我在先前的一篇文章中提到的那样,我们尚未完成2016年的工作,因此我们将有更多的清晰度去那里。
Mikasa- 感谢您伸出援手,对您就可以了。
这仍然是一项正在进行的工作。微软改变了我们需要处理的一吨,因此我们花时间做对了。
与您的Nutanix帐户团队合作,以获取何时将其投射到降落的详细信息,但是在这个公共论坛中,我会简单地说,我们正在努力,试图将其推开,至少在Tech上至少在日历Q1 2017年结束时预览。所有日期都可能会根据内部进度进行更改,但以这种方式看起来。
这仍然是一项正在进行的工作。微软改变了我们需要处理的一吨,因此我们花时间做对了。
与您的Nutanix帐户团队合作,以获取何时将其投射到降落的详细信息,但是在这个公共论坛中,我会简单地说,我们正在努力,试图将其推开,至少在Tech上至少在日历Q1 2017年结束时预览。所有日期都可能会根据内部进度进行更改,但以这种方式看起来。
+1
any update on this thread in term of supportability?
+2
We're keen to see Hyper-V 2016 on the Nutanix platform aswell. Is this the best place be notified for updates / Tracking progress?
+1
支持Hyper-V 2016和Windows Server 2016的任何更新?如果说Hyper-V我们仍然继续使用2012版,我们可以将客户端作为MS Windows 2016吗?
desmondgooi这是我们目前的设置2012R2管理程序,除了SCVMM之外的所有内容,还需要2012年的时间,以与Nutanix平台一起播放。运行完美。
Very disapointed with the lack of updates regarding the 2016 Hypervisor support. We'd aimed to be up on 2016 from the get go as we foolishly belived the 90day statement when making the purchase.
Very disapointed with the lack of updates regarding the 2016 Hypervisor support. We'd aimed to be up on 2016 from the get go as we foolishly belived the 90day statement when making the purchase.
第1/2页
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">