On Wed, Nov 12, 2014 at 10:11:37AM +0000, GMail via smartos-discuss wrote: > So what we're really saying here is that your local machine is a fair > substitute for a 'enterprise' grade environment. I'm inordinately
We need to be careful here. SmartOS, the standalone single-node OS demo, is naturally limited by its single-node nature. While you could create and use an LX-branded zone on this single node just like you could create and use a normal zone on this single node, you'll always be limited by the single-node nature of that system. SmartOS is also the OS and hypervisor stack used in SmartDataCenter (SDC), which is *not* single-node. I am not interested in debating the myriad definitions of "enterprise", but SDC is designed to provide management and provisioning across hundreds or thousands of physical nodes per headnode. One can, and many of us do, use SDC in exactly those kinds of environments to provide highly available services. > impressed with your local machine in that case. I get the benefits of > using the ABI to provide the sorely lacking security and other > features to the abortion that is linux but seriously no one else sees > the danger and the false castles in the sky were building by assuming > what I package in my Mac is ready for deployment in an enterprise > environment? I work in info sec at the moment and I would not only get I don't think we're asserting anything about how you choose to package and deploy your software. Yes, it's convenient and easy for development to take something you made on your laptop and throw it into a development environment (managed by SDC, or perhaps a standalone SmartOS host) using Docker. For some very small companies, that might be how they choose to enter production, too. I personally wouldn't do that, of course, and if you look at how Joyent actually builds and deploys our own software internally (which you can now get a sense of by looking at things like imgapi, imgadm, MG, and the various tools that are part of SDC), you'll see that we don't either. One could certainly construct a similar set of tools and processes around the creation of Docker images for deployment into staging and production environments. Nothing that we're doing forces you down either path, and I think the Docker folks would say the same. Please note as well: everything we're talking about here is optional. If you distrust LX, use a normal zone. If you don't like the SmartOS environment, use KVM and run whatever OS you like. If you don't like Docker, don't use it. If you don't want to deploy developer-built images into production, then by all means don't. We're providing mechanism here, not policy, while not foreclosing on reasonable policy choices. That's what a platform *should* do. Professional operations teams absolutely have an essential place in this world, just as they always have, and creating rigourous policies, processes, and tooling to provide a solid production environment remains a key role. We're giving you a sound, rigourously engineered platform on which to do that. ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
