----- Original Message ----- > From: "Arman Khalatyan" <arm2...@gmail.com> > To: "Itamar Heim" <ih...@redhat.com> > Cc: "users" <users@ovirt.org>, "Allon Mureinik" <amure...@redhat.com>, "Doron > Fediuck" <dfedi...@redhat.com>, > mskri...@redhat.com > Sent: Monday, October 20, 2014 3:45:46 PM > Subject: Re: [ovirt-users] [ANN] oVirt 3.5 GA Releases > > the second one I am not so sure if it is an bug or a feature? > The numa menu is grayed if the VM is HA. > If one remove the HA and force set VM to run on single node without > migration flag, then numa flag is editable so you can change to > "interleave" mode. > > I believe there's a fix coming for it in 3.5.1. One thing is for sure- proffered should not be used as a default.
So go ahead and open a BZ for it, and we'll see if we still need to fix something or have it resolved already and provide the info. > > On Mon, Oct 20, 2014 at 2:23 PM, Itamar Heim <ih...@redhat.com> wrote: > > > > > On Oct 20, 2014 8:08 AM, Arman Khalatyan <arm2...@gmail.com> wrote: > > > > > > I did not play anything. I had before Ovirt 3.4.4 up and running. > > > After upgrade I got 2 problems: > > > 1) disk profiles are empty > > > 2) numa box by default is preferred- grayed. > > > a. > > > > Then please open an urgent bug. Well. Two. One for each. > > > > > > > > On Mon, Oct 20, 2014 at 1:42 PM, Itamar Heim <ih...@redhat.com> wrote: > > >> > > >> On 10/20/2014 05:56 AM, Arman Khalatyan wrote: > > >>> > > >>> My bad!! > > >>> False Alarm.everything is working after some massaging:) > > >>> 1) start VM get error: error NUMA memory tuning in 'preferred' mode > > only > > >>> supports single node > > >>> 2) stop VM edit properties: > > >>> 2.a)- edit->host->Start Running on->specific host > > >>> 2.b)- edit->host->Migration options->do not allow migration > > >>> 2.c)- edit->host->ConfigureNuma->tune mode->interleave > > >>> Run VM and enjoy. > > >> > > >> > > >> but did you play with the numa definition or this happened on its own > > as part of the upgrade? > > >> > > >>> done! > > >>> > > >>> > > >>> On Mon, Oct 20, 2014 at 11:44 AM, Arman Khalatyan <arm2...@gmail.com > > >>> <mailto:arm2...@gmail.com>> wrote: > > >>> > > >>> My upgrade went well no problems. > > >>> Unfortuneatly I am not able to run any VM on Intel Hosts. > > >>> It throws an error: Exit message: internal error internal error > > NUMA > > >>> memory tuning in 'preferred' mode only supports single node. > > >>> I cannot edit numa menu it is disabled on the VM. > > >>> thanks, > > >>> Arman. > > >>> > > >>> > > >>> On Mon, Oct 20, 2014 at 10:50 AM, Sandro Bonazzola > > >>> <sbona...@redhat.com <mailto:sbona...@redhat.com>> wrote: > > >>> > > >>> Il 20/10/2014 10:13, Tiemen Ruiten ha scritto: > > >>> > Hello, > > >>> > > > >>> > Last week I upgraded to 3.5 and on the engine side > > everything went absolutely fine. Now I'm wondering what to do about my > > hosts (full CentOS 6 > > >>> > installs). Is the upgrade something the engine takes care of > > when I set the compatibility version to 3.5? Or should I install the > > ovirt-release35 rpm > > >>> > and run yum update on all hosts? > > >>> > > > >>> > Should I expect impact on running VM's, eg. from restarting > > vdsm? > > >>> > > >>> > > >>> Looks like we have a documentation gap here. > > >>> I tried to search the oVirt site for pointing you to a section > > >>> describing how to upgrade hosts but did not found one. > > >>> > > >>> I think that we need to finish > > >>> http://www.ovirt.org/DraftInstallationGuide > > >>> and probably prepare an upgrade guide too. > > >>> > > >>> You'll need to install the ovirt-release35 rpm on your hosts > > >>> since the engine is not able to add the new repository (yet? > > >>> maybe an RFE on this should > > >>> be filled for easing the upgrade process of the hosts). > > >>> > > >>> > > > >>> > On 20 October 2014 08:48, Sandro Bonazzola > > >>> <sbona...@redhat.com <mailto:sbona...@redhat.com> > > >>> <mailto:sbona...@redhat.com <mailto:sbona...@redhat.com>>> > > wrote: > > >>> > > > >>> > Il 19/10/2014 16:53, Daniel Helgenberger ha scritto: > > >>> > > Congratulations! Hope you could get your party. > > >>> > > > > >>> > > Sandro, as I know you always like to hear things like > > this: > > >>> > > I just upgraded my oVirt 3.4.4 installation to 3.5 and > > >>> everything went > > >>> > > really well (apart from some package siging / deps; > > but > > >>> these are really > > >>> > > not your issues). > > >>> > > > >>> > I really like when someone report everything goes fine > > :-) > > >>> > > > >>> > > > > >>> > > Tomorrow I start checking out the new stuff. > > >>> > > > > >>> > > Thank you! I really appreciate the work you do. > > >>> > > > > >>> > > Daniel > > >>> > > > > >>> > > On 17.10.2014 14:46, Sandro Bonazzola wrote: > > >>> > >> The oVirt Project is pleased to announce the general > > >>> availability of its sixth formal release, oVirt 3.5, as of > > >>> October 17, 2014. > > >>> > >> > > >>> > >> oVirt is an open source alternative to VMware > > vSphere, > > >>> and provides an excellent KVM management interface for > > >>> multi-node virtualization. oVirt is > > >>> > >> available now for Fedora 19, Fedora 20, Red Hat > > >>> Enterprise Linux 6.5, and CentOS 6.5 (or similar) and allow you > > >>> to use Red Hat Enterprise Linux > > >>> > 7 and > > >>> > >> CentOS 7 too as node and for running Hosted Engine. > > >>> > >> > > >>> > >> New features include: > > >>> > >> > > >>> > >> Live Merge > > >>> > >> ---------- > > >>> > >> If an image has one or more snapshots, oVirt 3.5's > > >>> merge command will combine the data of one volume into another. > > >>> Live merges can be performed > > >>> > with > > >>> > >> data is pulled from one snapshot into another > > >>> snapshot. The engine can merge multiple disks at the same time > > >>> and each merge can independently > > >>> > fail or > > >>> > >> succeed in each operation. > > >>> > >> Import Storage Domain > > >>> > >> > > >>> > >> This latest release expands oVirt's feature of > > >>> importing ISOs and exporting storage domains to expand support > > >>> for importing an existing data > > >>> > storage > > >>> > >> domain. Based on information stored in the storage > > >>> domain, oVirt can revive entities such as disks, virtual > > >>> machines, and templates in the setup of > > >>> > >> any data center to which the storage domain is > > attached. > > >>> > >> > > >>> > >> > > >>> > >> Advanced Foreman Integration > > >>> > >> ---------------------------- > > >>> > >> oVirt 3.5 adds the capability to provision and add > > >>> hypervisors to oVirt from bare metal. Foreman is a complete > > >>> lifecycle management tool for > > >>> > physical > > >>> > >> and virtual servers. Through deep integration with > > >>> configuration management, DHCP, DNS, TFTP, and PXE-based > > >>> unattended installations, Foreman > > >>> > manages > > >>> > >> every stage of the lifecycle of your physical or > > >>> virtual servers. Integrating Foreman with oVirt helps add > > >>> hypervisor hosts managed by Foreman > > >>> > to the > > >>> > >> oVirt engine. > > >>> > >> > > >>> > >> > > >>> > >> Enhanced Authentication, Authorization and Accounting > > >>> Support > > >>> > >> > > >>> ------------------------------------------------------------- > > >>> > >> A new architecture has been built for oVirt 3.5's > > >>> authentication, authorization and accounting (AAA) system. The > > >>> enhancements will provide a clear > > >>> > >> separation of authentication from authorization and > > >>> provide a developer API to develop custom extensions for > > >>> authentication and authorization. > > >>> > >> > > >>> > >> > > >>> > >> New PatternFly Interface > > >>> > >> ------------------------ > > >>> > >> oVirt 3.5 will have a new look and feel, using > > >>> PatternFly, the open interface project. The new look and feel > > >>> aims to maintain the colors and spirit > > >>> > >> associated with oVirt, while updating it with a new, > > >>> modern, sleek, and minimal look. The minimal design allows > > >>> complex screens to look cleaner and > > >>> > >> airier, and lets the user focus on the data and the > > >>> tasks by removing all extraneous visual elements. > > >>> > >> > > >>> > >> > > >>> > >> Advanced Scheduling with Optaplanner > > >>> > >> ------------------------------------ > > >>> > >> The Optaplanner is a new service that takes a > > snapshot > > >>> of a cluster (a list of hosts and VMs) and computes an > > optimized > > >>> VM-to-Host assignment > > >>> > >> solution. Optimization will is done on per Cluster > > >>> basis. The administrator can use this information as a hint to > > >>> tweak the cluster to better > > >>> > utilize > > >>> > >> resources. > > >>> > >> > > >>> > >> > > >>> > >> > > >>> > >> This release of oVirt also includes numerous bug > > >>> fixes. See the release notes [1] for a complete list of the new > > >>> features and bugs fixed. > > >>> > >> > > >>> > >> A new repository has been created and will be > > >>> automatically enabled by installing / upgrading ovirt-release35 > > >>> package. > > >>> > >> See release notes page for further instructions about > > >>> install / upgrade. > > >>> > >> > > >>> > >> A new oVirt Live iso is also available [2] and a new > > >>> oVirt Node iso will be available soon. > > >>> > >> > > >>> > >> [1] http://www.ovirt.org/OVirt_3.5_Release_Notes > > >>> > >> [2] > > >>> > > http://resources.ovirt.org/pub/ovirt-3.5/iso/ovirt-live-el6-3.5.0.iso > > >>> > >> > > >>> > > > > >>> > > > >>> > > > >>> > -- > > >>> > Sandro Bonazzola > > >>> > Better technology. Faster innovation. Powered by > > >>> community collaboration. > > >>> > See how it works at redhat.com <http://redhat.com> > > >>> <http://redhat.com> > > >>> > _______________________________________________ > > >>> > Users mailing list > > >>> > Users@ovirt.org <mailto:Users@ovirt.org> > > >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > > >>> > http://lists.ovirt.org/mailman/listinfo/users > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > -- > > >>> > Tiemen Ruiten > > >>> > Systems Engineer > > >>> > R&D Media > > >>> > > >>> > > >>> -- > > >>> Sandro Bonazzola > > >>> Better technology. Faster innovation. Powered by community > > >>> collaboration. > > >>> See how it works at redhat.com <http://redhat.com> > > >>> _______________________________________________ > > >>> Users mailing list > > >>> Users@ovirt.org <mailto: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