Sponsored Content
Full Discussion: Cluster a custom application
Top Forums UNIX for Beginners Questions & Answers Cluster a custom application Post 303034461 by rbatte1 on Friday 26th of April 2019 11:26:39 AM
Old 04-26-2019
It might be clearer if you took this bit:
Quote:
*************(floating IP)************
| ***route all traffic on every port ***|
| ******************************************|
ServerA*************************** ServerB
(APP) **************************(Stopped App)
.... and wrapped it in CODE tags, the edited it to look how you would like.

Wrapping in CODE tags will respect the spaces which is important for indenting or fixed-width data, or in your case a text-based diagram. I've tried, but I'm not quite sure what you want to show.


A short tutorial is included below. The look/feel of the forum has changed, as have the buttons, but method 1 still works just fine.



Kind regards,
Robin
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to custom application name in `ps -ef`?

A program named /usr/bin/aa.sh, two parameters: 11, 22. after start it, the row in `ps -ef` is almost like the following: root 12198 10278 0.0 Nov 25 pts/3 0:00.23 /usr/bin/aa.sh 11 22 but I want to change "/usr/bin/aa.sh 11 22" to one rule string, such as: "AA_11_22", how to... (1 Reply)
Discussion started by: linkjack
1 Replies

2. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

3. HP-UX

Install application on UNIX cluster

Hi everyone, I have a new engagement where in I would need to install an inhouse server application in a HP_UNIX cluster. Please let me know how this should be done. Satish (4 Replies)
Discussion started by: satish_000
4 Replies

4. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies

5. AIX

How to add node to the cluster with stoping the application?

In the production hacmp 5.3 is running with three nodes but i want to add new node to cluster with out stopping the application ie with same resource group if any bady know pls help me. (1 Reply)
Discussion started by: manjunath.m
1 Replies

6. Red Hat

Custom HA agent - Red Hat Linux Cluster

Hi experts, I have some custom application which I need to make Highly Available using red hat cluster service. How do I do it? i know in /usr/share/cluster i shall find HA agents for well known services like Apache or Sybase but I want to write HA agent for my own. I tried looking up on... (4 Replies)
Discussion started by: pshaikh
4 Replies

7. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

8. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
Mojolicious::Routes::Route(3pm) 			User Contributed Perl Documentation			   Mojolicious::Routes::Route(3pm)

