The "Writing your first OpenStack application" book contains code that does not work with OpenStack installations that use private IP's as public IP's
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-api-site |
Confirmed
|
Medium
|
Martin Paulo |
Bug Description
The sample libcloud code from the "Writing your first OpenStack application" book, in the "Getting Started" chapter will fail if run on an installation that that doesn't provide floating IP's - if it uses private IP's as public IP's.
Further, if floating IP's are supported, it will try to allocate a floating IP even if a public IP is assigned: and then not attach it. Given I'm on one of the aforesaid clouds that use private IP's as public IP's, this might be the correct behavior, but it strikes me as strange.
Lastly, if the aforesaid installation enables floating IP pools, but doesn't let them to dish out IP addresses, the code fails as well. Again, I'm on one such cloud.
Having checked out the api repository I think that these issues exist across all of the supported languages that cover this chapter, not just the libcloud implementation.
Changed in openstack-api-site: | |
assignee: | nobody → Martin Paulo (martin-paulo) |
Changed in openstack-api-site: | |
milestone: | none → mitaka |
Would you describe which IP address is problematic?
Also developer. openstack. org/firstapp- libcloud/ getting_ started. html
From seeing following URL
http://
It describes
Note
If you do not use floating IPs, substitute another IP address as appropriate