Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 621899

Summary:	[RFE] Specify a Elastic IP to associate with Amazon Grid instance
Product:	Red Hat Enterprise MRG	Reporter:	Steve Reichard <sreichar>
Component:	condor	Assignee:	Timothy St. Clair <tstclair>
Status:	CLOSED ERRATA	QA Contact:	Luigi Toscano <ltoscano>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.2	CC:	iboverma, jneedle, ltoscano, matt, mhusnain, tstclair
Target Milestone:	2.0	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	condor-7.6.0-0.4	Doc Type:	Enhancement
Doc Text:	C: Inability to bind to a elastic ip for condor ec2 jobs C: A dynamic ip will be created for each instance C: Added support to bind to a an elastic ip specified in the submit file via ec2_elastic_ip parameter R: Ec2 jobs now support binding to an elastic ip. Release Notes Entry: Previously, Condor EC2 jobs could not be bound to an elastic IP, forcing a dynamic IP to be created for each instance. The ec2_elastic_ip parameter is now used to support elastic IP binding for Condor EC2 jobs.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-23 15:42:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	679553
Bug Blocks:	693778

Description Steve Reichard 2010-08-06 12:49:31 UTC

Description of problem:

I have been attempting to use the MRG Grid to allocate Grid exec node for a application.   Because of the corp firewall,  I need to have a host outside the firewall that will tunnel my requests into the firewall.  Using a well known IP for this machine allows the configuration to be more or less static on the grid nodes.  
I attempted to use a EC2 instance spawned from MRG Grid for this node.  I had to resort to using either the EC2 command line tools or web console to associate the elastic IP to the instance. If this could be incorporated into the submit file, MRG would be self reliant for submitting jobs.  

Version-Release number of selected component (if applicable):
version 1.2

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Timothy St. Clair 2011-03-28 18:53:45 UTC

Is the preferred method to associate with a pre-established ElasticIP, or to Alloc a new address for every run and only care about the public IP?  

See 

http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/index.html?ApiReference-query-AssociateAddress.html

vs.

http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/index.html?ApiReference-query-AllocateAddress.html

Comment 3 Timothy St. Clair 2011-03-28 20:24:11 UTC

per conversation w/mattf, use associate.

Comment 4 Timothy St. Clair 2011-03-30 05:52:58 UTC

Modification will attempt to associate but will not block running if it fails (e.g. already in use).  The logs will contain the reason for failure.

Comment 6 Timothy St. Clair 2011-05-04 16:29:16 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
C: Inability to bind to a elastic ip for condor ec2 jobs
C: A dynamic ip will be created for each instance
C: Added support to bind to a an elastic ip specified in the submit file via ec2_elastic_ip parameter
R: Ec2 jobs now support binding to an elastic ip.

Comment 8 Misha H. Ali 2011-05-27 04:40:56 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1,7 @@
 C: Inability to bind to a elastic ip for condor ec2 jobs
 C: A dynamic ip will be created for each instance
 C: Added support to bind to a an elastic ip specified in the submit file via ec2_elastic_ip parameter
-R: Ec2 jobs now support binding to an elastic ip.+R: Ec2 jobs now support binding to an elastic ip.
+
+Release Notes Entry: 
+Previously, Condor EC2 jobs could not be bound to an elastic IP, forcing a dynamic IP to be created for each instance. The ec2_elastic_ip parameter is now used to support elastic IP binding for Condor EC2 jobs.

Comment 11 Luigi Toscano 2011-06-02 15:29:22 UTC

In order to make it working on EC2/Enhanced jobs, use
+EC2ElasticIp="YOUR.IP.AD.DR"
in the job submission file.


The feature work as expected: the last job which request the IP takes it (it works for both EC2/basic and EC2/Enhanced).
Verified on RHEL5.6/6.1, i386/x86_64.
condor-7.6.1-0.8

Comment 12 Misha H. Ali 2011-06-06 03:23:29 UTC

Technical note can be viewed in the release notes for 2.0 at the documentation stage here:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.0/html-single/MRG_Release_Notes/index.html#tabl-MRG_Release_Notes-GRID_Update_Notes-RHM_Known_Issues

Comment 13 errata-xmlrpc 2011-06-23 15:42:08 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0889.html