10:42 a.m.
Hi All, i have two ovirt / fakevdsm questions.
I am using fakevdsm to test my ovirt 4.0.5 engine.
I have a somewhat awkward setup where i have a relatively large amount
of dc's.
I cannot get nfs master domain to work from the api.
The api code is solid and is used on a ovirt-engine 3.5 production
cluster.
When creating the nfs storage domain i have no issues (it is created as
id (00000-00000 more zeros here......) but when i try to attach it to a
dc it fails.
I am not sure this is an ovirt of fakevdsm issue. When i manually add
the nfs storage domain it does get created which is somewhat worrying.
My real aim would be to run 500 dc's with 2 hosts and around 5 vms.
Not being able to use the nfs storage master domain is one of the
issues.
To work around this i decided to try and create 1000 dcs with a single
host using local storage.
Allthough this works it looks like the hosts and vms within the dc's
are actually not having their own storage pool.
In our prod environment we run at a much lower scale serveral dc's with
shared gluster storage (shared between the two hosts in the cluster)
This is considered per dc its own storage pool.
In my tests when reaching dc,cluster, host 249 things fail, this is
likely because of the value of 'maxnumberofhostsinstoragepool'. I would
expect this to be bound to the dcs and not the overall server.
In short i expect each dc to be able to run 249 hosts as each dc is its
own storage pool?
Similarly when i look at the ovirt ui some hosts actually show they are
running the total amount of running vms.
Again i am not sure if i am correct in assuming each dc is its own
storage pool.
Finally.
As this setup is somewhat awkward i would like to tweak the diverse
flags in ovirt engine to be more relaxed about obtaining data from the
hosts and storage domains.
I believe ovirt engine now checks every 3 seconds the host but i am
guessing i can live with every 60 seconds for example, the same would
apply for the storage part. what i am not sure about though is if there
is a golden ratio between these config items.
I.e. there is vdsRefreshRate, if i set this to 60 instead of 3 do i
need to also change the vdsTimeout value which is set to 180 by default?
sorru for the lenght of this message.
the most critical items are.
Should i worry about not being eable to create an nfs master domain or
is this a fakevdsm thing
Why are my dcs, for someone reason related to the main storage pool or
am i right in thinking a dc + cluster +host with local storage, is its
own storage pool?
Thanks you so much.
3:23 p.m.
On 27 October 2016 at 10:42, <joost(a)familiealbers.nl> wrote:
Hi All, i have two ovirt / fakevdsm questions.
I am using fakevdsm to test my ovirt 4.0.5 engine.
I have a somewhat awkward setup where i have a relatively large amount of
dc's.
I cannot get nfs master domain to work from the api.
The api code is solid and is used on a ovirt-engine 3.5 production
cluster.
When creating the nfs storage domain i have no issues (it is created
as id
(00000-00000 more zeros here......) but when i try to attach it to a dc it
fails.
please share the logs
I am not sure this is an ovirt of fakevdsm issue. When i manually add
the
nfs storage domain it does get created which is somewhat worrying.
Manually?
My real aim would be to run 500 dc's with 2 hosts and around 5
vms.
You'd have to have a host per DC, cause every DC has an SPM. You meant
cluster or I'm missing something.
Not being able to use the nfs storage master domain is one of the
issues.
To work around this i decided to try and create 1000 dcs with a single
host using local storage.
Allthough this works it looks like the hosts and vms within the dc's are
actually not having their own storage pool.
In our prod environment we run at a much lower scale serveral dc's with
shared gluster storage (shared between the two hosts in the cluster)
This is considered per dc its own storage pool.
In my tests when reaching dc,cluster, host 249 things fail, this is likely
because of the value of 'maxnumberofhostsinstoragepool'. I would expect
this to be bound to the dcs and not the overall server.
In short i expect each dc to be able to run 249 hosts as each dc is its
own storage pool?
I'm not sure I understand the question. However, the limitation is soft
and can
be overridden.
Similarly when i look at the ovirt ui some hosts actually show they
are
running the total amount of running vms.
Yes, when running with vdsm fake you must set this config value as well
```bash
sudo -i -u postgreexport ENGINE_DB=dbname
psql $ENGINE_DB -c "UPDATE vdc_options set option_value = 'true' WHERE
option_name = 'UseHostNameIdentifier';"
```
I've sent a patch to gerrit for that https://gerrit.ovirt.org/65804
Again i am not sure if i am correct in assuming each dc is its own
storage
pool.
Correct. DC = Storage Pool
Finally.
As this setup is somewhat awkward i would like to tweak the diverse flags
in ovirt engine to be more relaxed about obtaining data from the hosts and
storage domains.
I believe ovirt engine now checks every 3 seconds the host but i am
guessing i can live with every 60 seconds for example, the same would apply
for the storage part. what i am not sure about though is if there is a
golden ratio between these config items.
I.e. there is vdsRefreshRate, if i set this to 60 instead of 3 do i need
to also change the vdsTimeout value which is set to 180 by default?
Change the VdsRefreshRate to 20s - but bare in mind that we have a
limitation when
starting up a VM - its status will show as up only after
the next 20s interval
Please report with your finding on the above tweak
sorru for the lenght of this message.
the most critical items are.
Should i worry about not being eable to create an nfs master domain or is
this a fakevdsm thing
Why are my dcs, for someone reason related to the main storage pool or am
i right in thinking a dc + cluster +host with local storage, is its own
storage pool?
Thanks you so much.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
4:22 p.m.
Hi Roy,
thank you kindly for your response.
what i am trying to do is this.
1) Create a dc 'DC0-aws2'
2) Create a cluster 'CLUSTER0-aws2'
3) Add Host1 'PCB1-0-aws2'
4) Add Host2 'PCB2-0-aws2'
5) Create NFS Storage 'DC0-aws2-NFS'
6) Attach to DC 'DC0-aws2'
My issues are with step 5 and 6 but for reference some insights to what
i am doing in case i am making mistakes in earlier steps.
Please be aware that when doing steps 5 and 6 in the ovirt web ui it
seems to work which is somewhat strange i recon.
also note i see tons of the following log lines containing
Command 'ProcessOvfUpdateForStorageDomain'
i removed some to make the logs less verbose.
1) Create DC
self.api.datacenters.add(params.DataCenter(name='DC0-aws2',local=False,version=self.version))
1) Create Cluster
self.api.clusters.add(params.Cluster(
name='CLUSTER0-aws2',
cpu=params.CPU(id=self.cpu_type),
data_center=self.api.datacenters.get('DC0-aws2'),
version=self.version,
gluster_service = False,
threads_as_cores = True,
tunnel_migration = False,
trusted_service = False,
ha_reservation = False,
error_handling =
params.ErrorHandling(on_error='do_not_migrate')
)):
3 Add Host1
spmParams = params.SPM(priority=7)
self.api.hosts.add(params.Host(
name='PCB1-0-aws2',
address='PCB1-0-aws2',
cluster=self.api.clusters.get('CLUSTER0-aws2'),
root_password='test',
spm = spmParams
)):
4 Add Host2
spmParams = params.SPM(priority=-1)
self.api.hosts.add(params.Host(
name='PCB2-0-aws2',
address='PCB2-0-aws2',
cluster=self.api.clusters.get('CLUSTER0-aws2'),
root_password='test',
spm = spmParams
)):
5 create nfs storage
myDC = self.api.datacenters.get(name='DC0-aws2')
myHOST = self.api.hosts.get(name='PCB1-0-aws2')
storageParams = params.Storage(address='PCB1-0-aws2', path="/data",
type_="nfs",vfs_type='nfs' )
storageDomainParams =
params.StorageDomain(name='DC0-aws2-NFS',data_center=myDC,storage_format='v3',type_='data',
host=myHOST,storage=storageParams)# type_='data', storage_format="v3",
storage=s)
sd = self.api.storagedomains.add(storageDomainParams)
6 attach nfs storage
self.api.datacenters.get(name='DC0-aws2').storagedomains.add(self.api.storagedomains.get(name='DC0-aws2-NFS'))
The last steps fails but it might be more is not done properly.
Logs below from step 1 to step 6
2016-10-27 13:15:55,759 INFO
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
(DefaultQuartzScheduler7) [d2d316c] Command
'ProcessOvfUpdateForStorageDomain' (id:
'b6600ea7-f75d-4726-bea6-5d73d980cbeb') waiting on child command id:
'1990eaf9-c7c4-438d-a9be-2d4201cbdd34' type:'UploadStream' to complete
2016-10-27 13:15:55,761 INFO
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
(DefaultQuartzScheduler7) [49a0464] Command
'ProcessOvfUpdateForStorageDomain' (id:
'e9a99687-cb73-4481-959f-948f0a55449a') waiting on child command id:
'840e7689-359c-49ea-aae5-76efa085daac' type:'UploadStream' to complete
2016-10-27 13:16:04,452 INFO
[org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-113)
[] User admin@internal successfully logged in with scopes: ovirt-app-api
ovirt-ext=token-info:authz-search
ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate
2016-10-27 13:16:04,473 INFO
[org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default
task-112) [46539124] Running command: CreateUserSessionCommand internal:
false.
2016-10-27 13:16:04,603 INFO
[org.ovirt.engine.core.bll.storage.pool.AddEmptyStoragePoolCommand]
(default task-116) [356903d7] Running command:
AddEmptyStoragePoolCommand internal: false. Entities affected : ID:
aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group
CREATE_STORAGE_POOL with role type ADMIN, ID:
580f14ab-03b0-0347-0279-0000000001cf Type: MacPoolAction group
CONFIGURE_MAC_POOL with role type ADMIN
2016-10-27 13:16:04,613 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-116) [356903d7] Correlation ID: 356903d7, Call Stack:
null, Custom Event ID: -1, Message: Data Center DC0-aws2, Compatibility
Version 4.0 and Quota Type DISABLED was added by admin@internal-authz
2016-10-27 13:16:05,697 INFO
[org.ovirt.engine.core.bll.AddClusterCommand] (default task-118)
[527f31d2] Running command: AddClusterCommand internal: false. Entities
affected : ID: 27e028d7-c074-4e8f-bbb2-2e984e87e939 Type:
StoragePoolAction group CREATE_CLUSTER with role type ADMIN
2016-10-27 13:16:05,702 INFO
[org.ovirt.engine.core.bll.profiles.AddCpuProfileCommand] (default
task-118) [3ae9d68b] Running command: AddCpuProfileCommand internal:
false. Entities affected : ID: d124d1af-057c-4c52-ac55-bd0f3e2a575d
Type: ClusterAction group CREATE_CPU_PROFILE with role type ADMIN
2016-10-27 13:16:05,708 INFO
[org.ovirt.engine.core.bll.AddPermissionCommand] (default task-118)
[485fa98d] Running command: AddPermissionCommand internal: false.
Entities affected : ID: 9051303c-7027-4279-a6fc-d88a9715fc6c Type:
CpuProfileAction group MANIPULATE_PERMISSIONS with role type USER
2016-10-27 13:16:05,716 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-118) [485fa98d] Correlation ID: 485fa98d, Call Stack:
null, Custom Event ID: -1, Message: User/Group Everyone, Namespace *,
Authorization provider: N/A was granted permission for Role
CpuProfileOperator on Cpu Profile CLUSTER0-aws2, by
admin@internal-authz.
2016-10-27 13:16:05,719 INFO
[org.ovirt.engine.core.bll.AddPermissionCommand] (default task-118)
[5a420795] Running command: AddPermissionCommand internal: false.
Entities affected : ID: 9051303c-7027-4279-a6fc-d88a9715fc6c Type:
CpuProfileAction group MANIPULATE_PERMISSIONS with role type USER
2016-10-27 13:16:05,723 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-118) [5a420795] Correlation ID: 5a420795, Call Stack:
null, Custom Event ID: -1, Message: User/Group admin, Namespace *,
Authorization provider: internal-authz was granted permission for Role
CpuProfileCreator on Cpu Profile CLUSTER0-aws2, by admin@internal-authz.
2016-10-27 13:16:05,725 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-118) [] Correlation ID: 3ae9d68b, Call Stack: null, Custom
Event ID: -1, Message: CPU Profile CLUSTER0-aws2 was successfully added
(User: admin@internal-authz).
2016-10-27 13:16:05,729 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-118) [] Correlation ID: 527f31d2, Call Stack: null, Custom
Event ID: -1, Message: Cluster CLUSTER0-aws2 was added by
admin@internal-authz
2016-10-27 13:16:05,816 INFO
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
(DefaultQuartzScheduler6) [d2d316c] Command
'ProcessOvfUpdateForStorageDomain' (id:
'b6600ea7-f75d-4726-bea6-5d73d980cbeb') waiting on child command id:
'1990eaf9-c7c4-438d-a9be-2d4201cbdd34' type:'UploadStream' to complete
2016-10-27 13:16:05,820 INFO
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
(DefaultQuartzScheduler6) [49a0464] Command
'ProcessOvfUpdateForStorageDomain' (id:
'e9a99687-cb73-4481-959f-948f0a55449a') waiting on child command id:
'840e7689-359c-49ea-aae5-76efa085daac' type:'UploadStream' to complete
2016-10-27 13:16:06,871 INFO
[org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-120)
[1d8c5d35] Running command: AddVdsCommand internal: false. Entities
affected : ID: d124d1af-057c-4c52-ac55-bd0f3e2a575d Type: ClusterAction
group CREATE_HOST with role type ADMIN
2016-10-27 13:16:06,898 INFO
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-120)
[57331071] Before acquiring and wait lock
'EngineLock:{exclusiveLocks='[27e028d7-c074-4e8f-bbb2-2e984e87e939=<REGISTER_VDS,
ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2016-10-27 13:16:06,898 INFO
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-120)
[57331071] Lock-wait acquired to object
'EngineLock:{exclusiveLocks='[27e028d7-c074-4e8f-bbb2-2e984e87e939=<REGISTER_VDS,
ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2016-10-27 13:16:06,898 INFO
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-120)
[57331071] Running command: AddVdsSpmIdCommand internal: true. Entities
affected : ID: d3b3ea38-e4be-4b5c-9164-43a253413aad Type: VDS
2016-10-27 13:16:06,901 INFO
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-120)
[57331071] Lock freed to object
'EngineLock:{exclusiveLocks='[27e028d7-c074-4e8f-bbb2-2e984e87e939=<REGISTER_VDS,
ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2016-10-27 13:16:06,903 INFO
[org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand] (default task-120)
[57331071] START, RemoveVdsVDSCommand(HostName = PCB1-0-aws2,
RemoveVdsVDSCommandParameters:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad'}), log id: 67dd5c71
2016-10-27 13:16:06,903 INFO
[org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand] (default task-120)
[57331071] FINISH, RemoveVdsVDSCommand, log id: 67dd5c71
2016-10-27 13:16:06,905 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-120)
[57331071] START, AddVdsVDSCommand(HostName = PCB1-0-aws2,
AddVdsVDSCommandParameters:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad'}), log id: 7abefebd
2016-10-27 13:16:06,905 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-120)
[57331071] AddVds - entered , starting logic to add VDS
'd3b3ea38-e4be-4b5c-9164-43a253413aad'
2016-10-27 13:16:06,905 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-120)
[57331071] AddVds - VDS 'd3b3ea38-e4be-4b5c-9164-43a253413aad' was
added, will try to add it to the resource manager
2016-10-27 13:16:06,905 INFO
[org.ovirt.engine.core.vdsbroker.VdsManager] (default task-120)
[57331071] Entered VdsManager constructor
2016-10-27 13:16:06,906 INFO
[org.ovirt.engine.core.vdsbroker.VdsManager] (default task-120)
[57331071] Initialize vdsBroker 'PCB1-0-aws2:54321'
2016-10-27 13:16:06,907 INFO
[org.ovirt.engine.core.vdsbroker.ResourceManager] (default task-120)
[57331071] VDS 'd3b3ea38-e4be-4b5c-9164-43a253413aad' was added to the
Resource Manager
2016-10-27 13:16:06,907 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-120)
[57331071] FINISH, AddVdsVDSCommand, log id: 7abefebd
2016-10-27 13:16:06,911 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-120) [57331071] Correlation ID: null, Call Stack: null,
Custom Event ID: -1, Message: Failed to verify Power Management
configuration for Host PCB1-0-aws2.
2016-10-27 13:16:06,915 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-120) [57331071] Correlation ID: 1d8c5d35, Job ID:
45050d37-95c1-4052-9bcb-d07654558ef2, Call Stack: null, Custom Event ID:
-1, Message: Host PCB1-0-aws2 was added by admin@internal-authz.
2016-10-27 13:16:09,910 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (Stomp Reactor)
[] Connecting to PCB1-0-aws2/52.212.116.229
2016-10-27 13:16:10,037 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler7) [6ebf6fa5] START,
GetHardwareInfoVDSCommand(HostName = PCB1-0-aws2,
VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
vds='Host[PCB1-0-aws2,d3b3ea38-e4be-4b5c-9164-43a253413aad]'}), log id:
637f54ff
2016-10-27 13:16:10,038 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler7) [6ebf6fa5] FINISH, GetHardwareInfoVDSCommand,
log id: 637f54ff
2016-10-27 13:16:10,071 INFO
[org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand]
(DefaultQuartzScheduler7) [3fc9ae47] Running command:
HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities
affected : ID: d3b3ea38-e4be-4b5c-9164-43a253413aad Type: VDS
2016-10-27 13:16:10,079 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler7) [3fc9ae47] START,
GetHardwareInfoVDSCommand(HostName = PCB1-0-aws2,
VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
vds='Host[PCB1-0-aws2,d3b3ea38-e4be-4b5c-9164-43a253413aad]'}), log id:
7cf75477
2016-10-27 13:16:10,080 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler7) [3fc9ae47] FINISH, GetHardwareInfoVDSCommand,
log id: 7cf75477
2016-10-27 13:16:10,092 INFO
[org.ovirt.engine.core.bll.InitVdsOnUpCommand] (DefaultQuartzScheduler7)
[416e3e10] Running command: InitVdsOnUpCommand internal: true. Entities
affected : ID: 27e028d7-c074-4e8f-bbb2-2e984e87e939 Type: StoragePool
2016-10-27 13:16:10,136 ERROR
[org.ovirt.engine.core.bll.pm.FenceProxyLocator]
(DefaultQuartzScheduler7) [416e3e10] Can not run fence action on host
'PCB1-0-aws2', no suitable proxy host was found.
2016-10-27 13:16:10,138 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetMOMPolicyParametersVDSCommand]
(DefaultQuartzScheduler7) [416e3e10] START,
SetMOMPolicyParametersVDSCommand(HostName = PCB1-0-aws2,
MomPolicyVDSParameters:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad'}), log id: 61d1440
2016-10-27 13:16:10,140 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetMOMPolicyParametersVDSCommand]
(DefaultQuartzScheduler7) [416e3e10] FINISH,
SetMOMPolicyParametersVDSCommand, log id: 61d1440
2016-10-27 13:16:10,142 INFO
[org.ovirt.engine.core.bll.hostdev.RefreshHostDevicesCommand]
(DefaultQuartzScheduler7) [5cc80636] Running command:
RefreshHostDevicesCommand internal: true. Entities affected : ID:
d3b3ea38-e4be-4b5c-9164-43a253413aad Type: VDSAction group
MANIPULATE_HOST with role type ADMIN
2016-10-27 13:16:10,142 INFO
[org.ovirt.engine.core.vdsbroker.HostDevListByCapsVDSCommand]
(DefaultQuartzScheduler7) [5cc80636] START,
HostDevListByCapsVDSCommand(HostName = PCB1-0-aws2,
VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
vds='Host[PCB1-0-aws2,d3b3ea38-e4be-4b5c-9164-43a253413aad]'}), log id:
5b4aea22
2016-10-27 13:16:10,144 INFO
[org.ovirt.engine.core.vdsbroker.HostDevListByCapsVDSCommand]
(DefaultQuartzScheduler7) [5cc80636] FINISH,
HostDevListByCapsVDSCommand, return:
[HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_0', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e110', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_3', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e113', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_4', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e114', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_1', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e111', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_2', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e112', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_7', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e117', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_8', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e118', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='computer', parentDeviceName='computer',
capability='system',
iommuGroup='null', productName='ProLiant DL160 G6',
productId='null',
vendorName='null', vendorId='null', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_5', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e115', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_6', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e116', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_9', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e119', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_10', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e1110', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1f_12', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e1112', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
deviceName='pci_0000_00_1b_11', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e1111', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'}], log id: 5b4aea22
2016-10-27 13:16:10,153 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler7) [5cc80636] Correlation ID: null, Call Stack:
null, Custom Event ID: -1, Message: Status of host PCB1-0-aws2 was set
to Up.
2016-10-27 13:16:10,155 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler7) [5cc80636] Correlation ID: null, Call Stack:
null, Custom Event ID: -1, Message: Failed to verify Power Management
configuration for Host PCB1-0-aws2.
2016-10-27 13:16:10,164 INFO
[org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand]
(DefaultQuartzScheduler7) [48f7d6aa] Running command:
HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities
affected : ID: d3b3ea38-e4be-4b5c-9164-43a253413aad Type: VDS
2016-10-27 13:16:10,167 INFO
[org.ovirt.engine.core.bll.HandleVdsVersionCommand]
(DefaultQuartzScheduler7) [24768b15] Running command:
HandleVdsVersionCommand internal: true. Entities affected : ID:
d3b3ea38-e4be-4b5c-9164-43a253413aad Type: VDS
2016-10-27 13:16:12,344 INFO
[org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-126)
[308687cf] Running command: AddVdsCommand internal: false. Entities
affected : ID: d124d1af-057c-4c52-ac55-bd0f3e2a575d Type: ClusterAction
group CREATE_HOST with role type ADMIN
2016-10-27 13:16:12,369 INFO
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-126)
[91d8725] Before acquiring and wait lock
'EngineLock:{exclusiveLocks='[27e028d7-c074-4e8f-bbb2-2e984e87e939=<REGISTER_VDS,
ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2016-10-27 13:16:12,370 INFO
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-126)
[91d8725] Lock-wait acquired to object
'EngineLock:{exclusiveLocks='[27e028d7-c074-4e8f-bbb2-2e984e87e939=<REGISTER_VDS,
ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2016-10-27 13:16:12,370 INFO
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-126)
[91d8725] Running command: AddVdsSpmIdCommand internal: true. Entities
affected : ID: e00fe8e6-fe66-493c-92fd-f26de1990429 Type: VDS
2016-10-27 13:16:12,373 INFO
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-126)
[91d8725] Lock freed to object
'EngineLock:{exclusiveLocks='[27e028d7-c074-4e8f-bbb2-2e984e87e939=<REGISTER_VDS,
ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2016-10-27 13:16:12,374 INFO
[org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand] (default task-126)
[91d8725] START, RemoveVdsVDSCommand(HostName = PCB2-0-aws2,
RemoveVdsVDSCommandParameters:{runAsync='true',
hostId='e00fe8e6-fe66-493c-92fd-f26de1990429'}), log id: 7aa1c312
2016-10-27 13:16:12,374 INFO
[org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand] (default task-126)
[91d8725] FINISH, RemoveVdsVDSCommand, log id: 7aa1c312
2016-10-27 13:16:12,376 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-126)
[91d8725] START, AddVdsVDSCommand(HostName = PCB2-0-aws2,
AddVdsVDSCommandParameters:{runAsync='true',
hostId='e00fe8e6-fe66-493c-92fd-f26de1990429'}), log id: 399ee2e
2016-10-27 13:16:12,376 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-126)
[91d8725] AddVds - entered , starting logic to add VDS
'e00fe8e6-fe66-493c-92fd-f26de1990429'
2016-10-27 13:16:12,377 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-126)
[91d8725] AddVds - VDS 'e00fe8e6-fe66-493c-92fd-f26de1990429' was added,
will try to add it to the resource manager
2016-10-27 13:16:12,377 INFO
[org.ovirt.engine.core.vdsbroker.VdsManager] (default task-126)
[91d8725] Entered VdsManager constructor
2016-10-27 13:16:12,377 INFO
[org.ovirt.engine.core.vdsbroker.VdsManager] (default task-126)
[91d8725] Initialize vdsBroker 'PCB2-0-aws2:54321'
2016-10-27 13:16:12,379 INFO
[org.ovirt.engine.core.vdsbroker.ResourceManager] (default task-126)
[91d8725] VDS 'e00fe8e6-fe66-493c-92fd-f26de1990429' was added to the
Resource Manager
2016-10-27 13:16:12,379 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-126)
[91d8725] FINISH, AddVdsVDSCommand, log id: 399ee2e
2016-10-27 13:16:12,382 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-126) [91d8725] Correlation ID: null, Call Stack: null,
Custom Event ID: -1, Message: Failed to verify Power Management
configuration for Host PCB2-0-aws2.
2016-10-27 13:16:12,387 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-126) [91d8725] Correlation ID: 308687cf, Job ID:
170a1e42-f7ff-4183-a080-5258d58cf87c, Call Stack: null, Custom Event ID:
-1, Message: Host PCB2-0-aws2 was added by admin@internal-authz.
2016-10-27 13:16:15,381 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (Stomp Reactor)
[] Connecting to PCB2-0-aws2/52.212.116.229
2016-10-27 13:16:15,396 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler3) [6ebf6fa5] START,
GetHardwareInfoVDSCommand(HostName = PCB2-0-aws2,
VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
vds='Host[PCB2-0-aws2,e00fe8e6-fe66-493c-92fd-f26de1990429]'}), log id:
4ccad49c
2016-10-27 13:16:15,398 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler3) [6ebf6fa5] FINISH, GetHardwareInfoVDSCommand,
log id: 4ccad49c
2016-10-27 13:16:15,439 INFO
[org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand]
(DefaultQuartzScheduler3) [1c8c7f9b] Running command:
HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities
affected : ID: e00fe8e6-fe66-493c-92fd-f26de1990429 Type: VDS
2016-10-27 13:16:15,446 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler3) [1c8c7f9b] START,
GetHardwareInfoVDSCommand(HostName = PCB2-0-aws2,
VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
vds='Host[PCB2-0-aws2,e00fe8e6-fe66-493c-92fd-f26de1990429]'}), log id:
5ce5d20b
2016-10-27 13:16:15,447 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler3) [1c8c7f9b] FINISH, GetHardwareInfoVDSCommand,
log id: 5ce5d20b
2016-10-27 13:16:15,460 INFO
[org.ovirt.engine.core.bll.InitVdsOnUpCommand] (DefaultQuartzScheduler3)
[16ce93f9] Running command: InitVdsOnUpCommand internal: true. Entities
affected : ID: 27e028d7-c074-4e8f-bbb2-2e984e87e939 Type: StoragePool
2016-10-27 13:16:15,487 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetMOMPolicyParametersVDSCommand]
(DefaultQuartzScheduler3) [16ce93f9] START,
SetMOMPolicyParametersVDSCommand(HostName = PCB2-0-aws2,
MomPolicyVDSParameters:{runAsync='true',
hostId='e00fe8e6-fe66-493c-92fd-f26de1990429'}), log id: 4d0b0326
2016-10-27 13:16:15,489 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetMOMPolicyParametersVDSCommand]
(DefaultQuartzScheduler3) [16ce93f9] FINISH,
SetMOMPolicyParametersVDSCommand, log id: 4d0b0326
2016-10-27 13:16:15,491 INFO
[org.ovirt.engine.core.bll.hostdev.RefreshHostDevicesCommand]
(DefaultQuartzScheduler3) [452a5538] Running command:
RefreshHostDevicesCommand internal: true. Entities affected : ID:
e00fe8e6-fe66-493c-92fd-f26de1990429 Type: VDSAction group
MANIPULATE_HOST with role type ADMIN
2016-10-27 13:16:15,493 INFO
[org.ovirt.engine.core.vdsbroker.HostDevListByCapsVDSCommand]
(DefaultQuartzScheduler3) [452a5538] START,
HostDevListByCapsVDSCommand(HostName = PCB2-0-aws2,
VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
vds='Host[PCB2-0-aws2,e00fe8e6-fe66-493c-92fd-f26de1990429]'}), log id:
2c06f493
2016-10-27 13:16:15,494 INFO
[org.ovirt.engine.core.vdsbroker.HostDevListByCapsVDSCommand]
(DefaultQuartzScheduler3) [452a5538] FINISH,
HostDevListByCapsVDSCommand, return:
[HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_0', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e110', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_3', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e113', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_4', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e114', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_1', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e111', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_2', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e112', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_7', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e117', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_8', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e118', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='computer', parentDeviceName='computer',
capability='system',
iommuGroup='null', productName='ProLiant DL160 G6',
productId='null',
vendorName='null', vendorId='null', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_5', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e115', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_6', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e116', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_9', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e119', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_10', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e1110', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1f_12', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e1112', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'},
HostDevice:{hostId='e00fe8e6-fe66-493c-92fd-f26de1990429',
deviceName='pci_0000_00_1b_11', parentDeviceName='computer',
capability='pci', iommuGroup='null', productName='4 Series Chipset
DRAM
Controller', productId='0x2e1111', vendorName='Intel Corporation',
vendorId='0x8086', parentPhysicalFunction='null',
totalVirtualFunctions='null', networkInterfaceName='null',
driver='null', assignable='true', vmId='null'}], log id: 2c06f493
2016-10-27 13:16:15,504 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler3) [452a5538] Correlation ID: null, Call Stack:
null, Custom Event ID: -1, Message: Status of host PCB2-0-aws2 was set
to Up.
2016-10-27 13:16:15,507 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler3) [452a5538] Correlation ID: null, Call Stack:
null, Custom Event ID: -1, Message: Failed to verify Power Management
configuration for Host PCB2-0-aws2.
2016-10-27 13:16:15,516 INFO
[org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand]
(DefaultQuartzScheduler3) [6328520a] Running command:
HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities
affected : ID: e00fe8e6-fe66-493c-92fd-f26de1990429 Type: VDS
2016-10-27 13:16:15,520 INFO
[org.ovirt.engine.core.bll.HandleVdsVersionCommand]
(DefaultQuartzScheduler3) [90506fe] Running command:
HandleVdsVersionCommand internal: true. Entities affected : ID:
e00fe8e6-fe66-493c-92fd-f26de1990429 Type: VDS
2016-10-27 13:16:15,886 INFO
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
(DefaultQuartzScheduler9) [d2d316c] Command
'ProcessOvfUpdateForStorageDomain' (id:
'b6600ea7-f75d-4726-bea6-5d73d980cbeb') waiting on child command id:
'1990eaf9-c7c4-438d-a9be-2d4201cbdd34' type:'UploadStream' to complete
2016-10-27 13:16:15,888 INFO
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
(DefaultQuartzScheduler9) [49a0464] Command
'ProcessOvfUpdateForStorageDomain' (id:
'e9a99687-cb73-4481-959f-948f0a55449a') waiting on child command id:
'840e7689-359c-49ea-aae5-76efa085daac' type:'UploadStream' to complete
2016-10-27 13:16:16,768 INFO
[org.ovirt.engine.core.bll.storage.connection.AddStorageServerConnectionCommand]
(default task-5) [3247ae0f] Lock Acquired to object
'EngineLock:{exclusiveLocks='[PCB1-0-aws2:/data=<STORAGE_CONNECTION,
ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2016-10-27 13:16:16,774 INFO
[org.ovirt.engine.core.bll.storage.connection.AddStorageServerConnectionCommand]
(default task-5) [3247ae0f] Running command:
AddStorageServerConnectionCommand internal: false. Entities affected :
ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group
CREATE_STORAGE_DOMAIN with role type ADMIN
2016-10-27 13:16:16,774 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(default task-5) [3247ae0f] START,
ConnectStorageServerVDSCommand(HostName = PCB1-0-aws2,
StorageServerConnectionManagementVDSParameters:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
storagePoolId='00000000-0000-0000-0000-000000000000', storageType='NFS',
connectionList='[StorageServerConnections:{id='null',
connection='PCB1-0-aws2:/data', iqn='null', vfsType='null',
mountOptions='null', nfsVersion='null', nfsRetrans='null',
nfsTimeo='null', iface='null', netIfaceName='null'}]'}), log
id:
6ce2c1ab
2016-10-27 13:16:16,778 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(default task-5) [3247ae0f] FINISH, ConnectStorageServerVDSCommand,
return: {00000000-0000-0000-0000-000000000000=0}, log id: 6ce2c1ab
2016-10-27 13:16:16,782 INFO
[org.ovirt.engine.core.bll.storage.connection.AddStorageServerConnectionCommand]
(default task-5) [3247ae0f] Lock freed to object
'EngineLock:{exclusiveLocks='[PCB1-0-aws2:/data=<STORAGE_CONNECTION,
ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2016-10-27 13:16:16,783 INFO
[org.ovirt.engine.core.bll.storage.domain.GetExistingStorageDomainListQuery]
(default task-5) [] START,
GetExistingStorageDomainListQuery(GetExistingStorageDomainListParameters:{refresh='false',
filtered='false'}), log id: 734e5285
2016-10-27 13:16:16,784 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainsListVDSCommand]
(default task-5) [] START, HSMGetStorageDomainsListVDSCommand(HostName
= PCB1-0-aws2,
HSMGetStorageDomainsListVDSCommandParameters:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
storagePoolId='00000000-0000-0000-0000-000000000000',
storageType='null', storageDomainType='Data',
path='PCB1-0-aws2:/data'}), log id: 6c32e1b2
2016-10-27 13:16:16,784 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainsListVDSCommand]
(default task-5) [] FINISH, HSMGetStorageDomainsListVDSCommand, return:
[00000000-0000-0000-0000-000000000000], log id: 6c32e1b2
2016-10-27 13:16:16,790 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand]
(default task-5) [] START, HSMGetStorageDomainInfoVDSCommand(HostName =
PCB1-0-aws2,
HSMGetStorageDomainInfoVDSCommandParameters:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
storageDomainId='00000000-0000-0000-0000-000000000000'}), log id:
2bb14dc1
2016-10-27 13:16:16,791 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand]
(default task-5) [] FINISH, HSMGetStorageDomainInfoVDSCommand, return:
<StorageDomainStatic:{name='?',
id='00000000-0000-0000-0000-000000000000'}, null>, log id: 2bb14dc1
2016-10-27 13:16:16,791 INFO
[org.ovirt.engine.core.bll.storage.domain.GetExistingStorageDomainListQuery]
(default task-5) [] FINISH, GetExistingStorageDomainListQuery, log id:
734e5285
2016-10-27 13:16:16,802 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand]
(default task-5) [1ac83d9e] START,
HSMGetStorageDomainInfoVDSCommand(HostName = PCB1-0-aws2,
HSMGetStorageDomainInfoVDSCommandParameters:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
storageDomainId='00000000-0000-0000-0000-000000000000'}), log id:
3e5559d9
2016-10-27 13:16:16,803 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand]
(default task-5) [1ac83d9e] FINISH, HSMGetStorageDomainInfoVDSCommand,
return: <StorageDomainStatic:{name='?',
id='00000000-0000-0000-0000-000000000000'}, null>, log id: 3e5559d9
2016-10-27 13:16:16,808 INFO
[org.ovirt.engine.core.bll.storage.domain.AddExistingFileStorageDomainCommand]
(default task-5) [1ac83d9e] Running command:
AddExistingFileStorageDomainCommand internal: false. Entities affected :
ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group
CREATE_STORAGE_DOMAIN with role type ADMIN
2016-10-27 13:16:16,822 INFO
[org.ovirt.engine.core.bll.profiles.AddDiskProfileCommand] (default
task-5) [409b9426] Running command: AddDiskProfileCommand internal:
true. Entities affected : ID: 00000000-0000-0000-0000-000000000000
Type: StorageAction group CREATE_STORAGE_DISK_PROFILE with role type
ADMIN
2016-10-27 13:16:16,825 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-5) [409b9426] Correlation ID: 409b9426, Job ID:
228154f9-f219-441a-9531-3e70728c8373, Call Stack: null, Custom Event ID:
-1, Message: Disk Profile DC0-aws2-NFS was successfully added (User:
admin@internal-authz).
2016-10-27 13:16:16,829 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetStorageDomainStatsVDSCommand]
(default task-5) [409b9426] START,
GetStorageDomainStatsVDSCommand(HostName = PCB1-0-aws2,
GetStorageDomainStatsVDSCommandParameters:{runAsync='true',
hostId='d3b3ea38-e4be-4b5c-9164-43a253413aad',
storageDomainId='00000000-0000-0000-0000-000000000000'}), log id:
35b8f2fd
2016-10-27 13:16:16,830 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetStorageDomainStatsVDSCommand]
(default task-5) [409b9426] FINISH, GetStorageDomainStatsVDSCommand,
return: StorageDomain:{domainName='',
domainId='00000000-0000-0000-0000-000000000000'}, log id: 35b8f2fd
2016-10-27 13:16:16,836 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-5) [409b9426] Correlation ID: 1ac83d9e, Job ID:
228154f9-f219-441a-9531-3e70728c8373, Call Stack: null, Custom Event ID:
-1, Message: Storage Domain DC0-aws2-NFS was added by
admin@internal-authz
2016-10-27 13:16:18,063 INFO
[org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand]
(default task-10) [72f77b5f] Lock Acquired to object
'EngineLock:{exclusiveLocks='[00000000-0000-0000-0000-000000000000=<STORAGE,
ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2016-10-27 13:16:18,064 WARN
[org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand]
(default task-10) [72f77b5f] Validation of action
'AttachStorageDomainToPool' failed for user admin@internal-authz.
Reasons:
VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ATTACH,ACTION_TYPE_FAILED_STORAGE_DOMAIN_NOT_EXIST
2016-10-27 13:16:18,064 INFO
[org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand]
(default task-10) [72f77b5f] Lock freed to object
'EngineLock:{exclusiveLocks='[00000000-0000-0000-0000-000000000000=<STORAGE,
ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2016-10-27 13:16:18,068 ERROR
[org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
task-10) [] Operation Failed: [Cannot attach Storage. Storage Domain
doesn't exist.]
2016-10-27 13:16:21,910 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler2) [6ebf6fa5] Fetched 0 VMs from VDS
'd3b3ea38-e4be-4b5c-9164-43a253413aad'
2016-10-27 13:16:25,289 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler8) [6ebf6fa5] Correlation ID: null, Call Stack:
null, Custom Event ID: -1, Message: Available memory of host PCB1-0-aws2
[0 MB] is under defined threshold [1024 MB].
2016-10-27 13:16:25,942 INFO
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
(DefaultQuartzScheduler7) [d2d316c] Command
'ProcessOvfUpdateForStorageDomain' (id:
'b6600ea7-f75d-4726-bea6-5d73d980cbeb') waiting on child command id:
'1990eaf9-c7c4-438d-a9be-2d4201cbdd34' type:'UploadStream' to complete
2016-10-27 13:16:27,382 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler8) [6ebf6fa5] Fetched 0 VMs from VDS
'e00fe8e6-fe66-493c-92fd-f26de1990429'
2016-10-27 13:16:30,644 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler7) [6ebf6fa5] Correlation ID: null, Call Stack:
null, Custom Event ID: -1, Message: Available memory of host PCB2-0-aws2
[0 MB] is under defined threshold [1024 MB].
2016-10-27 13:16:36,000 INFO
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
(DefaultQuartzScheduler9) [d2d316c] Command
'ProcessOvfUpdateForStorageDomain' (id:
'b6600ea7-f75d-4726-bea6-5d73d980cbeb') waiting on child command id:
'1990eaf9-c7c4-438d-a9be-2d4201cbdd34' type:'UploadStream' to complete
For what its worth
when opening the apifor storage domains in my browser i get this.
http://blahblaba/ovirt-engine/api/storagedomains
<storage_domains>
<storage_domain
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000"
id="00000000-0000-0000-0000-000000000000">
<actions>
<link
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000/updateovfstore"
rel="updateovfstore"/>
<link
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000/refreshluns"
rel="refreshluns"/>
<link
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000/isattached"
rel="isattached"/>
</actions>
<name>DC0-aws2-NFS</name>
<link
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000/permissions"
rel="permissions"/>
<link
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000/templates"
rel="templates"/>
<link
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000/vms"
rel="vms"/>
<link
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000/disks"
rel="disks"/>
<link
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000/storageconnections"
rel="storageconnections"/>
<link
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000/disksnapshots"
rel="disksnapshots"/>
<link
href="/ovirt-engine/api/storagedomains/00000000-0000-0000-0000-000000000000/diskprofiles"
rel="diskprofiles"/>
<available>56908316672</available>
<committed>0</committed>
<critical_space_action_blocker>5</critical_space_action_blocker>
<external_status>ok</external_status>
<master>false</master>
<status>unattached</status>
<storage>
<address>PCB1-0-aws2</address>
<path>/data</path>
<type>nfs</type>
</storage>
<storage_format>v3</storage_format>
<type>data</type>
<used>216895848448</used>
<warning_low_space_indicator>10</warning_low_space_indicator>
<wipe_after_delete>false</wipe_after_delete>
</storage_domain>
</storage_domains>
Roy Golan schreef op 2016-10-27 14:23:
On 27 October 2016 at 10:42, <joost(a)familiealbers.nl [3]>
wrote:
> Hi All, i have two ovirt / fakevdsm questions.
>
> I am using fakevdsm to test my ovirt 4.0.5 engine.
> I have a somewhat awkward setup where i have a relatively large
> amount of dcs.
> I cannot get nfs master domain to work from the api.
> The api code is solid and is used on a ovirt-engine 3.5 production
> cluster.
I am not sure this is an ovirt of fakevdsm issue. When i manually
add
the nfs storage domain it does get created whic
> e="margin:0px 0px 0px 0.8ex;border-left:1px solid
> rgb(204,204,204);padding-left:1ex"> My real aim would be to run 500
> dcs with 2 hosts and a
br>
Youd have to have a host per DC, cause every DC has an SPM. You meant
cluster or Im missing something.
Links:
------
[1] https://gerrit.ovirt.org/65804
[2] mailto:Users@ovirt.org
[3] mailto:joost@familiealbers.nl
10:08 p.m.
I might have mixed up some items here, please ignore my previous email
and thank you for the info on setting the option to let ovirt use
hostnames
I think i have been looking at the screen for too long.
thanks!
Roy Golan schreef op 2016-10-27 14:23:
On 27 October 2016 at 10:42, <joost(a)familiealbers.nl [3]>
wrote:
> Hi All, i have two ovirt / fakevdsm questions.
>
> I am using fakevdsm to test my ovirt 4.0.5 engine.
> I have a somewhat awkward setup where i have a relatively large
> amount of dcs.
> I cannot get nfs master domain to work from the api.
> The api code is solid and is used on a ovirt-engine 3.5 production
> cluster.
I am not sure this is an ovirt of fakevdsm issue. When i manually
add
the nfs storage domain it does get created whic
> e="margin:0px 0px 0px 0.8ex;border-left:1px solid
> rgb(204,204,204);padding-left:1ex"> My real aim would be to run 500
> dcs with 2 hosts and a
br>
Youd have to have a host per DC, cause every DC has an SPM. You meant
cluster or Im missing something.
Links:
------
[1] https://gerrit.ovirt.org/65804
[2] mailto:Users@ovirt.org
[3] mailto:joost@familiealbers.nl
2948
days inactive
2948
days old
3 comments
2 participants
participants (2)
-
joost＠familiealbers.nl -
Roy Golan