| --- | Log | opened Sat Feb 17 00:00:35 2007 |
| 00:59 | |-| | symerian [~logbot@phoenix.nic.fr] has quit [Remote host closed the connection] |
| 01:03 | |-| | symerian [~logbot@phoenix.nic.fr] has joined #xen |
| 01:36 | |-| | Basic_py [~Basic@gatekeeper.real-time.com] has quit [Quit: Leaving] |
| 01:59 | |-| | visik7 [~visi@host13-167-dynamic.54-82-r.retail.telecomitalia.it] has joined #xen |
| 02:12 | |-| | mejlholm [~mejlholm@212.242.125.18] has joined #xen |
| 02:17 | |-| | KriP [kp@yancey.unixworld.dk] has joined #xen |
| 02:31 | |-| | jerone_ [~jerone@adsl-71-145-133-165.dsl.austtx.sbcglobal.net] has quit [Quit: jerone_] |
| 02:39 | |-| | visik7 [~visi@host13-167-dynamic.54-82-r.retail.telecomitalia.it] has quit [] |
| 02:50 | |-| | visik7 [~visi@host13-167-dynamic.54-82-r.retail.telecomitalia.it] has joined #xen |
| 03:00 | |-| | DoberMann_ changed nick to DoberMann |
| 03:09 | |-| | KriP [kp@yancey.unixworld.dk] has quit [Read error: Connection reset by peer] |
| 03:11 | |-| | KriP [~kp@yancey.unixworld.dk] has joined #xen |
| 03:46 | |-| | mejlholm [~mejlholm@212.242.125.18] has quit [Quit: Leaving] |
| 03:59 | |-| | symerian [~logbot@phoenix.nic.fr] has quit [Remote host closed the connection] |
| 03:59 | |-| | symerian_ [~logbot@192.134.4.91] has joined #xen |
| 04:07 | |-| | sputhenp [~sputhenp@202.80.58.210] has joined #xen |
| 05:02 | |-| | mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has joined #xen |
| 05:04 | |-| | symerian_ [~logbot@192.134.4.91] has quit [Write error: connection closed] |
| 05:05 | |-| | symerian [~logbot@192.134.4.91] has joined #xen |
| 05:05 | |-| | mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has quit [] |
| 05:09 | |-| | mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has joined #xen |
| 05:46 | |-| | cableman [~cableman@3e6b7156.rev.stofanet.dk] has joined #xen |
| 05:52 | |-| | mastermind [~mastermin@mastermind.kaltenbrunner.cc] has quit [Quit: Client exiting] |
| 05:52 | |-| | mastermind [~mastermin@mastermind.kaltenbrunner.cc] has joined #xen |
| 05:54 | |-| | pvanhoof [~pvanhoof@d54C0EE14.access.telenet.be] has joined #xen |
| 07:20 | |-| | mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has quit [Quit: Leaving] |
| 07:25 | |-| | mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has joined #xen |
| 07:39 | |-| | kalden [~kalden@fac34-3-82-231-26-11.fbx.proxad.net] has joined #xen |
| 08:11 | |-| | symerian [~logbot@192.134.4.91] has left #xen [] |
| 09:35 | |-| | cableman [~cableman@3e6b7156.rev.stofanet.dk] has quit [Quit: Leaving] |
| 09:39 | |-| | aliguori [~anthony@cpe-70-112-17-156.austin.res.rr.com] has joined #xen |
| 10:03 | |-| | mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has quit [Quit: Leaving] |
| 11:22 | |-| | cdub [~chrisw@dsl092-074-097.bos1.dsl.speakeasy.net] has quit [Ping timeout: 480 seconds] |
| 11:44 | |-| | trondaso [~trondaso@228.80-203-76.nextgentel.com] has joined #xen |
| 12:00 | |-| | mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has joined #xen |
| 12:12 | |-| | mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has quit [Quit: Leaving] |
| 12:21 | |-| | sputhenp [~sputhenp@202.80.58.210] has quit [Quit: Leaving] |
| 12:34 | |-| | Pivert [~pivert@user-85-201-95-140.static.tvcablenet.be] has quit [Ping timeout: 480 seconds] |
| 13:13 | |-| | Pivert [~pivert@user-85-201-95-140.static.tvcablenet.be] has joined #xen |
| 13:30 | |-| | trondaso [~trondaso@228.80-203-76.nextgentel.com] has left #xen [] |
| 13:48 | <bluefox> | Does Xen have load balancing built-in, or do I need a third party monitoring tool that looks for overloaded hardware nodes and executes a live migration? |
| 13:51 | <brendan> | it's not built in |
| 13:51 | <bluefox> | okay |
| 13:51 | <bluefox> | That's alright though, it's easy enough to monitor from the outside. |
| 13:52 | <bluefox> | Does XenSource supply software to do it? |
| 13:52 | <bluefox> | Or do I have to roll my own |
| 13:52 | <riel> | you'll have to roll your own |
| 13:52 | <riel> | I don't think anybody's done it yet |
| 13:54 | <bluefox> | Kay |
| 13:54 | <bluefox> | it supplies instant live migration though so no big deal |
| 13:56 | |-| | ivan_ [~ikelly@skynet.skynet.ie] has quit [Quit: leaving] |
| 13:57 | <bluefox> | Looks like Xen can load balance on one hardware node though |
| 13:57 | <riel> | yes |
| 13:58 | <bluefox> | if I allocate 500MB of my 512 to Dom0, and use 200MB; and then load a 256MB DomU; it suddenly rips 256MB off my Dom0, because it's available. |
| 14:28 | <waldi> | read the main config |
| 14:41 | <bluefox> | I need a clustering network storage system though |
| 14:41 | <bluefox> | something that can distribute storage across hardware nodes in such a way that if a hardware node fails, nothing is lost |
| 14:43 | <brendan> | drbd might work, I guess |
| 14:44 | <bluefox> | nice, network Raid-1 basically. |
| 14:45 | [~] | bluefox was more thinking distributed with parity and N-levels of redundancy. |
| 14:45 | <bluefox> | I can't think of a way to do it asynchronously though |
| 14:46 | <brendan> | I don't know what does that |
| 14:46 | <bluefox> | I don't think anything does |
| 14:47 | <bluefox> | I'm thinking, if I have a server with 2000GB, another with 1200GB, another with 2500GB, it should be able to distribute data across them and manage redundancy so I can lose 1 host; if I have 15 servers, I should be able to tell it to be durable against loss of 3 hosts. |
| 14:47 | <bluefox> | This is going to lead to me actually designing something to do this isn't it :/ |
| 14:47 | <bluefox> | Except I'll never implement it :/ |
| 14:47 | <brendan> | good luck recovering if you lose the server with 2500GB |
| 14:48 | [~] | bluefox is not sure how to negotiate that |
| 14:49 | <bluefox> | Perhaps parity across 1200GB; then parity across 800; that leaves like 500 unprotected though. |
| 14:50 | <bluefox> | somehow it would have to ensure that data does not exist "on one host only" but rather prove that any given data has N paths each independent of each other for so many hosts etc etc etc |
| 14:50 | <bluefox> | things that someone who is actually smart would have to figure out ;/ |
| 14:53 | |-| | rw23 [squid@wwwbox.uni-mb.si] has quit [Quit: Leaving] |
| 15:17 | |-| | aw [~awilliam@c-24-9-84-32.hsd1.co.comcast.net] has quit [Quit: Leaving] |
| 15:37 | |-| | KriP [~kp@yancey.unixworld.dk] has quit [Read error: Connection reset by peer] |
| 16:14 | |-| | DoberMann changed nick to DoberMann[ZZZzzz] |
| 16:48 | <bluefox> | http://bluefox.kicks-ass.org/stuff/bluefox/xen_virt/xen_virt.html |
| 16:49 | <bluefox> | work in progress |
| 17:05 | |-| | aw [~awilliam@c-24-9-84-32.hsd1.co.comcast.net] has joined #xen |
| 17:21 | |-| | dendrite [~ph@dsl092-150-203.wdc2.dsl.speakeasy.net] has joined #xen |
| 17:21 | |-| | hollisb [~hollisb@user-0vvdf2d.cable.mindspring.com] has joined #xen |
| 17:25 | <dendrite> | Are there any docs that discuss xen specific vulnerabilities, e.g., breaking out of the vm, etc? |
| 17:52 | <icblenke> | bluefox: have you looked at Ceph, Glusters, GFarm, Cleversafe, or any other network distributed filesystem? |
| 17:53 | <bluefox> | nope |
| 17:53 | <icblenke> | drbd is great for failover pairs. drbd-0.8 lets you do master/master replication and live failover rather easily. |
| 17:54 | <icblenke> | They all boil down to FUSE based frontends to a "metadata" cluster and a "storage" cluster. |
| 17:56 | <icblenke> | we're looking at them now, evaluating them to see which is best for our needs. |
| 17:57 | <icblenke> | heading out for a while. I'd like to hear your evaluations. the last time I looked at Xen and ATAoE was over a year ago. http://ian.blenke.com/xen |
| 17:57 | <icblenke> | bbl. |
| 18:14 | <bluefox> | No idea, I'm no expert in the field; I'm just absorbing this information as rapidly as I can |
| 18:14 | <bluefox> | <-- brain is a relational database, associates everything with everything |
| 18:17 | <murb> | does ATAoE work with xen now days? |
| 18:21 | <bluefox> | murb: it's a block device exported over a network, looks like an IDE drive |
| 18:22 | <bluefox> | murb: ATAoE + NFS + Xen -> ATAoE cluster :) |
| 18:22 | <murb> | bluefox: i know what it is, before there were bugs which prevented it working with the xen network devices. |
| 18:23 | <bluefox> | ah |
| 20:26 | <icblenke> | there are still some irritating behaviors with ATAoE I'd love to hear if they've addressed: like having targets drop out causing the need to unload/reload the ataoe initiator to recover when the target is restored. |
| 21:00 | |-| | visik7 [~visi@host13-167-dynamic.54-82-r.retail.telecomitalia.it] has quit [Read error: Connection reset by peer] |
| 21:00 | |-| | visik7 [~visi@host13-167-dynamic.54-82-r.retail.telecomitalia.it] has joined #xen |
| 22:08 | |-| | hollisb [~hollisb@user-0vvdf2d.cable.mindspring.com] has quit [Quit: Leaving] |
| 22:32 | |-| | cdub [~chrisw@216-99-217-87.dsl.aracnet.com] has joined #xen |
| 22:58 | |-| | VS_ChanLog [~stats@ns.theshore.net] has left #xen [Rotating Logs] |
| 22:58 | |-| | VS_ChanLog [~stats@ns.theshore.net] has joined #xen |
| 23:26 | |-| | DoberMann_ [~james@AToulouse-156-1-32-64.w81-49.abo.wanadoo.fr] has joined #xen |
| 23:28 | |-| | DoberMann[ZZZzzz] [~james@AToulouse-156-1-41-175.w90-16.abo.wanadoo.fr] has quit [Ping timeout: 480 seconds] |
| --- | Log | closed Sun Feb 18 00:00:23 2007 |
