Re: Child vs Resource

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In operation, do the children get started successfully before the parent is started? As opposed to them being started independently?

Is the failures (after everything has been running) handled the same?

    scottb


Ryan McCabe wrote:
On Mon, Nov 19, 2007 at 10:15:22AM -0800, Scott Becker wrote:
  
On luci's configure a service screen, there's a button to 'add a child' 
and another button to 'add a resource to this service'.

I haven't found anything which explains the difference.
    

Adding a child to an existing resource causes the resultant resource to
be nested under the one to which you're adding a child. For example, if
the resource you're adding a child to is named R, then, it will produce
something like:

<service ...>
 <restype name="R">
   <new_resource_here />
 </restype>
</service>

Clicking the 'add a resource to this service' button causes a new
resource to be added to the end of the service block. For example:

<service ...>
 <restype name="resource0">
   <optional_nested_resources />
 </restype>
 ...
 <restype name="resourceN" />

 <new_resource_here />
</service>


Ryan

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
  
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux