[jboss-jira] [JBoss JIRA] Commented: (JBAS-8001) Greater flexibility in picking bind address

Bela Ban (JIRA) jira-events at lists.jboss.org
Tue May 11 02:45:05 EDT 2010


    [ https://jira.jboss.org/jira/browse/JBAS-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12530044#action_12530044 ] 

Bela Ban commented on JBAS-8001:
--------------------------------

I forgot to comment what the above code does... :-)

If bind_addr is set in XML, we have a PropertyConverter (used by @Property) which creates an InetAddress from the string value.

If the system property jgroups.bind_addr (Global.BIND_ADDR) or jgroups.bindaddress (Global.BIND_ADDR_OLD) is set, it will override the value set in the XML config.

If, after this, bind_addr is still null, we'll set it to a default value defined in @Property, based on whether IPv4 or IPv6 is used.

I know JBoss AS has annotations to expose attrs and methods for management (JMX), and the above @Property annotations could be used to easily set values as well.

> Greater flexibility in picking bind address
> -------------------------------------------
>
>                 Key: JBAS-8001
>                 URL: https://jira.jboss.org/jira/browse/JBAS-8001
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>
> Consider adding a capability to the AS along the lines of what Bela did in JGRP-1204.
> An explanatory comment re JGRP-1204 from Bela:
> > might be interesting for you if you want to make JGroups bind to a certain *type* of IP address, but don't know the exact address before startup.
> > 
> > For example, in a cloud environment, you don't usually know the IP address assigned to you instance beforehand, unless you use elastic IPs and dyndns.org entries, for example.
> >
> > Since cloud provider often charge you for outgoing traffic on public IPs, you don't want replication or distribution traffic to go out over public IPs ! You rather want this type of traffic to use internal IP address, for  
> > which some provider (e.g. GoGrid) don't charge.
> >
> > This can be done by setting bind_addr or -Djgroups.bind_addr to a keyword rather than a dotted decimal or symbolic IP address:
> >
> >   * GLOBAL: pick a public IP address. You want to avoid this for
> >     replication traffic
> >   * SITE_LOCAL: use a private IP address, e.g. 192.168.x.x. This
> >     avoids charges for bandwith from GoGrid, for example
> >   * LINK_LOCAL: use a 169.x.x.x, 254.0.0.0 address. I've never used
> >     this, but this would be for traffic only within 1 box
> >   * NON_LOOPBACK: use the first address found on an interface (which
> >     is up), which is not a 127.x.x.x address
> >
> > For my could mod-cluster demo, I set bind address to SITE_LOCAL. This works for GoGrid, need to see whether this is also true for EC2 and Rackspace 
> This also has implications for the AS 7 domain model.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list