Current status of ManageIQ to manage oVirt 4.1.1?
Hello, is ManageIQ able to manage oVirt version 4.1.1?
From which version of ManageIQ has been included in case? I see this link abot prblems with 4.x api and such: https://github.com/ManageIQ/manageiq/issues/7573
Thanks, Gianluca
On 05/05/2017 03:47 PM, Gianluca Cecchi wrote:
Hello, is ManageIQ able to manage oVirt version 4.1.1? From which version of ManageIQ has been included in case? I see this link abot prblems with 4.x api and such: https://github.com/ManageIQ/manageiq/issues/7573
Thanks, Gianluca
Managing oVirt 4 is supported since ManageIQ 'darga' release, which is the previous release, current is 'euwe'. The issue that you mention is already closed. Like with any piece of software there may be issues. We are committed to fix them. If you find one, please let us know.
On Fri, May 5, 2017 at 4:29 PM, Juan Hernández <jhernand@redhat.com> wrote:
On 05/05/2017 03:47 PM, Gianluca Cecchi wrote:
Hello, is ManageIQ able to manage oVirt version 4.1.1? From which version of ManageIQ has been included in case? I see this link abot prblems with 4.x api and such: https://github.com/ManageIQ/manageiq/issues/7573
Thanks, Gianluca
Managing oVirt 4 is supported since ManageIQ 'darga' release, which is the previous release, current is 'euwe'.
The issue that you mention is already closed.
Like with any piece of software there may be issues. We are committed to fix them. If you find one, please let us know.
Ah, ok. Perfect. I was testing an older appliance ad I'm noticing now that is based on capablanca, so probably too old... and it didn't work Do you think there is a quick path to update it to the latest or better to directly deploy the euwe one? I have found this old link: http://mariopang.blogspot.it/2015/05/update-manageiq-image.html but I don't know if it is still ok hopefully there is also a yum/rpm path? Thanks, Gianluca
On 05/05/2017 04:40 PM, Gianluca Cecchi wrote:
On Fri, May 5, 2017 at 4:29 PM, Juan Hernández <jhernand@redhat.com <mailto:jhernand@redhat.com>> wrote:
On 05/05/2017 03:47 PM, Gianluca Cecchi wrote: > Hello, > is ManageIQ able to manage oVirt version 4.1.1? > From which version of ManageIQ has been included in case? > I see this link abot prblems with 4.x api and such: > https://github.com/ManageIQ/manageiq/issues/7573 <https://github.com/ManageIQ/manageiq/issues/7573> > > Thanks, > Gianluca >
Managing oVirt 4 is supported since ManageIQ 'darga' release, which is the previous release, current is 'euwe'.
The issue that you mention is already closed.
Like with any piece of software there may be issues. We are committed to fix them. If you find one, please let us know.
Ah, ok. Perfect. I was testing an older appliance ad I'm noticing now that is based on capablanca, so probably too old... and it didn't work Do you think there is a quick path to update it to the latest or better to directly deploy the euwe one? I have found this old link: http://mariopang.blogspot.it/2015/05/update-manageiq-image.html but I don't know if it is still ok
hopefully there is also a yum/rpm path?
Yes, capablanca is too old. The instructions that you mention should still work, but remember to make a backup before doing that in your production environment. Anyhow, I'd suggest that you install a fresh euwe, if that is an option for you. There is no support for YUM/RPM upgrades, as far as I know.
On Fri, May 5, 2017 at 4:47 PM, Juan Hernández <jhernand@redhat.com> wrote:
Yes, capablanca is too old.
The instructions that you mention should still work, but remember to make a backup before doing that in your production environment.
Anyhow, I'd suggest that you install a fresh euwe, if that is an option for you.
There is no support for YUM/RPM upgrades, as far as I know.
OK, after some attempts to upgrade in place my capablanca VM (just for learning), I abandoned it. It seems the euwe stable qemu/kvm has some problems too in general... I get this during the initialization after VM start appliance_console_cli --region 0 --internal --password smartvm /opt/rubies/ruby-2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.14.6/lib/bundler/source/git/git_proxy.rb:225:in allowed_in_path': The git source https://github.com/ManageIQ/manageiq-providers-amazon is not yet checked out. Please runbundle install` before trying to start your application (Bundler::GitError) Then I have tried the just released Fine qemu/kvm rc1 image and it works ok, so I'm using it for my tests... I was able to add oVirt engine 4.1.2 pre. But now I see almost all (VMs, datastores, ecc.) but the hosts... Furthermore in Compute --> Infrastructure --> Hosts I do find the engine but not the host... Do I have to add in any way also the hypervisors to the ManageIQ configuration? Or should it be automatic? Also, do you know when I choose to see console in ManageIQ, both the "web console" and the "WM console" options in "Access" menu, from where the connection is originated: my client where browser is running or from manageiq server and then passed in any way to client? Which protocol does the web console use? Thanks, Gianluca
On 05/09/2017 01:02 PM, Gianluca Cecchi wrote:
On Fri, May 5, 2017 at 4:47 PM, Juan Hernández <jhernand@redhat.com <mailto:jhernand@redhat.com>> wrote:
Yes, capablanca is too old.
The instructions that you mention should still work, but remember to make a backup before doing that in your production environment.
Anyhow, I'd suggest that you install a fresh euwe, if that is an option for you.
There is no support for YUM/RPM upgrades, as far as I know.
OK, after some attempts to upgrade in place my capablanca VM (just for learning), I abandoned it. It seems the euwe stable qemu/kvm has some problems too in general... I get this during the initialization after VM start
appliance_console_cli --region 0 --internal --password smartvm /opt/rubies/ruby-2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.14.6/lib/bundler/source/git/git_proxy.rb:225:in |allowed_in_path': The git source https://github.com/ManageIQ/manageiq-providers-amazon is not yet checked out. Please run|bundle install` before trying to start your application (Bundler::GitError)
Then I have tried the just released Fine qemu/kvm rc1 image and it works ok, so I'm using it for my tests... I was able to add oVirt engine 4.1.2 pre. But now I see almost all (VMs, datastores, ecc.) but the hosts... Furthermore in Compute --> Infrastructure --> Hosts I do find the engine but not the host... Do I have to add in any way also the hypervisors to the ManageIQ configuration? Or should it be automatic?
The hosts should be added automatically. Moti, I remember that you mentioned some issue with hosts. Was that resolved?
Also, do you know when I choose to see console in ManageIQ, both the "web console" and the "WM console" options in "Access" menu, from where the connection is originated: my client where browser is running or from manageiq server and then passed in any way to client? Which protocol does the web console use?
I am not sure about that. Martin, can you answer that question?
On Thu, May 11, 2017 at 9:44 AM, Juan Hernández <jhernand@redhat.com> wrote:
Do I have to add in any way also the hypervisors to the ManageIQ configuration? Or should it be automatic?
The hosts should be added automatically. Moti, I remember that you mentioned some issue with hosts. Was that resolved?
Sorry I was misreading the web output at a first sight. It is ok. I see hosts in Compute --> Infrastructure --> Hosts I see managers in Compute --> Infrastructure --> Providers
Also, do you know when I choose to see console in ManageIQ, both the "web console" and the "WM console" options in "Access" menu, from where the connection is originated: my client where browser is running or from manageiq server and then passed in any way to client? Which protocol does the web console use?
I am not sure about that. Martin, can you answer that question?
Ok, I took the time to RTFM ;-) here: http://manageiq.org/docs/reference/latest/doc-Managing_Infrastructure_and_In... It seems that for oVirt/RHEV it uses websocket proxy base console. The 2 options offered in "Fine" version of manageiq are for oVirt: Access --> VM Console for spice/vnc through websocket proxy Access -->Web Console
From the pop-up help message when mouse over it says Open a new browser window with Cockpit for this VM. This requires that Cockpit is pre-configured on the VM
I should investigate this second option.... Thanks for the moment and if there is more information it will be of help debugging. BTW: I was able to successfully configure inside ManageIQ 3 environments: - one standalone host with self hosted engine (in 4.1.2pre) - one engine that manages 3 hosts (in 4.1.1) - one ESXi vcenter with 6.0 that manages 6 hosts Nice environment. I have to understand better role segregation, limits and such... Gianluca
On 11 May 2017, at 10:50, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote: On Thu, May 11, 2017 at 9:44 AM, Juan Hernández <jhernand@redhat.com> wrote:
Do I have to add in any way also the hypervisors to the ManageIQ configuration? Or should it be automatic?
The hosts should be added automatically. Moti, I remember that you mentioned some issue with hosts. Was that resolved?
Sorry I was misreading the web output at a first sight. It is ok. I see hosts in Compute --> Infrastructure --> Hosts I see managers in Compute --> Infrastructure --> Providers
Also, do you know when I choose to see console in ManageIQ, both the "web console" and the "WM console" options in "Access" menu, from where the connection is originated: my client where browser is running or from manageiq server and then passed in any way to client? Which protocol does the web console use?
I am not sure about that. Martin, can you answer that question?
Ok, I took the time to RTFM ;-) here: http://manageiq.org/docs/reference/latest/doc-Managing_Infrastructure_and_In... It seems that for oVirt/RHEV it uses websocket proxy base console. The 2 options offered in "Fine" version of manageiq are for oVirt: Access --> VM Console for spice/vnc through websocket proxy Right. Just beware it may not work very well Access -->Web Console
From the pop-up help message when mouse over it says Open a new browser window with Cockpit for this VM. This requires that Cockpit is pre-configured on the VM
Yes, it's not what you would understand as a guest console in oVirt I should investigate this second option.... Thanks for the moment and if there is more information it will be of help debugging. BTW: I was able to successfully configure inside ManageIQ 3 environments: - one standalone host with self hosted engine (in 4.1.2pre) - one engine that manages 3 hosts (in 4.1.1) - one ESXi vcenter with 6.0 that manages 6 hosts Nice environment. I have to understand better role segregation, limits and such... Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (3)
-
Gianluca Cecchi -
Juan Hernández -
Michal Skrivanek