similar to: Gluster Community Congratulates OpenStack Developers on Havana Release

I''m happy to announce the release of version 2.0 of the Puppet Labs OpenStack modules to the Puppet Forge. These modules handle the deployment and management of the latest Grizzly releases of OpenStack, including Keystone, Swift, Glance, Cinder, Nova, and Horizon. Additionally, an OpenStack module is provided for single or multi-node deployments. Here is a set of links to the Forge

Joe, Agree with you on turning this around into something more positive. One aspect that would really help us decide on our next steps here is the actual number of deployments that will be affected by the removal of the gluster driver in Cinder. If you are running or aware of a deployment of OpenStack Cinder & Gluster, can you please respond on this thread or to me & Niels in private

Hello, setting up the newest OpenStack Grizzly release seems to be really straight-forward. Red Hat has put together all support for this at http://openstack.redhat.com/. I've documented installation, post-install config tweaks, how to add a few ready-to-use guest images and links to a few gotchas on the following wiki page: http://jur-linux.org/testwiki/index.php/CloudLinux/OpenStack

On Wed, Sep 26, 2018 at 09:57:22AM +0200, Fabien Dupont wrote: > Hi, > > There has been discussion about the OpenStack output and Richard asked for > a public thread on this list, so here it is. > > For v2v from VMware to RHV, there is a Python script that does some extra > steps to create the virtual machine after the disks have been converted. We > want to have the same

In some cases we have observed the time taken for a Cinder volume to attach to the conversion appliance can be longer than the current 60 seconds. Increase the timeout to 5 minutes. Thanks: Ming Xie. --- v2v/output_openstack.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/output_openstack.ml b/v2v/output_openstack.ml index caaedf452..e395ccb37 100644 ---

If ‘virt-v2v -oo insecure’ is used then ‘openstack --insecure’ flag is added whenever we invoke the openstack command. This turns of SSL certificate validation. --- v2v/output_openstack.ml | 14 +++++++++++++- v2v/virt-v2v-output-openstack.pod | 1 + v2v/virt-v2v.pod | 7 +++++++ 3 files changed, 21 insertions(+), 1 deletion(-) diff --git a/v2v/output_openstack.ml

(Apologies if I missed anyone off the To: line. Please add anyone else who is interested, but keep the libguestfs public mailing list) I did some preparatory work on adding the new ‘virt-v2v -o openstack’ output mode. I've put it in a private (non-FFwd) branch here: https://github.com/rwmjones/libguestfs/tree/openstack Most of the work was refactoring virt-v2v so that we have all of the

If ‘virt-v2v -oo verify-server-certificate=false’ is used then ‘openstack --insecure’ flag is added whenever we invoke the openstack command. This turns off SSL certificate validation. The default is to verify the server certificate (which is the default of the openstack command). --- v2v/output_openstack.ml | 16 +++++++++++++++- v2v/test-v2v-o-openstack.sh | 2 ++

We are looking at vCloud and OpenStack for our University Cloud offering (research and education). I''m curious what anyone''s experiences have been. We have an OpenStack ("Essex") installation now, but we are looking to upgrade to Grizzly or move to vCloud. Other than that cloud instance, we are a vmWare shop so moving to vCloud may be easier for us in terms of

Hello, I was very thrilled when I found openstack module since I am in the process of doing some "heavy" testing However I was not able to use it due to the "Could not find declared class quantum::db::mysql" error There is no quantum module available as part of the openstack module installation Here is a directory listing: ls /etc/puppet/modules apache apt cinder

On Wed, Sep 26, 2018 at 11:39 AM Richard W.M. Jones <rjones@redhat.com> wrote: > On Wed, Sep 26, 2018 at 09:57:22AM +0200, Fabien Dupont wrote: > > Hi, > > > > There has been discussion about the OpenStack output and Richard asked > for > > a public thread on this list, so here it is. > > > > For v2v from VMware to RHV, there is a Python script that

Improves the error message when openstack is not installed: $ virt-v2v -i disk fedora-28.img -o openstack virt-v2v: error: no binary called ‘openstack’ was found on the $PATH. We use this program to communicate with OpenStack so it must be installed to use this output mode. --- v2v/output_openstack.ml | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git

This patch implements output to OpenStack Cinder volumes using OpenStack APIs. It has only been lightly tested, but appears to work. There are some important things to understand about how this works: (1) You must run virt-v2v in a conversion appliance running on top of OpenStack. And you must supply the name or UUID of this appliance to virt-v2v using the ‘-oo server-id=NAME|UUID’ parameter.

Since this output method was written the code has always been capable of adding the hw_firmware_type = uefi image property, and this property has been supported since at least OpenStack 12 which is years old. Interestingly now all of the output modes support both BIOS and UEFI. --- v2v/output_openstack.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/output_openstack.ml

I believe the error indicates that hiera was installed as a rubygem which is not supported on Puppet 3.x. Maybe the error will go away if you remove the hiera gems? I think I have gotten around it by adding ''require rubygems'' to the puppet executable. I''m copying the puppet-users mailing list b/c I am guessing this is a common problem. On Wed, May 1, 2013 at 12:35

FWIW this passes with trunk now (bootstrapped with clang). On Mon, Oct 7, 2013 at 8:33 PM, İsmail Dönmez <ismail at donmez.ws> wrote: > This is with Linux on BeagleBone Black (Cortex-A8), regressed recently: > > > FAIL: LLVM :: MC/ARM/basic-arm-instructions.s (5404 of 8944) > ******************** TEST 'LLVM :: MC/ARM/basic-arm-instructions.s' FAILED >

This is with Linux on BeagleBone Black (Cortex-A8), regressed recently: FAIL: LLVM :: MC/ARM/basic-arm-instructions.s (5404 of 8944) ******************** TEST 'LLVM :: MC/ARM/basic-arm-instructions.s' FAILED ******************** Script: -- /havana/work/llvm/build/Release+Asserts/bin/llvm-mc -triple=armv7-apple-darwin -mcpu=cortex-a8 -show-encoding <

This patch series lifts the previous restriction that virt-v2v would refuse to convert a guest to Glance that had more than one disk. The first patch is just better documentation for the Glance output mode. The second patch contains the change (best viewed with 'git diff -w' since it is mostly a whitespace change). virt-v2v -o glance will now create multiple disks called: - guestname

Hi folks, I'm having a issue in the standard NFS driver on OpenStack, that uses qemu-img and libvirt to create snapshots of volumes. It uses qemu-img in the Controller to manage the snapshots when the volume is not attached (offline) or calls the Compute (which calls libvirt) to manage snapshots if the volume is attached (online). When I try to create/delete snapshots from a snapshot chain.

Folks, I am stumped! I have followed every tech tip I could find and I am still unable to complete my SMB installation. Specifically, I fail Test 4 and Tests 9 and 10. I believe the problem has something to do with the NMBD configuration. Below are the parameters of our system. Any help is greatly appreciated. Brandon Stauber brandon@inetevents.com 310-889-9264 [Please respond