Quicksearch
Events
13.10 - 15.10 - Horizons EMEA
Trusted Ad
Blower Door Test
Luftdichtigkeitsmessung für Gebäude Raum Hamburg ab 160 € excl. MwSt
www.m-tectum.de
Luftdichtigkeitsmessung für Gebäude Raum Hamburg ab 160 € excl. MwSt
www.m-tectum.de
Kategorien
- Apple
- iPhone
- Aviation
- Bahn
- Begriffe des Lebens
- Blogosphere
- Braindump
- Business Travel
- CANBOX
- CeBIT
- CEC
- del.icio.us
- Fundsache
- General
- i hate sundays
- Kochen
- Mindfuck
- Movies
- Music
- On Benchmarketing
- Persoenliches Pech
- Photographie
- policy of ...
- Privacy
- Recommended Blogs
- Security
- Solaris
- Strange Days
- Sun
- suncec2007
- Technology
- The IT Business
- Toolbox
- Travel
- Work
Is hypervisor based virtualisation the correct way?
Monday, April 14. 2008
Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
The killer-feature of hypervisors is live migration ... and maybe running different OS patchlevels.
Otherwise hypervisors waste too much resources (at least for I/O)
Otherwise hypervisors waste too much resources (at least for I/O)
I don´t think about Live Migration as a killer feature. Live Migration creates his own class of problems like uncontinious time and on really loaded systems live migration isn´t an easy nor short task.
hypervisors like vmware and virtual box are cool for testing and such, but for production? no way. zones, jails and such is what i use.
things that require live migration should be clustered anyways. hardware and firmware level support needs to evolve for useful virtualization.
things that require live migration should be clustered anyways. hardware and firmware level support needs to evolve for useful virtualization.
Are you referering to zones, of which best practice of patching is to delete and recreate them?
Yeah, it´s one of the best practices. Better than patching every vm on it´s own... and as the patching problem is solvable (or will disappear as such a problem, when the patchin process speeds up), the problem of having to patch each VM on it´s own isn´t solvable by the nature of this virtualisation.
The problem: Most people think of zones, as they are a static thing, but unlike VMs you can create a zones within seconds. You do not install a OS, you install an application execution environment. As soon you´ve seperated the os and application it is more efficient to simply throw away a zone and installing a new one.
The problem: Most people think of zones, as they are a static thing, but unlike VMs you can create a zones within seconds. You do not install a OS, you install an application execution environment. As soon you´ve seperated the os and application it is more efficient to simply throw away a zone and installing a new one.
yes, that sucks. but if you look at nexenta, you see that it is possible to patch them easy and fast. i dont know if ips is the solution for solaris or if the patching issue will be fixed without it. from the technical view, it should not be that big problem to speed up patching with the current system.
what i did is isolating app data from the os and scripting the setup of the zones.
what i did is isolating app data from the os and scripting the setup of the zones.
Pretty much both is happening. But we can´t change much of the old patching because of the compatibility guarantees for Solaris 10 and later.
IPS will solve that nicely for the Opensolaris reference distribution from sun.
And by the way: Since the last version of Solaris you can liveupgrade Solaris 10 with non-global zones. The tip with deleting/creating zones is pretty much from the time when this feature wasn´t available.
IPS will solve that nicely for the Opensolaris reference distribution from sun.
And by the way: Since the last version of Solaris you can liveupgrade Solaris 10 with non-global zones. The tip with deleting/creating zones is pretty much from the time when this feature wasn´t available.
The LKSF book
The book with the consolidated Less known Solaris Tutorials is available for download here
Web 2.0
Contact
Networking
open.bc
LinkedIn
Facebook
My photos
- mail: joerg@c0t0d0s0.org
- icq: 144000169
- Me, myself and I
- openBC
- My del.icio.us
- c0t0d0s0@twitter
- c0t0d0s0@last.fm
- wiki@c0t0d0s0
- c0t0d0s0.org Gadget Shop
Networking
open.bc
My photos
Syndication
Comments
about Fangorn found a new home
Thu, 28.08.2008 11:42
I called it fangorn (sindarin for Treebeard) because it´s th e oldest active machine in my home office.
Thu, 28.08.2008 11:42
I called it fangorn (sindarin for Treebeard) because it´s th e oldest active machine in my home office.
is call
ed niacin. about Fangorn found a new home
Thu, 28.08.2008 09:08
Writing this comment on a Sun Ultra6 with 2x450MHz und 2 GB RAM. It is a fine hardware.
Thu, 28.08.2008 09:08
Writing this comment on a Sun Ultra6 with 2x450MHz und 2 GB RAM. It is a fine hardware.
about MAID, ZFS and some further thoughts ...
Thu, 28.08.2008 01:06
There is another aspect of MAI D, when it is done properly, w hich is the design of a physic al enclosure for the dis [...]
Thu, 28.08.2008 01:06
There is another aspect of MAI D, when it is done properly, w hich is the design of a physic al enclosure for the dis [...]
about MAID, ZFS and some further thoughts ...
Wed, 27.08.2008 22:36
I'm not particularly convinced by MAID either. The little I' ve looked at it, they try to k eep the discs alive by d [...]
Wed, 27.08.2008 22:36
I'm not particularly convinced by MAID either. The little I' ve looked at it, they try to k eep the discs alive by d [...]
Getaggte Artikel
AMD Apple avs Bahn Blogging Blogosphere braindump Business Travel CeBIT cec cec2006 CMT del.icio.us deutsch dtrace fliegen Fundsache General Hamburg IBM i hate sundays Intel iscsi jumpstart Links Linux lksf Mindfuck Movies Music Musik Niagara Opensolaris Opteron Photographie policy of ... Politik Security Solaris storage Sun suncec2007 sunw t1 The IT Business Ultrasparc ultrasparc t1 Wirtschaft Work ZFS
Blog Administration
Buttons
