Some of what the differences involve the departures SmartOS has taken from the more generic implementation of zones, while the networking confusion involves the implementation of virtual networking (crossbow) for > Solaris 10. These are the biggest departures from Solaris 10 and they are both wonderful!
The `vmadm` command abstracts out much of what is happening under the covers when making a zone. It also integrates some nice features like published datasets. For an idea of what is happening behind the scenes, you can check out the OmniOS docs (http://omnios.omniti.com/wiki.php/GeneralAdministration#CreatingZones). This describes the more vanilla implementation of zones, and it will give you an idea how `diadm` creates a vnic for it to use. What is really great about having a vnic for each zone is that you no longer need to worry about the global zone default route issue that prevented you from creating zones on a variety of networks with S10. You can think of this as you would the Solaris 10 “exclusive” nic-> zone binding, except the NIC is virtual and sharing a common physical port and media (igb0 in your case). This OmniOS documentation will give you a good idea of what is happening with the virtualized networking (http://omnios.omniti.com/wiki.php/GeneralAdministration#Networking). These are the `diadm` and `ipadm` commands that you will need to use in place of the more traditional `ifconfig`. Unless your use case requires you to use both tagged and untagged interfaces, there is really no longer any reason you would not want to run all your vnics on the same interface. I hope this helps. Please let me know if any of this was unclear. Cliff > On Mar 1, 2016, at 4:33 PM, John Thurston <[email protected]> wrote: > > We run a few Solaris 10 SPARC servers with about 60 zones. We use mulitple > NICs, IPF, ZFS increments to create off-host copies, and scripts to move > zones between hosts. Looking over SmartOS, I suspect it would meet 80+ > percent of the business need we're currently meeting with Solaris. > > To check it out, I've put SmartOS an X4270 server and am poking at it. The > experience is leaving me feeling a bit like a country bumpkin walking into > the city for the first time. I can sort of find my way around, and tools like > zoneadm and zfs are still there, but it looks like I'm supposed to be working > at a more abstracted layer with vmadm. > > In my old world, I'd plumb one of my physical NICs with ifconfig for shared > use by several zones, create a dataset with zfs and mount it, define a zone > with zonecfg, install and boot it with zoneadm, zlogin to the console to > config it, and then turn it over to the customer who would ssh into it. I > assume I could still do all of this, but I also assume this ain't the way > it's done here. > > Where do I go to learn the right way? > I've been looking at the SmartOS wiki ( https://wiki.smartos.org/x/7IYL and > https://wiki.smartos.org/x/i4IL ) but I seem to be failing at some > fundamental level. For example, I wanted to create a zone on something other > than global's NIC (igb0). So I thought I defined a nic_tag "zone_nic1" using > the MAC of igb1, but all I get from vmadm is > Invalid nic tag "zone_nic1" > > Can anyone take pity on an unwashed Solaris user and point me in the right > direction? > > -- > Do things because you should, not just because you can. > > John Thurston 907-465-8591 > [email protected] > Enterprise Technology Services > Department of Administration > State of Alaska > ------------------------------------------- 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
