[Vserver] add new interface/ip to runnig server without restart
Hi Guys, simple question - I have an Apache running inside a vServer and now must add a new IP Adress to it. So i edited thte interface section in the configs as usual. Is there a way to commit these changes / activate the new IP Adresse without restarting the vServer ? Oliver -- Diese Nachricht wurde digital unterschrieben oliwel's public key: http://www.oliwel.de/oliwel.crt Basiszertifikat: http://www.ldv.ei.tum.de/page72 smime.p7s Description: S/MIME Cryptographic Signature ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
RE: [Vserver] solaris containers/zones
What we need here is PR too. If someone here knows how to create press releases and distribute them it would be good for the adoption of the project. But there are fundamental differences between Xen and vserver. Xen allows different Operating systems to run on the same server, now only linux and I think freebsd. Vserver only allows linux. The uppoint of vserver is that the kernel is shared wich means lower memory footprint. I think unification also reduces needed memory. I have not been here for a long time, have you guys implemented virtual ethernet devices per vserver like freevps? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory (Grisha) Trubetskoy Sent: Friday, June 24, 2005 4:50 AM To: vserver@list.linux-vserver.org Cc: [EMAIL PROTECTED] Subject: RE: [Vserver] solaris containers/zones On Fri, 24 Jun 2005, Mike Tierney wrote: As much as I like Vservers (we use them on 2 of our Production servers!!) it looks like the Xen project (open source virtual machine software) IS getting LOTS of media coverage and attention/resources from vendors (Novell, IBM, Sun, HP, Redhat, etc). This is called PR. If you read this, you'll have a better idea of what's going on here: http://www.pycon.org/data/95/pycon-20050325-1-0900-95-ike.mp3 Xen was funded by commercial research money (from Microsoft and Intel IIRC) with the intent of turning it into a commercial venture, which is what Xensource is. All this buzz is to a large degree artificially generated to support the venture. Apparently the current version (v2) isn't that great but the next version (due out in August) sounds like a huge leap forward. And longhorn will just totally kick ass, so I heard! :-) Grisha ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] add new interface/ip to runnig server without restart
simple question - I have an Apache running inside a vServer and now must add a new IP Adress to it. So i edited thte interface section in the configs as usual. Is there a way to commit these changes / activate the new IP Adresse without restarting the vServer ? I do it like this: I vserver sth enter and then /etc/init.d/apache restart, this way the enter session gets new IP, and when I start apache it inherits the new IP. You should do this for ssh and other services that are supposed to use new IP too. -- Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 The good Christian should beware of mathematicians, St Augustin ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] chcontext / vcontext different behavoir when joining a context ID.
Hi, While testing vcontext to remove dependencies on deprecated chcontext (chcontext-compat) in my own Python scripts to handle vservers, I was wondering why vcontext either create new context ID (--create) *or* switch to an existing ID (--migrate), but doesn't allow to specify an ID, and create if it don't already exist and otherwise just join it, just like chcontext do actually (sort of --create-or-migrate). I mean, creating context ID on the fly if we try to join it. What's the rationale behind that ? I can just change the kernel patch to support that.. but I guess there is a particular reason for this behavior. I could also try first to --migrate then try --create if that fail, but it's not atomic. Maybe I'm missing something (but I found nothing in Wiki about that.) -- Frédéric Jolliton ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] chcontext / vcontext different behavoir when joining a context ID.
On Sat, Jun 25, 2005 at 09:52:36PM +0200, Frédéric Jolliton wrote: Hi, While testing vcontext to remove dependencies on deprecated chcontext (chcontext-compat) in my own Python scripts to handle vservers, I was wondering why vcontext either create new context ID (--create) *or* switch to an existing ID (--migrate), but doesn't allow to specify an ID, and create if it don't already exist and otherwise just join it, just like chcontext do actually (sort of --create-or-migrate). I mean, creating context ID on the fly if we try to join it. What's the rationale behind that ? that a context usually want's some setup (i.e. flags, ccaps, bcaps, whatever) when created but before the first process (init comes to mind) joins ... but you can 'emulate' this by doing the create and if it fails the migrate ... I can just change the kernel patch to support that.. but I guess there is a particular reason for this behavior. I could also try first to --migrate then try --create if that fail, but it's not atomic. it was never atomic, and it will never be atomic :) Maybe I'm missing something (but I found nothing in Wiki about that.) HTH, Herbert -- Frédéric Jolliton ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Virtual Cluster Question
Dear Vserver Developement Team, we are using linux-vserver as an isp for hosting services, we have made several tests with enbd incl. fr1 patch for redundant storage servers. Now we are beginning to create a virtual grid platform based on linux-vserver. With entering and leaving virtual machines on several host machines temporally. I currently work on this project to fix build clusters free of hardware or other dependencies. My question: What are the possibilities of using linux-vserver virtual machines with loadbalancers. Roundrobin, direct routing or nat? We use as a cluster reseller direct routing with mac address rewrite for loadbalancing. The loadbalancer has a vip and the realservers have the same ip as loopback alias. The answers of the realservers are done via eth0. so it should be possible to Fix this with binding two ip addresses on the virtual machines, the loopback alias And the realserver address?! Thank you for your answers Tom Eschler ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Virtual Cluster Question
On Sun, 26 Jun 2005, Hans Eschler wrote: What are the possibilities of using linux-vserver virtual machines with loadbalancers. Roundrobin, direct routing or nat? We've had succesfully set up direct server return load-balancing, where vservers were on different physical machines. Direct server return means that the loadbalancer uses mac to send a packet which is then accepted by a server's kernel because the destination IP exists on the loopback interface. E.g. if the VIP is 1.2.3.4, then on every load balanced server you configure 1.2.3.4 on the loopback. Since loopbacks aren't visible from outside, there is no conflict. So for vserver, we used the dummy interfaces as the VIPs. There was a trick we had to do to alter the default ARP behaviour: echo 1 /proc/sys/net/ipv4/conf/eth0/arp_ignore Without this eth0 would answer even for the IP that's on the dummy interface. This was done with 1.9.x vserver. I haven't looked at how 2.0 deals with interfaces yet, I have a suspicion it might even be easier if we have a private loopback interface for every vserver. Grisha ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
RE: [Vserver] solaris containers/zones
On Sat, 25 Jun 2005, Ehab Heikal wrote: Xen allows different Operating systems to run on the same server, now only linux and I think freebsd. Vserver only allows linux. The uppoint of vserver is that the kernel is shared wich means lower memory footprint. I think unification also reduces needed memory. I'd say the key advantage of vserver is the ability to access what's inside the vserver from the host. With xen you cannot see what's inside a virtual machine from the host, nor can you access its files, which makes it very difficult to administer efficiently. Grisha ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
