[ClusterLabs] Antw: [EXT] Re: crm shell: "params param"?

[Ulrich Windl]

>>> Xin Liang <XLiang at suse.com> schrieb am 16.12.2020 um 17:49 in Nachricht
<HE1PR04MB32095093006D9002F0859180B0C50 at HE1PR04MB3209.eurprd04.prod.outlook.com>

> Hi Ulrich,
> 
>> params param config="/etc/libvirt/libxl/test‑jeos.xml
> 
> It seems should raise an error while parse input from command line, since 
> "param" as a RA parameter was not exist

Indeed I found out that "param" (most likely caused by some copy&paste error)
is a parameter named "param" that has no value ;-)
So thats "params param"...

> 
> Thanks for report!
> 
> Regards,
> Xin
> ________________________________
> From: Users <users‑bounces at clusterlabs.org> on behalf of Ulrich Windl 
> <Ulrich.Windl at rz.uni‑regensburg.de>
> Sent: Wednesday, December 16, 2020 10:23 PM
> To: users at clusterlabs.org <users at clusterlabs.org>; Roger Zhou
<ZZhou at suse.com>
> Subject: [ClusterLabs] crm shell: "params param"?
> 
>>>> Ulrich Windl schrieb am 16.12.2020 um 14:53 in Nachricht <5FDA1167.92C :
161 
> :
> 60728>:
> 
> [...]
>> primitive prm_xen_test‑jeos VirtualDomain \
>>         params param config="/etc/libvirt/libxl/test‑jeos.xml"
> 
> BTW: Is "params param" a bug in crm shell? In older crm shell I only see 
> "params"...
> 
>> hypervisor="xen:///system" autoset_utilization_cpu=false
>> autoset_utilization_hv_memory=false \
>>         op start timeout=120 interval=0 \
>>         op stop timeout=180 interval=0 \
>>         op monitor interval=600 timeout=90 \
>>         op migrate_to timeout=300 interval=0 \
>>         op migrate_from timeout=300 interval=0 \
>>         utilization utl_cpu=20 utl_ram=2048 \
>>         meta priority=123 allow‑migrate=true
>>
> [...]
> 
> Regards,
> Ulrich
> 
> 
> 
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/