[Openstack] [nova-volumes] relationship between nova-volumes and swift?
Hello ,all I am a little confused about the nova-volumes service and the swift.I know both are about the volume store,but what's the relationship between them ?Can some one please explain it to me please :) Thanks! Eric Luo 2012-04-28 ___ 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 deployment on Essex
hi, Dan I install openvswitch and quantum according this two docs. Now I have met some problems. 1. Using python ovs_quantum_agent.py ovs_quantum_plugin.ini -v DEBUG:root:## running command: sudo ovs-ofctl del-flows br-int DEBUG:root:## running command: sudo ovs-ofctl add-flow br-int priority=1,actions=normal INFO:root:Connecting to database ovs_quantum on localhost DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport thess debug show again and again, is it right? 2. this is my ova-vsctl show: 3f474726-21fc-40a4-b7b8-f438fcfe2c3e Bridge br-int Port eth1 Interface eth1 Port br-int Interface br-int type: internal is it right? 3. Then I use nova-manage network create to create network, but the database ova_quantum is empty, I have defined it in ovs_quantum_plugin.ini I don't know whether quantum and openvswitch work well together in my system. Can you give me any help? -- 非淡薄无以明志，非宁静无以致远 ___ 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] (no subject)
According doc: http://docs.openstack.org/incubation/openstack-network/admin/content/Net-Create-dle455.html when I create the second network, it return errors: root@cloud:/etc/quantum# nova-manage network create --label=public --fixed_range_v4=10.0.1.0/24 2012-04-28 15:27:21 DEBUG nova.utils [req-6001e498-c504-4bf1-ae5b-537d08e66325 None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=21612) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 root@cloud:/etc/quantum# nova-manage network create --label=test-1 --fixed_range_v4=10.0.2.0/24 --uuid=64a1c0f3-572b-4349-993d-36c06b746006 2012-04-28 15:27:46 DEBUG nova.utils [req-5d2924e1-6dce-44ae-bc45-c6c880c9cf9a None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=21756) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Command failed, please check log for more info 2012-04-28 15:27:46 CRITICAL nova [req-5d2924e1-6dce-44ae-bc45-c6c880c9cf9a None None] Detected existing vlan with id 100 2012-04-28 15:27:46 TRACE nova Traceback (most recent call last): 2012-04-28 15:27:46 TRACE nova File /usr/bin/nova-manage, line 1744, in module 2012-04-28 15:27:46 TRACE nova main() 2012-04-28 15:27:46 TRACE nova File /usr/bin/nova-manage, line 1731, in main 2012-04-28 15:27:46 TRACE nova fn(*fn_args, **fn_kwargs) 2012-04-28 15:27:46 TRACE nova File /usr/bin/nova-manage, line 812, in create 2012-04-28 15:27:46 TRACE nova fixed_cidr=fixed_cidr) 2012-04-28 15:27:46 TRACE nova File /usr/lib/python2.7/dist-packages/nova/network/manager.py, line 1843, in create_networks 2012-04-28 15:27:46 TRACE nova NetworkManager.create_networks(self, context, vpn=True, **kwargs) 2012-04-28 15:27:46 TRACE nova File /usr/lib/python2.7/dist-packages/nova/network/manager.py, line 1401, in create_networks 2012-04-28 15:27:46 TRACE nova network = self.db.network_create_safe(context, net) 2012-04-28 15:27:46 TRACE nova File /usr/lib/python2.7/dist-packages/nova/db/api.py, line 731, in network_create_safe 2012-04-28 15:27:46 TRACE nova return IMPL.network_create_safe(context, values) 2012-04-28 15:27:46 TRACE nova File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 102, in wrapper 2012-04-28 15:27:46 TRACE nova return f(*args, **kwargs) 2012-04-28 15:27:46 TRACE nova File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 1884, in network_create_safe 2012-04-28 15:27:46 TRACE nova raise exception.DuplicateVlan(vlan=values['vlan']) 2012-04-28 15:27:46 TRACE nova DuplicateVlan: Detected existing vlan with id 100 2012-04-28 15:27:46 TRACE nova Can anyone help me? -- 非淡薄无以明志，非宁静无以致远 ___ 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-volumes] relationship between nova-volumes and swift?
Hello, Eric Swift is actually an object store rather then volume store. It is used for storing any types of objects as files in underlying file system. This files can be anything, including binary images of block volumes. HTTP is used for transporting objects to and from the store. Nova-volume service is totally different. It allows to attach virtual block devices to VMs by providing correct parameters for nova-compute's 'attach_volume' method. It has a number of drivers that can manage different storage back-ends (Linux LVs, SAN virtual disks, distributed storage systems), but all these back-ends must be able to provide a virtual block device to VMs, which Swift is not capable of. Primary integration point between Swift and nova-volume is a way to store snapshots of virtual volumes to Swift store as files: https://blueprints.launchpad.net/nova/+spec/store-snapshots-to-swift. Status of work on this blueprint is unknown to me. -- Best regards, Oleg On Sat, Apr 28, 2012 at 10:15 AM, Eric Luo nextf...@gmail.com wrote: Hello ,all I am a little confused about the nova-volumes service and the swift.I know both are about the volume store,but what's the relationship between them ?Can some one please explain it to me please :) Thanks! Eric Luo 2012-04-28 ___ 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 scheduler when create a new instance.
Hi! 1. Is your locale anything different from C or en? If so, you're most likely getting an exception on nova-compute when it tries to start, exception gets lost (my fault, forgot to file a bug) and nova-compute dies. The exception is most likely occur because of https://bugs.launchpad.net/nova/+bug/983845, the workaround must be to nova delete instances that were failed to spawn on this node. 2. You're running nova-compute inside a VM, right? Then instance is most likely failing to spawn because KVM is not available. In order to use KVM inside a VM, you'll have to have nested virtualization available and turned on. For this, on host machine you need at least 3.2 kernel and pass kvm-intel.nested=1 to kernel at boot if you have Intel CPU (it looks like it's turned on by default for AMD). Then you can use KVM inside KVM. Kind regards, Yuriy. On Sat, Apr 28, 2012 at 08:39, Yong Sheng Gong gong...@cn.ibm.com wrote: Seems that your compute is not alive: nova-compute ubuntu0001 nova enabled XXX -openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: - To: openstack@lists.launchpad.net From: Rogerio Goncalves roge...@gmail.com Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.net Date: 04/28/2012 10:22AM Subject: Re: [Openstack] Error in scheduler when create a new instance. Zhang, I already triad. root@ubuntu0001:~# service libvirt-bin restart libvirt-bin stop/waiting libvirt-bin start/running, process 21469 root@ubuntu0001:~# service nova-compute restart stop: Unknown instance: nova-compute start/running, process 21524 root@ubuntu0001:~# service nova-scheduler restart nova-scheduler stop/waiting nova-scheduler start/running, process 21540 root@ubuntu0001:~# nova-manage service list 2012-04-27 21:36:23 DEBUG nova.utils [req-94ff244b-4fe2-4595-95b8-fea9deef4b22 None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=21547) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Binary Host Zone Status State Updated_At nova-scheduler ubuntu0001 nova enabled :-) 2012-04-28 00:36:06 nova-compute ubuntu0001 nova enabled XXX None nova-volume ubuntu0001 nova enabled :-) 2012-04-28 00:36:16 nova-network ubuntu0001 nova enabled :-) 2012-04-28 00:36:15 On Fri, Apr 27, 2012 at 11:17 PM, 张华 veryhua2...@gmail.com wrote: you need reboot libvirtd, yesterday I encounter the same problem 2012/4/28 Rogerio Goncalves roge...@gmail.com Yong, oot@ubuntu0001:~# free -m total used free shared buffers cached Mem: 3951 2121 2830 0 168 160 -/+ buffers/cache: 792 3159 Swap: 1951 0 1951 On Fri, Apr 27, 2012 at 8:11 PM, Yong Sheng Gong gong...@cn.ibm.com wrote: how much free ram left on your compute node? -openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: - To: Flavia Missi flaviami...@gmail.com From: Rogerio Goncalves roge...@gmail.com Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.net Date: 04/28/2012 04:43AM Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Error in scheduler when create a new instance. Flavia, Thanks, but does not help. Get the same error. 2012-04-27 17:41:39 WARNING nova.scheduler.manager [req-efb95a01-15f0-4ae7-9f7f-0ec71ff4d12a e53ddc6542c84f0791fd5ff8968162d7 c65c92296bf841c992c895074da03316] Failed to schedule_run_instance: No valid host was found. Is the appropriate service running? 2012-04-27 17:41:39 WARNING nova.scheduler.manager [req-efb95a01-15f0-4ae7-9f7f-0ec71ff4d12a e53ddc6542c84f0791fd5ff8968162d7 c65c92296bf841c992c895074da03316] Setting instance 01a15b65-7807-42b4-95a2-66d64d12f906 to ERROR state. root@ubuntu0001:/var/log/nova# nova-manage service list Binary Host Zone Status State Updated_At nova-scheduler ubuntu0001 nova enabled :-) 2012-04-27 20:42:57 nova-compute ubuntu0001 nova enabled XXX None nova-volume ubuntu0001 nova enabled :-) 2012-04-27 20:42:52 nova-network ubuntu0001 nova enabled :-) 2012-04-27 20:42:52 On Fri, Apr 27, 2012 at 5:02 PM, Flavia Missi flaviami...@gmail.com wrote: Rogerio, I had this problem and solved it by setting the following flag: scheduler_default_filters=AllHostsFilter Hope it helps. []'s On Fri, Apr 27, 2012 at 12:29 PM, Rogerio Goncalves roge...@gmail.com wrote: is enabled and not running my compute node is virtual machine to test and configured with qemu (2 core,
Re: [Openstack] Proposal for manuals translation process
Hi, Anne Thank you for your comments. I'm glad to know that you are working for a larger goal. I don't know Launchpad is broken with code strings now. What do you mean when you said Launchpad to be broken with code strings now? I take a look at Horizon in Transifex. Gabriel Hurley is the coordinator. Can I know the reason why Dashboard turn to Transifex other than Launchpad? Pootle will be a good open source project to look into. It supports a very powerful Terminology matching feature, which can match and list the relevant terminologies at real time. The translation memory feature is not so powerful. Suggested translations from a translation memory must be generated before translation, while Transifex can list suggested translations at real time. I will add the third column in our wiki page. There is a major issue for Pootle that we need to consider. Although Pootle has its official server to host the translation of Pootle UI and related projects, the policy for selecting projects on our official server are not finalised yet. I cannot find a way to register our projects in that official server. So we might need to host our own Pootle server if we use it. Are we able to host our own translation server? I'm not clear whether Pootle supports OpenID. If we are going to host our own Pootle server, maybe we can enhance it and enable the OpenID authentication. Both Launchpad and Transifex, even Pootle, manage the translation review process by their own. I think, the translation quality review shall be done using the translation tool. Gerrit and Jenkins will play an important role in Generating step. I'm not familiar with Gerrit and Jenkins. If my description is wrong, feel free to correct me. After the fourth step Converging, DocBooks in different languages will be generated and submitted to Gerrit for review. Jenkins will run Maven build and upload the generated sources to server. The reviewer ( translation coordinator ) will accept the changes. When I propose the five steps, I only think of manuals translation. Code strings may be a little different. Are there any globalization test in Jenkins? If there is no, we may need to add globalization test. Regards Daisy annegen...@justwriteclick.com wrote on 04/28/2012 03:21:07 AM: Anne Gentle a...@openstack.org Sent by: annegen...@justwriteclick.com 04/28/2012 03:21 AM To Ying Chun Guo/China/IBM@IBMCN, cc openstack@lists.launchpad.net Subject Re: [Openstack] Proposal for manuals translation process Hi Daisy, Thanks so much for this detailed proposal. I'd like you to put it on the OpenStack wiki, at http://wiki.openstack.org/Translations. My first read-through and discussion with the CI team brings up a few comments: - Whatever we do for docs, we should also do for code strings. So unfortunately the scope for the Goal probably cannot be so narrow. We know Launchpad to be broken with code strings now, that data point should be reflected in this point-in-time analysis. - Dashboard uses Transifex now (while the other projects unsuccessfully use Launchpad). Tres Henry, can you comment on the number of translators of Dashboard strings you have on the Transifex side already? - Not that I want analysis paralysis, but, we may need to add a third column of a crowd-sourced translation option like Pootle that is familiar to open-source translators. Also, the lack of a translation memory/dictionary (and having to hold such a valuable asset in a wiki page) is troubling, can we also analyze an option that offers a translation dictionary? So much re-use would be available to all the projects. - There seems to be assumptions that Jenkins and Gerrit will just work with out much description of the role those two crucial tools play. Can you further describe the workflow for those in the Slicing, Uploading, Downloading, Converging, and Generating steps? I appreciate all the hard work I _know_ went into this proposal. Let's get it on the wiki, discuss more, and keep adding details. I'd like to make this a blueprint, could be for openstack-manuals, could be for horizon, I don't know yet. Thanks for stepping up and embracing our international community's needs! Thanks, Anne On Fri, Apr 27, 2012 at 3:45 AM, Ying Chun Guo guoyi...@cn.ibm.com wrote: Hi, all During the I18N in OpenStack discussion in design summit, it is mentioned that documents need to I18N. I also noticed some requests for a Chinese version manuals from China users. But unlike Gettext strings in the codes, there is no process for DocBook translation yet. Translators, who want to help translation, have to take a DocBook into a tool and perform a translation on a copy which will be saved as a new file. This traditional translation model is not good for collaboration. Usually, the open source translation depends on volunteers. It's better to use the crowd translation model, which enables a mass of translators to work on the same job, just like the
Re: [Openstack] Quantum deployment on Essex
Hi Dan, I also run openvswitch + quantum according that two docs, my result is: 1) run openvswitch plugin + quantum on ubuntu server, success 2) run linux-bridge plugin + quantum on ubuntu server, success 3) run openvswitch plugin + quantum on fedora 16 failed 4) run linux-bridge plugin + quantum on fedora 16 failed 5) run openvswitch plugin + quantum on redhat failed 6) run linux-bridge plugin + quantum on redhat failed as for 3) , 4) , 5) , 6) , there are the same problem httplib throw 'TypeError: an integer is required' when run nova boot command' I also describe the details on https://answers.launchpad.net/quantum/+question/19 could you give me some input ? thanks. Highly Appreciated! Cheers, Zhang Hua(张华) IBM China System and Technology Lab(CSTL), Beijing E-Mail: zhhu...@cn.ibm.com Tel: 86-10-82452020 Address: Building 28(Ring Building), ZhongGuanCun Software Park, No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193 From: livemoon mwjpi...@gmail.com To: Dan Wendlandt d...@nicira.com, Cc: openstack@lists.launchpad.net Date: 28/04/2012 15:22 Subject:Re: [Openstack] Quantum deployment on Essex Sent by:openstack-bounces+zhhuabj=cn.ibm@lists.launchpad.net hi, Dan I install openvswitch and quantum according this two docs. Now I have met some problems. 1. Using python ovs_quantum_agent.py ovs_quantum_plugin.ini -v DEBUG:root:## running command: sudo ovs-ofctl del-flows br-int DEBUG:root:## running command: sudo ovs-ofctl add-flow br-int priority=1,actions=normal INFO:root:Connecting to database ovs_quantum on localhost DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport thess debug show again and again, is it right? 2. this is my ova-vsctl show: 3f474726-21fc-40a4-b7b8-f438fcfe2c3e Bridge br-int Port eth1 Interface eth1 Port br-int Interface br-int type: internal is it right? 3. Then I use nova-manage network create to create network, but the database ova_quantum is empty, I have defined it in ovs_quantum_plugin.ini I don't know whether quantum and openvswitch work well together in my system. Can you give me any help? -- 非淡薄无以明志，非宁静无以致远 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp inline: graycol.gif___ 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-volumes] relationship between nova-volumes and swift?
+me :-) Swift is much like Amazon S3(Simple Storage Service), and Nova-volume is much like Amazon EBS (Elastic Block Store). Swift is used as object store of VM images in OpenStack. but Nova-volume is used to store persistent data of VM instances which means even the instance was destroyed, the volume data will still be available for user. for example, it can be attached to another instance instead. Swift data model is a kind of Container/Object and providing unlimited number of objects, but Nova-volume is block device (much like a hard drive). The interesting thing is that Amazon ESB could provide snapshots of volumes which can be persisted to Amazon S3. So the same snopshot can spawn as many volumes as you want. Best Regards, Edward Zhang(张华)地址:北京市海淀区东北旺西路8号 中关村 Staff Software Engineer 软件园28号楼 环宇大厦3层 邮编：100193 TravelTransportation Standards Address: 3F Ring, Building 28 Emerging Technology Institute(ETI)Zhongguancun Software Park, 8 IBM China Software Development LabDongbeiwang West Road, Haidian e-mail: zhu...@cn.ibm.com District, Beijing, P.R.C.100193 Notes ID: Hua ZZ Zhang/China/IBM Tel: 86-10-82450483 Oleg Gelbukh ogelbukh@miranti s.com To Sent by: Eric Luo nextf...@gmail.com openstack-bounces cc +zhuadl=cn.ibm.co openstack@lists.launchpad.net m@lists.launchpad Subject .net Re: [Openstack] [nova-volumes] relationship between nova-volumes and swift? 2012-04-28 15:47 Hello, Eric Swift is actually an object store rather then volume store. It is used for storing any types of objects as files in underlying file system. This files can be anything, including binary images of block volumes. HTTP is used for transporting objects to and from the store. Nova-volume service is totally different. It allows to attach virtual block devices to VMs by providing correct parameters for nova-compute's 'attach_volume' method. It has a number of drivers that can manage different storage back-ends (Linux LVs, SAN virtual disks, distributed storage systems), but all these back-ends must be able to provide a virtual block device to VMs, which Swift is not capable of. Primary integration point between Swift and nova-volume is a way to store snapshots of virtual volumes to Swift store as files: https://blueprints.launchpad.net/nova/+spec/store-snapshots-to-swift. Status of work on this blueprint is unknown to me. -- Best regards, Oleg On Sat, Apr 28, 2012 at 10:15 AM, Eric Luo nextf...@gmail.com wrote: Hello ,all I am a little confused about the nova-volumes service and the swift.I know both are about the volume store,but what's the relationship between them ?Can some one please explain it to me please :) Thanks! Eric Luo 2012-04-28 ___ 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 :
Re: [Openstack] Quantum deployment on Essex
Hi livemoon, 3. Then I use nova-manage network create to create network, but the database ova_quantum is empty, I have defined it in ovs_quantum_plugin.ini If your database is empty, it's because the connection between quantum-server and the database is not working. Check your ovs_quantum_plugin.ini if you have the good sql_connection parameter. And restart the service. I don't know whether quantum and openvswitch work well together in my system. Can you give me any help? I can help you. I'm very close to release a complete documentation in which I explain from scratch how to install Essex (with Quantum of course). I have to fix some errors, and I release it before monday afternoon. Best regards -- Emilien Macchi Phone : +33 685 117 748 Skype : memilien69 Twitter : EmilienMacchi Website : http://my1.fr ___ 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] Using Foreign Keys
On Apr 26, 2012, at 12:03 PM, Monty Taylor wrote: On 04/26/2012 10:14 AM, Sean Dague wrote: On 04/25/2012 05:17 PM, Vishvananda Ishaya wrote: The main issue is when the relevant tables are moved into a separate service a la quantum or cinder. We can't keep referential integrity across multiple databases, so the foreign keys in this case need to be removed. It leads to an odd situation when there is still an internal implementation in addition to the external implementation because the internal implementation no longer has foreign keys. As an example, we used to have foreign key relationships between instances and networks. We can no longer have these because we support networks declared externally. The internal network management now has no referential integrity, but this is the price we pay for separation of concerns. We are going through a similar set of relationship-breaking with the volume code. There are definitely the practical aspects of where this can't be done because the services have split out, and I think that's fine. But enforcing the ref constraints where possible just provides another level of safety in the data. A policy where we break FK relationships if the preferred core model is 2 services (i.e. Nova / Quantum), but we add FK constraints within a service might be a good idea. I think the real key is to have a config option to tell sqlalchemy to not, even if we're running innodb, add the foreign keys to the DDL sent to the database. If sqlalchemy doesn't have that ability, we should write it and contribute it, because anyone using MySQL at scale via sqlalchemy actually wants the feature, whether they recognize it yet or not. I registered a blueprint for this: https://blueprints.launchpad.net/nova/+spec/disable-fkeys-by-config Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com smime.p7s Description: S/MIME cryptographic signature ___ 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 deployment on Essex
On Sat, Apr 28, 2012 at 12:18 AM, livemoon mwjpi...@gmail.com wrote: hi, Dan I install openvswitch and quantum according this two docs. Now I have met some problems. 1. Using python ovs_quantum_agent.py ovs_quantum_plugin.ini -v DEBUG:root:## running command: sudo ovs-ofctl del-flows br-int DEBUG:root:## running command: sudo ovs-ofctl add-flow br-int priority=1,actions=normal INFO:root:Connecting to database ovs_quantum on localhost DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport thess debug show again and again, is it right? Yes. The system should probably not default to DEBUG, as that is very verbose. 2. this is my ova-vsctl show: 3f474726-21fc-40a4-b7b8-f438fcfe2c3e Bridge br-int Port eth1 Interface eth1 Port br-int Interface br-int type: internal is it right? by ova-vsclt, I assume you mean ovs-vsctl? If so, this looks reasonable, assuming you haven't actually spun up any VMs (once you do, you should see additional ports listed, each starting with tap. 3. Then I use nova-manage network create to create network, but the database ova_quantum is empty, I have defined it in ovs_quantum_plugin.ini Running 'quantum-server' with the OVS plugin enabled (described here: http://openvswitch.org/openstack/documentation/) will automatically create the appropriate tables. The table is ovs_quantum, not ova_quantum... perhaps that could be the cause if you are seeing issues? dan I don't know whether quantum and openvswitch work well together in my system. Can you give me any help? -- 非淡薄无以明志，非宁静无以致远 -- ~~~ 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
Re: [Openstack] Quantum deployment on Essex
I've responded on launchpad answers as well. best, Dan It looks like this is an error being returned by nova, not quantum. My best guess is that you're running an older version of nova that is expecting the network-id being passed in during the create-server request to be an integer, not a string UUID. I think the os-create-server extension changed from expecting an int to a UUID in early Essex. Perhaps you're running diablo nova? On Sat, Apr 28, 2012 at 2:35 AM, Hua BJ Zhang zhhu...@cn.ibm.com wrote: Hi Dan, I also run openvswitch + quantum according that two docs, my result is: 1) run openvswitch plugin + quantum on ubuntu server, success 2) run linux-bridge plugin + quantum on ubuntu server, success 3) run openvswitch plugin + quantum on fedora 16 failed 4) run linux-bridge plugin + quantum on fedora 16 failed 5) run openvswitch plugin + quantum on redhat failed 6) run linux-bridge plugin + quantum on redhat failed as for 3) , 4) , 5) , 6) , there are the same problem httplib throw 'TypeError: an integer is required' when run nova boot command' I also describe the details on https://answers.launchpad.net/quantum/+question/19 could you give me some input ? thanks. Highly Appreciated! Cheers, Zhang Hua(张华) IBM China System and Technology Lab(CSTL), Beijing E-Mail: zhhu...@cn.ibm.com Tel: 86-10-82452020 Address: Building 28(Ring Building), ZhongGuanCun Software Park, No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193 [image: Inactive hide details for livemoon ---28/04/2012 15:22:15---hi, Dan I install openvswitch and quantum according this two docs.]livemoon ---28/04/2012 15:22:15---hi, Dan I install openvswitch and quantum according this two docs. Now I have met From: livemoon mwjpi...@gmail.com To: Dan Wendlandt d...@nicira.com, Cc: openstack@lists.launchpad.net Date: 28/04/2012 15:22 Subject: Re: [Openstack] Quantum deployment on Essex Sent by: openstack-bounces+zhhuabj=cn.ibm@lists.launchpad.net -- hi, Dan I install openvswitch and quantum according this two docs. Now I have met some problems. 1. Using python ovs_quantum_agent.py ovs_quantum_plugin.ini -v DEBUG:root:## running command: sudo ovs-ofctl del-flows br-int DEBUG:root:## running command: sudo ovs-ofctl add-flow br-int priority=1,actions=normal INFO:root:Connecting to database ovs_quantum on localhost DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 external_ids DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth1 ofport thess debug show again and again, is it right? 2. this is my ova-vsctl show: 3f474726-21fc-40a4-b7b8-f438fcfe2c3e Bridge br-int Port eth1 Interface eth1 Port br-int Interface br-int type: internal is it right? 3. Then I use nova-manage network create to create network, but the database ova_quantum is empty, I have defined it in ovs_quantum_plugin.ini I don't know whether quantum and openvswitch work well together in my system. Can you give me any help? -- 非淡薄无以明志，非宁静无以致远___ 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 ~~~ graycol.gif___ 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] (no subject)
i think you should use --vlan=vlanid in command nova-manage network create I thought by default nova-manage try to use vlan_start (default is vlanid 100) to insert it in db table networks. and if you already have one network with vlanid100 , it should return such error about duplicated vlan. what is the type of network_manager in you configuration? 2012/4/28 livemoon mwjpi...@gmail.com According doc: http://docs.openstack.org/incubation/openstack-network/admin/content/Net-Create-dle455.html when I create the second network, it return errors: root@cloud:/etc/quantum# nova-manage network create --label=public --fixed_range_v4=10.0.1.0/24 2012-04-28 15:27:21 DEBUG nova.utils [req-6001e498-c504-4bf1-ae5b-537d08e66325 None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=21612) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 root@cloud:/etc/quantum# nova-manage network create --label=test-1 --fixed_range_v4=10.0.2.0/24 --uuid=64a1c0f3-572b-4349-993d-36c06b746006 2012-04-28 15:27:46 DEBUG nova.utils [req-5d2924e1-6dce-44ae-bc45-c6c880c9cf9a None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=21756) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Command failed, please check log for more info 2012-04-28 15:27:46 CRITICAL nova [req-5d2924e1-6dce-44ae-bc45-c6c880c9cf9a None None] Detected existing vlan with id 100 2012-04-28 15:27:46 TRACE nova Traceback (most recent call last): 2012-04-28 15:27:46 TRACE nova File /usr/bin/nova-manage, line 1744, in module 2012-04-28 15:27:46 TRACE nova main() 2012-04-28 15:27:46 TRACE nova File /usr/bin/nova-manage, line 1731, in main 2012-04-28 15:27:46 TRACE nova fn(*fn_args, **fn_kwargs) 2012-04-28 15:27:46 TRACE nova File /usr/bin/nova-manage, line 812, in create 2012-04-28 15:27:46 TRACE nova fixed_cidr=fixed_cidr) 2012-04-28 15:27:46 TRACE nova File /usr/lib/python2.7/dist-packages/nova/network/manager.py, line 1843, in create_networks 2012-04-28 15:27:46 TRACE nova NetworkManager.create_networks(self, context, vpn=True, **kwargs) 2012-04-28 15:27:46 TRACE nova File /usr/lib/python2.7/dist-packages/nova/network/manager.py, line 1401, in create_networks 2012-04-28 15:27:46 TRACE nova network = self.db.network_create_safe(context, net) 2012-04-28 15:27:46 TRACE nova File /usr/lib/python2.7/dist-packages/nova/db/api.py, line 731, in network_create_safe 2012-04-28 15:27:46 TRACE nova return IMPL.network_create_safe(context, values) 2012-04-28 15:27:46 TRACE nova File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 102, in wrapper 2012-04-28 15:27:46 TRACE nova return f(*args, **kwargs) 2012-04-28 15:27:46 TRACE nova File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 1884, in network_create_safe 2012-04-28 15:27:46 TRACE nova raise exception.DuplicateVlan(vlan=values['vlan']) 2012-04-28 15:27:46 TRACE nova DuplicateVlan: Detected existing vlan with id 100 2012-04-28 15:27:46 TRACE nova Can anyone help me? -- 非淡薄无以明志，非宁静无以致远 ___ 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 plugins
On Fri, Apr 27, 2012 at 4:44 PM, Salman Malik salma...@live.com wrote: Hi Dan, Thanks for replying. There are few more questions: I am trying to learn the functionality of Quantum plugins used in OpenStack. I have read through the Quantum Admin Guide and had few basic/quick question about quantum and OVS interaction with it: 1) OVS can have ports in which vNICS can be plugged, so why does it need to use an integration bridge for connecting all VMs on the same node to a network? I'm not sure I follow what question you're asking. When OVS is running on a host, it has one or more bridges, and bridges have ports. A linux device representing the vNIC must be added as a port of a bridge being managed by the Quantum plugin. We call this bridge the integration bridge. The Quantum plugin can then configure the ports and bridges appropriately to forward traffic based on the logical model created via the Quantum API. Can you be more precise about what you're asking here? In short it means that the OVS is managing the linux bridges and the linux devices representing vNICs must be added to these bridges (Does Quantum manager adds these devices to bridges?). You have to be a bit careful here, because the linux bridge and open vswitch are two different things (you can think of open vswitch as an advanced version of the linux bridge). A driver in the Nova virt layer is actually the one who creates the linux devices that map to vNICs. For example, libvirt creates these devices as directed by the libvirt driver code: https://github.com/openstack/nova/blob/master/nova/virt/libvirt/vif.py . This code attaches the linux device to an OVS bridge as a port. The rest of the configuration of that port and the OVS bridge is up to the OVS plugin agent. And when you say that quantum plugin configures the ports and bridges appropriately to forward traffic, you mean that it updates the database and then quantum agent then assures the correct mapping of ports/network ids to logical networks at the switch level(by adding flow entries to vSwitch? or by adding the vNICs to right bridges, as there is one bridge per tenant's network on compute node). Right? Its not correct that there is one bridge per tenant network on the compute node. In the case of the OVS plugin, there is a single bridge (e.g., br-int) and different tenants are isolated based on configuration pushed down by the agent. Really the plugin consists of both the code running on the server, and (optionally) agents running on the compute nodes. Not all plugins require agents, for example, if they have some other way of managing the vswitch. Thanks for the reference. I have looked at the code and just to affirm my understanding please confirm/correct/answer the following: Quantum manager is responsible for configuring the network for new instances that spin up. When a tenant adds a port to his logical network the request will be forwarded to this manager by Nova and then Manager (using quantum client) would talk to quantum service/server (where can I see its code?) with the REST API. According to documentation, the quantum service is responsible for loading the plugin and passing the REST API calls to the plugin. The plugin then updates the database. Rest of the work is done by quantum agent. See: http://docs.openstack.org/incubation/openstack-network/admin/content/Using-dle455.html The workflow is actually that you create a VM with one or more vNICs, and as part of the VM creation process, nova-network is invoked using the allocate_for_instance RPC call. When you are running nova-network with QuantumManager, this code uses the main Quantum REST API to create ports for each vNIC. This is the code I pointed you to before: https://github.com/openstack/nova/blob/master/nova/network/quantum . Specifically, manager.py is the QuantumManager code, and quantum_connection.py and client.py are libraries used to talk to Quantum's REST API. Dan Salman ___ 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 ~~~ -- ~~~ 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
Re: [Openstack] Mailing-list split
Daniel P. Berrange wrote: On Fri, Apr 27, 2012 at 12:04:34PM +0200, Thierry Carrez wrote: To avoid Launchpad list slowness, we would run the new openstack-dev list off lists.openstack.org. Given the potential hassle of dealing with spam and delivery issues on mission-critical MLs, we are looking into the possibility of outsourcing the maintenance of lists.openstack.org to a group with established expertise running mailman instances. Please let us know ASAP if you could offer such services. We are not married to mailman either -- if an alternative service offers good performance and better integration (like OpenID-based subscription to integrate with our SSO), we would definitely consider it. FYI for libvirt mailing lists we are using the GNU project's spam filter: https://savannah.gnu.org/maintenance/ListHelperAntiSpam Thanks to this we get essentially zero spam on our mailing lists, with practically no burden on / work required by our list admins. Jim Meyering (CC'd) set it up for us originally may have some recommendations or tips if OpenStack want to make use of it too. Bob Proulx (one of the guys behind ListHelper) said no problem. All he needs is the hostname, i.e., what does/will the X-BeenThere: mail header be? Then you follow the instructions listed at the URL above for each list, and you'll see virtually no spam, and no inordinate approval delays, either. ___ 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][Nova] Minimum required code coverage per file
On Apr 26, 2012, at 9:19 PM, Kevin L. Mitchell wrote: Kevin, should we start copying openstack-common tests to client projects? Or just make sure to not count openstack-common code in the code coverage numbers for client projects? That's a tough one. If we copy in the tests, they end up being somewhat redundant, but slow down the project unit tests, but on the other hand, we'd be able to easily demonstrate that that code works properly. I think I'd prefer if we just try to not count openstack-common code for code coverage numbers… I just submitted this to ignore openstack-common code in coverage calculations: https://review.openstack.org/6905 Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
