Re: [CentOS-virt] LVM mirror database to ramdisk
On Sat, 2016-01-23 at 09:27 -0600, Robert Nichols wrote: > On 01/22/2016 11:02 AM, Ed Heron wrote: > >I'm still running CentOS 5 with Xen. > > > >We recently replaced a virtual host system board with an Intel > > S1400FP4, so the host went from a 4 core Xeon with 32G RAM to a 6 core > > Xeon with 48G RAM, max 96G. The drives are SSD. > > > >I was recently asked to move an InterBase server from Windows 7 to > > Windows Server. The database is 30G. > > > >I'm speculating that if I put the database on a 35G virtual disk and > > mirror it to a 35G RAM disk, the speed of database access might improve. > > If that were running under Linux rather than Windows I'd suggest just > giving that extra 35GB to its kernel and letting its normal caching > keep everything in RAM. Whether Windows (7 or Server) would be clever > enough to do that is another question. Of course you could just let > the Linux host do the caching, but that runs the risk of other VMs > or host activity displacing some of that cache and affecting the > performance of your database VM. > Yes... You've got much of my thought process. The RAM disk mirror pre-loads the database into memory and forces it to stay in RAM. ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] LVM mirror database to ramdisk
On Fri, 2016-01-22 at 14:56 -0600, NightLightHosts Admin wrote: > On Fri, Jan 22, 2016 at 11:02 AM, Ed Heron <e...@heron-ent.com> wrote: > > I'm still running CentOS 5 with Xen. > > > > We recently replaced a virtual host system board with an Intel > > S1400FP4, so the host went from a 4 core Xeon with 32G RAM to a 6 core > > Xeon with 48G RAM, max 96G. The drives are SSD. > > > > I was recently asked to move an InterBase server from Windows 7 to > > Windows Server. The database is 30G. > > > > I'm speculating that if I put the database on a 35G virtual disk and > > mirror it to a 35G RAM disk, the speed of database access might improve. > > > > I use local LVM for my virtual disks with DRBD on top to mirror the > > disk to a backup server. > > > > If I change grub.conf to increase RAM disk size and increase host RAM, > > I could create a 35G RAM disk. > > > > I'd modify rc.local to add > > pvcreate /dev/ramdisk > > vgextend vg /dev/ramdisk > > lvconvert -m 1 --corelog vg/lv_database /dev/ramdisk > > > > Even with lv_database being 35G, it doesn't take long to activate the > > mirror. > > > > I haven't decided where to put the commands to turn off the lvm > > mirror. > > lvconvert -m 0 vg/lv_database > > vgreduce vg /dev/ramdisk > > pvremove /dev/ramdisk > > > > I haven't put this in real world use, yet. > > > > On it's face, this might speed up database access. Would we expect it > > to speed up database access in real world use? > > > > Should I document the process so others could know how to do this? I > > realize new documentation for CentOS 5 virtualization would be > > considered obsolete before I wrote it but I'm expecting to test CentOS 7 > > virtualization in the next few months and, when I am comfortable, I'd > > upgrade my 18 virtual hosts. I would update the documentation, at that > > time, as well. > > > I may not understand enough to understand what you are doing, you want > to actively mirror this with LVM or? Yes, in a test environment, I am mirroring a Logical Volume with a RAM disk to increase the perceived speed of the disk. I'm expecting to convert a live guest to this type of setup, this weekend. I was asking 2 questions. 1. Should I expect a significant increase in speed in a real world environment? With enough RAM, a good caching system will eventually do a similar function. This is almost like pre-loading a cache. 2. Should I document the process for others? I'm using CentOS 5 now, which is on it's way out, but I would update the documentation to include CentOS 7 when I upgrade my servers. ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] LVM mirror database to ramdisk
On Fri, 2016-01-22 at 16:17 -0600, NightLightHosts Admin wrote: > > Ed Heron <e...@heron-ent.com> wrote: > > Yes, in a test environment, I am mirroring a Logical Volume with a RAM > > disk to increase the perceived speed of the disk. I'm expecting to > > convert a live guest to this type of setup, this weekend. > > > > I was asking 2 questions. > > 1. Should I expect a significant increase in speed in a real world > > environment? With enough RAM, a good caching system will eventually do > > a similar function. This is almost like pre-loading a cache. > > 2. Should I document the process for others? I'm using CentOS 5 > > now, > > which is on it's way out, but I would update the documentation to > > include CentOS 7 when I upgrade my servers. > > > > See this is where I was confused. Would not the LVM mirror have to > sync all the time with the disk anyways? Yes, but it isn't that simple. One copy of the mirror would be on a physical disk. The other copy of the mirror would be on RAM disk. Since data in RAM doesn't generally survive reboot, the RAM piece would need to be turned off before shutdown and created on startup. > Is there something about LVM mirroring that can handle disks of > different speeds? With newer LVM, there appears to be some settings that might help with that a bit. With this older verion, I'd be hoping that the next available disk would handle each request. If the physical disk takes longer to deal with the writes, the RAM disk might be the one that is available most of the time. I'd much prefer a method of pre-filling a 35G cache but I saw a reference to creating a disk mirror in RAM and decided to explore it. ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] LVM mirror database to ramdisk
On Fri, 2016-01-22 at 16:59 -0600, NightLightHosts Admin wrote: > On Fri, Jan 22, 2016 at 4:54 PM, Ed Heron <e...@heron-ent.com> wrote: > > Yes, but it isn't that simple. One copy of the mirror would be on a > > physical disk. The other copy of the mirror would be on RAM disk. > > Since data in RAM doesn't generally survive reboot, the RAM piece would > > need to be turned off before shutdown and created on startup. > > > >> Is there something about LVM mirroring that can handle disks of > >> different speeds? > > > > With newer LVM, there appears to be some settings that might help with > > that a bit. With this older verion, I'd be hoping that the next > > available disk would handle each request. If the physical disk takes > > longer to deal with the writes, the RAM disk might be the one that is > > available most of the time. > > > > I'd much prefer a method of pre-filling a 35G cache but I saw a > > reference to creating a disk mirror in RAM and decided to explore it. > > > > Can you post the results of your test when you get it working? Absolutely, I'll share my real world results. I'm happy that I'm not the only person interested in the technique. I'm a little disappointed somebody isn't telling me there is a much simpler method of putting my database in RAM. The technique is only useful in a situation where the server has gobs of RAM so it might only apply to a small subset of users but it might speed up database access. And since it is being done by the virtual host, the guest doesn't need to know anything about it. This keeps guest complexity down. Also, I don't have as much Windows knowledge as I have Linux knowledge so it was easier for me to implement under Linux. ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] LVM mirror database to ramdisk
I'm still running CentOS 5 with Xen. We recently replaced a virtual host system board with an Intel S1400FP4, so the host went from a 4 core Xeon with 32G RAM to a 6 core Xeon with 48G RAM, max 96G. The drives are SSD. I was recently asked to move an InterBase server from Windows 7 to Windows Server. The database is 30G. I'm speculating that if I put the database on a 35G virtual disk and mirror it to a 35G RAM disk, the speed of database access might improve. I use local LVM for my virtual disks with DRBD on top to mirror the disk to a backup server. If I change grub.conf to increase RAM disk size and increase host RAM, I could create a 35G RAM disk. I'd modify rc.local to add pvcreate /dev/ramdisk vgextend vg /dev/ramdisk lvconvert -m 1 --corelog vg/lv_database /dev/ramdisk Even with lv_database being 35G, it doesn't take long to activate the mirror. I haven't decided where to put the commands to turn off the lvm mirror. lvconvert -m 0 vg/lv_database vgreduce vg /dev/ramdisk pvremove /dev/ramdisk I haven't put this in real world use, yet. On it's face, this might speed up database access. Would we expect it to speed up database access in real world use? Should I document the process so others could know how to do this? I realize new documentation for CentOS 5 virtualization would be considered obsolete before I wrote it but I'm expecting to test CentOS 7 virtualization in the next few months and, when I am comfortable, I'd upgrade my 18 virtual hosts. I would update the documentation, at that time, as well. ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] LVM mirror database to ramdisk
On Fri, 2016-01-22 at 17:39 -0600, NightLightHosts Admin wrote: > Ed Heron <e...@heron-ent.com> wrote: > > Absolutely, I'll share my real world results. I'm happy that I'm not > > the only person interested in the technique. I'm a little disappointed > > somebody isn't telling me there is a much simpler method of putting my > > database in RAM. The technique is only useful in a situation where the > > server has gobs of RAM so it might only apply to a small subset of users > > but it might speed up database access. And since it is being done by > > the virtual host, the guest doesn't need to know anything about it. > > This keeps guest complexity down. Also, I don't have as much Windows > > knowledge as I have Linux knowledge so it was easier for me to implement > > under Linux. > > > See, > > This is where I get confused again, which type of database is it? It is a Customer Relationship Management database running under InterBase on Microsoft Windows Server. However, because the database server is a virtual machine, it doesn't matter. The technique could be useful for speeding up any disk-centric activity. ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Preferred method of provisioning VM images
On Tue, 2014-06-10 at 17:21 +0100, Lars Kurth wrote: Hi all, following the discussion on about documentation, I was wondering whether we need to look at a standard way in which we recommend how to provision images for VMs. Am starting this with a Xen hat, but the discussion should not be specific to this. There are a number of options, but all have some trade-offs == #1 virt-install == Advantages: similar to KVM Disadvantages: may cause weird issues / confusion with people switching back to xl. The core issue is that with the current version of xen and libvirt, this only works with xm (when xl is used, this can create some undefined behavior). However as we have seen in some recent threads on this list, people tend to mix which can cause problems. ... I've chosen the virt-install method on CentOS 5 precisely because it is like KVM. I was hoping it would fulfill the promise of being hypervisor agnostic. I'm hoping it continues to be available on future versions of CentOS with Xen. Though it is a waste of resources, I make all my virtual machines, Linux and MS Windows alike, fully virtualized. I can then move any of the VM's with the same virt-install --import or virsh dumpxml/edit/virsh define process. When moving a VM, usually the only thing I have to do outside of virt-install/virt-manager is add acpi/, apic/ or pae/, which can be done with virsh edit. I don't know why some of my virtual servers need them and other don't but I have higher priority things to think about. I'm the only technical support person and I don't work 24/7. The graphical interface of virt-manager makes it possible for non-tech people to see what is running and see consoles to restart any misbehaving VM's (usually MS Windows VM's). I have completely eliminated my use of xm. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-docs] CentOS5 OpenVPN cheatsheet
Searching for a detail of OpenVPN configuration, I noticed my draft of an OpenVPN for CentOS5 cheat sheet popped up as the second result. I didn't realize my drafts would be searchable, but that's OK, it looks relatively complete. I'd work out updates for CentOS 6 7, if I used them, but I don't, yet. Anyway, should I leave it where it is or should we move it from http://wiki.centos.org/EdHeron/CentOS5OpenVPN to http://wiki.centos.org/HowTos/CentOS5OpenVPN ? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Question about memory upper limit
My 32 bit CentOS 5 servers only report a little over 14G. On Thu, 2013-01-10 at 09:20 -0300, Héctor Herrera wrote: Oh yes, it will recognize until 16 Gb. I made the test a few months ago. 2013/1/10 Gerald Nathan gerald.airfo...@gmail.com I guess it should On Thu, Jan 10, 2013 at 11:56 AM, Dae James daeda...@126.com wrote: My CPU is 64 bit, but my CentOS is 32 bit version. Does my system support memory larger than 4G? __ Dae James ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs -- Saludos Héctor Herrera Anabalón Egresado ICCI UNAP Servicio Arquitectura Galatea - Oficina Técnica http://www.galatea.cl Miembro USoLIX Victoria Registered User #548600 (LinuxCounter.net) ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] How do I boot a xen domu into run level 1
On Fri, 2012-09-21 at 12:05 -0400, m...@tdiehl.org wrote: ... If I use virt-manager to make changes to the configuration, I see the changes in /etc/xen/vm_name I am now wondering if there is another config file some where that virt-manager is writing to. ... You could also run virsh edit vm_name ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] How do boot a xen domu into run level 1
You could loop mount the messed up disk on the host or you could mount the messed up disk on another DomU and change it. On Thu, 2012-09-20 at 08:58 -0400, m...@tdiehl.org wrote: Hi, I have a C5.8 machine with several DomU's. I fubared the fstab on one of them and I need to get it into single user mode. Does anyone know how to do that? I tried adding single to the extras line in /etc/xen/machine_name but it still tries to start in level 3. To make things worse, the root partition is on LVM. Alternatively, does anyone know how to access the image from DomU? I tried to use kpartx but when I run VGscan, I do not get the lvm activated. Regards, ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] How do boot a xen domu into run level 1
On Thu, 2012-09-20 at 12:03 -0400, m...@tdiehl.org wrote: On Thu, 20 Sep 2012, Ed Heron wrote: You could loop mount the messed up disk on the host or you could mount the messed up disk on another DomU and change it. Yes, I thought about mounting it on another DomU right after I sent the message to the list and that worked. It even activated the lvm partitions. I am still wondering why I cannot get the thing into Run level 1 though. I see numerous people on the net talking about just adding single to the extras line in the xen config file but that does not work. Thanks for the help. Regards, You could set the default runlevel in /etc/inittab when the disk is mounted on another VM... ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-docs] Access request to page TipsAndTricks/ApacheVhostDir
On Thu, 2012-07-12 at 13:07 -0600, Ed Heron wrote:
On Wed, 2012-07-11 at 19:40 -0400, Brian Mathis wrote:
The use of mv -v ...{,_} is too clever for this kind of educational
document, and should be changed to spell out the full mv command. I
get what you're doing there, but the purpose of the document is not to
teach clever uses of bash, it's to make it obvious to people that
you're renaming the file. It will trip up the flow of reading for all
but the most knowledgeable users, and users who don't understand it
will be totally lost.
I'm not trying to be clever, I just don't like to type it twice if I
can avoid it and the typing the higher the chance for a typo. I don't
have a problem having both forms. I'll add it and see what you think.
In most documents and scripts, I usually spell out the short form
options as well, such as using --verbose. Short forms save you
typing, but documentation should not trip people up if they don't know
what the option means.
Normally, I expect, if people don't understand a command, they will
refer to the man page for the command. However, to my constant
disappointment, I understand that many people aren't looking for long
term knowledge improvement, they are looking for a recipe to blindly
follow.
Also, I find the use of _ to be obtuse and highly error prone if one
were to actually run a server that way. It's far more obvious to use
disabled, which makes it very clear that those items are disabled.
It may work for you but only because that's a convention you came up
with so you're used to it, but we're not in dos 8.3 days with
filenames, so why not be more descriptive?
Having both forms should make it plain that people can use any
convention they wish. System administration is not a fixed target.
Like many things, there are many ways to accomplish the same result.
When approaching a system that someone else is administrating, we should
try to maintain the existing conventions instead of forcing our own
ideas onto a server for which we are not the primary responsible party.
In section 6.4, is there a reason not to make a vhosts.conf file
that contains the Include in the in the conf.d/ directory, instead
of appending to the httpd.conf, or do you run into ordering issues
there? I try to avoid changing the distro files if possible.
Sections 6 and 7 are optional. There are certainly arguments against
customization. In the past, upgrades might have replaced all files
including configuration files. In that case, creating a vhosts.conf
file in the conf.d directory to separate the directive would have been a
must. However, the Linux distributions I have used for the past decade
or so have avoided replacing existing configuration files, expecting
they might be customized.
That said, I like the suggestion. It would allow for the virtual host
files to be packaged into an RPM file that could be installed on
multiple web hosts.
❧ Brian Mathis
I made the changes I've described about a week ago. Brian, does that
satisfy your concerns? Does anybody else agree with Brian? Have the
changes I've made make it easier to read the document?
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Access request to page TipsAndTricks/ApacheVhostDir
On Wed, 2012-07-11 at 19:40 -0400, Brian Mathis wrote:
The use of mv -v ...{,_} is too clever for this kind of educational
document, and should be changed to spell out the full mv command. I
get what you're doing there, but the purpose of the document is not to
teach clever uses of bash, it's to make it obvious to people that
you're renaming the file. It will trip up the flow of reading for all
but the most knowledgeable users, and users who don't understand it
will be totally lost.
I'm not trying to be clever, I just don't like to type it twice if I
can avoid it and the typing the higher the chance for a typo. I don't
have a problem having both forms. I'll add it and see what you think.
In most documents and scripts, I usually spell out the short form
options as well, such as using --verbose. Short forms save you
typing, but documentation should not trip people up if they don't know
what the option means.
Normally, I expect, if people don't understand a command, they will
refer to the man page for the command. However, to my constant
disappointment, I understand that many people aren't looking for long
term knowledge improvement, they are looking for a recipe to blindly
follow.
Also, I find the use of _ to be obtuse and highly error prone if one
were to actually run a server that way. It's far more obvious to use
disabled, which makes it very clear that those items are disabled.
It may work for you but only because that's a convention you came up
with so you're used to it, but we're not in dos 8.3 days with
filenames, so why not be more descriptive?
Having both forms should make it plain that people can use any
convention they wish. System administration is not a fixed target.
Like many things, there are many ways to accomplish the same result.
When approaching a system that someone else is administrating, we should
try to maintain the existing conventions instead of forcing our own
ideas onto a server for which we are not the primary responsible party.
In section 6.4, is there a reason not to make a vhosts.conf file
that contains the Include in the in the conf.d/ directory, instead
of appending to the httpd.conf, or do you run into ordering issues
there? I try to avoid changing the distro files if possible.
Sections 6 and 7 are optional. There are certainly arguments against
customization. In the past, upgrades might have replaced all files
including configuration files. In that case, creating a vhosts.conf
file in the conf.d directory to separate the directive would have been a
must. However, the Linux distributions I have used for the past decade
or so have avoided replacing existing configuration files, expecting
they might be customized.
That said, I like the suggestion. It would allow for the virtual host
files to be packaged into an RPM file that could be installed on
multiple web hosts.
❧ Brian Mathis
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Access request to page TipsAndTricks/ApacheVhostDir
On Wed, 2012-07-11 at 10:42 -0400, Brian Mathis wrote: Requesting access to edit page TipsAndTricks/ApacheVhostDir Looking to make some small edits for clarity. ❧ Brian Mathis Yay, somebody read it! What are you suggesting? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] Basic shared storage + KVM
On Tue, 2012-06-19 at 18:21 +0200, Andrea Chierici wrote: Hi, I am trying to set up a shared iscsi storage to serve 6 kvm hypervisors running centos 6.2. I export an LVM from iscsi and configured virt-manager to see the iscsi space as LVM storage (a single storage pool). I can create space on this LVM storage pool directly from virt-manager and I am already running a couple of sample VMs, that do migrate from one hv to the other. This configuration has a problem: when I create a new LV on the LVM storage pool to host a new VM, the HV where I am creating the virtual machine on sees the LV as status available, while the others see it as NOT available. In some circumstances this can crash libvirtd. To fix this I generally issue: vgchange -an; sleep 1; vgchange -ay but sometimes this fails with error: device-mapper; create ioctl failed: Device or resource busy and anyway it's not very convenient to issue this command on every node every time a new LV is created. Can anyone suggest a solution (if any) to this problem? Keep in mind that the basic concept behind this approach is to keep things as simple as possible. I don't want to configure a cluster or any other complicated tool to simply be able to migrate VMs from one HV to another. Thanks, Andrea Please help me understand why you are doing it this way? I'm using Xen with integrated storage, but I've been considering separating my storage from my virtual hosts. Conceptually, we can ignore the Xen/KVM difference for this discussion. I would imagine using LVM on the storage server then setting the LVs up as iSCSI targets. On the virtual host, I imagine I would just configure the new device and hand it to my VM. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-docs] http://www.centos.org/docs
On Sat, 2012-04-21 at 16:05 +0100, Karanbir Singh wrote: ... But, most of it can be automated isnt it ? and the docs are only ever updated once every 6 to 8 months. Its more of a case of someone taking the task up, and spending the day or two needed to get to grips with whats involved and doing 1 doc. We can then scale up the effort from there. Breaking inertia is key. I would say the RHEL docs are a starting point. The first step is to remove the RHEL logos and such. The next step is to change the pieces that don't apply and add any sections for stuff that isn't close. At that point, the docs become an animal completely separate from the RHEL docs. Future RHEL docs would then have to be diff'd to discover what changes they've made and decide if we wish to add their changes to CentOS docs. I can fantasize that RHEL might even check out our docs and see if any of our changes are worth adding back into their docs. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] http://www.centos.org/docs
On Sat, 2012-04-21 at 23:35 +0100, Karanbir Singh wrote: ... I'll setup a resource in .centos.org space that allows us ( and whoever wants to join the effort ) the ability to collaborate and share files. details in personal email, early on Monday morning Some sort of revision control system would be nice. Is it possible to export a set of pages from the wiki into a pdf or e-pub format? Having the wiki and docs go to my kindle when they are changed would be pretty cool. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] http://www.centos.org/docs
On Sat, 2012-04-21 at 21:29 -0300, Paul R. (Crunch) wrote: ...On 04/21/2012 08:38 PM, Ed Heron wrote: On Sat, 2012-04-21 at 23:35 +0100, Karanbir Singh wrote: ... I'll setup a resource in .centos.org space that allows us ( and whoever wants to join the effort ) the ability to collaborate and share files. details in personal email, early on Monday morning Some sort of revision control system would be nice. That's not a bad idea. Something like CVS. The wiki has the equivalent of a revision control. Is it possible to export a set of pages from the wiki into a pdf or e-pub format? I don't see why not. It should be easy enough to run some conversion utility on the finished HTML docs. Although it'll probably take some tweaking. It'd be better to pull the raw page(s) and build the book from that. Having the wiki and docs go to my kindle when they are changed would be pretty cool. True enough. There is already a subscription to changes feature of the wiki. It'd be interesting if the page could prepared and mailed with the notification. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] http://www.centos.org/docs
On Fri, 2012-04-20 at 14:44 -0300, Crunch wrote: ... 1) Why if the original document was licensed with an open commons license is the document being relicensed as an open publication license. I think Red Hat changed their license since that footer was written. 2) Why does the foot note say that you can't modify the document? open commons states that you can do anything you like to the document so long as it retains a reference to the original document and licensor. Assuming that one could actually distribute the documentation as I described in points (2) above: 1) Would it be right to relabel their documentation as CentOS after they worked so hard on it. 2) The howto documentation style seems to be more practical or have more utility. Although, more may be better when it comes to information. There are pieces of the RHEL manuals that reference pieces that don't exist in CentOS. RHN being one example. Changing those pieces makes sense. HowTos explain a process which is usually abbreviated for a specific or narrow use-case. Manuals can discuss theory and be a reference. The HowTos, as they exist, don't store well on an e-reader. The RHEL manuals are offered in an epub format in an apparent attempt to be stored on an e-reader or printed. If we change anything, we should change the graphics and re-distribute the changed version. After thinking about this, CentOS(your) project goals and KB's comments, maybe keeping the current style of http://www.centos.org/docs is not such a bad idea. Although I'm not to sure the foot note is in line with the original license. Regards, Paul R. I agree that modifying and subsequently maintaining the manuals is a rather large project. That isn't to say I'm advocating either for or against. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] routing problem with domU bridged to two networks
On Wed, 2012-03-07 at 20:41 +0200, Peter Peltonen wrote: As I received no response on the general CentOS list, I'll repost it here as the question is about Xen virtual machine routing. This is my network setup: http://pastebin.com/kyWpTQYU Lets assume my dom0's eth2 public ip is 1.2.3.33 and my dmz network 11.22.33.96/255.255.255.224 . I have created NAT from my LAN with iptables. You can see my /etc/sysconfig/iptables here: http://pastebin.com/1FqSTvPH And this is my dom0 routing table: http://pastebin.com/gNjTFHp5 My goal: To access NFS shares on a (non-virtualized) file server in the LAN network from the domU web server in the DMZ network. What I tried: I attached the domU to both bridges using this Xen config: vif = [ mac=00:0c:29:de:3a:fe,bridge=xenbr0,mac=00:0C:29:76:19:85,bridge=xenbr1 ] and then created two eth interfaces inside the domU mapping to the MAC addresses above, giving eth1 an IP from the DMZ (11.22.33.111) and giving eth2 an IP from the LAN (192.168.0.12). After this I mounted the NFS share from the file server (192.168.0.2). My problem: If my domU web server is connected to both LAN and DMZ using the two bridges xenbr0 and xenbr1, I can access the NFS share from the domU web server and everything else works as expected, except for one thing -- my workstations in the LAN cannot anymore access the web server: web pages do not open anymore and from the workstations I cannot ping the domU. If the web server domU is only connected to DMZ via xenbr0, the workstations can access it ok. Any advice what I am doing wrong and I could fix my setup? The postrouting command uses -o eth2. To NAT LAN requests to your DMZ web server, shouldn't you be using xenbr0? Though, I would bridge eth2, as well, and create a virtual firewall with eth0 (DMZ?), eth1 (LAN) and eth2 (PUB). I wouldn't want the Dom0 to be directly compromised if my firewall was compromised. Regards, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-docs] Grub Installation for CentOS 5 and 6 HowTo
On Fri, 2012-03-02 at 19:02 -0500, Yves Bellefeuille wrote: ... I couldn't figure out how to do the two internal links at the very bottom, so please fix that. ... I modified the internal links. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] wiki request
On Tue, 2012-02-14 at 09:36 +, Karanbir Singh wrote: On 02/10/2012 06:36 PM, Aaron Anderson wrote: Probably best if I started out with a complete OpenVPN tutorial. I also have good information about font rendering. ok, I've created: http://wiki.centos.org/AaronAnderson/OpenVPN under your homepage at http://wiki.centos.org/AaronAnderson ( you should have edit rights to both places ). Also, noticed that Ed had a OpenVPN page that seems to have started off, but been abandoned - Ed, can you confirm ? if so, please delete that page or mark it All -read, so it does not cause search result mixup. Ref: http://wiki.centos.org/EdHeron/OpenVPN Oops. I can confirm I got side-tracked. Maybe we can work together to complete the document. Aaron, does your process differ from what's included, so far, in my document? Karanbir, let me know if I've marked it appropriately to prevent search engines from finding it. I guess I should do that for any other partial draft documents? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] wiki request
On Tue, 2012-02-14 at 09:26 -0700, Ed Heron wrote: On Tue, 2012-02-14 at 09:36 +, Karanbir Singh wrote: Also, noticed that Ed had a OpenVPN page that seems to have started off, but been abandoned - Ed, can you confirm ? if so, please delete that page or mark it All -read, so it does not cause search result mixup. Ref: http://wiki.centos.org/EdHeron/OpenVPN Oops. I can confirm I got side-tracked. Maybe we can work together to complete the document. Aaron, does your process differ from what's included, so far, in my document? Karanbir, let me know if I've marked it appropriately to prevent search engines from finding it. I guess I should do that for any other partial draft documents? I tried a few ways of changing the rights. From your hint and looking at another page, it looks like I should do '#acl All:-read', but it doesn't let me because I'm not admin. I assume people in the admin group override any acl in a document. Would I lose access with this command? Shouldn't it be something like '#acl EdHeron:read,write,revert,delete,All:-read' Or does edit group override some of this. Should restricted access rights be standard for draft documents? To prevent them from being found by search engines but still accessible by creator, EditGroup and AdminGroup (and maybe all logged in users)? I've forgotten the name of the Wiki software we are using. Please remind me, so I could look there for docs relating to acl? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] wiki request
On Tue, 2012-02-14 at 18:07 +, Karanbir Singh wrote: if you are working on it - dont worry, once a final version gets moved into the howto's area - we can just setup redirects from this page. till such time just add a draft tag to the top of the page.. Mostly, I just needed a reminder it was there. QQThey laid off my staff about 2 years ago, so I've been rather busy/QQ I was working on a rewrite of the PXE documentation, too. How can I prevent my pages from competing with the existing page in search engines? Shall we consider the draft tag sufficient to warn potential searchers that my page might be incomplete? Aaron, my OpenVPN page was started before CentOS 6 was out. I haven't touched CentOS 6, yet. If you are going to focus on the CentOS 6 aspects, we could collaborate. Or, if they are sufficiently different, we could just specify version in the title. Or, certainly, you are welcome to fill in missing pieces in my draft... Whatever gets the job done. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] RFC: Install OpenVPN on CentOS 5
Please review http://wiki.centos.org/EdHeron/CentOS5OpenVPN ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] Setting up serial ports on kvm guests
On Tue, 2012-01-31 at 14:01 -0500, James B. Byrne wrote: CentOS-6.2 We have a dedicated CentOS-5.7 host used for fax reception and transmission that we wish to move to a CentOS-6.2 virtual guest instance. The CentOS-6.2 virtual host has a 4-port serial card installed. Consider replacing your multi-serial port card with a VoIP analog gateway and use a pre-rolled Asterisk with virtual faxmodems, like Elastix. Just make sure your codec is high enough quality. We used to receive faxes using a dedicated Linux box with a Comtrol Rocketport and an USRobotics MP8. We Converted to SIP trunks and managed to get our faxes in the SIP trunks, as well. This will remove the PCI pass-through from the equation. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Setting up serial ports on kvm guests
On Wed, 2012-02-08 at 13:29 -0500, James B. Byrne wrote: On Wed, February 8, 2012 11:06, Ed Heron wrote: On Tue, 2012-01-31 at 14:01 -0500, James B. Byrne wrote: CentOS-6.2 We have a dedicated CentOS-5.7 host used for fax reception and transmission that we wish to move to a CentOS-6.2 virtual guest instance. The CentOS-6.2 virtual host has a 4-port serial card installed. Consider replacing your multi-serial port card with a VoIP analog gateway and use a pre-rolled Asterisk with virtual faxmodems, like Elastix. Just make sure your codec is high enough quality. We used to receive faxes using a dedicated Linux box with a Comtrol Rocketport and an USRobotics MP8. We Converted to SIP trunks and managed to get our faxes in the SIP trunks, as well. This will remove the PCI pass-through from the equation. After a brief read this seems to me the approach we should take. Recently I have discovered more about irqs, timing delays, and the difficulties/impossiblities of switching hardware from vm instances than I ever wanted to know. Given that we have three dedicated fax lines and 6 voice is there any hardware that would you suggest for a 4 core x86_64 Intel based host system? We have looked at going completely to v/f-oip but I do not have the time to deal with those intricacies and get this move completed at the same time. So, for the nonce it appears that we would have to employ an FXO gateway to connect our existing POTS lines to the host. It might be OK to virtualize a fax server, but I wouldn't switch to a new voice tech and virtualize it at the same time. If you are interested in moving to a VoIP phone system, you should get familiar with how it works before adding the virtual component. Currently, I'm running a couple of locations using Elastix with dedicated hardware. One location supports 6 users with an Intel D845G integrated desktop board with a 1.7 Celeron and 1G RAM, so the hardware requirements are pretty low, but virtualized machines are not necessarily real-time. I would consider virtualizing it if I dedicated a server CPU and network card, but you'd need to find an external analog VoIP gateway that you are comfortable with. I'm currently using internal Digium cards for T1 and analog connectivity, but obviously I'd want to move to an external gateway or move to pure SIP before virtualizing to avoid having a PCI passthrough issue of my own. Just make sure that your phone line vendor is not using VoIP internally and handing you an emulated analog interface. I had quite a mess when I tried connecting an analog/VoIP external gateway to some emulated analog lines. The 2 analog emulations didn't quite mesh and I had miscellaneous dropped calls. The issue hurt my department's credibility and led to a longer implementation schedule for our VoIP project. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] server host keys for kvm clones
On Thu, 2012-01-05 at 15:05 +, Karanbir Singh wrote: ... Personally, I hate images. Provisioning from fresh is easy enough, fast enough and manageable enough that images are almost always either the wrong solution or a by-product requirement from a third party tool that does not understand provisioning ( hello, all those so-called-cloud solutions .. ) I feel this way too. However, many people espousing imaging are so adamant. I don't argue because it just isn't worth it. Whatever they feel comfortable with as long as I'm not responsible for the result. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] server host keys for kvm clones
On Thu, 2012-01-05 at 15:09 +, Karanbir Singh wrote: ... Keep in mind that you need to have your provisioning happen in a fairly secure environment itself, if you are going to add trust points on signatures like this - specially if they are 'generated' on demand. Other than installing from a separate network, which is difficult with multiple locations and virtual machines (creating them in a central place then transferring them across the Internet seems unwieldy), what steps can we take to secure the provisioning? ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] server host keys for kvm clones
On Thu, 2012-01-05 at 21:02 +0200, Manuel Wolfshant wrote: ... My colleagues from the engineering dept ( I am IT... ) have to use a commercial application which comes as 2 CD images plus 3 sets of 2 isos with updates. All of which have to be installed (at last theoretically ) one after the other and only via their own Java-based installer. Guess who is not going to rpm-ize the process of installing that 8*450 MB piece of wonderful software. Nice. The company I work for uses some MS Windows software where the vendor won't even give me install software. They insist the user must call them to install. The user must log into their website to get access to the install software. I don't have a log in, so I don't pre-install that software. The users complain to me and I refer them to the vendor. Yes, some vendors are annoying. It sounds like maybe you'd prefer clean installs but, due to real world compromises, you can't always do that. And by the way, there are 50% chances that this piece of software was used in the process of design of your phone. At least if the phone was engineered after 2000. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Transfer of LVM based guests
On Tue, 2011-11-29 at 15:51 -0500, James B. Byrne wrote: I am investigating the procedure to follow when moving a KVM guest instance from one host to another where the guest uses LVM as its storage. As a preliminary cut I have cobbled the following together from various sources located through Google searches: ... If you are moving the virtual disk, you can't run the virtual machine while you are moving it. Therefore, taking a snapshot (and removing it later) is superfluous. I use md5sum to give myself some extra re-assurance that a copy that big is accurate. Are the virtualization servers at the same location? How often do you move virtual machines? If your virtualization servers are in the same location, you might want to look into setting up a LAN for transferring virtual machine images. It would only take an extra network card in each virtualization server and a Gb Ethernet switch (or better). If you are interested in virtual disk replication, you might want to look at DRBD. It adds an extra layer to your storage, but allows for hot replication of disk space which would allow you to start a virtual machine on any virtualization server. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Should I switch and if so what is the procedure
On Wed, 2011-10-05 at 10:55 -0400, Rich wrote: Since the Xen and Linux kernel people have finally made peace and Xen is going to be included with the kernel, should I keep using the Xen virtual server with Centos or should I switch to KVM? I am running Centos 5.7 now. I guess the real question is can I still use Xen with Centos 6? The support end of life for CentOS 5 is listed as March 31, 2014 (http://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d). There isn't any pressure, at this point, to convert your VM hosts to CentOS 6 unless there is some feature you require. I doubt RH will add XEN support to RHEL 6. They don't like to add functionality to an existing product. We can hope they bring XEN back in RHEL 7. There was some discussion about producing RPMs to add XEN support into CentOS 6, but I haven't seen any status updates, recently. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Slightly OT: Centos KVM Host/Guest functions and LVM considerations
On Fri, 2011-09-16 at 10:46 -0700, Eric Shubert wrote: ... Now, take all of your ideal logical servers (and the networking which ties them all together), and make them VMs on your host. I've done this, and these are the VMs I presently have (the list is still evolving): .) net (IPCop distro, provides network services, WAN/DMZ/LAN) .) web (DMZ/STOR) .) ftp (DMZ/STOR) .) mail (DMZ/STOR) .) domain control (LAN/STOR) .) storage (LAN/STOR) One aspect that we haven't touched on is network topology. I have 2 nics in the host, one for WAN and one for LAN. These are both bridged to the appropriate subnet. I also have host-only subnets for DMZ and STORage. The DMZ is used with IPCop port forwarding giving access to services from the internet. The STOR subnet is sort of a backplane, used by servers to access the storage VM, which provides access to user data via SMB, NFS, AFP, and SQL. All user data is accessed via this storage VM, which has access to raw (non-virtual) storage. ... If I'm understanding you, if you split this out to multiple physical hosts, you would need to convert DMZ and STOR from virtual to physical segments; increasing the number of required network interfaces in each host to 4. Are you concerned that your hosts are connected to WAN without a firewall? I assume you bridge the interface without assigning IP address? What software do you use for storage. I'd think having the host handle integrated storage would be simpler, but, of course, that doesn't scale to multiple hosts... ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Slightly OT: Centos KVM Host/Guest functions and LVM considerations
I've been considering this type of setup for a distributed virtualization setup. I have several small locations and we would be more comfortable having a host in each. I was nervous about running the firewall as a virtual machine, though if nobody screams bloody murder, I'll start exploring it further as it could reduce machine count at each location by 2 (backup fw). I'm not as paranoid about the host providing storage to the VM's directly, for booting. I'm considering using DRBD to replicate storage on 2 identical hosts to allow fail-over in the case of a host hardware failure. What kind of VM management tool do you use; VMM or something else? ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] P2V of NEtware 3.12 working server to Centos =5.x
On Wed, 2011-09-07 at 19:54 +0530, Rajagopal Swaminathan wrote: Greetings, On Wed, Sep 7, 2011 at 12:34 AM, Ed Heron e...@heron-ent.com wrote: On Tue, 2011-09-06 at 23:20 +0530, Rajagopal Swaminathan wrote: There are so many variables that aren't mentioned... Do you currently have a CentOS box running KVM? I have used centos with KVM,brctrl etc. What does your Netware server currently do? Just just pure and simple file storage. The worst part of it is The client has to be a DOS6.22 with some custom ISA base hardware. Netware 3 defaulted to using the IPX protocol for sharing file and print services. Are you still using IPX? If so, you are looking at a significant network reconfiguration. Indeed. with 802.3 frame etc :) There might be lots of changes to client setup and software, but look at Samba. It can be setup with a workgroup for file and print Now, How to access Samba with Dos 6.22? :p There was a workgroup client for DOS that used TCP/IP. I can't vouch for it's working, but try ftp://ftp.microsoft.com/BusSys/Clients/MSCLIENT/ One main thought that first came to my mind is about the NIC Driver under KVM I do understand that the Centos5 can present it as different types of NIC (Intel, Realtek etc.) I am investigating it further. Hopefully, you already have significant CentOS experience. Last 6 years or so I have worked only Fedora/Centos/RHEL. Since then I have tried avoid taking calls windows etc. But this call I took because I have significant experience in netware too about 10 years 2.2 to 4.10 with NDS etc I, also, supported Netware 2 and 3. I avoided 4 due to NDS and the availability of Samba. It was a big deal when the Internet was gaining momentum. At first, we had multiple protocols and multi-protocol routers. My memory is vague but I'm pretty sure Netware 3 could run NetBIOS on a TCP/IP stack. The broad wording of your request might just be language barrier. I realised that. I will experiment further share my experience sometime later. So, are you looking to move your existing Netware 3 server into a virtual environment? Or, are you looking to replace an existing Netware 3 server with a CentOS equivalent? I would suggest setting up a CentOS server with Samba and convert the DOS network stack, if you can. Samba appears to be much more supportable, currently. Take a look at the FreeDOS project, too, as an example of getting DOS to work in a more recent environment. The biggest concern (after getting the clients to talk to Samba) is that there have been a few choices made in Samba with respect to file sharing/locking mechanisms. With old software, you may have to look at those settings. If you attempt to virtualize Netware, you may run into issues, though it'd be an interesting exercise. I don't know if a Linux hypervisor will handle IPX packets without IPX support installed. You might need to check for an ipx kernel module. Also, my version of Virtual Machine Manager running on CentOS 5 with Xen doesn't give me any sort of Netware OS option when creating a new virtual machine, so you'll probably have to play with settings. I google'd netware virtual machine and saw a few links to virtualizing Netware 3 under VMWare which might give you some insights. Either way, do it in a separate test environment to work out any issues prior to production deployment. If I hadn't been strongly encouraged (successfully) to de-clutter my software repository, I'd pull out my old Netware 3.12 disks and try installing on a virtual machine. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] P2V of NEtware 3.12 working server to Centos =5.x
On Thu, 2011-09-08 at 02:35 +0530, Rajagopal Swaminathan wrote: I would suggest setting up a CentOS server with Samba and convert the DOS network stack, if you can. Samba appears to be much more supportable, currently. Take a look at the FreeDOS project, too, as an example of getting DOS to work in a more recent environment. The biggest concern (after getting the clients to talk to Samba) is that there have been a few choices made in Samba with respect to file sharing/locking mechanisms. With old software, you may have to look at those settings. I am not sure about freedos as there is a Piece of custom built ISA hardware and the forget about replacing it. there is a budget(was there any?) constraint at clients end. Just suggesting looking at the docs for ideas. I google'd netware virtual machine and saw a few links to virtualizing Netware 3 under VMWare which might give you some insights. No additional cash flow for software :p . :) Just another suggested reading for ideas. Either way, do it in a separate test environment to work out any issues prior to production deployment. Even buying is a hard disk is a constraint. (Cash outflow constraint, remember :) ) If you can't buy hardware, then you already have a Linux box running KVM? If I hadn't been strongly encouraged (successfully) to de-clutter my software repository, I'd pull out my old Netware 3.12 disks and try installing on a virtual machine. If only I had that luxury of having those original _working_ floppy disks. If I had to virtualize an existing machine, I'd boot the equipment with a Linux Live CD and copy (using dd/ssh) the raw disk data to a virtual disk on the virtual machine server. Verify the copy is accurate with md5sum. Then, make another copy to start a virtual machine with. I'd still suggest your best option would be to take one of the DOS clients and get it to connect to a Samba server and migrate the data. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] P2V of NEtware 3.12 working server to Centos =5.x
On Tue, 2011-09-06 at 23:20 +0530, Rajagopal Swaminathan wrote: Greetings, I would be grateful if anybody can kindly give a pointer to port a Working netware 3.12 server using Centos =5.x KVM howto? There are so many variables that aren't mentioned... Do you currently have a CentOS box running KVM? If no, this is your first step. Since a virtual server can run multiple virtual machines, it is only useful if you intend to run multiple virtual machines. What does your Netware server currently do? If it does more than file and print services, you will have to determine how you would replace those other services. Netware 3 defaulted to using the IPX protocol for sharing file and print services. Are you still using IPX? If so, you are looking at a significant network reconfiguration. Netware 3 could integrate with a variety of client OS's; Unix, DOS, OS/2 and MS windows. What method is your server using to provide services? There might be lots of changes to client setup and software, but look at Samba. It can be setup with a workgroup for file and print services that might be sufficiently similar to how you are currently working. The differences between a physical CentOS server with Samba and a virtualized CentOS server running Samba are minimal and don't directly effect Samba configuration. There might not be a simple document or a series of simple documents to point you at. It might be easier to setup a new network with the new server and a few clients to work out the concepts and any issues you're going to run into. Once you have everything working well on your new network, do a last copy of current data and migrate all your workstations. I hope I'm mentioning use cases that don't apply. Hopefully, you already have significant CentOS experience. Hopefully, this might be a simple file and print server migration for MS Windows clients. The broad wording of your request might just be language barrier. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] lvm and kvm
On Mon, 2011-08-15 at 15:54 -0400, James B. Byrne wrote: I am performing some configuration testing on a kvm host. When installing a guest operating system is it advisable to place each instance in a separate lv or better to accept the default and store them on the root file system? I think you are asking LV based or file based guest storage. I vote for LV on the host. Respecting lvm, does one configure lvs in a virtual server to take space from the main vg or does one allocate lv space from inside that allocated to the virtual instance? Is it even considered advisable to use lvs with virtual guests? ... It seems that you are asking whether to use (1) multiple host LV's to keep different partitions on different virtual disks, (2) a single host LV with nested LVM or (3) a single host LV with traditional partitioning... I use Xen, but if we treat this as a philosophical discussion, that probably doesn't matter. I like option 1 (multiple host LVs) for the flexibility it gives, but I don't like the large number of LVs on the host. I don't like option 2 (nested LVM) due to the difficulties of resizing guest PV. Option 3 (single host LV, raw guest partitions) keeps the number of host LVs lower, but only the last guest partition is easily resized. If you can accept the number of LVs or you need to resize your partitions frequently, I'd recommend option 1. I have gravitated to option 3 because I find I don't need to resize my guest virtual disks very often. MS Windows uses a single partition, so those VMs are simple. On my Linux VMs, I normally only need to resize either the var partition or the home partition depending on the machine's function, but not both, so I put that partition last. I recommend against using LVM within a VM. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Suggestions to improve this minimal kickstart config for CentOS 6?
On Tue, 2011-07-19 at 12:36 -0400, Kartik Subbarao wrote: I've come up with the following kickstart config (see below) for deploying a minimal CentOS 6 VM. It takes about 460MB. I'm assuming that all of the -firmware RPMs aren't needed for a VM installation, so I removed them. Also removed as many selinux packages as possible since I don't need that. I was wondering whether anyone could offer any further suggestions on minimizing the disk usage of the VM image. ... ... rootpw admin123 I use the --iscrypted option so people can't easily see my default root password. An easy method of viewing the command is looking at /root/anaconda-ks.cfg (at least it was in 5) after install. For setting unique initial root passwords, there is a method for creating it on the command line. ... # Repositories url --url=http://mirrors.kernel.org/centos/6.0/os/x86_64/; Shouldn't we encourage the creation of a local mirror? Installs are much faster. Also, with local mirrors, you can snapshot the repo. This allows for testing updates before pushing them to your live servers. ... I create ks files for many of my CentOS and CentOS derived (Elastix) boxes. Backups take less space when you only save data. Routers are great for this as they rarely change (except possibly for firewall rules). With PXE boot, I can rebuild a router in 10 minutes. Also handy if the router hardware fails (I'm using old PCs). An on-site user without any Linux knowledge can install a replacement router (or re-install an existing router if it is suspected to be compromised) in little time. As long as the ks file is used as the master configuration where changes are made and the router re-installed to make them active, you don't get into a position where a change is lost if the hardware fails. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Now on to creation of disk images
On Tue, 2011-06-28 at 09:30 -0400, Steve Campbell wrote: Mr. Heron was so kind to make a suggestion that I should use disk images to install VMs. Upon further thought, I kinda like the idea. So I re-read the manual and google a little, and discover I still don't know what should be in these disk images. Should I copy the contents of the CDs to a file or what? I've got a test server at the moment with Centos 5.5 and xen installed as the host OS, but have just downloaded the 5.6 CD ISOs along with the DVD ISO, so I'll use 5.6 for my VMs. I've read about how I can create an image from something that already exists. Again, any clarity would be appreciated. Just put the ISO's in /var/lib/xen/images and point at them. If you didn't download the discs, you can rip them using: dd if=/dev/optical device of=/var/lib/xen/images/name of disc For example, if ripping the first 5.6 CD... dd if=/dev/hdc of=/var/lib/xen/images/CentOS-5.6-i386-d1.iso I generally rip a disc multiple times and then do a file compare to make sure I've got a reasonable chance of having an undamaged copy. Keep in mind that it isn't as easy to change discs when you are using images on a paravirtual machine. I still recommend setting up a local repository as a much better solution because it allows you to take a snapshot so multiple installs use the exact same versions of everything. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Now on to creation of disk images
On Tue, 2011-06-28 at 13:35 -0400, Steve Campbell wrote: Ed, What do you mean by ripping? As far as the dd command you mentioned, it appears that the ISO file itself is copied to the folder, not the expanded iso-into-files themselves. Is this correct? If so, that's just too easy. Thanks for your kind assistance. steve campbell Yes. By 'ripping', I'm referring to pulling the data from a disc. In this case, I'm using the dd command to create a file with the raw data from the disc. That raw data file can then be used to burn another disc or provided to a virtual machine as a virtual disc. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] New to virtualization - can't use more than one CD when installing a new VM
On Mon, 2011-06-27 at 16:02 -0400, Steve Campbell wrote: ... I'm trying to install my first VM using Centos 5.5 as the host as well as the VM OS. It starts fine using VMM, but when it asks for the second disk of 8 CDs, the first one isn't ejected, although unmounted because I can open the tray, and won't recognize that the second CD is inserted. ... Why not use a DVD image in /var/lib/xen/images? ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] New to virtualization - can't use more than one CD when installing a new VM
On Mon, 2011-06-27 at 15:37 -0600, Ed Heron wrote: On Mon, 2011-06-27 at 16:02 -0400, Steve Campbell wrote: ... I'm trying to install my first VM using Centos 5.5 as the host as well as the VM OS. It starts fine using VMM, but when it asks for the second disk of 8 CDs, the first one isn't ejected, although unmounted because I can open the tray, and won't recognize that the second CD is inserted. ... Why not use a DVD image in /var/lib/xen/images? Or better, setup a local mirror using http://wiki.centos.org/HowTos/CreateLocalMirror Then create your CentOS DomU with something like: virt-install --name=VMName --vnc --vncport=59xx --noautoconsole --paravirt --ram=512 --vcpus=1 --network=bridge:network bridge device --file=virtual disk device --location=mirror URL --os-type=linux --os-variant=rhel5 --extra-args=xencons=tty noipv6 ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-docs] proposal TipsAndTricks/EditorDefaultNano
On my systems, I set nano to be the default editor. Is this something that can be done with some sort of configuration script? I don't find anything like system-switch-mail for editors. I do it in my kickstart files, but it can easily be done from a command line. Since nano is only useful to people using the command line, I think it completely appropriate... Is a document describing this short process desirable to have on the wiki? yum install -y nano echo set nowrap /etc/nanorc cat EOF /etc/profile.d/nano.sh export VISUAL=nano export EDITOR=nano EOF ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] proposal TipsAndTricks/EditorDefaultNano
On Wed, 2010-12-01 at 22:12 +0100, Marcus Moeller wrote: Is a document describing this short process desirable to have on the wiki? You may want to add some notes about the ability to define these variables on per user base: I've thrown a quick page together and included your suggestion at http://wiki.centos.org/EdHeron/EditorDefaultNano ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] new to xen - got questions, please
On Wed, 2010-06-16 at 12:40 -0700, Drew wrote: The free ESXi can virtualize more then three guests. The limitations imposed on the free license revolve more around advanced capabilities within the suite. Things like vMotion (automatic guest migration between hosts), High Availability, etc are disabled. http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=1006543 Down at the bottom you'll find the edition comparatives. Thanks for that. Obviously, I am not entirely informed with respect to ESXi. I've used VMWare Server on Linux and MS Windows (XP, 2003) and, while it worked, I wasn't satisfied with the performance for a production environment. Due to my limited budget, I've been 'scared off' from setting up a ESXi testing environment, though it is still 'on my list of things to do'. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-docs] copying upstream docs to centos.org
On Thu, 2010-06-03 at 10:15 +0200, Tru Huynh wrote: ... I don't think that Red Hat as provided any updated guide, if we are missing any please point them here or add them to bugs.centos.org. According to http://www.redhat.com/docs/manuals/enterprise/, Installation Guide was published Mar 2010 and has a 5.5 link. I haven't compared actual content, though. Even if there haven't been any updates to guide content, we should link the guides under 5.5 so people don't think our guides are out-dated. Out-dated guides are an indirect indication of inadequate project resources. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] copying upstream docs to centos.org
On Thu, 2010-06-03 at 10:15 +0200, Tru Huynh wrote: ... I don't think that Red Hat as provided any updated guide, if we are missing any please point them here or add them to bugs.centos.org. One interesting change is the license. 5.4 and 5.5 Installation Guides are released under Creative Commons Attribution - Share Alike which appears to grant us the ability to edit it to replace the Redhat logos with CentOS and to remove the references to RHN as long as we attribute Redhat and provide a link to the original docs. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] copying upstream docs to centos.org
Is there a place, from the upstream provider, where we can download the multi-file html docs in a single file? Otherwise, I can download each page manually or use wget to get everything recursively... Is the footer the only difference? (besides any links) Do we want to encapsulate each page into the centos site or keep it printable, like it kind of is, currently. Do we just copy the current pdf? or do we modify it? Since the manual is on the main centos.org site, do I need a sine in or access to start adding the manuals? I should still have an EdHeron login over there. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Tips and Tricks: Install from GRUB
On Fri, 2010-05-28 at 11:57 -0400, Phil Schaffner wrote: Ed Heron wrote on 05/27/2010 04:27 PM: On Wed, 2010-05-26 at 10:30 -0400, Phil Schaffner wrote: Proposed new page for comment: http://wiki.centos.org/TipsAndTricks/InstallFromGRUB Phil I suggest adding links to some supporting documentation. For example, you could add a prerequisites section saying this technique or trick requires the install media available, either on the network or on the local disk. Instructions for setting up the install media on the network can be found in the Installation guide, chapter 2.5 Preparing for a Network Installation http://centos.org/docs/5/html/5.2/Installation_Guide/s1-steps-network-installs-x86.html Instructions for putting the install media on the local disk can be found in the Installation guide, chapter 2.6 Preparing for a hard drive Installation http://centos.org/docs/5/html/5.2/Installation_Guide/ch02s06.html It looks like the version 5.2 docs are the most recent on the centos.org site. Ed, Thanks for the suggestion. For a short Tips page I'm reluctant to add too much, and also don't like linking to the obsolete docs. Feel free to edit the page if you feel differently. :-) I feel linking is better than not giving the reader an idea of where to go next. I felt linking to the obsolete CentOS docs was better than linking to upstream docs, since that part hasn't really changed. I suppose if we used http://centos.org/docs/5/html/Installation_Guide-en-US/ as the base, it would be re-linked when a document was updated and could (theoretically) be changed by the translators (assuming alternate language manuals existed). OT: So what's happening with updating docs? Phil I had an urge to ask the same about updating CentOS docs, but that is commonly interpreted as volunteering to lead the task. I'd volunteer to help, though. Is someone currently in charge of that? http://www.centos.org/docs/5/ suggests that the CentOS project redistributes without modification. Since this isn't code, I assume (subject to correction) that this process is different than the process at http://wiki.centos.org/FAQ/General/RebuildReleaseProcess but possibly similar in some respects for the equivalent rpms. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Tips and Tricks: Install from GRUB
On Wed, 2010-05-26 at 10:30 -0400, Phil Schaffner wrote: Proposed new page for comment: http://wiki.centos.org/TipsAndTricks/InstallFromGRUB Phil I suggest adding links to some supporting documentation. For example, you could add a prerequisites section saying this technique or trick requires the install media available, either on the network or on the local disk. Instructions for setting up the install media on the network can be found in the Installation guide, chapter 2.5 Preparing for a Network Installation http://centos.org/docs/5/html/5.2/Installation_Guide/s1-steps-network-installs-x86.html Instructions for putting the install media on the local disk can be found in the Installation guide, chapter 2.6 Preparing for a hard drive Installation http://centos.org/docs/5/html/5.2/Installation_Guide/ch02s06.html It looks like the version 5.2 docs are the most recent on the centos.org site. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] www.centos.org and the wildcard dns
From: Karanbir Singh, Friday, April 16, 2010 8:57 AM ... At the moment there is a www.centos.org site. There is also a wildcard dns setup that directs anything.centos.org to www.centos.org's content ... Unless I'm missing something, http://yadda.centos.org doesn't redirect, it displays a copy of the (www.)centos.org content. I'm not that knowledgeable about SEO stuff, but wouldn't a redirect be better? Assuming an Apache setup, adding something like a catch-all virtual host after any other centos.org host definitions. I prefer URL's without the www unless there is a good reason... VirtualHost *:80 ServerAlias *.centos.org Redirect permanent / http://centos.org /VirtualHost That should get the browser client to notice and change where it is going. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] kickstart + domU for static IP
From: john maclean, Tuesday, April 06, 2010 4:11 AM I've set up a local webserver to store kickstart files for domUs. All parameters are respected apart from the network settings. DomU always gets DHCP. Can any one help to unwrap this one? Does one add hostname, ip, netmask and gateway values to the /etc/xen/blah.cfg file? # domU kickstart file # ... # sudo cat /etc/xen/dns1.cfg ... -- John Maclean 07739 171 531 MSc (DIC) Enterprise Linux Systems Engineer It's not quite clear to me what your process for creating the DomU is, but I think you're creating the xen config file by hand then running xm create vm? I'm not sure when you are having the IP issue. If during the installation process, anaconda has to initialize eth0 before it can get access to the kickstart file, so it must use DHCP. After some discussion with Russ some time ago, he convinced me that in most cases, virt-install is your friend. I use virt-install (specifying a mac address) to create my virtual machines, which sets up a boot partition, just like a physical machine, so my extra parameters go into the VM's /boot/grub/grub.conf file. I assign static IP addresses with DHCP during the install process and also set the IP address in the kickstart file (if it is a server). I like that the VM's config is mostly internal to the virtual disk image. I don't have a problem controlling my IP addresses. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] kickstart + domU for static IP
From: Ed Heron, Wednesday, April 07, 2010 9:11 AM ... and also set the IP address in the kickstart file (if it is a server). ... I should add that I set the static IP address from %post using: # Configure eth0 file=/etc/sysconfig/network-scripts/ifcfg-eth0 sed --in-place s/^\(BOOTPROTO=.*\)$/#\1/ $file sed --in-place s/^\(DHCPCLASS=.*\)$/#\1/ $file cat EOF $file BOOTPROTO=none IPADDR=xxx.xxx.xxx.xxx NETMASK=xxx.xxx.xxx.xxx GATEWAY=xxx.xxx.xxx.xxx EOF I do it this way, because I really don't care what the IP address is during install. I want the IP address to be set during the next boot. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-docs] EdHeron/DomU_LVM_NTFS_resize
From: Fabian Arrotin, Monday, February 08, 2010 12:52 PM Ed Heron wrote: Please, if anybody has time, take a look at http://wiki.centos.org/EdHeron/DomU_LVM_NTFS_resize Contructive criticism welcome. Well, why using ntfsprog when the Windows guest can resize the FS itself with diskpart ? (of course, if it's not on the system/boot disk) ... I've always only used lvextend and then used that in the VM itself (for Windows guests, that is) Thanks. I didn't realize that was supported. I'll check it out. -- Fabian Arrotin test -e /dev/human/brain || ( echo 1 /proc/sys/kernel/sysrq ; echo c /proc/sysrq-trigger ) ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] EdHeron/DomU_LVM_NTFS_resize
Please, if anybody has time, take a look at http://wiki.centos.org/EdHeron/DomU_LVM_NTFS_resize Contructive criticism welcome. Ed Heron ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] TipsAndTricks/ApacheVhostDir re-org
From: Ralph Angenendt, Thursday, January 21, 2010 5:56 AM On Mon, Jan 18, 2010 at 8:47 PM, Ed Heron e...@heron-ent.com wrote: Hopefully, this will make the document easier to read for those that don't have any interest in the optional alternatives or reading it entirely. Too me it looks more clearly arranged this way. Thank you. I tend to read documentation all the way through before following it, when I read it at all ;). So, I didn't initially understand the depth of emotion that appeared to be expressed over the previous version. (simplified english: Russ seemed very annoyed.) But, with Russ's patient explanation and a bit of thought, I think I understand what he was saying. I think both points of view are valid but the new organization is probably more applicable to our audience. I hope the new document is more useful as a reference document and produces less confusion. It occurs to me that I could separate the vhost.d/ and virtual disabling sections into separate Tips articles. Please let me know if this is desireable. Is that desirable? You're weighing options here (do it this way or do it the other way), so I don't really see how that could be split out in a sane way. Yes. I think so, as well. However, the document is getting a bit large for a tips page and goes slightly beyond the stated scope. If that isn't an issue, yet, I don't have an issue with leaving it as a single document. For example, we could split the restart section into a separate document and expand the explanation a little.. Then, this page and other potential Apache tips pages could refer to it by command and link. The disabling virtual hosts could probably be put into a separate doc, though it depends on putting the virtual host config files in a directory, so both docs would need to refer to each other. The potential pitfall here is that no single document completes a thought and the referrals fly, apparently endlessly. I sometimes have trouble drawing the line. The axiom, In for a penny; In for a pound, seems to exclude, or maybe ignore, the idea of only being in for tupence. Certainly wouldn't be the first to question my sanity, though. The other thought I had is collecting all the Apache tips into a howto, but I'm not ready to accept the responsibility to create and maintain it, nor do I have the confidence that it would be sufficiently authoritative. Other's mileage may vary, though :) Cheers, Ralph ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] TipsAndTricks/ApacheVhostDir re-org
After much ruminating about Russ's suggestions, including his addition of a second example vhost conf file, I've made some additional changes. I've added a single level contents section to give readers an idea of what's in the document, since it is getting a little large for a Tips article. I've integrated the 2 example sections. I've placed the vhost.d/ section last because it is rather large and breaks the flow for people using the existing conf.d/. The vhost.d/ section included a subsection on toggling whether a virtual host was active. I've broken this out to it's own section, since it is applicable to the conf.d/ method. Hopefully, this will make the document easier to read for those that don't have any interest in the optional alternatives or reading it entirely. It occurs to me that I could separate the vhost.d/ and virtual disabling sections into separate Tips articles. Please let me know if this is desireable. Ed Heron ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] TipsAndTricks/ApacheVhostDir changes for virtual host source files
From: R P Herrold, Wednesday, December 16, 2009 4:24 PM
On Wed, 16 Dec 2009, Ed Heron wrote:
I see someone has noticed my lack of suggestions or recommendations for
placement of virtual host source files...
That would be me
A questioner reading the page in IRC today was confused by the
article. I added the pointer to the 'official' doco location
for the conf files, a sample stanza showing an approach
without alias wildcarding, and a reasonable approach
consistent with SELinux for location of content pages and CGI
that does not break SElinux expectations.
Thanks. I appreciate the overview of your process.
Since there are many places to put virtual host source files, I had
intentionally avoided the discussion due to the complexities and to keep
the
document restricted to a single topic. I had planned to create a
separate
document devoted to the discussion. Specifically, there are a couple of
SELinux related issues to work out with a couple of them. I would start
a
discussion of the various places to put virtual host source files and the
issues associated with them. Where should such a discussion take place?
In
one of the forums or on this list?
The wiki diff's speak, this mailing list speaks; as noted in
the reorg discussion on web presence, the Forums seem to
attract a different type of editor; it drew a proposal for yet
another FAQ, it drew Les M with a request for (but no work
done to make) a recap of the mailing list with editorial
cleanup.
The issue remains: Who does work and who cleans up when there
is not funding to incentivize such, and why? My answer is to
clean up when CentOS' reputation is impaired. As I read it,
this particular content has rotted (seemingly half done
without warning guards, as I read your comment) with your
'inside' intent to come back to the topic unknown and
unknowable to an outside observer.
I agree that the docs need to be clear. I have my documents in my watch
list specifically so I can maintain them. I will try to make them less
likely to be misinterpreted. Though I disagree with putting information
into this document about where to put virtual host source files.
However, I'm not sure what is meant by The following section is the
approach advocated by its initial author, EdHeron. It is not clear that
varying from the approach above is warranted, and by the version from
him,
does not explain the needed SElinux changes.
It appears to suggest my disclaimer, Another method, for those of us
that
might have a tendency to 'over engineer', is creating a new directory,
vhost.d for example, and putting an include where the configuration, as
distributed, has the virtual host example. This retains the position of
the
virtual host definitions in the Apache configuration, isn't enough to
discourage most system administrators from using it or explain my reasons
and
give a reader a hint that there are other ways, even, from the three
discussed?
Do you explain a _good_ reason that warrants a non-standard
approach? I sure don't see one. More on SElinux matters in a
bit
The terms, 'non-standard' and 'good', are fuzzy here. Many people use
vhost.d/ for virtual host container files. With Linux, the standard is as
people do. Upstream doesn't prohibit using vhost.d/ and it doesn't break
the standard. To satisfy the standard of 'good' for you is probably never
going to happen as you don't agree with segregating the module configuration
files and the virtual host container files. I don't have an issue with your
opinion being different from mine.
I put the discouragement in because the reader was confused.
In so far as the questioner was reading it -- the absence of a
set off, and no ! caused him to ** not ** see the issues.
As such I added the
-
and the !
and made the {{{ }}} box around it
I do not consider your approach some cute form of
'over-engineering' but rather a method ignoring the well
docoed ways in the doco we provide. Personal makework
perhaps, not rationalized as, say, part of a larger VHost
management automation system. Not durably integrated as
the CentOS operating system reputation implies. Change for
its own sake, alone. Basically, out of place.
I put the 'cute' over-engineering comment in there (and I don't deny that
it wasn't appropriate) because I didn't have a simpler cohesive reason for
using vhost.d/. I'm not the one that created the concept, but I like it for
it's esthetics. I am endevouring to explain the concept and reasons behind
it with updates to the article.
As far as the SELinux issue, from the directory listing
that accompanies the
directory creation instruction, a reader might notice that the SELinux
user
is listed as root instead of system_u. The SELinux user discrepancy is
resolved with the chcon command shown. Is there a desire for additional
explanation of the process?
That a person *might* notice
[CentOS-docs] TipsAndTricks/ApacheVhostDir changes for virtual host source files
I see someone has noticed my lack of suggestions or recommendations for placement of virtual host source files... Since there are many places to put virtual host source files, I had intentionally avoided the discussion due to the complexities and to keep the document restricted to a single topic. I had planned to create a separate document devoted to the discussion. Specifically, there are a couple of SELinux related issues to work out with a couple of them. I would start a discussion of the various places to put virtual host source files and the issues associated with them. Where should such a discussion take place? In one of the forums or on this list? However, I'm not sure what is meant by The following section is the approach advocated by its initial author, EdHeron. It is not clear that varying from the approach above is warranted, and by the version from him, does not explain the needed SElinux changes. It appears to suggest my disclaimer, Another method, for those of us that might have a tendency to 'over engineer', is creating a new directory, vhost.d for example, and putting an include where the configuration, as distributed, has the virtual host example. This retains the position of the virtual host definitions in the Apache configuration, isn't enough to discourage most system administrators from using it or explain my reasons and give a reader a hint that there are other ways, even, from the three discussed? As far as the SELinux issue, from the directory listing that accompanies the directory creation instruction, a reader might notice that the SELinux user is listed as root instead of system_u. The SELinux user discrepancy is resolved with the chcon command shown. Is there a desire for additional explanation of the process? The additional warning against the vhost.d/ section seems to excessively disparage my contribution and discourage other options. Certainly, it could be considered impolite to expand and significantly modify the content of a document when the author is available and willing to make changes. As well, I seek to improve my documentation technique and by-passing me deprives me of the opportunity. I'd like to know the process that culminated in the changes to my document. Are there a large number of people reading the document, not understanding it but making non standard changes to their systems, and requesting support? Ed Heron attention.png___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] Virsh shutdown all command?
From: Torkil Zachariassen, Monday, November 23, 2009 5:35 AM On Fri, 2009-11-13 at 10:47 -0700, Ed Heron wrote: From: Neil Aggarwal, Thursday, November 12, 2009 5:34 PM Is there a command in virsh to shutdown all domains? I'm sure my script isn't very efficient and I'd appreciate any polite, constructive suggestions. Also, since I've pulled it out of a script and modified it on the fly for virsh, there might be bugs. Fixed a bug or two and made some hoovering. All the best. ...torkil... Shall I assume it is useful? I was expecting someone to ask why I was getting a list of VM's separately from the section that did the shutdown... I did that because my script does an action on either a default list of VM's (stop/shutdown uses list of active VM's, start uses list in /etc/xen/auto, reboot uses list in /etc/xen/reboot) or the list from the command line. I link vm-stop and vm-start to vm-reboot and check $0 when it runs. Should we expand the script and include the other options? Maybe rename it to virt-start, virt-stop, virt-reboot? (to complement virt-install) Or, call it virt-cntl and have options like --reboot, --stop --start? ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Xen domU default gateway missing/ARP table full
I was slightly confused about this thread until I realized you were using static IP config on your VM's... Why do people do that? I have an extra step of picking up the HW address (or setting the HW address when creating the VM) and putting it into my dhcp configuration, but then I have all of my hosts in a single file and I can change the network configuration of my whole network in a single place. I realize that my DHCP server becomes a single point of failure, but with a reasonably long retrain time the DHCP server going down won't effect any workstations for as much as several hours (as long as nothing reboots). Also, there are ways of having fault tolerance with DHCP, the easiest would be to have a non running VM with a copy of the data. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Virsh shutdown all command?
From: Neil Aggarwal, Thursday, November 12, 2009 5:34 PM Is there a command in virsh to shutdown all domains? I can do one at a time, but that is untenable for a large number of domains. I use a script to shutdown my domains. I am not always happy with stopping the service, which is supposed to have the effect of stopping the virtual machines. I use xm and do other things, including rebooting my MS Windows XP VM's on a schedule, but here's the piece that just does a shutdown on running VM's. I'm sure my script isn't very efficient and I'd appreciate any polite, constructive suggestions. Also, since I've pulled it out of a script and modified it on the fly for virsh, there might be bugs. The debug environment var is use for verbosity. The fake environment variable is used for 'faking' the run. Setting both while debugging might be a good idea unless you are using a test system without any production virtual machines. -- #!/bin/bash # file: /usr/local/sbin/vm-shutdown # Description: shutdown active virtual machines # Get list of active virtual machines vmList=`virsh list | ( while read vmID vmName vmStatus do if [ -n $vmName -a $vmName != Name -a $vmName != Domain-0 ] then [ -z $vmList ] vmList=$vmName || vmList=$vmList $vmName fi done echo $vmList )` # check there are some active VM's if [ -n $vmList ]; then # Shutdown VM's with verification for vmName in $vmList do # send initial request [ -n $debug ] echo -n Attempting to shutdown $vmName [ -z $fake ] virsh shutdown $vmName # wait a limited time for the VM to be not running count=300 while ( virsh list | grep $vmName /dev/null ) [ count -gt 0 ] do sleep 1 let count=count-1 [ -n $debug ] echo -n . done # report current status ( virsh list | grep $vmName /dev/null ) echo failed! || echo down. # if still running, destroy it if ( virsh list | grep $vmName /dev/null ) then [ -n $debug ] echo -n Attempting to destroy $vmName [ -z $fake ] virsh destroy $vmName # wait a limited time for the VM to be not running count=60 while ( virsh list | grep $vmName /dev/null ) [ count -gt 0 ] do sleep 1 let count=count-1 [ -n $debug ] echo -n . done # report current status ( virsh list | grep $vmName /dev/null ) echo failed! || echo down. fi fi -- over engineering and over analysing for 3 decades... or is it over analysing and over engineering... ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-docs] CentOS 5.4 Network install
From: Toshikazu Aiyama, Sunday, November 01, 2009 1:07 AM I have just completed to write up the procedure to install 5.4 through network There is an interesting article that that you might want to read at http://wiki.centos.org/HowTos/PXE/InternetInstallation ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] New User Wishes to Contribute
From: Ralph Angenendt, Tuesday, October 06, 2009 7:22 AM On Mon, Oct 5, 2009 at 7:05 PM, Ed Heron e...@heron-ent.com wrote: From my point of view, the process wasn't onerous in itself. The only issues I had/have are the sparse guidelines of acceptable content and the voracity of the reaction, by some, to what they viewed as unacceptable content. It appears there are multiple standards for content. This is true. While I'm for rather more content (as long as quality doesn't go down) others have a different view of that. And I think we have to find some common ground here. It appears that the people who are preferring the more restricted content guidelines are saying they will accept content separation. But having 2 separate content systems seems redundant. Is there a way to have a section (directory) of the wiki that is core and an expanded section? This might satisfy both sides? For aspiring content producers that suggest modification to existing content, those changes should go through the page's creator or maintainer or someone else in the edit group. If they describe the changes on this list, it should be a simple matter for someone else to implement or possibly give them access to that page. Once those people have sufficient history, I assume adding them to the edit group so they can make changes directly would follow. This is roughly how it is working at the moment, if I didn't misunderstand you. I'm summarizing intentionally. I don't think there is anything wrong with the current process. Being a recent addition to the 'edit group', even though it took some time to get there, it wasn't too bad. A little patience was all I really needed. Opening up the content to the public could put a rather large burden on the existing admin/edit group. Going through the current process should result in greater longevity of contributors compared to instant edit access. Making edit access easier for people 'passing through' could result in more orphaned content. The only thing that comes to mind is possibly allowing someone to edit a page without committing the changes. These could be the equivalent of submitted patches pending approval. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] New User Wishes to Contribute
From: Ralph Angenendt, Monday, October 05, 2009 9:54 AM ... Okay, than I did misunderstand that. Mind, that I'm not native speaker either. Then *everybody* please be not vague: I think my last post might have fallen in to the vague category... I was trying to say that as one of those new members, I was trying to ease into the job. New members are being added... How would openness work in your view a) without compromising the wiki's spam-free-ness (?) b) with making people adhere to a CC license beforehand c) with making sure that the content quality doesn't get worse (I think we have a rather high quality at the moment) d) with making sure that there's no off topic content I'd really be interested to hear that. I have a view how that can work, but that is a view which still makes some people better than other people - and will create more work for them. I know we had that discussion about a year and a half ago, and I have some ideas - but the result from last year was, that there would be around 5 to 6 people who watch over the content. I think that that isn't enough. ... From my point of view, the process wasn't onerous in itself. The only issues I had/have are the sparse guidelines of acceptable content and the voracity of the reaction, by some, to what they viewed as unacceptable content. It appears there are multiple standards for content. I don't have a problem with easing people into the 'trusted' position of the edit group. It is already possible to get a user account and access to create a user page with little 'qualification'. For new conttibutors, this provides a sandbox to both say something about themselves and produce content, or spam. For aspiring content producers that suggest modification to existing content, those changes should go through the page's creator or maintainer or someone else in the edit group. If they describe the changes on this list, it should be a simple matter for someone else to implement or possibly give them access to that page. Once those people have sufficient history, I assume adding them to the edit group so they can make changes directly would follow. The only people excluded by the current process are the impatient. This is a long-term project. Impatience is for more transitory media, like on-line chat and lists/forums. The world isn't going to end if a page isn't updated or access isn't granted for a few days. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] New User Wishes to Contribute
From: Ralph Angenendt, Friday, October 02, 2009 6:11 AM We already have 70 people who would be able to do so (no idea how many of these accounts are still in use). Do I see those going over pages? Rarely, it's nearly always the same persons. I'm OK with helping to update/maintain the wiki. I've made a couple of minor changes and I started on a revision of the PXE stuff. Since much of the PXE articles are not core, but a generic discussion of how to configure it and related software, I'm interested in the result of this discussion. In general, I'm asking myself, How deep do I jump in and how fast? I don't want to step on toes or take articles in non-intended directions. I certainly don't want to create work for others if my changes aren't desired by forcing admins to roll back my changes. Or, would you rather I made the changes I think need to be made, attempt to describe them in the space provided and allow others to censure me if I wander or mangle? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] HowTos/PXE/PXE_Setup add?
From: Vitor Afonso Strabello, Friday, September 11, 2009 5:51 PM Also I got one link about this. I think that is better a checkou, not sure if this will be usefult: http://www.linux-mag.com/id/6747 Have a nice weekend, Vitor Yes, that is an excellent article. It has a a few things specific to their setup, though. They have multiple subnets. They provide IP addresses only for defined machines; They must have a separate mechanism for other machines. Of course, the extra information can be useful as an extensive example, provided the person using it can filter out what they don't need. Thank you for the reference. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] HowTos/PXE/PXE_Setup add?
Anybody mind if I add explanations to HowTos/PXE/PXE_Setup and maybe make it a little prettier? Ed Heron ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] doc: TipsAndTricks/ApacheVhost[Dir,Default]
From: Ralph Angenendt, Thursday, September 10, 2009 3:30 AM Am I able to rename them to move them from my directory to the TipsAndTricks directory? Yes, now you can. Thanks. After renaming, I had to verify the change log. Very nice that it is still available. Or should they go to HowTos? No. And please add a section Apache Tips to the page while you are at it (when linking from the TipsAndTricks main page. Done. I put it after Tools and Applications. I considered making Apache Tips a sub-section, but there wasn't precedence. If you have any questions, ask. All set. Ralph ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] doc: TipsAndTricks/ApacheVhost[Dir,Default]
Has there been sufficient discussion about these pages? Am I able to rename them to move them from my directory to the TipsAndTricks directory? Or should they go to HowTos? Ed Heron ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] modification notification messages
From: Ralph Angenendt, Friday, September 04, 2009 4:33 AM On Thu, 2009-09-03 at 15:41 -0600, Ed Heron wrote: Spam filtering is rather limited on this account, so I think it unlikely, but not impossible. You should have gotten a mail. Yes! I received a lovely message with a diff-like description of changes. Did you do anything? I didn't get a notification message when TimothyLee made changes on 2009-07-26... If it is working, now, I'll trust it will continue to work. When I make a change, I don't see my username listed as being notified... Yes, that doesn't work. You changed it yourself, so you don't get a notification. I assumed it would make that choice. Status of sending notification mails: [en] [...] EdHeron, [...]: Mail sent OK Thanks! ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] doc?: TipsAndTricks/ApacheVHostDir
From: Manuel Wolfshant, Thursday, September 03, 2009 5:39 PM I would provide a few more details under the Virtual Host files can be placed in the configuration directory directly or by link. category (i.e. about the separate folder with configs and symlinks to conf.d/vhost.d). Do you (or anybody else, since Manuel might be on vacation, already) know of a url that might describe linking files? I was nervous that if I put it 'in line' I'd be opening a larger can of worms and expanding the document beyond what a TipsAndTricks page should be. An applicable example might make too strong a suggestion about where to put virtual host web data... Or should I stir things up and write a page about where to put virtual hosts? (hint: I don't like /var/www, I like creating a group and user for the website and putting it into that user's home directory. It simplifies access control, including updates. It also makes it less wierd when sharing the webspace out using NFS or Samba) But yes, now it looks much better. Even though your over engineered method is way too complex, given that simply dropping the configuration files in the default conf dir achieves the very same result with much less effort and, more important, no risk of breakage during updates. I can't bring myself to put virtual host files in conf.d. Let's just say I'm borderline OCD... I don't like my module config files and my virtual host files touching. ot type='personal'Oddly enough, though, I have no problem with my vegetables touching my protein and/or my starch./ot The extra information might be useful in a conceptual way to someone. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] doc?: TipsAndTricks/ApacheVHostDir
Are there any other opinions? Questions? Is my suggestion to add ./vhost.d/ to the Apache configuration as a user installable option not acceptable? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] modification notification messages
Is there a way for us to add ourselves to the list of people notified of modifications for the documents we are writing/supporting? Ed Heron ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] modification notification messages
From: Patrice Guay, Thursday, September 03, 2009 11:52 AM Ed Heron wrote: Is there a way for us to add ourselves to the list of people notified of modifications for the documents we are writing/supporting? On the top of wiki pages, there is a 'Subscribe' link pointing to http://wiki.centos.org/__your_page_of_interest?action=subscribe I imagine subsequent modifications will be sent to subscribers. That is what I assumed. Pages that I have created have the unsubscribe option, when I view them, implying I am subscribed... I have verified that I have Subscribe to trivial changes checked in my profile and my pages are listed in Subscribed wiki pages. However, I have not received notification of changes to my pages made by others. (I'm not expecting notification of changes that I've made) ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] doc?: TipsAndTricks/ApacheVHostDir
From: Manuel Wolfshant, Thursday, September 03, 2009 12:39 PM On 09/03/2009 07:02 PM, Ed Heron wrote: Are there any other opinions? Questions? Is my suggestion to add ./vhost.d/ to the Apache configuration as a user installable option not acceptable? From a technical point of view, your suggestion seems 100% correct, including the selinux context needed for the new directory [*]. However I still think that it simply duplicates the existing functionality of the conf.d folder (which, in my opinion, exists with the very purpose of adding new configuration files -- including the definition of virtual hosts) and therefore it is useless. I added some information to describe my position. I have no problem if you want to add a section describing your point of view. If nothing else, we are providing information to users. On the other hand, I do like your proposal from http://wiki.centos.org/EdHeron/ApacheVhostDefault (minus the first subparagraph of paragraph #5, of course). Thanks! [1] I am not sure what will happen after a full relabeling of the system, since the new directory does not exist in the selinux database (I mean /etc/selinux/targeted/contexts/files/file_contexts, part of selinux-policy) I added a disclaimer. Does it cover it? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] doc?: TipsAndTricks/ApacheVHostDir
- Original Message - From: Filipe Brandenburger filbran...@gmail.com To: Mail list for wiki articles centos-docs@centos.org Sent: Thursday, September 03, 2009 12:56 PM Subject: Re: [CentOS-docs] doc?: TipsAndTricks/ApacheVHostDir Hi, On Thu, Sep 3, 2009 at 14:39, Manuel Wolfshantwo...@nobugconsulting.ro wrote: On 09/03/2009 07:02 PM, Ed Heron wrote: Is my suggestion to add ./vhost.d/ to the Apache configuration as a user installable option not acceptable? I still think that it simply duplicates the existing functionality of the conf.d folder (which, in my opinion, exists with the very purpose of adding new configuration files -- including the definition of virtual hosts) and therefore it is useless. +1 on using conf.d/ directory. Your Wiki page reads The issue with [using conf.d/] is that, since the files in conf.d/ are included with the module configuration files, the virtual host definitions would come before other options that could effect them. It is unclear whether the virtual host inherits the configuration items defined after the virtual host is defined. That is not true, VirtualHost sections will inherit everything that is in the main config file, independent of being before or after the virtual host definition. There is an evidence of that in Apache documentation: Sections inside VirtualHost sections are applied after the corresponding sections outside the virtual host definition. This allows virtual hosts to override the main server configuration. (in http://httpd.apache.org/docs/2.2/sections.html) The only thing that matters on position of VirtualHosts in the config file is their relative position to other VirtualHosts used to determine which one of them will be the default, and there I believe your other page gives two very interesting tips on how to define that. Cheers, Filipe ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] doc?: TipsAndTricks/ApacheVHostDir
From: Filipe Brandenburger, Thursday, September 03, 2009 12:56 PM ... Your Wiki page reads The issue with [using conf.d/] is that, since the files in conf.d/ are included with the module configuration files, the virtual host definitions would come before other options that could effect them. It is unclear whether the virtual host inherits the configuration items defined after the virtual host is defined. That is not true, VirtualHost sections will inherit everything that is in the main config file, independent of being before or after the virtual host definition. There is an evidence of that in Apache documentation: Sections inside VirtualHost sections are applied after the corresponding sections outside the virtual host definition. This allows virtual hosts to override the main server configuration. (in http://httpd.apache.org/docs/2.2/sections.html) Thanks for the reference! OK. That helps. That page seems to be saying that the configuration options are stored (reordered) and possibly only processed when a request is received. I still like my method and the other parts of my argument, but I can see that putting virtual host config files in conf.d is not invalid or risky. Give me a few. I'll modify my page to take my new world view into account. The only thing that matters on position of VirtualHosts in the config file is their relative position to other VirtualHosts used to determine which one of them will be the default, and there I believe your other page gives two very interesting tips on how to define that. Thanks! At least I'm not 'just' annoying everyone... Cheers, Filipe ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] doc?: TipsAndTricks/ApacheVHostDir
From: Filipe Brandenburger, Thursday, September 03, 2009 1:27 PM Hi, On Thu, Sep 3, 2009 at 15:13, Ed Herone...@heron-ent.com wrote: [1] I am not sure what will happen after a full relabeling of the system, since the new directory does not exist in the selinux database (I mean /etc/selinux/targeted/contexts/files/file_contexts, part of selinux-policy) I added a disclaimer. Does it cover it? The right way to fix it is to use semanage fcontext (see man semanage) to make that change permanent even after a relabel. I believe it should be something like: # semanage fcontext -a -t httpd_config_t /etc/httpd/vconf\.d(/.*)? After that, you can use restorecon instead of chcon: # restorecon -R /etc/httpd/vconf.d I did not test those above, so if you want to add them to the Wiki page you should test them before you do. Interestingly... # semanage fcontext -l | grep http returns, among other things, /etc/httpd(/.*)? all files system_u:object_r:httpd_config_t:s0 so, the newly created directory is covered... I also found... /etc/vhostsregular file system_u:object_r:httpd_config_t:s0 Not entirely sure what that is there for, except to cover people doing wierded things than I'm proposing... When I: # mkdir /etc/httpd/yadda # ls -lZ /etc/httpd I get: drwxr-xr-x root root system_u:object_r:httpd_config_t conf drwxr-xr-x root root root:object_r:httpd_config_t yadda next: # restorecon -R /etc/httpd and # ls -lZ I get the same thing. So, it isn't changing the SELinux user.. I'm guessing we should... # chcon --user=system_u yadda but it would be optional? But I still agree that just using conf.d achieves exactly the same results with a lot less work, so it would still be my advice... I now agree that the same results are achieved with virtual host files in conf.d I have updated the page. Have I acceptably promoted the 'preferred' method? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] modification notification messages
From: Ralph Angenendt, Thursday, September 03, 2009 1:26 PM Am 03.09.09 20:35, schrieb Ed Heron: I have verified that I have Subscribe to trivial changes checked in my profile and my pages are listed in Subscribed wiki pages. However, I have not received notification of changes to my pages made by others. (I'm not expecting notification of changes that I've made) That shouldn't happen. Are you sure that those don't land in some sort of spam filter on your side? Spam filtering is rather limited on this account, so I think it unlikely, but not impossible. Do you have a page handy with which I could test? When I make a change, I don't see my username listed as being notified... Please, I am subscribed to http://wiki.centos.org/HowTos/CentOS5ConvertToRAID and http://wiki.centos.org/EdHeron/ApacheVhostDefault ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] document proposal: TipsAndTricks/ApacheVHostDir
On Fri, Aug 21, 2009 at 3:41 PM, Ed Herone...@heron-ent.com wrote: ... I've written a quick little article detailing how to create a vhost directory under CentOS. ... From: Brian Mathis, Friday, August 21, 2009 1:52 PM I always figured that the CentOS way to handle that was to put them into the conf.d folder. Is there an advantage to using this method? One thing I can think of is that the conf.d is included in the middle of the httpd.conf file, while this would be at the bottom. On 08/22/2009 12:12 AM, Ed Heron wrote: That is exactly my reasoning. The config file, as distributed, has the virtual host containers at the end of the file. From: Manuel Wolfshant, Friday, August 21, 2009 3:31 PM No, the config file as distributed has - just like the original apache config - an example at the end of it. I do understand that there is already a config file directory. However, the example virtual host is at the end of the the distributed Apache config file. From that positioning, I conclude that it is recommended to have the virtual host stuff at the end, rather than the middle. The existing include is in the middle, therefore, (I'm concluding that) it is not recommended. conf.d appears to be for module config files. I don't know if the virtual host only inherits configuration directives that are defined before it is. If that is the case, any configuration items after the conf.d include would not apply to the virtual hosts (though this is easy to test). Even if that is not the case, it still seems that putting virtual host files in conf.d is improper. Putting virtual host files in conf.d may work but appears to be a shortcut. While nobody would suggest you can't take a shortcut, if it works for you, there should be an official method. To me, moving virtual hosts out of the main config file requires a separate directory. It may be my 'heritage' but separate directories is how it is done in Gentoo. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] document proposal: TipsAndTricks/ApacheVhostDefault
Draft at http://wiki.centos.org/EdHeron/ApacheVhostDefault Obviously, if ApacheVhostDir is not accepted, I'd remove the parts that refer to my vhost.d... ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] document proposal: TipsAndTricks/ApacheVHostDir
From: Manuel Wolfshant, Saturday, August 22, 2009 2:00 PM While we are at it, let's also add a folder for all existing modules and another one for symlinks of active modules, pointing back to the first folder. And also, let's have all vhosts in a folder, but all active vhosts should be symlinks to them, from another folder. And why not compile the binary from source, that's how gentoo does it ! I didn't realize I was inviting sarcasm. I don't think it is appropriate in this forum. I was, apparently unreasonably, expecting calm, thought out discussion followed by a consensus. I was merely suggesting I am not alone in my opinion. As were you when you made reference to Fedora method. Both Fedora and Gentoo are merely alternate examples of GNU/Linux distributions. Just because an idea is used in another distribution, whose basic tenents you don't agree with, doesn't make the idea useless or valueless or, worse, worthy of scorn. CentOS has a philosophy of method. Apache has a philosophy of method. I am making a suggestion that I believe fits with both that would make a more proper solution than putting the virtual host files in conf.d. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] document proposal: TipsAndTricks/ApacheVHostDir
I use named virtual hosts on my web servers, as I'm sure many others do. I'm used to the method of using a vhost directory for the container files. I didn't find documentation for it in the CentOS docs or the Apache docs. I'm not sure if I should take it as a hint that it is depreciated... If I've missed something, please point me to it. I've written a quick little article detailing how to create a vhost directory under CentOS. It is at http://wiki.centos.org/EdHeron/ApacheVhostDir Please, consider this a request to create the page TipsAndTricks/ApacheVhostDir with access given to wiki user EdHeron. Ed Heron ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] document proposal: TipsAndTricks/ApacheVHostDir
From: Brian Mathis, Friday, August 21, 2009 1:52 PM On Fri, Aug 21, 2009 at 3:41 PM, Ed Herone...@heron-ent.com wrote: ... I've written a quick little article detailing how to create a vhost directory under CentOS. ... I always figured that the CentOS way to handle that was to put them into the conf.d folder. Is there an advantage to using this method? One thing I can think of is that the conf.d is included in the middle of the httpd.conf file, while this would be at the bottom. That is exactly my reasoning. The config file, as distributed, has the virtual host containers at the end of the file. Using a separate vhost directory maintains this. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] document proposal: TipsAndTricks/ApacheVHostDir
From: Filipe Brandenburger, Friday, August 21, 2009 2:03 PM # service httpd graceful Thanks! ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] How to pass messages from dom0 to domU??
From: David Knierim, Wednesday, July 22, 2009 3:18 PM I apologize if this is a newbie question, but I have been unable to work out how to do this. I am adding code to my installation on dom0 (running CentOS 5.3) to monitor for hardware faults. If there is an issue, I want to propagate the status to all of the domUs (running CentOS 4.x or CentOS 5) running on the host. What are my options to do this?? I would use shared file space. Maybe an NFS share that all machines could access... That way it is not restricted to virtual machines running on that server. If you expanded to 2 servers for increased capacity or fault tolerance, you would not have to redesign it. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-docs] New template for Homepage
From: Dag Wieers, Thursday, June 04, 2009 7:08 PM Hey, I reworked the HomepageTemplate since the original one was pretty empty. You can find my proposal here: http://wiki.centos.org/HomepageTemplate But to see how it looks properly, I adapted my Homepage to look like it: http://wiki.centos.org/DagWieers I'd like to open a discussion about what items belong on this page and how we can improve it. ... So what do people think ? What is missing ? ... A more fleshed out template certainly does a better job of guiding new personal page developement and providing examples. I think I see that the new template encourages a specific ordering of sections that focuses on the person's relationship to the project. Meaning you've put the relationship before the person's biography. I agree. I suggest that 'List of Achievements' might sound better as 'Contributions'. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] Tips and tricks : create image file from CD/DVD?
Should the wiki have a Tips and Tricks page for creating a ISO file from a CD or DVD? I realize this information is everywhere. Including http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-steps-network-installs-ppc.html I don't, however, find it on the wiki... Is it within the scope of the wiki project to have it somewhere? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Tips and tricks : create image file from CD/DVD?
From: JohnS, Friday, May 15, 2009 12:18 PM On Fri, 2009-05-15 at 12:01 -0600, Ed Heron wrote: Should the wiki have a Tips and Tricks page for creating a ISO file from a CD or DVD? I realize this information is everywhere. Including http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-steps-network-installs-ppc.html I don't, however, find it on the wiki... Is it within the scope of the wiki project to have it somewhere? --- http://wiki.centos.org/TipsAndTricks/CDtoDVDMedia The description on that page... -- The following script (mkdvdiso.sh) has been tested for CentOS 4 and 5 i386 to create DVD ISO images from CD images, or from an installation tree. If the installation tree does not contain a .discinfo file, one must be obtained from the top level of a CD. -- seems to be describing creating a DVD image from a CD image or a source directory, not how to create a image from a CD or DVD. I'm just talking about the dd if=/dev/cd of=/usr/share/cd.iso command. Useful for creating boot images for virtual machines and cd images for cd/dvd servers. with maybe a suggestion of where to put the image, like /var/lib/xen/images for xen or maybe /usr/share for other uses. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Comments? HowTos/CentOS5ConvertToRAID
From: Phil Schaffner, Wednesday, May 13, 2009 6:20 AM It just works. I habitually use rsync for incremental updates across directories or systems, but tar is often more robust for this type of job, just because of things like needing to remember to use -H. Both rsync and cpio will work if used properly, just like tar. Like I said, largely a matter of preference. I read somewhere that tar doesn't save extended attributes. Is this still the case or did I read old news? Should we submit a bug report somewhere for rsync not correctly copying SELinux attributes? Or is it some mistake of mine that it didn't appear to work? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Comments? HowTos/CentOS5ConvertToRAID
From: Ralph Angenendt, Wednesday, May 13, 2009 9:42 AM What happens when you set --xattrs in rsync, too? Their manual page does not mention SELinux, though. That's the X that I added to the rsync command. It does not successfully copy SELinux attributes. That's why I had to set the relabel flag. I'll have to try the process again with the --xattrs in tar and see if the system is functional without re-labeling. Thanks. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] Comments? HowTos/CentOS5ConvertToRAID
From: Ed Heron, Tuesday, May 05, 2009 2:16 PM My first draft of http://wiki.centos.org/HowTos/CentOS5ConvertToRAID is complete. Please, give it a once or thrice over and let me know what you think. I didn't go into too much detail with some steps. If you think a specific step needs more explanation, let me know. Has anybody had a chance to look at this? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Comments? HowTos/CentOS5ConvertToRAID
haven't yet, but will do so later today. And if nobody complains, hey, it probably is a good article :) Ralph Either that or I've hit a target nobody is interested in... OK. It's a great article and nobody has any suggestions or problems... I'm batting 1000... yeah, that. Thanks. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Comments? HowTos/CentOS5ConvertToRAID
From: Phil Schaffner, Tuesday, May 12, 2009 2:11 PM Ed Heron wrote: Has anybody had a chance to look at this? Moving it up on my to-do list... Thanks. When cloning the root partition need to add H to the rsync flags to preserve hard links. Don't think /boot uses hard links, but wouldn't hurt to use it there also... I'm not sure how well it would do that, but it won't hurt to add. I'll have to put in a hard link and copy across devices and see if the hard linked files are hard linked on the dest dev. Thanks for catching that. I don't use hard links much... ... An often-recommended alternative is to use tar: tar -C /mnt/boot.old -cf - . | tar -C /mnt/boot.new -xf - tar -C /mnt/root.old -cf - . | tar -C /mnt/root.new -xf - Probably a matter of preference. I think so. I use rsync to synchronize samba shares and web sites between servers so I've gotten used to using it for other things. It also looks more like a copy, which might be easier to understand for those less familiar. I was considering adding the tar option. How does tar handle hard links? At step 6, since everything has already been cleanly unmounted, should just be able to hit the power button. Add something to the effect of Remove the rescue media before rebooting. I've added the cleanly unmounted / power switch aspect and moved the 'remove rescue media' to the booting back up portion of the testing step. Does that look better? I debated briefly with myself over suggesting they could simply power it off and had discarded it as not best practice. I'm reasonably happy with the compromise. I'll have to check if install / rescue has a shutdown command available... That's all the comments I have without actually going through testing the procedure. Will try that later if I get a round tuit. :-) Nice job. Will reference it from the HowTos/SoftwareRAIDonCentOS5 page when it goes live. Thanks. Writing documentation is always a balancing act between not putting enough detail in because it seems intuitive to the person who does it every day and putting too much in with the effect of it being too pedantic. I like that the contents becomes a checklist for repeatable processes. Do you have a source for round tuits? I can only find finite sided ones... Phil ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] HowTo/RAID/convert non-RAID CentOS 5 system tosoftware RAID1 using rescue mode
From: Phil Schaffner, Wednesday, April 29, 2009 8:31 AM Having a RAID section in the HowTos page makes sense to me, rather than cluttering up Misc. Does not require /RAID/ in the directory structure. How about HowTos/CentOS5ConvertToRAID for a more Wiki-like name? Works for me. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Updated How to Setup a Software RAID on CentOS 5
From: Phil Schaffner, Tuesday, April 28, 2009 5:36 PM I have attempted to address all comments: http://wiki.centos.org/HowTos/SoftwareRAIDonCentOS5 Give me your best shot! :-D Phil There's always going to be an argument about whether to put /boot and swap on RAID. It's all about performance most of the time being slightly better versus stability in the event of device failure. What's the disaster recovery plan here? Obviously, if the second drive fails, there's no issue. Standard removal and eventual addition of replacement device(s). If the first drive fails, are we hoping the computer will boot off the second drive or are we moving the second drive to the first interface? Is it outside the scope of this document to describe and test disaster recovery? I think it is. I'm just making a note to suggest a further complimentary page at some time in the future... (though, at this time, I am NOT volunteering to write it) Is there a wiki page todo list somewhere? ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] HowTo/RAID/convert non-RAID CentOS 5 system to software RAID1 using rescue mode
Does documentation exist describing how to convert a simple, single disk non-RAID CentOS 5 system to software RAID1 using the CentOS install CD/DVD as a rescue disk? (Assuming not) Is there a need for such? (Assuming need) I volunteer to produce it. Ed Heron ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
