similar to: Is there a plan for managing physical servers as well ?

This lays 90% of the groundwork needed on the server side to support the use of a remote ipa server. Leaving the option disabled in the installer until the necessary node integration(dns/keytab placementi location) is completed Also apply: [PATCH server] update ovirt-add-host to use ipa commands instead of kadmin.local [PATCH server] separate ipa common tasks freeipa::common and rename

LinkedIn ------------ J'aimerais vous inviter ? rejoindre mon r?seau professionnel en ligne, sur le site LinkedIn. Fabien Fabien Dupont Architecte Syst?me Unix/Linux chez CEA France Veuillez confirmer que vous connaissez Fabien Dupont?: https://www.linkedin.com/e/h24oga-h02h13s2-1w/isd/6381163954/lTfQQJ_9/?hs=false&tok=2oumAa6oXER581 -- Vous recevez des invitations ? vous connecter

Hello, I have the following question. How to install ovirt in working environment? Details: I want to install ovirt server on a physical host with Fedora 10 (Intel, no VT). I installed rpms from ovirt repo as stated on website. I allready have ipa, cobbler, dns, dhcp, nfs, two networks and such set up and working. I want to preserve this setup. The host I am installing ovirt on is ipa

This removes the appliance configuration bits from the installer and associated files since it has been deprecated --- installer/modules/ovirt/files/cobbler-import | 6 - .../modules/ovirt/files/ovirt-appliance-setup | 4 - installer/modules/ovirt/files/ovirt-storage | 73 ---------- installer/modules/ovirt/manifests/appliance.pp | 152 -------------------- 4 files

Hi, I installed ovirt on fedora 12 (64 bits) successfully but I had to make some changes to make it work. 1. Installation from rpms builded from the lastest git version 2. Patch ace : missing backslashes in sed commands vim /usr/share/ace/modules/ovirt/manifests/freeipa.pp line 33 : '/\\[kdcdefaults\\]/a \\ kdc_ports = 88' single_exec {"set_kdc_defaults":

There are lots of exciting things happening in the CentOS ecosystem at the moment, by which I mean "upstream" or "across stream" in Fedora and RHEL. I'm thinking of projects that equip RH-like EL in general for serious entry into the enterprise, things like the Fedora Directory Server, and RedHat's Emerging Technologies projects such as Cobbler, FreeIPA and Ovirt.

In this case, shouldn't that be done by the upload-disk API ? When you upload a VM, oVirt knows what to do with it and handle the locking and any operations required to make the VM an oVirt VM. On 27 February 2018 at 13:53, Tomáš Golembiovský <tgolembi@redhat.com> wrote: > On Tue, 27 Feb 2018 13:43:59 +0100 > Fabien Dupont <fdupont@redhat.com> wrote: > > > We can

Announcing oVirt 0.99 ===================== We are pleased to announce the release of oVirt 0.99, a significant step forward in stability and feature set for oVirt project users. Some highlights from the change log: * Improved installer, oVirt Server will now install with an existing FreeIPA setup present rather than insisting on installing FreeIPA from scratch * Anyterm console support --

On Tue, 27 Feb 2018 13:43:59 +0100 Fabien Dupont <fdupont@redhat.com> wrote: > We can still find them and run the sysprep, but I have > the feeling that it would be more logical if virt-v2v did the sysprep when > target is oVirt / RHV. This is trickier than you think. For LVM volumes somebody (VDSM) has to lock and prepare the disks for you first and there is no external API to do

New code tries SIGTERM first, with a grace period of 30 seconds: https://github.com/ManageIQ/manageiq-content/pull/433. On Wed, Sep 26, 2018 at 6:10 PM Richard W.M. Jones <rjones@redhat.com> wrote: > On Wed, Sep 26, 2018 at 04:57:19PM +0200, Fabien Dupont wrote: > > It's not virt-v2v-wrapper that kills virt-v2v, it's ManageIQ. We have the > > PID from

On Wed, Sep 26, 2018 at 4:25 PM Richard W.M. Jones <rjones@redhat.com> wrote: > On Wed, Sep 26, 2018 at 02:40:54PM +0200, Fabien Dupont wrote: > > [Adding Tomas Golembiovsky] > > > > Well, that's mainly IMS related challenges. We're working on > > OpenStack output support and migration throttling and this implies > > changes to virt-v2v-wrapper.

On my current instance, the meta_data.json is the following: { "availability_zone": "nova", "devices": [], "hostname": "ims-host-1", "keys": [ { "data": "ssh-rsa

On Mon, Sep 24, 2018 at 6:30 PM Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Sep 24, 2018 at 10:00:21AM +0200, Fabien Dupont wrote: > > Hi, > > Hi Fabien, sorry I didn't respond to this earlier as I was doing some > work. If you CC me on emails then you can usually get a quicker > response. > > > I've read the virt-v2v OpenStack output code

This set the cobbler modules dns/dhcp to dnsmasq, removes a duplicate ip replacement in /etc/cobbler/settings, and sets the ip address to the admin network instead of the guest networkwhere it should've been in the first place. --- installer/modules/ovirt/files/modules.conf | 4 ++-- installer/modules/ovirt/manifests/cobbler.pp | 16 ++++------------ 2 files changed, 6 insertions(+),

Hi, I've read the virt-v2v OpenStack output code to understand how it works and I've seen this: > (* The server name or UUID of the conversion appliance where > * virt-v2v is currently running. In future we may be able > * to make this optional and derive it from the OpenStack > * metadata service instead. > *) > server_id : string; Indeed, it can be

On Tue, Sep 25, 2018 at 10:20:07AM +0200, Fabien Dupont wrote: > "uuid": "7ee62bdc-1c9d-4193-bb8f-fdbbbdfded0f" > } > > The information we need is the uuid. I don't have a way to test it, so this is only compile tested, however something like this? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming

Running sysprep is quite easy today because we use the export domain, which is frequently NFS. So we simply mount it on the conversion host and run sysprep against the disks of the converted VM before it is imported. Soon, we want to skip the export domain, so the disks of the VM will be in a separate domain. We can still find them and run the sysprep, but I have the feeling that it would be more

Hi, I'm experiencing a weird behavior when tried to use guestmount with a XFS formatted volume. I have created a RHEL 8 virtual machine using libvirt. I have retrieved the disk image on a RHEL 7.7 server to mount the image root filesystem and explore it. The command returns an error message: # guestmount -a /disks/jamesdream.qcow2 -m /dev/sda1 /mnt/ libguestfs: error: mount_options: mount

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

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 behavior for OpenStack, i.e. have virt-v2v create the instance once the volumes have been created.