Re: [Openstack] OpenStack Quantum plugins
Hi Salman, Please see the inline comments. On Fri, Apr 27, 2012 at 1:25 AM, Salman Malik salma...@live.com wrote: Hi All, 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? [Hitesh]: As far as I know that OVS have more features over the Linux bridge, for example, VM isolation, mobility and security. These can be configured by remote controller. To help and gian the control on all these activities the integration bridge is required. I am not sure about it but I Dan or Salvotore can explain this better way. You can find the more information here http://openvswitch.org/support/ 2) The OVS quantum plugin seems to implement the core API functions and (viewing the code) I concluded that it just makes maintains the logical mappings e.g. b/w net IDs and VLAN IDs in a database. So how is this mapping implemented on the actual ports of OVS? Is it the OVS quantum agent responsible for directing the packets to correct input/output ports based on the updates that it gets from the database? [Hitesh]: OVS agent is responsible for to update the database(accoding to actions have been told) for the local server as well Quantum server. As far as I know OVS quantum is not responsible for directing the packets to correct in/op, This job is hadled by OVS core module on the server (datapath). OVS agent only updates the database and creation bridge etc.. Dan or Salvotore can be explained more... 3) The quantum admin guide says that the nova client will be the main user of quantum and will interact with it via REST API, so it would be nice if someone can point me to the code (file path name etc.) where this happens. [Hitesh]: You can see the devstack script where we are configuring nove-network to quantum. thats the enry point for the nova-network to communicate to quantum. I will share soon more on this. However, I tried my best to give to these answers. Please feel free to correct me if anything needs to share more. Salman, Let me know if you want more info about this. I will be happy to share Thanks, Salman PS: What is the purpose of Quantum Manager in this architecture and where should I look for its code? [Hitesh]: As I am working on different machine, I will share this with details to you soon. ___ 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] s3 interface in Essex
Just an update on this. I have found the issue and will be submitting a bug with a code review to make this work. Currently nova talks to s3 via a set access and secret key in nova.conf if FLAGS.auth_strategy == 'keystone' then it should/can use the credentials of the user. Cheers, Sam On Thu, Apr 26, 2012 at 2:16 PM, Sam Morrison sorri...@gmail.com wrote: Hi, I'm trying to get the s3 interface in Essex working. I'm using the packages provided in Ubuntu 12.04. my pipeline order is: pipeline = catch_errors healthcheck cache swift3 s3token authtoken keystone proxy-server [filter:s3token] paste.filter_factory = keystone.middleware.s3_token:filter_factory auth_port = 35357 auth_host = xxx.xxx.xxx.xxx auth_protocol = http service_protocol = http service_port = 5000 service_host = xxx.xxx.xxx.xxx admin_tenant_name = sam admin_user = sam admin_password = xxx admin_token = xxx auth_token = xxx When I try for instance to do a cloud-publish-tarball in ubuntu with one of the uec images it works initially but then starts to fail. In swift the container is created and some files get uploaded but then I start getting 401s from keystone. Debugging this in keystone I see the credentials being sent to keystone have notchecked as the access parameter after about the 3rd request. {credentials: {access: notchecked, token: R0VUCgoKVGh1LCAyNiBBcHIgMjAxMiAwMzoyNTo0MiBHTVQKL3Rlc3Qv, signature: +XGyhuz7pmcnrQG1Kh45ihRCp1o=}} Am I doing something wrong or is this a bug that needs reporting? Cheers, Sam ___ 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 Nova APIs from Javascript: possible?
Awesome Javier Anxiously waiting for a meeting with you guys to see your progress! Cheers Diego -- Diego Parrilla http://www.stackops.com/*CEO* *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 | skype:diegoparrilla* * http://www.stackops.com/ * * On Thu, Apr 26, 2012 at 9:50 AM, javier cerviño jcerv...@dit.upm.es wrote: Hi all, I'm glad to hear that there's a lot of interest in the implementation of Openstack JavaScript clients. Actually, in my group we're developing a single page application developed entirely in JavaScript, that widely supports Nova and Keystone APIs. This work is part of a European Project called FI-Ware (http://www.fi-ware.eu/), in which we are currently using Openstack APIs. We've modified Nova and Keystone installations by adding CORS support. We did it by implementing a kind of filter on their APIs. For doing this we used Adam's implementation (https://github.com/adrian/swift/tree/cors), and we adapted it to Nova and Keystone components. We also developed a JS library (http://ging.github.com/jstack/) that can be used by both web and Node.js applications, for example. This library aims to provide same functionalities as python-novaclient, adding support for Keystone API. And finally we are copying Openstack horizon functionality, using JS library and other frameworks such as jQuery and Backbone.js to implement the web application. This web application is an early-stage work, but we will probably publish it by the end of this week. I will let you know the github link. We didn't find much problems with CORS implementation and support in browsers. For the time being, according to our experiments, the only web browser that is not usable at all with this technology is Internet Explorer, but we have tried it in Google Chrome, Safari and Firefox as well and we didn't have any problems. Cheers, Javier Cerviño. On 26 April 2012 06:28, Nick Lothian nick.loth...@gmail.com wrote: On Thu, Apr 26, 2012 at 5:49 AM, Adam Young ayo...@redhat.com wrote: Let me try to summarize: 1. If you are running from a web browser, post requests to hosts or ports other than the origin are allowed, but the headers cannot be modified. This prevents the addition of the token from Keystone to provide single sign on. 2. There are various browser side technologies (JSONP, CORS) that get around this limitation, but they are typically not enabled, and can be considered security issues. While implementing these might require support from teh Openstack server, they are fundamentally browser decisions. This is inaccurate. JSONP is supported by all browsers since ~Netscape 4.0. CORS is supported by all modern browsers: IE 8, Firefox 3.5, Chrome 3, Safari 4 (See http://en.wikipedia.org/wiki/Cross-origin_resource_sharing#Browser_support ). Additionally, CORS support is not a browser decision - the server has to EXPLICITLY opt-in to support it. Obviously CORS support *can* be a security issue - that is why it is disabled unless the server enables it. I do not believe that CORS support adds any additional security issues above what the OpenStack APIs already face. Specially, the most common problem (CSRF) is not an issue here because the APIs are not authorised on a session basis. [snip] I've been working on Single Sign on Issues for another project for the past year and a half. Here's a couple things I've learned. Kerberos is designed to solve this problem. It has the benefit of being integrated into the browser. Where Kerberos fails is that: typically it only allows a single authentication provider (KDC in Kerberso speak) and it does not work well with Firewalls. The only crytographically secure way to authenticate on the web that can get around the firewall issue is Client side X509 certificates. This is the foundation for https://blueprints.launchpad.net/keystone/+spec/pki. This could, in theory, work in with OAuth, OpenID, or some other distributed authorization service, or we could embed the authorization information right into the Certitificate, which is what I suggest we do. To be clear, identity/authorisation is NOT the problem here. The OpenStack APIs work well for my use cases, once I work around the cross domain POST problem. However, I've also worked with SSO solutions. The simple truth is that client side certificates do not play well with the web - browser support ranges from non-existent (on some mobile platforms - see http://mobilitydojo.net/2010/12/28/client-certificate-support-across-mobile-platforms-a-summary/ ) to abysmal (there is a reason why many websites that use certificates end up using a Java applet), and their interaction with cross domain Javascript is unknown. Even if certificates did work for identification, CORS would still be needed - many OpenStack APIs
Re: [Openstack] Pending reviews
Russell Bryant wrote: It was nice to see a number of discussions at the summit in this area. The biggest backlog is nova, and there are discussions of both splitting parts out to make nova smaller, as well as adopting feature branches and merge windows. The feature branches could have more reviewers that are experts in that area, but not necessarily nova-core. Hopefully these things will help in the Folsom cycle. I suspect the backlog in linked to the design summit and people taking time off the week after. It should be gradually absorbed in the following days. The long-term solution is indeed smaller groups of topic-experts reviewers being responsible for a smaller batch of reviews. In the short term, we might review nova-core membership to make sure it still matches people who can actually regularly commit time to the review duty. Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] database migration cleanup
Vishvananda Ishaya wrote: +1. Might be nice to have some kind of test to verify that the new migration leaves the tables in exactly the same state as the old migrations. Sounds like a good way to avoid nasty regressions. And maybe run that test (at least once) over the range of supported databases (SQLite, MySQL, PostgreSQL) ? -- 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
Re: [Openstack] [OpenStack][Nova] Minimum required code coverage per file
Joe Gordon wrote: It would nice to initially see the code coverage delta per merge proposal as a comment in gerrit (similar to SmokeStack), and not as a gating factor. +1 Sounds like a good way to evaluate how blocking it should be, and use it to make more informed decisions on the quality of a patch. -- 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
Re: [Openstack] questions about IP addressing and network config
On Thu, Apr 26, 2012 at 10:31 PM, Vishvananda Ishaya vishvana...@gmail.comwrote: On Apr 25, 2012, at 7:31 PM, Jimmy Tsai wrote: Hi everyone, I'm running with Essex 2012.1, and have some questions about the nova network operation, 1. Is it possible manually assigned IP address to a launched instance, my situation is : after instance boot up (OS: CentOS 6.2), I changed the /etc/sysconfig/network-scripts/ifcfg-eth0 setting from dhcp to static (the same subnet as created by command : nova-manage create network), and restart the network service, And then I couldn't ssh or ping the instance from other server with the same subnet. What is the problem ? I checked the iptables policies on the compute host, and find nothing about the DROP packets. I also tried to changed the record from nova.fixed_ips table and libvirt.xml of the instance, then reboot the instance, still not worked. I used FlatDHCP as my network manager. You can't do this. Libvirt sets up no mac spoofing and no ip spoofing so the ip address needs to match the dhcp'd one. You should be able to switch to a static and use the same info that you get from dhcp though. 2. According to the first question, I have another requirement to set up a loopback IP address (lo:0) on the running instance, after setting was completed,I couldn't ping or ssh the loopback IP from the same subnet, and I tried to set a alias IP address with eth0:0, but still not get worked. Any ideas with this ? Not sure I guess it's the same issue as with setting a different IP from what dnsmasq provided. You can try ebtables -F; ebtables -t nat -F to flush those anti spoofing rules. 3. Is there any way to use 2 NICs with different subnets on instances? I want to separate the network traffic. Now I'm running with one bridged interface (br100), and it works well. In order to backup the large log files, I'm planing to use 2 NICs for the compute hosts, I want use 2 vNICs on instance, one for web service and the other for log backup, I think I should create a new network for the second bridged interface, but I can't find any document to guild me. This is definitely possible with FlatManager (You could use cloud_config drive and some version of contrib/openstack-config converted to work with centos to set up the interfaces) It was possible at one point with FlatDHCPManager as well by creating multiple networks and using a specific combination of config options like use_single_default_gateway. I don' t know if anyone has tried this for a while so there may be issues with it. You might try creating a second network and setting use_single_default_gateway and see what happens. Confirm that it works with Essex release. If you don't specify use_single_default_gateway=true your default route will be jumping from one interface to another. If you both subnets are covered by --fixed_network, it's fine even without setting the use_single_default_gateway. There are plans underway to support this by only dhcping the first interface and allowing a guest agent to set up the other interfaces, but it isn't in place yet. 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 -- Mike Scherbakov ___ 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
- Original Message - 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… Yep, one approach would be for the copy script to decorate the common code with whatever signals the coverage exclusion (e.g. #pragma: no cover) so that the code is counted in the openstack-common coverage metrics, but not counted after being copied into nova/glance/wherever. Cheers, Eoghan ___ 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] database migration cleanup
https://review.openstack.org/#/c/6847/ Nice! * Migrations added during Folsom release cycle could be compacted during E release cycle. TBD if/when we do the next compaction. An alternative idea would be to do the compaction *prior* to the Folsom relase instead of after, so that the cleanest possible migration path is presented to non-trunk-chasing users. It could for example be a task that's part of spinning up the first Folsom-RC. Its unlikely that after new migrations are added after the release candidate goes out the door (as these are generally associated with non-trivial new features, which would have missed the boat at that late stage). But if there are any, these would have to be adde to the squashed aggregate migration from the get-go. Cheers, Eoghan ___ 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] Mailing-list split
Hello everyone, TL;DR summary: Due to traffic exploding, we will split the current openstack list into user / usage topics (openstack list) and development / next-version topics (openstack-dev list). Long version: At the Communication session at the design summit [1] we looked at the state of our communication media in general, and mailing-list in particular [2]. [1] http://folsomdesignsummit2012.sched.org/event/366accca0fda271fc23e82b9cb5162cc [2] http://etherpad.openstack.org/FolsomCommunication The traffic on the openstack@lists.launchpad.net list doubled in the last 4 months [3], with more users and deployers asking for information on OpenStack projects. It becomes difficult for contributors to properly prioritize their ML reading, and we can no longer have all the discussions in the same place. [3] http://openstack.markmail.org/ The proposal is to split between: 1/ Usage, deployment, Essex / current-stable discussions 2/ Development, contribution, Folsom / forward-looking discussions A new list will be created for (2) and existing contributors will be asked to subscribe to that new list. Since we expect to have a more disciplined/focused group in that new list, we'll define a set of subject prefixes that should be used for easier client-side/at-a-glance filtering of discussions: [General] Affects all projects [Swift] [Nova] [Glance] [Quantum] [Horizon] [Keystone] Project-specific [Common] openstack-common [QA] [CI] [Docs] Discussions / Information on specific topics [...] Add your own here To keep that list usable, I suggest we aggressively enforce those topics and redirect inappropriate discussions to the other list when necessary. 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. There was a suggestion during the session of using umbrella/siblings lists to aggregate content from multiple project-specific sublists. I reviewed the options and I think it introduces a lot of complexity, reduces flexibility in adding new topics, so client-side filtering sounds like a better bet. If most people use subject prefixes appropriately, keeping it simple is probably the best bet. We'll let you know when the new list is set up. Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Mailing-list split
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. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ 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] How to let Flat Networking wok in Essex?
Hi Shake Chen, Essex on Ubuntu . The following Configured using KVM, Flat, MySQL, and Glance, API is OpenStack (or EC2) 1. Edit your network interfaces configuration to look like the following example: vi /etc/network/interfaces # The loopback network interface auto lo iface lo inet loopback auto eth0 auto br100 iface br100 inet static bridge_ports eth0 bridge_stp off bridge_maxwait 0 bridge_fd 0 address 11.204.15.10 netmask 255.255.255.0 broadcast 11.204.15.255 gateway 11.204.15.1 2. /etc/nova/nova.conf file will have the following : --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --allow_admin_api=true --use_deprecated_auth=false --auth_strategy=keystone --scheduler_driver=nova.scheduler.simple.SimpleScheduler --s3_host=11.204.15.10 --ec2_host=11.204.15.10 --rabbit_host=11.204.15.10 --cc_host=11.204.15.10 --nova_url=http://11.204.15.10:8774/v1.1/ --routing_source_ip=11.204.15.10 --glance_api_servers=11.204.15.10:9292 --image_service=nova.image.glance.GlanceImageService --iscsi_ip_prefix=131.10.4 --sql_connection=mysql://root:password@11.204.15.10/nova --ec2_url=http://11.204.15.10:8773/services/Cloud --keystone_ec2_url=http://11.204.15.10:5000/v2.0/ec2tokens --api_paste_config=/etc/nova/api-paste.ini --libvirt_type=kvm --libvirt_use_virtio_for_bridges=true --start_guests_on_host_boot=true --resume_guests_state_on_host_boot=true --vnc_enabled=true --vncproxy_url=http://11.204.15.10:6080 --vnc_console_proxy_url=http://11.204.15.10:6080 # network specific settings --network_manager=nova.network.manager.FlatManager --flat_interface=eth0 --flat_network_bridge=br100 --fixed_range=131.10.4.0/24 --network_size=256 --iscsi_helper=tgtadm --connection_type=libvirt --root_helper=sudo nova-rootwrap --verbose 3. Create private network nova-manage network create private --fixed_range_v4=131.10.4.0/24 --num_networks=1 --bridge=br100 --bridge_interface=eth0 --network_size=256 Meena Raja Consultant __ WIPRO TECHNOLOGIES No 53/1 Ganapa Towers ,Near Madivala Police Station , Hosur Main Road ,Bangalore-560068 Hand Phone : +91-9880549725 | Desk : +91-80-39912554 |Fax No: +91-80-25502160 Email : raja.me...@wipro.com | Website : www.wipro.com From: openstack-bounces+raja.meena=wipro@lists.launchpad.net [openstack-bounces+raja.meena=wipro@lists.launchpad.net] on behalf of Shake Chen [shake.c...@gmail.com] Sent: Friday, April 27, 2012 10:43 AM To: openstack@lists.launchpad.net Subject: [Openstack] How to let Flat Networking wok in Essex? HI Now I can config FlatHHCP mode and working. but the Flat netwok can not working . who can share the the config 1: /etc/network/interface 2: /etc/nova/nova.conf 3: how to create private network fro vm -- Shake Chen Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ 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 I think the procedure documented there works fine for gnu projects, but that something special has to be done for projects hosted elsewhere. I'll check and get back to you. 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. ___ 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] questions about IP addressing and network config
Thanks Vish Mike. It works very well after flush the anti-spoofing rules , I change the IP address and bind alias IP to an interface, but when I restart nova-network and nova-compute , I can't ping neither the IP I changed nor the instances I haven't changed. I'll try to figure out what happened with that !! Even I change the IP address, I can't not see the correct address on Dashboard, because the record of nova.fixed_ips not changed. I should try with FlatManager to allocate static IP. Thanks, -Jimmy 2012/4/27 Mike Scherbakov mih...@gmail.com On Thu, Apr 26, 2012 at 10:31 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: On Apr 25, 2012, at 7:31 PM, Jimmy Tsai wrote: Hi everyone, I'm running with Essex 2012.1, and have some questions about the nova network operation, 1. Is it possible manually assigned IP address to a launched instance, my situation is : after instance boot up (OS: CentOS 6.2), I changed the /etc/sysconfig/network-scripts/ifcfg-eth0 setting from dhcp to static (the same subnet as created by command : nova-manage create network), and restart the network service, And then I couldn't ssh or ping the instance from other server with the same subnet. What is the problem ? I checked the iptables policies on the compute host, and find nothing about the DROP packets. I also tried to changed the record from nova.fixed_ips table and libvirt.xml of the instance, then reboot the instance, still not worked. I used FlatDHCP as my network manager. You can't do this. Libvirt sets up no mac spoofing and no ip spoofing so the ip address needs to match the dhcp'd one. You should be able to switch to a static and use the same info that you get from dhcp though. 2. According to the first question, I have another requirement to set up a loopback IP address (lo:0) on the running instance, after setting was completed,I couldn't ping or ssh the loopback IP from the same subnet, and I tried to set a alias IP address with eth0:0, but still not get worked. Any ideas with this ? Not sure I guess it's the same issue as with setting a different IP from what dnsmasq provided. You can try ebtables -F; ebtables -t nat -F to flush those anti spoofing rules. 3. Is there any way to use 2 NICs with different subnets on instances? I want to separate the network traffic. Now I'm running with one bridged interface (br100), and it works well. In order to backup the large log files, I'm planing to use 2 NICs for the compute hosts, I want use 2 vNICs on instance, one for web service and the other for log backup, I think I should create a new network for the second bridged interface, but I can't find any document to guild me. This is definitely possible with FlatManager (You could use cloud_config drive and some version of contrib/openstack-config converted to work with centos to set up the interfaces) It was possible at one point with FlatDHCPManager as well by creating multiple networks and using a specific combination of config options like use_single_default_gateway. I don' t know if anyone has tried this for a while so there may be issues with it. You might try creating a second network and setting use_single_default_gateway and see what happens. Confirm that it works with Essex release. If you don't specify use_single_default_gateway=true your default route will be jumping from one interface to another. If you both subnets are covered by --fixed_network, it's fine even without setting the use_single_default_gateway. There are plans underway to support this by only dhcping the first interface and allowing a guest agent to set up the other interfaces, but it isn't in place yet. 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 -- Mike Scherbakov ___ 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 Nova APIs from Javascript: possible?
I'd be really interested to hear how you go on with the CORS middleware Javier. Did it work as-is or did you have to modify it? Was there much effort involved in using it with Nova? From your experience it sounds like there's decent CORS support in browsers now so it's probably time to submit this change to gerrit. Adrian 2012/4/27 Diego Parrilla Santamaría diego.parrilla.santama...@gmail.com Awesome Javier Anxiously waiting for a meeting with you guys to see your progress! Cheers Diego -- Diego Parrilla http://www.stackops.com/*CEO* *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 | skype:diegoparrilla* * http://www.stackops.com/ * * On Thu, Apr 26, 2012 at 9:50 AM, javier cerviño jcerv...@dit.upm.eswrote: Hi all, I'm glad to hear that there's a lot of interest in the implementation of Openstack JavaScript clients. Actually, in my group we're developing a single page application developed entirely in JavaScript, that widely supports Nova and Keystone APIs. This work is part of a European Project called FI-Ware (http://www.fi-ware.eu/), in which we are currently using Openstack APIs. We've modified Nova and Keystone installations by adding CORS support. We did it by implementing a kind of filter on their APIs. For doing this we used Adam's implementation (https://github.com/adrian/swift/tree/cors), and we adapted it to Nova and Keystone components. We also developed a JS library (http://ging.github.com/jstack/) that can be used by both web and Node.js applications, for example. This library aims to provide same functionalities as python-novaclient, adding support for Keystone API. And finally we are copying Openstack horizon functionality, using JS library and other frameworks such as jQuery and Backbone.js to implement the web application. This web application is an early-stage work, but we will probably publish it by the end of this week. I will let you know the github link. We didn't find much problems with CORS implementation and support in browsers. For the time being, according to our experiments, the only web browser that is not usable at all with this technology is Internet Explorer, but we have tried it in Google Chrome, Safari and Firefox as well and we didn't have any problems. Cheers, Javier Cerviño. On 26 April 2012 06:28, Nick Lothian nick.loth...@gmail.com wrote: On Thu, Apr 26, 2012 at 5:49 AM, Adam Young ayo...@redhat.com wrote: Let me try to summarize: 1. If you are running from a web browser, post requests to hosts or ports other than the origin are allowed, but the headers cannot be modified. This prevents the addition of the token from Keystone to provide single sign on. 2. There are various browser side technologies (JSONP, CORS) that get around this limitation, but they are typically not enabled, and can be considered security issues. While implementing these might require support from teh Openstack server, they are fundamentally browser decisions. This is inaccurate. JSONP is supported by all browsers since ~Netscape 4.0. CORS is supported by all modern browsers: IE 8, Firefox 3.5, Chrome 3, Safari 4 (See http://en.wikipedia.org/wiki/Cross-origin_resource_sharing#Browser_support ). Additionally, CORS support is not a browser decision - the server has to EXPLICITLY opt-in to support it. Obviously CORS support *can* be a security issue - that is why it is disabled unless the server enables it. I do not believe that CORS support adds any additional security issues above what the OpenStack APIs already face. Specially, the most common problem (CSRF) is not an issue here because the APIs are not authorised on a session basis. [snip] I've been working on Single Sign on Issues for another project for the past year and a half. Here's a couple things I've learned. Kerberos is designed to solve this problem. It has the benefit of being integrated into the browser. Where Kerberos fails is that: typically it only allows a single authentication provider (KDC in Kerberso speak) and it does not work well with Firewalls. The only crytographically secure way to authenticate on the web that can get around the firewall issue is Client side X509 certificates. This is the foundation for https://blueprints.launchpad.net/keystone/+spec/pki. This could, in theory, work in with OAuth, OpenID, or some other distributed authorization service, or we could embed the authorization information right into the Certitificate, which is what I suggest we do. To be clear, identity/authorisation is NOT the problem here. The OpenStack APIs work well for my use cases, once I work around the cross domain POST problem. However, I've also worked with SSO solutions. The simple truth is that client side certificates do not play well with the web - browser support ranges from
Re: [Openstack] questions about IP addressing and network config
Jimmy, Nova is designed to manage IP addresses. That means that even with Flat manager it will be allocating IP addresses for you, storing them in DB. The difference btw FlatDHCP is Flat injects /etc/network/interfaces to the instance, not providing IP by DHCP. So, anti-spoofing rules should be the same (I never checked though for Flat). If you want to provide your own addresses to instances, I believe you will need to extend nova code to provide your custom IP address in API request, and then if it's not already allocated, it should get allocated. Regards, On Fri, Apr 27, 2012 at 3:27 PM, Jimmy Tsai cmi...@gmail.com wrote: Thanks Vish Mike. It works very well after flush the anti-spoofing rules , I change the IP address and bind alias IP to an interface, but when I restart nova-network and nova-compute , I can't ping neither the IP I changed nor the instances I haven't changed. I'll try to figure out what happened with that !! Even I change the IP address, I can't not see the correct address on Dashboard, because the record of nova.fixed_ips not changed. I should try with FlatManager to allocate static IP. Thanks, -Jimmy 2012/4/27 Mike Scherbakov mih...@gmail.com On Thu, Apr 26, 2012 at 10:31 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: On Apr 25, 2012, at 7:31 PM, Jimmy Tsai wrote: Hi everyone, I'm running with Essex 2012.1, and have some questions about the nova network operation, 1. Is it possible manually assigned IP address to a launched instance, my situation is : after instance boot up (OS: CentOS 6.2), I changed the /etc/sysconfig/network-scripts/ifcfg-eth0 setting from dhcp to static (the same subnet as created by command : nova-manage create network), and restart the network service, And then I couldn't ssh or ping the instance from other server with the same subnet. What is the problem ? I checked the iptables policies on the compute host, and find nothing about the DROP packets. I also tried to changed the record from nova.fixed_ips table and libvirt.xml of the instance, then reboot the instance, still not worked. I used FlatDHCP as my network manager. You can't do this. Libvirt sets up no mac spoofing and no ip spoofing so the ip address needs to match the dhcp'd one. You should be able to switch to a static and use the same info that you get from dhcp though. 2. According to the first question, I have another requirement to set up a loopback IP address (lo:0) on the running instance, after setting was completed,I couldn't ping or ssh the loopback IP from the same subnet, and I tried to set a alias IP address with eth0:0, but still not get worked. Any ideas with this ? Not sure I guess it's the same issue as with setting a different IP from what dnsmasq provided. You can try ebtables -F; ebtables -t nat -F to flush those anti spoofing rules. 3. Is there any way to use 2 NICs with different subnets on instances? I want to separate the network traffic. Now I'm running with one bridged interface (br100), and it works well. In order to backup the large log files, I'm planing to use 2 NICs for the compute hosts, I want use 2 vNICs on instance, one for web service and the other for log backup, I think I should create a new network for the second bridged interface, but I can't find any document to guild me. This is definitely possible with FlatManager (You could use cloud_config drive and some version of contrib/openstack-config converted to work with centos to set up the interfaces) It was possible at one point with FlatDHCPManager as well by creating multiple networks and using a specific combination of config options like use_single_default_gateway. I don' t know if anyone has tried this for a while so there may be issues with it. You might try creating a second network and setting use_single_default_gateway and see what happens. Confirm that it works with Essex release. If you don't specify use_single_default_gateway=true your default route will be jumping from one interface to another. If you both subnets are covered by --fixed_network, it's fine even without setting the use_single_default_gateway. There are plans underway to support this by only dhcping the first interface and allowing a guest agent to set up the other interfaces, but it isn't in place yet. 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 -- Mike Scherbakov -- Mike Scherbakov ___ 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] Swift authentication using keystone (Essex deploy manual)
Hey there I'm installing my OpenStack Essex environment with ubuntu 12.04 using the new deploy manual from docs.openstack.org and i'm having problems to make swift work with keystone. I had everything installed but swift, because as far as I remember the manual didn't had a swift insllation and setup section, but now it does so I'm using it. I installed everything in a single node (192.168.100.140) using the manual, and now I'm installing swift in another single node (192.168.100.138) using an old swift manual for a all-in-one installation without keystone. After I made swift work without keystone, I setup the endpoint for my swift node, and used the proxy-server.conf file from the new manual. Here's the output when I get my token from keystone http://paste.openstack.org/show/13988/ and then I try to use it to list swift containers but it gives me a 503 http error http://paste.openstack.org/show/13989/ my proxy-server.conf file http://paste.openstack.org/show/13991/ Can someone help me to configure that ___ 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
On 04/27/2012 06:11 AM, Jim Meyering wrote: 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 I think the procedure documented there works fine for gnu projects, but that something special has to be done for projects hosted elsewhere. I'll check and get back to you. Awesome - and thanks. It's entirely possible that our Jim Blair already knows a decent amount of that, as he set up most of the FSF's mail and mailing list infrastructure, iirc. BUT - that was several years ago, so it's also possible something has changed. :) 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. ___ 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] Mailing-list split
Hey everyone! On 04/27/2012 05:04 AM, 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. Just to be clear - I definitely think that mailing lists are an important part of dev infrastructure and would love for this to be a fully integrated part of all of the rest of our tools. However, the current set of active infrastructure team members have huge todo lists at the moment. So the biggest home run from my perspective would be if someone out there had time or resources and wanted to join us on the infra team to manage this on our existing resources (turns out we have plenty of servers for running this, and even a decent amount of expertise, just missing manpower). The existing team would be more than happy to be involved, and it would help avoid get-hit-by-a-truck issues. We're a pretty friendly bunch, I promise. Any takers? Anybody want to pony up somebody with some bandwidth to admin a mailman? Respond back here or just find us in #openstack-infra and we'll get you plugged in and stuff. Thanks! 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
Re: [Openstack] Using Nova APIs from Javascript: possible?
Hi! We have just published the code of the portal in Github. You can find it in https://github.com/ging/horizon-js. It will only work with Keystone and Nova if they have CORS implemented. Adrian, we didn't make big changes in your code, only logger classes and a little problem we found with PUT requests in some cases (I have to take a deeper look into this problem, anyway). We've made tests from iPhone, iPad, Safari, Firefox and Chrome and we didn't have any problems. But on the other hand CORS doesn't work in IE9 with PUT and DELETE methods. Next week I will test it with Android and Opera browsers. Sure! It will be very interesting to submit your code to gerrit!! Diego, I will talk with Joaquin to check if we can show you a demo in two weeks!! Cheers, Javier. 2012/4/27 Adrian Smith adrian_f_sm...@dell.com I'd be really interested to hear how you go on with the CORS middleware Javier. Did it work as-is or did you have to modify it? Was there much effort involved in using it with Nova? From your experience it sounds like there's decent CORS support in browsers now so it's probably time to submit this change to gerrit. Adrian 2012/4/27 Diego Parrilla Santamaría diego.parrilla.santama...@gmail.com Awesome Javier Anxiously waiting for a meeting with you guys to see your progress! Cheers Diego -- Diego Parrilla http://www.stackops.com/*CEO* *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 | skype:diegoparrilla* * http://www.stackops.com/ * * On Thu, Apr 26, 2012 at 9:50 AM, javier cerviño jcerv...@dit.upm.eswrote: Hi all, I'm glad to hear that there's a lot of interest in the implementation of Openstack JavaScript clients. Actually, in my group we're developing a single page application developed entirely in JavaScript, that widely supports Nova and Keystone APIs. This work is part of a European Project called FI-Ware (http://www.fi-ware.eu/), in which we are currently using Openstack APIs. We've modified Nova and Keystone installations by adding CORS support. We did it by implementing a kind of filter on their APIs. For doing this we used Adam's implementation (https://github.com/adrian/swift/tree/cors), and we adapted it to Nova and Keystone components. We also developed a JS library (http://ging.github.com/jstack/) that can be used by both web and Node.js applications, for example. This library aims to provide same functionalities as python-novaclient, adding support for Keystone API. And finally we are copying Openstack horizon functionality, using JS library and other frameworks such as jQuery and Backbone.js to implement the web application. This web application is an early-stage work, but we will probably publish it by the end of this week. I will let you know the github link. We didn't find much problems with CORS implementation and support in browsers. For the time being, according to our experiments, the only web browser that is not usable at all with this technology is Internet Explorer, but we have tried it in Google Chrome, Safari and Firefox as well and we didn't have any problems. Cheers, Javier Cerviño. On 26 April 2012 06:28, Nick Lothian nick.loth...@gmail.com wrote: On Thu, Apr 26, 2012 at 5:49 AM, Adam Young ayo...@redhat.com wrote: Let me try to summarize: 1. If you are running from a web browser, post requests to hosts or ports other than the origin are allowed, but the headers cannot be modified. This prevents the addition of the token from Keystone to provide single sign on. 2. There are various browser side technologies (JSONP, CORS) that get around this limitation, but they are typically not enabled, and can be considered security issues. While implementing these might require support from teh Openstack server, they are fundamentally browser decisions. This is inaccurate. JSONP is supported by all browsers since ~Netscape 4.0. CORS is supported by all modern browsers: IE 8, Firefox 3.5, Chrome 3, Safari 4 (See http://en.wikipedia.org/wiki/Cross-origin_resource_sharing#Browser_support ). Additionally, CORS support is not a browser decision - the server has to EXPLICITLY opt-in to support it. Obviously CORS support *can* be a security issue - that is why it is disabled unless the server enables it. I do not believe that CORS support adds any additional security issues above what the OpenStack APIs already face. Specially, the most common problem (CSRF) is not an issue here because the APIs are not authorised on a session basis. [snip] I've been working on Single Sign on Issues for another project for the past year and a half. Here's a couple things I've learned. Kerberos is designed to solve this problem. It has the benefit of being integrated into the browser. Where Kerberos fails is that: typically it only allows a single authentication provider (KDC in Kerberso
Re: [Openstack] Mailing-list split
On Fri, Apr 27, 2012 at 8:46 AM, Monty Taylor mord...@inaugust.com wrote: Hey everyone! On 04/27/2012 05:04 AM, 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. Just to be clear - I definitely think that mailing lists are an important part of dev infrastructure and would love for this to be a fully integrated part of all of the rest of our tools. However, the current set of active infrastructure team members have huge todo lists at the moment. So the biggest home run from my perspective would be if someone out there had time or resources and wanted to join us on the infra team to manage this on our existing resources (turns out we have plenty of servers for running this, and even a decent amount of expertise, just missing manpower). The existing team would be more than happy to be involved, and it would help avoid get-hit-by-a-truck issues. We're a pretty friendly bunch, I promise. Any takers? Anybody want to pony up somebody with some bandwidth to admin a mailman? Respond back here or just find us in #openstack-infra and we'll get you plugged in and stuff. Thanks! Monty Count me in, Monty. I've been managing mailman lists for about 12 years now (and, incidentally, Barry and I are bruthas from anutha mutha), so I'd be quite comfortable handling those responsibilities. I can couple it with the python.org SIG mail list that I manage, so there'd be zero context switching. d ___ 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] database migration cleanup
- Original Message - From: Eoghan Glynn egl...@redhat.com To: Dan Prince dpri...@redhat.com Cc: openstack@lists.launchpad.net Sent: Friday, April 27, 2012 5:45:27 AM Subject: Re: [Openstack] database migration cleanup https://review.openstack.org/#/c/6847/ Nice! * Migrations added during Folsom release cycle could be compacted during E release cycle. TBD if/when we do the next compaction. An alternative idea would be to do the compaction *prior* to the Folsom relase instead of after, so that the cleanest possible migration path is presented to non-trunk-chasing users. It could for example be a task that's part of spinning up the first Folsom-RC. Its unlikely that after new migrations are added after the release candidate goes out the door (as these are generally associated with non-trivial new features, which would have missed the boat at that late stage). But if there are any, these would have to be adde to the squashed aggregate migration from the get-go. I thought about this... but that still leaves only a couple weeks to catch any issues that might come up in the release candidate phase. Also, using the RC makes the compaction point a bit more fuzzy for end users who are following trunk more closely. I do like that it would keep the release tree cleaner however. Performing the compaction after release is sort of a middle ground approach which should allow us to clean house from time to time but also keep things stable around release time. Cheers, Eoghan ___ 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] database migration cleanup
On 04/26/2012 03:24 PM, Dan Prince wrote: snip I think this scheme would support users who follow stable releases as well as users who follow trunk very closely. We talked about this at the conference but I thought this issue might be near and dear to some of our end users so it was worth discussing on the list. What are general thoughts on this approach? Is there any support in sqlalchemy, or related tools, to handle migrations the way rails does, where a schema file is created at the end of every migration? It would be ideal if we both had a full migration history, as well as a short cut at any snap shot to get to the end. -Sean -- Sean Dague IBM Linux Technology Center email: slda...@us.ibm.com alt-email: sda...@linux.vnet.ibm.com ___ 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] [Metering] First meeting for the Metering project
On 04/25/2012 09:10 AM, Nick Barcet wrote: Thanks to the 16 persons that took the time to give their preference on Doodle [1]. The poll is now closed and the meeting time that came out of it is: Thursdays at 4pm UTC on #openstack-metering I was not sure if we could use #openstack-meeting as we are not yet an official project, lkm if you have an opinion on this. The proposed agenda can be found at [2]. Anyone is welcome to attend. The meeting occurred as planned, and overran... Nevertheless a lot of good decisions were made, the obviously most important one grin being the project name: ceilometer. For a more complete meeting summary, go visit: http://wiki.openstack.org/Meetings/MeteringAgenda/meeting-0-summary Next week we will have for objective to find an agreement on schema and counter definitions. If anyone does not do it before me I'll fire an introduction email on the subject soon (sometime this we), as we agreed to start the discussion via mailing list and use the irc meeting to finalize the choices. Nick signature.asc Description: OpenPGP digital 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] Public image repository via a synchronization script
On Wed, 25 Apr 2012, Justin Santa Barbara wrote: I think it would be very convenient to have public image repositories and an easy way to use them, so someone installing OpenStack can easily get images into Glance with minimal work. At the design summit, there were a number of talks which all seemed to hinge on how to get an image into glance from a public store. I'd like to make a proposal to get the ball rolling, which we can collectively pick apart to figure out the best way. 1. A public image repository lives on an HTTP / FTP / ... site and can be dumb. (Glance could one day be the server here as well, but this should also work on a CDN or simple webserver etc). 2. Each image is stored as a (possibly compressed) file. fwiw, qcow images support compression inside: qemu-img convert -c disk.img -O qcow2 my.qcow2 compression is potentially useful elsewhere. It might be good thoguh, in your properties to explicitly list this rather than implying by the name. 3. Each image has a .properties file alongside it. 4. There is a 'directory' file which lists the property files. An md5sum of the directory is easy, and the hashes be useful generally. 5. If there are different sets of images, we have multiple directory files. They can point to the same images. 6. We don't try to solve security initially. But this could be as simple as signing the directory files, if they had hashes of all the other files (e.g. md5sum). Overall, I think this looks reasonable. A couple nits: * I don't like using md5sum as a directory file. Better to explicitly name something for that purpose. There could be other files in that directory that are not images (and would be desireable to appear in the md5sum file) * your example .properties file contains things that aren't really properties (where properties == things that would be added to glance as tags) disk_format=qcow2 container_format=bare is_public=True * Disk format, container_format are useful, but its possibly confusing as its an attribute of the image, while other things are tags. * is_public=True Just because you thought this image should be public does not mean I do when I sync it. I might suggest, something like this (hand-yaml formated): tags: org.openstack__1__os_distro=debian.org org.openstack__1__os_version=6.0.4 org.openstack__1__architecture=x64 org.openstack__1__updated_at=20120425 data: file: debian_squeeze_20120425.qcow2.gz disk_format: qcow2 container_format: bare md5sum: 224237ee1b9a341ac7d79bcebda0580d size: 627965952 compression: gzip Alternatively, 'data' above could be named 'org.openstack.sync__1__image' or something. Ben Howard has been doing something similar to this with https://code.launchpad.net/~utlemming/+junk/sync-images which reads data at https://cloud-images.ubuntu.com/query2/ I'd like to work together to get something that addresses both sets of needs. Also, if we do this well, I suppose that the glance aggregator described at https://blueprints.launchpad.net/glance/+spec/public-glance http://etherpad.openstack.org/FolsomGlanceReadOnlyGlance could potentially support this source something it presented in its aggregated list. ___ 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] Configuring Keystone in OpenStack (Essex) white-papers
On Fri, 27 Apr 2012 22:35:02 +0800 Shake Chen shake.c...@gmail.com wrote: HI Canonical provide the keystone document about how to config. http://www.canonical.com/about-canonical/resources/white-papers/configuring-keystone-openstack-essex but The document have one mistake. when I run NOVA_PUBLIC_URL=”http://$NOVA_IP:8774/v1.1/%(tenant_id)s” root@node77:~# NOVA_PUBLIC_URL=”http://$NOVA_IP:8774/v1.1/%(tenant_id)s” bash: syntax error near unexpected token `(' the error was cause by lack for (), I need add ( ) as below: NOVA_PUBLIC_URL=”http://$NOVA_IP:8774/v1.1/%;(tenant_id)s” Thanks I forwarded this off to the relevant persons. Regards chuck ___ 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] Configuring Keystone in OpenStack (Essex) white-papers
It looks like the PDF is rendering trying to render the outside quotes as \\paired smart quotes// instead of ||regular double quotes||. Try this instead: http://paste.openstack.org/raw/14073/ -Dolph On Fri, Apr 27, 2012 at 9:35 AM, Shake Chen shake.c...@gmail.com wrote: HI Canonical provide the keystone document about how to config. http://www.canonical.com/about-canonical/resources/white-papers/configuring-keystone-openstack-essex but The document have one mistake. when I run NOVA_PUBLIC_URL=”http://$NOVA_IP:8774/v1.1/%(tenant_id)s” root@node77:~# NOVA_PUBLIC_URL=”http://$NOVA_IP:8774/v1.1/%(tenant_id)s” bash: syntax error near unexpected token `(' the error was cause by lack for (), I need add ( ) as below: NOVA_PUBLIC_URL=”http://$NOVA_IP:8774/v1.1/%;(tenant_id)s” -- Shake Chen ___ 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] Configuring Keystone in OpenStack (Essex) white-papers
On 04/27/2012 04:35 PM, Shake Chen wrote: HI Canonical provide the keystone document about how to config. http://www.canonical.com/about-canonical/resources/white-papers/configuring-keystone-openstack-essex but The document have one mistake. when I run NOVA_PUBLIC_URL=”http://$NOVA_IP:8774/v1.1/%(tenant_id)s” root@node77:~# NOVA_PUBLIC_URL=”http://$NOVA_IP:8774/v1.1/%(tenant_id)s” bash: syntax error near unexpected token `(' the error was cause by lack for (), I need add ( ) as below: NOVA_PUBLIC_URL=”http://$NOVA_IP:8774/v1.1/%;(tenant_id)s” Thanks for reporting this Shake. Putting Joshua (the author of the WP) in cc to makes sure he gets it. Nick signature.asc Description: OpenPGP digital 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
[Openstack] proposal for Russell Bryant to be added to Nova Core
Russell Bryant wrote the Nova Qpid rpc implementation and is a member of the Nova security team. He has been helping chipping away at reviews and contributing to discussions for some time now. I'd like to seem him Nova core so he can help out w/ reviews... definitely the RPC ones. Dan ___ 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 Thu, Apr 26, 2012 at 12:55 PM, Salman Malik salma...@live.com wrote: Hi All, Hi Salman, 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? 2) The OVS quantum plugin seems to implement the core API functions and (viewing the code) I concluded that it just makes maintains the logical mappings e.g. b/w net IDs and VLAN IDs in a database. So how is this mapping implemented on the actual ports of OVS? Is it the OVS quantum agent responsible for directing the packets to correct input/output ports based on the updates that it gets from the database? In VLAN-mode, its even simpler than that. The agent simply puts each port as a VLAN access port for the right VLAN, based on the database, and then has OVS perform standard L2 learning to forward packets. 3) The quantum admin guide says that the nova client will be the main user of quantum and will interact with it via REST API, so it would be nice if someone can point me to the code (file path name etc.) where this happens. This is the QuantumManager code in Nova: https://github.com/openstack/nova/tree/master/nova/network/quantum One word of warning: this code will be being simplified and largely removed in Folsom, so while its useful to look at it to learn about Quantum, I'd ask around before investing the time to make significant changes to the code. PS: What is the purpose of Quantum Manager in this architecture and where should I look for its code? see above :) Dan ___ 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
Re: [Openstack] Mailing-list split
On 04/27/2012 09:44 AM, Duncan McGreggor wrote: On Fri, Apr 27, 2012 at 8:46 AM, Monty Taylor mord...@inaugust.com wrote: Hey everyone! On 04/27/2012 05:04 AM, 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. Just to be clear - I definitely think that mailing lists are an important part of dev infrastructure and would love for this to be a fully integrated part of all of the rest of our tools. However, the current set of active infrastructure team members have huge todo lists at the moment. So the biggest home run from my perspective would be if someone out there had time or resources and wanted to join us on the infra team to manage this on our existing resources (turns out we have plenty of servers for running this, and even a decent amount of expertise, just missing manpower). The existing team would be more than happy to be involved, and it would help avoid get-hit-by-a-truck issues. We're a pretty friendly bunch, I promise. Any takers? Anybody want to pony up somebody with some bandwidth to admin a mailman? Respond back here or just find us in #openstack-infra and we'll get you plugged in and stuff. Thanks! Monty Count me in, Monty. I've been managing mailman lists for about 12 years now (and, incidentally, Barry and I are bruthas from anutha mutha), so I'd be quite comfortable handling those responsibilities. I can couple it with the python.org SIG mail list that I manage, so there'd be zero context switching. You make me very happy! Let's work out the details and stuff... Check it out - it's like we're, you know, a collaborative community or something! ___ 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 Integration Part 3
On Thu, Apr 26, 2012 at 3:32 AM, Emilien Macchi emilien.openst...@gmail.com wrote: ** Hi again, After inverstigation, it finally works. I have the network on my instances in using Quantum. The fact was I've follow official OVS documentation, and you should not follow this direction : ovs-vsctl add-port br-int eth1 Hi Emilien, Which mode are you running OVS in? VLAN or tunneled? If you are using VLAN-mode (default) you need to add some physical interface to br-int, so that VLANs are trunked to the physical network. Is it possible that eth1 was also the interface you were using for IP communication on the box? That definitely won't work with OVS or the linux bridge. I'll improve the docs around that to make this more clear. If you see on the logs file of OVS, you can see that the bridge will not work properly... that's why my instances did not get the network. Can you ping me with the error messages (can be offlist)? I still don't understand what you misconfigured, or how you fixed it. I've tried ovs-vsctl del-port br-int eth1, restart all the services and now, all is working. I have now a dual-node with : Nova-*, Glance, Quantum (without authentification), Keystone, and Horizon (without Quantum UI yet). Great to hear. As I mentioned in a previous post, Horizon + Quantum isn't complete. You won't be able to create networks using Horizon, or boot VMs while specifying a particular set of vNICs. If you're interested in helping this work move forward more quickly, I'm happy to put you in touch with the right people. Dan Next steps : QoS, UI, Isolation testing, and documentation :-) I will continue to post about Quantum when I will advance in the project. Best regards Le mercredi 25 avril 2012 à 10:54 -0700, Dan Wendlandt a écrit : Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: For example, Quantum does not work with Keystone : When nova-network send an API call to Quantum-server, the token is missing in the HTTP HEADER. I've disabled Keystone at this time. That is correct. In the Quantum Admin Guide, it explains some work that was done to support Keystone Authn, but notes that this is all experimental, as the Quantum API does not support Authz. This is because the only person that calls Quantum in Essex is Nova itself. Troy Toman's team is working on Quantum Authz for Folsom, so the API can be exposed directly to tenants. *- What is working at this time :* - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum *- What is not working (yet !) :* - When I create an instance (from dashboard or with Nova CLI), the network is created with Quantum, an private IP is attributed to the instance, but when I check the instance log file, the network interface doesn't get an IP adress. Here the log : http://paste.openstack.org/show/13821 Are you able to access the VM via VNC? If you statically configure the IP does it work? What happens if you run dhcpc manually? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html Essex Horizon does not support Quantum. Its actually not just a Horizon thing, it has to do with how the Nova + Quantum integration works. Each Quantum network has to be associated with appropriate IPAM subnet, meaning the existing . For now, you need to create networks using nova-manage. If you want VMs to get the default set of NICs, you can then boot them with Horizon. If you want to specify what networks vNICs are plugged into, this is only supported via the nova boot command with the --nic option. I'll flush this out in more detail in the Quantum Admin Guide. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ -- *Emilien Macchi* Phone : +33 685 117 748 Skype : memilien69 Twitter : EmilienMacchi https://twitter.com/ Website : http://my1.fr -- ~~~ 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] Question on notifications
Yes, the publisher_id is servicename.host, so ya, you can determine the compute host from that. On Apr 25, 2012, at 4:44 PM, Joshua Harlow wrote: Hi all, I was looking at the notification outputs, which are very useful and I was wondering if the way to say figure out which hypervisor a VM is being built on. There seems to be the following key: publisher_id: compute.buildingbuild (event is compute.instance.create.end) It would seem the stuff after “compute” is the hostname, would that be correct, or should the scheduler messages be intercepted, which as example has the following: weighted_host: { host: buildingbuild, weight: -1488.0 } I would think the first practice would be right, since its from the compute node instead of the scheduler, but would like some feedback :-) Thx! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Monsyne M. Dragon OpenStack/Nova cell 210-441-0965 work x 5014190 ___ 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.
is enabled and not running my compute node is virtual machine to test and configured with qemu (2 core, 4gb, 10gb free in nova-volumes) my last log message on nova-compute is: 2012-04-27 12:22:25 DEBUG nova.virt.libvirt.connection [-] Connecting to libvirt: qemu:///system from (pid=18588) _get_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.*py*:292 libvirt is running 18420 ?Sl 0:00 /usr/sbin/libvirtd -d On Thu, Apr 26, 2012 at 10:43 PM, heut2008 heut2...@gmail.com wrote: be sure nova-compute is running and is enabled by using nova-manage service list,also confirm that the compute node have enough resources(cpu,mem,disk) . 2012/4/27 Rogerio Goncalves roge...@gmail.com: Hello, Im getting this error when launching a new instance. Failed to schedule_run_instance: No valid host was found. Is the appropriate service running? http://paste.openstack.org/show/14020/ SO Ubuntu 12.04 libvirt-bin start/running, process 4153 nova-network start/running, process 4174 nova-compute start/running, process 4187 nova-api start/running, process 4198 nova-objectstore start/running, process 4210 nova-scheduler start/running, process 4222 nova-volume start/running, process 4235 nova-vncproxy start/running, process 4246 rabbitmq is up too Thanks Rogério Gonçalves ___ 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 Integration Part 3
Hi Alan, That's a good question. I had assumed that my recent commits to https://www.github.com/openstack/openstack-manuals would automatically propagate to http://docs.openstack.org/incubation/openstack-network/admin/content/index.html, but that doesn't seem to have happened for the latest commits. Anne Gentle, can you help out here? Thanks! Dan On Thu, Apr 26, 2012 at 3:30 PM, Alan Kavanagh alan.kavan...@ericsson.comwrote: ** Hi Dan When will the revised Quantum Admin Guide be posted? Alan -- *From:* openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net[mailto: openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net] *On Behalf Of *Dan Wendlandt *Sent:* April-25-12 1:55 PM *To:* Emilien Macchi *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] Quantum Integration Part 3 Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: For example, Quantum does not work with Keystone : When nova-network send an API call to Quantum-server, the token is missing in the HTTP HEADER. I've disabled Keystone at this time. That is correct. In the Quantum Admin Guide, it explains some work that was done to support Keystone Authn, but notes that this is all experimental, as the Quantum API does not support Authz. This is because the only person that calls Quantum in Essex is Nova itself. Troy Toman's team is working on Quantum Authz for Folsom, so the API can be exposed directly to tenants. *- What is working at this time :* - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum *- What is not working (yet !) :* - When I create an instance (from dashboard or with Nova CLI), the network is created with Quantum, an private IP is attributed to the instance, but when I check the instance log file, the network interface doesn't get an IP adress. Here the log : http://paste.openstack.org/show/13821 Are you able to access the VM via VNC? If you statically configure the IP does it work? What happens if you run dhcpc manually? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html Essex Horizon does not support Quantum. Its actually not just a Horizon thing, it has to do with how the Nova + Quantum integration works. Each Quantum network has to be associated with appropriate IPAM subnet, meaning the existing . For now, you need to create networks using nova-manage. If you want VMs to get the default set of NICs, you can then boot them with Horizon. If you want to specify what networks vNICs are plugged into, this is only supported via the nova boot command with the --nic option. I'll flush this out in more detail in the Quantum Admin Guide. Dan -- ~~~ 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] [Metering] First meeting for the Metering project
On 12-04-27 10:50 AM, Nick Barcet wrote: The meeting occurred as planned, and overran... Nevertheless a lot of good decisions were made, the obviously most important one grin being the project name: ceilometer. For a more complete meeting summary, go visit: http://wiki.openstack.org/Meetings/MeteringAgenda/meeting-0-summary Next week we will have for objective to find an agreement on schema and counter definitions. If anyone does not do it before me I'll fire an introduction email on the subject soon (sometime this we), as we agreed to start the discussion via mailing list and use the irc meeting to finalize the choices. The Launchpad project was created: https://launchpad.net/ceilometer Cheers -- Francis J. Lacoste francis.laco...@canonical.com signature.asc Description: OpenPGP digital 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] database migration cleanup
- Original Message - From: Sean Dague sda...@linux.vnet.ibm.com To: openstack@lists.launchpad.net Sent: Friday, April 27, 2012 10:21:17 AM Subject: Re: [Openstack] database migration cleanup On 04/26/2012 03:24 PM, Dan Prince wrote: snip I think this scheme would support users who follow stable releases as well as users who follow trunk very closely. We talked about this at the conference but I thought this issue might be near and dear to some of our end users so it was worth discussing on the list. What are general thoughts on this approach? Is there any support in sqlalchemy, or related tools, to handle migrations the way rails does, where a schema file is created at the end of every migration? It would be ideal if we both had a full migration history, as well as a short cut at any snap shot to get to the end. Ah. Yes, the Rails schema.rb. I looked around for just this sort of thing and didn't find much. Python-migrate has some experimental support for generating models and I did make use of that initially. See 'create_model' below: [root@nova1 migrate_repo]# python ./manage.py --repository=./ --url=mysql://nova:password@localhost/nova Usage: manage.py COMMAND ... Available commands: compare_model_to_db - compare MetaData against the current database state create - create an empty repository at the specified path create_model - dump the current database as a Python model to stdout db_version - show the current version of the repository under version control downgrade- downgrade a database to an earlier version drop_version_control - removes version control from a database help - displays help on a given command make_update_script_for_model - create a script changing the old MetaData to the new (current) MetaData manage - creates a Python script that runs Migrate with a set of default values script - create an empty change Python script script_sql - create empty change SQL scripts for given database source - display the Python code for a particular version in this repository test - performs the upgrade and downgrade command on the given database update_db_from_model - modify the database to match the structure of the current MetaData upgrade - upgrade a database to a later version version - display the latest version available in a repository version_control - mark a database as under this repository's version control python-migrate's 'create_model' does not however give you something that exactly matches the schema you'd get by running the all the migrations. So auto generation doesn't appear to be an option right now. It would be nice to contribute python-migrate in this regard and get better support for model generation, etc. Maybe a good long term goal? Dan -Sean -- Sean Dague IBM Linux Technology Center email: slda...@us.ibm.com alt-email: sda...@linux.vnet.ibm.com ___ 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] database migration cleanup
- Original Message - From: Johannes Erdfelt johan...@erdfelt.com To: openstack@lists.launchpad.net Sent: Friday, April 27, 2012 10:20:38 AM Subject: Re: [Openstack] database migration cleanup On Thu, Apr 26, 2012, Dan Prince dpri...@redhat.com wrote: The OpenStack Essex release had 82 database migrations. As these grow in number it seems reasonable to clean house from time to time. Now seems as good a time as any. Mirations don't appear to be particularly slow right now, and it doesn't appear that merging migrations will make them significantly faster. What exactly is the benefit of doing this? Speed wasn't the primary motivation here I suppose. Do we really want to continue to maintain 100+ migrations in our codebase over the lifetime of the project? As we add more and more to our pep8/hacking tools this could become an annoying burden right? I mean why require end users to run migrations that add and drop the same table repeatedly? By merging migrations, we lose history in git for why the migrations were added in the first place. I'm not sure I understand? Git still has the source code for the old migrations. All you'd need to do is checkout an old version of master or look at the stable/essex, stable/diablo branches right? JE ___ 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 Integration Part 3
Ah, the Jenkins job copies to incubated and it should be incubation - fixing now. Anne On Fri, Apr 27, 2012 at 10:30 AM, Dan Wendlandt d...@nicira.com wrote: Hi Alan, That's a good question. I had assumed that my recent commits to https://www.github.com/openstack/openstack-manuals would automatically propagate to http://docs.openstack.org/incubation/openstack-network/admin/content/index.html, but that doesn't seem to have happened for the latest commits. Anne Gentle, can you help out here? Thanks! Dan On Thu, Apr 26, 2012 at 3:30 PM, Alan Kavanagh alan.kavan...@ericsson.com wrote: ** Hi Dan When will the revised Quantum Admin Guide be posted? Alan -- *From:* openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net[mailto: openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net] *On Behalf Of *Dan Wendlandt *Sent:* April-25-12 1:55 PM *To:* Emilien Macchi *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] Quantum Integration Part 3 Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: For example, Quantum does not work with Keystone : When nova-network send an API call to Quantum-server, the token is missing in the HTTP HEADER. I've disabled Keystone at this time. That is correct. In the Quantum Admin Guide, it explains some work that was done to support Keystone Authn, but notes that this is all experimental, as the Quantum API does not support Authz. This is because the only person that calls Quantum in Essex is Nova itself. Troy Toman's team is working on Quantum Authz for Folsom, so the API can be exposed directly to tenants. *- What is working at this time :* - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum *- What is not working (yet !) :* - When I create an instance (from dashboard or with Nova CLI), the network is created with Quantum, an private IP is attributed to the instance, but when I check the instance log file, the network interface doesn't get an IP adress. Here the log : http://paste.openstack.org/show/13821 Are you able to access the VM via VNC? If you statically configure the IP does it work? What happens if you run dhcpc manually? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html Essex Horizon does not support Quantum. Its actually not just a Horizon thing, it has to do with how the Nova + Quantum integration works. Each Quantum network has to be associated with appropriate IPAM subnet, meaning the existing . For now, you need to create networks using nova-manage. If you want VMs to get the default set of NICs, you can then boot them with Horizon. If you want to specify what networks vNICs are plugged into, this is only supported via the nova boot command with the --nic option. I'll flush this out in more detail in the Quantum Admin Guide. Dan -- ~~~ 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
[Openstack] [nova-compute] Startup error
Hello, I'm clueless as how to solve this problem, any ideas? DEBUG nova.utils [req-007e9c3f-2dcb-4b42-8486-800a51e272e1 None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=17035) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 336, in fire_timers timer() File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main result = function(*args, **kwargs) File /usr/lib/python2.7/dist-packages/nova/service.py, line 101, in run_server server.start() File /usr/lib/python2.7/dist-packages/nova/service.py, line 174, in start self.manager.update_available_resource(ctxt) File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2403, in update_available_resource self.driver.update_available_resource(context, self.host) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1898, in update_available_resource 'local_gb': self.get_local_gb_total(), File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1712, in get_local_gb_total stats = libvirt_utils.get_fs_info(FLAGS.instances_path) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/utils.py, line 277, in get_fs_info hddinfo = os.statvfs(path) OSError: [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 CRITICAL nova [-] [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 TRACE nova Traceback (most recent call last): 2012-04-27 16:51:48 TRACE nova File /usr/bin/nova-compute, line 49, in module 2012-04-27 16:51:48 TRACE nova service.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 413, in wait 2012-04-27 16:51:48 TRACE nova _launcher.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 131, in wait 2012-04-27 16:51:48 TRACE nova service.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait 2012-04-27 16:51:48 TRACE nova return self._exit_event.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait 2012-04-27 16:51:48 TRACE nova return hubs.get_hub().switch() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch 2012-04-27 16:51:48 TRACE nova return self.greenlet.switch() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main 2012-04-27 16:51:48 TRACE nova result = function(*args, **kwargs) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 101, in run_server 2012-04-27 16:51:48 TRACE nova server.start() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 174, in start 2012-04-27 16:51:48 TRACE nova self.manager.update_available_resource(ctxt) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2403, in update_available_resource 2012-04-27 16:51:48 TRACE nova self.driver.update_available_resource(context, self.host) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1898, in update_available_resource 2012-04-27 16:51:48 TRACE nova 'local_gb': self.get_local_gb_total(), 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1712, in get_local_gb_total 2012-04-27 16:51:48 TRACE nova stats = libvirt_utils.get_fs_info(FLAGS.instances_path) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/utils.py, line 277, in get_fs_info 2012-04-27 16:51:48 TRACE nova hddinfo = os.statvfs(path) 2012-04-27 16:51:48 TRACE nova OSError: [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 TRACE nova Exception KeyError: KeyError(140477118368240,) in module 'threading' from '/usr/lib/python2.7/threading.pyc' ignored Regards, Leander ___ 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] proposal for Russell Bryant to be added to Nova Core
+1 -- Eric Windisch On Friday, April 27, 2012 at 11:09 AM, Dan Prince wrote: Russell Bryant wrote the Nova Qpid rpc implementation and is a member of the Nova security team. He has been helping chipping away at reviews and contributing to discussions for some time now. I'd like to seem him Nova core so he can help out w/ reviews... definitely the RPC ones. Dan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net (mailto: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] proposal for Russell Bryant to be added to Nova Core
+1 from me On Apr 27, 2012, at 8:09 AM, Dan Prince dpri...@redhat.com wrote: Russell Bryant wrote the Nova Qpid rpc implementation and is a member of the Nova security team. He has been helping chipping away at reviews and contributing to discussions for some time now. I'd like to seem him Nova core so he can help out w/ reviews... definitely the RPC ones. Dan ___ 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] Code contribution
Hello How code in gerrit becomes verified? ___ 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] database migration cleanup
On Fri, Apr 27, 2012, Dan Prince dpri...@redhat.com wrote: Mirations don't appear to be particularly slow right now, and it doesn't appear that merging migrations will make them significantly faster. What exactly is the benefit of doing this? Speed wasn't the primary motivation here I suppose. Do we really want to continue to maintain 100+ migrations in our codebase over the lifetime of the project? As we add more and more to our pep8/hacking tools this could become an annoying burden right? Has that been a problem? I'm not sure I see where pep8/hacking changes would require changes to the unmerged migrations but the merged migrations wouldn't require them. Wouldn't that affect either? Looking at the logs for the migrations most of the changes (outside of PEP8 changes) appear to be sqlalchemy related changes, which will exist regardless if they are merged or not as well. I mean why require end users to run migrations that add and drop the same table repeatedly? It's hard to just grep for which migrations drop a table/column added in a previous migration. Did you see how many are like that when you merged all of the migrations together? I'm not sure I understand? Git still has the source code for the old migrations. All you'd need to do is checkout an old version of master or look at the stable/essex, stable/diablo branches right? True, you would just need to go out of your way to look at the history instead. I guess it's a matter of pros vs cons. Right now, I'd prefer to not merge them simply because I haven't seen what the benefit is. JE ___ 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] proposal for Russell Bryant to be added to Nova Core
+2 On Apr 27, 2012, at 8:09 AM, Dan Prince wrote: Russell Bryant wrote the Nova Qpid rpc implementation and is a member of the Nova security team. He has been helping chipping away at reviews and contributing to discussions for some time now. I'd like to seem him Nova core so he can help out w/ reviews... definitely the RPC ones. Dan ___ 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] Mailing-list split
On 04/27/2012 08:27 AM, Monty Taylor wrote: You make me very happy! Let's work out the details and stuff... Check it out - it's like we're, you know, a collaborative community or something! Amen! Thank you Duncan. Cheers, stef ___ 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] proposal for Russell Bryant to be added to Nova Core
On Apr 27, 2012, at 11:09 AM, Dan Prince wrote: Russell Bryant wrote the Nova Qpid rpc implementation and is a member of the Nova security team. He has been helping chipping away at reviews and contributing to discussions for some time now. I'd like to seem him Nova core so he can help out w/ reviews... definitely the RPC ones. +1 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] proposal for Russell Bryant to be added to Nova Core
On Fri, 2012-04-27 at 11:09 -0400, Dan Prince wrote: I'd like to seem him Nova core so he can help out w/ reviews... definitely the RPC ones. +1 -- Kevin L. Mitchell kevin.mitch...@rackspace.com ___ 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] [Metering] First meeting for the Metering project
On 04/27/2012 05:37 PM, Francis J. Lacoste wrote: On 12-04-27 10:50 AM, Nick Barcet wrote: The meeting occurred as planned, and overran... Nevertheless a lot of good decisions were made, the obviously most important one grin being the project name: ceilometer. For a more complete meeting summary, go visit: http://wiki.openstack.org/Meetings/MeteringAgenda/meeting-0-summary Next week we will have for objective to find an agreement on schema and counter definitions. If anyone does not do it before me I'll fire an introduction email on the subject soon (sometime this we), as we agreed to start the discussion via mailing list and use the irc meeting to finalize the choices. The Launchpad project was created: https://launchpad.net/ceilometer Thank you :-) I'm not familiar with the launchpad ways. Should I wait for the git repository to be created ? Or can I help with that ? Chers ___ 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] database migration cleanup
Even better, what would it take to try using Alembic? (http://alembic.readthedocs.org/en/latest/front.html#project-homepage) It's a big improvement over sqlalchemy. Amongst other things, migrations are not numbered, they are linked by dependancy, and run in topological-sort order. That there eliminates alot of my migration number got taken... again... problems. On Apr 27, 2012, at 10:47 AM, Dan Prince wrote: - Original Message - From: Sean Dague sda...@linux.vnet.ibm.com To: openstack@lists.launchpad.net Sent: Friday, April 27, 2012 10:21:17 AM Subject: Re: [Openstack] database migration cleanup On 04/26/2012 03:24 PM, Dan Prince wrote: snip I think this scheme would support users who follow stable releases as well as users who follow trunk very closely. We talked about this at the conference but I thought this issue might be near and dear to some of our end users so it was worth discussing on the list. What are general thoughts on this approach? Is there any support in sqlalchemy, or related tools, to handle migrations the way rails does, where a schema file is created at the end of every migration? It would be ideal if we both had a full migration history, as well as a short cut at any snap shot to get to the end. Ah. Yes, the Rails schema.rb. I looked around for just this sort of thing and didn't find much. Python-migrate has some experimental support for generating models and I did make use of that initially. See 'create_model' below: [root@nova1 migrate_repo]# python ./manage.py --repository=./ --url=mysql://nova:password@localhost/nova Usage: manage.py COMMAND ... Available commands: compare_model_to_db - compare MetaData against the current database state create - create an empty repository at the specified path create_model - dump the current database as a Python model to stdout db_version - show the current version of the repository under version control downgrade- downgrade a database to an earlier version drop_version_control - removes version control from a database help - displays help on a given command make_update_script_for_model - create a script changing the old MetaData to the new (current) MetaData manage - creates a Python script that runs Migrate with a set of default values script - create an empty change Python script script_sql - create empty change SQL scripts for given database source - display the Python code for a particular version in this repository test - performs the upgrade and downgrade command on the given database update_db_from_model - modify the database to match the structure of the current MetaData upgrade - upgrade a database to a later version version - display the latest version available in a repository version_control - mark a database as under this repository's version control python-migrate's 'create_model' does not however give you something that exactly matches the schema you'd get by running the all the migrations. So auto generation doesn't appear to be an option right now. It would be nice to contribute python-migrate in this regard and get better support for model generation, etc. Maybe a good long term goal? Dan -Sean -- Sean Dague IBM Linux Technology Center email: slda...@us.ibm.com alt-email: sda...@linux.vnet.ibm.com ___ 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 -- Monsyne M. Dragon OpenStack/Nova cell 210-441-0965 work x 5014190 ___ 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 Integration Part 3
All fixed up, let me know if you have any other issues. Thanks Jim Blair for the help. Anne On Fri, Apr 27, 2012 at 10:57 AM, Anne Gentle a...@openstack.org wrote: Ah, the Jenkins job copies to incubated and it should be incubation - fixing now. Anne On Fri, Apr 27, 2012 at 10:30 AM, Dan Wendlandt d...@nicira.com wrote: Hi Alan, That's a good question. I had assumed that my recent commits to https://www.github.com/openstack/openstack-manuals would automatically propagate to http://docs.openstack.org/incubation/openstack-network/admin/content/index.html, but that doesn't seem to have happened for the latest commits. Anne Gentle, can you help out here? Thanks! Dan On Thu, Apr 26, 2012 at 3:30 PM, Alan Kavanagh alan.kavan...@ericsson.com wrote: ** Hi Dan When will the revised Quantum Admin Guide be posted? Alan -- *From:* openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net[mailto: openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net] *On Behalf Of *Dan Wendlandt *Sent:* April-25-12 1:55 PM *To:* Emilien Macchi *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] Quantum Integration Part 3 Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: For example, Quantum does not work with Keystone : When nova-network send an API call to Quantum-server, the token is missing in the HTTP HEADER. I've disabled Keystone at this time. That is correct. In the Quantum Admin Guide, it explains some work that was done to support Keystone Authn, but notes that this is all experimental, as the Quantum API does not support Authz. This is because the only person that calls Quantum in Essex is Nova itself. Troy Toman's team is working on Quantum Authz for Folsom, so the API can be exposed directly to tenants. *- What is working at this time :* - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum *- What is not working (yet !) :* - When I create an instance (from dashboard or with Nova CLI), the network is created with Quantum, an private IP is attributed to the instance, but when I check the instance log file, the network interface doesn't get an IP adress. Here the log : http://paste.openstack.org/show/13821 Are you able to access the VM via VNC? If you statically configure the IP does it work? What happens if you run dhcpc manually? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html Essex Horizon does not support Quantum. Its actually not just a Horizon thing, it has to do with how the Nova + Quantum integration works. Each Quantum network has to be associated with appropriate IPAM subnet, meaning the existing . For now, you need to create networks using nova-manage. If you want VMs to get the default set of NICs, you can then boot them with Horizon. If you want to specify what networks vNICs are plugged into, this is only supported via the nova boot command with the --nic option. I'll flush this out in more detail in the Quantum Admin Guide. Dan -- ~~~ 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] Quantum Integration Part 3
Hi Dan, Le vendredi 27 avril 2012 à 08:28 -0700, Dan Wendlandt a écrit : Which mode are you running OVS in? VLAN or tunneled? If you are using VLAN-mode (default) you need to add some physical interface to br-int, so that VLANs are trunked to the physical network. Is it possible that eth1 was also the interface you were using for IP communication on the box? That definitely won't work with OVS or the linux bridge. I'll improve the docs around that to make this more clear. I'm using default mode : VLAN. Can you ping me with the error messages (can be offlist)? I still don't understand what you misconfigured, or how you fixed it. I actually had an issue when I executed : ovs-vsctl add-port br-int eth1 I checked on the log and could see that Quantum-Agent didn't start. After inverstigation, it's seem that it was looking for a free physical interface to bridge. I released eth1 and all worked very good. Great to hear. As I mentioned in a previous post, Horizon + Quantum isn't complete. You won't be able to create networks using Horizon, or boot VMs while specifying a particular set of vNICs. If you're interested in helping this work move forward more quickly, I'm happy to put you in touch with the right people. Of course I am ! I'm writing a documentation to install OpenStack Essex from scratch with Ubuntu 12.04 with Quantum OVS. I will to release it soon :-) 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
[Openstack] Periodic clean-up of fixed_ip addresses in multi-host DHCP mode
Hi Folks, In multi-host mode the host field of a network never seems to get set (as only IPs are allocated, not networks) However the periodic revovery task in NetworkManager uses the host field to filter what addresses it should consider cleaning up (to catch the case where the message from dnsmasq is either never sent or not delivered for some reason) if self.timeout_fixed_ips: now = utils.utcnow() timeout = FLAGS.fixed_ip_disassociate_timeout time = now - datetime.timedelta(seconds=timeout) num = self.db.fixed_ip_disassociate_all_by_timeout(context, self.host, time) if num: LOG.debug(_('Dissassociated %s stale fixed ip(s)'), num) Where db.fixed_ip_disassociate_all_by_timeout is: def fixed_ip_disassociate_all_by_timeout(_context, host, time): session = get_session() inner_q = session.query(models.Network.id).\ filter_by(host=host).\ subquery() result = session.query(models.FixedIp).\ filter(models.FixedIp.network_id.in_(inner_q)).\ filter(models.FixedIp.updated_at time).\ filter(models.FixedIp.instance_id != None).\ filter_by(allocated=False).\ update({'instance_id': None, 'leased': False, 'updated_at': utils.utcnow()}, synchronize_session='fetch') return result So what this seems to do to me is: - Find all of the fixed_ips which are: o on networks assigned to this host o Were last updated more that Timeout seconds ago o Are associated to an instance o Are not allocated Because in multi-host mode the network host field is always Null, this query does nothing apart from give the DB a good work out every 10 seconds - so there could be a slow leakage of IP addresses. Has anyone else spotted this - and if so do you have a good strategy for dealing with it ? It seems that running this on every network_manager every 10 seconds is excessive - so what still running on all netwok_managers but using a long random sleep between runs in mult-host mode ? Thoughts ? Cheers, Phil ___ 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-compute] Startup error
Hi Leander, Looks like a misconfiguration. The base path for nova's instances is typically /var/lib/nova/instances, set by the instances_path configuration option. Somehow it is being set to /usr/lib/python2.7/dist-packages/instances, which is clearly incorrect. How did you install your Nova code? Best, -jay On 04/27/2012 12:00 PM, Leander Bessa wrote: Hello, I'm clueless as how to solve this problem, any ideas? DEBUG nova.utils [req-007e9c3f-2dcb-4b42-8486-800a51e272e1 None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=17035) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 336, in fire_timers timer() File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main result = function(*args, **kwargs) File /usr/lib/python2.7/dist-packages/nova/service.py, line 101, in run_server server.start() File /usr/lib/python2.7/dist-packages/nova/service.py, line 174, in start self.manager.update_available_resource(ctxt) File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2403, in update_available_resource self.driver.update_available_resource(context, self.host) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1898, in update_available_resource 'local_gb': self.get_local_gb_total(), File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1712, in get_local_gb_total stats = libvirt_utils.get_fs_info(FLAGS.instances_path) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/utils.py, line 277, in get_fs_info hddinfo = os.statvfs(path) OSError: [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 CRITICAL nova [-] [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 TRACE nova Traceback (most recent call last): 2012-04-27 16:51:48 TRACE nova File /usr/bin/nova-compute, line 49, in module 2012-04-27 16:51:48 TRACE nova service.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 413, in wait 2012-04-27 16:51:48 TRACE nova _launcher.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 131, in wait 2012-04-27 16:51:48 TRACE nova service.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait 2012-04-27 16:51:48 TRACE nova return self._exit_event.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait 2012-04-27 16:51:48 TRACE nova return hubs.get_hub().switch() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch 2012-04-27 16:51:48 TRACE nova return self.greenlet.switch() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main 2012-04-27 16:51:48 TRACE nova result = function(*args, **kwargs) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 101, in run_server 2012-04-27 16:51:48 TRACE nova server.start() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 174, in start 2012-04-27 16:51:48 TRACE nova self.manager.update_available_resource(ctxt) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2403, in update_available_resource 2012-04-27 16:51:48 TRACE nova self.driver.update_available_resource(context, self.host) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1898, in update_available_resource 2012-04-27 16:51:48 TRACE nova 'local_gb': self.get_local_gb_total(), 2012-04-27 16:51:48 TRACE nova File
Re: [Openstack] Code contribution
If you are asking how it becomes approved the answer is that two core-contributors of the specific project need to manually review the code, and +2 it. When that is done, Jenkins, a CI tool, will run the various automated acceptability tests against the code and if they all pass, it will merge it in to the project. John Postlethwait Nebula, Inc. 206-999-4492 On Friday, April 27, 2012 at 9:08 AM, Victor Rodionov wrote: Hello How code in gerrit becomes verified? ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net (mailto: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] Checking InnoDB table creation as part of unit tests for nova
I've got a patch out for review that opportunistically tests the nova migrations on mysql, if a very specific mysql database name/password/db exists on the test system (fails gracefully if it doesn't). It then also checks to make sure that there are no non-InnoDB tables in the resultant migration (also failing gracefully if there isn't). We did a couple of draft reviews with the CI team to make sure this was something they could support as a gating test. This would prevent new migrations that don't specify engine from sneaking in. I'd like feedback from Nova devs on the approach - https://review.openstack.org/#/c/6805/ comments, flames, etc are welcome. Thanks, -Sean -- Sean Dague IBM Linux Technology Center email: slda...@us.ibm.com alt-email: sda...@linux.vnet.ibm.com ___ 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] 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 Launchpad Web UI for Gettext strings translation, any people can jump in at any time and contribute to any part of the translatable contents. In order to facilitate the manuals translation, I investigated several translation websites and several open source projects. I composed this proposal. Now it's open for suggestions and comments. *Goal* ** A process for manuals translation *Background* *--* OpenStack Manuals are in DocBook format. The source is on GitHub: http://github.com/openstack/openstack-manuals Launchpad and Transifex are free web based tools used for crowd translation. Both of them provide a simple web interface in which non-technical people can help translation. They don't support DocBook format, but support the popular GNU Gettext file formats (PO Template or PO). *Translation Process* *---* In order to translate OpenStack Manuals to multiple languages, which are in DocBook format, we can slice the documents into short statements, then use a web based translation management tool to manage the translation process, and finally converge the translated content into a new copy of DocBook. Here are the five steps of the translation process: Step #1 Slicing - extract translatable content from DocBooks and generate Gettext compatible POT files (PO Template or PO); Step #2 Uploading - upload the POT (or PO) files to a web based translation management tool; Step #3 Downloading - download PO (or MO) files from the web tool after translation and review; Step #4 Converging - converge the translated contents into new copies of DocBook, create DocBooks in multiple languages Step #5 Generating - generate HTML/PDF in multiple languages from DocBooks in multiple languages The picture in the attachment describes these steps. *(See attached file: DocBook translation process.png)* *Compare of Launchpad and Transifex* *---* Launchpad (https://launchpad.net/) and Transifex ( https://www.transifex.net/) are similar web based tools used for crowd translation. The goal of the compare is to find the most appropriate tool for this scenario. The compare are made between Launchpad and Transifex free version for open sources. (Refer to https://www.transifex.net/plans/ to get details of “Transifex free version for open sources”) After considering the requirements for manuals translation, below perspectives are taking into consideration: *Supported format *DocBook slicing support *Converging
Re: [Openstack] [nova-compute] Startup error
Could you paste your nova.conf? Looks like your instances_path flag is pointing to python's dist packages directory, maybe you've set it with a relative path...? Have you already checked it? []'s On Fri, Apr 27, 2012 at 1:00 PM, Leander Bessa leande...@gmail.com wrote: Hello, I'm clueless as how to solve this problem, any ideas? DEBUG nova.utils [req-007e9c3f-2dcb-4b42-8486-800a51e272e1 None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=17035) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 336, in fire_timers timer() File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main result = function(*args, **kwargs) File /usr/lib/python2.7/dist-packages/nova/service.py, line 101, in run_server server.start() File /usr/lib/python2.7/dist-packages/nova/service.py, line 174, in start self.manager.update_available_resource(ctxt) File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2403, in update_available_resource self.driver.update_available_resource(context, self.host) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1898, in update_available_resource 'local_gb': self.get_local_gb_total(), File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1712, in get_local_gb_total stats = libvirt_utils.get_fs_info(FLAGS.instances_path) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/utils.py, line 277, in get_fs_info hddinfo = os.statvfs(path) OSError: [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 CRITICAL nova [-] [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 TRACE nova Traceback (most recent call last): 2012-04-27 16:51:48 TRACE nova File /usr/bin/nova-compute, line 49, in module 2012-04-27 16:51:48 TRACE nova service.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 413, in wait 2012-04-27 16:51:48 TRACE nova _launcher.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 131, in wait 2012-04-27 16:51:48 TRACE nova service.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait 2012-04-27 16:51:48 TRACE nova return self._exit_event.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait 2012-04-27 16:51:48 TRACE nova return hubs.get_hub().switch() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch 2012-04-27 16:51:48 TRACE nova return self.greenlet.switch() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main 2012-04-27 16:51:48 TRACE nova result = function(*args, **kwargs) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 101, in run_server 2012-04-27 16:51:48 TRACE nova server.start() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 174, in start 2012-04-27 16:51:48 TRACE nova self.manager.update_available_resource(ctxt) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2403, in update_available_resource 2012-04-27 16:51:48 TRACE nova self.driver.update_available_resource(context, self.host) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1898, in update_available_resource 2012-04-27 16:51:48 TRACE nova 'local_gb': self.get_local_gb_total(), 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1712, in get_local_gb_total 2012-04-27 16:51:48 TRACE nova stats = libvirt_utils.get_fs_info(FLAGS.instances_path) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/utils.py, line 277, in get_fs_info 2012-04-27 16:51:48 TRACE nova hddinfo = os.statvfs(path) 2012-04-27 16:51:48 TRACE nova OSError: [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 TRACE nova Exception KeyError: KeyError(140477118368240,) in module 'threading' from '/usr/lib/python2.7/threading.pyc' ignored Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to :
Re: [Openstack] [Metering] First meeting for the Metering project
On 12-04-27 01:24 PM, Loic Dachary wrote: On 04/27/2012 05:37 PM, Francis J. Lacoste wrote: On 12-04-27 10:50 AM, Nick Barcet wrote: The meeting occurred as planned, and overran... Nevertheless a lot of good decisions were made, the obviously most important one grin being the project name: ceilometer. For a more complete meeting summary, go visit: http://wiki.openstack.org/Meetings/MeteringAgenda/meeting-0-summary Next week we will have for objective to find an agreement on schema and counter definitions. If anyone does not do it before me I'll fire an introduction email on the subject soon (sometime this we), as we agreed to start the discussion via mailing list and use the irc meeting to finalize the choices. The Launchpad project was created: https://launchpad.net/ceilometer Thank you :-) I'm not familiar with the launchpad ways. Should I wait for the git repository to be created ? Or can I help with that ? Yes, please. I'm not familiar with the github ways :-) So please go ahead, and create the required github repository. Cheers -- Francis J. Lacoste francis.laco...@canonical.com signature.asc Description: OpenPGP digital 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] Mailing-list split
I like this idea but what happens to the openstack-operators list in this scenario? I don't think we'd want to have the openstack and openstack-operators list going along in parallel since it sounds like they would overlap. I propose that the members of the openstack-operators list would be (automatically or manually) migrated to the openstack list. Then the openstack-operators list would be set to read-only or maybe even removed completely to avoid confusion. Comments? Feedback? Everett On Fri, Apr 27, 2012 at 4:04 AM, Thierry Carrez thie...@openstack.orgwrote: Hello everyone, TL;DR summary: Due to traffic exploding, we will split the current openstack list into user / usage topics (openstack list) and development / next-version topics (openstack-dev list). Long version: At the Communication session at the design summit [1] we looked at the state of our communication media in general, and mailing-list in particular [2]. [1] http://folsomdesignsummit2012.sched.org/event/366accca0fda271fc23e82b9cb5162cc [2] http://etherpad.openstack.org/FolsomCommunication The traffic on the openstack@lists.launchpad.net list doubled in the last 4 months [3], with more users and deployers asking for information on OpenStack projects. It becomes difficult for contributors to properly prioritize their ML reading, and we can no longer have all the discussions in the same place. [3] http://openstack.markmail.org/ The proposal is to split between: 1/ Usage, deployment, Essex / current-stable discussions 2/ Development, contribution, Folsom / forward-looking discussions A new list will be created for (2) and existing contributors will be asked to subscribe to that new list. Since we expect to have a more disciplined/focused group in that new list, we'll define a set of subject prefixes that should be used for easier client-side/at-a-glance filtering of discussions: [General] Affects all projects [Swift] [Nova] [Glance] [Quantum] [Horizon] [Keystone] Project-specific [Common] openstack-common [QA] [CI] [Docs] Discussions / Information on specific topics [...] Add your own here To keep that list usable, I suggest we aggressively enforce those topics and redirect inappropriate discussions to the other list when necessary. 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. There was a suggestion during the session of using umbrella/siblings lists to aggregate content from multiple project-specific sublists. I reviewed the options and I think it introduces a lot of complexity, reduces flexibility in adding new topics, so client-side filtering sounds like a better bet. If most people use subject prefixes appropriately, keeping it simple is probably the best bet. We'll let you know when the new list is set up. Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] database migration cleanup
On Fri, Apr 27, 2012, Monsyne Dragon mdra...@rackspace.com wrote: Even better, what would it take to try using Alembic? (http://alembic.readthedocs.org/en/latest/front.html#project-homepage) It's a big improvement over sqlalchemy. Amongst other things, migrations are not numbered, they are linked by dependancy, and run in topological-sort order. That there eliminates alot of my migration number got taken... again... problems. I've mentioned in on the list before, but here's a partial switch over to alembic: https://github.com/jerdfelt/nova/tree/alembic However, it's orthogonal to merging migrations. It wouldn't be any better or worse in that regard. JE ___ 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.
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.comwrote: is enabled and not running my compute node is virtual machine to test and configured with qemu (2 core, 4gb, 10gb free in nova-volumes) my last log message on nova-compute is: 2012-04-27 12:22:25 DEBUG nova.virt.libvirt.connection [-] Connecting to libvirt: qemu:///system from (pid=18588) _get_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.*py*:292 libvirt is running 18420 ?Sl 0:00 /usr/sbin/libvirtd -d On Thu, Apr 26, 2012 at 10:43 PM, heut2008 heut2...@gmail.com wrote: be sure nova-compute is running and is enabled by using nova-manage service list,also confirm that the compute node have enough resources(cpu,mem,disk) . 2012/4/27 Rogerio Goncalves roge...@gmail.com: Hello, Im getting this error when launching a new instance. Failed to schedule_run_instance: No valid host was found. Is the appropriate service running? http://paste.openstack.org/show/14020/ SO Ubuntu 12.04 libvirt-bin start/running, process 4153 nova-network start/running, process 4174 nova-compute start/running, process 4187 nova-api start/running, process 4198 nova-objectstore start/running, process 4210 nova-scheduler start/running, process 4222 nova-volume start/running, process 4235 nova-vncproxy start/running, process 4246 rabbitmq is up too Thanks Rogério Gonçalves ___ 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 -- Flávia Missi @flaviamissi http://twitter.com/flaviamissi flaviamissi.com.br https://github.com/flaviamissi ___ 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-compute] Startup error
In nova.conf, what is instances_path being set to? It's blowing up trying to find the path '/usr/lib/python2.7/dist-packages/instances', which is getting set as the value of FLAGS.instances_path. On Fri, Apr 27, 2012 at 12:00 PM, Leander Bessa leande...@gmail.com wrote: Hello, I'm clueless as how to solve this problem, any ideas? DEBUG nova.utils [req-007e9c3f-2dcb-4b42-8486-800a51e272e1 None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=17035) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 336, in fire_timers timer() File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main result = function(*args, **kwargs) File /usr/lib/python2.7/dist-packages/nova/service.py, line 101, in run_server server.start() File /usr/lib/python2.7/dist-packages/nova/service.py, line 174, in start self.manager.update_available_resource(ctxt) File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2403, in update_available_resource self.driver.update_available_resource(context, self.host) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1898, in update_available_resource 'local_gb': self.get_local_gb_total(), File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1712, in get_local_gb_total stats = libvirt_utils.get_fs_info(FLAGS.instances_path) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/utils.py, line 277, in get_fs_info hddinfo = os.statvfs(path) OSError: [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 CRITICAL nova [-] [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 TRACE nova Traceback (most recent call last): 2012-04-27 16:51:48 TRACE nova File /usr/bin/nova-compute, line 49, in module 2012-04-27 16:51:48 TRACE nova service.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 413, in wait 2012-04-27 16:51:48 TRACE nova _launcher.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 131, in wait 2012-04-27 16:51:48 TRACE nova service.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait 2012-04-27 16:51:48 TRACE nova return self._exit_event.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait 2012-04-27 16:51:48 TRACE nova return hubs.get_hub().switch() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch 2012-04-27 16:51:48 TRACE nova return self.greenlet.switch() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main 2012-04-27 16:51:48 TRACE nova result = function(*args, **kwargs) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 101, in run_server 2012-04-27 16:51:48 TRACE nova server.start() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 174, in start 2012-04-27 16:51:48 TRACE nova self.manager.update_available_resource(ctxt) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2403, in update_available_resource 2012-04-27 16:51:48 TRACE nova self.driver.update_available_resource(context, self.host) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1898, in update_available_resource 2012-04-27 16:51:48 TRACE nova 'local_gb': self.get_local_gb_total(), 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1712, in get_local_gb_total 2012-04-27 16:51:48 TRACE nova stats = libvirt_utils.get_fs_info(FLAGS.instances_path) 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/utils.py, line 277, in get_fs_info 2012-04-27 16:51:48 TRACE nova hddinfo = os.statvfs(path) 2012-04-27 16:51:48 TRACE nova OSError: [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/instances' 2012-04-27 16:51:48 TRACE nova Exception KeyError: KeyError(140477118368240,) in module 'threading' from '/usr/lib/python2.7/threading.pyc' ignored Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to :
[Openstack] [QA] Summary of QA Weekly Status meeting
The QA team had its weekly IRC meeting yesterday. Here is a summary of the action items and decisions coming out of the meeting. * Progress - Currently up to more than 150 integration tests - The dev-gate-tempest-devstack-vm Jenkins job [1] has run smoothly now for a number of iterations. There are still some issues with the job: - The job takes more than 40 minutes to complete on *some* cloud providers. Most of this time is taken by devstack installing the OpenStack environment via devstack into the utility VMs - Jim Blair upped the timeout to 60 minutes to help this problem - 2 test failures are consistently reproduceable - Working to fix both by end of week - Jim Blair added a nice report output [3] to the Jenkins job utilizing the nosetests xUnit output plugin (thank you Jim!) * Action items - (jaypipes) Get dev-gate-tempest-devstack-vm Jenkins job [1] gating Tempest by end of week * Decisions made - Going to start a rotating QA captain role [2] that is responsible for communicating an agenda for the weekly status meeting and a summary like this one for the meeting * Blockers identified - Inclusion of python-glanceclient package in devstack has caused issues in the gating job. jaypipes working on fix for it with bcwaldon and dtroyer. * Outstanding Reviews Community, please feel free to provide code reviews on outstanding Tempest merge proposals: https://review.openstack.org/#/q/status:open+project:openstack/tempest,n,z Thanks! -jay [1] https://jenkins.openstack.org/job/dev-gate-tempest-devstack-vm/ [2] http://wiki.openstack.org/QACaptainRotation [3] https://jenkins.openstack.org/job/dev-gate-tempest-devstack-vm/344/testReport/ ___ 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] Unable to download images using Glance+Keystone+Swift
DOH! (boy I say this a lot…) As usual, a stupid configuration error. In my old Diablo setup, the administrative role was specified via the keyword Admin. I imported the existing user accounts, tenants, and roles into my Essex test setup. However I neglected to set the Glance 'admin_role' configuration flag, so it defaulted to the keyword admin. Once I fixed this, image downloads are working fine and instances boot with no problem. Congrats to everyone that pulled Essex together. Overall stability and functionality is much improved. We'll be migrating our Diablo cloud to Essex over the next week. Ross On Apr 26, 2012, at 7:32 PM, Sam Morrison wrote: Hi Ross, I had the same issue. Could upload images to swift but not download them getting a 404. I needed to apply the patch outlined in this bug to fix it: https://bugs.launchpad.net/glance/+bug/979745 Cheers, Sam On Fri, Apr 27, 2012 at 9:53 AM, Lillie Ross-CDSR11 ross.lil...@motorolasolutions.com wrote: Jay, These are the Ubuntu 12.04 packages from the beta with all known updates. I'm configuring another set of instances with the Ubuntu Precise final packages just to make sure I didn't miss a patch. However, this error seems fundamental to me. I don't see how a glance POST can work but the corresponding GET fails. All calls that just hit the backend DB work fine. Also I can access the bucket and objects directly via swift w no problem. I'll post my results with the final Ubuntu release sometime tomorrow hopefully. (finger tapped on my iPhone) On Apr 26, 2012, at 1:40 PM, Jay Pipes jaypi...@gmail.com wrote: On 04/26/2012 02:37 PM, Lillie Ross-CDSR11 wrote: Hi Jay, Cut and paste error. It still doesn't work. If I issue the simple command (without the pipe or content-type header) I get the following root@essex1:/etc/keystone# curl -v -H 'X-Auth-Token: 45d01460a0e04bff967eb954e7f4fee8' http://essex3:9292/v1/images/423b0ecc-5ca1-44d8-8e85-5a245ce620e2 * About to connect() to essex3 port 9292 (#0) * Trying 172.16.1.5... connected GET /v1/images/423b0ecc-5ca1-44d8-8e85-5a245ce620e2 HTTP/1.1 User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3 Host: essex3:9292 Accept: */* X-Auth-Token: 45d01460a0e04bff967eb954e7f4fee8 HTTP/1.1 404 Not Found Content-Length: 315 Content-Type: text/html; charset=UTF-8 Date: Thu, 26 Apr 2012 18:35:21 GMT html head title404 Not Found/title /head body h1404 Not Found/h1 An object with the specified identifier was not found. Details: Swift could not find image at uri swift+http://service:glance:glance@essex1:5000/v2.0/glance/423b0ecc-5ca1-44d8-8e85-5a245ce620e2br /br / /body * Connection #0 to host essex3 left intact * Closing connection #0 /html root@essex1:/etc/keystone# Now, I can access the image directly via the Swift CLI using my glance tenant, username, and password. However, the Glance REST call fails. All other REST calls work fine. I'm stumped. Ross, what version of Glance and Swift are you using? Best, -jay ___ 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] Code contribution
the full setup is described here: http://wiki.openstack.org/GerritJenkinsGithub On Fri, Apr 27, 2012 at 2:42 PM, John Postlethwait john.postlethw...@nebula.com wrote: If you are asking how it becomes approved the answer is that two core-contributors of the specific project need to manually review the code, and +2 it. When that is done, Jenkins, a CI tool, will run the various automated acceptability tests against the code and if they all pass, it will merge it in to the project. John Postlethwait Nebula, Inc. 206-999-4492 On Friday, April 27, 2012 at 9:08 AM, Victor Rodionov wrote: Hello How code in gerrit becomes verified? ___ 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 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 enabledXXX 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.comwrote: is enabled and not running my compute node is virtual machine to test and configured with qemu (2 core, 4gb, 10gb free in nova-volumes) my last log message on nova-compute is: 2012-04-27 12:22:25 DEBUG nova.virt.libvirt.connection [-] Connecting to libvirt: qemu:///system from (pid=18588) _get_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.*py*:292 libvirt is running 18420 ?Sl 0:00 /usr/sbin/libvirtd -d On Thu, Apr 26, 2012 at 10:43 PM, heut2008 heut2...@gmail.com wrote: be sure nova-compute is running and is enabled by using nova-manage service list,also confirm that the compute node have enough resources(cpu,mem,disk) . 2012/4/27 Rogerio Goncalves roge...@gmail.com: Hello, Im getting this error when launching a new instance. Failed to schedule_run_instance: No valid host was found. Is the appropriate service running? http://paste.openstack.org/show/14020/ SO Ubuntu 12.04 libvirt-bin start/running, process 4153 nova-network start/running, process 4174 nova-compute start/running, process 4187 nova-api start/running, process 4198 nova-objectstore start/running, process 4210 nova-scheduler start/running, process 4222 nova-volume start/running, process 4235 nova-vncproxy start/running, process 4246 rabbitmq is up too Thanks Rogério Gonçalves ___ 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 -- Flávia Missi @flaviamissi http://twitter.com/flaviamissi flaviamissi.com.br https://github.com/flaviamissi ___ 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] Unable to download images using Glance+Keystone+Swift
Good to hear, Ross! Thanks for sharing the fix :) -jay On 04/27/2012 04:42 PM, Lillie Ross-CDSR11 wrote: DOH! (boy I say this a lot…) As usual, a stupid configuration error. In my old Diablo setup, the administrative role was specified via the keyword Admin. I imported the existing user accounts, tenants, and roles into my Essex test setup. However I neglected to set the Glance 'admin_role' configuration flag, so it defaulted to the keyword admin. Once I fixed this, image downloads are working fine and instances boot with no problem. Congrats to everyone that pulled Essex together. Overall stability and functionality is much improved. We'll be migrating our Diablo cloud to Essex over the next week. Ross On Apr 26, 2012, at 7:32 PM, Sam Morrison wrote: Hi Ross, I had the same issue. Could upload images to swift but not download them getting a 404. I needed to apply the patch outlined in this bug to fix it: https://bugs.launchpad.net/glance/+bug/979745 Cheers, Sam On Fri, Apr 27, 2012 at 9:53 AM, Lillie Ross-CDSR11 ross.lil...@motorolasolutions.com wrote: Jay, These are the Ubuntu 12.04 packages from the beta with all known updates. I'm configuring another set of instances with the Ubuntu Precise final packages just to make sure I didn't miss a patch. However, this error seems fundamental to me. I don't see how a glance POST can work but the corresponding GET fails. All calls that just hit the backend DB work fine. Also I can access the bucket and objects directly via swift w no problem. I'll post my results with the final Ubuntu release sometime tomorrow hopefully. (finger tapped on my iPhone) On Apr 26, 2012, at 1:40 PM, Jay Pipesjaypi...@gmail.com wrote: On 04/26/2012 02:37 PM, Lillie Ross-CDSR11 wrote: Hi Jay, Cut and paste error. It still doesn't work. If I issue the simple command (without the pipe or content-type header) I get the following root@essex1:/etc/keystone# curl -v -H 'X-Auth-Token: 45d01460a0e04bff967eb954e7f4fee8' http://essex3:9292/v1/images/423b0ecc-5ca1-44d8-8e85-5a245ce620e2 * About to connect() to essex3 port 9292 (#0) * Trying 172.16.1.5... connected GET /v1/images/423b0ecc-5ca1-44d8-8e85-5a245ce620e2 HTTP/1.1 User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3 Host: essex3:9292 Accept: */* X-Auth-Token: 45d01460a0e04bff967eb954e7f4fee8 HTTP/1.1 404 Not Found Content-Length: 315 Content-Type: text/html; charset=UTF-8 Date: Thu, 26 Apr 2012 18:35:21 GMT html head title404 Not Found/title /head body h1404 Not Found/h1 An object with the specified identifier was not found. Details: Swift could not find image at uri swift+http://service:glance:glance@essex1:5000/v2.0/glance/423b0ecc-5ca1-44d8-8e85-5a245ce620e2br /br / /body * Connection #0 to host essex3 left intact * Closing connection #0 /html root@essex1:/etc/keystone# Now, I can access the image directly via the Swift CLI using my glance tenant, username, and password. However, the Glance REST call fails. All other REST calls work fine. I'm stumped. Ross, what version of Glance and Swift are you using? Best, -jay ___ 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] Mailing-list split
Makes sense to me. On Apr 27, 2012 2:27 PM, Everett Toews everett.to...@cybera.ca wrote: I like this idea but what happens to the openstack-operators list in this scenario? I don't think we'd want to have the openstack and openstack-operators list going along in parallel since it sounds like they would overlap. I propose that the members of the openstack-operators list would be (automatically or manually) migrated to the openstack list. Then the openstack-operators list would be set to read-only or maybe even removed completely to avoid confusion. Comments? Feedback? Everett On Fri, Apr 27, 2012 at 4:04 AM, Thierry Carrez thie...@openstack.orgwrote: Hello everyone, TL;DR summary: Due to traffic exploding, we will split the current openstack list into user / usage topics (openstack list) and development / next-version topics (openstack-dev list). Long version: At the Communication session at the design summit [1] we looked at the state of our communication media in general, and mailing-list in particular [2]. [1] http://folsomdesignsummit2012.sched.org/event/366accca0fda271fc23e82b9cb5162cc [2] http://etherpad.openstack.org/FolsomCommunication The traffic on the openstack@lists.launchpad.net list doubled in the last 4 months [3], with more users and deployers asking for information on OpenStack projects. It becomes difficult for contributors to properly prioritize their ML reading, and we can no longer have all the discussions in the same place. [3] http://openstack.markmail.org/ The proposal is to split between: 1/ Usage, deployment, Essex / current-stable discussions 2/ Development, contribution, Folsom / forward-looking discussions A new list will be created for (2) and existing contributors will be asked to subscribe to that new list. Since we expect to have a more disciplined/focused group in that new list, we'll define a set of subject prefixes that should be used for easier client-side/at-a-glance filtering of discussions: [General] Affects all projects [Swift] [Nova] [Glance] [Quantum] [Horizon] [Keystone] Project-specific [Common] openstack-common [QA] [CI] [Docs] Discussions / Information on specific topics [...] Add your own here To keep that list usable, I suggest we aggressively enforce those topics and redirect inappropriate discussions to the other list when necessary. 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. There was a suggestion during the session of using umbrella/siblings lists to aggregate content from multiple project-specific sublists. I reviewed the options and I think it introduces a lot of complexity, reduces flexibility in adding new topics, so client-side filtering sounds like a better bet. If most people use subject prefixes appropriately, keeping it simple is probably the best bet. We'll let you know when the new list is set up. Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] nova nofitications
Juan/Stackers, I am curious after this blueprint was created if there is any development on the volume piece of the notifications? If there has been some work done towards this, i would be very interested on working together to get this in ASAP. If not, I will take on part of this blueprint and contribute it. Thanks, Craig Vyvial ___ 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
On Fri, Apr 27, 2012 at 3:52 PM, Everett Toews everett.to...@cybera.ca wrote: I like this idea but what happens to the openstack-operators list in this scenario? I don't think we'd want to have the openstack and openstack-operators list going along in parallel since it sounds like they would overlap. I propose that the members of the openstack-operators list would be (automatically or manually) migrated to the openstack list. Then the openstack-operators list would be set to read-only or maybe even removed completely to avoid confusion. Comments? Feedback? Hrm. One of the things that came out of the Design Summit discussions around DevOps was that the OpenStack DevOps sub-community doesn't really feel like it has a voice. As a result, I'd be loathe to remove that venue for discussion right now, even if it's only of symbolic value. That being said, I propose that something along the following lines could happen: * intense dev work, collaboration, etc., happening on openstack-dev@ * general usage of openstack questions by folks who are not code contributors, but standing up OpenStack itself, happening on openstack@ * conversations around DevOps in particular (the wide spectrum of definitions that comprise DevOps in various people's minds) happening in openstack-operators@ In helping jump-start (or re-jump-start) the OpenStack DevOps community, I'd really like to have a dedicated place for announcements, questions, etc. Even if we spent some time pointing folks to more detailed, technical resources. In hallway conversations at the summit (and in various emails and phone calls since then), people who consider themselves DevOps have expressed concern over the possibility that the operators list would go away. They are overwhelmed by the volume of traffic on the openstack list, and don't have the time to devise a solution for creating appropriate filters, etc. That objection may simply go away with the new mail list split. But if openstack-operators has become a property valuable to community members, we shouldn't just get rid of it because it doesn't make logical sense. We should make sure that folks are ready to transition to another location for their DevOps needs. And that might take a cycle to sort out... d ___ 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] [Metering] Metering repository in stackforge
Hi, I would like to create a repository ceilometer in https://github.com/stackforge to host the code for the newborn Metering project ( https://launchpad.net/ceilometer , first meeting held this thursday http://wiki.openstack.org/Meetings/MeteringAgenda ). I'm not sure how to proceed, could you please guide me ? My github account name is dachary Thanks in advance -- Loïc Dachary Chief Research Officer // eNovance labs http://labs.enovance.com // ✉ l...@enovance.com ☎ +33 1 49 70 99 82 ___ 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.
how much free ram left on your compute node?-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -To: Flavia Missi flaviami...@gmail.comFrom: Rogerio Goncalves roge...@gmail.comSent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.netDate: 04/28/2012 04:43AMCc: openstack@lists.launchpad.netSubject: 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 listBinary Host Zone Status State Updated_Atnova-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=AllHostsFilterHope it helps.[]'sOn Fri, Apr 27, 2012 at 12:29 PM, Rogerio Goncalves roge...@gmail.com wrote: is enabled and not runningmy compute node is virtual machine to test and configured with qemu (2 core, 4gb, 10gb free in nova-volumes)my last log message on nova-compute is:2012-04-27 12:22:25 DEBUG nova.virt.libvirt.connection [-] Connecting to libvirt: qemu:///system from (pid=18588) _get_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py:292 libvirt is running18420 ?Sl 0:00 /usr/sbin/libvirtd -d On Thu, Apr 26, 2012 at 10:43 PM, heut2008 heut2...@gmail.com wrote: be sure nova-compute is running and is enabled by using nova-manage service list,also confirm that the compute node have enough resources(cpu,mem,disk) . 2012/4/27 Rogerio Goncalves roge...@gmail.com: Hello, Im getting this error when launching a new instance. "Failed to schedule_run_instance: No valid host was found. Is the appropriate service running?" http://paste.openstack.org/show/14020/ SO Ubuntu 12.04 libvirt-bin start/running, process 4153 nova-network start/running, process 4174 nova-compute start/running, process 4187 nova-api start/running, process 4198 nova-objectstore start/running, process 4210 nova-scheduler start/running, process 4222 nova-volume start/running, process 4235 nova-vncproxy start/running, process 4246 rabbitmq is up too Thanks Rogério Gonçalves ___ 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-- Flávia Missi@flaviamissiflaviamissi.com.br https://github.com/flaviamissi ___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore 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
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?). 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? 2) The OVS quantum plugin seems to implement the core API functions and (viewing the code) I concluded that it just makes maintains the logical mappings e.g. b/w net IDs and VLAN IDs in a database. So how is this mapping implemented on the actual ports of OVS? Is it the OVS quantum agent responsible for directing the packets to correct input/output ports based on the updates that it gets from the database? In VLAN-mode, its even simpler than that. The agent simply puts each port as a VLAN access port for the right VLAN, based on the database, and then has OVS perform standard L2 learning to forward packets. good to know. 3) The quantum admin guide says that the nova client will be the main user of quantum and will interact with it via REST API, so it would be nice if someone can point me to the code (file path name etc.) where this happens. This is the QuantumManager code in Nova: https://github.com/openstack/nova/tree/master/nova/network/quantum One word of warning: this code will be being simplified and largely removed in Folsom, so while its useful to look at it to learn about Quantum, I'd ask around before investing the time to make significant changes to the code. PS: What is the purpose of Quantum Manager in this architecture and where should I look for its code? 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 above :) Thanks again for clarification. Since, I am still trying to understand the data flow, please pardon me for questions that are confusing. 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 ~~~ ___ 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
Hi Hitesh, Thanks for the considerate reply. Please see the inline comments. On Fri, Apr 27, 2012 at 1:25 AM, Salman Malik salma...@live.com wrote: Hi All, 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? [Hitesh]: As far as I know that OVS have more features over the Linux bridge, for example, VM isolation, mobility and security. These can be configured by remote controller. To help and gian the control on all these activities the integration bridge is required. I am not sure about it but I Dan or Salvotore can explain this better way. You can find the more information here http://openvswitch.org/support/ Now, what I have understood from Dan's reply is that OVS itself consists of these bridges (each bridge on a node, being called as an integration bridge). Correct me if I am wrong. 2) The OVS quantum plugin seems to implement the core API functions and (viewing the code) I concluded that it just makes maintains the logical mappings e.g. b/w net IDs and VLAN IDs in a database. So how is this mapping implemented on the actual ports of OVS? Is it the OVS quantum agent responsible for directing the packets to correct input/output ports based on the updates that it gets from the database? [Hitesh]: OVS agent is responsible for to update the database(accoding to actions have been told) for the local server as well Quantum server. As far as I know OVS quantum is not responsible for directing the packets to correct in/op, This job is hadled by OVS core module on the server (datapath). OVS agent only updates the database and creation bridge etc.. Dan or Salvotore can be explained more... Are you sure that quantum agent updates the database? I used to think that it only grabs updates by looking into the database (which is actually modified by the plugin). I am not sure so just confirming. 3) The quantum admin guide says that the nova client will be the main user of quantum and will interact with it via REST API, so it would be nice if someone can point me to the code (file path name etc.) where this happens. [Hitesh]: You can see the devstack script where we are configuring nove-network to quantum. thats the enry point for the nova-network to communicate to quantum. I will share soon more on this. Thanks Hitesh for sharing you knowledge :) Can you comment on how nova-network interacts with Quantum-manager? However, I tried my best to give to these answers. Please feel free to correct me if anything needs to share more. Salman, Let me know if you want more info about this. I will be happy to share Thanks again Hitesh. I appreciate your help. 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 ___ 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-compute] Startup error
I installed everything from ubuntu's 12.04 repositories. Below is the nova config file template i'm using. I don't have access to the machine i'm using at the moment, so i can't get the final output. I hope it's enough :/ [DEFAULT] # LOG/State verbose=True # Authentication auth_strategy=keystone # Scheduler compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler # VOLUMES volume_group=nova-volumes volume_name_template=volume-%08x iscsi_helper=tgtadm iscsi_ip_prefix=%HOST_IP% # COMPUTE libvirt_type=%LIBVIRT_TYPE% connection_type=libvirt instance_name_template=instance-%08x api_paste_config=/etc/nova/api-paste.ini allow_resize_to_same_host=True root_helper=sudo nova-rootwrap libvirt_use_virtio_for_bridges=True api_paste_config=api-paste-keystone.ini allow_admin_api=true # DATABASE sql_connection=mysql://nova:%MYSQL_NOVA_PASS%@%MYSQL_HOST%/nova # APIS osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions osapi_host=%HOST_IP% # Glance glance_api_servers=%HOST_IP%:9292 # RABBITMQ rabbit_host=%HOST_IP% # NETWORK firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver dhcpbridge_flagfile=/etc/nova/nova.conf dhcpbridge=/usr/bin/nova-dhcpbridge force_dhcp_release=True public_interface=%PUBLIC_INTERFACE% vlan_interface=%VLAN_INTERFACE% vlan_start=%VLAN_START% zone_name=%REGION% node_availability_zone=%REGION% storage_availability_zone=%REGION% enable_zone_routing=true # NOVNC CONSOLE novncproxy_base_url=http://%HOST_IP%:6080/vnc_auto.html vncserver_proxyclient_address=%HOST_IP% vncserver_listen=%HOST_IP% On Fri, Apr 27, 2012 at 7:40 PM, Jay Pipes jaypi...@gmail.com wrote: Hi Leander, Looks like a misconfiguration. The base path for nova's instances is typically /var/lib/nova/instances, set by the instances_path configuration option. Somehow it is being set to /usr/lib/python2.7/dist-**packages/instances, which is clearly incorrect. How did you install your Nova code? Best, -jay On 04/27/2012 12:00 PM, Leander Bessa wrote: Hello, I'm clueless as how to solve this problem, any ideas? DEBUG nova.utils [req-007e9c3f-2dcb-4b42-8486-**800a51e272e1 None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-**packages/nova/db/sqlalchemy/**api.pyc' from (pid=17035) __get_backend /usr/lib/python2.7/dist-**packages/nova/utils.py:658 Traceback (most recent call last): File /usr/lib/python2.7/dist-**packages/eventlet/hubs/hub.py* *, line 336, in fire_timers timer() File /usr/lib/python2.7/dist-**packages/eventlet/hubs/timer.**py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-**packages/eventlet/greenthread.**py, line 192, in main result = function(*args, **kwargs) File /usr/lib/python2.7/dist-**packages/nova/service.py, line 101, in run_server server.start() File /usr/lib/python2.7/dist-**packages/nova/service.py, line 174, in start self.manager.update_available_**resource(ctxt) File /usr/lib/python2.7/dist-**packages/nova/compute/manager.**py, line 2403, in update_available_resource self.driver.update_available_**resource(context, self.host) File /usr/lib/python2.7/dist-**packages/nova/virt/libvirt/** connection.py, line 1898, in update_available_resource 'local_gb': self.get_local_gb_total(), File /usr/lib/python2.7/dist-**packages/nova/virt/libvirt/** connection.py, line 1712, in get_local_gb_total stats = libvirt_utils.get_fs_info(**FLAGS.instances_path) File /usr/lib/python2.7/dist-**packages/nova/virt/libvirt/**utils.py, line 277, in get_fs_info hddinfo = os.statvfs(path) OSError: [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-**packages/instances' 2012-04-27 16:51:48 CRITICAL nova [-] [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-**packages/instances' 2012-04-27 16:51:48 TRACE nova Traceback (most recent call last): 2012-04-27 16:51:48 TRACE nova File /usr/bin/nova-compute, line 49, in module 2012-04-27 16:51:48 TRACE nova service.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-**packages/nova/service.py, line 413, in wait 2012-04-27 16:51:48 TRACE nova _launcher.wait() 2012-04-27 16:51:48 TRACE nova File /usr/lib/python2.7/dist-**packages/nova/service.py, line 131, in wait 2012-04-27 16:51:48 TRACE nova service.wait() 2012-04-27 16:51:48 TRACE nova File
Re: [Openstack] [Openstack-operators] Mailing-list split
On Fri 27 Apr 2012 02:43:14 PM PDT, Duncan McGreggor wrote: But if openstack-operators has become a property valuable to community members, we shouldn't just get rid of it because it doesn't make logical sense. We should make sure that folks are ready to transition to another location for their DevOps needs. I agree with this approach: let's cross that bridge when we come to it. We should make one small change at the time, measure/evaluate and keep changing as needed. thanks, stef ___ 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.
Yong, oot@ubuntu0001:~# free -m total used free sharedbuffers cached Mem: 3951 2121 2830 0168 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 flaviami...@gmail.com From: Rogerio Goncalves roge...@gmail.com 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 enabledXXX 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.comwrote: 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.comwrote: is enabled and not running my compute node is virtual machine to test and configured with qemu (2 core, 4gb, 10gb free in nova-volumes) my last log message on nova-compute is: 2012-04-27 12:22:25 DEBUG nova.virt.libvirt.connection [-] Connecting to libvirt: qemu:///system from (pid=18588) _get_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.*py*:292 libvirt is running 18420 ?Sl 0:00 /usr/sbin/libvirtd -d On Thu, Apr 26, 2012 at 10:43 PM, heut2008 heut2...@gmail.com wrote: be sure nova-compute is running and is enabled by using nova-manage service list,also confirm that the compute node have enough resources(cpu,mem,disk) . 2012/4/27 Rogerio Goncalves roge...@gmail.com: Hello, Im getting this error when launching a new instance. Failed to schedule_run_instance: No valid host was found. Is the appropriate service running? http://paste.openstack.org/show/14020/ SO Ubuntu 12.04 libvirt-bin start/running, process 4153 nova-network start/running, process 4174 nova-compute start/running, process 4187 nova-api start/running, process 4198 nova-objectstore start/running, process 4210 nova-scheduler start/running, process 4222 nova-volume start/running, process 4235 nova-vncproxy start/running, process 4246 rabbitmq is up too Thanks Rogério Gonçalves ___ 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 -- Flávia Missi @flaviamissi http://twitter.com/flaviamissi flaviamissi.com.br https://github.com/flaviamissi ___ 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.
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 enabledXXX 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 sharedbuffers cached Mem: 3951 2121 2830 0168 160 -/+ buffers/cache:792 3159 Swap: 1951 0 1951 On Fri, Apr 27, 2012 at 8:11 PM, Yong Sheng Gong gong...@cn.ibm.comwrote: how much free ram left on your compute node? -openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: - To: Flavia Missi flaviami...@gmail.com flaviami...@gmail.com From: Rogerio Goncalves roge...@gmail.com 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 enabledXXX 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.comwrote: 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.comwrote: is enabled and not running my compute node is virtual machine to test and configured with qemu (2 core, 4gb, 10gb free in nova-volumes) my last log message on nova-compute is: 2012-04-27 12:22:25 DEBUG nova.virt.libvirt.connection [-] Connecting to libvirt: qemu:///system from (pid=18588) _get_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.*py*:292 libvirt is running 18420 ?Sl 0:00 /usr/sbin/libvirtd -d On Thu, Apr 26, 2012 at 10:43 PM, heut2008 heut2...@gmail.com wrote: be sure nova-compute is running and is enabled by using nova-manage service list,also confirm that the compute node have enough resources(cpu,mem,disk) . 2012/4/27 Rogerio Goncalves roge...@gmail.com: Hello, Im getting this error when launching a new instance. Failed to schedule_run_instance: No valid host was found. Is the appropriate service running? http://paste.openstack.org/show/14020/ SO Ubuntu 12.04 libvirt-bin start/running, process 4153 nova-network start/running, process 4174 nova-compute start/running, process 4187 nova-api start/running, process 4198 nova-objectstore start/running, process 4210 nova-scheduler start/running, process 4222 nova-volume start/running, process 4235 nova-vncproxy start/running, process 4246 rabbitmq is up too Thanks Rogério Gonçalves ___ Mailing list:
Re: [Openstack] [Metering] Metering repository in stackforge
Hey! On 04/27/2012 06:20 PM, Loic Dachary wrote: Hi, I would like to create a repository ceilometer in https://github.com/stackforge to host the code for the newborn Metering project ( https://launchpad.net/ceilometer , first meeting held this thursday http://wiki.openstack.org/Meetings/MeteringAgenda ). We would be more than thrilled to get you set up. I'm including Andrew here, as he's been doing most of the StackForge work. I'll also file a bug on openstack-ci to make sure we don't lose this. I'm not sure how to proceed, could you please guide me ? My github account name is dachary 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] Error in scheduler when create a new instance.
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.netFrom: Rogerio Goncalves roge...@gmail.comSent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.netDate: 04/28/2012 10:22AMSubject: Re: [Openstack] Error in scheduler when create a new instance.Zhang,I already triad.root@ubuntu0001:~# service libvirt-bin restartlibvirt-bin stop/waitinglibvirt-bin start/running, process 21469root@ubuntu0001:~# service nova-compute restartstop: Unknown instance: nova-compute start/running, process 21524root@ubuntu0001:~# service nova-scheduler restartnova-scheduler stop/waitingnova-scheduler start/running, process 21540 root@ubuntu0001:~# nova-manage service list2012-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_Atnova-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:15On Fri, Apr 27, 2012 at 11:17 PM, 张华 veryhua2...@gmail.com wrote: you need reboot libvirtd, yesterday I encounter the same problem2012/4/28 Rogerio Goncalves roge...@gmail.com Yong, oot@ubuntu0001:~# free -m totalusedfree shared buffers cachedMem: 395121212830 0168160-/+ buffers/cache:7923159 Swap: 1951 01951On 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.comFrom: Rogerio Goncalves roge...@gmail.comSent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.net Date: 04/28/2012 04:43AMCc: openstack@lists.launchpad.netSubject: 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 listBinary Host Zone Status State Updated_Atnova-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=AllHostsFilterHope it helps.[]'sOn Fri, Apr 27, 2012 at 12:29 PM, Rogerio Goncalves roge...@gmail.com wrote:is enabled and not runningmy compute node is virtual machine to test and configured with qemu (2 core, 4gb, 10gb free in nova-volumes)my last log message on nova-compute is:2012-04-27 12:22:25 DEBUG nova.virt.libvirt.connection [-] Connecting to libvirt: qemu:///system from (pid=18588) _get_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py:292 libvirt is running18420 ?Sl 0:00 /usr/sbin/libvirtd -d On Thu, Apr 26, 2012 at 10:43 PM, heut2008 heut2...@gmail.com wrote: be sure nova-compute is running and is enabled by using nova-manage service list,also confirm that the compute node have enough resources(cpu,mem,disk) . 2012/4/27 Rogerio Goncalves roge...@gmail.com: Hello, Im getting this error when launching a new instance. "Failed to schedule_run_instance: No valid host was found. Is the appropriate service running?" http://paste.openstack.org/show/14020/ SO Ubuntu 12.04 libvirt-bin start/running, process 4153 nova-network start/running, process 4174 nova-compute start/running, process 4187 nova-api start/running, process 4198 nova-objectstore start/running, process 4210 nova-scheduler start/running, process 4222 nova-volume start/running, process 4235 nova-vncproxy start/running, process 4246 rabbitmq is