Hi George and Dave,

Im not sure how but I do have all the parameters in VMs other-config

[root@s3 ~]# xe vm-param-get param-name=other-config
uuid=1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490
auto_poweron: true; vgpu_pci: ; import_task:
OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed:
66442023-d353-6051-c701-47b93aeca922; last_shutdown_time:
20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiator:
internal; last_shutdown_reason: halted; linux_template: true; rhel5: true;

[root@s3 ~]# cat /etc/xensource-inventory
BUILD_NUMBER='61549c'
DOM0_MEM='752'
MANAGEMENT_INTERFACE='xenbr0'
INSTALLATION_UUID='5a17feac-b1bb-4e3d-ad26-374edb6414a0'
COMPANY_NAME_SHORT='xen.org'
PLATFORM_NAME='XCP'
PLATFORM_VERSION='1.6.8'
KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.08.734.170748xen'
BRAND_CONSOLE='a console'
COMPANY_NAME='xen.org'
XEN_VERSION='4.1.3'
PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001'
CONTROL_DOMAIN_UUID='9280c554-38f7-48e8-867b-9c183b2e8b59'
MANAGEMENT_ADDRESS_TYPE='IPv4'
BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2'
INSTALLATION_DATE='2012-11-10 06:30:22.102128'


There is an ambiguity in last_shutdown_time but I think it is there because
I imported it from XCP1.1. ( Notice the host installation data vs vm
shutdown date )

Is it the case that *new* created VMs on XCP1.6 do not have "other-config"
or did I miss anything ?
We also use these fields and they are important for us hence if you confirm
that they are removed in XCP1.6 then I would request to bring them back.


Regards,
Rushikesh







On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin <george.shuk...@gmail.com>wrote:

> Yes, if possible. Those fields was very useful.
>
> Some use cases:
>
> 1) They can be used to detect crashed VM's. If SR is going offline and VM
> mount options says errors=panic, VM is crashing. Those fields allows very
> easy to search for crashed VM and restart them after SR is repaired.
> 2) Status 'crashed' allows to answer customers about reason why their VM
> was rebooted.
> 3) If 'last_shutdown_reason=**rebooted' and VM is not started, that is
> sign of problems (bad boot kernel, grub options or something else).
> 4) last_shutdown_time allows native and very intuitive sorting key for
> halted VM's (if vm was halted recently, it can be on top, and vm with
> shutdown date two years ago naturally can be at the list bottom).
> 5) When some complicated works with infrastructure are planned,
> last_shutdown_time allows to predict if VM will be started soon or not (if
> it was halted recently, it can be started at any time, if vm was halted two
> weeks ago, there is very little chance it will started in near 1-2-3 hrs.)
>
>
> We displays them to client in management interface
>
> 03.01.2013 19:30, Dave Scott пишет:
>
>  Hi George,
>>
>> They weren't deliberately removed -- they were missed when we split
>> xenopsd from xapi. I think they could probably be put back again. Perhaps
>> we should make them first-class fields rather than other-config keys, to
>> make sure they don't go missing again?
>>
>> Out of curiousity, what kind of thing did you use that information for?
>>
>> Thanks,
>> Dave
>>
>>  -----Original Message-----
>>> From: xen-api-boun...@lists.xen.org [mailto:xen-api-
>>> boun...@lists.xen.org] On Behalf Of George Shuklin
>>> Sent: 03 January 2013 3:07 PM
>>> To: xen-api@lists.xen.org
>>> Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator
>>>
>>> Good day.
>>>
>>> Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown
>>> time, reason and initiator. Those was extremely useful metrics and it's
>>> really sad to see lack of them in new version.
>>>
>>> In XCP 1.1 they was placed in other-config:
>>> last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart;
>>> last_shutdown_initiator: external; last_shutdown_reason: rebooted;
>>>
>>> In XCP 1.6 nothing like this is in other-config.
>>>
>>> Is those fields disappear completely or I just miss them?
>>>
>>> Thanks.
>>>
>>> ______________________________**_________________
>>> Xen-api mailing list
>>> Xen-api@lists.xen.org
>>> http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api<http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>
>>>
>>
>
> ______________________________**_________________
> Xen-api mailing list
> Xen-api@lists.xen.org
> http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api<http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>
>
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

Reply via email to