tr3buchet,
Thanks for making this use case explicit. This is sort of what I was guessing,
but it is nice to see it spelled out. With this use case, perhaps it will no
longer make sense for the openstack api to bother with floating ips at all,
since there won't really be a place for them to fi
Mark, in our use case that (public ip for free per instance) wouldn't
change. Our use case doesn't involve floating IPs (yet). We'll have flat
networks for both "public" and "private", as we define them. The way nova is
currently implemented, all of these addresses would be considered "private"
whe
Thanks to all for answers!
It seems that API for floating ips needs to be discussed.
For approach #1 we already have implementation, and it seems that approach
#3 and approach #1 aim little bit different use cases.
Approach #3 give us ability to work with floating ips using OpenStack API
and appr
Perhaps I misunderstood. I thought option #3 consisted of adding new http
resources to the openstack api to expose the add/allocate/associate/etc
floating ip functionality to the api consumer.
If that is the case, I believe it would be a break with the cloud servers 1.0
api, where a customer
I like the simple solution (#3) as well.
It gets parity for the APIs while leaving more advanced topics for the NaaS
discussions.
-- Sent from my Tandy 1000sx
Jesse Andrews
anotherje...@gmail.com
On Apr 18, 2011, at 11:36 AM, Trey Morris wrote:
> Appears my response got lost somehow. I vote
Appears my response got lost somehow. I vote for #3 as it's the most
configurable (and affects nothing contrariwise). In addition to believing we
use flags too often, I don't think having a flag solves the problem very
well. A couple of examples show why:
you want a few instances having floating IP
Mark,
approach #1 implementation is here:
https://code.launchpad.net/~openstack-gd/nova/auto-float-ip. I saw that you
interested in approach #3 too. May be you have some ideas of specification
of API for approach #3?
Erik,
there is implementation of floating ips in Nova. In implementation of
appr
Eldar,
I'm having some trouble finding the diff for your implementation of approach
#1. Any chance you can share it on the list?
Thanks
"Erik Carlin" said:
> Cool. Got it. Floating IPs or what Amazon calls Elastic IPs. How are you
> solving the cross L2 problem?
>
> Erik
>
> Sent fro
Cool. Got it. Floating IPs or what Amazon calls Elastic IPs. How are you
solving the cross L2 problem?
Erik
Sent from my iPhone
On Apr 15, 2011, at 7:28 PM, "Eldar Nugaev" wrote:
> Hi Erik
>
> Thank you for response!
> Yes, you are absolutely right OpenStack API already support shared IP
Hi Erik
Thank you for response!
Yes, you are absolutely right OpenStack API already support shared IP groups.
Suppose there are some misunderstanding, because I wrote about floating IPs.
I want to have API for association IPs from floating IPs pool with
particular VM.
At this moment we have #1 i
Eldar -
The OpenStack API already supports sharing IPs between instances (although
this may be an extension?). What exact behavior are you after? More
important than the way in which we expose via the API is how it's
implemented. It's important to note that this is extremely network
topology de
> 1. FLAG --auto_assign_floating_ip (default=False)
> 2. Optional parameter "auto_assign_floating_ip" in existing "create" method
> 3. OpenStack API add floating_ip - allocate_floating_ip, associate_floating_ip
>
> What way is more suitable at this time?
I think primarily #1, with some degree of
Hello everyone,
We going to add possibility to assigning floating IP addresses in OpenStack API.
Our goal reproduce AWS behavior when creating instance automatically
assigns any free floating IP or add methods to OpenStack API for
allocation and association API addresses.
At this time we see thre
13 matches
Mail list logo
