Re: [Openstack] How to assign External ip to vm without quantum L3 agent
Hi Aron, Do we have any sample provider network extension available in Grizzly Release. If so, Can you please share that information. Any other information on this will be appreciated. Thanks, Balaji.P On Thu, May 30, 2013 at 11:37 AM, Aaron Rosen aro...@nicira.com wrote: No but the provider network extention does provide a way to do this that might work for your usecase: http://docs.openstack.org/trunk/openstack-network/admin/content/provider_networks.html On Wed, May 29, 2013 at 11:02 PM, Veera Reddy veerare...@gmail.comwrote: Hi, IS there any way to access VM from external network without using quantum l3 agent. -- Regards, VeeraReddy.B ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] TC candidacy
+1 On Fri, Mar 22, 2013 at 7:33 PM, Monty Taylor mord...@inaugust.com wrote: I confirm that Vishvananda is eligible to run for a seat on the TC. On 03/15/2013 05:41 PM, Vishvananda Ishaya wrote: Hello all, I would like to run for a seat on The Technical Comittee. I have been working on Nova since it was a project as Nasa and I have been heavily involved in openstack since it was founded. I was elected to the precursor to TC (the Project Oversight Committee, later named the Project Policy Board) when it was first created. I was also elected as the first PTL for Nova and have been filling that role for the last two years. I am the top contributor to Nova over the lifetime of the project, and the third most frequent contributor over the past 12 months. I helped to create Devstack, Keystone, and Cinder. In addition, I have contributed to Oslo and I am a member of the stable-maintenance team. Despite passing on the mantle of Nova PTL, I am still deeply involved with OpenStack and I want to make sure that it continues to be a huge success. As OpenStack grows, one of the most important challenges we face is integration. It is vital that we have technical leaders that are focused cross-project and dedicated to making OpenStack as a whole successful. I currently work as the Director of Open Source at Nebula, Inc. Previously I was a principal engineer on the private cloud team at Rackspace, and before that I was a senior developer on the Nebula project at NASA where Nova was created. Thanks, Vish ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] TC candidacy
+1 On Fri, Mar 22, 2013 at 7:30 PM, Monty Taylor mord...@inaugust.com wrote: I confirm that Thierry is eligible to run for a seat on the TC. On 03/15/2013 11:32 AM, Thierry Carrez wrote: Hi everyone, I'd like to run for reelection to one of the Technical Committee directly-elected seats. For those who don't know me, I've been handling release management duties for OpenStack since November 2010, a work currently sponsored by the OpenStack Foundation. My involvement is mostly around project coordination, keeping a global view and trying to anticipate issues as our development community grows even larger. I'm also heading the Vulnerability Management team, which handles incoming security issues reports. On the development side, I authored the rootwrap framework which is being used by a few of our projects, and whenever I find some free time, I'm working on improving it. I've been regularly elected by our community to the Project Policy Board and Technical Committee directly-elected seats for the last two years. I was heavily involved in the transition to our new governance, authored the Technical Committee charter, and have been chosen to chair it for the past 6 months. I think it's important that the Technical Committee contains representation from the horizontal functions within the project (Docs, QA, Infrastructure, Vulnerability management, Release management...), since each project is already represented by the seats granted for all PTLs. Over the last 30 months we grew from 2 projects to 10 projects, and I'm proud to be part of this community which successfully managed to handle growth and adoption while preserving our ideals of open design and open development. The challenges ahead of us include accommodating further growth, resist fragmentation, and maintaining efficiency and coherence as we grow well past Dunbar's number. I hope that you place me in a position where I can help us through those challenges. Thanks, ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] [Quantum] Need suggestion on networking
Do we have any other way to reach VM public IPs, with out using name space nat router gvien in the below link. Lets say that i will configure my dhcp-agent with the pool of Public IPs, which will be assigned to VMs by Quantum. Iam curious that if there is any possible setup which we can create with out using name space NAT router. balaji On Thu, Mar 21, 2013 at 7:21 AM, Dan Wendlandt d...@nicira.com wrote: if you want private networks, but also to give VMs public IPs, you will want to create one or more private networks + subnets, create a router, uplink each subnet to the router, create an external network + subnet using your public IPs, and then allocate a floating ip for each VM that needs a public address. You can mostly follow the workflow outlined here: http://docs.openstack.org/trunk/openstack-network/admin/content/l3_workflow.html dan On Wed, Feb 20, 2013 at 2:57 AM, Anil Vishnoi vishnoia...@gmail.comwrote: Hi, I did Openstack(Folsom+Quantum) setup, with one controller node ( also running networking services) and 8 compute nodes. Both controller node and compute nodes have 2 NIC each, one on public network (internet) and one on private network. My requirement is that for each tenant, every VM should be connected to private network as well as it should also have public IP address, so that user can directly access that machine over internet. I might add some more compute node as well, and my VM counts can grow in range of 200-300+. You can assume that we do have these many public IP's available. My plan is to create vlan based private network for each tenant, but i am confused on the public network part of it. Shell i use provider network or use router/floating ip based networking. I want to user openvswtich (vlan) plugin for networking.Any suggestions? Thanks Anil ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Name
+1 for Havana. On Fri, Jan 25, 2013 at 1:36 AM, Tim Bell tim.b...@cern.ch wrote: ** ** There is also Robin Hood (http://en.wikipedia.org/wiki/Robin_hood) … “steal from the rich and give to the poor”… ** ** Personally, Havana got my vote…. ** ** Tim ** ** *From:* openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto: openstack-bounces+tim.bell=cern...@lists.launchpad.net] *On Behalf Of *Matt Joyce *Sent:* 24 January 2013 20:58 *To:* Marton Kiss *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] Name it Hood! ** ** Don't forget the HMS hood who was sunk by the Bismark. Rallying the British navy to seek vengeance and crush the unsinkable foe. =P -Matt On Thu, Jan 24, 2013 at 11:53 AM, Marton Kiss marton.k...@gmail.com wrote: And it also means beaver in hungarian. :) http://translate.google.hu/?hl=entab=wT#en/hu/beaver ** ** Márton ** ** 2013/1/24 Monty Taylor mord...@inaugust.com Hey all! Here's my pitch for Hood: a) It's the tallest mountain in Oregon, and honestly, it's a pretty kick-ass mountain in general b) Being in the pacific northwest, the mountain itself is quite regularly in the clouds. That's gotta count for something. c) It's actually a volcano. d) Mount Hood is CLEARLY an Oregon thing. Havana is clearly a town in Cuba. (We should have a design summit in cuba!!!) e) Harbor is super-problematic because of the US/UK clash in spelling. Half of us will spell it wrong no matter what. f) Hood is only 4 letters. Think about that when you think about typing hatfield a lot. Also, if we name it hatfield, we're going to have to have the M summit somewhere that has a town called McCoy. g) I'll buy you a beer at the summit if you vote for Hood. Monty ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ** ** ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ** ** ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] [Openstack :: Folsom] Quantum Network Node setup
Hi, Iam having essex setup [where we dont have Quantum Network] and now if we want to have Folsom setup and if we dont want to use L3-Agent and Quantum router for DNAT of Floating-IPs. How can we achieve this with Folsom.? As well i want to understand the real time deployment of Teanant VMs for Public Access using Public -IPs, I hope it can be achieved in Folsom setup as well. Can any one give me inputs on this. Just curious to understand the quantum router use case apart from NAT,iptable rules any other advantages we have in real time deployments. please share your understanding and experience. Thanks in advance. regards, balaji On Mon, Nov 12, 2012 at 6:17 AM, gong yong sheng gong...@linux.vnet.ibm.com wrote: On 11/10/2012 10:06 PM, balaji patnala wrote: Hi Yong, I downloaded the Quantum Architecture in Folsom Powerpoint prepared by you and found that in slide-10: lL3-agent lTo implement floating Ips and other L3 features, such as NAT *lOne per network* Can you elaborate on the comment 'one per network' for L3-Agent. # If use_namespaces is set as False then the agent can only configure one router. # This is done by setting the specific router_id. # router_id = # Each L3 agent can be associated with at most one external network. This # value should be set to the UUID of that external network. If empty, # the agent will enforce that only a single external networks exists and # use that external network id # gateway_external_network_id = two options: 1. use namespace = False and set router_id to specific one can support multi l3-agent, or 2. create multiples external networks, and use gateway_external_network_id = to run multil3-agent This way, we must set router's gateway port: we can create router with external_gateway_info: such as quantum router-create router1 --external_gateway_info network_id=id or quantum router-create router2 quantum router-gateway-set As i understood that the L3-Agent will be only one for complete setup. If we have more than one Network Node then we must install dhcp-agent and L3-Agent in each of these Network Nodes. So, the comment of 'one per network' is like we can have one router/gateway per tenant network. Can you give us your comments on this. you can reach at this target by creating a router or external network per tenant. bye, balaji On Wed, Oct 31, 2012 at 10:38 AM, balaji patnala patnala...@gmail.comwrote: Hi Yong, Thanks for information. I think you mean to say that these Quantum Network Node is not per Tenant basis and it can serve all the Tenants of DC setup. Just want to understand what will be the advantages we are thinking of by doing so. Regards, Balaji On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng gong...@linux.vnet.ibm.com wrote: Hi, In fact, we can split Quantum network Node into two categories: one is for dhcp, which install ovs agent and dhcp agent. We can have one such kind of node one is for l3 agent, we can deal with one external network on one l3 agent. We can have many nodes of this kind. Regards, Yong Sheng Gong On 10/30/2012 02:27 PM, balaji patnala wrote: Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.comwrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation
Re: [Openstack] [Openstack :: Folsom] Quantum Network Node setup
Hi Yong, I downloaded the Quantum Architecture in Folsom Powerpoint prepared by you and found that in slide-10: lL3-agent lTo implement floating Ips and other L3 features, such as NAT *lOne per network* Can you elaborate on the comment 'one per network' for L3-Agent. As i understood that the L3-Agent will be only one for complete setup. If we have more than one Network Node then we must install dhcp-agent and L3-Agent in each of these Network Nodes. So, the comment of 'one per network' is like we can have one router/gateway per tenant network. Can you give us your comments on this. bye, balaji On Wed, Oct 31, 2012 at 10:38 AM, balaji patnala patnala...@gmail.comwrote: Hi Yong, Thanks for information. I think you mean to say that these Quantum Network Node is not per Tenant basis and it can serve all the Tenants of DC setup. Just want to understand what will be the advantages we are thinking of by doing so. Regards, Balaji On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng gong...@linux.vnet.ibm.com wrote: Hi, In fact, we can split Quantum network Node into two categories: one is for dhcp, which install ovs agent and dhcp agent. We can have one such kind of node one is for l3 agent, we can deal with one external network on one l3 agent. We can have many nodes of this kind. Regards, Yong Sheng Gong On 10/30/2012 02:27 PM, balaji patnala wrote: Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.comwrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.comwrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation and configuration change with this type of Installation? Please guide me on How to achieve the same. Thanking you -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] OpenStack (+ Quantum Deployment) Scenarios
Hi Openers, One doubt i have is like, as we see in the demo setup in the Quantum Admin guide available in openstack.org, we have Network Node as a seperate physical node connected to Controller Node and Compute Node. But i see that the openstack community who is actively using Folsom is not discussing more on this kind of setup. Not sure if iam missing any key information on this like that the Network Node setup may not be widely used in current deployment scenarios or it is too early to use Network Node as a seperate physical host for openstack. Open comments on this will be more helpful for openstack community to understand better on the features of folsom. regards, balaji On Thu, Nov 8, 2012 at 7:09 PM, Skible OpenStack skible.openst...@gmail.com wrote: OpenStack Folsom install guidehttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst You will find what you want and even more ;) Le 08/11/2012 14:30, Veera Reddy a écrit : Hi Skible, Can you please send me below configuration files of three setups you have mentioned. - ovs_quantum_plugin.ini (For controller and node) - nova.conf (For controller and node) Thanks in advance Regards, Veera. On Thu, Nov 8, 2012 at 2:57 PM, Skible OpenStack skible.openst...@gmail.com wrote: Hello Stackers ! I am currently trying to create pictures of my OpenStack deployment architecture as a part of my OpenStack Folsom install guidehttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rstand i would like to ask a favorite. Could you be kind and please take a look at these Pics below and report back if there is a missing or wrong thing. Thank you. ==Quantum on VLAN + 3 NICs on controller node http://i.imgur.com/Ueh5Z.jpg === ==Quantum on VLAN + 2 NICs on controller node http://i.imgur.com/RK6X7.jpg === ==Quantum on GRE-tunneling + 3 NICs on controller node=== http://i.imgur.com/1jCFC.jpg === To make of OpenStack, the IT project of the century Best regards ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regards, VeeraReddy.B 9959236555. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] [Openstack :: Folsom] Quantum Network Node setup
Thanks Salvatore. It gave me good understanding of these python-*clients. On Mon, Nov 5, 2012 at 6:46 PM, Salvatore Orlando sorla...@nicira.comwrote: Hi Balaji, I am not sure I understand your questions. I think that with clients your referring to python-novaclient and/or python-quantumclient. If that is correct, those are merely applications that provide users with tools for access the respective endpoints. These applications are usually not part of the server-side architecture. It sounds pretty natural to me then each tenant will run its own client application, which could be python-quantumclient, something based on it, or something completely different that interfaces with the quantum API. Similar reasoning applies to nova, and all the other Openstack projects IMHO. Salvatore On 5 November 2012 13:47, balaji patnala patnala...@gmail.com wrote: Hi, Just want to understand the design of *client architecture like Nova client and Quantum Client. Can we run these clients more than one in multiple nodes like Controller and as well Compute Node to communicate with Central DB on controller. If we do this, do we see any side-affects of overall architecture. Appreciate your help in understanding.. regards, balaji ___ 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] OpenStack Folsom Install Guide
Hi Skibie, If we can have installation guide for demo setup like Network Node, Compute Node and Controller Node that would be great as it will help to create deployment setup.. If any body has installation guide as per demo setup, Please share regards, Balaji On Wed, Oct 31, 2012 at 6:16 PM, Skible OpenStack skible.openst...@gmail.com wrote: Hi Stackers, i am currently seeing a lot of people having trouble deploying OpenStack Folsom si i humbly present this guide for those who are experimented and even those who are still taking their first steps into the cloud world. The guide has been updated from the last version to support: * Multi Node install * ubuntu server 12.10 * Quatum Configuration * No Quantum is you are not interrested Test it to see for yourself how simple and fun has OpenStack deployment has became ! OpenStack Folsom Install Guidehttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst Cheers ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] [Openstack :: Folsom] Quantum DHCP Agent in Compute HOST
Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.comwrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.comwrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation and configuration change with this type of Installation? Please guide me on How to achieve the same. Thanking you -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] [Openstack :: Folsom] Quantum Network Node setup
Hi Yong, Thanks for information. I think you mean to say that these Quantum Network Node is not per Tenant basis and it can serve all the Tenants of DC setup. Just want to understand what will be the advantages we are thinking of by doing so. Regards, Balaji On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng gong...@linux.vnet.ibm.com wrote: Hi, In fact, we can split Quantum network Node into two categories: one is for dhcp, which install ovs agent and dhcp agent. We can have one such kind of node one is for l3 agent, we can deal with one external network on one l3 agent. We can have many nodes of this kind. Regards, Yong Sheng Gong On 10/30/2012 02:27 PM, balaji patnala wrote: Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.comwrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.comwrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation and configuration change with this type of Installation? Please guide me on How to achieve the same. Thanking you -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] ERROR in ‘/var/log/quantum/agent-dhcp.log’ for FOLSOM-3
Thanks for info Aaron. On Tue, Sep 18, 2012 at 10:32 PM, Aaron Rosen aro...@nicira.com wrote: Hi Balaji, This issue seems to have been solved for Srikanth here: https://answers.launchpad.net/quantum/+question/208446 Thanks, Aaron On Tue, Sep 18, 2012 at 1:53 AM, Srikanth Kumar Lingala srikanthkumar.ling...@gmail.com wrote: Hi Dan, Yes, we have mentioned valid rabbit_host, rabbit_userid and rabbit_password fields in quantum.conf. And also, we gave the same fields in ovs_quantum_plugin.ini also. But, we are getting the same errors in agent-dhcp.log Srikanth. On Mon, Sep 17, 2012 at 9:56 PM, Dan Wendlandt d...@nicira.com wrote: Does the quantum.conf on the host that the dhcp agent is running on point to a valid rabbit_host and have a valid user/password for that rabbit host? Dan On Mon, Sep 17, 2012 at 4:29 AM, balaji patnala patnala...@gmail.com wrote: Hi, I'm using Folsom Testing Packages on Ubuntu 12.04., Quantum V2 with OVS Plugin Agent running. I am getting the following error for every 30 secs in ‘/var/log/quantum/agent-dhcp.log’ in the Openstack Controller: 2012-09-17 12:25:12ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 112, in sync_state active_networks = set(self.plugin_rpc.get_active_networks()) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 260, in get_active_networks topic=self.topic) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/proxy.py, line 80, in call return rpc.call(context, self._get_topic(topic), msg, timeout) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/__init__.py, line 102, in call return _get_impl().call(cfg.CONF, context, topic, msg, timeout) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 712, in call rpc_amqp.get_connection_pool(conf, Connection)) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py, line 368, in call rv = list(rv) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py, line 329, in __iter__ self.done() File /usr/lib/python2.7/contextlib.py, line 24, in __exit__ self.gen.next() File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py, line 326, in __iter__ self._iterator.next() File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 595, in iterconsume yield self.ensure(_error_callback, _consume) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 526, in ensure error_callback(e) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 576, in _error_callback raise rpc_common.Timeout() Timeout: Timeout while waiting on RPC response. Can anybody help me on this -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] AMPQ RPC errors in Folsom
Hi, Is it related to PYTHON version..!! Can any one help us in finding the cause for the below errors: Controller Error “nova-schedular” 2012-09-18 18:53:50 ERROR nova.openstack.common.rpc.amqp [-] Exception during message handling 2012-09-18 18:53:50 TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last): 2012-09-18 18:53:50 TRACE nova.openstack.common.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py, line 275, in _process_data 2012-09-18 18:53:50 TRACE nova.openstack.common.rpc.amqp rval = self.proxy.dispatch(ctxt, version, method, **args) 2012-09-18 18:53:50 TRACE nova.openstack.common.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/dispatcher.py, line 150, in dispatch 2012-09-18 18:53:50 TRACE nova.openstack.common.rpc.amqp raise rpc_common.UnsupportedRpcVersion(version=version) 2012-09-18 18:53:50 TRACE nova.openstack.common.rpc.amqp UnsupportedRpcVersion: Specified RPC version, 1.0, not supported by this endpoint. 2012-09-18 18:53:50 TRACE nova.openstack.common.rpc.amqp Node Error “nova-compute” 2012-09-18 18:50:00 ERROR nova.openstack.common.rpc.amqp [-] Exception during message handling 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last): 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp File /usr/lib/python2.6/site-packages/nova-2012.2-py2.6.egg/nova/openstack/common/rpc/amqp.py, line 275, in _process_data 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp rval = self.proxy.dispatch(ctxt, version, method, **args) 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp File /usr/lib/python2.6/site-packages/nova-2012.2-py2.6.egg/nova/openstack/common/rpc/dispatcher.py, line 150, in dispatch 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp raise rpc_common.UnsupportedRpcVersion(version=version) 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp UnsupportedRpcVersion: Specified RPC version, 2.1, not supported by this endpoint. 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp Exception during message handling 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last): 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp File /usr/lib/python2.6/site-packages/nova-2012.2-py2.6.egg/nova/openstack/common/rpc/amqp.py, line 275, in _process_data 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp rval = self.proxy.dispatch(ctxt, version, method, **args) 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp File /usr/lib/python2.6/site-packages/nova-2012.2-py2.6.egg/nova/openstack/common/rpc/dispatcher.py, line 150, in dispatch 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp raise rpc_common.UnsupportedRpcVersion(version=version) 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp UnsupportedRpcVersion: Specified RPC version, 2.1, not supported by this endpoint. 2012-09-18 18:50:00 TRACE nova.openstack.common.rpc.amqp Thanks, balaji ___ 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] per-net-dhcp-enable in quantum v2.0
Hi Salvatore, Thanks for information and doc details. Will wait for the details on DHCP-Agent configuring and running. Regards, Balaji.P On Mon, Sep 17, 2012 at 5:21 PM, Salvatore Orlando sorla...@nicira.comwrote: Hi Balaji, Quantum now has a dhcp agent which serves addresses to subnets using dnsmasq. The dhcp agent is a separate binary (bin/dhcp-agent). per-net-dhcp-enable has been translated into a simple feature that enables or disables the dhcp agent for specific subnets. This is controlled by the Quantum API with the enable_dhcp flag on the subnet object. Documentation concerning configuring and running the DHCP agent is in preparation and will be published soon. Documentation on Quantum v2 API is available at http://docs.openstack.org/api/openstack-network/2.0/content/ Regards, Salvatore On 17 September 2012 12:34, balaji patnala patnala...@gmail.com wrote: Hi Stackers, Do we have any docs/information on per-net-dhcp-enable feature in Quantum v2.0.? Please share with us. As it is observed that using folsom-3 releases, we didnt see any DHCP services enabled by default. Do we still have issues with quantum v2.0 w.r.t DHCP !! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] per-net-dhcp-enable in quantum v2.0
Hi Stackers, Do we have any docs/information on per-net-dhcp-enable feature in Quantum v2.0.? Please share with us. As it is observed that using folsom-3 releases, we didnt see any DHCP services enabled by default. Do we still have issues with quantum v2.0 w.r.t DHCP !! ___ 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] ERROR in ‘/var/log/quantum/agent-dhcp.log’ for FOLSOM-3
Hi, I'm using Folsom Testing Packages on Ubuntu 12.04., Quantum V2 with OVS Plugin Agent running. I am getting the following error for every 30 secs in ‘/var/log/quantum/agent-dhcp.log’ in the Openstack Controller: *2012-09-17 12:25:12ERROR [quantum.agent.dhcp_agent] Unable to sync network state.* *Traceback (most recent call last):* * File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 112, in sync_state* *active_networks = set(self.plugin_rpc.get_active_networks())* * File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 260, in get_active_networks* *topic=self.topic)* * File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/proxy.py, line 80, in call* *return rpc.call(context, self._get_topic(topic), msg, timeout)* * File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/__init__.py, line 102, in call* *return _get_impl().call(cfg.CONF, context, topic, msg, timeout)* * File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 712, in call* *rpc_amqp.get_connection_pool(conf, Connection))* * File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py, line 368, in call* *rv = list(rv)* * File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py, line 329, in __iter__* *self.done()* * File /usr/lib/python2.7/contextlib.py, line 24, in __exit__* *self.gen.next()* * File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py, line 326, in __iter__* *self._iterator.next()* * File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 595, in iterconsume* *yield self.ensure(_error_callback, _consume)* * File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 526, in ensure* *error_callback(e)* * File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 576, in _error_callback* *raise rpc_common.Timeout()* *Timeout: Timeout while waiting on RPC response.* * * Can anybody help me on this ___ 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] Not Authorized Error in ‘/var/log/nova/nova-compute.log’ for FOLSOM-3 setup
Hi,
I'm using Folsom Testing Packages on Ubuntu 12.04., Quantum V2 with OVS
Plugin Agent running on Openstack Controller.
And also, I have a Host Node using Folsom Testing Packages on Ubuntu 12.04,
Quantum OVS Agent, nova-compute and nova-api.
I am keep on getting the following error in
‘/var/log/nova/nova-compute.log’ for every 30 secs.
* *
* *
*2012-09-17 12:33:56 DEBUG nova.network.quantumv2.api [-]
get_instance_nw_info() for test1 from (pid=8948) _get_instance_nw_info
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/api.py:178*
*2012-09-17 12:33:56 ERROR nova.network.quantumv2 [-] _get_auth_token()
failed*
*2012-09-17 12:33:56 TRACE nova.network.quantumv2 Traceback (most recent
call last):*
*2012-09-17 12:33:56 TRACE nova.network.quantumv2 File
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/__init__.py, line
38, in _get_auth_token*
*2012-09-17 12:33:56 TRACE nova.network.quantumv2
httpclient.authenticate()*
*2012-09-17 12:33:56 TRACE nova.network.quantumv2 File
/usr/lib/python2.7/dist-packages/quantumclient/client.py, line 194, in
authenticate*
*2012-09-17 12:33:56 TRACE nova.network.quantumv2
content_type=application/json)*
*2012-09-17 12:33:56 TRACE nova.network.quantumv2 File
/usr/lib/python2.7/dist-packages/quantumclient/client.py, line 132, in
_cs_request*
*2012-09-17 12:33:56 TRACE nova.network.quantumv2 raise
exceptions.Unauthorized(message=body)*
*2012-09-17 12:33:56 TRACE nova.network.quantumv2 Unauthorized: {error:
{message: Invalid user / password, code: 401, title: Not
Authorized}}*
*2012-09-17 12:33:56 TRACE nova.network.quantumv2 *
*2012-09-17 12:33:56 DEBUG nova.manager [-] Skipping
ComputeManager._run_image_cache_manager_pass, 6 ticks left until next run
from (pid=8948) periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:167*
* *
Can anyone guide me to identify the issue?
Thanks in advance.
___
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] Cells Status
Atleast we should have continued with ZONES until CELLS were part of up-stream releases. I was waiting for this feature eagerly to explore more on this. Can we try with the patch listed below. Only one concern with patches are we dont get much help from stack users/testers.. This is little disappointing... On Fri, Sep 14, 2012 at 10:35 PM, Joshua Harlow harlo...@yahoo-inc.comwrote: Ya, is there a session on it at the summit. I'd at least like to talk about it and what it could be in the end. Or maybe we can 'freestyle' that session :-P On 9/14/12 8:36 AM, Russell Bryant rbry...@redhat.com wrote: On 09/14/2012 11:08 AM, Joe Topjian wrote: We didnt find any information related to CELLS [which is planned to replace ZONES] in the latest Folsom pre-release. Can any body give us information on this. Unfortunately, cells was unable to make feature freeze. It should be in Grizzly. Sorry for the delay :/ This is very disappointing. I was looking forward to cells as well. When was this decided and was the decision announced somewhere else? I'd like to know so I can monitor for other announcements like this. The patch is here: https://review.openstack.org/#/c/10707/ It was proposed for inclusion on August 2nd, which was just a couple of weeks before the feature freeze. There were enough significant things that came up in discussion that it just wasn't going to make it in for Folsom. In addition to working through the technical details, it also desperately needs some documentation (ideally both architectural, as well as how to use it). It seems like we should be able to get this all wrapped up for Grizzly, though. -- Russell Bryant ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Cells Status
Hi Stackers, We didnt find any information related to CELLS [which is planned to replace ZONES] in the latest Folsom pre-release. Can any body give us information on this. -Balaji On Thu, Aug 2, 2012 at 1:19 PM, Chris Behrens cbehr...@codestud.com wrote: I found time to update the branch with the latest code tonight: https://github.com/comstud/nova/tree/cells_service I put a review up here as a WIP also: https://review.openstack.org/#/c/10707/ I reviewed what's changed since the last update… and it was essentially: Rebase against master… resolving things that had moved to openstack-common Push bandwidth usage updates to top level API cell. Push instance metadata updates to top level API cell (though I don't think they would change in a child cell) instance system metadata syncing with instance updates Better delete instance handling Removed broken near/far filter which could have potential DoS issues, until it can be redone Looks like I might have lost some code cleanups I had done previously… and I'll restore those asap. The cells code as it is in the above branch is what's now running in a production environment and working… but there's still some edge cases of issues and doesn't support things like security groups and host aggregates. I'll give an update tomorrow about trying to land this in folsom… but I'll probably be posting it at the new dev list: openstack-...@lists.openstack.org - Chris On Aug 1, 2012, at 9:03 PM, Chris Behrens wrote: Ah, hit send early from my phone. There's a few additions I have in a private branch along with it being up2date with trunk. Will get that into the public branch and get the update out tomorrow! On Aug 1, 2012, at 9:01 PM, Chris Behrens cbehr...@codestud.com wrote: I'll push up the latest tomorrow, promise! And I'll give an update at that time. Sorry, been crazy times lately preparing for Rackspace's release today. We are live with cells, and I'm extremely anxious to start getting it into trunk. There's been a few additions not in the branch on github. - Chris On Aug 1, 2012, at 8:19 PM, Russell Sim russell@gmail.com wrote: Hey, We have been experimenting with the cells branch and I'm hoping I can get an update. The branch on github hasn't been updated for a couple of months and we are starting to hack on it but we are hesitant because we are aware that there are uncommitted changes. Cheers, Russell ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Quantum -. Multi-Plugin and support for provisioning of other devices.
Hi Dan, Can you give us some insight into CINDER component of folsom release. Thanks in advance. -balaji On Mon, Sep 10, 2012 at 10:28 PM, Dan Wendlandt d...@nicira.com wrote: Yes, Tim is correct that we expect to discuss load-balancing capabilities at the Grizzly summit. This is a topic for discussion at the summit, but I expect that it will be possible to run many different types of load balancers independent of your choice of the core L2/L3 plugin you're using to run Quantum (perhaps this is what you're getting at with mentioning 'multi-plugins'). As far as storage devices that require network access, I suspect that would more be under the purview of something like Cinder, which may need to integrate with Quantum (similar to Nova's integration with Quantum) if the goal is to plug storage devices into networks directly. Dan On Sun, Sep 9, 2012 at 10:56 PM, Tim Bell tim.b...@cern.ch wrote: There has been some load balancing discussion and more is due at the summit. The various current activities are summarised in http://wiki.openstack.org/Quantum/LBaaS Can you explain what you mean by storage devices with respect to Quantum ? The storage activities are underway as part of Cinder. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Endre Karlson Sent: 09 September 2012 19:57 To: openstack@lists.launchpad.net Subject: [Openstack] Quantum -. Multi-Plugin and support for provisioning of other devices. Hi, I am wondering if there are any community plans to support to use Quantum to provision up interfaces on other devices in areas of say LoadBalancers, Storage devices etc and if there are plans to support multi-active plugins in Quantum for this? Is there a timeframe maybe? Endre. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Folsom branch download
Hello Friends, Can we download Folsom branch codebase for understanding Quantum and other changes in Folsom release? Please give us your comments,experience and known issues. Thanks in advance. -balaji ___ 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] [Quantum] Removing quantum-rootwrap
Hello Thierry, Can we download Folsom branch codebase for understanding Quantum and other changes in Folsom release? Please give us your comments,experience and known issues. Thanks in advance. -balaji On Wed, Aug 8, 2012 at 7:01 PM, Thierry Carrez thie...@openstack.orgwrote: Hi everyone, Quantum currently contains bin/quantum-rootwrap, a copy of nova-rootwrap supposed to control its privilege escalation to run commands as root. However quantum-rootwrap is currently non-functional, missing a lot of filter definitions that are necessary for it to work correctly. Quantum is generally run with root_helper=sudo and a wildcard sudoers file. That means Quantum is not ready to deprecate in Folsom (and remove in Grizzly) its ability to run with root_helper=sudo, like Nova and Cinder do. I discussed this with Dan, and it appears that the sanest approach would be to remove quantum-rootwrap from Quantum and only support root_helper=sudo (the only option that works). I suspect nobody is actually using quantum-rootwrap right now anyway, given how broken it seems to be. For the first official release of Quantum as an OpenStack core project, I would prefer not to ship half-working options :) Quantum would then wait for rootwrap to move to openstack-common (should be done in Grizzly) to reconsider using it. Let me know if any of you see issues with that approach. (posted to the general list to get the widest feedback). -- 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 ___ 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] Heterogeneous hardware support
Hi, Does open stack [Essex] release support Heterogeneous hardware for creating VMs with Security Applications? If not, what is the road map for this. Please let me know. Also, Please let me know about Heterogeneous Hardware deployment in Cloud infrastructure we have right now. Thanks in advance. Regards, Balaji.P ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
