Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 5:32 PM, Nir Sofferwrote: > On Wed, Feb 24, 2016 at 6:28 PM, Dan Kenigsberg wrote: >> >> On Wed, Feb 24, 2016 at 03:36:36PM +0100, Fabian Deutsch wrote: >> > On Wed, Feb 24, 2016 at 3:10 PM, Yaniv Bronheim >> > wrote: >> > > I suspect that it relates to the desire to remove the dependency in >> > > vdsm-cli >> > > - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and >> > > Fabian >> > >> > Moti and I discussed this a bit off list, adn we found an issue: >> > >> > It looks like vdsm-cli provides vdsClient. >> > vdsClient is required by thevdsm sos plugin. >> > The vdsm sos plugin is part f the vdsm package. >> > >> > Thus: If vdsm is instaleld without the vdsm-cli, then the sos plugin >> > will not work. >> > vdsm should either have a dependency on the vdsm-cli pkg (which would >> > also fix the host deploy issue), or the sos plugin should be relocated >> > into a subpackage with the dependency on the vdsm-cli pkg. >> > >> > Thoughts? >> >> We would like to drop all xmlrpc dependencies, including sos. It should >> be ported to use jsonrpc. >> >> But until that happens, vdsm must explictly state that it requires >> vdsm-cli. > > > Vdsm does not need vdsm-cli. sos plugin needs vdsm-cli and should require > it. > Yep, but currently the sos plugin is part of the vdsm package. - fabian >> >> >> > >> > Independently of that Moti convinced me that the vdsClient tool is a >> > useful tool, thus we'll pull it in through our release file: >> > >> > https://gerrit.ovirt.org/53972 node: Add vdsm-cli dependency >> > >> > Moti, I wonder: Would it make sense to create a package, let's call it >> > ovirt-host - which will depened on all of the dependencies recommended >> > for a host? (like vdsm, and vdsm-cli). It would basically have the >> > dependencies which are currently installed during the host-deploy >> > process. >> ___ >> Devel mailing list >> Devel@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel > > -- Fabian Deutsch RHEV Hypervisor Red Hat ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Move host-deploy package installations into package?
Hey, IIUIC host-deploy is currently installing some packages manually: https://gerrit.ovirt.org/gitweb?p=ovirt-host-deploy.git;a=blob;f=src/plugins/ovirt-host-deploy/vdsm/packages.py;hb=HEAD Can't these dependencies moved to vdsm - or if not - can't they be moved to a ovirt-host package? Then we'd have all package related informations in one place. I find it odd that host-deploy is taking care of package installation, imo it should be sufficient to install a single package and have a host ready. host-deploy can then focus on just configuring the existing packages. Thoughts? - fabian ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 5:28 PM, Dan Kenigsbergwrote: > On Wed, Feb 24, 2016 at 03:36:36PM +0100, Fabian Deutsch wrote: >> On Wed, Feb 24, 2016 at 3:10 PM, Yaniv Bronheim wrote: >> > I suspect that it relates to the desire to remove the dependency in >> > vdsm-cli >> > - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and Fabian >> >> Moti and I discussed this a bit off list, adn we found an issue: >> >> It looks like vdsm-cli provides vdsClient. >> vdsClient is required by thevdsm sos plugin. >> The vdsm sos plugin is part f the vdsm package. >> >> Thus: If vdsm is instaleld without the vdsm-cli, then the sos plugin >> will not work. >> vdsm should either have a dependency on the vdsm-cli pkg (which would >> also fix the host deploy issue), or the sos plugin should be relocated >> into a subpackage with the dependency on the vdsm-cli pkg. >> >> Thoughts? > > We would like to drop all xmlrpc dependencies, including sos. It should > be ported to use jsonrpc. > > But until that happens, vdsm must explictly state that it requires > vdsm-cli. Cool: https://gerrit.ovirt.org/54006 spec: Add a dependency to vdsm on vdsm-cli I want to discuss the host-deploy packaging part in a different thread. - fabian >> >> Independently of that Moti convinced me that the vdsClient tool is a >> useful tool, thus we'll pull it in through our release file: >> >> https://gerrit.ovirt.org/53972 node: Add vdsm-cli dependency >> >> Moti, I wonder: Would it make sense to create a package, let's call it >> ovirt-host - which will depened on all of the dependencies recommended >> for a host? (like vdsm, and vdsm-cli). It would basically have the >> dependencies which are currently installed during the host-deploy >> process. -- Fabian Deutsch RHEV Hypervisor Red Hat ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 6:28 PM, Dan Kenigsbergwrote: > On Wed, Feb 24, 2016 at 03:36:36PM +0100, Fabian Deutsch wrote: > > On Wed, Feb 24, 2016 at 3:10 PM, Yaniv Bronheim > wrote: > > > I suspect that it relates to the desire to remove the dependency in > vdsm-cli > > > - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and > Fabian > > > > Moti and I discussed this a bit off list, adn we found an issue: > > > > It looks like vdsm-cli provides vdsClient. > > vdsClient is required by thevdsm sos plugin. > > The vdsm sos plugin is part f the vdsm package. > > > > Thus: If vdsm is instaleld without the vdsm-cli, then the sos plugin > > will not work. > > vdsm should either have a dependency on the vdsm-cli pkg (which would > > also fix the host deploy issue), or the sos plugin should be relocated > > into a subpackage with the dependency on the vdsm-cli pkg. > > > > Thoughts? > > We would like to drop all xmlrpc dependencies, including sos. It should > be ported to use jsonrpc. > > But until that happens, vdsm must explictly state that it requires > vdsm-cli. > Vdsm does not need vdsm-cli. sos plugin needs vdsm-cli and should require it. > > > > > Independently of that Moti convinced me that the vdsClient tool is a > > useful tool, thus we'll pull it in through our release file: > > > > https://gerrit.ovirt.org/53972 node: Add vdsm-cli dependency > > > > Moti, I wonder: Would it make sense to create a package, let's call it > > ovirt-host - which will depened on all of the dependencies recommended > > for a host? (like vdsm, and vdsm-cli). It would basically have the > > dependencies which are currently installed during the host-deploy > > process. > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 06:26:41PM +0200, Dan Kenigsberg wrote: > On Wed, Feb 24, 2016 at 09:09:39AM -0500, Eli Mesika wrote: > > Attached > > > > - Original Message - > > > > > From: "Dan Kenigsberg" < dan...@redhat.com > > > > To: "Eli Mesika" < emes...@redhat.com > > > > Cc: "devel" < devel@ovirt.org >, "Fabian Deutsch" < fdeut...@redhat.com > > > > Sent: Wednesday, February 24, 2016 4:01:12 PM > > > Subject: Re: [ovirt-devel] NGN - Network error when adding a new NGN node > > > > > On Wed, Feb 24, 2016 at 08:16:45AM -0500, Eli Mesika wrote: > > > > Hi Guys > > > > > > > > I am working on NGN > > > > I had installed a ovirt-node from ISO, it (by mistake) did not include > > > > the > > > > vdsm-cli package, so host-deploy failed on that > > > > Fabian asked me to install vdsm-cli manually using : > > > > > > > > yum --enablerepo=ovirt* install vdsm-cli > > > > > > > > In that time the host was installed but did not came up having > > > > networking > > > > issues (see attached logs) > > > > > > > > Fabian thinks that this is regression in VDSM, he said that same method > > > > was > > > > tested 2 weeks ago with no problems > > > > > Let's see {super,vdsm}.log, then and the exact vdsm version involved. > > I see that Engine asked Vdsm to create ovirtmgmt with no IP address, which is > generally not a good thing > > jsonrpc.Executor/4::DEBUG::2016-02-24 > 12:15:55,841::__init__::509::jsonrpc.JsonRpcServer::(_serveRequest) Calling > 'Host.setupNetworks' in bridge with {u'bondings': {}, u'networks': > {u'ovirtmgmt': {u'nic': u'em1', u'mtu': 1500, u'bootproto': u'dhcp', u'STP': > u'no', u'bridged': u'true', u'defaultRoute': True}}, u'options': > {u'connectivityCheck': u'true', u'connectivityTimeout': 120}} Oops, "dhcp" should have been good enough - understanding why it failed requires deeper reading of the logs. Sorry. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 03:36:36PM +0100, Fabian Deutsch wrote: > On Wed, Feb 24, 2016 at 3:10 PM, Yaniv Bronheimwrote: > > I suspect that it relates to the desire to remove the dependency in vdsm-cli > > - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and Fabian > > Moti and I discussed this a bit off list, adn we found an issue: > > It looks like vdsm-cli provides vdsClient. > vdsClient is required by thevdsm sos plugin. > The vdsm sos plugin is part f the vdsm package. > > Thus: If vdsm is instaleld without the vdsm-cli, then the sos plugin > will not work. > vdsm should either have a dependency on the vdsm-cli pkg (which would > also fix the host deploy issue), or the sos plugin should be relocated > into a subpackage with the dependency on the vdsm-cli pkg. > > Thoughts? We would like to drop all xmlrpc dependencies, including sos. It should be ported to use jsonrpc. But until that happens, vdsm must explictly state that it requires vdsm-cli. > > Independently of that Moti convinced me that the vdsClient tool is a > useful tool, thus we'll pull it in through our release file: > > https://gerrit.ovirt.org/53972 node: Add vdsm-cli dependency > > Moti, I wonder: Would it make sense to create a package, let's call it > ovirt-host - which will depened on all of the dependencies recommended > for a host? (like vdsm, and vdsm-cli). It would basically have the > dependencies which are currently installed during the host-deploy > process. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 09:09:39AM -0500, Eli Mesika wrote: > Attached > > - Original Message - > > > From: "Dan Kenigsberg" < dan...@redhat.com > > > To: "Eli Mesika" < emes...@redhat.com > > > Cc: "devel" < devel@ovirt.org >, "Fabian Deutsch" < fdeut...@redhat.com > > > Sent: Wednesday, February 24, 2016 4:01:12 PM > > Subject: Re: [ovirt-devel] NGN - Network error when adding a new NGN node > > > On Wed, Feb 24, 2016 at 08:16:45AM -0500, Eli Mesika wrote: > > > Hi Guys > > > > > > I am working on NGN > > > I had installed a ovirt-node from ISO, it (by mistake) did not include the > > > vdsm-cli package, so host-deploy failed on that > > > Fabian asked me to install vdsm-cli manually using : > > > > > > yum --enablerepo=ovirt* install vdsm-cli > > > > > > In that time the host was installed but did not came up having networking > > > issues (see attached logs) > > > > > > Fabian thinks that this is regression in VDSM, he said that same method > > > was > > > tested 2 weeks ago with no problems > > > Let's see {super,vdsm}.log, then and the exact vdsm version involved. I see that Engine asked Vdsm to create ovirtmgmt with no IP address, which is generally not a good thing jsonrpc.Executor/4::DEBUG::2016-02-24 12:15:55,841::__init__::509::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'Host.setupNetworks' in bridge with {u'bondings': {}, u'networks': {u'ovirtmgmt': {u'nic': u'em1', u'mtu': 1500, u'bootproto': u'dhcp', u'STP': u'no', u'bridged': u'true', u'defaultRoute': True}}, u'options': {u'connectivityCheck': u'true', u'connectivityTimeout': 120}} instead of copying it from {'em1': {'addr': '10.35.0.210', 'ipv6gateway': 'fe80::2e3f:38ff:fea6:ca48', 'ipv6addrs': ['2620:52:0:2300:1a03:73ff:fe4f:6a0b/64', 'fe80::1a03:73ff:fe4f:6a0b/64'], 'mtu': '1500', 'dhcpv4': True, 'netmask': '255.255.254.0', 'dhcpv6': True, 'ipv4addrs': ['10.35.0.210/23'], 'cfg': {'IPV6INIT': 'yes', 'NAME': 'em1', 'NETBOOT': 'yes', 'BOOTPROTO': 'dhcp', 'DEVICE': 'em1', 'TYPE': 'Ethernet', 'ONBOOT': 'yes', 'UUID': '95ef0937-7d6c-4f35-a544-2702307e8fba'}, 'hwaddr': '18:03:73:4f:6a:0b', 'speed': 1000, 'gateway': '10.35.1.254'}} Any idea why, Yevgeni? ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] oVirt Community Newsletter, January 2016
January was a great start for 2016 with the release of oVirt 3.6.2, as well as a stream of technical content and lots of interesting activities at FOSDEM 2016 in Brussels. Check out the newsletter for all the updates. **Apologies for the late publication, we were waiting for FOSDEM videos to finish processing but due to technical delays on the FOSDEM side the videos are not available yet. See below for slide links in the meantime!** - Software Releases - oVirt 3.6.3 First Release Candidate is now available for testing http://lists.ovirt.org/pipermail/announce/2016-January/000231.html oVirt 3.6.2 Final Release is now available http://lists.ovirt.org/pipermail/announce/2016-January/000230.html In the Community Roman Mohr presented about oVirt at the Czech JBoss User Group http://eventle.com/jbug-cz/6103 Slides are available for all oVirt-related sessions at FOSDEM 2016: https://fosdem.org/2016/schedule/event/virt_iaas_host_lifecycle_content_management_in_ovirt/ https://fosdem.org/2016/schedule/event/virt_iaas_reactive_processing_ovirt/ https://fosdem.org/2016/schedule/event/virt_iaas_sweep_away_the_garbage/ https://fosdem.org/2016/schedule/event/managing_ceph_through_cinder_using_ovirt/ https://fosdem.org/2016/schedule/event/virt_iaas_ovirt_hyperconverge/ https://fosdem.org/2016/schedule/event/virt_iaas_containers_and_virtualization/ Deep Dives and Technical Discussions Using oVirt API to automate VPS provisioning https://bobcares.com/blog/using-ovirt-api-to-automate-vps-provisioning/ Installing the oVirt Node Next (Early-Preview) http://dummdida.tumblr.com/post/136872577940/installing-the-ovirt-node-next-early-preview Hyperconverged Infrastructure using oVirt and Gluster http://blogs-ramesh.blogspot.cz/2016/01/ovirt-and-gluster-hyperconvergence.html oVirt as VMWare Replacement https://www.reddit.com/r/sysadmin/comments/412wwg/ovirt_as_a_vmware_replacement (Discussion) How we configured disaster recovery in an oVirt system https://bobcares.com/blog/how-we-configured-disaster-recovery-in-a-server-virtualization-system-based-on-ovirt/ Summary of oVirt 3.6.2 Release [Portuguese] http://blog.seprol.com.br/solucoes-corporativas/nova-versao-do-ovirt-3-6-2-disponivel/ Manage KVM with oVirt [Japanese] http://qiita.com/idzzy/items/338fcd27bb386867cdd8 -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady signature.asc Description: OpenPGP digital signature ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 3:46 PM, Eli Mesikawrote: > > > > > From: "Fabian Deutsch" > To: "Yaniv Bronheim" , "Eli Mesika" > > Cc: "Dan Kenigsberg" , "devel" > Sent: Wednesday, February 24, 2016 4:16:55 PM > Subject: Re: [ovirt-devel] NGN - Network error when adding a new NGN node > > On Wed, Feb 24, 2016 at 3:10 PM, Yaniv Bronheim wrote: >> I suspect that it relates to the desire to remove the dependency in >> vdsm-cli >> - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and Fabian >> created the iso without vdsm-cli so the deploy failed in the middle. after >> it failed it couldn't recover even when vdsm-cli was installed. sounds >> reasonable? > > Sounds reasonable - if host deploy can mess up networking that much. > > Eli, can you restart with a clean installation and install vdsm-cli > before trying to add the host? > > > Do you mean clean installation of NGN ? Yep. . It sounds like the networking config is now messed up. You could also try to manually fix it. - fabian ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
- Original Message - > From: "Fabian Deutsch"> To: "Yaniv Bronheim" , "Eli Mesika" > Cc: "Dan Kenigsberg" , "devel" > Sent: Wednesday, February 24, 2016 4:16:55 PM > Subject: Re: [ovirt-devel] NGN - Network error when adding a new NGN node > On Wed, Feb 24, 2016 at 3:10 PM, Yaniv Bronheim wrote: > > I suspect that it relates to the desire to remove the dependency in > > vdsm-cli > > - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and Fabian > > created the iso without vdsm-cli so the deploy failed in the middle. after > > it failed it couldn't recover even when vdsm-cli was installed. sounds > > reasonable? > Sounds reasonable - if host deploy can mess up networking that much. > Eli, can you restart with a clean installation and install vdsm-cli > before trying to add the host? Do you mean clean installation of NGN ? > (This is actually what I do in my testing: Install, add vdsm-cli, then add > host) > - fabian > > On Wed, Feb 24, 2016 at 4:01 PM, Dan Kenigsberg wrote: > >> > >> On Wed, Feb 24, 2016 at 08:16:45AM -0500, Eli Mesika wrote: > >> > Hi Guys > >> > > >> > I am working on NGN > >> > I had installed a ovirt-node from ISO, it (by mistake) did not include > >> > the vdsm-cli package, so host-deploy failed on that > >> > Fabian asked me to install vdsm-cli manually using : > >> > > >> > yum --enablerepo=ovirt* install vdsm-cli > >> > > >> > In that time the host was installed but did not came up having > >> > networking issues (see attached logs) > >> > > >> > Fabian thinks that this is regression in VDSM, he said that same method > >> > was tested 2 weeks ago with no problems > >> > >> Let's see {super,vdsm}.log, then and the exact vdsm version involved. > >> ___ > >> Devel mailing list > >> Devel@ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/devel > > > > > > > > > > -- > > Yaniv Bronhaim. > -- > Fabian Deutsch > RHEV Hypervisor > Red Hat ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 3:10 PM, Yaniv Bronheimwrote: > I suspect that it relates to the desire to remove the dependency in vdsm-cli > - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and Fabian Moti and I discussed this a bit off list, adn we found an issue: It looks like vdsm-cli provides vdsClient. vdsClient is required by thevdsm sos plugin. The vdsm sos plugin is part f the vdsm package. Thus: If vdsm is instaleld without the vdsm-cli, then the sos plugin will not work. vdsm should either have a dependency on the vdsm-cli pkg (which would also fix the host deploy issue), or the sos plugin should be relocated into a subpackage with the dependency on the vdsm-cli pkg. Thoughts? Independently of that Moti convinced me that the vdsClient tool is a useful tool, thus we'll pull it in through our release file: https://gerrit.ovirt.org/53972 node: Add vdsm-cli dependency Moti, I wonder: Would it make sense to create a package, let's call it ovirt-host - which will depened on all of the dependencies recommended for a host? (like vdsm, and vdsm-cli). It would basically have the dependencies which are currently installed during the host-deploy process. - fabian > created the iso without vdsm-cli so the deploy failed in the middle. after > it failed it couldn't recover even when vdsm-cli was installed. sounds > reasonable? > > On Wed, Feb 24, 2016 at 4:01 PM, Dan Kenigsberg wrote: >> >> On Wed, Feb 24, 2016 at 08:16:45AM -0500, Eli Mesika wrote: >> > Hi Guys >> > >> > I am working on NGN >> > I had installed a ovirt-node from ISO, it (by mistake) did not include >> > the vdsm-cli package, so host-deploy failed on that >> > Fabian asked me to install vdsm-cli manually using : >> > >> > yum --enablerepo=ovirt* install vdsm-cli >> > >> > In that time the host was installed but did not came up having >> > networking issues (see attached logs) >> > >> > Fabian thinks that this is regression in VDSM, he said that same method >> > was tested 2 weeks ago with no problems >> >> Let's see {super,vdsm}.log, then and the exact vdsm version involved. >> ___ >> Devel mailing list >> Devel@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel > > > > > -- > Yaniv Bronhaim. -- Fabian Deutsch RHEV Hypervisor Red Hat ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 3:16 PM, Fabian Deutschwrote: > On Wed, Feb 24, 2016 at 3:10 PM, Yaniv Bronheim wrote: >> I suspect that it relates to the desire to remove the dependency in vdsm-cli >> - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and Fabian >> created the iso without vdsm-cli so the deploy failed in the middle. after >> it failed it couldn't recover even when vdsm-cli was installed. sounds >> reasonable? > > Sounds reasonable - if host deploy can mess up networking that much. > > Eli, can you restart with a clean installation and install vdsm-cli > before trying to add the host? > > (This is actually what I do in my testing: Install, add vdsm-cli, then add > host) For now I've added a hack to pull in vdsm-cli until https://gerrit.ovirt.org/#/c/53831/ is merged. The squashfs img in ~1hr should have the fix. - fabian > - fabian > >> On Wed, Feb 24, 2016 at 4:01 PM, Dan Kenigsberg wrote: >>> >>> On Wed, Feb 24, 2016 at 08:16:45AM -0500, Eli Mesika wrote: >>> > Hi Guys >>> > >>> > I am working on NGN >>> > I had installed a ovirt-node from ISO, it (by mistake) did not include >>> > the vdsm-cli package, so host-deploy failed on that >>> > Fabian asked me to install vdsm-cli manually using : >>> > >>> > yum --enablerepo=ovirt* install vdsm-cli >>> > >>> > In that time the host was installed but did not came up having >>> > networking issues (see attached logs) >>> > >>> > Fabian thinks that this is regression in VDSM, he said that same method >>> > was tested 2 weeks ago with no problems >>> >>> Let's see {super,vdsm}.log, then and the exact vdsm version involved. >>> ___ >>> Devel mailing list >>> Devel@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/devel >> >> >> >> >> -- >> Yaniv Bronhaim. > > > > -- > Fabian Deutsch > RHEV Hypervisor > Red Hat -- Fabian Deutsch RHEV Hypervisor Red Hat ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 3:10 PM, Yaniv Bronheimwrote: > I suspect that it relates to the desire to remove the dependency in vdsm-cli > - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and Fabian > created the iso without vdsm-cli so the deploy failed in the middle. after > it failed it couldn't recover even when vdsm-cli was installed. sounds > reasonable? Sounds reasonable - if host deploy can mess up networking that much. Eli, can you restart with a clean installation and install vdsm-cli before trying to add the host? (This is actually what I do in my testing: Install, add vdsm-cli, then add host) - fabian > On Wed, Feb 24, 2016 at 4:01 PM, Dan Kenigsberg wrote: >> >> On Wed, Feb 24, 2016 at 08:16:45AM -0500, Eli Mesika wrote: >> > Hi Guys >> > >> > I am working on NGN >> > I had installed a ovirt-node from ISO, it (by mistake) did not include >> > the vdsm-cli package, so host-deploy failed on that >> > Fabian asked me to install vdsm-cli manually using : >> > >> > yum --enablerepo=ovirt* install vdsm-cli >> > >> > In that time the host was installed but did not came up having >> > networking issues (see attached logs) >> > >> > Fabian thinks that this is regression in VDSM, he said that same method >> > was tested 2 weeks ago with no problems >> >> Let's see {super,vdsm}.log, then and the exact vdsm version involved. >> ___ >> Devel mailing list >> Devel@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel > > > > > -- > Yaniv Bronhaim. -- Fabian Deutsch RHEV Hypervisor Red Hat ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
I suspect that it relates to the desire to remove the dependency in vdsm-cli - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and Fabian created the iso without vdsm-cli so the deploy failed in the middle. after it failed it couldn't recover even when vdsm-cli was installed. sounds reasonable? On Wed, Feb 24, 2016 at 4:01 PM, Dan Kenigsbergwrote: > On Wed, Feb 24, 2016 at 08:16:45AM -0500, Eli Mesika wrote: > > Hi Guys > > > > I am working on NGN > > I had installed a ovirt-node from ISO, it (by mistake) did not include > the vdsm-cli package, so host-deploy failed on that > > Fabian asked me to install vdsm-cli manually using : > > > > yum --enablerepo=ovirt* install vdsm-cli > > > > In that time the host was installed but did not came up having > networking issues (see attached logs) > > > > Fabian thinks that this is regression in VDSM, he said that same method > was tested 2 weeks ago with no problems > > Let's see {super,vdsm}.log, then and the exact vdsm version involved. > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- *Yaniv Bronhaim.* ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
Attached - Original Message - > From: "Dan Kenigsberg" < dan...@redhat.com > > To: "Eli Mesika" < emes...@redhat.com > > Cc: "devel" < devel@ovirt.org >, "Fabian Deutsch" < fdeut...@redhat.com > > Sent: Wednesday, February 24, 2016 4:01:12 PM > Subject: Re: [ovirt-devel] NGN - Network error when adding a new NGN node > On Wed, Feb 24, 2016 at 08:16:45AM -0500, Eli Mesika wrote: > > Hi Guys > > > > I am working on NGN > > I had installed a ovirt-node from ISO, it (by mistake) did not include the > > vdsm-cli package, so host-deploy failed on that > > Fabian asked me to install vdsm-cli manually using : > > > > yum --enablerepo=ovirt* install vdsm-cli > > > > In that time the host was installed but did not came up having networking > > issues (see attached logs) > > > > Fabian thinks that this is regression in VDSM, he said that same method was > > tested 2 weeks ago with no problems > Let's see {super,vdsm}.log, then and the exact vdsm version involved. vdsm-logs.tar.gz Description: application/compressed-tar ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [ANN] oVirt 3.6.3 Fourth Release Candidate is now available for testing
The oVirt Project is pleased to announce the availability of the Fourth Release Candidate of oVirt 3.6.3 for testing, as of February 24th, 2016 This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar) and Fedora 22. Highly experimental support for Debian 8.3 Jessie has been added too. This release candidate includes updated packages for: - ovirt-engine - vdsm - ovirt-hosted-engine-ha - ovirt-hosted-engine-setup This release of oVirt 3.6.3 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. A new oVirt Live ISO will be available soon [2]. Please note that mirrors[3] may need usually one day before being synchronized. * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/release/3.6.3/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Read more about oVirt Project community events: http://www.ovirt.org/Upcoming_events [1] http://www.ovirt.org/release/3.6.3/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 08:16:45AM -0500, Eli Mesika wrote: > Hi Guys > > I am working on NGN > I had installed a ovirt-node from ISO, it (by mistake) did not include the > vdsm-cli package, so host-deploy failed on that > Fabian asked me to install vdsm-cli manually using : > > yum --enablerepo=ovirt* install vdsm-cli > > In that time the host was installed but did not came up having networking > issues (see attached logs) > > Fabian thinks that this is regression in VDSM, he said that same method was > tested 2 weeks ago with no problems Let's see {super,vdsm}.log, then and the exact vdsm version involved. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] NGN - Network error when adding a new NGN node
On Wed, Feb 24, 2016 at 2:16 PM, Eli Mesikawrote: > Hi Guys > > I am working on NGN > I had installed a ovirt-node from ISO, it (by mistake) did not include the > vdsm-cli package, so host-deploy failed on that Yes, there is a bug for this: Bug 1309912 - Unnecessary vdsm-cli dependency pulled in by host-deploy > Fabian asked me to install vdsm-cli manually using : > > yum --enablerepo=ovirt* install vdsm-cli > > In that time the host was installed but did not came up having networking > issues (see attached logs) > > Fabian thinks that this is regression in VDSM, he said that same method was > tested 2 weeks ago with no problems Yes - In the past the networking came up nicely. It can be a regression inmaster, as the rpms we use in NGN are pulled from the master snapshot repository. - fabian ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Cockpit-oVirt plugin
Can we have some screenshot or even a short video? That would be wonderful! Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: yd...@redhat.com IRC : ydary On Wed, Feb 24, 2016 at 1:19 PM, Marek Librawrote: > The rpm is not yet ready. As soon as some WIP is done, I'll focus on that. > > - Original Message - > > From: "Fabian Deutsch" > > To: "Marek Libra" > > Cc: "devel" > > Sent: Tuesday, February 23, 2016 4:46:51 PM > > Subject: Re: [ovirt-devel] Cockpit-oVirt plugin > > > > On Tue, Feb 23, 2016 at 1:23 PM, Marek Libra wrote: > > > I'm pleased to announce initial version of new oVirt plugin for > Cockpit, > > > which is recently a proposed feature for oVirt 4.0. > > > > > > The oVirt Wiki Feature can be found at [3]. > > > > > > Sources and README file can be found on the github [1]. > > > Up-to-date issue list is at [2] (includes planed enhancements) > > > > > > Please refer the README file for install instructions, so far tested on > > > Centos 7 (minimal). > > > > > > The plugin will be distributed as an rpm in the future and is meant as > an > > > optional add-on to oVirt. > > > > > > Main focus is on > > > - troubleshooting when accessibility/functionality of webadmin is > limited > > > - easy-to-use tool for VM-centric host monitoring/administration > > > - potential integration point with oVirt on UI level > > > - easy to use, so for small setups the preferred choice with an option > to > > > "upgrade" to full oVirt later > > > > > > The plugin or its parts can be used as standalone same as embedded into > > > other UIs, like drill-down from webadmin or ManageIQ for more details > or > > > fine-tuning. > > > > > > The plugin has dependency on VDSM. > > > Please note, since there was a VDSM patch needed, recent master is > required > > > (see README in the source). > > > > > > Dependency on oVirt's engine is optional - when accessible then > additional > > > plugin functionality is available. > > > Please note, the plugin is in early development phase showing basic > > > concept. > > > > Hey Marek, > > > > this work looks pretty promising! > > > > Do you already have rpm build which we could include in our nightly > > oVirt Node Next builds? > > > > Greetnigs > > fabian > > > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] vdsm meeting summary - 23.2.16
On Wed, Feb 24, 2016 at 10:59 AM, Yaniv Bronheimwrote: > > > On Tue, Feb 23, 2016 at 10:54 PM, Nir Soffer wrote: > >> On Tue, Feb 23, 2016 at 6:30 PM, Yaniv Bronheim >> wrote: >> >>> (Nir, Adam, YanivB, Dan, Milan, Piotr, Francesco, Martin Polednik, >>> Edward) >>> >>> - Some of us started to work on refactoring for python3, basic file >>> movements and improving testings >>> >>> - We added functional tests to check-merged automation script - >>> currently, for some reason, it doesn't run tests that require root. I'm on >>> it. >>> >>> - if anyone know that their functional tests work good please add them >>> to the list >>> so they will run each merge >>> >>> - moving code from supervdsmServer to supervdsm_api - follow >>> https://gerrit.ovirt.org/53496 and move also virt, storage and sla part >>> >>> - Nir says to use the weekly contact from storage team to help with >>> verification about storage code changes- I'll try to reach them next week >>> to test direct LUN >>> >> >> Tal should know who is the qe contact >> > > can you publish it somewhere or send mail to the devels when you change > shifts? > We will send mail to list once a week about this. > I struggle with testing specific rpms with ovirt-system-tests currently - > it requires some tweaks there and I prefer to trust your verification - I > moved blkid, parted_utils, hostdev, alignmentScan - > hostdev is maintained by virt, I'm not sure about parted_utils. > how do you suggest to approve that it didn't break anything ( > https://gerrit.ovirt.org/#/c/53897/4) > Tal can help you this week (Feb 23 - March 1). > > >> >>> >>> - I also wanted to use lago basic_suite (ovirt-system-tests) to run >>> full flow from specific vdsm commit - but the infrastructure for that >>> requires many manual steps and its not easy as I expected it to be. >>> >>> - moving code from vdsm dir (/usr/share/vdsm/) to site-packages/vdsm (by >>> moving them to lib/vdsm) - this is required to avoid relative imports which >>> are not allowed in python3 - storage dir is the main gap we currently have. >>> >>> - python-modernize - Dan uses it for network tests dir and encourage us >>> to start running it for our parts >>> >> >> Where is this tool? >> > > dnf install python-modernize > Thanks Nir ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [vdsm][virt] what's new in virt (20160224)
Hi all, Here it is a new weekly summary about what's going on on virt's world (VDSM edition). The virt team is heading at full throttle towards new features, without of course neglecting bufixes. The team is focusing on new shiny features, or on large cleanups and refactoring to make new features possible, or both :) General directions: * Francesco: more work on the codename `convirt'[1] module mostly (support containers with libvirt API). the module is shaping up nicely, I'm near to run containers through it. Preliminar Vdsm patches have been posted. Changes to Engine are expected to be minimal. Expect a comprehensive overview on the (new shiny!) wiki next week. * MartinPolednik: more work onNUMA cleanup * MartinBetak: patches for (http://wiki.ovirt.org/Features/Migration_Enhancements) * Milan: posted patch set to cleanup vmdevices. * Shahar: porting v2v to the new jobs infrastructure * Vinzenz: Guest Lifecycle Events (and Hooks). - https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:guest-lifecycle-events Patch topics in need of attention * Tomas/MartinBetak Their http://wiki.ovirt.org/Features/Migration_Enhancements - related patches are been reviewed and received feedback. Initial patches were merged * Francesco: low need: https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:bz1309884 * MartinPolednik: https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:numa * Milan: low need - already partially reviewed: https://gerrit.ovirt.org/#/q/topic:vm-devices-move-prep * Shahar: it seems the patches are receiving attention * Vinzenz: it seems the patches are receiving attention Single patches in need of attention: * Francesco: - https://gerrit.ovirt.org/53958 * MartinPolednik: - N/A * Milan: - N/A * Shahar: https://gerrit.ovirt.org/#/c/52858/ - again! * Vinzenz: - N/A That's all for this week! +++ [1] We are aware of possible naming issues as pointed out last week. will evaluate new name when the module actually starts doing something useful :) -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Cockpit-oVirt plugin
The rpm is not yet ready. As soon as some WIP is done, I'll focus on that. - Original Message - > From: "Fabian Deutsch"> To: "Marek Libra" > Cc: "devel" > Sent: Tuesday, February 23, 2016 4:46:51 PM > Subject: Re: [ovirt-devel] Cockpit-oVirt plugin > > On Tue, Feb 23, 2016 at 1:23 PM, Marek Libra wrote: > > I'm pleased to announce initial version of new oVirt plugin for Cockpit, > > which is recently a proposed feature for oVirt 4.0. > > > > The oVirt Wiki Feature can be found at [3]. > > > > Sources and README file can be found on the github [1]. > > Up-to-date issue list is at [2] (includes planed enhancements) > > > > Please refer the README file for install instructions, so far tested on > > Centos 7 (minimal). > > > > The plugin will be distributed as an rpm in the future and is meant as an > > optional add-on to oVirt. > > > > Main focus is on > > - troubleshooting when accessibility/functionality of webadmin is limited > > - easy-to-use tool for VM-centric host monitoring/administration > > - potential integration point with oVirt on UI level > > - easy to use, so for small setups the preferred choice with an option to > > "upgrade" to full oVirt later > > > > The plugin or its parts can be used as standalone same as embedded into > > other UIs, like drill-down from webadmin or ManageIQ for more details or > > fine-tuning. > > > > The plugin has dependency on VDSM. > > Please note, since there was a VDSM patch needed, recent master is required > > (see README in the source). > > > > Dependency on oVirt's engine is optional - when accessible then additional > > plugin functionality is available. > > Please note, the plugin is in early development phase showing basic > > concept. > > Hey Marek, > > this work looks pretty promising! > > Do you already have rpm build which we could include in our nightly > oVirt Node Next builds? > > Greetnigs > fabian > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] vdsm meeting summary - 23.2.16
On Tue, Feb 23, 2016 at 6:30 PM, Yaniv Bronheimwrote: > (Nir, Adam, YanivB, Dan, Milan, Piotr, Francesco, Martin Polednik, Edward) > > - Some of us started to work on refactoring for python3, basic file > movements and improving testings > > - We added functional tests to check-merged automation script - > currently, for some reason, it doesn't run tests that require root. I'm on > it. > > - if anyone know that their functional tests work good please add them to > the list > so they will run each merge > > - moving code from supervdsmServer to supervdsm_api - follow > https://gerrit.ovirt.org/53496 and move also virt, storage and sla part > > - Nir says to use the weekly contact from storage team to help with > verification about storage code changes- I'll try to reach them next week > to test direct LUN > > - I also wanted to use lago basic_suite (ovirt-system-tests) to run full > flow from specific vdsm commit - but the infrastructure for that requires > many manual steps and its not easy as I expected it to be. > > - moving code from vdsm dir (/usr/share/vdsm/) to site-packages/vdsm (by > moving them to lib/vdsm) - this is required to avoid relative imports which > are not allowed in python3 - storage dir is the main gap we currently have. > > - python-modernize - Dan uses it for network tests dir and encourage us to > start running it for our parts > > - there are some schema changes, mostly removal parts that Piotr posted as > part of converting to yaml structure. this code needs to be reviewed > - Nir asks to keep the current API order instead of sorting by names > - Nir concerns about yaml notation looks for a list with single element > - split the yaml schema to several files is complex but nir asks to see if > its possible > > - storage team mainly works hard on SDM patches > > - Edward works on splitting network tests between unit tests and > integration tests which do environment setup changes > > - we currently don't run the slow test automatically > - we might want more "tags" for tests such as SlowTests, StressTests > > And the most important issue - vdsm for ovirt 4.0 will keep only 3.6 > backward compatibility - if you don't agree with that statement, please say > why ... but as far as we see it, this is the direction and we already > removing 3.5 stuff. > If a customer has 3.5 level cluster with all hosts on RHEL 7, why would we break compatibility? Need to understand the cost here. The very least is to allow live migration . Y. > Thanks all for participating, > > -- > *Yaniv Bronhaim.* > > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] vdsm meeting summary - 23.2.16
On Tue, Feb 23, 2016 at 10:54 PM, Nir Sofferwrote: > On Tue, Feb 23, 2016 at 6:30 PM, Yaniv Bronheim > wrote: > >> (Nir, Adam, YanivB, Dan, Milan, Piotr, Francesco, Martin Polednik, Edward) >> >> - Some of us started to work on refactoring for python3, basic file >> movements and improving testings >> >> - We added functional tests to check-merged automation script - >> currently, for some reason, it doesn't run tests that require root. I'm on >> it. >> >> - if anyone know that their functional tests work good please add them >> to the list >> so they will run each merge >> >> - moving code from supervdsmServer to supervdsm_api - follow >> https://gerrit.ovirt.org/53496 and move also virt, storage and sla part >> >> - Nir says to use the weekly contact from storage team to help with >> verification about storage code changes- I'll try to reach them next week >> to test direct LUN >> > > Tal should know who is the qe contact > can you publish it somewhere or send mail to the devels when you change shifts? I struggle with testing specific rpms with ovirt-system-tests currently - it requires some tweaks there and I prefer to trust your verification - I moved blkid, parted_utils, hostdev, alignmentScan - how do you suggest to approve that it didn't break anything (https://gerrit.ovirt.org/#/c/53897/4 ) > >> >> - I also wanted to use lago basic_suite (ovirt-system-tests) to run >> full flow from specific vdsm commit - but the infrastructure for that >> requires many manual steps and its not easy as I expected it to be. >> >> - moving code from vdsm dir (/usr/share/vdsm/) to site-packages/vdsm (by >> moving them to lib/vdsm) - this is required to avoid relative imports which >> are not allowed in python3 - storage dir is the main gap we currently have. >> >> - python-modernize - Dan uses it for network tests dir and encourage us >> to start running it for our parts >> > > Where is this tool? > dnf install python-modernize > >> >> - there are some schema changes, mostly removal parts that Piotr posted >> as part of converting to yaml structure. this code needs to be reviewed >> - Nir asks to keep the current API order instead of sorting by names >> - Nir concerns about yaml notation looks for a list with single element >> > > Whis is less nice than the previous notation: > > new: > > - name: pathlist > type: > - *IscsiSessionInfo > > old: > > 'pathlist': ['IscsiSessionInfo'], > > I don't see how to make this better. > > - split the yaml schema to several files is complex but nir asks to see if >> its possible >> >> - storage team mainly works hard on SDM patches >> >> - Edward works on splitting network tests between unit tests and >> integration tests which do environment setup changes >> >> - we currently don't run the slow test automatically >> - we might want more "tags" for tests such as SlowTests, StressTests >> > > We can solve this issue by marking tests as slowtest, but we better use > more > specific tags such as "integration", for tests that depend on the > environment, and > "privileged" for tests that requires root. > > >> >> And the most important issue - vdsm for ovirt 4.0 will keep only 3.6 >> backward compatibility - if you don't agree with that statement, please say >> why ... but as far as we see it, this is the direction and we already >> removing 3.5 stuff. >> > > +2 from storage side > > >> >> Thanks all for participating, >> > > Thanks for taking the notes! > > Nir > > -- *Yaniv Bronhaim.* ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel