- On Jun 27, 2022, at 3:54 PM, kgaillot kgail...@redhat.com wrote:
> As an aside, the preferred naming for custom agents is to change the
> provider (ocf:PROVIDER:AGENT), putting them in
> /usr/lib/ocf/resource.d/PROVIDER/AGENT.
>
> For example, ocf:local:VirtualDomain or
As an aside, the preferred naming for custom agents is to change the
provider (ocf:PROVIDER:AGENT), putting them in
/usr/lib/ocf/resource.d/PROVIDER/AGENT.
For example, ocf:local:VirtualDomain or ocf:mcd:VirtualDomain
The main advantage is having your own namespace and not having to worry
about
- On Jun 27, 2022, at 2:57 PM, Oyvind Albrigtsen oalbr...@redhat.com wrote:
> You need to update the agent name in the metadata section to be the
> same as the filename.
>
>
> Oyvind
>
OMG. Thank you !!!
Bernd
smime.p7s
Description: S/MIME Cryptographic Signature
You need to update the agent name in the metadata section to be the
same as the filename.
Oyvind
On 27/06/22 14:54 +0200, Lentes, Bernd wrote:
Hi,
i adapted the RA ocf/heartbeat/VirtualDomain to my needs and renamed it to
VirtualDomain.ssh
When i try to use it now, i get an error message.
I
Hi,
i adapted the RA ocf/heartbeat/VirtualDomain to my needs and renamed it to
VirtualDomain.ssh
When i try to use it now, i get an error message.
I start e.g. "crm configure edit vm-idcc-devel" to modify an existing
VirtualDomain that it uses the new RA
and want to save it i get the following
