Re: [Openstack] Floating IP in OS API
Hy Thierry. Yes, we should make it before June 27th. If we have any problem, we inform you about retargeting this task. Thank you! On Thu, Jun 16, 2011 at 11:16 AM, Thierry Carrez thie...@openstack.org wrote: Eldar Nugaev wrote: Let me present the full specification (http://wiki.openstack.org/os_api_floating_ip) for the blueprint (https://blueprints.launchpad.net/nova/+spec/openstack-api-floating-ips) Any response from the community about the spec is very important for us. Hey Eldar, This is targeted to diablo-2, which means it needs to get in before Monday June 27th... Do you think you can make it, or is it more reasonable to target it to diablo-3 (end of July) now ? Thanks for your input. -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Floating IP in OS API
Hi OS developers. Let me present the full specification (http://wiki.openstack.org/os_api_floating_ip) for the blueprint (https://blueprints.launchpad.net/nova/+spec/openstack-api-floating-ips) Any response from the community about the spec is very important for us. -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Nova] Unassigned essential Diablo specs
Hi Thierry We are interested in Add support for floating IPs in the OpenStack API (diablo-2, Jun 30) https://blueprints.launchpad.net/nova/+spec/openstack-api-floating-ips And can implement this feature, but we are looking for creation common vision with the community about approaches of implementation. And Implement clear rest API for volumes (targeted at diablo-2, Jun 30) is very interesting blueprint too. https://blueprints.launchpad.net/nova/+spec/implement-volume-api So we going to take these blueprints. Please assign them to the ElKirya team https://launchpad.net/~elkirya Eldar On Wed, May 18, 2011 at 1:59 PM, Thierry Carrez thie...@openstack.org wrote: Hello Nova developers, In the plan that Vish came up with for Diablo[1], we have a number of essential specs that do not have an assignee. [1] https://blueprints.launchpad.net/nova/diablo This is an issue, since Essential specs are supposed to delay the Diablo release if they are not completed, and not having someone that is committed to deliver the feature sounds like the first step to certain failure. Here they are: Implement clear rest API for volumes (targeted at diablo-2, Jun 30) https://blueprints.launchpad.net/nova/+spec/implement-volume-api This is an essential piece of the decoupling of the volume code. Justin, you seemed to be interested ? Anyone else that could take it ? EC2 Id compatibility (targeted at diablo-3, Jul 28) https://blueprints.launchpad.net/nova/+spec/ec2-id-compatibilty The nova-instance-referencing work will break EC2 API, and this blueprint is tracking the work that needs to be done to prevent that. Anyone interested ? Other (High) specs that are in the plan but unassigned: Instance Migration (targeted at diablo-2, Jun 30) https://blueprints.launchpad.net/nova/+spec/instance-migration Allow cloud admins to perform maintenance of hosts by enabling shutdown of an instance and moving it to a new host node. Does that fall into Ozone realm, as part of the service-provider-readiness ? Add support for floating IPs in the OpenStack API (diablo-2, Jun 30) https://blueprints.launchpad.net/nova/+spec/openstack-api-floating-ips This should ultimately be deferred to the NaaS API, but we probably need some support for this until that is finalized. Also note that plan to decouple network services is partially assigned: Refactor Networking - assigned to Ryu Ishimoto Implement clear rest API for networks (diablo-3) - unassigned Integrate Network Services (diablo-4) - unassigned Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Problem with values in JSON responses
Hi gents. At this moment we have problem in OS API 1.1. Any JSON response with values doesn't meet specification. Could you please provide information - why we want to see values field in JSON and who is responsable for implementation this specification in OS API 1.1? Also we have broken documentation on openstack.org OS API 1.0 http://docs.openstack.org/cactus/openstack-compute/developer/openstack-compute-api-1.0/content/index.html -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Problem with values in JSON responses
I'm referring to the http://docs.openstack.org/cactus/openstack-compute/developer/openstack-compute-api-1.1/ documentation. There are examples of json responses with values. I suppose we should change documentation to the actual state or change actual state to the documentation. On Tue, May 3, 2011 at 4:58 PM, Jorge Williams jorge.willi...@rackspace.com wrote: On May 3, 2011, at 6:29 PM, Eldar Nugaev wrote: Hi gents. At this moment we have problem in OS API 1.1. Any JSON response with values doesn't meet specification. What specification are you referring to? Could you please provide information - why we want to see values field in JSON and who is responsable for implementation this specification in OS API 1.1? We use values as a first attempt to add extensibility to collections in JSON. We had a lengthy discussion about this at the summit. To summarize: there's no really easy/clean way of doing this as JSON is not extensible. We're currently exploring other approaches, so values may go away in the long term. The 1.1 spec is not set in stone in this regard. Also we have broken documentation on openstack.org OS API 1.0 http://docs.openstack.org/cactus/openstack-compute/developer/openstack-compute-api-1.0/content/index.html Right, Anne -- can you look into this? -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com, and delete the original message. Your cooperation is appreciated. -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Do we need SSL on nova-api ports?
Hi all. So what is the decision? I see three decisions: #1 Replace existed plain http to ssl #2 Add additional ports for ssl (save plain http) #3 Do nothing Eldar On Tue, Apr 26, 2011 at 11:27 AM, Dirk-Willem van Gulik dirk-willem.van.gu...@bbc.co.uk wrote: On 25 Apr 2011, at 19:47, Kirill Shileev wrote: Recently, playing with libcloud against a private openstack installation we realized that 8773 and 8774 ports listened by openstack-nova-api expect plain HTTP. This is something that is rarely allowed in production installations. . Other option would be making this configurable, although not sure why and where the plain HTTP might be justified. Any thoughts, comments? An important side effect of slapping SSL with client/server certs on pretty much all connection is that it makes all sort of governance and validation jobs much easier from an organisational point of view. With more 'reuse' of existing process and validation. The attack footprint/exposed estate now splits in three clean realms: issuing of client cert, security of the TCP and SSL layer - and a specific model for what happens within that connection. With the latter bound by the previous two. Furthermore client validation can be done with narly a secret in sight. So for those reasons alone - SSLis good. Dw. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Floating IP in OpenStack API
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 implementation as a path in our RPM repo http://yum.griddynamics.net/. And going to make the merge proposal to trunk. Also we going to create blueprint about #3 and attach branch to it. Eldar On Sat, Apr 16, 2011 at 2:34 AM, Erik Carlin erik.car...@rackspace.com wrote: 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 dependent. Sharing IPs today requires L2 adjacency so other VMs can GARP for the IP. L2 doesn't work at scale so you need another mechanism. I'm pretty sure the way AWS does it is to have a separate pool of IPs and inject /32 routes higher up that route towards the appropriate VM IP. What are your thoughts around how this would be implemented? Multiple people are working towards an independent Network as a Service external to nova so it may make sense to plug this requirement in there. Erik On 4/11/11 8:31 AM, Eldar Nugaev enug...@griddynamics.com wrote: 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 three way: 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? -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com, and delete the original message. Your cooperation is appreciated. -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Floating IP in OpenStack API
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 three way: 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? -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
