Re: [Users] ovirt-node on Gentoo
by dfediuck@redhat.com
Adding vdsm-devel, which is where such changes should be considered.
It looks like in the future this may be a good choice, but we'll
still need to support existing implementations, as well as colleague
distro's who still do not have a proper systemd implementation.
BTW, Gentoo is using ~29-r1 which is still unstable in portage tree.
Any input from vdsm dev's on systemd scripts?
On Monday 21 November 2011 13:23:05 Dimitrije Zivkovic wrote:
> Hi,
>
> so, since I'm also migrating my system from OpenRC to systemd - pure
> systemd, no OpenRC compatibility, would it be any help to set the condition
> that ovirt-node requires systemd? I mean, the question here is ( and I
> think it is worth asking it ) is it worth the time and effort to keep
> parallel scripts and stuff?
> If using systemd means that, for now, init standards are no longer an
> issue, maybe that should be the way to go? Setup ovirt-node under systemd
> for now and solve init scripts problems later? Is systemd mature enough to
> inherit SysV or OpenRC completly? Or am I somehow wrong?
> My system is working with systemd quite nice, no obvious problems so far...
>
> PS. Maybe someone could point out what is the minimal set of services
> needed to run on ovirt-node system/computer? So just to check if systemd
> has needed scripts already...
>
> On Mon, Nov 21, 2011 at 11:58 AM, Doron Fediuck <dfediuck(a)redhat.com> wrote:
>
> > Taking Dimitrije's issue as an example, we hit the first
> > conflict; Gentoo is using OpenRC by default (and has some BSD-style
> > leftovers), while RedHat and Fedora are using their SysV-style
> > implementation, which confirms to LSB. Also, some Fedora services
> > are moving to systemd implementation. Obviously these implementations
> > are not trivial to bridge. So where Fedora's script will have
> > "Required-Start:"
> > Gentoo will use a depend() function (see vixie-cron as a sample).
> > So unless we find a magical bridge for init standards, we'll have
> > to have several init scripts, and each distro will use it's own
> > script. We can try and generalize it, to make sure distor's
> > with similar implementations use the same script.
> >
>
--
/d
“Funny,” he intoned funereally, “how just when you think life can't possibly get any worse it suddenly does.” --Douglas Adams, The Hitchhiker's Guide to the Galaxy
12 years, 7 months
AUTO: Yih-Herng Chuang is out of the office (returning 11/21/2011)
by Yih-Herng Chuang
I am out of the office until 11/21/2011.
I will respond to emails when return back to office. If there is an
emergency please contact Doug Jans for technical issues or my manager Carol
Roth.
Note: This is an automated response to your message "vdsm-devel Digest,
Vol 6, Issue 24" sent on 11/18/2011 4:23:49.
This is the only notification you will receive while this person is away.
12 years, 7 months
Re: Install VDSM on Ubuntu
by Dan Kenigsberg
On Thu, Nov 17, 2011 at 04:10:08PM +0800, Jenna Johnson wrote:
> Dan,
> Newbie but very willing to have a try.I expect the rewrite include
> following steps:
> 1.using upstart-job
> 2.configure the following stuff just as old script do
> - configure libvirtd.conf/qemu.conf
> - setup a password for libvirt
> - configure sysctl.conf
> - create some paths (if missing)
>
> Are there more details to refer or I should notice?
There are plenty of Fedoraisms lurking in the code. We assume rpms, for
one. And as Dan Berrange noted few weeks back, we play with network
ifcfg- files. But I'm sure there are plenty more. It is going to be a
jurney.
Dan.
12 years, 7 months
New version of git-request-review
by smizrahi@redhat.com
I just finished a version of my git-request-review script.
For those who are not yet using it it's meant to make sending patches to
gerrit more streamlined.
It show you a list of the patches before sending them and also warns you
if you are not rebased.
To have it working you need to have a configured remote for gerrit
already in your git config
In order for git to detect it as a new verb you have to have this in
your path
usage: git request-review <gerrit-remote> <remote-branch>
eg. git request-review gerrit master
For those of you who are using the old version will probably notice this
version forgoes special gerrit configuration and can support multiple
gerrit servers (just configure more remotes).
Fixes, features and comments are always welcome.
Happy reviewing.
12 years, 7 months
A newbie of RHEV and An question about rhev hypervisor
by 李范茂
Hi all,
In my environment, I mapped two luns to rhev hypervisor
through a single HBA. I can see the two luns in hypervisor’s command line, but
when new a Storage Domain in RHEV Manager, the hypervisor can’t discover any of
them. Where can I find the error log ? And maybe I should configure something
in the hypervisor, if so could you show me the detailed configuration steps?
I’ll be very appreciate.
Thanks a lot & Best wishes.
Gonzalez(Fanmao Li)| dlut_lfm(a)yahoo.cn
12 years, 7 months
Install VDSM on Ubuntu
by Jenna Johnson
Hey guys,
Trying to install VDSM on Ubuntu11.04,pulled vdsm code ,here are my
steps:
1../autobuild --system
2.make
3.sudo make install
4.sudo service vdsmd start
encountered error : unrecognised service
Does someone have idea about how to install and startup VDSM on Ubuntu?
Jenna,
12 years, 7 months
patch for vdsm to fix discovery and allow iser discovery
by Roi Dayan
We use an rpm version: vdsm-4.9-106.el6.x86_64
First change makes target login to try transport iSER and if fails to try transport iSCSI.
Second change is adding '-o new' to the discovery command so already discovered targets settings won't be overridden
with default settings.
Thanks,
Roi
--- iscsi.py 2011-11-01 12:35:06.707272165 +0200
+++ iscsi.py 2011-11-09 11:52:01.935067375 +0200
@@ -25,7 +25,7 @@
import storage_exception as se
import devicemapper
-SENDTARGETS_DISCOVERY = [constants.EXT_ISCSIADM, "-m", "discoverydb", "-t", "sendtargets"]
+SENDTARGETS_DISCOVERY = [constants.EXT_ISCSIADM, "-m", "discoverydb", "-t", "sendtargets", "-o", "new"]
ISCSIADM_NODE = [constants.EXT_ISCSIADM, "-m", "node"]
ISCSIADM_IFACE = [constants.EXT_ISCSIADM, "-m", "iface"]
ISCSI_DEFAULT_PORT = "3260"
@@ -376,6 +376,28 @@
return rc, out
+def setNodeTransport(portal, iqn, transport='tcp'):
+ """Configure a node transport
+transport :tcp, iser
+ """
+ if transport not in ['tcp', 'iser']:
+ transport = 'tcp'
+
+ log.info('Set transport %s to target %s on portal %s' % (transport, iqn, portal))
+
+ cmds = [
+ [constants.EXT_ISCSIADM] + '-m node -o update -n node.conn[0].iscsi.HeaderDigest -v None'.split(),
+ [constants.EXT_ISCSIADM] + ('-m node -o update -n iface.transport_name -v '+transport).split()
+ ]
+
+ cmds[0] += ['-p', portal, '-T', iqn]
+ cmds[1] += ['-p', portal, '-T', iqn]
+
+ for cmd in cmds:
+ rc = misc.execCmd(cmd)[0]
+ if rc != 0:
+ raise se.iSCSILoginError(portal)
+
def remiSCSIPortal(ip, port):
"""
Removes iSCSI portal from discovery list
@@ -467,9 +489,16 @@
raise se.SetiSCSIPasswdError(portal)
# Finally instruct the iscsi initiator to login to the target
+ # try iser first and then tcp
+ setNodeTransport(portal, iqn, 'iser')
cmd = cmdt + ["-l", "-p", portal]
rc = misc.execCmd(cmd)[0]
if rc != 0:
+ # now try iSCSI
+ setNodeTransport(portal, iqn, 'tcp')
+ cmd = cmdt + ["-l", "-p", portal]
+ rc = misc.execCmd(cmd)[0]
+ if rc != 0:
raise se.iSCSILoginError(portal)
except se.StorageException:
exc_class, exc, tb = sys.exc_info()
12 years, 7 months
left overs after removing a storage
by Itzik Brown
Hi,
Using RHEV manager I added an iSCSI storage which created PV over it and LVs.
After "destroying" it from RHEV manager the storage is not available anymore when doing discovery.
In the console of the host running vdsmd I see the PV and LVs are still there.
After manually removing the LVs and PV the discovery from RHEV manager worked again.
Should it be like this? Is it a bug? Is there a fix already?
Thanks,
Itzik
12 years, 7 months
Offering my collaboration for HA
by José Román Bilbao Castro
Hi all,
I am interested on helping in the development of a robust HA solution for
ovirt. I have in mind to build a solution based on a distributed mechanism
(like that provided by vmware where HA will still work even when the
management nodes are down). The problem is that I do not know where to
start, what to read to get familiar with the vdsm architecture and so on
Any hints?.
Best,
Jose.
12 years, 7 months
Correct the variable name from VDSM-BIN to VDSM-REG-BIN in vdsm-reg script
by Jarod.w
Hi,All
The patch is to correct the variable name from VDSM-BIN to VDSM-REG-BIN
in vdsm-reg script.
--- vdsm/vdsm_reg/vdsm-reg 2011-11-07 10:14:13.755603162 +0800
+++ vdsm/vdsm_reg/vdsm-reg.new 2011-11-07 10:15:15.925603172 +0800
@@ -22,7 +22,7 @@
start() {
echo "vdsm-reg: starting"
- pid=`pidofproc -p $PIDFILE $VDSM_BIN`
+ pid=`pidofproc -p $PIDFILE $VDSM_REG_BIN`
RETVAL=$?
if [ "$RETVAL" -eq 0 ]; then
log_failure_msg "$prog: already running"
12 years, 7 months