Re: [ovirt-users] Error in attaching export storage domain

2017-05-21 Thread Fred Rolland
Can you share the Vdsm log from the host that fails to mount ?

On Sun, May 21, 2017 at 10:00 PM, shubham dubey  wrote:

> Thanks for reply, I am not sure about how to mount the storage domain
> manually.
> But I have run the nfs-check and it gives no error.
>
> One more thing I want to add is there are another sd also on the same host
> which are connected to another dc ,so is this can be a problem in anyway?
>
>
>
>
> On Sun, May 21, 2017 at 2:42 PM, Fred Rolland  wrote:
>
>> Hi,
>>
>> Can you check if you can mount manually from the DC1 host ?
>> You can use vdsm/contrib/nfs-check.py .
>> See also [1]
>>
>> Regards,
>>
>> Fred
>>
>> [1] http://www.ovirt.org/documentation/how-to/troubleshooting/tr
>> oubleshooting-nfs-storage-issues/
>>
>>
>> On Sat, May 20, 2017 at 3:16 PM, shubham dubey 
>> wrote:
>>
>>> I have a export storage domain myexport in dc0 with one vm moved to
>>> it.Now when I am trying to
>>> detach it and attach it to another datacenter dc1, I am getting
>>> following error:
>>>
>>>
>>> 017-05-20 16:52:31,694+05 ERROR [org.ovirt.engine.core.dal.dbb
>>> roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-7-thread-25)
>>> [72a6de4f] EVENT_ID: VDS_STORAGES_CONNECTION_FAILED(188), Correlation
>>> ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to connect
>>> Host node2dc1 to the Storage Domains myexport.
>>> 2017-05-20 16:52:31,694+05 INFO  [org.ovirt.engine.core.vdsbrok
>>> er.vdsbroker.ConnectStorageServerVDSCommand]
>>> (org.ovirt.thread.pool-7-thread-25) [72a6de4f] FINISH,
>>> ConnectStorageServerVDSCommand, return: 
>>> {b7acd809-af92-4c6d-84c5-327550208bf1=477},
>>> log id: 4f995793
>>> 2017-05-20 16:52:31,699+05 ERROR [org.ovirt.engine.core.dal.dbb
>>> roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-7-thread-25)
>>> [72a6de4f] EVENT_ID: STORAGE_DOMAIN_ERROR(996), Correlation ID: null, Call
>>> Stack: null, Custom Event ID: -1, Message: The error message for connection
>>> 192.168.122.145:/mnt/exportsd returned by VDSM was: Problem while
>>> trying to mount target
>>> 2017-05-20 16:52:31,701+05 ERROR [org.ovirt.engine.core.bll.sto
>>> rage.connection.BaseFsStorageHelper] (org.ovirt.thread.pool-7-thread-25)
>>> [72a6de4f] The connection with details '192.168.122.145:/mnt/exportsd'
>>> failed because of error code '477' and error message is: problem while
>>> trying to mount target
>>> 2017-05-20 16:52:31,706+05 ERROR [org.ovirt.engine.core.bll.sto
>>> rage.connection.ConnectStorageToVdsCommand]
>>> (org.ovirt.thread.pool-7-thread-25) [72a6de4f] Transaction rolled-back
>>> for command 'org.ovirt.engine.core.bll.storage.connection.ConnectStorage
>>> ToVdsCommand'.
>>> 2017-05-20 16:52:31,707+05 ERROR [org.ovirt.engine.core.bll.sto
>>> rage.domain.AttachStorageDomainToPoolCommand]
>>> (org.ovirt.thread.pool-7-thread-27) [96ebeffb-dffa-4bdb-bea7-ffa330f8374d]
>>> Cannot connect storage connection server, aborting attach storage domain
>>> operation.
>>> 2017-05-20 16:52:31,708+05 INFO  [org.ovirt.engine.core.bll.sto
>>> rage.domain.AttachStorageDomainToPoolCommand]
>>> (org.ovirt.thread.pool-7-thread-27) [96ebeffb-dffa-4bdb-bea7-ffa330f8374d]
>>> Command [id=d5ed8604-ae17-4d61-b5a2-929b36bf0e64]: Compensating
>>> NEW_ENTITY_ID of org.ovirt.engine.core.common.b
>>> usinessentities.StoragePoolIsoMap; snapshot:
>>> StoragePoolIsoMapId:{storagePoolId='eee50640-deea-4668-8168-a9f31a8bc006',
>>> storageId='04e2444d-990e-48b1-957b-833375ba7b3d'}.
>>> 2017-05-20 16:52:31,752+05 ERROR [org.ovirt.engine.core.dal.dbb
>>> roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-7-thread-27)
>>> [96ebeffb-dffa-4bdb-bea7-ffa330f8374d] EVENT_ID:
>>> USER_ATTACH_STORAGE_DOMAIN_TO_POOL_FAILED(963), Correlation ID:
>>> 96ebeffb-dffa-4bdb-bea7-ffa330f8374d, Job ID:
>>> 7538f0a0-90b6-414f-a62d-3d6a3287349a, Call Stack: null, Custom Event
>>> ID: -1, Message: Failed to attach Storage Domain myexport to Data Center
>>> dc1. (User: admin@internal-authz)
>>>
>>> Thanks,
>>> Shubham
>>>
>>>
>>> ___
>>> 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


