Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow config.floating_ip_pool to take an array as input #90

Closed
julienvey opened this issue Sep 5, 2014 · 2 comments
Closed

Allow config.floating_ip_pool to take an array as input #90

julienvey opened this issue Sep 5, 2014 · 2 comments
Assignees
Milestone

Comments

@julienvey
Copy link
Collaborator

both syntax would be accepted

os.floating_ip_pool = 'PublicNetwork1'
os.floating_ip_pool = ['PublicNetwork1', 'PublicNetwork2'] 

with the second syntax, we would try to allocate or use an IP from one or the other

@julienvey julienvey added this to the 0.5 milestone Sep 24, 2014
@julienvey julienvey self-assigned this Sep 24, 2014
@julienvey julienvey modified the milestones: 0.5, 0.6 Oct 3, 2014
@julienvey julienvey removed their assignment Oct 15, 2014
@ggiamarchi
Copy link
Owner

Expected behavior :
When resolving floating IP, if an IP is already allocated in any of the pools from the list we take it. If no IP is eligible from the ones already allocated, we try to allocate one from the first pool from the list. If it succeed we take it, if it fails for any reason we try the second one. And we repeat that until we get an IP or until we reach the end of the list. If we finally cannot allocate a floating IP we will fail.

@simonmazas
Copy link
Contributor

I take this one

simonmazas added a commit to simonmazas/vagrant-openstack-provider that referenced this issue Nov 7, 2014
simonmazas added a commit to simonmazas/vagrant-openstack-provider that referenced this issue Nov 7, 2014
simonmazas added a commit to simonmazas/vagrant-openstack-provider that referenced this issue Nov 7, 2014
simonmazas added a commit to simonmazas/vagrant-openstack-provider that referenced this issue Nov 10, 2014
simonmazas added a commit to simonmazas/vagrant-openstack-provider that referenced this issue Nov 14, 2014
simonmazas added a commit to simonmazas/vagrant-openstack-provider that referenced this issue Nov 14, 2014
simonmazas added a commit to simonmazas/vagrant-openstack-provider that referenced this issue Nov 14, 2014
simonmazas added a commit to simonmazas/vagrant-openstack-provider that referenced this issue Nov 14, 2014
ggiamarchi added a commit that referenced this issue Nov 16, 2014
Sharpie pushed a commit to Sharpie/vagrant-openstack-provider that referenced this issue Jan 18, 2016
Sharpie pushed a commit to Sharpie/vagrant-openstack-provider that referenced this issue Jan 18, 2016
Sharpie pushed a commit to Sharpie/vagrant-openstack-provider that referenced this issue Jan 18, 2016
Sharpie pushed a commit to Sharpie/vagrant-openstack-provider that referenced this issue Jan 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants