Re: [ovirt-users] ovirt-guest-agent puppet module available for testing

2016-02-21 Thread Trey Dockendorf
Good to see such a module in the Forge.  I never got around to publishing
my module for oVirt which has very basic ovirt guest management.
https://github.com/treydock/puppet-ovirt/blob/1.x/manifests/guest.pp

- Trey

On Sun, Feb 21, 2016 at 5:42 AM, Eyal Edri  wrote:

> Hi Rene,
>
> Adding the oVirt infra list.
> It might be useful to use it to manage the jenkins slaves that are running
> on oVirt right now.
> Not sure if we are guest agent installed on them right now, but this can
> come in handy since we use puppet
> to maintain oVirt infra.
>
> e.
>
> On Fri, Feb 19, 2016 at 8:16 AM, René Koch  wrote:
>
>> Hi,
>>
>> As I'm trying to manage my infrastructure using puppet, I figured out
>> that there's no puppet module available for installing and configuring
>> ovirt-guest-agent (or at least I couldn't find one). So I created a module,
>> which is tested on Debian 7/8 (please see Readme for limitations) and
>> CentOS/Scientifc Linux/RHEL 6/7. Other operating systems will follow soon...
>>
>> If you're using puppet, feel free to test this module and leave me some
>> feedback:
>> https://forge.puppetlabs.com/scrat14/ovirt_guest_agent
>>
>>
>> Regards,
>> René
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
> Eyal Edri
> Associate Manager
> EMEA ENG Virtualization R
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
> ___
> 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] VDSM network persistence through re-install

2015-06-22 Thread Trey Dockendorf
Dan,

Thanks for the information. I'll follow that RFE.  Being able to
re-provision a host and not have to remember the correct network interface
mapping for 10 interfaces would be a huge help...too much can go wrong if I
have to re-setup a config that I thought was saved in the engine.

Thanks,
- Trey

On Mon, Jun 22, 2015 at 3:35 AM, Dan Kenigsberg dan...@redhat.com wrote:

 On Sat, Jun 20, 2015 at 12:28:10PM -0500, Trey Dockendorf wrote:
  I recently found that when I reinstall a VDSM host via the engine
  interface, if that host was actually re-provisioned via kickstart, the
  network settings defined in the engine are lost.  Before the re-install I
  had defined 4 bonds and attached 5 logical networks to the host.  After a
  re-install only ovirtmgmt was attached to the node.  Is it intended
  behavior that a host's network configuration in the ovirt-engine be lost
  when a host is re-provisioned ?  If I have to re-deploy a node, is there
 a
  way to make the ovirt-engine define networks for that host get applied to
  the re-deployed system?

 Yes, this is the inteded behavior, though some consider this a design
 bug. Network config is persisted on each host, and Engine do not
 automatically applies its own definitions ona re-provisioned host,
 however, we have

 1194297 [RFE] Allow to synchronize all networks on an
 out-of-sync host

 in the works, which would make life easier in such conditions.

 Dan.

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


Re: [ovirt-users] Upgrade to 3.5.3 fails on ovirt-engine-notifier service

2015-06-22 Thread Trey Dockendorf
I thought using /usr/share/ovirt-engine was wrong, but I was going off of
RedHat docs [1].  I didn't realize an alternative location existed.

Having just searched some more I found the oVirt docs [2] which I don't
recall existing or mentioning the conf.d at the time I setup the notifier
service.

Thanks,
- Trey

[1]:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html/Administration_Guide/Parameters_for_event_notifications_in_notifier.conf1.html
[2]: http://www.ovirt.org/Features/configuration-event-subscribers

On Mon, Jun 22, 2015 at 2:38 PM, Martin Perina mper...@redhat.com wrote:

 Hi,

 please never change anything in /usr/share/ovirt-engine, because these file
 will always be overwritten on RPM upgrades.

 To change MAIL_SERVER for ovirt-engine-notifier please create config file
 (for example 99-user.conf) under /etc/ovirt-engine/notifier/notifier.conf.d
 and put you customizations here, for example:

   MAIL_SERVER=my-mail-server.com

 This way your changes survive upgrades.

 Let me know if you have any other issues with it.

 Thanks

 Martin Perina

 - Original Message -
  From: Trey Dockendorf treyd...@gmail.com
  To: users users@ovirt.org
  Sent: Monday, June 22, 2015 7:09:57 PM
  Subject: [ovirt-users] Upgrade to 3.5.3 fails on ovirt-engine-notifier
   service
 
  I just upgraded from 3.5.1 to 3.5.3 and found the end of engine-setup
 failed
  because of the ovirt-engine-notifier service. The logs indicate that the
  MAIL_SERVER option was not set. I had set this before via Puppet and
 know it
  was working because right before I started the upgrade I was receiving
 event
  notifications. It appears as though the RPM (or some other mechanism) set
  the config file at
 
 /usr/share/ovirt-engine/services/ovirt-engine-notifier/ovirt-engine-notifier.conf
  back to its original state with my changes removed.
 
  Attached is the log from engine-setup.
 
  Is this a bug? I was able to work around this by manually setting
 MAIL_SERVER
  back to the value I had already set previously and then re-running
  engine-setup. Even after re-running engine-setup I noticed I had to
 manually
  start ovirt-engine-notifier service.
 
  Thanks,
  - Trey
 
  ___
  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


[ovirt-users] VDSM network persistence through re-install

2015-06-20 Thread Trey Dockendorf
I recently found that when I reinstall a VDSM host via the engine
interface, if that host was actually re-provisioned via kickstart, the
network settings defined in the engine are lost.  Before the re-install I
had defined 4 bonds and attached 5 logical networks to the host.  After a
re-install only ovirtmgmt was attached to the node.  Is it intended
behavior that a host's network configuration in the ovirt-engine be lost
when a host is re-provisioned ?  If I have to re-deploy a node, is there a
way to make the ovirt-engine define networks for that host get applied to
the re-deployed system?

Thanks,
- Trey
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Automation and engine-setup

2015-02-25 Thread Trey Dockendorf
I am attempting to update my Puppet module [1] that manages oVirt and have
found my method for executing engine-setup works on a fresh install but
fails if run after install, for example to enable reports.

Normally I run this:

yes 'Yes' | engine-setup
--config-append=/var/lib/ovirt-engine/setup/answers/ovirt-engine-setup.conf

However if I've already installed ovirt-engine and then install the
packages for reports and re-run the above command it gets stuck at this
step:

[ INFO  ] Stage: Setup validation
  During execution engine service will be stopped (OK, Cancel)
[OK]:

Since Yes is not a valid response my method does not work.  Is there a
flag I can provide in the answers file that would prevent the above
prompt?  I am semi familiar with using expect but was hoping to avoid using
expect from within a Puppet module.

Thanks,
- Trey

[1]: https://github.com/treydock/puppet-ovirt/tree/1.x
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] qemu-kvm from Jenkins - renamed packages to rhev?

2014-10-30 Thread Trey Dockendorf
Ah, thanks for the info.  I've yet to update to 3.5 but good to know that
the packages are now in ovirt repo for when I do upgrade I don't need to
maintain a copy of qemu-kvm locally.

Thanks,
- Trey

On Thu, Oct 30, 2014 at 5:42 PM, Itamar Heim ih...@redhat.com wrote:

 On 10/30/2014 09:05 PM, Trey Dockendorf wrote:

 In the past in order to have live snapshots work in CentOS 6.5 I had to
 use RPMs from
 http://jenkins.ovirt.org/job/qemu-kvm-rhev_create-rpms_el6/.  I've
 noticed now that the RPMs have been renamed and no longer match the
 names of those distributed by CentOS.  Are the CentOS builds of QEMU now
 supporting live snapshots, or are these builds in Jenkins still required?

 Thanks,
 - Trey


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


 native centos - no
 the jenkins job isn't needed as well as the build is now in the repo (and
 3.5 now requires qemu-kvm-rhev to avoid such problems)
 http://resources.ovirt.org/pub/ovirt-3.5/rpm/el6Server/x86_64/

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


Re: [ovirt-users] Are there some general strategyhow to Iscsi strorage domain?

2014-10-23 Thread Trey Dockendorf
Not sure if it's a solution for you, but ZFS.  My domains are all ZFS
(using ZFS on Linux in EL6.5) and my backup server receives incremental
snapshots from primary storage which includes both NFS exports and iSCSI.
ZFS makes creating block devices for iSCSI very easy, and they are included
in snapshot replication.  The replication is not HA but disaster recovery
and off site.

I've hit 300MB/s using ZFS send over IPoIB on my DDR fabric, which isn't
amazing but not terrible for an old DDR fabric.

ZFS is probably not an easy solution as requires rebuilding your storage,
but maybe for future use or other readers it will give some useful ideas.

- Trey
On Oct 22, 2014 11:56 AM, Arman Khalatyan arm2...@gmail.com wrote:

 Hi,
 I have 2x40TB domains each are exported with iser/iscsi with ib and 10Gb
 interfaces.
 For sure they are RAID6 storage little bit save on failure.
 But I was wondered if any way to backup those domains. particularly master
 one.

 I was thinking somehow DRBD based replication, with lvm snapshots etc. But
 it looks like overkill.
 Will be nice somehow to deploy replicated/HA Master domain with ability to
 backp on tapes as well.

 Any ideas are welcome.
 Thanks,
 Arman.

 ___
 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] Fwd: Are there some general strategyhow to Iscsi strorage domain?

2014-10-23 Thread Trey Dockendorf
Also, if performance is the key, and you don't need the maximum space, try
using 8x mirrors.  If your ZVOL is doing MySQL or any database , set
primary and secondary cache properties to metadata only.  The caching in
ZFS can sometimes hurt when the application does its own caching.

Having a ZIL/slog device is good, in my situation I have neither ZIL or
l2_arc because my zpool is pure SSD.

Maximizing the amount of striped raid sets helps a lot with ZFS, as Karli
mentioned, you'll see better performance with 2x8 than 1x16.

I too have seen RAID cards out perform a plain HBA + ZFS, in some
situations.  This is usually due to the cards doing their own internal
caching and other dangerous (my opinion) types of behavior.  Doing ZFS on
those cards is semi-dangerous.  A few months ago I threw away 8 Areca cards
after we lost a 30TB RAID set due to errors in the Areca.  I have yet to
lose a single bit on ZFS.  I have chosen to trade some performance for
stability and data integrity.  To me it was worth it.

For what it's worth, I use ZFS on Linux as the backing file system for our
HPC cluster's parallel filesystem storage nodes, and after upgrading from
0.6.2 to 0.6.3 I saw a double in overall throughput to all storage
systems.  I've also had to tweak things like prefetching and cache tunables
in ZFS to get better performance.

Right now my oVirt instance that's backed by ZFS has done well for MySQL
with the iSCSI backed data domain.  I believe the numbers were ~250
transactions per second on a small-ish (2 core, 8GB RAM) virtual machine
using sysbench 0.5 on MariaDB.  I was formatting the iSCSI backed VM disks
as ext4 mounted with nobarrier.  Can post specifics about my zvol and
zpool setup if it'll help, just don't want to flood oVirt list with too
much ZFS stuff :)

- Trey

On Thu, Oct 23, 2014 at 4:34 AM, Karli Sjöberg karli.sjob...@slu.se wrote:

 On Thu, 2014-10-23 at 11:09 +0200, Arman Khalatyan wrote:
  yes + 1xssd cache
 
 
  NAMESTATE READ
  WRITE CKSUM
  tankONLINE   0
  0 0
raidz2-0  ONLINE   0
  0 0
  scsi-35000cca22be96bed  ONLINE   0
  0 0
  scsi-35000cca22bc5a20e  ONLINE   0
  0 0
  scsi-35000cca22bc515ee  ONLINE   0
  0 0
  ata-Hitachi_HUS724030ALE640_PK2A31PAG9VJXW  ONLINE   0
  0 0
  scsi-35000cca22bc1f9cf  ONLINE   0
  0 0
  scsi-35000cca22be68899  ONLINE   0
  0 0
  scsi-35000cca22bc58e1b  ONLINE   0
  0 0
  scsi-35000cca22bc4dc6b  ONLINE   0
  0 0
  scsi-35000cca22bc394ee  ONLINE   0
  0 0
  scsi-35000cca22bc10d97  ONLINE   0
  0 0
  scsi-35000cca22bc605d1  ONLINE   0
  0 0
  scsi-35000cca22bc412bf  ONLINE   0
  0 0
  scsi-35000cca22bc3f9ad  ONLINE   0
  0 0
  scsi-35000cca22bc53004  ONLINE   0
  0 0
  scsi-35000cca22bc5b8e2  ONLINE   0
  0 0
  scsi-35000cca22bc3beb3  ONLINE   0
  0 0
  cache
sdc   ONLINE   0
  0 0

 OK, two things:

 1) Redo the pool layout into 2x8 disk radiz2
 2) Add two really fast SSD's as mirrored log devices, like a pair of
 200GB Intel DC S3700 e.g.

 Do this and it may provide even better performance than the HW RAID.

 But that depends on the specs of the rest of the HW; CPU and RAM mostly,
 can never have enough RAM with ZFS;)

 /K

 
 
 
  On Thu, Oct 23, 2014 at 10:57 AM, Karli Sjöberg karli.sjob...@slu.se
  wrote:
  On Thu, 2014-10-23 at 10:11 +0200, Arman Khalatyan wrote:
  
   -- Forwarded message --
   From: Arman Khalatyan arm2...@gmail.com
   Date: Thu, Oct 23, 2014 at 10:11 AM
   Subject: Re: [ovirt-users] Are there some general
  strategyhow to Iscsi
   strorage domain?
   To: Trey Dockendorf treyd...@gmail.com
  
  
   Thank you Trey for sharing your setup.
  
   I have also one test system with zvol exported with iscsi
  over 10G.
   Unfortunately the difference in performance of zfs over raid
   controller is huge, particularly where VM running mysql. I
  did not try
   HBAs yet, I have only LSI/Adaptec/Areca RaidControllers they
  dont have
   IT mode. Maybe that can be the reason.
  
   For sure always one

Re: [ovirt-users] Proper way to change iSCSI and NFS IP

2014-10-22 Thread Trey Dockendorf
Thanks, will give it a try and report if I run into any problems.

- Trey

On Tue, Oct 21, 2014 at 9:19 PM, Amador Pahim apa...@redhat.com wrote:

  On 10/21/2014 07:37 PM, Trey Dockendorf wrote:

 What is the proper way to change iSCSI and NFS IP used to access the
 storage domains?


 Using the API: http://www.ovirt.org/Features/Manage_Storage_Connections

 i.e. using ovirt-cli:

 - Put SD in maintenance mode, then:

 [root@ovirt-engine ~]# ovirt-shell -c -l
 https://ovirt-engine.example.com/api;
 https://ovirt-engine.example.com/api -u admin@internal -I
 [...]

 [oVirt shell (connected)]# list storageconnections
 [...]

 [oVirt shell (connected)]# show storageconnection
 3aff9de7-426f-4ebf-99f7-088b52d08da1
 [...]

 [oVirt shell (connected)]# update storageconnection
 3aff9de7-426f-4ebf-99f7-088b52d08da1 --address NEW_IP
 [...]

 Activate SD.



  My IB fabric which was doing storage crashed and we have a scheduled
 maintenance window for next week at which time I'd like to either move my
 storage to 10GbE or back to IB.  I was able to move things off IB to
 standard TCP/IP by editing the database but that is likely not the correct
 way.  I am on ovirt 3.4.3.  My NFS domain is the master and iSCSI data
 domain is only used by two VMs while NFS is used by ~30 VMs.

  Thanks,
 - Trey


 ___
 Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users



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


[ovirt-users] VMs cannot be started, stuck in migration

2014-10-21 Thread Trey Dockendorf
I recently had my IB switch go down which brought down all storage
connections.  As a result all VMs were either paused or entered an unknown
state.  After many hours they are all finally in the off state according
to the web GUI.

When I try and start some VMs I get the following message:

Cannot run VM.  VM ns01 is being migrated.

There are 0 tasks in the web GUI and the state in web GUI is off for that
VM.

The engine.log just shows this line:

2014-10-21 11:32:17,274 INFO  [org.ovirt.engine.core.bll.RunVmCommand]
(ajp--127.0.0.1-8702-4) [3f235291] Failed to Acquire Lock to object
EngineLock [exclusiveLocks= key: 552aa31c-249e-46fe-9bcb-efd135aff4a6
value: VM
, sharedLocks= ]
2014-10-21 11:32:17,276 WARN  [org.ovirt.engine.core.bll.RunVmCommand]
(ajp--127.0.0.1-8702-4) [3f235291] CanDoAction of action RunVm failed.
Reasons:VAR__ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED,$VmName
ns01

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


[ovirt-users] Changing iSCSI LUN host IP and changing master domain

2014-10-21 Thread Trey Dockendorf
I had a catastrophic failure of the IB switch that was used by all my
storage domains.  I had one data domain that was NFS and one that was
iSCSI. I managed to get the iSCSI LUN detached using the docs [1] but now I
noticed that somehow my master domain went from the NFS domain to the iSCSI
domain and I'm unable to switch them back.

How does one change the master?  Right now I am having issues getting iSCSI
over TCP to work, so am sort of stuck with 30 VMs down and an entire
cluster inaccessible.

Thanks,
- Trey

[1] http://www.ovirt.org/Features/Manage_Storage_Connections
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] VMs cannot be started, stuck in migration

2014-10-21 Thread Trey Dockendorf
Thanks for the response.  Restarting engine was something I found when
searching too, but now I'm in much worse shape as I can't get my storage
domains back online.

There's another thread for that.

- Trey

On Tue, Oct 21, 2014 at 12:59 PM, Sven Kieske svenkie...@gmail.com wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 21.10.2014 18:39, Trey Dockendorf wrote:
  I recently had my IB switch go down which brought down all storage
  connections.  As a result all VMs were either paused or entered an
  unknown state.  After many hours they are all finally in the off
  state according to the web GUI.

  Suggestions?

 the fastest, but dirtiest way would be
 to restart the engine, as some vms might be hung in some
 stale state, you could also try to check the status in the db.

 there where some postings on the mailing list on how to do so.

 but afaik restarting engine might clear those stale vms.

 hth

 sven

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2

 iQGcBAEBAgAGBQJURp8AAAoJEAq0kGAWDrqluaoL+QEWdb+ypmEMVNNW1nZVZUxz
 4apynzZgpQwv0cHgWc7ajhy79wUZoz1OCDWONyebUOM3Db0aY97dF+POaZbERJ7s
 8Q53WG0fiZMF9XX4qkFtgBb1/aJuRjm3uMM5e7cRO/iiaIu90mCTX+OPy+pCgvfM
 r8LA7J4li2vap5lj2G01yAT8DzufcTVqzcf+RB4hsKmg8xnyHCh832L/Vh8Z+IHS
 18Sviu8VvVqdmwLcwa04dTBuslmcK970nHt0H1OFFW25OW7eT5RacALU+hRQUui0
 i7pzZvgNpbnEZwStnggdp4zW5EvIW5FJcEBbxvcqtt081g+c19sxgO1qUllXr8+b
 qbxjdlRIlMsLbZJUylpEkPRpInpV75I0XmwtV7oYo7315QG9pOS2Z7qIfcQjD6f5
 MK38V4zfhjUIG0k5nhPjs+bxbjGzCcYAPMqd9VkwZ8X7fa9ZL6vqCpZdBb4StNDB
 xAjd87NjM7yam6AT1eYUoO4sSmEAXrWEn29G7f5yJQ==
 =TdQI
 -END PGP SIGNATURE-
 ___
 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] Changing iSCSI LUN host IP and changing master domain

2014-10-21 Thread Trey Dockendorf
I was able to get iSCSI over TCP working...but now the task of adding the
LUN to the GUI has been stuck at the spinning icon for about 20 minutes.

I see these entries in vdsm.log over and over with the Task value changing:

Thread-14::DEBUG::2014-10-21
14:16:50,086::task::595::TaskManager.Task::(_updateState)
Task=`ebcd8e0a-54b1-43d2-92a2-ed9fd62d00fa`::moving from state init -
state preparing
Thread-14::INFO::2014-10-21
14:16:50,086::logUtils::44::dispatcher::(wrapper) Run and protect:
repoStats(options=None)
Thread-14::INFO::2014-10-21
14:16:50,086::logUtils::47::dispatcher::(wrapper) Run and protect:
repoStats, Return response: {}
Thread-14::DEBUG::2014-10-21
14:16:50,087::task::1185::TaskManager.Task::(prepare)
Task=`ebcd8e0a-54b1-43d2-92a2-ed9fd62d00fa`::finished: {}
Thread-14::DEBUG::2014-10-21
14:16:50,087::task::595::TaskManager.Task::(_updateState)
Task=`ebcd8e0a-54b1-43d2-92a2-ed9fd62d00fa`::moving from state preparing -
state finished
Thread-14::DEBUG::2014-10-21
14:16:50,087::resourceManager::940::ResourceManager.Owner::(releaseAll)
Owner.releaseAll requests {} resources {}
Thread-14::DEBUG::2014-10-21
14:16:50,087::resourceManager::977::ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {}
Thread-14::DEBUG::2014-10-21
14:16:50,087::task::990::TaskManager.Task::(_decref)
Task=`ebcd8e0a-54b1-43d2-92a2-ed9fd62d00fa`::ref 0 aborting False

What is there I can do to get my storage back online?  Right now my iSCSI
is master (something I did not want) which is odd considering the NFS data
domain was added as master when I setup oVirt.  Nothing will come back
until I get the master domain online and unsure what to do now.

Thanks,
- Trey

On Tue, Oct 21, 2014 at 12:58 PM, Trey Dockendorf treyd...@gmail.com
wrote:

 I had a catastrophic failure of the IB switch that was used by all my
 storage domains.  I had one data domain that was NFS and one that was
 iSCSI. I managed to get the iSCSI LUN detached using the docs [1] but now I
 noticed that somehow my master domain went from the NFS domain to the iSCSI
 domain and I'm unable to switch them back.

 How does one change the master?  Right now I am having issues getting
 iSCSI over TCP to work, so am sort of stuck with 30 VMs down and an entire
 cluster inaccessible.

 Thanks,
 - Trey

 [1] http://www.ovirt.org/Features/Manage_Storage_Connections

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


Re: [ovirt-users] Changing iSCSI LUN host IP and changing master domain

2014-10-21 Thread Trey Dockendorf
::(_updateState)
Task=`8674b6b0-5e4c-4f0c-8b6b-c5fa5fef6126`::moving from state preparing -
state finished
Thread-13::DEBUG::2014-10-21
15:13:18,282::resourceManager::940::ResourceManager.Owner::(releaseAll)
Owner.releaseAll requests {} resources {}
Thread-13::DEBUG::2014-10-21
15:13:18,282::resourceManager::977::ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {}
Thread-13::DEBUG::2014-10-21
15:13:18,283::task::990::TaskManager.Task::(_decref)
Task=`8674b6b0-5e4c-4f0c-8b6b-c5fa5fef6126`::ref 0 aborting False

The lines prefixed with Thread-13 just repeat over and over only changing
the Task value.

Unsure what could be done to restore things.  The iscsi connection is good
and I'm able to see the logical volumes:

# lvscan
  ACTIVE'/dev/4eeb8415-c912-44bf-b482-2673849705c9/metadata'
[512.00 MiB] inherit
  ACTIVE'/dev/4eeb8415-c912-44bf-b482-2673849705c9/leases'
[2.00 GiB] inherit
  ACTIVE'/dev/4eeb8415-c912-44bf-b482-2673849705c9/ids' [128.00
MiB] inherit
  ACTIVE'/dev/4eeb8415-c912-44bf-b482-2673849705c9/inbox'
[128.00 MiB] inherit
  ACTIVE'/dev/4eeb8415-c912-44bf-b482-2673849705c9/outbox'
[128.00 MiB] inherit
  ACTIVE'/dev/4eeb8415-c912-44bf-b482-2673849705c9/master'
[1.00 GiB] inherit
  inactive
 
'/dev/4eeb8415-c912-44bf-b482-2673849705c9/aced9726-5a28-4d52-96f5-89553ba770af'
[100.00 GiB] inherit
  inactive
 
'/dev/4eeb8415-c912-44bf-b482-2673849705c9/87bf28aa-be25-4a93-9b23-f70bfd8accc0'
[1.00 GiB] inherit
  inactive
 
'/dev/4eeb8415-c912-44bf-b482-2673849705c9/27256587-bf87-4519-89e7-260e13697de3'
[20.00 GiB] inherit
  inactive
 
'/dev/4eeb8415-c912-44bf-b482-2673849705c9/ac2cb7f9-1df9-43dc-9fda-8a9958ef970f'
[20.00 GiB] inherit
  inactive
 
