[PATCH] Remove README statement that advises user does not use Kimchi in production
PowerKVM is a good example that Kimchi can be used in production environment. Signed-off-by: Aline Manera <alinefm@linux.vnet.ibm.com> --- docs/README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/README.md b/docs/README.md index de6db91..555ce89 100644 --- a/docs/README.md +++ b/docs/README.md @@ -169,9 +169,7 @@ pool (default path is: /var/lib/kimchi/isos). Known Issues ------------ -1. Kimchi is still experimental and should not be used in a production -environment. -2. When you are using NFS as storage pool, check the nfs export path permission +1. When you are using NFS as storage pool, check the nfs export path permission is configured as: (1) export path need to be squashed as kvm gid and libvirt uid: /my_export_path *(all_squash,anongid=<kvm-gid>, anonuid=<libvirt-uid>,rw,sync) -- 1.9.3
Reviewed-By: Christy Perez <christy@linux.vnet.ibm.com> On 11/19/2014 01:47 PM, Aline Manera wrote:
PowerKVM is a good example that Kimchi can be used in production environment.
Signed-off-by: Aline Manera <alinefm@linux.vnet.ibm.com> --- docs/README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/docs/README.md b/docs/README.md index de6db91..555ce89 100644 --- a/docs/README.md +++ b/docs/README.md @@ -169,9 +169,7 @@ pool (default path is: /var/lib/kimchi/isos). Known Issues ------------
-1. Kimchi is still experimental and should not be used in a production -environment. -2. When you are using NFS as storage pool, check the nfs export path permission +1. When you are using NFS as storage pool, check the nfs export path permission is configured as: (1) export path need to be squashed as kvm gid and libvirt uid: /my_export_path *(all_squash,anongid=<kvm-gid>, anonuid=<libvirt-uid>,rw,sync)
participants (2)
-
Aline Manera -
Christy Perez