Re: [ovirt-users] Docker images for oVirt engine

2017-05-21 Thread Leni Kadali Mutungi
On 5/22/17, Leni Kadali Mutungi  wrote:
On 5/19/17, Juan Hernández  wrote:
> On 05/19/2017 05:20 AM, Leni Kadali Mutungi wrote:
>> Running `make build` went fine until I saw this error:
>>
>> Step 26/34 : RUN sed -i 's/multipathd.service //g'
>> /usr/lib/systemd/system/vdsmd.service
>>  ---> Running in 6a0948c94798
>> ERRO[0104] containerd: notify OOM events error=cgroup
>> path for memory not found
>> sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or
>> directory
>> The command '/bin/sh -c sed -i 's/multipathd.service //g'
>> /usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2
>> Failed to build image 'ovirt/vdsc:master'
>>
>> I tried restarting the Docker daemon and re-running `make build`,
>> since before this I got this error:
>>
>> Message from syslogd@localhost at May 19 06:07:57 ... kernel:[
>> 7498.623027] unregister_netdevice: waiting for lo to become free.
>> Usage count = 1
>>
>
> Did that restart of the docker daemon resolve the problem?
>
> As far as I can tell that 'RUN sed' instruction that failed is correct.
> I just re-checked it in my environment and it works correctly. Looks
> more like a resources issue or a bug in docker itself. The message says
> OOM, out of memory, is that machine low on memory maybe?
>
> Restart of the docker daemon does not solve the issue. Will try to see
> how the memory issue can be solved, since I have enough memory (8GB),
> so the problem is not hardware.

Seems to be a problem related to the Debian Kernel. cgroup swap
accounting is not enabled. I tried adding `cgroup_enable=memory
swapaccount=1` to the GRUB_CMDLINE_LINUX_DEFAULT option in
/etc/default/grub
after the `quiet` option. After this I ran `sudo update-grub` and
restarted my computer. The memory error has disappeared, the RUN sed
instruction error has not.

Step 26/34 : RUN sed -i 's/multipathd.service //g'
/usr/lib/systemd/system/vdsmd.service
 ---> Running in 67d580645333
sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or directory
The command '/bin/sh -c sed -i 's/multipathd.service //g'
/usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2
Failed to build image 'ovirt/vdsc:master'

Is vdsm a dependency for ovirt-containers? If so, how do I get the container to
successfully locate the service it seems to be looking for?

CCing Oved Ourfali since Juan Hernández is on vacation till May 29th.

