In this episode, Sean Donahue looks back at the tech stories from 2022. The highs, lows, and everything in between. What story did we miss? Which stories surprised you in 2022? Please leave your comments below.<\/p>

Have a wonderful 2023!<\/p>

<\/oembed><\/p>

\u00a0<\/p>

If you have any questions, feel free to reach out to me on\u00a0Twitter<\/a>\u00a0and if you haven't already done so, make sure you are subscribed to the show wherever you consume podcasts.<\/p>

\u00a0<\/p>","id":41482,"featuredImage":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/f38aec9c-1b9f-472b-8bc4-5177f93527b7_thumb.png","label":"Blog","replyCount":0,"views":88,"post":{"id":63100,"author":{"id":7898,"url":"\/members\/aluciani-7898","name":"aluciani","avatar":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/icon\/200x200\/77accf89-4f79-48be-81e6-c2ac5507e29b.png","userTitle":"Chevalier","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"name":"Chevalier","color":"#660099"},"userLevel":7},"content":"

In this episode, Sean Donahue looks back at the tech stories from 2022. The highs, lows, and everything in between. What story did we miss? Which stories surprised you in 2022? Please leave your comments below.<\/p>

Have a wonderful 2023!<\/p>

<\/oembed><\/p>

\u00a0<\/p>

If you have any questions, feel free to reach out to me on\u00a0Twitter<\/a>\u00a0and if you haven't already done so, make sure you are subscribed to the show wherever you consume podcasts.<\/p>

\u00a0<\/p>","url":"\/community-blog-154\/nutanix-community-podcast-2022-year-in-review-41482?postid=63100#post63100","creationDate":"2023-01-03T14:40:38+0000","relativeCreationDate":"3 days ago"},"contentType":"article","type":3,"likes":3,"hasCurrentUserLiked":false},"phrases":{"Forum":{"{n} year|{n} years":"{n} year|{n} years","{n} month|{n} months":"{n} month|{n} months","{n} day|{n} days":"{n} day|{n} days","{n} hour|{n} hours":"{n} hour|{n} hours","{n} minute|{n} minutes":"{n} minute|{n} minutes","just":"just now","{plural} ago":"{plural} ago"}}}">

为什么只有一个容器？

s
徽章 +2
我看不到关于为什么单个容器是最佳实践的解释。有多个容器会导致开销更多（内存使用以外）？



似乎一个明显的选择是将您的OS VM放置在涂上的容器中几乎相同以最大化空间节省。然后将任何用户数据VDisks放在压缩容器中。



只是寻找一些关于为什么这不是一个好主意的输入。

    \n

    \nIt seems like an obvious choice would be to put your OS VM's that are virtually identical in a deduped container to maximize space savings. Then put any user data vDisks in a compressed container.

    \n

    \nJust looking for some input on why this is not a good idea.","quoteUsername":"stever3901","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    4个答复

    b
    UserLevel 4
    徽章 +17
    它应该是一个存储池而不是容器



    您应该有多个容器取决于您的要求

    每个容器级别部署螺纹和压缩燃烧器



    容器就像一个文件夹，可为您的管理程序提供数据存储

    \n

    \nYou should have multiple container depend on your requirements

    \nDedupe and Compression fetures are deployed per Container level

    \n

    \nContainer is like a folder providing datastore to your Hypervisor","quoteUsername":"bezeddin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    乔恩
    秩
    UserLevel 6
    徽章 +29
    嘿，史蒂夫，

    很乐意在本地或在Webex上同步，但现在是我的2美分。



    如果需要的话，您可以拥有大量的容器，但是就像过去的Lun/卷一样，它往往会使事情变得更加迷惑和复杂。



    尤其是在AHV世界中，拥有一个容器只会使生活变得轻松。另外，在4.5 ++中，您可以同时运行所有存储功能，并且系统只是“算出”（即缩放，压缩，擦除编码等）



    至少，我的吻原理（以及咨询的全面建议）至少是在线压缩的。这是魔术，而且坦率地说，很棒。
    乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！

    \nHappy to sync up locally or on webex if you'd like, but here's my 2 cents for now.

    \n

    \nYou can have a ton of containers if you'd like, but like the LUN's\/volumes of yesteryear, it tends to make things more obfuscated and complicated.

    \n

    \nEspecially in the AHV world, having one container just makes life easy. Also, in 4.5++, you can run all storage feature simultaneously, and the system just \"figures it out\" (i.e Dedupe, Compression, Erasure Coding, etc)

    \n

    \nAt minimum, my KISS principle here (and what consulting recommends across the board) is at least turn on in-line compression. It's magic, and quite frankly, works darn great.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    s
    徽章 +2
    为什么一个容器“尤其是在AHV世界中”更好？
    乔恩
    秩
    UserLevel 6
    徽章 +29
    在AHV世界中，从管理程序的角度来看，它所看到的只是VM的VM，每个VM都附有直接量（类似于VMW的VVOL）。



    该管理程序没有看到一个带有文件的通用数据存储，只有VM及其各自的磁盘。





    老实说，在AHV中，容器只是一个“策略对象”，而不是传统的卷或数据存储。这用于数据策略，例如压缩/dedupe以及AHV图像服务之类的东西。



    在现实世界中，我见过的AHV部署，由于所有这些都不是一个以上的容器。
    乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！

    \n

    \nThe hypervisor doesn't see one common datastore with files on it, just the VM's and their respective disks.

    \n

    \n

    \nHonestly, in AHV, the container is just a \"policy object\", rather than a traditional volume or datastore. This goes for data policies like compression\/dedupe, as well as things like the AHV Image Service.

    \n

    \nIn the real world AHV deployment's I've seen, its pretty rare to have more than one container because of all of this..","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    条款和条件
    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"}}}">
    Baidu