'/dev/4eeb8415-c912-44bf-b482-2673849705c9/d8c41f05-006a-492b-8e5f-101c4e113b28'
[100.00 GiB] inherit
  inactive
 
'/dev/4eeb8415-c912-44bf-b482-2673849705c9/83f17e9b-183e-4bad-ada5-bcef1c5c8e6a'
[20.00 GiB] inherit
  inactive
 
'/dev/4eeb8415-c912-44bf-b482-2673849705c9/cf79052e-b4ef-4bda-96dc-c53b7c2acfb5'
[20.00 GiB] inherit
  ACTIVE'/dev/vg_ovirtnode02/lv_swap' [46.59 GiB] inherit
  ACTIVE'/dev/vg_ovirtnode02/lv_root' [418.53 GiB] inherit

Thanks,
- Trey



On Tue, Oct 21, 2014 at 2:49 PM, Sandra Taylor jtt77...@gmail.com wrote:

 Hi Trey,
 Sorry for your trouble.
 Don't know if I can help but I run iscsi here as my primary domain so
 I've had some experience with it.
 I don't know the answer to the master domain question.

 Does iscsi show connected  using iscsiadm -m session and   -m node  ?
 in the vdsm log there should be the iscsiadm commands that were
 executed to connect.
 Does multipath -ll show anything?

 -John

 On Tue, Oct 21, 2014 at 3:18 PM, Trey Dockendorf treyd...@gmail.com
 wrote:
  I was able to get iSCSI over TCP working...but now the task of adding the
  LUN to the GUI has been stuck at the spinning icon for about 20
 minutes.
 
  I see these entries in vdsm.log over and over with the Task value
 changing:
 
  Thread-14::DEBUG::2014-10-21
  14:16:50,086::task::595::TaskManager.Task::(_updateState)
  Task=`ebcd8e0a-54b1-43d2-92a2-ed9fd62d00fa`::moving from state init -
 state
  preparing
  Thread-14::INFO::2014-10-21
  14:16:50,086::logUtils::44::dispatcher::(wrapper) Run and protect:
  repoStats(options=None)
  Thread-14::INFO::2014-10-21
  14:16:50,086::logUtils::47::dispatcher::(wrapper) Run and protect:
  repoStats, Return response: {}
  Thread-14::DEBUG::2014-10-21
  14:16:50,087::task::1185::TaskManager.Task::(prepare)
  Task=`ebcd8e0a-54b1-43d2-92a2-ed9fd62d00fa`::finished: {}
  Thread-14::DEBUG::2014-10-21
  14:16:50,087::task::595::TaskManager.Task::(_updateState)
  Task=`ebcd8e0a-54b1-43d2-92a2-ed9fd62d00fa`::moving from state preparing
 -
  state finished
  Thread-14::DEBUG::2014-10-21
  14:16:50,087::resourceManager::940::ResourceManager.Owner::(releaseAll)
  Owner.releaseAll requests {} resources {}
  Thread-14::DEBUG::2014-10-21
  14:16:50,087::resourceManager::977::ResourceManager.Owner::(cancelAll)
  Owner.cancelAll requests {}
  Thread-14::DEBUG::2014-10-21
  14:16:50,087::task::990::TaskManager.Task::(_decref)
  Task=`ebcd8e0a-54b1-43d2-92a2-ed9fd62d00fa`::ref 0 aborting False
 
  What is there I can do to get my storage back online?  Right now my
 iSCSI is
  master (something I did not want) which is odd considering the NFS data
  domain was added as master when I setup oVirt.  Nothing will come back
 until
  I get the master domain online and unsure what to do now.
 
  Thanks,
  - Trey
 
  On Tue, Oct 21, 2014 at 12:58 PM, Trey Dockendorf treyd...@gmail.com
  wrote:
 
  I had a catastrophic failure of the IB switch that was used by all my
  storage domains.  I had one data domain that was NFS and one that was
 iSCSI.
  I managed to get the iSCSI LUN detached using the docs [1] but now I
 noticed
  that somehow my master domain went from the NFS domain to the iSCSI
 domain
  and I'm unable to switch them back.
 
  How

[ovirt-users] Recovering iSCSI domain (Was: Changing iSCSI LUN host IP and changing master domain)

2014-10-21 Thread Trey Dockendorf
Somehow my NFS domain got to be master again.  I went into the database and
updated the connections for NFS and I noticed that once I updated the IP
for the ISCSI in the storage_server_connections table that the interface
kept moving (master) between the iSCSI and NFS domain...very odd.

I did these commands and now NFS is up.

update storage_server_connections set connection='10.0.0.10:/tank/ovirt/data'
where id='a89fa66b-8737-4bb8-a089-d9067f61b58a';
update storage_server_connections set
connection='10.0.0.10:/tank/ovirt/import_export'
where id='521a8477-9e88-4f2d-96e2-d3667ec407df';
update storage_server_connections set
connection='192.168.202.245:/tank/ovirt/iso'
where id='fb55cfea-c7ef-49f2-b77f-16ddd2de0f7a';
update storage_server_connections set connection='10.0.0.10' where
id='d6da7fbf-5056-44a7-9fc8-e76a1ff9f525';

Once I activated the NFS master domain all my other domains went to active,
including iSCSI.

My concern now is whether the iSCSI domain is usable.  The API path at
/api/storagedomains/4eeb8415-c912-44bf-b482-2673849705c9/storageconnections
shows

storage_connections/

If I go to edit the iSCSI domain and check the LUN the warning I get is
this:

This operation might be unrecoverable and destructive!
The following LUNs are already in use:
- 1IET_00010001 (Used by VG: 3nxXNr-bIHu-9YS5-Kfzc-A2Na-sMhb-jihwdt)

That alone makes me very hesitant to approve the operation.  I could use
some wisdom if this is safe or not.

Thanks,
- Trey

On Tue, Oct 21, 2014 at 3:17 PM, Trey Dockendorf treyd...@gmail.com wrote:

 John,

 Thanks for reply.  The Discover function in GUI works...it's once I try
 and login (Click the array next to target) that things just hang
 indefinitely.

 # iscsiadm -m session
 tcp: [2] 10.0.0.10:3260,1
 iqn.2014-04.edu.tamu.brazos.vmstore1:ovirt-data_iscsi

 # iscsiadm -m node
 10.0.0.10:3260,1 iqn.2014-04.edu.tamu.brazos.vmstore1:ovirt-data_iscsi

 # multipath -ll
 1IET_00010001 dm-3 IET,VIRTUAL-DISK
 size=500G features='0' hwhandler='0' wp=rw
 `-+- policy='round-robin 0' prio=1 status=active
   `- 8:0:0:1 sdd 8:48 active ready running
 1ATA_WDC_WD5003ABYZ-011FA0_WD-WMAYP0DNSAEZ dm-2 ATA,WDC WD5003ABYZ-0
 size=466G features='0' hwhandler='0' wp=rw
 `-+- policy='round-robin 0' prio=1 status=active
   `- 3:0:0:0 sdc 8:32 active ready running

 The first entry, 1IET_00010001 is the iSCSI LUN.

 The log when I click the array in the interface for the target is this:

 Thread-14::DEBUG::2014-10-21
 15:12:49,900::BindingXMLRPC::251::vds::(wrapper) client [192.168.202.99]
 flowID [7177dafe]
 Thread-14::DEBUG::2014-10-21
 15:12:49,901::task::595::TaskManager.Task::(_updateState)
 Task=`01d8d01e-8bfd-4764-890f-2026fdeb78d9`::moving from state init -
 state preparing
 Thread-14::INFO::2014-10-21
 15:12:49,901::logUtils::44::dispatcher::(wrapper) Run and protect:
 connectStorageServer(domType=3,
 spUUID='----', conList=[{'connection':
 '10.0.0.10', 'iqn': 'iqn.2014-04.edu.tamu.brazos.)
 Thread-14::DEBUG::2014-10-21
 15:12:49,902::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) '/usr/bin/sudo
 -n /sbin/iscsiadm -m node -T
 iqn.2014-04.edu.tamu.brazos.vmstore1:ovirt-data_iscsi -I default -p
 10.0.0.10:3260,1 --op=new' (cwd None)
 Thread-14::DEBUG::2014-10-21
 15:12:56,684::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) SUCCESS: err =
 ''; rc = 0
 Thread-14::DEBUG::2014-10-21
 15:12:56,685::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) '/usr/bin/sudo
 -n /sbin/iscsiadm -m node -T
 iqn.2014-04.edu.tamu.brazos.vmstore1:ovirt-data_iscsi -I default -p
 10.0.0.10:3260,1 -l' (cwd None)
 Thread-14::DEBUG::2014-10-21
 15:12:56,711::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) SUCCESS: err =
 ''; rc = 0
 Thread-14::DEBUG::2014-10-21
 15:12:56,711::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) '/usr/bin/sudo
 -n /sbin/iscsiadm -m node -T
 iqn.2014-04.edu.tamu.brazos.vmstore1:ovirt-data_iscsi -I default -p
 10.0.0.10:3260,1 -n node.startup -v manual --op)
 Thread-14::DEBUG::2014-10-21
 15:12:56,767::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) SUCCESS: err =
 ''; rc = 0
 Thread-14::DEBUG::2014-10-21
 15:12:56,767::lvm::373::OperationMutex::(_reloadvgs) Operation 'lvm reload
 operation' got the operation mutex
 Thread-14::DEBUG::2014-10-21
 15:12:56,768::lvm::296::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n
 /sbin/lvm vgs --config  devices { preferred_names = [\\^/dev/mapper/\\]
 ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3)
 Thread-14::DEBUG::2014-10-21
 15:12:56,968::lvm::296::Storage.Misc.excCmd::(cmd) SUCCESS: err = '  No
 volume groups found\n'; rc = 0
 Thread-14::DEBUG::2014-10-21
 15:12:56,969::lvm::415::OperationMutex::(_reloadvgs) Operation 'lvm reload
 operation' released the operation mutex
 Thread-14::DEBUG::2014-10-21
 15:12:56,974::hsm::2352::Storage.HSM::(__prefetchDomains) Found SD uuids: ()
 Thread-14::DEBUG::2014-10-21
 15:12:56,974::hsm::2408::Storage.HSM::(connectStorageServer) knownSDs: {}
 Thread-14::INFO::2014-10-21
 15

Re: [ovirt-users] Changing iSCSI LUN host IP and changing master domain

2014-10-21 Thread Trey Dockendorf
John,

Thanks again for the reply.  Yes the API at the path you mentioned shows
the domain.  This has to have been a bug as things began working after I
changed values in the database.  Somehow setting the new IP for the storage
connection in the database for both NFS and iSCSI resulted in the NFS
domain becoming master again and at that point the iSCSI magically went
active once NFS (master) was active.  I don't pretend to know how this
happened and even my boss laughed when I shrugged to the question how did
you fix it?.  I'd be glad to supply the devs with whatever information I
can, but I can't change much now as the goal of today was to get back
online and that's been achieved.

One thing I may have done that could have been a cause of iSCSI not coming
back was once I lost the IB fabric, in order to disconnect iSCSI that was
over ISER, I issued the vgchange -an domain ID and then logged out of
the iscsi session on each ovirt node.  One of my hosts would not
re-activate once everything was back online and doing a vgchange -ay
domain ID then removing the host from maintenance worked.  Since I had
to switch from one network to another and from iSER to iSCSI, I wanted all
active connections closed and the only way I could make the block devices
disconnect cleanly was to disable the volume group on the LUN.

Thanks,
- Trey

On Tue, Oct 21, 2014 at 4:06 PM, Sandra Taylor jtt77...@gmail.com wrote:

 Trey,
 The thread that keeps repeating is the call to repoStats. I believe
 it's part of the storage monitoring and in my environment it repeats
 every 15 seconds
 Mine looks like
 Thread-168::INFO::2014-10-21
 15:02:42,616::logUtils::44::dispatcher::(wrapper) Run and protect:
 repoStats(options=None)
 Thread-168::INFO::2014-10-21
 15:02:42,617::logUtils::47::dispatcher::(wrapper) Run and protect:
 repoStats, Return response: {'86f0a388-dc9d-4e44-a599-b3f2c9e58922':
 {'code': 0, 'version': 3, 'acquired': True, 'delay': '0.00066814',
 'lastCheck': '1.8', 'valid': True}}

 but yours isn't returning anything , that's the the response: {}

 But I think that the problem is that the hsm isn't finding volume
 groups in its call to lvm vgs, and thus no storage domains (below in
 the No volume groups found and  Found SD uuids: () )

 Thread-14::DEBUG::2014-10-21
 15:12:56,768::lvm::296::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n
 /sbin/lvm vgs --config  devices { preferred_names =
 [\\^/dev/mapper/\\] ignore_suspended_devices=1 write_cache_state=0
 disable_after_error_count=3)
 Thread-14::DEBUG::2014-10-21
 15:12:56,968::lvm::296::Storage.Misc.excCmd::(cmd) SUCCESS: err = '
 No volume groups found\n'; rc = 0
 Thread-14::DEBUG::2014-10-21
 15:12:56,969::lvm::415::OperationMutex::(_reloadvgs) Operation 'lvm
 reload operation' released the operation mutex
 Thread-14::DEBUG::2014-10-21
 15:12:56,974::hsm::2352::Storage.HSM::(__prefetchDomains) Found SD
 uuids: ()
 Thread-14::DEBUG::2014-10-21
 15:12:56,974::hsm::2408::Storage.HSM::(connectStorageServer) knownSDs:
 {}

 But I don't really know how that's possible considering you show what
 looks to be an domain in the lvscan.
 The only thing that comes to mind is that there was a bug in some of
 the iscsi initiator tools where there was an error returned if a
 session was already logged in but that doesn't look to be the case by
 the logs. Or maybe something like lvmetad caching but vdsm uses its
 own config to turn lvmetad off  (at /var/run/vdsm/lvm I think)

 Does the storage domain with that id exist ?
 It should be seen at
 /api/storagedomains/4eeb8415-c912-44bf-b482-2673849705c9

 -John



 On Tue, Oct 21, 2014 at 4:17 PM, Trey Dockendorf treyd...@gmail.com
 wrote:
  John,
 
  Thanks for reply.  The Discover function in GUI works...it's once I try
 and
  login (Click the array next to target) that things just hang
 indefinitely.
 
  # iscsiadm -m session
  tcp: [2] 10.0.0.10:3260,1
  iqn.2014-04.edu.tamu.brazos.vmstore1:ovirt-data_iscsi
 
  # iscsiadm -m node
  10.0.0.10:3260,1 iqn.2014-04.edu.tamu.brazos.vmstore1:ovirt-data_iscsi
 
  # multipath -ll
  1IET_00010001 dm-3 IET,VIRTUAL-DISK
  size=500G features='0' hwhandler='0' wp=rw
  `-+- policy='round-robin 0' prio=1 status=active
`- 8:0:0:1 sdd 8:48 active ready running
  1ATA_WDC_WD5003ABYZ-011FA0_WD-WMAYP0DNSAEZ dm-2 ATA,WDC WD5003ABYZ-0
  size=466G features='0' hwhandler='0' wp=rw
  `-+- policy='round-robin 0' prio=1 status=active
`- 3:0:0:0 sdc 8:32 active ready running
 
  The first entry, 1IET_00010001 is the iSCSI LUN.
 
  The log when I click the array in the interface for the target is this:
 
  Thread-14::DEBUG::2014-10-21
  15:12:49,900::BindingXMLRPC::251::vds::(wrapper) client [192.168.202.99]
  flowID [7177dafe]
  Thread-14::DEBUG::2014-10-21
  15:12:49,901::task::595::TaskManager.Task::(_updateState)
  Task=`01d8d01e-8bfd-4764-890f-2026fdeb78d9`::moving from state init -
 state
  preparing
  Thread-14::INFO::2014-10-21
  15:12:49,901::logUtils::44::dispatcher::(wrapper) Run and protect

[ovirt-users] Proper way to change iSCSI and NFS IP

2014-10-21 Thread Trey Dockendorf
What is the proper way to change iSCSI and NFS IP used to access the
storage domains?  My IB fabric which was doing storage crashed and we have
a scheduled maintenance window for next week at which time I'd like to
either move my storage to 10GbE or back to IB.  I was able to move things
off IB to standard TCP/IP by editing the database but that is likely not
the correct way.  I am on ovirt 3.4.3.  My NFS domain is the master and
iSCSI data domain is only used by two VMs while NFS is used by ~30 VMs.

Thanks,
- Trey
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] How to add custom lines in to host interface?

2014-10-19 Thread Trey Dockendorf
I'd be interested in this too.  I currently set CONNECTED_MODE outside of
ovirt using Puppet, and have no tried this with 3.5 as yet to upgrade.
Having full 65K MTU is key on my IB fabric and using iSER benefits from
maintaining that value.

- Trey
On Oct 19, 2014 10:11 AM, Arman Khalatyan arm2...@gmail.com wrote:

 Hi,
 I need to add following line in the hosts ifcfg-ib0 interface:
 ---
 CONNECTED_MODE=yes
 MTU=65520
 IPV6INIT=no
 ---
 From the web Interface I can change only custom  MTU.
 IB interface supports big MTUs only if it is in the connected mode.

 Are there way to set it during the deployment/upgrade process?
 Thanks,
 Arman.


 ___
 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] Is it possible to add ISCSI over iser?

2014-09-29 Thread Trey Dockendorf
Arman,

One of my storage domains is iSCSI using iSER.  You need the following
in vdsm.conf:

[irs]
iscsi_default_ifaces = iser,default

I believe the proper way to set that so it's preserved during node
updates is the following

# cat /etc/ovirt-host-deploy.conf.d/40-custom-vdsm-config.conf
[environment:enforce]
VDSM_CONFIG/irs/iscsi_default_ifaces=str:iser,default

The filename I believe can be changed, just requires .conf extension

Once VDSM is configured to use iser you can add the domain in the GUI
using the IPoIB IP address to initiate iSER.

ovirtnode01 # iscsiadm -m session
iser: [3] 192.168.211.245:3260,1 iqn.2014-04.DOMAIN.vmstore1:ovirt-data_iscsi

- Trey

On Wed, Sep 24, 2014 at 6:42 AM, Arman Khalatyan arm2...@gmail.com wrote:
 Hi,
 I am trying to attach my new storage domain over iser.
 My server always gets that request is tcp/ip not rdma.
 Simple work around is login from hosts over iser.
 Would be good to add a possibility to select the protocol of
 iscsi:tcp/iser/srp.

 Thanks,
 Arman

 PS
 for those who was struggling with same trouble:
 1) on hosts:
 add lines in /etc/rdma/rdma.conf
 # Load iSER module
 ISER_LOAD=YES
 2) service rdma restart (or modprobe ib_iser
 3) iscsiadm -m discovery -t st -p 10.10.10.31 -I iser
 4) iscsiadm -m node --login

 5) check if disks are there
 iscsiadm -m session -o show
 lssci
 [1228:0:0:0] storage IET  Controller   0001  -
 [1228:0:0:1] diskIET  VIRTUAL-DISK 0001  /dev/sde
  lsblk /dev/sde
 NAME MAJ:MIN RM
 SIZE RO TYPE  MOUNTPOINT
 sde8:64   0
 36.4T  0 disk
 ââ100090001 (dm-8)   253:80
 36.4T  0 mpath
   ââ18b70b0d--4944--4c73--970d--87a1af353b9f-metadata (dm-9) 253:90
 512M  0 lvm
   ââ18b70b0d--4944--4c73--970d--87a1af353b9f-ids (dm-10) 253:10   0
 128M  0 lvm
   ââ18b70b0d--4944--4c73--970d--87a1af353b9f-leases (dm-11)  253:11   0
 2G  0 lvm
   ââ18b70b0d--4944--4c73--970d--87a1af353b9f-outbox (dm-12)  253:12   0
 128M  0 lvm
   ââ18b70b0d--4944--4c73--970d--87a1af353b9f-inbox (dm-13)   253:13   0
 128M  0 lvm
   ââ18b70b0d--4944--4c73--970d--87a1af353b9f-master (dm-14)  253:14   0
 1G  0 lvm

 ___
 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] Admin console - Always show advanced options

2014-09-19 Thread Trey Dockendorf
If it was 3.4 then it's not working as I've always had to click the
advanced options.  Likely a 3.5 feature then?

- Trey
On Sep 19, 2014 7:33 AM, Alexander Wels aw...@redhat.com wrote:

 It should remember your setting of the advanced mode so once you clicked it
 once, the next time it should be in advanced mode. I forget which version
 this
 became available, might be 3.5 or might be 3.4.


 On Friday, September 19, 2014 02:38:38 PM John Gardeniers wrote:
  Hi All,
 
  When viewing/editing a VM's properties in the admin console is it
  possible to show the advanced options by default? Quite frankly, I can't
  understand why that isn't the default. The standard options show nothing
  that isn't already visible in the properties window in the console, so
  what's the point of making that the default in the editing window?
 
  Regards,
  John
 
  ___
  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

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


[ovirt-users] VDSM and iSCSI issue due to ulimits

2014-09-12 Thread Trey Dockendorf
Today I got an alert from monitoring systems that my EL7 MariaDB VM
was down.  I looked in oVirt and it showed the VM as paused due to
storage I/O problem.  That VM is the only one currently attached to
disks that are on an iSCSI storage domain.  That iSCSI storage domain
uses iSER (over DDR Infiniband).

My instance is made up of two ovirt nodes, both with CentOS 6.5
running oVirt 3.4.3.  The host that was running this VM has 16 running
VMs total.

I looked at the vdsm logs for the hypervisor and found log entries
with No free file handlers in pool.  Below are logs.

I quick google showed old posts about it being a ulimit problem.

Right now after resuming the paused VM I see this on the VDSM server

# lsof -u vdsm | wc -l
2377
# sudo -H -u vdsm -s ulimit -a
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 1032295
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 12288
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 10240
cpu time   (seconds, -t) unlimited
max user processes  (-u) 4096
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

If the issue was due to number of open files, is it the case that if
the only VM using the iSCSI storage domain was paused, the file
descriptors were flushed?

How do I go about finding out the cause of this, so I can prevent
future issues?  Is the fix to just increase the nofile ulimit for
vdsm in /etc/security/limits.d/99-vdsm.conf?

Thanks,
- Trey

LOGS:


Sep 12 12:10:49 ovirtnode01 vdsm TaskManager.Task ERROR
Task=`f467714c-8948-4cc3-94af-efba6b67701c`::Unexpected
error#012Traceback (most recent call last):#012  File
/usr/share/vdsm/storage/task.py, line 873, in _run#012return
fn(*args, **kargs)#012  File /usr/share/vdsm/logUtils.py, line 45,
in wrapper#012res = f(*args, **kwargs)#012  File
/usr/share/vdsm/storage/hsm.py, line 3055, in getVolumeSize#012
apparentsize = str(dom.getVSize(imgUUID, volUUID))#012  File
/usr/share/vdsm/storage/fileSD.py, line 314, in getVSize#012
return self.oop.os.stat(volPath).st_size#012  File
/usr/share/vdsm/storage/remoteFileHandler.py, line 312, in
callCrabRPCFunction#012raise Exception(No free file handlers in
pool)#012Exception: No free file handlers in pool
Sep 12 12:10:49 ovirtnode01 vdsm vm.Vm ERROR
vmId=`967dce86-63c2-412a-97c5-d7c6f1af8dfb`::Unable to update the
volume 92c6cfd0-c236-44ab-894d-cb80421dd865 (domain:
6da59b00-0de7-4219-960b-d581b27052b5 image:
06060f34-12c5-4396-bfe3-ad0f1d4b03fc) for the drive vda
Sep 12 12:10:54 ovirtnode01 sanlock[3379]: 2014-09-12 12:10:54-0500
1773913 [5185]: s1 delta_renew read rv -202 offset 0
/rhev/data-center/mnt/192.168.211.245:_tank_ovirt_data/6da59b00-0de7-4219-960b-d581b27052b5/dom_md/ids
Sep 12 12:10:54 ovirtnode01 sanlock[3379]: 2014-09-12 12:10:54-0500
1773913 [5185]: s1 renewal error -202 delta_length 10 last_success
1773883
repeats a few times
Sep 12 12:10:58 ovirtnode01 vdsm vm.Vm ERROR
vmId=`151972dc-0025-470e-bdfe-38d3b085a63c`::Unable to update the
volume 1b589b1b-aeb8-4a7a-a005-d5042de47f36 (domain:
6da59b00-0de7-4219-960b-d581b27052b5 image:
5d9456a3-12e1-4e50-b899-b12430a4fdb9) for the drive vda
Sep 12 12:10:58 ovirtnode01 vdsm vm.Vm ERROR
vmId=`b15f90ff-f359-447a-b309-2cf64d01d0ce`::Unable to update the
volume 70a0fee4-2dd3-4460-94da-9ddbfb66845b (domain:
6da59b00-0de7-4219-960b-d581b27052b5 image:
4e133730-f549-4b49-a8e9-baedaca4c1f1) for the drive vda
snip

Then lines like this:

Sep 12 12:11:49 ovirtnode01 sanlock[3379]: 2014-09-12 12:11:49-0500
1773968 [5185]: s1 delta_renew read rv -2 offset 0
/rhev/data-center/mnt/192.168.211.245:_tank_ovirt_data/6da59b00-0de7-4219-960b-d581b27052b5/dom_md/ids
Sep 12 12:11:49 ovirtnode01 sanlock[3379]: 2014-09-12 12:11:49-0500
1773968 [5185]: s1 renewal error -2 delta_length 10 last_success
1773883
Sep 12 12:11:49 ovirtnode01 vdsm TaskManager.Task ERROR
Task=`b39a6636-451e-409c-9a81-7392000206d3`::Unexpected
error#012Traceback (most recent call last):#012  File
/usr/share/vdsm/storage/task.py, line 873, in _run#012return
fn(*args, **kargs)#012  File /usr/share/vdsm/logUtils.py, line 45,
in wrapper#012res = f(*args, **kwargs)#012  File
/usr/share/vdsm/storage/hsm.py, line 3055, in getVolumeSize#012
apparentsize = str(dom.getVSize(imgUUID, volUUID))#012  File
/usr/share/vdsm/storage/fileSD.py, line 314, in getVSize#012
return self.oop.os.stat(volPath).st_size#012  File
/usr/share/vdsm/storage/remoteFileHandler.py, line 297, in
callCrabRPCFunction#012*args, **kwargs)#012  File
/usr/share/vdsm/storage/remoteFileHandler.py, line 184, in
callCrabRPCFunction#012rawLength =
self._recvAll(LENGTH_STRUCT_LENGTH, 

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-22 Thread Trey Dockendorf
For what it's worth I managed to get the ovirt-engine's public key
from engine.cer using Ruby and turn it into a Puppet fact.  Had to
borrow some code from https://github.com/bensie/sshkey

https://github.com/treydock/puppet-ovirt/blob/1.x/lib/facter/ovirt_engine_ssh_pubkey.rb

Thanks for all the help Alon, now have semi-automated deployment of
nodes :).  Once 3.5 is released and the Foreman integration is in
place, it will be much nicer.

Thanks,
- Trey

On Fri, Aug 22, 2014 at 5:30 AM, Alon Bar-Lev alo...@redhat.com wrote:

 you are hijacking this thread... but anyway... please refer to the original 
 question, how to easily convert X.509 certificate to SSH public key. the best 
 method should avoid using the private key. newer ssh-keygen supports exactly 
 that.

 - Original Message -
 From: Sven Kieske s.kie...@mittwald.de
 To: Alon Bar-Lev alo...@redhat.com
 Cc: users@ovirt.org
 Sent: Friday, August 22, 2014 1:24:17 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 well yeah, it does not generate pkcs#8 by default
 but you can easily convert existing keys via openssl:

 openssl pkcs8 -topk8 -v2 des3 \
 -in test_rsa_key.old -passin 'pass:super secret passphrase' \
 -out test_rsa_key -passout 'pass:super secret passphrase'
 see this page for more details:
 http://martin.kleppmann.com/2013/05/24/improving-security-of-ssh-private-keys.html

 newer ssh-keygen versions use PBKDF2 by default and not MD5 anymore.

 HTH

 Am 22.08.2014 10:51, schrieb Alon Bar-Lev:
  the ssh-keygen does not.

 --
 Mit freundlichen Grüßen / Regards

 Sven Kieske

 Systemadministrator
 Mittwald CM Service GmbH  Co. KG
 Königsberger Straße 6
 32339 Espelkamp
 T: +49-5772-293-100
 F: +49-5772-293-333
 https://www.mittwald.de
 Geschäftsführer: Robert Meyer
 St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
 Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
 ___
 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] Proper way to change and persist vdsm configuration options

2014-08-21 Thread Trey Dockendorf
I likely won't automate this yet, as a lot of what's coming in 3.5
seems to obsolete many things I was doing previously via Puppet.  In
particular the Foreman integration and the ability to add custom
iptables rules to engine-config.  Previous posts on the list made is
seem like modifying IPTables could potentially make upgrades less
reliable.

Created a gist of a working series of commands based on Alon's example
using the Host Deploy Protocol [1].

https://gist.github.com/treydock/570a776b5c160bca7c9c

Curious , where is the public key used by the ovirt-engine stored?
The one that is available using command=get-ssh-trust.  Is there a way
to query it from the engine?  I'm thinking if it would be possible to
create a custom Facter face that stores the value of that public key
so easier to re-use and access for deployment.

Thanks,
- Trey

[1] - http://www.ovirt.org/Features/HostDeployProtocol

On Tue, Aug 5, 2014 at 11:32 PM, Alon Bar-Lev alo...@redhat.com wrote:


 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Alon Bar-Lev alo...@redhat.com
 Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian 
 Deutsch fabi...@redhat.com, Dan
 Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com, Douglas 
 Landgraf dougsl...@redhat.com, Oved
 Ourfali ov...@redhat.com
 Sent: Tuesday, August 5, 2014 11:27:45 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 Thanks for clarifying, makes sense now.

 The public key trust needed for registration, is that the same key
 that would be used when adding host via UI?

 yes.

 you can download it via:
 $ curl 
 'http://engine/ovirt-engine/services/pki-resource?resource=engine-certificateformat=OPENSSH-PUBKEY'
 $ curl 
 'http://engine/ovirt-engine/services/host-register?version=1command=get-ssh-trust'

 probably better to use https and verify CA certificate fingerprint if you do 
 that from host.

 Any examples of how to use the HostDeployProtocol [1]?  I like the
 idea of using registration but haven't the slightest idea how to
 implement what's described in the docs [1].  I do recall seeing an
 article posted (searching email and can't find) that had a nice
 walk-through of how to use the oVirt API using browser tools.  I'm
 unsure if this HostDeployProtocol would be done that way or via some
 other method.

 there are two apis, the formal rest-api that is exposed by the engine and can 
 be accessed using any rest api tool or ovirt-engine-cli, 
 ovirt-engine-sdk-java, ovirt-engine-sdk-python wrappers. I sent you a minimal 
 example in previous message.

 and the host-deploy protocol[1], which should have been exposed in the 
 rest-api, but for some reason I cannot understand it was not included in the 
 public interface of the engine.

 the advantage of using the rest-api is that you can achieve full cycle using 
 the protocol, the add host cycle is what you seek.

 the host-deploy protocol just register the host, but the sysadmin needs to 
 approve the host via the ui (or via the rest api) before it is usable.


 Thanks,
 - Trey


 [1] http://www.ovirt.org/Features/HostDeployProtocol

 On Tue, Aug 5, 2014 at 3:01 PM, Alon Bar-Lev alo...@redhat.com wrote:
 
 
  - Original Message -
  From: Trey Dockendorf treyd...@gmail.com
  To: Alon Bar-Lev alo...@redhat.com
  Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian
  Deutsch fabi...@redhat.com, Dan
  Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com,
  Douglas Landgraf dougsl...@redhat.com, Oved
  Ourfali ov...@redhat.com
  Sent: Tuesday, August 5, 2014 10:45:12 PM
  Subject: Re: [ovirt-users] Proper way to change and persist vdsm
  configuration options
 
  Excellent, so installing 'ovirt-host-deploy' on each node then
  configuring the /etc/ovirt-host-deploy.conf.d files seems very
  automate-able, will see how it works in practice.
 
  you do not need to install the ovirt-host-deploy, just create the files.
 
  Regarding the actual host registration and getting the host added to
  ovirt-engine, are there other methods besides the API and the sdk?
  Would it be possible to configure the necessary
  ovirt-host-deploy.conf.d files then execute ovirt-host-deploy?  I
  notice that running 'ovirt-host-deploy' wants to make whatever host
  executes it a ovir hypervisor but haven't yet run it all the way
  through as no server to test with at this time.  There seems to be no
  --help or similar command line argument.
 
  you should not run host-deploy directly, but via the engine's process,
  either registration or add host as I replied previously.
 
  when base system is ready, you issue add host via api of engine or via ui,
  the other alternative is to register the host host the host-deploy
  protocol, and approve the host via api of engine or via ui.
 
  I'm sure this will all be more clear once I attempt the steps and run
  through the motions.  Will try to find a system to test on so I'm
  ready once our new

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-21 Thread Trey Dockendorf
Is there a method that works in EL6?

$ openssl x509 -in /etc/pki/ovirt-engine/certs/engine.cer -noout
-pubkey | ssh-keygen -i -m PKCS8 -f /dev/stdin
ssh-keygen: illegal option -- m

$ openssl x509 -in /etc/pki/ovirt-engine/certs/engine.cer -noout
-pubkey | ssh-keygen -i -f /dev/stdin
buffer_get_string_ret: bad string length 813826338
key_from_blob: can't read key type
decode blob failed.

I achieved somewhat similar result by doing the following, though
likely is a security issue having something like Facter read from
/etc/pki/ovirt-engine/keys

$  ssh-keygen -y -f /etc/pki/ovirt-engine/keys/engine_id_rsa
ssh-rsa PUBKEY

Thanks,
- Trey

On Thu, Aug 21, 2014 at 1:44 PM, Alon Bar-Lev alo...@redhat.com wrote:


 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Alon Bar-Lev alo...@redhat.com
 Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian 
 Deutsch fabi...@redhat.com, Dan
 Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com, Douglas 
 Landgraf dougsl...@redhat.com, Oved
 Ourfali ov...@redhat.com
 Sent: Thursday, August 21, 2014 9:41:03 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 Sorry, I meant the SSH public key.  Is that a file or in the database?
  I did a grep for the public key downloaded via the
 command=get-ssh-trust and found no files in /etc/ or
 /var/lib/ovirt-engine that matched.

 openssl x509 -in /etc/pki/ovirt-engine/certs/engine.cer -noout -pubkey | 
 ssh-keygen -i -m PKCS8 -f /dev/stdin


 - Trey

 On Thu, Aug 21, 2014 at 11:33 AM, Alon Bar-Lev alo...@redhat.com wrote:
 
 
  - Original Message -
  From: Trey Dockendorf treyd...@gmail.com
  To: Alon Bar-Lev alo...@redhat.com
  Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian
  Deutsch fabi...@redhat.com, Dan
  Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com,
  Douglas Landgraf dougsl...@redhat.com, Oved
  Ourfali ov...@redhat.com
  Sent: Thursday, August 21, 2014 7:15:56 PM
  Subject: Re: [ovirt-users] Proper way to change and persist vdsm
  configuration options
 
  I likely won't automate this yet, as a lot of what's coming in 3.5
  seems to obsolete many things I was doing previously via Puppet.  In
  particular the Foreman integration and the ability to add custom
  iptables rules to engine-config.  Previous posts on the list made is
  seem like modifying IPTables could potentially make upgrades less
  reliable.
 
  Created a gist of a working series of commands based on Alon's example
  using the Host Deploy Protocol [1].
 
  https://gist.github.com/treydock/570a776b5c160bca7c9c
 
  Curious , where is the public key used by the ovirt-engine stored?
  The one that is available using command=get-ssh-trust.  Is there a way
  to query it from the engine?  I'm thinking if it would be possible to
  create a custom Facter face that stores the value of that public key
  so easier to re-use and access for deployment.
 
  /etc/pki/ovirt-engine/certs/engine.cer
 
 
  Thanks,
  - Trey
 
  [1] - http://www.ovirt.org/Features/HostDeployProtocol
 
  On Tue, Aug 5, 2014 at 11:32 PM, Alon Bar-Lev alo...@redhat.com wrote:
  
  
   - Original Message -
   From: Trey Dockendorf treyd...@gmail.com
   To: Alon Bar-Lev alo...@redhat.com
   Cc: ybronhei ybron...@redhat.com, users users@ovirt.org,
   Fabian
   Deutsch fabi...@redhat.com, Dan
   Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com,
   Douglas Landgraf dougsl...@redhat.com, Oved
   Ourfali ov...@redhat.com
   Sent: Tuesday, August 5, 2014 11:27:45 PM
   Subject: Re: [ovirt-users] Proper way to change and persist vdsm
   configuration options
  
   Thanks for clarifying, makes sense now.
  
   The public key trust needed for registration, is that the same key
   that would be used when adding host via UI?
  
   yes.
  
   you can download it via:
   $ curl
   'http://engine/ovirt-engine/services/pki-resource?resource=engine-certificateformat=OPENSSH-PUBKEY'
   $ curl
   'http://engine/ovirt-engine/services/host-register?version=1command=get-ssh-trust'
  
   probably better to use https and verify CA certificate fingerprint if
   you
   do that from host.
  
   Any examples of how to use the HostDeployProtocol [1]?  I like the
   idea of using registration but haven't the slightest idea how to
   implement what's described in the docs [1].  I do recall seeing an
   article posted (searching email and can't find) that had a nice
   walk-through of how to use the oVirt API using browser tools.  I'm
   unsure if this HostDeployProtocol would be done that way or via some
   other method.
  
   there are two apis, the formal rest-api that is exposed by the engine
   and
   can be accessed using any rest api tool or ovirt-engine-cli,
   ovirt-engine-sdk-java, ovirt-engine-sdk-python wrappers. I sent you a
   minimal example in previous message.
  
   and the host-deploy protocol[1], which should have been exposed in the
   rest-api, but for some reason I

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-05 Thread Trey Dockendorf
On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:
 Hey,

 Just noticed something that I forgot about..
 before filing new BZ, see in ovirt-host-deploy README.environment [1] the
 section:
 VDSM/configOverride(bool) [True]
 Override vdsm configuration file.

 changing it to false will keep your vdsm.conf file as is after deploying the
 host again (what happens after node upgrade)

 [1]
 https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment

 please check if that what you meant..

 Thanks,
 Yaniv Bronhaim.


I was unaware of that package.  I will check that out as that seems to
be what I am looking for.

I have not filed this in BZ and will hold off pending
ovirt-host-deploy.  If you feel a BZ is still necessary then please do
file one and I would be happy to provide input if it would help.

Right now this is my workflow.

1. Foreman provisions bare-metal server with CentOS 6.5
2. Once provisioned and system rebooted Puppet applies puppet-ovirt
[1] module that adds the necessary yum repos, and installs packages.
Part of my Puppet deployment is basic things like sudo management
(vdsm's sudo is account for), sssd configuration, and other aspects
that are needed by every system in my infrastructure.  Part of the
ovirt::node Puppet class is managing vdsm.conf, and in my case that
means ensuring iSER is enabled for iSCSI over IB.
3. Once host is online and has had the full Puppet catalog applied I
log into ovirt-engine web interface and add those host (pulling it's
data via the Foreman provider).

What I've noticed is that after step #3, after a host is added by
ovirt-engine, the vdsm.conf file is reset to default and I have to
reapply Puppet before it can be used as the one of my Data Storage
Domains requires iSER (not available over TCP).

What would be the workflow using ovirt-host-deploy?  Thus far I've had
to piece together my workflow based on the documentation and filling
in blanks where possible since I do require customizations to
vdsm.conf and the documented workflow of adding a host via web UI does
not allow for such customization.

Thanks,
- Trey

[1] - https://github.com/treydock/puppet-ovirt (README not fully
updated as still working out how to use Puppet with oVirt)


 On 08/05/2014 08:12 AM, Trey Dockendorf wrote:

 I'll file BZ.  As far as I can recall this has been an issue since 3.3.x
 as
 I have been using Puppet to modify values and have had to rerun Puppet
 after installing a node via GUI and when performing update from GUI.
 Given
 that it has occurred when VDSM version didn't change on the node it seems
 likely to be something being done by Python code that bootstraps a node
 and
 performs the other tasks.  I won't have any systems available to test with
 for a few days.  New hardware specifically for our oVirt deployment is on
 order so should be able to more thoroughly debug and capture logs at that
 time.

 Would using vdsm-reg be a better solution for adding new nodes?  I only
 tried using vdsm-reg once and it went very poorly...lots of missing
 dependencies not pulled in from yum install I had to install manually via
 yum.  Then the node was auto added to newest cluster with no ability to
 change the cluster.  Be happy to debug that too if there's some docs that
 outline the expected behavior.

 Using vdsm-reg or something similar seems like a better fit for puppet
 deployed nodes, as opposed to requiring GUI steps to add the node.

 Thanks
 - Trey
 On Aug 4, 2014 5:53 AM, ybronhei ybron...@redhat.com wrote:

 On 07/31/2014 01:28 AM, Trey Dockendorf wrote:

 I'm running ovirt nodes that are stock CentOS 6.5 systems with VDSM
 installed.  I am using iSER to do iSCSI over RDMA and to make that
 work I have to modify /etc/vdsm/vdsm.conf to include the following:

 [irs]
 iscsi_default_ifaces = iser,default

 I've noticed that any time I upgrade a node from the engine web
 interface that changes to vdsm.conf are wiped out.  I don't know if
 this is being done by the configuration code or by the vdsm package.
 Is there a more reliable way to ensure changes to vdsm.conf are NOT
 removed automatically?


 Hey,

 vdsm.conf shouldn't wiped out and shouldn't changed at all during
 upgrade.
 other related conf files (such as libvirtd.conf) might be overrided to
 keep
 defaults configurations for vdsm. but vdsm.conf should persist with
 user's
 modification. from my check, regular yum upgrade doesn't touch vdsm.conf

 Douglas can you verify that with node upgrade? might be specific to that
 flow..

 Trey, can file a bugzilla on that and describe your steps there?

 Thanks

 Yaniv Bronhaim,


 Thanks,
 - Trey
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users



 --
 Yaniv Bronhaim.



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


Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-05 Thread Trey Dockendorf
On Tue, Aug 5, 2014 at 12:37 PM, Alon Bar-Lev alo...@redhat.com wrote:
 Hi,

 Do you actually use puppet over ovirt-node?
 This is unsupported.

 Regards,
 Alon


I use Puppet to configure everything on the system and some of those
things conflict with changes made by ovirt-engine when adding a node
so I've moved to managing those changes in an ovirt Puppet module.

When you refer to ovirt-node your refering to the pre-built ISO
images?  AFAIK the ovirt-node is not an option for me as I use
Infiniband to do all storage connections.  Currently NFS is done using
IPoIB (NFS over RDMA was crashing so I am not pursuing at the moment)
and iSCSI is done using iSER.  At some point in time I'd like to use
IB interfaces in my guests utilizing SR-IOV which my Mellanox cards
support, but I'm postponing that project till after our HPC cluster's
upgraded :)

Right now the Puppet module does the following:

* Configures firewall rules just like what is done by ovirt (with
exception of a few not supported by puppetlabs-firewall, so I override
global directive that purges unknown firewall rules)
** This is necessary as I have to add other Firewall rules, such as Zabbix
* Exports /etc/hosts entry for the node that is collected by
ovirt-engine host so that if DNS goes down ovirt-engine does not lose
access to ovirtmgmt interfaces
* Install yum repos for ovirt
* install vdsm
* ensure vdsm.conf exists
* Populates /etc/vdsm/vdsm.id (IIRC a bug in previous ovirt required this)
* Ensures vdsmd is running and will start at boot
* Ensures vdsm sudo rules are present.
* Manages default vdsm.conf configurations as a Puppet type,
vdsm_config, rather than managing file contents via template (allows
for purging unmanaged entries also)

A lot of the above is handled by ovirt already, but in the past
customizations were not possible (firewall rules, vdsm.conf entries,
etc) so if I was going to have to manage those separately I wanted
them in Puppet :)

Now that I'm aware of ovirt-host-deploy and have seen the potential
of using vdsm-reg in Puppet, I'm curious what is the right way to
automate node deployment's in oVirt. Ideally I could still use Puppet
to configure the method or fill in the gaps for customizations that
are needed (ie enabling iSER).

I'd be glad to know what the recommended method for automating ovirt
would be, and would be happy to refactor my module in hopes it would
offer other Puppet users a quick-start way to deploy oVirt while still
doing things the ovirt way.

If the right way is using the ovirt-node images then I'd like to know
what customizations are possible on those images and so on.  oVirt is
moving very rapidly and despite using ovirt for a long time I'm still
learning new things about it almost daily, so forgive any of my
assumptions above that may be wrong :).

Thanks,
- Trey

 - Original Message -
 From: ybronhei ybron...@redhat.com
 To: Trey Dockendorf treyd...@gmail.com
 Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan 
 Kenigsberg dan...@redhat.com, Itamar
 Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, Alon 
 Bar-Lev alo...@redhat.com
 Sent: Tuesday, August 5, 2014 8:32:04 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 Hey,

 Just noticed something that I forgot about..
 before filing new BZ, see in ovirt-host-deploy README.environment [1]
 the section:
 VDSM/configOverride(bool) [True]
  Override vdsm configuration file.

 changing it to false will keep your vdsm.conf file as is after deploying
 the host again (what happens after node upgrade)

 [1]
 https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment

 please check if that what you meant..

 Thanks,
 Yaniv Bronhaim.

 On 08/05/2014 08:12 AM, Trey Dockendorf wrote:
  I'll file BZ.  As far as I can recall this has been an issue since 3.3.x as
  I have been using Puppet to modify values and have had to rerun Puppet
  after installing a node via GUI and when performing update from GUI.  Given
  that it has occurred when VDSM version didn't change on the node it seems
  likely to be something being done by Python code that bootstraps a node and
  performs the other tasks.  I won't have any systems available to test with
  for a few days.  New hardware specifically for our oVirt deployment is on
  order so should be able to more thoroughly debug and capture logs at that
  time.
 
  Would using vdsm-reg be a better solution for adding new nodes?  I only
  tried using vdsm-reg once and it went very poorly...lots of missing
  dependencies not pulled in from yum install I had to install manually via
  yum.  Then the node was auto added to newest cluster with no ability to
  change the cluster.  Be happy to debug that too if there's some docs that
  outline the expected behavior.
 
  Using vdsm-reg or something similar seems like a better fit for puppet
  deployed nodes, as opposed to requiring GUI steps to add the node.
 
  Thanks
  - Trey

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-05 Thread Trey Dockendorf
Ah, thank you for the input!  Just so I'm not spending time
implementing the wrong changes, let me confirm I understand your
comments.

1) Deploy host with Foreman
2) Apply Puppet catalog including ovirt Puppet module
3) Initiate host-deploy via rest API

In the ovirt module the following takes place:

2a) Add yum repos
2b) Manage  /etc/ovirt-host-deploy.conf.d/40-xxx.conf

For #2b I have a few questions

* The name of the .conf file is simply for sorting and
labeling/organization, it has not functional impact on what those
overrides apply to?
* That file is managed on the ovirt-engine server, not the actual nodes?
* Is there any way to apply overrides to specific hosts?  For example
if I have some hosts that require a config and others that don't, how
would I separate those *.conf files?  This is more theoretical as
right now my setup is common across all nodes.

For #3...the implementation of API calls from within Puppet is a
challenge and one I can't tackle yet, but definitely will make it a
goal for the future.  In the mean time, what's the manual way to
initiate host-deploy?  Is there a CLI command that would have the same
result as an API call or is the recommended way to perform the API
call manually (ie curl)?

Thanks!
- Trey