-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-21 Thread Leni Kadali Mutungi
On 5/19/17, Juan Hernández  wrote:
> Did that restart of the docker daemon resolve the problem?
>
> As far as I can tell that 'RUN sed' instruction that failed is correct.
> I just re-checked it in my environment and it works correctly. Looks
> more like a resources issue or a bug in docker itself. The message says
> OOM, out of memory, is that machine low on memory maybe?

Restart of the docker daemon does not solve the issue. Will try to see
how the memory issue can be solved, since I have enough memory (8GB),
so the problem is not hardware.


-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Error in attaching export storage domain

2017-05-21 Thread shubham dubey
Thanks for reply, I am not sure about how to mount the storage domain
manually.
But I have run the nfs-check and it gives no error.

One more thing I want to add is there are another sd also on the same host
which are connected to another dc ,so is this can be a problem in anyway?




On Sun, May 21, 2017 at 2:42 PM, Fred Rolland  wrote:

> Hi,
>
> Can you check if you can mount manually from the DC1 host ?
> You can use vdsm/contrib/nfs-check.py .
> See also [1]
>
> Regards,
>
> Fred
>
> [1] http://www.ovirt.org/documentation/how-to/troubleshooting/
> troubleshooting-nfs-storage-issues/
>
>
> On Sat, May 20, 2017 at 3:16 PM, shubham dubey 
> wrote:
>
>> I have a export storage domain myexport in dc0 with one vm moved to
>> it.Now when I am trying to
>> detach it and attach it to another datacenter dc1, I am getting following
>> error:
>>
>>
>> 017-05-20 16:52:31,694+05 ERROR [org.ovirt.engine.core.dal.dbb
>> roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-7-thread-25)
>> [72a6de4f] EVENT_ID: VDS_STORAGES_CONNECTION_FAILED(188), Correlation
>> ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to connect
>> Host node2dc1 to the Storage Domains myexport.
>> 2017-05-20 16:52:31,694+05 INFO  [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.ConnectStorageServerVDSCommand]
>> (org.ovirt.thread.pool-7-thread-25) [72a6de4f] FINISH,
>> ConnectStorageServerVDSCommand, return: 
>> {b7acd809-af92-4c6d-84c5-327550208bf1=477},
>> log id: 4f995793
>> 2017-05-20 16:52:31,699+05 ERROR [org.ovirt.engine.core.dal.dbb
>> roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-7-thread-25)
>> [72a6de4f] EVENT_ID: STORAGE_DOMAIN_ERROR(996), Correlation ID: null, Call
>> Stack: null, Custom Event ID: -1, Message: The error message for connection
>> 192.168.122.145:/mnt/exportsd returned by VDSM was: Problem while trying
>> to mount target
>> 2017-05-20 16:52:31,701+05 ERROR [org.ovirt.engine.core.bll.sto
>> rage.connection.BaseFsStorageHelper] (org.ovirt.thread.pool-7-thread-25)
>> [72a6de4f] The connection with details '192.168.122.145:/mnt/exportsd'
>> failed because of error code '477' and error message is: problem while
>> trying to mount target
>> 2017-05-20 16:52:31,706+05 ERROR [org.ovirt.engine.core.bll.sto
>> rage.connection.ConnectStorageToVdsCommand]
>> (org.ovirt.thread.pool-7-thread-25) [72a6de4f] Transaction rolled-back
>> for command 'org.ovirt.engine.core.bll.storage.connection.ConnectStorage
>> ToVdsCommand'.
>> 2017-05-20 16:52:31,707+05 ERROR [org.ovirt.engine.core.bll.sto
>> rage.domain.AttachStorageDomainToPoolCommand]
>> (org.ovirt.thread.pool-7-thread-27) [96ebeffb-dffa-4bdb-bea7-ffa330f8374d]
>> Cannot connect storage connection server, aborting attach storage domain
>> operation.
>> 2017-05-20 16:52:31,708+05 INFO  [org.ovirt.engine.core.bll.sto
>> rage.domain.AttachStorageDomainToPoolCommand]
>> (org.ovirt.thread.pool-7-thread-27) [96ebeffb-dffa-4bdb-bea7-ffa330f8374d]
>> Command [id=d5ed8604-ae17-4d61-b5a2-929b36bf0e64]: Compensating
>> NEW_ENTITY_ID of org.ovirt.engine.core.common.b
>> usinessentities.StoragePoolIsoMap; snapshot:
>> StoragePoolIsoMapId:{storagePoolId='eee50640-deea-4668-8168-a9f31a8bc006',
>> storageId='04e2444d-990e-48b1-957b-833375ba7b3d'}.
>> 2017-05-20 16:52:31,752+05 ERROR [org.ovirt.engine.core.dal.dbb
>> roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-7-thread-27)
>> [96ebeffb-dffa-4bdb-bea7-ffa330f8374d] EVENT_ID:
>> USER_ATTACH_STORAGE_DOMAIN_TO_POOL_FAILED(963), Correlation ID:
>> 96ebeffb-dffa-4bdb-bea7-ffa330f8374d, Job ID:
>> 7538f0a0-90b6-414f-a62d-3d6a3287349a, Call Stack: null, Custom Event ID:
>> -1, Message: Failed to attach Storage Domain myexport to Data Center dc1.
>> (User: admin@internal-authz)
>>
>> Thanks,
>> Shubham
>>
>>
>> ___
>> 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


