Project

General

Profile

Actions
Copy link

Feature #5999

closed

Support assigning public IP to Amazon EC2 host

Added by cristian falcas over 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Compute resources - EC2
Target version:
1.7.1
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/1932
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hello,

When creating a new host on an amazon compute resource and choosing for the "Managed IP" Public, no real IP is assigned to the machine.

We are using VPCs and not EC2.

We have a "nat" role that should also use some awscli commands in order to configure itself. Because no real IP is assigned, those commands timeout and fail, so we need to manually add an IP and rerun puppet.

I didn't see anything relevant in the logs, so please let me know if you want anything from our side regarding this.

Best regards,
Cristian Falcas

Related issues 3 (2 open — 1 closed)

Related to Foreman - Feature #7072: More EC2 IntegrationNew08/13/2014Actions
Related to Foreman - Feature #3521: Assign a specific IP to an AWS instance inside a VPCNewDaniel Lobato Garcia10/25/2013Actions
Has duplicate Foreman - Feature #6818: Add Public IP option to AWS hostsDuplicate07/29/2014Actions
Actions
Copy link
 #1

Updated by Dominic Cleal over 10 years ago

  • Category set to Compute resources

It's worth noting that the "Managed IP" is about which IP Foreman picks to try and contact the new VM on, rather than having any impact on how the VM is created and which IP it's allocated. I'm not sure how the latter works.

Actions
Copy link
 #2

Updated by cristian falcas over 10 years ago

I was thinking about this feature more:

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-ip-addressing.html#vpc-public-ip

Thank you for your response, please close this issue then.

Actions
Copy link
 #3

Updated by Dominic Cleal over 10 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from on amazon compute resource, choosing public ip is not working to Support assigning public IP to Amazon EC2 host

Let's rephrase it as a feature request :)

Actions
Copy link
 #4

Updated by cristian falcas over 10 years ago

Thank you Dominic.

Actions
Copy link
 #5

Updated by Dominic Cleal over 10 years ago

  • Has duplicate Feature #6818: Add Public IP option to AWS hosts added
Actions
Copy link
 #6

Updated by Dominic Cleal about 10 years ago

  • Category changed from Compute resources to Compute resources - EC2
Actions
Copy link
 #7

Updated by Dominic Cleal about 10 years ago

Actions
Copy link
 #8

Updated by Dominic Cleal about 10 years ago

  • Related to Feature #3521: Assign a specific IP to an AWS instance inside a VPC added
Actions
Copy link
 #9

Updated by Dominic Cleal about 10 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 1.7.2
  • Pull request https://github.com/theforeman/foreman/pull/1932 added
Actions
Copy link
 #10

Updated by Henrik Feldt about 10 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #11

Updated by Dominic Cleal about 10 years ago

  • Translation missing: en.field_release set to 29
Actions
Copy link

Also available in: Atom PDF