On Tue, Aug 5, 2014 at 1:45 PM, Alon Bar-Lev alo...@redhat.com wrote:


 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: ybronhei ybron...@redhat.com
 Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan 
 Kenigsberg dan...@redhat.com, Itamar
 Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, Alon 
 Bar-Lev alo...@redhat.com
 Sent: Tuesday, August 5, 2014 9:36:24 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:
  Hey,
 
  Just noticed something that I forgot about..
  before filing new BZ, see in ovirt-host-deploy README.environment [1] the
  section:
  VDSM/configOverride(bool) [True]
  Override vdsm configuration file.
 
  changing it to false will keep your vdsm.conf file as is after deploying
  the
  host again (what happens after node upgrade)
 
  [1]
  https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment
 
  please check if that what you meant..
 
  Thanks,
  Yaniv Bronhaim.
 

 I was unaware of that package.  I will check that out as that seems to
 be what I am looking for.

 I have not filed this in BZ and will hold off pending
 ovirt-host-deploy.  If you feel a BZ is still necessary then please do
 file one and I would be happy to provide input if it would help.

 Right now this is my workflow.

 1. Foreman provisions bare-metal server with CentOS 6.5
 2. Once provisioned and system rebooted Puppet applies puppet-ovirt
 [1] module that adds the necessary yum repos

 and should stop here..

 , and installs packages.
 Part of my Puppet deployment is basic things like sudo management
 (vdsm's sudo is account for), sssd configuration, and other aspects
 that are needed by every system in my infrastructure.  Part of the
 ovirt::node Puppet class is managing vdsm.conf, and in my case that
 means ensuring iSER is enabled for iSCSI over IB.

 you can create a file /etc/ovirt-host-deploy.conf.d/40-xxx.conf
 ---
 VDSM_CONFIG/section/key=str:content
 ---

 this will create a proper vdsm.conf when host-deploy is initiated.

 you should now use the rest api to initiate host-deploy.

 3. Once host is online and has had the full Puppet catalog applied I
 log into ovirt-engine web interface and add those host (pulling it's
 data via the Foreman provider).

 right, but you should let this process install packages and manage 
 configuration.

 What I've noticed is that after step #3, after a host is added by
 ovirt-engine, the vdsm.conf file is reset to default and I have to
 reapply Puppet before it can be used as the one of my Data Storage
 Domains requires iSER (not available over TCP).

 right, see above.

 What would be the workflow using ovirt-host-deploy?  Thus far I've had
 to piece together my workflow based on the documentation and filling
 in blanks where possible since I do require customizations to
 vdsm.conf and the documented workflow of adding a host via web UI does
 not allow for such customization.

 Thanks,
 - Trey

 [1] - https://github.com/treydock/puppet-ovirt (README not fully
 updated as still working out how to use Puppet with oVirt)

 
  On 08/05/2014 08:12 AM, Trey Dockendorf wrote:
 
  I'll file BZ.  As far as I can recall this has been an issue since 3.3.x
  as
  I have been using Puppet to modify values and have had to rerun Puppet
  after installing a node via GUI and when performing update from GUI.
  Given
  that it has occurred when VDSM version didn't change on the node it seems
  likely to be something being done by Python code that bootstraps a node
  and
  performs the other tasks.  I won't have any systems available to test with
  for a few days.  New

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-05 Thread Trey Dockendorf
Excellent, so installing 'ovirt-host-deploy' on each node then
configuring the /etc/ovirt-host-deploy.conf.d files seems very
automate-able, will see how it works in practice.

Regarding the actual host registration and getting the host added to
ovirt-engine, are there other methods besides the API and the sdk?
Would it be possible to configure the necessary
ovirt-host-deploy.conf.d files then execute ovirt-host-deploy?  I
notice that running 'ovirt-host-deploy' wants to make whatever host
executes it a ovir hypervisor but haven't yet run it all the way
through as no server to test with at this time.  There seems to be no
--help or similar command line argument.

I'm sure this will all be more clear once I attempt the steps and run
through the motions.  Will try to find a system to test on so I'm
ready once our new servers arrive.

Thanks,
- Trey

On Tue, Aug 5, 2014 at 2:23 PM, Alon Bar-Lev alo...@redhat.com wrote:


 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Alon Bar-Lev alo...@redhat.com
 Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian 
 Deutsch fabi...@redhat.com, Dan
 Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com, Douglas 
 Landgraf dougsl...@redhat.com
 Sent: Tuesday, August 5, 2014 10:01:14 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 Ah, thank you for the input!  Just so I'm not spending time
 implementing the wrong changes, let me confirm I understand your
 comments.

 1) Deploy host with Foreman
 2) Apply Puppet catalog including ovirt Puppet module
 3) Initiate host-deploy via rest API

 In the ovirt module the following takes place:

 2a) Add yum repos
 2b) Manage  /etc/ovirt-host-deploy.conf.d/40-xxx.conf


 you can have any # of files with any prefix :))

 For #2b I have a few questions

 * The name of the .conf file is simply for sorting and
 labeling/organization, it has not functional impact on what those
 overrides apply to?

 right.

 * That file is managed on the ovirt-engine server, not the actual nodes?

 currently on the host, in future we will provide a method to add this to 
 engine database[1]

 [1] http://gerrit.ovirt.org/#/c/27064/

 * Is there any way to apply overrides to specific hosts?  For example
 if I have some hosts that require a config and others that don't, how
 would I separate those *.conf files?  This is more theoretical as
 right now my setup is common across all nodes.

 the poppet module can put whatever required on each host.

 For #3...the implementation of API calls from within Puppet is a
 challenge and one I can't tackle yet, but definitely will make it a
 goal for the future.  In the mean time, what's the manual way to
 initiate host-deploy?  Is there a CLI command that would have the same
 result as an API call or is the recommended way to perform the API
 call manually (ie curl)?

 well, you can register host using the following protocol[1], but it is 
 difficult to do this securely, what you actually need is to establish ssh 
 trust for root with engine key then register.

 you can also use the register command using curl by something like (I have 
 not checked):
 https://admin%40internal:password@engine/ovirt-engine/api/hosts
 ---
 ?xml version=1.0 encoding=UTF-8 standalone=yes?
 host
   namehost1/name
   addressdns/address
   ssh
 authentication_methodpublickey/authentication_method
   /ssh
   cluster id=cluster-uuid/
 /host
 ---

 you can also use the ovirt-engine-sdk-python package:
 ---
 import ovirtsdk.api
 import ovirtsdk.xml

 sdk = ovirtsdk.api.API(
 url='https://host/ovirt-engine/api',
 username='admin@internal',
 password='password',
 insecure=True,
 )
 sdk.hosts.add(
 ovirtsdk.xml.params.Host(
 name='host1',
 address='host1',
 cluster=engine_api.clusters.get(
 'cluster'
 ),
 ssh=self._ovirtsdk_xml.params.SSH(
 authentication_method='publickey',
 ),
 )
 )
 ---

 [1] http://www.ovirt.org/Features/HostDeployProtocol


 Thanks!
 - Trey

 On Tue, Aug 5, 2014 at 1:45 PM, Alon Bar-Lev alo...@redhat.com wrote:
 
 
  - Original Message -
  From: Trey Dockendorf treyd...@gmail.com
  To: ybronhei ybron...@redhat.com
  Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan
  Kenigsberg dan...@redhat.com, Itamar
  Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, Alon
  Bar-Lev alo...@redhat.com
  Sent: Tuesday, August 5, 2014 9:36:24 PM
  Subject: Re: [ovirt-users] Proper way to change and persist vdsm
  configuration options
 
  On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:
   Hey,
  
   Just noticed something that I forgot about..
   before filing new BZ, see in ovirt-host-deploy README.environment [1]
   the
   section:
   VDSM

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-05 Thread Trey Dockendorf
Thanks for clarifying, makes sense now.

The public key trust needed for registration, is that the same key
that would be used when adding host via UI?

Any examples of how to use the HostDeployProtocol [1]?  I like the
idea of using registration but haven't the slightest idea how to
implement what's described in the docs [1].  I do recall seeing an
article posted (searching email and can't find) that had a nice
walk-through of how to use the oVirt API using browser tools.  I'm
unsure if this HostDeployProtocol would be done that way or via some
other method.

Thanks,
- Trey


[1] http://www.ovirt.org/Features/HostDeployProtocol

On Tue, Aug 5, 2014 at 3:01 PM, Alon Bar-Lev alo...@redhat.com wrote:


 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Alon Bar-Lev alo...@redhat.com
 Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian 
 Deutsch fabi...@redhat.com, Dan
 Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com, Douglas 
 Landgraf dougsl...@redhat.com, Oved
 Ourfali ov...@redhat.com
 Sent: Tuesday, August 5, 2014 10:45:12 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 Excellent, so installing 'ovirt-host-deploy' on each node then
 configuring the /etc/ovirt-host-deploy.conf.d files seems very
 automate-able, will see how it works in practice.

 you do not need to install the ovirt-host-deploy, just create the files.

 Regarding the actual host registration and getting the host added to
 ovirt-engine, are there other methods besides the API and the sdk?
 Would it be possible to configure the necessary
 ovirt-host-deploy.conf.d files then execute ovirt-host-deploy?  I
 notice that running 'ovirt-host-deploy' wants to make whatever host
 executes it a ovir hypervisor but haven't yet run it all the way
 through as no server to test with at this time.  There seems to be no
 --help or similar command line argument.

 you should not run host-deploy directly, but via the engine's process, either 
 registration or add host as I replied previously.

 when base system is ready, you issue add host via api of engine or via ui, 
 the other alternative is to register the host host the host-deploy protocol, 
 and approve the host via api of engine or via ui.

 I'm sure this will all be more clear once I attempt the steps and run
 through the motions.  Will try to find a system to test on so I'm
 ready once our new servers arrive.

 Thanks,
 - Trey

 On Tue, Aug 5, 2014 at 2:23 PM, Alon Bar-Lev alo...@redhat.com wrote:
 
 
  - Original Message -
  From: Trey Dockendorf treyd...@gmail.com
  To: Alon Bar-Lev alo...@redhat.com
  Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian
  Deutsch fabi...@redhat.com, Dan
  Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com,
  Douglas Landgraf dougsl...@redhat.com
  Sent: Tuesday, August 5, 2014 10:01:14 PM
  Subject: Re: [ovirt-users] Proper way to change and persist vdsm
  configuration options
 
  Ah, thank you for the input!  Just so I'm not spending time
  implementing the wrong changes, let me confirm I understand your
  comments.
 
  1) Deploy host with Foreman
  2) Apply Puppet catalog including ovirt Puppet module
  3) Initiate host-deploy via rest API
 
  In the ovirt module the following takes place:
 
  2a) Add yum repos
  2b) Manage  /etc/ovirt-host-deploy.conf.d/40-xxx.conf
 
 
  you can have any # of files with any prefix :))
 
  For #2b I have a few questions
 
  * The name of the .conf file is simply for sorting and
  labeling/organization, it has not functional impact on what those
  overrides apply to?
 
  right.
 
  * That file is managed on the ovirt-engine server, not the actual nodes?
 
  currently on the host, in future we will provide a method to add this to
  engine database[1]
 
  [1] http://gerrit.ovirt.org/#/c/27064/
 
  * Is there any way to apply overrides to specific hosts?  For example
  if I have some hosts that require a config and others that don't, how
  would I separate those *.conf files?  This is more theoretical as
  right now my setup is common across all nodes.
 
  the poppet module can put whatever required on each host.
 
  For #3...the implementation of API calls from within Puppet is a
  challenge and one I can't tackle yet, but definitely will make it a
  goal for the future.  In the mean time, what's the manual way to
  initiate host-deploy?  Is there a CLI command that would have the same
  result as an API call or is the recommended way to perform the API
  call manually (ie curl)?
 
  well, you can register host using the following protocol[1], but it is
  difficult to do this securely, what you actually need is to establish ssh
  trust for root with engine key then register.
 
  you can also use the register command using curl by something like (I have
  not checked):
  https://admin%40internal:password@engine/ovirt-engine/api/hosts
  ---
  ?xml version=1.0 encoding=UTF-8 standalone=yes?
  host

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-05 Thread Trey Dockendorf
On Tue, Aug 5, 2014 at 3:31 PM, Itamar Heim ih...@redhat.com wrote:
 On 08/05/2014 09:36 PM, Trey Dockendorf wrote:

 On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:

 Hey,

 Just noticed something that I forgot about..
 before filing new BZ, see in ovirt-host-deploy README.environment [1] the
 section:
 VDSM/configOverride(bool) [True]
  Override vdsm configuration file.

 changing it to false will keep your vdsm.conf file as is after deploying
 the
 host again (what happens after node upgrade)

 [1]
 https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment

 please check if that what you meant..

 Thanks,
 Yaniv Bronhaim.


 I was unaware of that package.  I will check that out as that seems to
 be what I am looking for.

 I have not filed this in BZ and will hold off pending
 ovirt-host-deploy.  If you feel a BZ is still necessary then please do
 file one and I would be happy to provide input if it would help.

 Right now this is my workflow.

 1. Foreman provisions bare-metal server with CentOS 6.5
 2. Once provisioned and system rebooted Puppet applies puppet-ovirt
 [1] module that adds the necessary yum repos, and installs packages.
 Part of my Puppet deployment is basic things like sudo management
 (vdsm's sudo is account for), sssd configuration, and other aspects
 that are needed by every system in my infrastructure.  Part of the
 ovirt::node Puppet class is managing vdsm.conf, and in my case that
 means ensuring iSER is enabled for iSCSI over IB.
 3. Once host is online and has had the full Puppet catalog applied I
 log into ovirt-engine web interface and add those host (pulling it's
 data via the Foreman provider).


 just wondering (and i may have missed this in the thread) - if you want bare
 metal provisioning and foreman, why not just use the new 3.5 integration
 doing that:
 http://www.ovirt.org/Features/AdvancedForemanIntegration

 it will call foreman, do bare metal provision with the hostgroup you chose,
 then foreman will call add host in the engine on your behalf?

 (doesn't limit you from either extending ovirt-host-deploy plugins, or using
 more puppet modules via the hostgroup).


I was actually looking forward to using those features but haven't yet
had a chance to test 3.5 as I have no spare hardware at the moment.
The Foreman Integration is definitely on my radar as we rely very
heavily on Foreman.

Thanks,
- Trey
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-04 Thread Trey Dockendorf
I'll file BZ.  As far as I can recall this has been an issue since 3.3.x as
I have been using Puppet to modify values and have had to rerun Puppet
after installing a node via GUI and when performing update from GUI.  Given
that it has occurred when VDSM version didn't change on the node it seems
likely to be something being done by Python code that bootstraps a node and
performs the other tasks.  I won't have any systems available to test with
for a few days.  New hardware specifically for our oVirt deployment is on
order so should be able to more thoroughly debug and capture logs at that
time.

Would using vdsm-reg be a better solution for adding new nodes?  I only
tried using vdsm-reg once and it went very poorly...lots of missing
dependencies not pulled in from yum install I had to install manually via
yum.  Then the node was auto added to newest cluster with no ability to
change the cluster.  Be happy to debug that too if there's some docs that
outline the expected behavior.

Using vdsm-reg or something similar seems like a better fit for puppet
deployed nodes, as opposed to requiring GUI steps to add the node.

Thanks
- Trey
On Aug 4, 2014 5:53 AM, ybronhei ybron...@redhat.com wrote:

 On 07/31/2014 01:28 AM, Trey Dockendorf wrote:

 I'm running ovirt nodes that are stock CentOS 6.5 systems with VDSM
 installed.  I am using iSER to do iSCSI over RDMA and to make that
 work I have to modify /etc/vdsm/vdsm.conf to include the following:

 [irs]
 iscsi_default_ifaces = iser,default

 I've noticed that any time I upgrade a node from the engine web
 interface that changes to vdsm.conf are wiped out.  I don't know if
 this is being done by the configuration code or by the vdsm package.
 Is there a more reliable way to ensure changes to vdsm.conf are NOT
 removed automatically?


 Hey,

 vdsm.conf shouldn't wiped out and shouldn't changed at all during upgrade.
 other related conf files (such as libvirtd.conf) might be overrided to keep
 defaults configurations for vdsm. but vdsm.conf should persist with user's
 modification. from my check, regular yum upgrade doesn't touch vdsm.conf

 Douglas can you verify that with node upgrade? might be specific to that
 flow..

 Trey, can file a bugzilla on that and describe your steps there?

 Thanks

 Yaniv Bronhaim,


 Thanks,
 - Trey
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users



 --
 Yaniv Bronhaim.

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


[ovirt-users] Proper way to change and persist vdsm configuration options

2014-07-30 Thread Trey Dockendorf
I'm running ovirt nodes that are stock CentOS 6.5 systems with VDSM
installed.  I am using iSER to do iSCSI over RDMA and to make that
work I have to modify /etc/vdsm/vdsm.conf to include the following:

[irs]
iscsi_default_ifaces = iser,default

I've noticed that any time I upgrade a node from the engine web
interface that changes to vdsm.conf are wiped out.  I don't know if
this is being done by the configuration code or by the vdsm package.
Is there a more reliable way to ensure changes to vdsm.conf are NOT
removed automatically?

Thanks,
- Trey
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ovirt-3.4.2 add host failed

2014-07-15 Thread Trey Dockendorf
Try yum downgrading 'python-pthreading'.  I had similar issue
yesterday and seeing others reporting the same.

- Trey

On Tue, Jul 15, 2014 at 2:51 AM, lofyer lof...@gmail.com wrote:
 I installed ovirt-3.4.2 on CentOS-6.5 from yum.
 While I was trying to add host, I got an error like this:

 Host IAM196 installation failed. Network error during communication with the
 host.

 Here's my log.

 ___
 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] IO errors when adding new disk on iSCSI storage

2014-05-15 Thread Trey Dockendorf
A colleague of mine has run into issues doing Linux (EL6.5) iSCSI over
bonded interfaces.  The solution he found was to abandon bonding and
instead use multiple interfaces and multipath on the iscsi initiators.  I
can't provide details yet as this is all second hand knowledge.  The errors
you posted are almost identical to what he faced.

- Trey
On May 13, 2014 3:10 AM, Morten A. Middelthon mor...@flipp.net wrote:

 Hi,

 I have a new oVirt setup which is giving me some headache. I have one
 administration server running on CentOS 6.5, and two hosts also running
 CentOS 6.5. Storage is running on both NFS and iSCSI, but iSCSI is the
 preferred storage, running on a HP LeftHand server.

 oVirt Engine Version: 3.4.0-1.el6

 Administration server and hosts are all updated with latest packages both
 for CentOS and oVirt.

 Both hosts are attached to a dedicated storage network with bonded
 interfaces:

 # ifconfig bond1
 bond1 Link encap:Ethernet  HWaddr AC:16:2D:8B:90:5E
   inet addr:192.168.40.160  Bcast:192.168.40.255 Mask:255.255.255.0
   inet6 addr: fe80::ae16:2dff:fe8b:905e/64 Scope:Link
   UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
   RX packets:4149464 errors:0 dropped:0 overruns:0 frame:0
   TX packets:5590278 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:5387975600 (5.0 GiB)  TX bytes:6981018034 (6.5 GiB)

 On the hosts the LUN is seen as:

 scsi3 : iSCSI Initiator over TCP/IP
  connection1:0: detected conn error (1020)
  scsi 3:0:0:0: Direct-Access LEFTHAND iSCSIDiska500 PQ: 0
 ANSI: 5
  sd 3:0:0:0: Attached scsi generic sg2 type 0
  sd 3:0:0:0: [sdb] 8589934592 512-byte logical blocks: (4.39 TB/4.00 TiB)
  sd 3:0:0:0: [sdb] Write Protect is off
  sd 3:0:0:0: [sdb] Mode Sense: 77 00 00 08
  sd 3:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't
 support DPO or FUA
   sdb: unknown partition table
   sd 3:0:0:0: [sdb] Attached SCSI disk

 The iSCSI LUN I'm using is 4TB large, with 2.5TB free, according to the
 oVirt admin interface:

 Size:   4095 GB
 Available:  2551 GB
 Used:   1544 GB
 Allocated:  1540 GB
 Over Allocation Ratio:  0%

 Over to the problem:

 On the virtual machine I'm testing on, I'm adding a new disk on the iSCSI
 storage server. The virtual machine is Debian 7.4 amd64. In this case 20GB
 large with thin provisioning. Then on the virtual machine I create a new
 logical volume group and disk:

 Create a new partition with type 8e (Linux LVM):
 fdisk /dev/vdc

 Setup LVM:
 pvcreate /dev/vdc1
 vgcreate VGTEST /dev/vdc1
 lvcreate -n lv_test -l 100%FREE VGTEST
 mkfs.ext4 /dev/mapper/VGTEST-lv_test
 mkdir /mnt/test
 mount /dev/mapper/VGTEST-lv_test /mnt/test

 Then I try writing to the new disk with f.ex dd:
 dd if=/dev/zero of=/mnt/test/storfil bs=64k count=20480

 Almost immediately oVirt will pause the machine with the following error
 message:

 VM INT-KVM-SSM02 has paused due to no Storage space error.

 dmesg on the virtual machine gives to following errors:

 [353290.564507] Buffer I/O error on device dm-7, logical block 294774
 [353290.564509] Buffer I/O error on device dm-7, logical block 294775
 [353290.564511] EXT4-fs warning (device dm-7): ext4_end_bio:250: I/O error
 writing to inode 12 (offset 1039114240 size 520192 starting block 294650)
 [353290.564514] end_request: I/O error, dev vdc, sector 2362304
 [353290.564516] Buffer I/O error on device dm-7, logical block 294776
 [353290.564518] Buffer I/O error on device dm-7, logical block 294777
 [353290.564519] Buffer I/O error on device dm-7, logical block 294778
 [353290.564521] Buffer I/O error on device dm-7, logical block 294779
 [353290.564522] Buffer I/O error on device dm-7, logical block 294780
 [353290.564524] Buffer I/O error on device dm-7, logical block 294781
 [353290.564525] Buffer I/O error on device dm-7, logical block 294782
 [353290.564744] Buffer I/O error on device dm-7, logical block 294910
 [353290.564746] Buffer I/O error on device dm-7, logical block 294911
 [353290.564748] EXT4-fs warning (device dm-7): ext4_end_bio:250: I/O error
 writing to inode 12 (offset 1040154624 size 32768 starting block 294904)
 [353291.035703] EXT4-fs (dm-7): This should not happen!! Data will be lost
 [353291.035705]
 [353291.036280] JBD2: Detected IO errors while flushing file data on dm-7-8
 [353291.036506] end_request: I/O error, dev vdc, sector 17043640
 [353291.036509] end_request: I/O error, dev vdc, sector 17043640
 [353291.036518] Aborting journal on device dm-7-8.
 [353291.036734] end_request: I/O error, dev vdc, sector 17043456
 [353291.036737] Buffer I/O error on device dm-7, logical block 2129920
 [353291.036739] lost page write due to I/O error on dm-7
 etc etc

 If I try to do large writes on the existing disk on either the iSCSI or
 NFS storage there are no problems at all.

 I have attached the engine.log from the administration server, and also
 the vdsm.log from 

[ovirt-users] Unable to edit virt-v2v import VM - 3.4.0

2014-04-15 Thread Trey Dockendorf
I just imported a VM using the following command:

virt-v2v -ic qemu+ssh://root@kvm1.DOMAIN/system -o rhev -os
192.168.202.245:/tank/ovirt/import_export --network ovirtmgmt --vmtype
server syslog.DOMAIN

I successfully imported it in the oVirt web UI, but when I try to edit
the VM I get the following message, Cannot edit VM. Cannot set single
display device via VNC display..

I noticed the Single PCI option in the Console section is checked,
when none of my other VMs have this checked.

Another VM I imported using version 3.3.x does not have this checked.

The checkbox is greyed out, so I can't make any modifications in the
Edit dialog.

Any suggestions?

For issues regarding importing from KVM using virt-v2v, what logs are
useful besides engine.log?

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


Re: [Users] proper way to move nfs data storage domain?

2014-03-20 Thread Trey Dockendorf
I believe for the iso/exports domain you can export them from the UI
Storage tab once they are detached from the data center, then import
them from new server.  Haven't tested this thoroughly, but before my
system was production I had to shift storage domains around due to
host renaming.

- Trey

On Thu, Mar 20, 2014 at 2:51 PM, David Smith dsm...@mypchelp.com wrote:
 apparently only the data domain path can be edited at this point.. different
 procedure for iso/exports?


 On Thu, Mar 20, 2014 at 12:49 PM, David Smith dsm...@mypchelp.com wrote:

 nevermind, it appears i've figured this out;
 shut down all VMs
 put the export and iso storage into maintenance mode
 put data domain into maintenance mode
 paths can be edited, in the system - storage tab
 reenable everything


 On Thu, Mar 20, 2014 at 12:21 PM, David Smith dsm...@mypchelp.com wrote:

 Two examples;

 1) I need to move the nfs data domain to a new server, whats the best
 way?

 2) I think this applies the same as above, if I need to rename the nfs
 server hostname, whats the best way?


 I managed to export/import the export and iso domains and have them up
 and running on the new server, however, since you can't import a data
 domain, i'm wondering whats the best method for this.

 thanks




 ___
 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: [Users] Snapshots not listed for VM using 3.3.4

2014-03-08 Thread Trey Dockendorf
On Sat, Mar 8, 2014 at 1:24 AM, Markus Stockhausen
stockhau...@collogia.de wrote:
 Von: users-boun...@ovirt.org [users-boun...@ovirt.org]quot; im Auftrag von 
 quot;Trey Dockendorf
 [treyd...@gmail.com]
 Gesendet: Freitag, 7. März 2014 23:23
 An: users
 Betreff: [Users] Snapshots not listed for VM using 3.3.4

 I have two VMs in my cluster, one is CentOS 6.5 and one is CentOS
 5.10.  I have updated qemu on the ovirt nodes to use the RPMs from
 http://jenkins.ovirt.org/view/Packaging/job/qemu-kvm-rhev_create_rpms_el6.

 # yum list installed | grep qemu
 gpxe-roms-qemu.noarch 0.9.7-6.10.el6@base
 qemu-img.x86_64   2:0.12.1.2-2.415.el6_5.4
 qemu-kvm.x86_64   2:0.12.1.2-2.415.el6_5.4
 qemu-kvm-tools.x86_64 2:0.12.1.2-2.415.el6_5.4

 I am able to perform a snapshot using the web UI, which succeeds, but
 the snapshot is never listed in the Snapshots tab for either VM.

 Maybe be only a temporary problem and a browser restart could help
 see https://bugzilla.redhat.com/show_bug.cgi?id=1058618