Re: [ovirt-users] 4.1 appliance install fails due to missing GPG key

2017-05-21 Thread Ryan Barry
There was a bug filed about a very similar problem when using Cockpit:
https://bugzilla.redhat.com/show_bug.cgi?id=1421249

This looks like a problem with ovirt-hosted-engine-setup not accepting your
response. Can you attachs logs from /var/log/ovirt-hosted-engine-setup ?

As a workaround, you can "yum install ovirt-engine-appliance", which will
prompt you to accept the GPG key even if you don't actually install it,
though the root cause is hard to determine without logs.

On Sat, May 20, 2017 at 3:23 PM, Michael Hall  wrote:

> Note: screenshot attached.
>
> I installed an oVirt node 4.1, then attempted to install oVirt engine on
> that using ovirt-hosted-engine-setup The installer downloads the appliance
> RPM, but installation fails due to missing GPG key. Installation fails
> whether I answer yes or no to "Use this key?" question. There is what
> appears to be an oVirt key in /etc/pki/rpm-gpg.
>
>
> Have I missed something?
>
> Thanks, Mike
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

RYAN BARRY

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR

Red Hat NA 

rba...@redhat.comM: +1-651-815-9306 IM: rbarry

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] How to use virt-sysprep

2017-05-21 Thread Joel Diaz
Done. Thanks!

On May 20, 2017 10:31 AM, "Arik Hadas"  wrote:

>
>
> On Fri, May 19, 2017 at 9:42 PM, Joel Diaz  wrote:
>
>> Arik,
>>
>> After adding the snapshot repo, and updating the engine, I now see the
>> seal option.
>>
>
> Great. Note that you probably need to update the hosts with the snapshot
> repository as well for this operation to work.
>
>
>>
>> Thanks again,
>>
>> Joel
>>
>>
>>
>> On May 19, 2017 1:07 PM, "Arik Hadas"  wrote:
>>
>>>
>>>
>>> On Fri, May 19, 2017 at 7:22 PM, Joel Diaz  wrote:
>>>
 I ran yum update on my three host and the engine VM so I believe an up
 to date on all the packages. How can I check if I am on version 4.1.2?

>>>
>>> You can find the engine's version in the 'About' dialog (at the
>>> top-right corner of the screen of the webadmin). If you don't use the
>>> 'ovirt-4.1-snapshot' repository then it makes sense that you didn't get
>>> this update yet.
>>>
>>>
 I restarted the httpd and ovirt-engine service after the updates, but
 still don't the seal option.

 Thanks,

 On May 19, 2017 11:49 AM, "Arik Hadas"  wrote:



 On Fri, May 19, 2017 at 4:10 PM, Joel Diaz 
 wrote:

