Description of problem: As it stands now we can already associate with a standard elastic ip, the only modification that would be necessary would be to add the allocation id. ec2_elastic_ip = your.elastic.ip.addr : allocation_id
Tracking upstream under: https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=2252
For reference in setting up vpc: http://docs.amazonwebservices.com/AmazonVPC/latest/UserGuide/
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: Request for VPC support for ec2_gahp C: Prior to feature support, images could not join a virtual private cloud. C: Added params to allow AMI(s) to join a VPC during initialization R: AMI(s) can now join virtual private clouds
The VPC subnet specified by ec2_vpc_subnet is passed to the AMI and set for it. When ec2_vpc_ip is specified, it is passed to the AMI if available and used to configure it; otherwise, if the IP is already taken, the job is put on HOLD with a proper error message. ec2_elastic_ip for elastic VPC addresses is not supported at this time. Verified on RHEL5.7/6.1, i386/x86_64. condor-7.6.3-0.3 condor-classads-7.6.3-0.3
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/RHSA-2011-1249.html