Awesome! Is it worth while trying it now, or should I wait for 3.4 beta?
On Fri, Jan 10, 2014 at 8:47 AM, Itamar Heim <ih...@redhat.com> wrote: > On 01/08/2014 02:49 PM, Doron Fediuck wrote: > >> >> >> ----- Original Message ----- >> >>> From: "Doron Fediuck" <dfedi...@redhat.com> >>> To: "Andrew Lau" <and...@andrewklau.com> >>> Cc: "users" <users@ovirt.org> >>> Sent: Wednesday, January 8, 2014 2:48:20 PM >>> Subject: Re: [Users] virtualized engine / port to self-hosted engine >>> >>> >>> >>> ----- Original Message ----- >>> >>>> From: "Andrew Lau" <and...@andrewklau.com> >>>> To: "Yedidyah Bar David" <d...@redhat.com> >>>> Cc: "users" <users@ovirt.org> >>>> Sent: Wednesday, January 8, 2014 11:15:21 AM >>>> Subject: Re: [Users] virtualized engine / port to self-hosted engine >>>> >>>> On Tue, Jan 7, 2014 at 2:43 AM, Yedidyah Bar David < d...@redhat.com > >>>> wrote: >>>> >>>> >>>> >>>> ----- Original Message ----- >>>> >>>>> From: "Blaster" < blas...@556nato.com > >>>>> To: "Yedidyah Bar David" < d...@redhat.com > >>>>> Cc: users@ovirt.org >>>>> Sent: Monday, January 6, 2014 5:20:00 PM >>>>> Subject: Re: [Users] virtualized engine / port to self-hosted engine >>>>> >>>>> On 1/6/2014 7:12 AM, Yedidyah Bar David wrote: >>>>> >>>>>> Did you have problems with engine-backup? Or had other reasons to not >>>>>> use it? Thanks! >>>>>> >>>>> >>>>> Can engine-backup be used to move an AIO configuration from one host to >>>>> another? >>>>> >>>> >>>> I didn't try that. In principle it can. Note that it will only >>>> backup/restore >>>> the engine - not local storage domains (ISO or data), VM images, etc. >>>> >>>> If you try that, please report back. Thanks! >>>> >>>> >>>>> I currently need to move an AIO configuration from AMD hardware to >>>>> Intel >>>>> I7 hardware. The engine-backup WIKI discusses backups, but not >>>>> restores. I am a bit concerned about using engine-backup to restore an >>>>> AIO configuration to a different system as another WIKI page with >>>>> step-by-step instructions to do what engine-backup does for you, >>>>> mentions you have to do some extra steps if you are changing hostnames >>>>> as the hostname of the ovirt-engine is embedded in the database. >>>>> >>>> >>>> Changing the hostname is specifically not in the scope of engine-backup. >>>> >>>> Note that you do not need to have the hostname equal to the "fqdn" input >>>> during engine-setup - this last one just needs to be dns-resolvable and >>>> point to the machine intended. >>>> >>>> Also, there is another utility to do that, called ovirt-engine-rename - >>>> see this for details and implications: >>>> >>>> http://www.ovirt.org/Changing_Engine_Hostname >>>> >>>> >>>>> There really needs to be some work done in Ovirt on making it easier to >>>>> import existing disk images and just generally moving things around >>>>> without having to bounce off an NFS server. >>>>> >>>>> Should I do a BZ on that? >>>>> >>>> >>>> Not sure what you mean exactly, but you are always welcome to open BZs >>>> on >>>> bugs/RFEs... >>>> >>>> Best regards, >>>> -- >>>> Didi >>>> >>>> Sorry for going slightly off topic, but how is everyone's hosted engine >>>> deployment going? Are you restricted to NFS? >>>> >>>> Andrew, in general I get positive feedbacks from RHEL users. For Fedora >>> and other distros, this should be in a better situation in the following >>> 1-2 weeks when we'll have 3.4 beta available. >>> I'd love to get your feedback on it. >>> >>> I missed your NFS question, sorry; >> Yes. Currently we have NFS limitation and we will do our best to see >> if SAN can be added. Note that time is not on our side for 3.4. >> > > worth mentioning you can use hosted engine on an iscsi/FC cluster - just > the hosted engine VM needs to be on NFS > > > >> I tried the migration procedure last month and it worked.. but had quite >>>> a >>>> lot of issues so I ended up reverting back. I didn't open any bugs in >>>> the >>>> assumption it was in super alpha stage. >>>> >>>> Next time please open bugs... That's the best way to improve the >>> project, >>> regardless of the version state. If unsure, you can always try irc / this >>> list >>> first to see if this is a known issue and if there are workarounds. >>> >>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users@ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> >>>> _______________________________________________ >>> Users mailing list >>> Users@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> _______________________________________________ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users