Opening in a new browser did the trick.  Thanks!

- Trey

 Running virsh -r snapshot-list domain for either VMs shows no snapshots.

 Attached is vdsm.log and engine.log (output when creating snapshot of
 EL6 VM) and vdsm2.log and engine2.log (output when creating snapshot
 of EL5 VM).

 Engine and nodes are updated to 3.3.4
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] eninge-cleanup left db non-empty (was: Downgrading to 3.3.3 after 3.4.0 beta 2 testing)

2014-02-18 Thread Trey Dockendorf
Submitted against 3.3.3, https://bugzilla.redhat.com/show_bug.cgi?id=1066654

I am in process of installing 3.4.0-betaN to see if this only effects 3.3.3.

- Trey

On Sun, Feb 16, 2014 at 5:01 AM, Yedidyah Bar David d...@redhat.com wrote:
 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Yedidyah Bar David d...@redhat.com
 Cc: users users@ovirt.org, infra in...@ovirt.org
 Sent: Thursday, February 13, 2014 7:36:52 PM
 Subject: Re: eninge-cleanup left db non-empty (was: [Users] Downgrading to 
 3.3.3 after 3.4.0 beta 2 testing)

 On Thu, Feb 13, 2014 at 1:55 AM, Yedidyah Bar David d...@redhat.com wrote:
  - Original Message -
  From: Yedidyah Bar David d...@redhat.com
  To: Trey Dockendorf treyd...@gmail.com
  Cc: users users@ovirt.org, in...@ovirt.org
  Sent: Thursday, February 13, 2014 8:32:01 AM
  Subject: eninge-cleanup left db non-empty (was: [Users] Downgrading to
  3.3.3 after 3.4.0 beta 2 testing)
 
  - Original Message -
   From: Trey Dockendorf treyd...@gmail.com
   To: users users@ovirt.org
   Sent: Wednesday, February 12, 2014 8:19:25 PM
   Subject: [Users] Downgrading to 3.3.3 after 3.4.0 beta 2 testing
   $ engine-cleanup
   $ engine-backup --mode=restore --scope=all
   --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log
   Restoring...
   FATAL: Database is not empty
  
   Attached are the two engine-cleanup logs from both attempts.  The
   first (from 20140211) was answering Yes only to remove Engine DB
   content.  The second (from 20140212, today) was Yes to remove all
   components.
 
  Apparently engine-cleanup does not clean up everything. We tried to
  make it do that, and I am pretty certain it used to at some point...
 
  1. You might want to open a bug about this. As you already posted,
  manually dropping and creating the database still works...
  2. Adding infra@ - I think we should add a jenkins job to verify
  that engine-cleanup cleans up at least the database, perhaps other
  things. I am pretty certain it should be so for 3.3, didn't check
  3.4 yet.
 
  Well, I now tried that with 3.4.0-beta2 and did not manage to reproduce -
  database was empty after engine-cleanup.
 
  If you manage to reproduce, please post the output of:
  pg_dump engine | grep -i ^create
  (as postgres, or passing credentials as needed).
  It should only output one line:
  CREATE EXTENSION IF NOT EXISTS plpgsql WITH SCHEMA pg_catalog;
 
  If it outputs anything else it's probably a bug.
 
  Thanks, FYI,
  --
  Didi

 With 3.3.3 I got this after engine-cleanup.

 (/root/pgpass was created by me mimicking what's created by engine-backup).

 $ PGPASSFILE=/root/pgpass pg_dump -U engine -h localhost -p 5432
 engine | grep -vi '^create extension' | grep -i '^create'
 CREATE PROCEDURAL LANGUAGE plpgsql;

 OK, makes (some?) sense...
 Eli - How come it does not always appear in pg_dump's outout? Is it because
 it's not always created, or not always output, or something else?


 The grep statements above mimic what was executed by the engine-backup
 which resulted in a message FATAL: Database is not empty.

 I will try and reproduce with 3.4.0-beta2.

 Should I file a bug for this issue against 3.3.x?

 Please do!

 Thanks for the report,
 --
 Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Host Non-Operational from sanlock and VM fails to migrate

2014-02-18 Thread Trey Dockendorf
Thanks for the thorough response!

 This looks like an error in the kernel. You should consult kernel/rpcrdma 
 folks with this error.

Mind pointing me in the direction of how to get in contact with the
appropriate mailing list to begin a dialog with the kernel/rpcrdma
folks?

Thanks
- Trey

On Wed, Feb 12, 2014 at 3:04 AM, Nir Soffer nsof...@redhat.com wrote:
 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Itamar Heim ih...@redhat.com
 Cc: users users@ovirt.org
 Sent: Monday, February 10, 2014 3:03:05 AM
 Subject: Re: [Users] Host Non-Operational from sanlock and VM fails to   
  migrate

 No, in fact I just had the issue arise again after trying to figure
 out what about my setup causes this crash.  So far it only seems to
 occur if both nodes are running NFS over RDMA, but I'm unsure if it's
 VM traffic or the host being SPM that causes it to misbehave.

 vm02 was running a single VM and was SPM.  The crash was on vm02
 Invalid status on Data Center Default.  Setting Data Center status to
 Non Responsive (On host vm02, Error: Network error during
 communication with the Host)..  SPM successfully switched to vm01 but
 the VM is stuck in migration and unresponsive.  Both engine and nodes
 using ovirt 3.3.3.

 vm01 and vm02 both have the following in vdsm.conf

 [addresses]
 management_port = 54321

 [vars]
 ssl = true


 [irs]
 nfs_mount_options = rdma,port=20049

 This is the ovirt NFS mount lines in /proc/mounts for each:

 vm01:

 192.168.211.245:/tank/ovirt/import_export
 /rhev/data-center/mnt/192.168.211.245:_tank_ovirt_import__export nfs
 rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=rdma,port=20049,timeo=600,retrans=2,sec=sys,mountaddr=192.168.211.245,mountvers=3,mountproto=tcp,local_lock=none,addr=192.168.211.245
 0 0
 192.168.211.245:/tank/ovirt/iso
 /rhev/data-center/mnt/192.168.211.245:_tank_ovirt_iso nfs
 rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=rdma,port=20049,timeo=600,retrans=2,sec=sys,mountaddr=192.168.211.245,mountvers=3,mountproto=tcp,local_lock=none,addr=192.168.211.245
 0 0
 192.168.211.245:/tank/ovirt/data
 /rhev/data-center/mnt/192.168.211.245:_tank_ovirt_data nfs
 rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=rdma,port=20049,timeo=600,retrans=2,sec=sys,mountaddr=192.168.211.245,mountvers=3,mountproto=tcp,local_lock=none,addr=192.168.211.245
 0 0

 vm02:

 192.168.211.245:/tank/ovirt/import_export
 /rhev/data-center/mnt/192.168.211.245:_tank_ovirt_import__export nfs
 rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=rdma,port=20049,timeo=600,retrans=2,sec=sys,mountaddr=192.168.211.245,mountvers=3,mountproto=tcp,local_lock=none,addr=192.168.211.245
 0 0
 192.168.211.245:/tank/ovirt/iso
 /rhev/data-center/mnt/192.168.211.245:_tank_ovirt_iso nfs
 rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=rdma,port=20049,timeo=600,retrans=2,sec=sys,mountaddr=192.168.211.245,mountvers=3,mountproto=tcp,local_lock=none,addr=192.168.211.245
 0 0
 192.168.211.245:/tank/ovirt/data
 /rhev/data-center/mnt/192.168.211.245:_tank_ovirt_data nfs
 rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=rdma,port=20049,timeo=600,retrans=2,sec=sys,mountaddr=192.168.211.245,mountvers=3,mountproto=tcp,local_lock=none,addr=192.168.211.245
 0 0

 The NFS server had these 2 log entries in /var/log/messages around the
 time vm02 went Non-operational.

 Feb  9 17:27:59 vmstore1 kernel: svcrdma: Error fast registering
 memory for xprt 882014683400
 Feb  9 17:28:21 vmstore1 kernel: svcrdma: Error fast registering
 memory for xprt 882025bf1400

 This looks like the root cause - failure on the storage server

 This leads to failure in the hosts connected to this storage:

 Feb  2 13:37:11 vm01 kernel: rpcrdma: connection to 192.168.211.245:20049 
 closed (-103)
 ...
 Feb  3 07:44:31 vm01 kernel: [ cut here ]
 Feb  3 07:44:31 vm01 kernel: WARNING: at kernel/softirq.c:159 
 local_bh_enable_ip+0x7d/0xb0() (Not tainted)
 Feb  3 07:44:31 vm01 kernel: Hardware name: H8DMT-IBX
 Feb  3 07:44:31 vm01 kernel: Modules linked in: ebt_arp xprtrdma nfs fscache 
 auth_rpcgss nfs_acl bonding ebtable_nat ebtables softdog lockd sunrpc 
 powernow_k8 freq_table mperf
 8021q garp bridge stp llc xt_physdev ipt_REJECT nf_conntrack_ipv4 
 nf_defrag_ipv4 xt_multiport iptable_filter ip_tables ip6t_REJECT 
 nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_
 conntrack ip6table_filter ip6_tables ib_ipoib rdma_ucm ib_ucm ib_uverbs 
 ib_umad rdma_cm ib_cm iw_cm ib_addr ipv6 dm_round_robin dm_multipath 
 vhost_net macvtap macvlan tun kvm_a
 md kvm microcode serio_raw k10temp amd64_edac_mod edac_core edac_mce_amd igb 
 dca i2c_algo_bit ptp pps_core mlx4_ib ib_sa ib_mad ib_core mlx4_en mlx4_core 
 sg i2c_nforce2 i2c_cor
 e ext4 jbd2 mbcache raid1 sd_mod crc_t10dif sata_nv ata_generic pata_acpi 
 pata_amd dm_mirror dm_region_hash dm_log dm_mod [last unloaded: 
 scsi_wait_scan]
 Feb  3 07:44:31

Re: [Users] eninge-cleanup left db non-empty (was: Downgrading to 3.3.3 after 3.4.0 beta 2 testing)

2014-02-18 Thread Trey Dockendorf
I just tried same steps with 3.4.0-beta2 and got same results.

Performed full 'engine-cleanup' and a engine-backup --mode=restore
failed with FATAL: Database is not empty

$ su - postgres -c pg_dump engine | grep -i ^create
CREATE PROCEDURAL LANGUAGE plpgsql;

After the failed restore the following two commands were enough to
allow restore to run.

$ su - postgres -c dropdb engine
$ su - postgres -c psql -c \create database engine owner engine
template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype
'en_US.UTF-8'\

- Trey


On Tue, Feb 18, 2014 at 2:32 PM, Trey Dockendorf treyd...@gmail.com wrote:
 Submitted against 3.3.3, https://bugzilla.redhat.com/show_bug.cgi?id=1066654

 I am in process of installing 3.4.0-betaN to see if this only effects 3.3.3.

 - Trey

 On Sun, Feb 16, 2014 at 5:01 AM, Yedidyah Bar David d...@redhat.com wrote:
 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Yedidyah Bar David d...@redhat.com
 Cc: users users@ovirt.org, infra in...@ovirt.org
 Sent: Thursday, February 13, 2014 7:36:52 PM
 Subject: Re: eninge-cleanup left db non-empty (was: [Users] Downgrading to 
 3.3.3 after 3.4.0 beta 2 testing)

 On Thu, Feb 13, 2014 at 1:55 AM, Yedidyah Bar David d...@redhat.com wrote:
  - Original Message -
  From: Yedidyah Bar David d...@redhat.com
  To: Trey Dockendorf treyd...@gmail.com
  Cc: users users@ovirt.org, in...@ovirt.org
  Sent: Thursday, February 13, 2014 8:32:01 AM
  Subject: eninge-cleanup left db non-empty (was: [Users] Downgrading to
  3.3.3 after 3.4.0 beta 2 testing)
 
  - Original Message -
   From: Trey Dockendorf treyd...@gmail.com
   To: users users@ovirt.org
   Sent: Wednesday, February 12, 2014 8:19:25 PM
   Subject: [Users] Downgrading to 3.3.3 after 3.4.0 beta 2 testing
   $ engine-cleanup
   $ engine-backup --mode=restore --scope=all
   --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log
   Restoring...
   FATAL: Database is not empty
  
   Attached are the two engine-cleanup logs from both attempts.  The
   first (from 20140211) was answering Yes only to remove Engine DB
   content.  The second (from 20140212, today) was Yes to remove all
   components.
 
  Apparently engine-cleanup does not clean up everything. We tried to
  make it do that, and I am pretty certain it used to at some point...
 
  1. You might want to open a bug about this. As you already posted,
  manually dropping and creating the database still works...
  2. Adding infra@ - I think we should add a jenkins job to verify
  that engine-cleanup cleans up at least the database, perhaps other
  things. I am pretty certain it should be so for 3.3, didn't check
  3.4 yet.
 
  Well, I now tried that with 3.4.0-beta2 and did not manage to reproduce -
  database was empty after engine-cleanup.
 
  If you manage to reproduce, please post the output of:
  pg_dump engine | grep -i ^create
  (as postgres, or passing credentials as needed).
  It should only output one line:
  CREATE EXTENSION IF NOT EXISTS plpgsql WITH SCHEMA pg_catalog;
 
  If it outputs anything else it's probably a bug.
 
  Thanks, FYI,
  --
  Didi

 With 3.3.3 I got this after engine-cleanup.

 (/root/pgpass was created by me mimicking what's created by engine-backup).

 $ PGPASSFILE=/root/pgpass pg_dump -U engine -h localhost -p 5432
 engine | grep -vi '^create extension' | grep -i '^create'
 CREATE PROCEDURAL LANGUAGE plpgsql;

 OK, makes (some?) sense...
 Eli - How come it does not always appear in pg_dump's outout? Is it because
 it's not always created, or not always output, or something else?


 The grep statements above mimic what was executed by the engine-backup
 which resulted in a message FATAL: Database is not empty.

 I will try and reproduce with 3.4.0-beta2.

 Should I file a bug for this issue against 3.3.x?

 Please do!

 Thanks for the report,
 --
 Didi
 ___
 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: [Users] engine-backup --restore

2014-02-13 Thread Trey Dockendorf
A wiki page is a good idea, glad the steps worked in more than my case.

- Trey

On Thu, Feb 13, 2014 at 9:37 AM, Juan Pablo Lorier jplor...@gmail.com wrote:
 Hi Trey,

 Following your procedure, I was able to get the engine running. THANKS A
 LOT TO EVERYONE!!
 If you allow me, I'll create a wiki page with this mentioning you so
 others can get this easily.
 Regards,

 On 12/02/14 17:32, Trey Dockendorf wrote:
 I was having the same issue (and posted about it today, with full
 steps).  I'd reply to my current post to list but I don't seem to
 receive my own posts.

 I have since taken these steps (as root)

 $ su - postgres -c dropdb engine
 $ su - postgres -c psql -c \create user engine password 'PASSWORD'\
 $ su - postgres -c psql -c \create database engine owner engine
 template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype
 'en_US.UTF-8'\
 $ engine-backup --mode=restore --scope=all
 --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log
 --change-db-credentials --db-host=localhost --db-port=5432
 --db-user=engine --db-name=engine --db-password=PASSWORD
 Restoring...
 Rewriting /etc/ovirt-engine/engine.conf.d/10-setup-database.conf
 Note: you might need to manually fix:
 - iptables/firewalld configuration
 - autostart of ovirt-engine service
 You can now start the engine service and then restart httpd
 Done.

 $ engine-setup

 I believe I initially created the database incorrectly (ran 'createdb
 engine' as postgres user).  I was getting errors during engine-setup
 that indicated the database could not be accessed.

 After the steps above, everything looks good.

 - Trey


 On Wed, Feb 12, 2014 at 1:10 PM, Juan Pablo Lorier jplor...@gmail.com 
 wrote:
 Well, too soon to say boodbye.
 Thought I used --change-db-credentials in the restore, the engine seems
 to be unable to connect to the database. I assume that it didn't get the
 new password, so, is there a way to tell the engine about the new password?
 Regards,

 On 12/02/14 16:03, Yedidyah Bar David wrote:
 - Original Message -
 From: Juan Pablo Lorier jplor...@gmail.com
 To: Yedidyah Bar David d...@redhat.com
 Cc: Sahina Bose sab...@redhat.com, users users@ovirt.org
 Sent: Wednesday, February 12, 2014 7:55:35 PM
 Subject: Re: [Users] Problems accesing the database

 Hi Yedidyah,

 But If I run engine-setup and then engine-backup restore shuldn't it
 import the data to the existing db created by engine-setup?
 That's shown everywhere so I thought it's a valid way to migrate
 No.

 There is a specific case in which this works automatically:
 All on the same host:
 1. engine-setup
 2. engine-backup --mode=backup
 (perhaps do other stuff here)
 3. engine-cleanup
 4. engine-backup --mode=restore

 Why does this work? Because 'engine-cleanup', since 3.3, does not drop
 the database nor user inside postgres. So when restore tries to access
 this database using this user and password it succeeds.

 In general, if you do the restore on another machine, and do there
 'engine-setup; engine-cleanup' as a quick-postgres-provisioning-tool,
 you end up almost ready, but not quite - because the password is random,
 and therefore different between the installations. In principle you could
 have provided just the password to restore, but we decided that if you
 need to change the credentials, you should pass all of them (except for
 defaults).

 Hope this clarifies,


 ___
 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: [Users] eninge-cleanup left db non-empty (was: Downgrading to 3.3.3 after 3.4.0 beta 2 testing)

2014-02-13 Thread Trey Dockendorf
On Thu, Feb 13, 2014 at 1:55 AM, Yedidyah Bar David d...@redhat.com wrote:
 - Original Message -
 From: Yedidyah Bar David d...@redhat.com
 To: Trey Dockendorf treyd...@gmail.com
 Cc: users users@ovirt.org, in...@ovirt.org
 Sent: Thursday, February 13, 2014 8:32:01 AM
 Subject: eninge-cleanup left db non-empty (was: [Users] Downgrading to 3.3.3 
 after 3.4.0 beta 2 testing)

 - Original Message -
  From: Trey Dockendorf treyd...@gmail.com
  To: users users@ovirt.org
  Sent: Wednesday, February 12, 2014 8:19:25 PM
  Subject: [Users] Downgrading to 3.3.3 after 3.4.0 beta 2 testing
  $ engine-cleanup
  $ engine-backup --mode=restore --scope=all
  --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log
  Restoring...
  FATAL: Database is not empty
 
  Attached are the two engine-cleanup logs from both attempts.  The
  first (from 20140211) was answering Yes only to remove Engine DB
  content.  The second (from 20140212, today) was Yes to remove all
  components.

 Apparently engine-cleanup does not clean up everything. We tried to
 make it do that, and I am pretty certain it used to at some point...

 1. You might want to open a bug about this. As you already posted,
 manually dropping and creating the database still works...
 2. Adding infra@ - I think we should add a jenkins job to verify
 that engine-cleanup cleans up at least the database, perhaps other
 things. I am pretty certain it should be so for 3.3, didn't check
 3.4 yet.

 Well, I now tried that with 3.4.0-beta2 and did not manage to reproduce -
 database was empty after engine-cleanup.

 If you manage to reproduce, please post the output of:
 pg_dump engine | grep -i ^create
 (as postgres, or passing credentials as needed).
 It should only output one line:
 CREATE EXTENSION IF NOT EXISTS plpgsql WITH SCHEMA pg_catalog;

 If it outputs anything else it's probably a bug.

 Thanks, FYI,
 --
 Didi

With 3.3.3 I got this after engine-cleanup.

(/root/pgpass was created by me mimicking what's created by engine-backup).

$ PGPASSFILE=/root/pgpass pg_dump -U engine -h localhost -p 5432
engine | grep -vi '^create extension' | grep -i '^create'
CREATE PROCEDURAL LANGUAGE plpgsql;

The grep statements above mimic what was executed by the engine-backup
which resulted in a message FATAL: Database is not empty.

I will try and reproduce with 3.4.0-beta2.

Should I file a bug for this issue against 3.3.x?

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


Re: [Users] engine-backup --restore

2014-02-12 Thread Trey Dockendorf
I was having the same issue (and posted about it today, with full
steps).  I'd reply to my current post to list but I don't seem to
receive my own posts.

I have since taken these steps (as root)

$ su - postgres -c dropdb engine
$ su - postgres -c psql -c \create user engine password 'PASSWORD'\
$ su - postgres -c psql -c \create database engine owner engine
template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype
'en_US.UTF-8'\
$ engine-backup --mode=restore --scope=all
--file=engine-20140211-1457.tar.bz2 --log=engine-backup.log
--change-db-credentials --db-host=localhost --db-port=5432
--db-user=engine --db-name=engine --db-password=PASSWORD
Restoring...
Rewriting /etc/ovirt-engine/engine.conf.d/10-setup-database.conf
Note: you might need to manually fix:
- iptables/firewalld configuration
- autostart of ovirt-engine service
You can now start the engine service and then restart httpd
Done.

$ engine-setup

I believe I initially created the database incorrectly (ran 'createdb
engine' as postgres user).  I was getting errors during engine-setup
that indicated the database could not be accessed.

After the steps above, everything looks good.

- Trey


On Wed, Feb 12, 2014 at 1:10 PM, Juan Pablo Lorier jplor...@gmail.com wrote:
 Well, too soon to say boodbye.
 Thought I used --change-db-credentials in the restore, the engine seems
 to be unable to connect to the database. I assume that it didn't get the
 new password, so, is there a way to tell the engine about the new password?
 Regards,

 On 12/02/14 16:03, Yedidyah Bar David wrote:
 - Original Message -
 From: Juan Pablo Lorier jplor...@gmail.com
 To: Yedidyah Bar David d...@redhat.com
 Cc: Sahina Bose sab...@redhat.com, users users@ovirt.org
 Sent: Wednesday, February 12, 2014 7:55:35 PM
 Subject: Re: [Users] Problems accesing the database

 Hi Yedidyah,

 But If I run engine-setup and then engine-backup restore shuldn't it
 import the data to the existing db created by engine-setup?
 That's shown everywhere so I thought it's a valid way to migrate
 No.

 There is a specific case in which this works automatically:
 All on the same host:
 1. engine-setup
 2. engine-backup --mode=backup
 (perhaps do other stuff here)
 3. engine-cleanup
 4. engine-backup --mode=restore

 Why does this work? Because 'engine-cleanup', since 3.3, does not drop
 the database nor user inside postgres. So when restore tries to access
 this database using this user and password it succeeds.

 In general, if you do the restore on another machine, and do there
 'engine-setup; engine-cleanup' as a quick-postgres-provisioning-tool,
 you end up almost ready, but not quite - because the password is random,
 and therefore different between the installations. In principle you could
 have provided just the password to restore, but we decided that if you
 need to change the credentials, you should pass all of them (except for
 defaults).

 Hope this clarifies,



 ___
 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: [Users] Mixing tagged and untagged VLANs

2014-02-05 Thread Trey Dockendorf
I attempted to set ovirtmgmt to untagged and making it a VM network
but that would not save.

The configuration:

ovirtmgmt:
 - Display Network
 - Migration Network
 - VM Network
 - NO VLAN

ipmi:
 - VM Network
 - VLAN 2

When I go into a host's Network Interfaces and attempt to sync the
removal of VLAN 1 from ovirtmgmt I get the following message:

Cannot setup Networks. The following Network Interfaces can have only
a single VM Logical Network, or at most one non-VM Logical Network
and/or several VLAN Logical Networks: eth0.

So simply having one untagged and the rest tagged doesn't work.  Is
that expected?

The use case here is simply to minimize cabling and hardware
requirements as our current hypervisors have two GbE interfaces and a
single IB interface.  Our connectivity requirements are to 3 networks,
public (direct connected to switches we have no control over for
campus) and private (internal LAN) and our dedicated IPMI /
Out-of-Band network (internal LAN).  To interface VMs with all 3
networks and only 2 uplinks we used a tagged VLAN on our primary
private network switch to link up our IPMI network as long as
interface is tagged VLAN 2.  The private continues to work as-is by
remaining untagged.

At the moment since the untagged ovirtmgmt + tagged ipmi logical
network isn't allowed in oVirt we've had to explicitly set VLAN 1
(private) to tagged for specific ports on our switch.  While this
isn't a huge issue, to us it's an unnecessary complication of
something that should work.  I'm able to achieve the desired
untagged + tagged setup using bridges in Linux when configured by
hand, so I know that it technically can be done.

Thanks
- Trey

On Tue, Feb 4, 2014 at 2:11 AM, Assaf Muller amul...@redhat.com wrote:
 Is it not possible to have multiple untagged VLAN networks associated
 to one interface in oVirt?

 No, not at this time.

 You can have one untagged network and N tagged networks on the same device,
 but only up to one untagged network.

 If you need multiple untagged networks on a single device then you're very
 welcome to report an RFE :)


 Assaf Muller, Cloud Networking Engineer
 Red Hat

 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: users users@ovirt.org
 Sent: Monday, February 3, 2014 10:45:44 PM
 Subject: [Users] Mixing tagged and untagged VLANs

 Using 3.3.2 I seem unable to mix tagged and untagged VLANs on a single
 interface.  I'm trying to put the following logical networks on a
 host's eth0.

 ovirtmgmt:
  - Display Network
  - Migration Network
  - NOT VM Network
  - NO VLAN

 private:
  - VM network
  - NO VLAN

 ipmi:
  - VM Network
  - VLAN 2

 In the host's network setup ovirtmgmt is already linked to eth0.  If I
 attach 'ipmi (VLAN 2)' then try and attach 'private' the message is
 Cannot have more than one non-VLAN network on one interface.  Same
 occurs if I try and attach 'private' when only 'ovirtmgmt' is assigned
 to eth0.

 Is it not possible to have multiple untagged VLAN networks associated
 to one interface in oVirt?

 Thanks
 - Trey
 ___
 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


[Users] Mixing tagged and untagged VLANs

2014-02-03 Thread Trey Dockendorf
Using 3.3.2 I seem unable to mix tagged and untagged VLANs on a single
interface.  I'm trying to put the following logical networks on a
host's eth0.

ovirtmgmt:
 - Display Network
 - Migration Network
 - NOT VM Network
 - NO VLAN

private:
 - VM network
 - NO VLAN

ipmi:
 - VM Network
 - VLAN 2

In the host's network setup ovirtmgmt is already linked to eth0.  If I
attach 'ipmi (VLAN 2)' then try and attach 'private' the message is
Cannot have more than one non-VLAN network on one interface.  Same
occurs if I try and attach 'private' when only 'ovirtmgmt' is assigned
to eth0.

Is it not possible to have multiple untagged VLAN networks associated
to one interface in oVirt?

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


Re: [Users] vdsm re setup?

2014-01-31 Thread Trey Dockendorf
I ran into same issue.  I'm setting up an ovirt module that has the sudoer
file for ovirt 3.3.2.  Are you using filebucket with puppet?  If so, try
restoring.

- Trey
On Jan 31, 2014 1:15 PM, Matt Warren mwar...@hnw.com wrote:

 I'm putting vdsm on a host that is also managed by puppet.
 I'm tracing some of my troubles to the fact that puppet stepped on some
 sudoers config done by vdsm.

 Is it possible to re-run the setup scripts for vdsm to regenerate the
 sudoers changes?
 ___
 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: [Users] vdsm re setup?

2014-01-31 Thread Trey Dockendorf
Matt,

I uploaded the puppet module I wrote for oVirt,
https://github.com/treydock/puppet-ovirt.  It's very in the very early
stages and lightly tested so use with caution.

- Trey

On Fri, Jan 31, 2014 at 1:15 PM, Matt Warren mwar...@hnw.com wrote:
 I'm putting vdsm on a host that is also managed by puppet.
 I'm tracing some of my troubles to the fact that puppet stepped on some 
 sudoers config done by vdsm.

 Is it possible to re-run the setup scripts for vdsm to regenerate the sudoers 
 changes?
 ___
 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: [Users] vdsm-python-cpopen is obsoleted by python-cpopen

2014-01-30 Thread Trey Dockendorf
Try manually installing python-cpopen on the node before adding node in the
engine.
On Jan 30, 2014 2:33 PM, Robert Story rst...@tislabs.com wrote:

 Hello,

 Any status on the pthon-cpopen obsoleted issue? Or any work-arounds? BZ is
 here: https://bugzilla.redhat.com/show_bug.cgi?id=1056470. I can't
 install add an el6 host to my cluster.. :-/

 -- Processing Dependency: vdsm-python-cpopen for package:
 vdsm-xmlrpc-4.13.3-2.el6.noarch
 Package vdsm-python-cpopen is obsoleted by python-cpopen, but obsoleting
 package does not provide for requirements
 -- Finished Dependency Resolution
 Error: Package: vdsm-xmlrpc-4.13.3-2.el6.noarch (ovirt-3.3.2)
Requires: vdsm-python-cpopen
Available: python-cpopen-1.3-1.el6.x86_64 (epel)
vdsm-python-cpopen = 4.13.2
Available: vdsm-python-cpopen-4.12.1-2.el6.i686 (ovirt-stable)
vdsm-python-cpopen = 4.12.1-2.el6
Available: vdsm-python-cpopen-4.12.1-4.el6.i686 (ovirt-stable)
vdsm-python-cpopen = 4.12.1-4.el6
Available: vdsm-python-cpopen-4.13.0-9.el6.i686 (ovirt-stable)
vdsm-python-cpopen = 4.13.0-9.el6
Available: vdsm-python-cpopen-4.13.0-11.el6.i686 (ovirt-stable)
vdsm-python-cpopen = 4.13.0-11.el6
Available: vdsm-python-cpopen-4.13.2-1.el6.i686 (ovirt-3.3.2)
vdsm-python-cpopen = 4.13.2-1.el6
Available: vdsm-python-cpopen-4.13.3-2.el6.i686 (ovirt-3.3.2)
vdsm-python-cpopen = 4.13.3-2.el6
  You could try using --skip-broken to work around the problem


 Robert

 --
 Senior Software Engineer @ Parsons

 ___
 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: [Users] Storage unresponsive after sanlock

2014-01-29 Thread Trey Dockendorf
On Wed, Jan 29, 2014 at 4:33 AM, Maor Lipchuk mlipc...@redhat.com wrote:
 The VDSM log seems to be from the 26th and from the engine logs it seems
 that the incident occurred at the 24th, so I can't really see the what
 happened in VDSM that time.

 From the engine logs it seems that at around 2014-01-24 16:59 the master
 storage domain was in maintenance and then there was an attempt to
 activate it, but VDSM threw an exception that it cannot find master
 domain with the arguments of
 spUUID=5849b030-626e-47cb-ad90-3ce782d831b3,
 msdUUID=7c49750d-7eae-4cd2-9b63-1dc71f357b88'

 This could be happen from various reasons, for example a failure in
 connecting the storage (for example see https://bugzilla.redhat.com/782864)


Some errors on my part that occurred before the sanlock issue were
having all the NFS exports with same fsid, as well as initial
failures to correctly pass custom NFS options to VDSM.  The sanlock
issue was not present as late as 18:00 on 2014-01-24 as I was still
working in the web interface at that time and saw no issues.

 Since you mentioned that once you have added a second node and it
 worked, it seems like to origin of the problem is in the Host it self.

 what are the differences between the two hosts (VDSM version, OS version)

There should be no differences.  They are identical hardware and
provisioned and configured using Puppet.

* vdsm-4.13.3-2.el6.x86_64
* OS is CentOS 6.5 - 2.6.32-431.3.1.el6.x86_64

 Does the first host succeeded to work on other DC?

I only have the default DC defined.  Would it be worth setting up
another DC for the sake of troubleshooting?

 Have you tried to reinstall it?

Not yet.  The install processes is automated as well as the
configuration, so whatever issues I'm running into SHOULD be present
upon re-install.  If there is a possibility a fresh install could
somehow fix this, I can re-provision.

I just noticed the 2nd host (vm02) added to the default cluster has
become Non Operational and the VM on that host failed to migrate to
the 1st host (vm01) which became SPM and is marked as Up.  The logs
on vm02 are full of sanlock messages.  What concerns me is the VM I
have running for testing is non responsive and vm01 shows messages
such as Time out during operation: cannot acquire state change lock.

I can't yet pinpoint when the failure occurred and to avoid sending 3
days worth of logs from 3 hosts I'll reset everything and try to
reproduce this with some monitoring to get a timestamp for approximate
time of failure.

Thanks
- Trey


 Regards,
 Maor




 On 01/29/2014 02:50 AM, Trey Dockendorf wrote:
 See attached.  The event seems to have begun around 06:00:00 on
 2014-01-26.  I was unable to get the single node cluster back online
 so I provisioned another node to add to the cluster, which became the
 SPM.  Adding the second node worked and I had to power cycle the node
 that hung as sanlock was in a zombie state.  This is my first attempt
 at production use of NFS over RDMA and I'd like to rule out that being
 the cause.  Since the issue I've changed the 'nfs_mount_options' in
 /etc/vdsm/vdsm.conf to 'soft,nosharecache,rdma,port=20049'.  The
 options during the crash were only 'rdma,port=20049'.  I am also
 forcing NFSv3 by setting 'Nfsvers=3' in /etc/nfsmount.conf, which is
 still in place and was in place during the crash.

 Thanks
 - Trey

 On Tue, Jan 28, 2014 at 2:45 AM, Maor Lipchuk mlipc...@redhat.com wrote:
 Hi Trey,

 Can you please also attach the engine/vdsm logs.

 Thanks,
 Maor

 On 01/27/2014 06:12 PM, Trey Dockendorf wrote:
 I setup my first oVirt instance since 3.0 a few days ago and it went
 very well, and I left the single host cluster running with 1 VM over
 the weekend.  Today I come back and the primary data storage is marked
 as unresponsive.  The logs are full of entries [1] that look very
 similar to a knowledge base article on RHEL's website [2].

 This setup is using NFS over RDMA and so far the ib interfaces report
 no errors (via `ibcheckerrs -v LID 1`).  Based on a doc on ovirt
 site [3] it seems this could be due to response problems.  The storage
 system is a new purchase and not yet in production so if there's any
 advice on how to track down the cause that would be very helpful.
 Please let me know what additional information would be helpful as
 it's been about a year since I've been active in the oVirt community.

 Thanks
 - Trey

 [1]: http://pastebin.com/yRpSLKxJ

 [2]: https://access.redhat.com/site/solutions/400463

 [3]: http://www.ovirt.org/SANLock
 ___
 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: [Users] Storage unresponsive after sanlock

2014-01-29 Thread Trey Dockendorf
On Wed, Jan 29, 2014 at 4:33 AM, Maor Lipchuk mlipc...@redhat.com wrote:
 The VDSM log seems to be from the 26th and from the engine logs it seems
 that the incident occurred at the 24th, so I can't really see the what
 happened in VDSM that time.

 From the engine logs it seems that at around 2014-01-24 16:59 the master
 storage domain was in maintenance and then there was an attempt to
 activate it, but VDSM threw an exception that it cannot find master
 domain with the arguments of
 spUUID=5849b030-626e-47cb-ad90-3ce782d831b3,
 msdUUID=7c49750d-7eae-4cd2-9b63-1dc71f357b88'


The actual error was higher in the logs after I tried activating this
host. Puppet had removed the unmanaged /etc/sudoers.d/50_vdsm file and
that was preventing vdsm from being able to execute any mount
commands.  The issues with vm02 are likely all due to that mistake on
my part.  My apologies.

- Trey

 This could be happen from various reasons, for example a failure in
 connecting the storage (for example see https://bugzilla.redhat.com/782864)

 Since you mentioned that once you have added a second node and it
 worked, it seems like to origin of the problem is in the Host it self.

 what are the differences between the two hosts (VDSM version, OS version)
 Does the first host succeeded to work on other DC?
 Have you tried to reinstall it?

 Regards,
 Maor




 On 01/29/2014 02:50 AM, Trey Dockendorf wrote:
 See attached.  The event seems to have begun around 06:00:00 on
 2014-01-26.  I was unable to get the single node cluster back online
 so I provisioned another node to add to the cluster, which became the
 SPM.  Adding the second node worked and I had to power cycle the node
 that hung as sanlock was in a zombie state.  This is my first attempt
 at production use of NFS over RDMA and I'd like to rule out that being
 the cause.  Since the issue I've changed the 'nfs_mount_options' in
 /etc/vdsm/vdsm.conf to 'soft,nosharecache,rdma,port=20049'.  The
 options during the crash were only 'rdma,port=20049'.  I am also
 forcing NFSv3 by setting 'Nfsvers=3' in /etc/nfsmount.conf, which is
 still in place and was in place during the crash.

 Thanks
 - Trey

 On Tue, Jan 28, 2014 at 2:45 AM, Maor Lipchuk mlipc...@redhat.com wrote:
 Hi Trey,

 Can you please also attach the engine/vdsm logs.

 Thanks,
 Maor

 On 01/27/2014 06:12 PM, Trey Dockendorf wrote:
 I setup my first oVirt instance since 3.0 a few days ago and it went
 very well, and I left the single host cluster running with 1 VM over
 the weekend.  Today I come back and the primary data storage is marked
 as unresponsive.  The logs are full of entries [1] that look very
 similar to a knowledge base article on RHEL's website [2].

 This setup is using NFS over RDMA and so far the ib interfaces report
 no errors (via `ibcheckerrs -v LID 1`).  Based on a doc on ovirt
 site [3] it seems this could be due to response problems.  The storage
 system is a new purchase and not yet in production so if there's any
 advice on how to track down the cause that would be very helpful.
 Please let me know what additional information would be helpful as
 it's been about a year since I've been active in the oVirt community.

 Thanks
 - Trey

 [1]: http://pastebin.com/yRpSLKxJ

 [2]: https://access.redhat.com/site/solutions/400463

 [3]: http://www.ovirt.org/SANLock
 ___
 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: [Users] ovirt-3.3.3 release postponed due to blockers

2014-01-28 Thread Trey Dockendorf
I found manually installing python-cpopen before adding a node in the
engine is a viable workaround. This was on EL6.5

- Trey
On Jan 28, 2014 7:57 AM, Sven Kieske s.kie...@mittwald.de wrote:

 Hi,

 and thanks for your fast reply.

 I know this does not fix it, but I'm preparing to
 deploy new hosts with EL6.5 and therefore need
 a workaround.

 I will try this out, thank you!

 Am 28.01.2014 14:48, schrieb Fabian Deutsch:
  Am Dienstag, den 28.01.2014, 14:44 +0100 schrieb Sandro Bonazzola:
 
  I already asked this in a different BZ, I think:
 
  Is the full blown host node install for EL6
  also affected?
 
  Fabian?
 
  Hey,
 
  well - I ran into this while building Node, but you should also run into
  this when installing e.g. vdsm on a full blown host. You can probably
  workaround this problem on a full blown host by excluding some packages.
  But that's just a workaround and doesn't solve the problem.
 
  - fabian
 

 --
 Mit freundlichen Grüßen / Regards

 Sven Kieske

 Systemadministrator
 Mittwald CM Service GmbH  Co. KG
 Königsberger Straße 6
 32339 Espelkamp
 T: +49-5772-293-100
 F: +49-5772-293-333
 https://www.mittwald.de
 Geschäftsführer: Robert Meyer
 St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
 Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
 ___
 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


[Users] Storage unresponsive after sanlock

2014-01-27 Thread Trey Dockendorf
I setup my first oVirt instance since 3.0 a few days ago and it went
very well, and I left the single host cluster running with 1 VM over
the weekend.  Today I come back and the primary data storage is marked
as unresponsive.  The logs are full of entries [1] that look very
similar to a knowledge base article on RHEL's website [2].

This setup is using NFS over RDMA and so far the ib interfaces report
no errors (via `ibcheckerrs -v LID 1`).  Based on a doc on ovirt
site [3] it seems this could be due to response problems.  The storage
system is a new purchase and not yet in production so if there's any
advice on how to track down the cause that would be very helpful.
Please let me know what additional information would be helpful as
it's been about a year since I've been active in the oVirt community.

Thanks
- Trey

[1]: http://pastebin.com/yRpSLKxJ

[2]: https://access.redhat.com/site/solutions/400463

[3]: http://www.ovirt.org/SANLock
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] What do you want to see in oVirt next?

2013-01-09 Thread Trey Dockendorf
On Jan 3, 2013 4:15 PM, Moran Goldboim mgold...@redhat.com wrote:

 On 01/03/2013 07:42 PM, Darrell Budic wrote:


 On Jan 3, 2013, at 10:25 AM, Patrick Hurrelmann wrote:

 On 03.01.2013 17:08, Itamar Heim wrote:

 Hi Everyone,


 as we wrap oVirt 3.2, I wanted to check with oVirt users on what they

 find good/useful in oVirt, and what they would like to see

 improved/added in coming versions?


 Thanks,

Itamar


 For me, I'd like to see official rpms for RHEL6/CentOS6. According to
 the traffic on this list quite a lot are using Dreyou's packages.


 I'm going to second this strongly! Official support would be very much
appreciated. Bonus points for supporting a migration from the dreyou
packages. No offense to dreyou, of course, just rather be better supported
by the official line on Centos 6.x.


 EL6 rpms are planned to be delivered with 3.2 GA version, and nightly
builds from there on.
 hopefully we can push it to 3.2 beta.

 Moran.



 Better support/integration of windows based SPICE clients would also be
much appreciated, I have many end users on Windows, and it's been a chore
to keep it working so far. This includes the client drivers for windows VMs
to support the SPICE display for multiple displays. More of a client side
thing, I know, but a desired feature in my environment.

 Thanks for the continued progress and support as well!

 -
 Darrell Budic
 Zenfire







 ___
 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


Will the EL6 releases also include an EL6 version of ovirt-node?  If not
will the build dependencies for ovirt node be available to allow for custom
node iso builds?

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


Re: [Users] New website live! Feedback welcome

2012-12-01 Thread Trey Dockendorf
On Fri, Nov 30, 2012 at 6:18 AM, Dave Neary dne...@redhat.com wrote:
 Hi everyone,

 The new oVirt website is now live!

   http://www.ovirt.org

 We have made some changes to the infrastructure (the website is now running
 on MediaWiki: http://www.mediawiki.org on Red Hat's Platform as a Service
 offering OpenShift: https://openshift.redhat.com) and also to the look and
 feel. There is a new theme, designed and laid out by Garrett Lesage, some
 new content to discover, and best of all, since the entire website is now a
 wiki, it will be much easier to maintain over time.

 We have been careful to ensure that all of the old website links redirect to
 appropriate pages on the new site. If you find any dead links, or redirects
 which do not make sense, please let us know! And as the site has had limited
 exposure up to this point, we are happy to hear your feedback on things you
 like, and things we can improve.

 Thank you all for your support, assistance and understanding throughout this
 process!

 Regards,
 Dave.

 --
 Dave Neary - Community Action and Impact
 Open Source and Standards, Red Hat - http://community.redhat.com
 Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


The site looks amazing!  I'm a huge fan of Mediawiki, but have yet to
see a site with that design / layout.  Would you mind enlightening me
as to what was used to produce a site that looks little like a typical
Mediawiki instance?

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


Re: [Users] Migrating from KVM to oVirt 3.1 fails - corrupt OVF

2012-08-11 Thread Trey Dockendorf
On Sun, Jul 22, 2012 at 3:20 PM, Ayal Baron aba...@redhat.com wrote:
 SNIP

 
  Would a qcow2 image with preallocation=metadata be possible on an
  iSCSI data store?
  ayal?
 
  nope.  metadata preallocation means that each logical block has a
  corresponding physical block.
 Ayal, by saying logical block and physical block here,  what do
 they
 stand for in linux systems?  I guess, physical block is the scsi lun
 disk, logical block is lvm disk? right?

 No, guest writing to block X, qcow maps X to Y on underlying device (e.g. LV)
 X is logical in example above.
 Y is 'physical'

 *Warning*, following explanation is a bit convoluted ;)

 Metadata preallocation means that all qcow clusters are already preset with 
 every X mapped to a Y.
 Now on block storage, if guest writes to an X where X is mapped to Y which is 
 beyond device size (because it's thinly provisioned), we would need to extend 
 device to at least Y if not beyond.
 Worst case is if the guest I/O is to a block which is mapped to offset = size 
 of virtual disk, which would force us to preallocate the entire disk at this 
 point for a single block.



  With files this is fine as you can seek wherever you want and the
  file will remain sparse.  With block devices this makes little
  sense as the second the guest accesses a block which is mapped to
  an unallocated physical block we'd have to allocate all the area
  up to that point.
  (btw, qemu-img will fail if you try to create such an image on a
  block device)
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 


 --
 Shu Ming shum...@linux.vnet.ibm.com
 IBM China Systems and Technology Laboratory



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


Wanted to followup on this previous issue and report that after
upgrading to the stable release of 3.1, the import works.  What's
strange, is the latest attempt was using latest virt-v2v in EL6,
virt-v2v-0.8.7-6 , and when I went into the storage domain to view the
Imports it showed one of my past imports in the list that had failed
previously.  However it was fixed, it now works!

For all those wondering what steps I took to import a KVM VM into oVirt...

# virsh dumpxml dh-imager01  dh-imager01.xml
(No editing of XML required now)
# virt-v2v -b ovirtmgmt -i libvirtxml -o rhev -os
dc-engine.tamu.edu:/exportdomain dh-imager01.xml

* From in the Engine Web interface go to the Export Domain's entry
under Storage Tab
* Select the VM Import tab
* Restore imported VM


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


Re: [Users] Issue setting IP information for Non-VM networks

2012-08-09 Thread Trey Dockendorf
On Thu, Aug 9, 2012 at 3:19 AM, Igor Lvovsky ilvov...@redhat.com wrote:


 - Original Message -
 From: Mark Wu wu...@linux.vnet.ibm.com
 To: Trey Dockendorf treyd...@gmail.com
 Cc: users users@ovirt.org, ilvov...@redhat.com
 Sent: Thursday, August 9, 2012 10:44:42 AM
 Subject: Re: [Users] Issue setting IP information for Non-VM networks

 On 08/09/2012 01:25 AM, Trey Dockendorf wrote:

 A few weeks back I started a discussion about my issues with
 IP/Netmask not being set on networks that weren't enabled for VM use.
 The bug is here, https://bugzilla.redhat.com/show_bug.cgi?id=834205 .

 I've since upgrade to latest ovirt / vdsm and while the issue seems
 to
 be resolved it's now failing in a different way.  Looking at the logs
 , it looks like the correct parameters are being passed to vdsm but
 the ifcfg-eth* is still left with no IPADDR or NETMASK values.

 Attached are logs from when Assigning a Static IP to both eth0 /
 ovirtmgmt and eth1/stor0.

 CentOS 6.3 on the Engine host with the following versions
 ovirt-engine-cli-3.1.0.2-1alpha.el6.noarch
 ovirt-engine-webadmin-portal-3.1.0-3.16.el6.noarch
 ovirt-engine-notification-service-3.1.0-3.16.el6.noarch
 ovirt-iso-uploader-3.1.0-16.el6.noarch
 ovirt-engine-sdk-3.1.0.1-1alpha.el6.noarch
 ovirt-engine-restapi-3.1.0-3.16.el6.noarch
 ovirt-engine-backend-3.1.0-3.16.el6.noarch
 ovirt-engine-userportal-3.1.0-3.16.el6.noarch
 ovirt-engine-tools-common-3.1.0-3.16.el6.noarch
 ovirt-engine-dbscripts-3.1.0-3.16.el6.noarch
 ovirt-engine-3.1.0-3.16.el6.noarch
 ovirt-log-collector-3.1.0-16.el6.noarch
 ovirt-engine-jbossas711-1-0.x86_64
 ovirt-engine-setup-3.1.0-3.16.el6.noarch
 ovirt-engine-config-3.1.0-3.16.el6.noarch
 ovirt-engine-genericapi-3.1.0-3.16.el6.noarch
 ovirt-image-uploader-3.1.0-16.el6.noarch

 CentOS 6.3 on the Node with the following versions
 vdsm-xmlrpc-4.10.0-0.42.12.el6.noarch
 vdsm-python-4.10.0-0.42.12.el6.x86_64
 vdsm-cli-4.10.0-0.42.12.el6.noarch
 vdsm-hook-simpleqemu-0.1-1.el6.noarch
 vdsm-4.10.0-0.42.12.el6.x86_64

 After performing the change in the web interface, this is ifcfg-eth1
 (missing IPADDR and NETMASK)
 # cat ifcfg-eth1
 DEVICE=eth1
 ONBOOT=yes
 BOOTPROTO=none
 HWADDR=00:25:90:4c:91:bf
 NM_CONTROLLED=no
 MTU=9000 I can reproduce this problem with vdsm-4.10.0-6.fc17.x86_64.
 It turns out the fix for bz834205 is not backported to oVirt 3.1
 branch.
 Igor, do you think it should be backported?

 Unfortunately, we are not support non-VM networks for oVirt 3.1 release
 This is exactly a reason why we didn't backport it yet.



 I've also run into an issue where in the web interface, the ovirtmgmt
 network always reverts back to DHCP as the boot protocol.  The ifcfg
 on node will reflect the correct setting after I change to static,
 but
 if I go to re-edit the entry, it's back on DHCP. I hit this problem
 before, and filed a bug for it:
 https://bugzilla.redhat.com/show_bug.cgi?id=838816

 Thanks
 - Trey

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


Thanks for the info.  I guess for now the simple solution is to make
all logical networks VM capable.

The version latest was refering the latest in the Dreyou repo, which I
believe is at 3.1.  I'm rebuilding the official 3.1 RPMs right now for
CentOS as I don't think they've made it to Dreyou yet.

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


[Users] Issue setting IP information for Non-VM networks

2012-08-08 Thread Trey Dockendorf
A few weeks back I started a discussion about my issues with
IP/Netmask not being set on networks that weren't enabled for VM use.
The bug is here, https://bugzilla.redhat.com/show_bug.cgi?id=834205.

I've since upgrade to latest ovirt / vdsm and while the issue seems to
be resolved it's now failing in a different way.  Looking at the logs
, it looks like the correct parameters are being passed to vdsm but
the ifcfg-eth* is still left with no IPADDR or NETMASK values.

Attached are logs from when Assigning a Static IP to both eth0 /
ovirtmgmt and eth1/stor0.

CentOS 6.3 on the Engine host with the following versions
ovirt-engine-cli-3.1.0.2-1alpha.el6.noarch
ovirt-engine-webadmin-portal-3.1.0-3.16.el6.noarch
ovirt-engine-notification-service-3.1.0-3.16.el6.noarch
ovirt-iso-uploader-3.1.0-16.el6.noarch
ovirt-engine-sdk-3.1.0.1-1alpha.el6.noarch
ovirt-engine-restapi-3.1.0-3.16.el6.noarch
ovirt-engine-backend-3.1.0-3.16.el6.noarch
ovirt-engine-userportal-3.1.0-3.16.el6.noarch
ovirt-engine-tools-common-3.1.0-3.16.el6.noarch
ovirt-engine-dbscripts-3.1.0-3.16.el6.noarch
ovirt-engine-3.1.0-3.16.el6.noarch
ovirt-log-collector-3.1.0-16.el6.noarch
ovirt-engine-jbossas711-1-0.x86_64
ovirt-engine-setup-3.1.0-3.16.el6.noarch
ovirt-engine-config-3.1.0-3.16.el6.noarch
ovirt-engine-genericapi-3.1.0-3.16.el6.noarch
ovirt-image-uploader-3.1.0-16.el6.noarch

CentOS 6.3 on the Node with the following versions
vdsm-xmlrpc-4.10.0-0.42.12.el6.noarch
vdsm-python-4.10.0-0.42.12.el6.x86_64
vdsm-cli-4.10.0-0.42.12.el6.noarch
vdsm-hook-simpleqemu-0.1-1.el6.noarch
vdsm-4.10.0-0.42.12.el6.x86_64

After performing the change in the web interface, this is ifcfg-eth1
(missing IPADDR and NETMASK)
# cat ifcfg-eth1
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=none
HWADDR=00:25:90:4c:91:bf
NM_CONTROLLED=no
MTU=9000

I've also run into an issue where in the web interface, the ovirtmgmt
network always reverts back to DHCP as the boot protocol.  The ifcfg
on node will reflect the correct setting after I change to static, but
if I go to re-edit the entry, it's back on DHCP.

Thanks
- Trey


vdsm_add_non_vm_network.log
Description: Binary data


engine_add_non_vm_network.log
Description: Binary data
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Migrating from KVM to oVirt 3.1 fails - corrupt OVF

2012-07-20 Thread Trey Dockendorf
On Fri, Jul 20, 2012 at 3:52 AM, Itamar Heim ih...@redhat.com wrote:
 On 07/20/2012 02:08 AM, Trey Dockendorf wrote:

 On Thu, Jul 19, 2012 at 4:00 AM, Matthew Booth mbo...@redhat.com wrote:

 On 18/07/12 23:52, Itamar Heim wrote:


 On 07/18/2012 06:00 PM, Trey Dockendorf wrote:


 I'm attempting to fine-tune the process of getting my KVM/Libvirt
 managed VMs over into my new oVirt infrastructure, and the virt-v2v
 import is failing in the WUI with Failed to read VM 'dh-imager01'
 OVF, it may be corrupted.  I've attached both engine and vdsm logs
 that are a snapshot from when I ran the virt-v2v command until I saw
 the failure under Events.



 matt - any thoughts?



 Nothing springs to mind immediately, but it sounds like v2v is producing
 an
 invalid OVF. If somebody can diagnose what the problem with the OVF is I
 can
 fix v2v.

 Matt




 virt-v2v command used...

 # virt-v2v -i libvirtxml -o rhev -os
 dc-vmarchitect.tamu.edu:/exportdomain dh-imager01.xml
 dh-imager01_sys.qcow2: 100%


 [===]D

 0h00m37s
 virt-v2v: dh-imager01 configured with virtio drivers.

 The xml has been modified numerous times based on past mailing list
 comments to have VNC and Network information removed, but still the
 same failure.  I've attached the latest XML that was used in the log's
 failure as dh-imager01.xml.  I've also tried passing hte bridge device
 (ovirtmgmt) in the above command with same failure results.

 Node and Engine are both CentOS 6.2, with vdsm-4.10.0-4 and
 ovirt-engine-3.1 respectively.

 Please let me know what other configuration information could be
 helpful to debug / troubleshoot this.

 Are there any other methods besides a virt-v2v migration that can
 allow me to use my previous KVM VMs within oVirt?


 Thanks
 - Trey



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





 --
 Matthew Booth, RHCA, RHCSS
 Red Hat Engineering, Virtualisation Team

 GPG ID:  D33C3490
 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490



 Attached is the virt-v2v generated ovf that's in my NFS export domain

 Any other means to get KVM/libvirt/virt-manager based VMs into oVirt?
 Possibly something as crude as provisioning new VMs with oVirt then
 replacing the virtual hard drives?


 this would work - just create the VM on an NFS storage domain with a disk
 the same size as origin, and copy over the disk you had.
 a bit trickier for iscsi, so i'd do this with nfs.

 Thanks
 - Trey




Why is it trickier with iSCSI?  Currently the only Data Center I have
functioning in oVirt only has iSCSI storage available.

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


Re: [Users] Migrating from KVM to oVirt 3.1 fails - corrupt OVF

2012-07-20 Thread Trey Dockendorf
On Fri, Jul 20, 2012 at 11:32 AM, Itamar Heim ih...@redhat.com wrote:
 On 07/20/2012 07:21 PM, Trey Dockendorf wrote:

 On Fri, Jul 20, 2012 at 3:52 AM, Itamar Heim ih...@redhat.com wrote:

 On 07/20/2012 02:08 AM, Trey Dockendorf wrote:


 On Thu, Jul 19, 2012 at 4:00 AM, Matthew Booth mbo...@redhat.com
 wrote:


 On 18/07/12 23:52, Itamar Heim wrote:



 On 07/18/2012 06:00 PM, Trey Dockendorf wrote:



 I'm attempting to fine-tune the process of getting my KVM/Libvirt
 managed VMs over into my new oVirt infrastructure, and the virt-v2v
 import is failing in the WUI with Failed to read VM 'dh-imager01'
 OVF, it may be corrupted.  I've attached both engine and vdsm logs
 that are a snapshot from when I ran the virt-v2v command until I saw
 the failure under Events.




 matt - any thoughts?




 Nothing springs to mind immediately, but it sounds like v2v is
 producing
 an
 invalid OVF. If somebody can diagnose what the problem with the OVF is
 I
 can
 fix v2v.

 Matt




 virt-v2v command used...

 # virt-v2v -i libvirtxml -o rhev -os
 dc-vmarchitect.tamu.edu:/exportdomain dh-imager01.xml
 dh-imager01_sys.qcow2: 100%



 [===]D

 0h00m37s
 virt-v2v: dh-imager01 configured with virtio drivers.

 The xml has been modified numerous times based on past mailing list
 comments to have VNC and Network information removed, but still the
 same failure.  I've attached the latest XML that was used in the
 log's
 failure as dh-imager01.xml.  I've also tried passing hte bridge
 device
 (ovirtmgmt) in the above command with same failure results.

 Node and Engine are both CentOS 6.2, with vdsm-4.10.0-4 and
 ovirt-engine-3.1 respectively.

 Please let me know what other configuration information could be
 helpful to debug / troubleshoot this.

 Are there any other methods besides a virt-v2v migration that can
 allow me to use my previous KVM VMs within oVirt?


 Thanks
 - Trey



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





 --
 Matthew Booth, RHCA, RHCSS
 Red Hat Engineering, Virtualisation Team

 GPG ID:  D33C3490
 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490



 Attached is the virt-v2v generated ovf that's in my NFS export domain

 Any other means to get KVM/libvirt/virt-manager based VMs into oVirt?
 Possibly something as crude as provisioning new VMs with oVirt then
 replacing the virtual hard drives?


 this would work - just create the VM on an NFS storage domain with a disk
 the same size as origin, and copy over the disk you had.
 a bit trickier for iscsi, so i'd do this with nfs.

 Thanks
 - Trey




 Why is it trickier with iSCSI?  Currently the only Data Center I have
 functioning in oVirt only has iSCSI storage available.


 with iscsi, you will have to create the disks as pre-allocated, and use DD
 to overwrite them.
 NFS doesn't have to be pre-allocated.
 and since you are using pre-allocated, you need to use the RAW format iirc



Currently most of my KVM VMs are qcow2, so converting them to raw
would not be a problem.  However, why is DD necessary?  Why can't I
overwrite the image_name.img with my *.img file ?  Since I've used
mostly qcow2 in my time with KVM/libvirt I may lack some understanding
of how to correctly handle raw images.

Would a qcow2 image with preallocation=metadata be possible on an
iSCSI data store?

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


Re: [Users] iSCSI discovery not showing all LUNs - oVirt 3.1

2012-07-06 Thread Trey Dockendorf
On Fri, Jul 6, 2012 at 8:07 AM, Itamar Heim ih...@redhat.com wrote:
 On 07/05/2012 06:08 PM, Trey Dockendorf wrote:

 I have a Promise M300i iSCSI with 2 LUNs.  A 2TB LUN with ID
 2260-0001-557c-af0a and a 4TB LUN with ID 22d9-0001-553e-4d6a.

 What's strange, is the very first time I ran discovery I saw both
 LUNs.  I checked the 2TB LUN and storage failed to add, I don't have
 logs at this time, but I went back to repeat the process and now only
 1 LUN shows in the GUI (see attached image).  Also the size it reports
 is way off.

 Looking at VDSM logs, I get this output when doing the login to a target

 {'devList':
[
  {'vendorID': 'Promise',
   'capacity': '2188028149760',
   'fwrev': '0227',
   'partitioned': False,
   'vgUUID': 'AZ1iMt-gzBD-2uug-xTih-1z0b-PqPy-xSP0A4',
   'pathlist': [
 {
   'initiatorname': 'default',
   'connection': '192.168.203.100',
   'iqn': 'iqn.1994-12.com.promise.xxx',
   'portal': '1',
   'password': '**',
   'port': '3260'
 }
],
'logicalblocksize': '512',
'pathstatus': [
 {
   'physdev': 'sde',
   'type': 'iSCSI',
   'state': 'active',
   'lun': '0'
 }
],
'devtype': 'iSCSI',
'physicalblocksize': '512',
'pvUUID': 'v2N3ok-wrki-OQQn-1XFL-w69n-8wAF-rmCFWt',
'serial':
 'SPromise_VTrak_M300i_F08989F89FFF6C42',
'GUID': '22261557caf0a',
'productID': 'VTrak M300i'
  },
  {
'vendorID': 'Promise',
'capacity': '20246190096384',
'fwrev': '0227',
'partitioned': False,
'vgUUID': '',
'pathlist': [
 {
   'initiatorname': 'default',
   'connection': '192.168.203.100',
   'iqn': 'iqn.1994-12.com.promise.xxx',
   'portal': '1',
   'password': '**',
   'port': '3260'
 }
],
'logicalblocksize': '2048',
'pathstatus': [
 {
   'physdev': 'sdf',
   'type': 'iSCSI',
   'state': 'active',
   'lun': '1'
 }
],
'devtype': 'iSCSI',
'physicalblocksize': '2048',
'pvUUID': '',
'serial':
 'SPromise_VTrak_M300i_DA3FF8D8099662D7',
'GUID': '222d90001553e4d6a',
'productID': 'VTrak M300i'
  }
]
 }

 In that output both LUNs are seen.  I couldn't tell from the code what
 format the capacity is in, but now the interface shows only the LUN
 with the 4d6a GUID as being 18TB.

 I've attached the VDSM Logs from the point of selecting my datacenter
 to after clicking Login.  Any suggestions?

 node - vdsm-4.10.0-2.el6.x86_64

 Thanks
 - Trey



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


 the LUN you don't see is 'dirty' and vdsm filters it.
 there are some patches for showing all LUNs and just graying them out at ui
 level (but these are post ovirt 3.1.
 dd with zeros the start of your LUN should bring it back


I re-initialized the RAID array, and attempted adding the storage
domain that resulted in failure again.  This is the error in Web
interface

Error: Cannot attach Storage. Storage Domain doesn't exist.

I've attached log vdsm that is a snapshot from the time right before
clicking Ok and the error.  ovirt-engine is 3.1 and vdsm is
4.10.0-4.  Both engine and node are CentOS 6.2

I attempted to run the failing command manually

# /sbin/lvm pvcreate --config  devices { preferred_names =
[\^/dev/mapper/\] ignore_suspended_devices=1 write_cache_state=0
disable_after_error_count=3 filter = [
\a%1ATA_ST32000644NS_9WM7SV9Y|1ATA_ST32000644NS_9WM7ZXVC|22261557caf0a%\,
\r%.*%\ ] }  global {  locking_type=1  prioritise_write_locks=1
wait_for_locks=1 }  backup {  retain_min = 50  retain_days = 0 } 
--metadatasize 128m --metadatacopies 2 --metadataignore y
/dev/mapper/22261557caf0a

Can't open /dev/mapper/22261557caf0a exclusively.  Mounted filesystem?

What's strange is fuser shows nothing using that path, or the
/dev/dm-4 path it's referencing.  However the device created in dmesg
(/dev/sde) does show usage

# ls -la /dev/mapper/
total 0
drwxr-xr-x.  2 root root180 Jul  6 15:23 .
drwxr-xr-x. 20 root root   4020 Jul  6 15:27 ..
lrwxrwxrwx.  1 root root  7 Jul  6 15:12
1ATA_ST32000644NS_9WM7SV9Y - ../dm-2
lrwxrwxrwx.  1 root root  7 Jul  6 15:12
1ATA_ST32000644NS_9WM7ZXVC - ../dm-3
lrwxrwxrwx.  1 root root  7 Jul  6 15:27 22261557caf0a - ../dm-4
crw-rw.  1 root root 10, 58 Jul  6 15:11 control
lrwxrwxrwx.  1 root root  7 Jul  6 15:23
ef7e7c07--f144--4843--8526--4afd0ec33368-metadata - ../dm-5
lrwxrwxrwx.  1 root root  7 Jul  6 15:11 vg_dhv01-lv_root - ../dm-1
lrwxrwxrwx.  1 root root  7 Jul  6 15:11 vg_dhv01-lv_swap - ../dm-0
[root@dhv01 ~]# fuser /dev/mapper

Re: [Users] What is it going to take to get EL6 builds?

2012-07-05 Thread Trey Dockendorf
On Jul 5, 2012 5:05 PM, Robert Middleswarth rob...@middleswarth.net
wrote:

 I know there are a few things that don't work under oVirt on EL6 but
there are unofficial builds out there and they seem to work pretty well.

 What is the major stopper from getting EL6 builds?  Is it just a mater of
getting patches submitted for building the spec files?  Is there a need for
EL 6 based slaves?  Is there a concern about the features that don't work
like Live Migration?

 I guess a good starting point is to build a todo list of what has to be
done.

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

Based on personal attempts to rebuild ovirt for EL6 the biggest hurdle I
ran into is build dependencies.

Thanks to the help of Dreyou Im using the work around of a binary download
of Maven and packages from jpackage repo.  Ive built latest vdsm without
much issue and am setting up my mock environment to rebuild the latest
ovirt-engine release.

Before Dreyou's repo I spent considerable time attempting to rebuild Fedora
SRPMs in EL6 to meet all dependencies but there were numerous circular
dependency issues building maven2 in EL6.  This was before 3.1 and have not
attempted a full dependency build since.

Id be interested in knowing what other challenges exist for an EL6 release
and would like to help where I can.

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


Re: [Users] Setting up logical storage networks

2012-06-22 Thread Trey Dockendorf
On Thu, Jun 21, 2012 at 7:17 AM, Dan Kenigsberg dan...@redhat.com wrote:
 On Wed, Jun 20, 2012 at 02:52:19PM -0400, Mike Kolesnik wrote:
  Thanks for the response, see responses inline.

 You're welcome, responses inline.

 
  On Wed, Jun 20, 2012 at 2:54 AM, Mike Kolesnik mkole...@redhat.com
  wrote:
   Hi,
  
   Please see reply in-line.
  
   In ovirt-engine-3.1 I'm attempting to setup the base logical
   networks
   and have run into 2 major issues.
  
   Are you using cluster version 3.0 or 3.1?
  
 
  I have been using 3.1 as it's the default.  Is the different just the
  API updates?  All I could really find related to 3.0 vs 3.1
  pertaining
  to networking was this document
  http://www.ovirt.org/wiki/Features/Design/Network/SetupNetworks
 

 As Itamar replied, there are a few more network features in 3.1 other than
 this one.

 For a Host which is in a 3.1 cluster there should be a Setup Networks
 button which indeed enables the functionality described in that wiki.
 This is a new feature for 3.1  up which allows to do several network
 changes in an atomic manner, with an improved UI experience.

 However, from the logs it looks like you're using the old commands to edit
 the networks on the Host, so if you have this button (you should) then you
 can try using it.

 SNIP

  
   Unfortunately, oVirt supports setting only the default gateway of
   the Host
   (This is the field you saw in the management network).
  
   We could theoretically use initscripts' static routing files, but
   that is left for
   future development.
  
 
  So for now, is it then easier to just run all public interfaces
  through the same subnet/gateway?  The main reason to run management
  via 100Mbps and everything else 1Gbps was that our campus is out of
  IPs so we're attempting to conserve on the usage of gigabit IPs.

 Yes, currently the only gateway you can specify is the default one which
 is set on the management network.

 However it is worth mentioning that VM networks should generally not
 have an IP address (or gateway) of their own. At best, they serve as
 layer-2-only entities. Putting the management network in one subnet and
 VMs on a different one, makes a lot of sense.


 SNIP

 snap
 
 
  So in the host interface eth5 I set the following via web interface
 
  Network: private1
  Boot Protocol: Static
  IP: 10.20.1.241
  Subnet Mask: 255.0.0.0
  Check: Save network configuration
 
  After the save the node's ifcfg-eth5 is touched (based on modified
  date in ls -la) but this is all it contains
  DEVICE=eth5
  ONBOOT=yes
  BOOTPROTO=none
  HWADDR=00:1b:21:1d:33:f1
  NM_CONTROLLED=no
  MTU=9000
 
 
  As far as I can tell the only setting from ovirt-engine that made it
  to that file was the MTU setting defined when creating the logical
  network for the cluster.
 
  Is my process somehow wrong or am I missing a step?  I've done this
  with the node being in both Up status and Maintenance, same
  results.

 No, it looks like a bug that should be taken care of.

 And a serious one, that hinders the usability of non-VM networks, and
 which I consider an oVirt-3.1 release blocker

  Bug 834281 - [vdsm][bridgeless] BOOTPROTO/IPADDR/NETMASK options are
  not set on interface

 Thanks for reporting it.

 Dan.

If I keep my ovirtmgmt interface on a 100Mbps subnet, and my VM
Networks on 1Gbps network, there's anything special I have to do in
routing or anything to prevent traffic of the VMs from following the
default route defined in ovirtmgmt?

I'm also experiencing an issue with bonds that may be related.  I
create the bond and set to Mode 5, yet the ifcfg-bond0 seems to
reflect Mode 4.

DEVICE=bond0
ONBOOT=yes
BOOTPROTO=none
BONDING_OPTS='mode=802.3ad miimon=150'
NM_CONTROLLED=no
MTU=9000


Here's what looks relevant in the vdsm.log


Thread-55232::DEBUG::2012-06-22
16:56:56,242::BindingXMLRPC::872::vds::(wrapper) client
[128.194.76.185]::call setupNetworks with ({'stor0': {'bonding':
'bond0', 'bridged': 'false', 'mtu': '9000'}}, {'bond0': {'nics':
['eth3', 'eth2'], 'BONDING_OPTS': 'mode=5'}}, {'connectivityCheck':
'true', 'connectivityTimeout': '6'}) {} flowID [39d484a3]
Thread-55233::DEBUG::2012-06-22
16:56:56,242::BindingXMLRPC::872::vds::(wrapper) client
[128.194.76.185]::call ping with () {} flowID [39d484a3]
Thread-55233::DEBUG::2012-06-22
16:56:56,244::BindingXMLRPC::879::vds::(wrapper) return ping with
{'status': {'message': 'Done', 'code': 0}}
MainProcess|Thread-55232::DEBUG::2012-06-22
16:56:56,270::configNetwork::1061::setupNetworks::(setupNetworks)
Setting up network according to configuration: networks:{'stor0':
{'bonding': 'bond0', 'bridged': 'false', 'mtu': '9000'}},
bondings:{'bond0': {'nics': ['eth3', 'eth2'], 'BONDING_OPTS':
'mode=5'}}, options:{'connectivityCheck': 'true',
'connectivityTimeout': '6'}
MainProcess|Thread-55232::DEBUG::2012-06-22
16:56:56,270::configNetwork::1065::root::(setupNetworks) Validating
configuration
Thread-55234::DEBUG::2012-06-22

Re: [Users] Setting up logical storage networks

2012-06-20 Thread Trey Dockendorf
Thanks for the response, see responses inline.

On Wed, Jun 20, 2012 at 2:54 AM, Mike Kolesnik mkole...@redhat.com wrote:
 Hi,

 Please see reply in-line.

 In ovirt-engine-3.1 I'm attempting to setup the base logical networks
 and have run into 2 major issues.

 Are you using cluster version 3.0 or 3.1?


I have been using 3.1 as it's the default.  Is the different just the
API updates?  All I could really find related to 3.0 vs 3.1 pertaining
to networking was this document
http://www.ovirt.org/wiki/Features/Design/Network/SetupNetworks


 The first is I'm only seeing a Gateway field for the management
 interface.  When I went to create a network for VMs (on seperate
 subnet) I did not see a place to specify gateway (see img
 ovirt_network_missing_gateway.png).  Right now my management port is
 on a 100mbps network and the bridged devices live on a 1Gbps network
 (net140 in cluster).  Is there a reason the gateway would be missing?
 I've attached ovirt_networks.png that shows all the interfaces on my
 host.

 Unfortunately, oVirt supports setting only the default gateway of the Host
 (This is the field you saw in the management network).

 We could theoretically use initscripts' static routing files, but that is 
 left for
 future development.


So for now, is it then easier to just run all public interfaces
through the same subnet/gateway?  The main reason to run management
via 100Mbps and everything else 1Gbps was that our campus is out of
IPs so we're attempting to conserve on the usage of gigabit IPs.


 The second issue I'm having is creating a storage network.  I created
 2 logical networks , private0 and private1.  I left the VM Network
 unchecked on both as my assumption was that dicates if they can be
 added to VMs.  Since these are only for hosts to connect to the iSCSI
 I didn't think that was necessary.  When I set the IP information
 (private_network0.png) and select Ok the save goes through but when I
 edit the interface again the information is gone and the file
 ifcfg-eth4 does not have IP information.  This is what I looks like

 DEVICE=eth4
 ONBOOT=yes
 BOOTPROTO=none
 HWADDR=00:1b:21:1d:33:f0
 NM_CONTROLLED=no
 MTU=9000

 I didn't quite understand what you did here..
 What I think you meant is:
 1. You edited the network on a NIC, and provided static boot protocol
   with the parameters (ip, netmask).
 2. After that when you clicked OK then the configuration was sent to
   the Host, and in the Network Interfaces tab for the Host you could
   see the IP in the Address column. On the host the ifcfg script for
   this network had these fields set.
 --- Assuming that no restart of Host or VDSM on Host was done ---
 3. You edited the network again, didn't change anything, and clicked OK.
 4. This time, the boot protocol info was gone from display  ifcfg file
   on the Host.

 Is this correct?

 Also do you by any chance have the log files of ovirt (engine.log)/vdsm
 (vdsm.log) with the flow that you did?

I'll try to clarify the steps I took a little better, sorry if it was
unclear before.

1. Create logical network in Cluster that was NOT a VM Network (my
assumption of how to setup a storage network)
2. Edit NIC on host, set boot protocol to static and provide
IP/Netmask, and select the logical network created in #1, check Save
network configuration
3. After clicking OK the corresponding ifcfg file on the node was
modified, but the values for IP/Netmask were missing.  Also the values
did not appear in the network interface list, and were not shown when
going to that same interface and selecting Add/Edit again

That process did not involve a reboot of the host.

So in the host interface eth5 I set the following via web interface

Network: private1
Boot Protocol: Static
IP: 10.20.1.241
Subnet Mask: 255.0.0.0
Check: Save network configuration

After the save the node's ifcfg-eth5 is touched (based on modified
date in ls -la) but this is all it contains
DEVICE=eth5
ONBOOT=yes
BOOTPROTO=none
HWADDR=00:1b:21:1d:33:f1
NM_CONTROLLED=no
MTU=9000


As far as I can tell the only setting from ovirt-engine that made it
to that file was the MTU setting defined when creating the logical
network for the cluster.

Is my process somehow wrong or am I missing a step?  I've done this
with the node being in both Up status and Maintenance, same
results.

As a test I manually updated the IP/Netmask of ifcfg-eth4 and it shows
up in the web interface with the correct information however any
changes via the web interface will remove the IPADDR and NETMASK
lines.



 I also attached image cluster_logical_networks.png that shows the all
 the logical networks on this cluster.  So far my plan is to have a
 single public interface for VM traffic, then two for storage traffic,
 each going to a different switch.  This setup is just an initial test
 but I'd hope to have it in production once I get some of these kinks
 worked out.

 Please let me know what information would be useful to debug this
 further.

 Thanks
 - 

Re: [Users] oVirt 3.1 - Error adding host , incorrect vdsm version

2012-06-19 Thread Trey Dockendorf
On Tue, Jun 19, 2012 at 1:40 PM, Dan Kenigsberg dan...@redhat.com wrote:
 On Tue, Jun 19, 2012 at 12:08:09PM -0400, Ofer Schreiber wrote:
 Just checked this issue with latest ovirt-engine on F17 (with vdsm 4.10), 
 and didn't encounter this issue at all.

 Danken - any idea why?

 Hey! I was the one soliciting ideas on how come this issue was not seen
 until Trey bumped on it. ;-)

 Maybe, just maybe, you host sees BOTH 4.10 and 4.9 ?

 what does the following print on your python interpreter?

 import yum
 my = yum.YumBase()
 my.pkgSack.searchNevra(name='rpm')



 - Original Message -
  On Mon, Jun 18, 2012 at 04:08:06PM -0500, Trey Dockendorf wrote:
   On Mon, Jun 18, 2012 at 3:25 PM, Dan Kenigsberg dan...@redhat.com
   wrote:
  
On Mon, Jun 18, 2012 at 03:01:10PM -0500, Trey Dockendorf wrote:
 
  snip
 
   
You are right. And it is truly surprising that this bug hasn't
been
open since we've bumped vdsm version to 4.10.
   
Would you open up this bug, and make it block
   Bug 822145 - Tracker: oVirt 3.1 release
?
   
The bootstrapping code is a mess. It evolves by adding one ugly
patch
over the other. In that spirit, would the following patch solve
your
bootstrapping pains?
 
  I actually really really hate the code there, and spent some time
  suggesting a less bad approach. Would you be kind enough to test
  http://gerrit.ovirt.org/#/c/5469/
  and the 2 patches below it?
 
   
diff --git a/vds_bootstrap/vds_bootstrap.py
b/vds_bootstrap/vds_bootstrap.py
index 0df5023..4fcc040 100755
--- a/vds_bootstrap/vds_bootstrap.py
+++ b/vds_bootstrap/vds_bootstrap.py
@@ -76,11 +76,11 @@ rhel6based =
deployUtil.versionCompare(deployUtil.getOSVersion(), 6.0) = 0
   
 # TODO this is an infra-hackish heuristic for identifying Fedora
 # drop as soon as possible
-fedorabased =
deployUtil.versionCompare(deployUtil.getOSVersion(), 16)
= 0
+fedorabased =
deployUtil.versionCompare(deployUtil.getOSVersion(), 17)
= 0
   
 if rhel6based:
    VDSM_NAME = vdsm
-    VDSM_MIN_VER = VDSM_NAME + -4.9
+    VDSM_MIN_VER = VDSM_NAME + -4.10
    KERNEL_VER = 2.6.32-.*.el6
    KERNEL_MIN_VER = 150
    MINIMAL_SUPPORTED_PLATFORM = 6.0
   
   
  
   Those changes worked, the install is now past that point and
   installing
   packages.
  
   Bug filed, https://bugzilla.redhat.com/show_bug.cgi?id=833201
 
  Thanks!
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 


From the python , you want to output of name='rpm' or name='vdsm' ?  I
figured the later but included both

On VDSM node

 import yum
 my = yum.YumBase()
 my.pkgSack.searchNevra(name='rpm')
Loaded plugins: fastestmirror, presto, priorities
Loading mirror speeds from cached hostfile
 * base: mirror.raystedman.net
 * epel: mirror.utexas.edu
 * extras: mirror.unl.edu
 * updates: mirror.raystedman.net
[YumAvailablePackageSqlite : rpm-4.8.0-19.el6.x86_64 (0x28c49d0),
YumAvailablePackageSqlite : rpm-4.8.0-19.el6_2.1.x86_64 (0x28c4b90)]
 my.pkgSack.searchNevra(name='vdsm')
[YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64
(0x28c4cd0)]


On the ovirt-engine host

 import yum
 my = yum.YumBase()
 my.pkgSack.searchNevra(name='rpm')
Loaded plugins: fastestmirror, priorities, versionlock
Loading mirror speeds from cached hostfile
 * base: mirror.steadfast.net
 * epel: mirror.steadfast.net
 * extras: mirror.steadfast.net
 * updates: mirror.anl.gov
[YumAvailablePackageSqlite : rpm-4.8.0-19.el6.x86_64
(0x7f60110cedd0), YumAvailablePackageSqlite :
rpm-4.8.0-19.el6_2.1.x86_64 (0x7f60110dde90)]
 my.pkgSack.searchNevra(name='vdsm')
[YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64
(0x7f60110dd490)]

Let me know if anything else would be helpful.

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


[Users] oVirt 3.1 - Error adding host , incorrect vdsm version

2012-06-18 Thread Trey Dockendorf
I have a ovirt-3.1 server installed in CentOS 6.2 via the ovirt-dre repo ,
this is what is installed on the server with ovirt-engine

ovirt-engine.noarch
 3.1.0_0001-1.8.el6
 @ovirt-dre
ovirt-engine-backend.noarch
 3.1.0_0001-1.8.el6
 @ovirt-dre
ovirt-engine-config.noarch
  3.1.0_0001-1.8.el6
   @ovirt-dre
ovirt-engine-dbscripts.noarch
 3.1.0_0001-1.8.el6
 @ovirt-dre
ovirt-engine-genericapi.noarch
  3.1.0_0001-1.8.el6
   @ovirt-dre
ovirt-engine-jbossas711.x86_64
  1-0
  @ovirt-dre
ovirt-engine-notification-service.noarch
  3.1.0_0001-1.8.el6
   @ovirt-dre
ovirt-engine-restapi.noarch
 3.1.0_0001-1.8.el6
 @ovirt-dre
ovirt-engine-sdk.noarch
 3.1.0.1-1alpha.el6
 @ovirt-dre
ovirt-engine-setup.noarch
 3.1.0_0001-1.8.el6
 @ovirt-dre
ovirt-engine-tools-common.noarch
  3.1.0_0001-1.8.el6
   @ovirt-dre
ovirt-engine-userportal.noarch
  3.1.0_0001-1.8.el6
   @ovirt-dre
ovirt-engine-webadmin-portal.noarch
 3.1.0_0001-1.8.el6
 @ovirt-dre
ovirt-image-uploader.noarch
 1.0.0-1.el6
  @ovirt-dre
ovirt-iso-uploader.noarch
 1.0.0-1.el6
  @ovirt-dre
ovirt-log-collector.noarch
  1.0.0-1.el6
  @ovirt-dre


I took an existing KVM server and installed vdsm and follow both the Dreyou
instructions and those in ovirt documentation on setting up a node.
 However when I add the node via ovirt management portal I get an error in
the GUI on the step for VDSM_MAJOR_VER

on the node , /tmp/vds_bootstrap.64713.log
Mon, 18 Jun 2012 14:20:20 DEBUG Start VDS Validation 
Mon, 18 Jun 2012 14:20:20 DEBUGEntered VdsValidation(subject = '
dc-kvm0.tamu.edu', random_num = '8408ad00-510d-47a7-98e9-ed73d95ad85d',
rev_num = 'None', installVirtualizationService = 'True',
installGlusterService = 'False')
Mon, 18 Jun 2012 14:20:20 DEBUGSetting up Package Sacks
Mon, 18 Jun 2012 14:20:22 DEBUGyumSearch: found vdsm entries:
[YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64
(0x17e8e90)]
Mon, 18 Jun 2012 14:20:22 DEBUGHost properly registered with
RHN/Satellite.
Mon, 18 Jun 2012 14:20:22 DEBUGBSTRAP component='RHN_REGISTRATION'
status='OK' message='Host properly registered with RHN/Satellite.'/
Mon, 18 Jun 2012 14:20:25 DEBUGyumSearchVersion: pkg
vdsm-4.10.0-0.33.git40b2d55.el6.x86_64 does not start with: vdsm-4.9
Mon, 18 Jun 2012 14:20:25 ERRORUnable to fetch VDSM with minimal
version of vdsm-4.9. Please check if host is properly registered with
updated yum repository
Mon, 18 Jun 2012 14:20:25 DEBUGBSTRAP component='VDSM_MAJOR_VER'
status='FAIL' message='Unable to fetch VDSM with minimal version of
vdsm-4.9. Please check if host is properly registered with updated yum
repository'/
Mon, 18 Jun 2012 14:20:25 ERRORcheckMajorVersion test failed
Mon, 18 Jun 2012 14:20:25 DEBUGBSTRAP component='RHEV_INSTALL'
status='FAIL'/
Mon, 18 Jun 2012 14:20:25 DEBUG End VDS Validation 


This is a rather obvious error, it expects vdsm-4.9* and I have vdsm-4.10*.
 Is this a bug or expected?  I'd seem to think it's a bug as the beta repo
for ovirt has ovirt-3.1 with vdsm-4.10.

This is what's on the node
vdsm.x86_64
4.10.0-0.33.git40b2d55.el6
   @vdsm-dre
vdsm-cli.noarch
4.10.0-0.33.git40b2d55.el6
   @vdsm-dre
vdsm-python.x86_64
 4.10.0-0.33.git40b2d55.el6
   @vdsm-dre
vdsm-xmlrpc.noarch
 4.10.0-0.33.git40b2d55.el6
   @vdsm-dre

Any advice?

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


Re: [Users] oVirt 3.1 - Error adding host , incorrect vdsm version

2012-06-18 Thread Trey Dockendorf
On Mon, Jun 18, 2012 at 3:25 PM, Dan Kenigsberg dan...@redhat.com wrote:

 On Mon, Jun 18, 2012 at 03:01:10PM -0500, Trey Dockendorf wrote:
  I have a ovirt-3.1 server installed in CentOS 6.2 via the ovirt-dre repo
 ,
  this is what is installed on the server with ovirt-engine
 
  ovirt-engine.noarch
   3.1.0_0001-1.8.el6
   @ovirt-dre
  ovirt-engine-backend.noarch
   3.1.0_0001-1.8.el6
   @ovirt-dre
  ovirt-engine-config.noarch
3.1.0_0001-1.8.el6
 @ovirt-dre
  ovirt-engine-dbscripts.noarch
   3.1.0_0001-1.8.el6
   @ovirt-dre
  ovirt-engine-genericapi.noarch
3.1.0_0001-1.8.el6
 @ovirt-dre
  ovirt-engine-jbossas711.x86_64
1-0
@ovirt-dre
  ovirt-engine-notification-service.noarch
3.1.0_0001-1.8.el6
 @ovirt-dre
  ovirt-engine-restapi.noarch
   3.1.0_0001-1.8.el6
   @ovirt-dre
  ovirt-engine-sdk.noarch
   3.1.0.1-1alpha.el6
   @ovirt-dre
  ovirt-engine-setup.noarch
   3.1.0_0001-1.8.el6
   @ovirt-dre
  ovirt-engine-tools-common.noarch
3.1.0_0001-1.8.el6
 @ovirt-dre
  ovirt-engine-userportal.noarch
3.1.0_0001-1.8.el6
 @ovirt-dre
  ovirt-engine-webadmin-portal.noarch
   3.1.0_0001-1.8.el6
   @ovirt-dre
  ovirt-image-uploader.noarch
   1.0.0-1.el6
@ovirt-dre
  ovirt-iso-uploader.noarch
   1.0.0-1.el6
@ovirt-dre
  ovirt-log-collector.noarch
1.0.0-1.el6
@ovirt-dre
 
 
  I took an existing KVM server and installed vdsm and follow both the
 Dreyou
  instructions and those in ovirt documentation on setting up a node.
   However when I add the node via ovirt management portal I get an error
 in
  the GUI on the step for VDSM_MAJOR_VER
 
  on the node , /tmp/vds_bootstrap.64713.log
  Mon, 18 Jun 2012 14:20:20 DEBUG Start VDS Validation 
  Mon, 18 Jun 2012 14:20:20 DEBUGEntered VdsValidation(subject = '
  dc-kvm0.tamu.edu', random_num = '8408ad00-510d-47a7-98e9-ed73d95ad85d',
  rev_num = 'None', installVirtualizationService = 'True',
  installGlusterService = 'False')
  Mon, 18 Jun 2012 14:20:20 DEBUGSetting up Package Sacks
  Mon, 18 Jun 2012 14:20:22 DEBUGyumSearch: found vdsm entries:
  [YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64
  (0x17e8e90)]
  Mon, 18 Jun 2012 14:20:22 DEBUGHost properly registered with
  RHN/Satellite.
  Mon, 18 Jun 2012 14:20:22 DEBUGBSTRAP component='RHN_REGISTRATION'
  status='OK' message='Host properly registered with RHN/Satellite.'/
  Mon, 18 Jun 2012 14:20:25 DEBUGyumSearchVersion: pkg
  vdsm-4.10.0-0.33.git40b2d55.el6.x86_64 does not start with: vdsm-4.9
  Mon, 18 Jun 2012 14:20:25 ERRORUnable to fetch VDSM with minimal
  version of vdsm-4.9. Please check if host is properly registered with
  updated yum repository
  Mon, 18 Jun 2012 14:20:25 DEBUGBSTRAP component='VDSM_MAJOR_VER'
  status='FAIL' message='Unable to fetch VDSM with minimal version of
  vdsm-4.9. Please check if host is properly registered with updated yum
  repository'/
  Mon, 18 Jun 2012 14:20:25 ERRORcheckMajorVersion test failed
  Mon, 18 Jun 2012 14:20:25 DEBUGBSTRAP component='RHEV_INSTALL'
  status='FAIL'/
  Mon, 18 Jun 2012 14:20:25 DEBUG End VDS Validation 
 
 
  This is a rather obvious error, it expects vdsm-4.9* and I have
 vdsm-4.10*.
   Is this a bug or expected?  I'd seem to think it's a bug as the beta
 repo
  for ovirt has ovirt-3.1 with vdsm-4.10.

 You are right. And it is truly surprising that this bug hasn't been
 open since we've bumped vdsm version to 4.10.

 Would you open up this bug, and make it block
Bug 822145 - Tracker: oVirt 3.1 release
 ?

 The bootstrapping code is a mess. It evolves by adding one ugly patch
 over the other. In that spirit, would the following patch solve your
 bootstrapping pains?

 diff --git a/vds_bootstrap/vds_bootstrap.py
 b/vds_bootstrap/vds_bootstrap.py
 index 0df5023..4fcc040 100755
 --- a/vds_bootstrap/vds_bootstrap.py
 +++ b/vds_bootstrap/vds_bootstrap.py
 @@ -76,11 +76,11 @@ rhel6based =
 deployUtil.versionCompare(deployUtil.getOSVersion(), 6.0) = 0

  # TODO this is an infra-hackish heuristic for identifying Fedora
  # drop as soon as possible
 -fedorabased = deployUtil.versionCompare(deployUtil.getOSVersion(), 16)
 = 0
 +fedorabased = deployUtil.versionCompare(deployUtil.getOSVersion(), 17)
 = 0

  if rhel6based:
 VDSM_NAME = vdsm
 -VDSM_MIN_VER = VDSM_NAME + -4.9

Re: [Users] Host setup for 3.1 beta

2012-06-18 Thread Trey Dockendorf
On Mon, Jun 18, 2012 at 4:58 PM, Dennis Jacobfeuerborn
denni...@conversis.de wrote:
 On 06/18/2012 10:27 PM, Dan Kenigsberg wrote:
 On Mon, Jun 18, 2012 at 10:24:51PM +0200, Dennis Jacobfeuerborn wrote:
 Hi,
 is there a working way to add a host with the current beta code? I tried
 the latest node iso and also a plain Fedora 17 with the latest vdsm
 packages but in both cases the registration seems to succeed but the
 installation seems to fail.

 Could you provide more information about the failure? is this the issue
 reported by Trey Dockendorf in
 http://lists.ovirt.org/pipermail/users/2012-June/002466.html


 Actually after seeing the /tmp/vds_bootstrap.64713.log bit in that mail I
 was able to find out what the problem was and fix it. Logs should really go
 into /var/log that where I was trying to find information on what was going 
 on.

 The installation seems to succeed now and the Host is displayed as Up. I
 got stuck almost 5 minutes in the state Reboot though even though the
 node was up in a few seconds after the reboot. What exactly is causing this
 long delay? Is the engine trying to contact vdsm or is the engine waiting
 for vdsm to connect to the engine?

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


I noticed the same delay and it could be due to the log being in /tmp.
 I got an SELinux denial of /sbin/shutdown trying to write to the
/tmp/vps_bootstrap* file.  Just a guess.  I also noticed that the
vdsm.conf file had context of the tmp directory and not etc_t.  After
doing numerous restorecon on files I cleared my SELinux audit log, If
I see it again I'll report as it may cause some problems.

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


[Users] Managing ovirt-node with Puppet - Bad idea?

2012-06-18 Thread Trey Dockendorf
Currently I've been running all my KVM systems as standard libvirt
managed hypervisors with virt-manager for creating VMs.  All the setup
of these systems was done via Puppet, including bridges and pool
definitions.  Now that I've setup my first ovirt-node I'm wondering if
Puppet is appropriate on the ovirt-node.

The first thing that concerned me was libvirtd was not set to start on
boot after installing in the ovirt web interface, is this because the
vdsmd daemon starts/stops libvirtd?  Also is is it safe to manage
things like vdsm.conf via Puppet or will ovirt-engine ever touch that
file outside of the bootstrap process?

Right now all my nodes will be bare CentOS 6.2 systems with a basic
KVM / libvirt hypervisor and then vdsm.  What I'm curious of is if
anyone has suggestions or insight into whether or not something like
Puppet should be managing ovirt-nodes.  Ideally I'd like to use a bare
hypervisor like RHEV-H or the oVirt-node ISO but all I have access to
is the later and I'm very weary of having anywhere Fedora in my data
center aside from my desktop.  So far Puppet has proven useful in the
process of setting up the ovirt-node prior to adding it to oVirt
interface, but I'm worried something I'm enforcing will be changed by
ovirt and then changed back by Puppet and break my setup.

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


Re: [Users] oVirt RPM install for RHEL 6.2

2012-03-20 Thread Trey Dockendorf
On Tue, Mar 20, 2012 at 12:17 PM, Andrei Vakhnin
andrey.a.vakh...@nasa.gov wrote:
 Anyone was able to get a successful installation of ovirt-engine on RHELS 6.2?


 When I try to do rpm install of virt-engine on rhel6.2 I'm getting following 
 errors:

 Error: Package: ovirt-engine-3.0.0_0001-1.6.fc16.x86_64 (ovirt-engine-stable)
           Requires: libc.so.6(GLIBC_2.14)(64bit)
 Error: Package: ovirt-engine-log-collector-3.0.0_0001-1.6.fc16.x86_64 
 (ovirt-engine-stable)
           Requires: python(abi) = 2.7
           Installed: python-2.6.6-29.el6.x86_64 (@rhel-x86_64-server-6)
               python(abi) = 2.6
           Available: python-2.6.5-3.el6.i686 (rhel-x86_64-server-6)
               python(abi) = 2.6
           Available: python-2.6.5-3.el6_0.2.i686 (rhel-x86_64-server-6)
               python(abi) = 2.6
           Available: python-2.6.6-20.el6.x86_64 (rhel-x86_64-server-6)
               python(abi) = 2.6
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest

 Thanks

 Andrei

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


Using the FC16 RPMs will not work in RHEL or CentOS in this case.
This was referenced a few days ago on the list,
http://www.dreyou.org/ovirt/.  I haven't tried it myself, but looks
promising.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] installing ovirt engine on CentOS

2012-03-08 Thread Trey Dockendorf
On Thu, Mar 8, 2012 at 1:12 PM, Nathan Stratton nat...@robotics.net wrote:
 On Thu, 8 Mar 2012, Elias Abacioglu wrote:

 I was hoping to have something in the middle cause I have no budget. I'm
 going to use this server to host my own test virtual guests. Basically to
 build and test packages on different flavours of Linux..
 I'm a bit stubborn, so I guess next step for me is to try to build these
 newer packages for EL6 and the missing ones a swell unless anyone has a
 better idea..


 Well the better idea is to stick with the supported distro, but... if you
 must be on Centos then you will need to do just what you suggest and upgrade
 to the supported packages.

 -Nathan

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


I've been attempting to re-build both oVirt and RHEV (from public FTP)
in CentOS 6 but am stuck on the maven2 dependancies.  I cannot find
the SRPMs on RedHat's public FTP for Maven, so I've been trying to
rebuild them from the FC16 SRPMs with little luck.  Does anyone have
any advice on getting maven2 into CentOS 6?  Or how it was done for
Red Hat 6?

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


Re: [Users] installing ovirt engine on CentOS

2012-03-08 Thread Trey Dockendorf
On Thu, Mar 8, 2012 at 5:30 PM, Elias Abacioglu elias.r...@gmail.com wrote:

 Will jpackage help? http://www.jpackage.org/installation.php

 Yes, It solves many of the problems but I still need to build a python-2.7
 rpm package for EL6.
 After that I would reckon the next step would be to build ovirt packages for
 EL6. Fedora 16 uses a newer glibc.

 Trey, did you have a Python 2.7  RPM or SRPM for EL6?


I tried jpackage but it never would resolve all the maven2 deps during
install.  It's been about 2 months so I'll try again.

I never got to Python 2.7.  When I tried rebuilding the ovirt SRPM in
mock the first thing that failed was compiling without maven2.  For
RHEV rebuild it was the maven2 and jboss dependancies I couldn't get
past.


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


Re: [Users] installing ovirt engine on CentOS

2012-03-08 Thread Trey Dockendorf
On Thu, Mar 8, 2012 at 5:30 PM, Elias Abacioglu elias.r...@gmail.com wrote:

 Will jpackage help? http://www.jpackage.org/installation.php

 Yes, It solves many of the problems but I still need to build a python-2.7
 rpm package for EL6.
 After that I would reckon the next step would be to build ovirt packages for
 EL6. Fedora 16 uses a newer glibc.

 Trey, did you have a Python 2.7  RPM or SRPM for EL6?

Where do you see the Python 2.7 dependency?  Running a rebuild with no
changes on the latest SPEC gives me this ...

# rpmbuild -ba --define 'dist .el6' --define 'rhel 6' ovirt-engine.spec
snip
+ make PREFIX=/builddir/build/BUILDROOT/ovirt-engine-3.0.0_0001-1.6.el6.x86_64/
install
which: no mvn in (/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/builddir/bin)
export MAVEN_OPTS=-XX:MaxPermSize=512m
install -P gwt-admin,gwt-user -D skipTests
install: WARNING: ignoring --preserve-context; this kernel is not
SELinux-enabled
install: cannot stat `gwt-admin,gwt-user': No such file or directory
make: *** [build_mvn] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.oHg34r (%install)

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