> Arik,
>
> Very cool. It's exactly what I was looking for.
>
> However, I don't see that checkbox. I've attached an image of what the
> template window looks like on my end. Maybe I'm looking in the wrong 
> place?
>

 No , you're looking at the right place. This feature got in pretty late
 in the release cycle of 4.1, so it is available from 4.1.2. Maybe the
 version you are using is lower than that?


>
> Thanks for the response,
>
> On May 18, 2017 12:29 PM, "Arik Hadas"  wrote:
>
>>
>>
>> On Thu, May 18, 2017 at 10:40 AM, Luca 'remix_tj' Lorenzetto <
>> lorenzetto.l...@gmail.com> wrote:
>>
>>> Hello Joel,
>>>
>>> as far as i know, virt-sysprep has to be executed inside the VM
>>> before
>>> cloning it to template. This removes some infos from the VM like udev
>>> rules & ssh keys.
>>>
>>>
>> So this has changed in 4.1. You can now choose to seal a template
>> during its creation. This will take a VM, that may have not been sealed,
>> create a template out of it and then invoke virt-sysprep on the 
>> template's
>> disks.
>>
>> Joel, in the 'make template' dialog you'll see a checkbox (at the
>> bottom) for 'Seal Template' that will do the trick. There is also a 
>> 'seal'
>> parameter in the REST-API, of course [1].
>>
>> [1] https://github.com/oVirt/ovirt-engine-api-model/blob/mas
>> ter/src/main/java/services/TemplatesService.java#L168
>>
>>
>>>
>>> Luca
>>>
>>> On Wed, May 17, 2017 at 8:53 PM, Joel Diaz 
>>> wrote:
>>> > Good afternoon ovirt users,
>>> >
>>> > I'm new to ovirt. I've created templates in the past using this
>>> guide,
>>> > https://github.com/rharmonson/richtech/wiki/CentOS-7-1511-Mi
>>> nimal-oVirt-Template
>>> > .
>>> >
>>> > I was going over the list of features and stumbled on to
>>> virt-sysprep.
>>> >
>>> > http://www.ovirt.org/develop/release-management/features/vir
>>> t-sysprep/
>>> >
>>> >  http://libguestfs.org/virt-sysprep.1.html
>>> >
>>> > How can I use virt-sysprep from within ovirt to create templates?
>>> >
>>> > Thank you for your help,
>>> >
>>> > Joel
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Joel
>>> >
>>> >
>>> > ___
>>> > Users mailing list
>>> > Users@ovirt.org
>>> > http://lists.ovirt.org/mailman/listinfo/users
>>> >
>>>
>>>
>>>
>>> --
>>> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
>>> calcoli che potrebbero essere affidati a chiunque se si usassero
>>> delle
>>> macchine"
>>> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>>>
>>> "Internet è la più grande biblioteca del mondo.
>>> Ma il problema è che i libri sono tutti sparsi sul pavimento"
>>> John Allen Paulos, Matematico (1945-vivente)
>>>
>>> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
>>> lorenzetto.l...@gmail.com>
>>> ___
>>> 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


Re: [ovirt-users] add direct LUN disk to a VM with python SDK

2017-05-21 Thread Guy Chen

That works, thank you !

Regards,

-
Guy Chen, RHV
Performance
O: +972.9.7692152M: +972.52.8545202
guc...@redhat.com

- Original Message -
> From: "Ondra Machacek" 
> To: "Guy Chen" 
> Cc: "users" 
> Sent: Friday, May 19, 2017 9:22:30 AM
> Subject: Re: [ovirt-users] add direct LUN disk to a VM with python SDK
> 
> I've sent following example to our Python SDK,
> feel free to try and review:
> 
>  https://gerrit.ovirt.org/#/c/77003/1
> 
> Also you may checkout relevant Ansible module, which support this
> functionality as well:
> 
>  http://docs.ansible.com/ansible/ovirt_disks_module.html
> 
> 
> On Wed, May 17, 2017 at 1:21 PM, Guy Chen  wrote:
> 
> >
> > I am trying to add direct LUN disk to a VM with python ovirtsdk4 ( storage
> > domain is iscsi ) .
> > Adding a COW disk is working as in the SDK example, attached below, i have
> > tried different things that i saw online but did not work, anybody have an
> > example of how to add a direct LUN disk ?
> >
> > def add_VM_disk(self):
> >
> >
> > vms_service = self.connection.system_service().vms_service()
> > vm = vms_service.list(search='name=myvm')[0]
> >
> > # Locate the service that manages the disk attachments of the virtual
> > # machine:
> > disk_attachments_service =
> > vms_service.vm_service(vm.id).disk_attachments_service()
> >
> > # Use the "add" method of the disk attachments service to add the disk.
> > # Note that the size of the disk, the `provisioned_size` attribute, is
> > # specified in bytes, so to create a disk of 10 GiB the value should
> > # be 10 * 2^30.
> > disk_attachment = disk_attachments_service.add(
> > types.DiskAttachment(
> > disk=types.Disk(
> > name='mydisk',
> > description='My disk',
> > format=types.DiskFormat.COW,
> > provisioned_size=10 * 2 ** 30,
> > ),
> > interface=types.DiskInterface.VIRTIO,
> > bootable=False,
> > active=True,
> > ),
> > )
> >
> >
> >
> >
> >
> > ___
> > 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


Re: [ovirt-users] [Pkg-libvirt-discuss] Fwd: Building ovirt-host-deploy gives `configure: error: otopi-devtools required but missing`

2017-05-21 Thread Guido Günther
On Fri, May 19, 2017 at 06:28:36AM +0300, Leni Kadali Mutungi wrote:
> I'd like the input of the Debian Virtualization Team on the messages
> below. When replying, cc the oVirt team 
> 
> -- Forwarded message --
> From: Yedidyah Bar David 
> Date: Tue, 16 May 2017 09:51:24 +0300
> Subject: Re: [ovirt-users] Building ovirt-host-deploy gives
> `configure: error: otopi-devtools required but missing`
> To: Leni Kadali Mutungi 
> Cc: Jason Brooks , users 
> 
> On Mon, May 15, 2017 at 10:42 PM, Leni Kadali Mutungi
>  wrote:
> > On 5/15/17, Yedidyah Bar David  wrote:
> >
> >> Now is the time to explain something.
> >>
> >> ovirt-host-deploy is not designed to be ran manually like you try.
> >>
> >> You will get the exact same error if you try to do this on CentOS or
> >> Fedora.
> >>
> >> The normal way it works is that the engine "bundles" it in a tarball,
> >> copies it to the target host using ssh, untars it there and runs it.
> >>
> >> It then talks with it - the engine sends some stuff, host-deploy replies,
> >> etc.
> >>
> > I'm guessing this means I can now move on to building ovirt-engine.

When looking into packaging the Java dependencies talk to the Debian
Java packaging team:

debian-j...@lists.debian.org
> 
> That would be great, but:
> 
> 1. It will require a lot of work, mostly probably of packaging in Debian
> dependencies of the engine that are not yet there.
> 
> 2. You'll be mostly walking the unwalked path. Most of the work on Debian
> support so far was on the hosts' side.
> 
> Re (1.), you should also note that currently, the engine is not even
> packaged properly for Fedora/CentOS. I know this sounds weird, as everyone
> uses the packages we provide, but it's true - these packages are not
> compliant with Fedora's packaging guidelines. Why? Because we use maven
> for building the engine, and package also many dependencies simply as
> a result of maven getting them from maven central. See also:
> 
> https://bugzilla.redhat.com/showdependencytree.cgi?id=1168605_resolved=0
> 
> Best,
> 
> >
> >> The protocol they use is described in otopi, in the file README.dialog.
> >>
> >> otopi has (currently) two "dialects" - "human" (default) and "machine".
> >> The engine and ovirt-host-deploy talk using the machine dialog.
> >>
> >> To make ovirt-host-deploy talk with you using the machine dialog,
> >> you should run it with:
> >>
> >> ovirt-host-deploy DIALOG/dialect=str:machine
> >>
> >> To make it let you configure it, run it with:
> >>
> >> ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True
> >>
> >> To know what it expects at each stage, I suggest to have a look at an
> >> ovirt-host-deploy log generated on el7 or fedora.
> >>
> > This is very useful; will definitely try this out.
> >> Anyway, congrats for a nice progress!
> > Thanks. I wouldn't have come this far without the community's help and
> > the documentation.
> >
> >>> I tried starting the libvirtd service to see if that would make the
> >>> VIRT/enable error go away or at least satisfy the requirements of
> >>> ovirt-host-deploy, but it didn't seem to work.
> >>
> >> If you check such a log file, you'll see there (among other things):
> >>
> >> DIALOG:SEND   **%QStart: CUSTOMIZATION_COMMAND
> >> DIALOG:SEND   ###
> >> DIALOG:SEND   ### Customization phase, use 'install' to proceed
> >> DIALOG:SEND   ### COMMAND>
> >> DIALOG:SEND   **%QHidden: FALSE
> >> DIALOG:SEND   ***Q:STRING CUSTOMIZATION_COMMAND
> >> DIALOG:SEND   **%QEnd: CUSTOMIZATION_COMMAND
> >> DIALOG:RECEIVEenv-query -k VIRT/enable
> >> DIALOG:SEND   **%QStart: VIRT/enable
> >> DIALOG:SEND   ###
> >> DIALOG:SEND   ### Please specify value for 'VIRT/enable':
> >> DIALOG:SEND   ### Response is VALUE VIRT/enable=type:value or
> >> ABORT VIRT/enable
> >> DIALOG:SEND   ***Q:VALUE VIRT/enable
> >> DIALOG:SEND   **%QEnd: VIRT/enable
> >> DIALOG:RECEIVEVALUE VIRT/enable=bool:true
> >>
> >> "SEND" is what the host-deploy sends, "RECEIVE" is what the engine
> >> replies.
> >>
> >> So host-deploy sent a prompt asking for a customization command,
> >> the engine sent the command 'env-query -k VIRT/enable', host-deploy
> >> then asked the engine to provide a value for 'VIRT/enable', and the
> >> engine replied 'VIRT/enable=bool:true'.
> >>
> > Okay. Will try to look into this as well.
> >
> >>> The other errors seem
> >>> to be related to not having an IP address that ovirt-host-deploy can
> >>> recognize. To package this for Debian, I would need to find the
> >>> equivalent of yumpackager.py for aptitude/apt-get/apt, since it seems
> >>> to be a dependency required by ovirt-host-deploy.
> >>
> >> As I said, you can ignore it for now. But IMO this isn't specific
> >> to Debian - search a bit and you'll find other similar cases.
> > Alright. Good to 

Re: [ovirt-users] oVirt Power Management with Cisco UCS C220 M4S

2017-05-21 Thread Mahdi Adnan
Thank you very much, i've been searching for this for so long.


--

Respectfully
Mahdi A. Mahdi


From: users-boun...@ovirt.org  on behalf of Abi 
Askushi 
Sent: Saturday, May 20, 2017 4:14:46 PM
To: users
Subject: [ovirt-users] oVirt Power Management with Cisco UCS C220 M4S

Hi All,

For anyone that might stumble on a Cisco UCS C220 M4S and wondering how to 
configure power management. below are the steps to configure it, as it took me 
some hours to figure it out...

1. enable IPMI on server. (Cisco has this documented)

2. at ovirt GUI, edit host -> power management, then select "ipmilan" and add 
lanplus=1 as an option. (the bold one was the tricky part)

To test from command line:
 ipmitool -I lanplus -H  -U admin -P somepass -v chassis power status
It will give the response: "Chassis Power is on"

Alex
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users