NAME
Mojolicious::Routes::Route - Route container SYNOPSIS
use Mojolicious::Routes::Route; my $r = Mojolicious::Routes::Route->new; DESCRIPTION
Mojolicious::Routes::Route is the route container used by Mojolicious::Routes. ATTRIBUTES
Mojolicious::Routes::Route implements the following attributes. "children" my $children = $r->children; $r = $r->children([Mojolicious::Routes::Route->new]); The children of this route, used for nesting routes. "inline" my $inline = $r->inline; $r = $r->inline(1); Allow "bridge" semantics for this route. "parent" my $parent = $r->parent; $r = $r->parent(Mojolicious::Routes::Route->new); The parent of this route, used for nesting routes. "partial" my $partial = $r->partial; $r = $r->partial(1); Route has no specific end, remaining characters will be captured in "path". "pattern" my $pattern = $r->pattern; $r = $r->pattern(Mojolicious::Routes::Pattern->new); Pattern for this route, defaults to a Mojolicious::Routes::Pattern object. METHODS
Mojolicious::Routes::Route inherits all methods from Mojo::Base and implements the following ones. "new" my $r = Mojolicious::Routes::Route->new; my $r = Mojolicious::Routes::Route->new('/:controller/:action'); Construct a new Mojolicious::Routes::Route object. "add_child" $r = $r->add_child(Mojolicious::Route->new); Add a new child to this route, it will be automatically removed from its current parent if necessary. # Reattach route $r->add_child($r->find('foo')); "any" my $route = $r->any('/:foo' => sub {...}); my $route = $r->any([qw(GET POST)] => '/:foo' => sub {...}); Generate route matching any of the listed HTTP request methods or all. See also the Mojolicious::Lite tutorial for more argument variations. $r->any('/user')->to('user#whatever'); "bridge" my $bridge = $r->bridge; my $bridge = $r->bridge('/:action'); my $bridge = $r->bridge('/:action', action => qr/w+/); my $bridge = $r->bridge(format => 0); Generate bridge. my $auth = $r->bridge('/user')->to('user#auth'); $auth->get('/show')->to('#show'); $auth->post('/create')->to('#create'); "delete" my $route = $r->delete('/:foo' => sub {...}); Generate route matching only "DELETE" requests. See also the Mojolicious::Lite tutorial for more argument variations. $r->delete('/user')->to('user#remove'); "detour" $r = $r->detour(action => 'foo'); $r = $r->detour({action => 'foo'}); $r = $r->detour('controller#action'); $r = $r->detour('controller#action', foo => 'bar'); $r = $r->detour('controller#action', {foo => 'bar'}); $r = $r->detour($app); $r = $r->detour($app, foo => 'bar'); $r = $r->detour($app, {foo => 'bar'}); $r = $r->detour('MyApp'); $r = $r->detour('MyApp', foo => 'bar'); $r = $r->detour('MyApp', {foo => 'bar'}); Set default parameters for this route and allow partial matching to simplify application embedding. "find" my $route = $r->find('foo'); Find child route by name, custom names have precedence over automatically generated ones. $r->find('show_user')->to(foo => 'bar'); "get" my $route = $r->get('/:foo' => sub {...}); Generate route matching only "GET" requests. See also the Mojolicious::Lite tutorial for more argument variations. $r->get('/user')->to('user#show'); "has_conditions" my $success = $r->has_conditions; Check if this route has active conditions. "has_custom_name" my $success = $r->has_custom_name; Check if this route has a custom name. "has_websocket" my $success = $r->has_websocket; Check if this route has a WebSocket ancestor. "is_endpoint" my $success = $r->is_endpoint; Check if this route qualifies as an endpoint. "is_websocket" my $success = $r->is_websocket; Check if this route is a WebSocket. "name" my $name = $r->name; $r = $r->name('foo'); The name of this route, defaults to an automatically generated name based on the route pattern. Note that the name "current" is reserved for refering to the current route. $r->get('/user')->to('user#show')->name('show_user'); "options" my $route = $r->options('/:foo' => sub {...}); Generate route matching only "OPTIONS" requests. See also the Mojolicious::Lite tutorial for more argument variations. $r->options('/user')->to('user#overview'); "over" my $over = $r->over; $r = $r->over(foo => qr/w+/); Activate conditions for this route. Note that this automatically disables the routing cache, since conditions are too complex for caching. $r->get('/foo')->over(host => qr/mojolicio.us/)->to('foo#bar'); "parse" $r = $r->parse('/:action'); $r = $r->parse('/:action', action => qr/w+/); $r = $r->parse(format => 0); Parse a pattern. "patch" my $route = $r->patch('/:foo' => sub {...}); Generate route matching only "PATCH" requests. See also the Mojolicious::Lite tutorial for more argument variations. $r->patch('/user')->to('user#update'); "post" my $route = $r->post('/:foo' => sub {...}); Generate route matching only "POST" requests. See also the Mojolicious::Lite tutorial for more argument variations. $r->post('/user')->to('user#create'); "put" my $route = $r->put('/:foo' => sub {...}); Generate route matching only "PUT" requests. See also the Mojolicious::Lite tutorial for more argument variations. $r->put('/user')->to('user#replace'); "remove" $r = $r->remove; Remove route from parent. # Remove route completely $r->find('foo')->remove; # Reattach route to new parent $r->route('/foo')->add_child($r->find('bar')->remove); "render" my $path = $r->render($suffix); my $path = $r->render($suffix, {foo => 'bar'}); Render route with parameters into a path. "root" my $root = $r->root; The Mojolicious::Routes object this route is an ancestor of. $r->root->cache(0); "route" my $route = $r->route; my $route = $r->route('/:action'); my $route = $r->route('/:action', action => qr/w+/); my $route = $r->route(format => 0); Generate route matching all HTTP request methods. "to" $r = $r->to(action => 'foo'); $r = $r->to({action => 'foo'}); $r = $r->to('controller#action'); $r = $r->to('controller#action', foo => 'bar'); $r = $r->to('controller#action', {foo => 'bar'}); $r = $r->to($app); $r = $r->to($app, foo => 'bar'); $r = $r->to($app, {foo => 'bar'}); $r = $r->to('MyApp'); $r = $r->to('MyApp', foo => 'bar'); $r = $r->to('MyApp', {foo => 'bar'}); Set default parameters for this route. "to_string" my $string = $r->to_string; Stringify the whole route. "under" my $route = $r->under(sub {...}); my $route = $r->under('/:foo'); Generate bridge. See also the Mojolicious::Lite tutorial for more argument variations. my $auth = $r->under('/user')->to('user#auth'); $auth->get('/show')->to('#show'); $auth->post('/create')->to('#create'); "via" my $methods = $r->via; $r = $r->via('GET'); $r = $r->via(qw(GET POST)); $r = $r->via([qw(GET POST)]); Restrict HTTP methods this route is allowed to handle, defaults to no restrictions. $r->route('/foo')->via(qw(GET POST))->to('foo#bar'); "websocket" my $websocket = $r->websocket('/:foo' => sub {...}); Generate route matching only "WebSocket" handshakes. See also the Mojolicious::Lite tutorial for more argument variations. $r->websocket('/echo')->to('example#echo'); SHORTCUTS
In addition to the attributes and methods above you can also call shortcuts on Mojolicious::Routes::Route objects. $r->root->add_shortcut(firefox => sub { my ($r, $path) = @_; $r->get($path, agent => qr/Firefox/); }); $r->firefox('/welcome')->to('firefox#welcome'); $r->firefox('/bye')->to('firefox#bye); SEE ALSO
Mojolicious, Mojolicious::Guides, <http://mojolicio.us>. perl v5.14.2 2012-09-05 Mojolicious::Routes::Route(3pm)
All times are GMT -4. The time now is 11:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy