Re: [openstack-dev] distibuted caching system in front of mysql server for openstack transactions
Dolph, Thanks! It is good that python example is provided! Qing From: Dolph Mathews [mailto:dolph.math...@gmail.com] Sent: Thursday, October 31, 2013 9:25 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] distibuted caching system in front of mysql server for openstack transactions On Mon, Oct 28, 2013 at 5:46 PM, Qing He qing...@radisys.commailto:qing...@radisys.com wrote: In my hard drive-less use case, I need an in-core-db/cache that can be in the same db cluster with real db (with hard drive) with the same sql api so that the current openstack code do not need to be changed, instead, just a pluggin with some configurations. This is pretty much the original use case that dogpile.cache grew out of, see: http://docs.sqlalchemy.org/en/rel_0_9/orm/examples.html#dogpile-caching -Original Message- From: Morgan Fainberg [mailto:m...@metacloud.commailto:m...@metacloud.com] Sent: Monday, October 28, 2013 10:22 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] distibuted caching system in front of mysql server for openstack transactions In light of what Dolph said with regards to Keystone, we are using dogpile.cache to implement memoization in front of our driver calls. It it has the ability to cache directly as well, but it has been effective (so far) for our use-case. That being said, I am unsure if caching in front of MySQL is really what we want. I believe that we should be caching after processing work (hence memoization mechanism) instead of at the SQL layer. This also means we can be measured in what we cache (oh hey, it makes no sense to cache X because it needs to be real time or there isn't a performance issue with that query / call, but Y does a ton of processing and is an expensive join/temptable query). In my experience, unless the whole application is designed with caching in mind, caching something as broad as MySQL calls (or any SQL store) is likely going to net exactly what Shawn Hartsock stated, adding a second performance issue. --Morgan On Mon, Oct 28, 2013 at 10:05 AM, Shawn Hartsock hartso...@vmware.commailto:hartso...@vmware.com wrote: I once heard a quote.. I had a performance problem, so I added caching. now I have two performance problems. this. 1,000 times this. Just to float this thought ... make sure it's considered... I've seen a *lot* of people misuse caching when what the really want is memoization. * http://stackoverflow.com/questions/1988804/what-is-memoization-and-how -can-i-use-it-in-python * http://stackoverflow.com/questions/10879137/how-can-i-memoize-a-class- instantiation-in-python ... I'm not sure what you're trying to do. So YMMV, TTFN, BBQ. # Shawn Hartsock - Original Message - From: Clint Byrum cl...@fewbar.commailto:cl...@fewbar.com To: openstack-dev openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Sent: Monday, October 28, 2013 12:12:49 PM Subject: Re: [openstack-dev] distibuted caching system in front of mysql server for openstack transactions Excerpts from Dolph Mathews's message of 2013-10-28 08:40:19 -0700: It's not specific to mysql (or sql at all), but keystone is using dogpile.cache around driver calls to a similar effect. http://dogpilecache.readthedocs.org/en/latest/ It can persist to memcache, redis, etc. I once heard a quote.. I had a performance problem, so I added caching. now I have two performance problems. Caching is unbelievably awesome in the jobs it can do well. When the problem is straight forward and the requirements are few, it is just the right thing to relieve engineering pressure to make an application more scalable. However, IMO, more than narrow, well defined cache usage is a sign that the application needs some reworking to scale. I like the principle of let's use dogpile so we don't have to reinvent multi-level caching. However, let's make sure we look at each performance issue individually, rather than just throwing them all in a cache box and waving the memcache wand. https://github.com/openstack/keystone/blob/master/keystone/common/c ache/core.py On Fri, Oct 25, 2013 at 6:53 PM, Qing He qing...@radisys.commailto:qing...@radisys.com wrote: All, Has anyone looked at the options of putting a distributed caching system in front of mysql server to improve performance? This should be similar to Oracle Coherence, or VMware VFabric SQLFire. ** ** Thanks, ** ** Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev
Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey
Has anyone looked at any lock-free solution? -Original Message- From: Sandy Walsh [mailto:sandy.wa...@rackspace.com] Sent: Wednesday, October 30, 2013 12:20 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey On 10/30/2013 03:10 PM, Steven Dake wrote: I will -2 any patch that adds zookeeper as a dependency to Heat. Certainly any distributed locking solution should be plugin based and optional. Just as a database-oriented solution could be the default plugin. Re: the Java issue, we already have optional components in other languages. I know Java is a different league of pain, but if it's an optional component and left as a choice of the deployer, should we care? -S PS As an aside, what are your issues with ZK? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ceilometer] Suggestions for alarm improvements ...
Sandy, Does the framework account for customizable events?: In my use case, I have a network (or some other proprietary way, e.g., some special BUS protocol) attached device that does not fit into openstack node structure. It can generate events. According to these events, Openstack orchestration layer (HEAT?) may need to do thing like failing over all vms on one system to another system (compute node). If I would like to use the alarm/notification system, I would need to add a Customized collector, and my events would need to be routed to, say HEAT, and I would need to define the action ( a plugging/callback?) corresponding to the event for HEAT to take on my behalf. Is my approach right/supported under the framework and the current HEAT (or some other components) release? Thanks, Qing -Original Message- From: Sandy Walsh [mailto:sandy.wa...@rackspace.com] Sent: Tuesday, October 29, 2013 6:34 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Ceilometer] Suggestions for alarm improvements ... Hey y'all, Here are a few notes I put together around some ideas for alarm improvements. In order to set it up I spent a little time talking about the Ceilometer architecture in general, including some of the things we have planned for IceHouse. I think Parts 1-3 will be useful to anyone looking into Ceilometer. Part 4 is where the meat of it is. https://wiki.openstack.org/wiki/Ceilometer/AlarmImprovements Look forward to feedback from everyone and chatting about it at the summit. If I missed something obvious, please mark it up so we can address it. -S ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] distibuted caching system in front of mysql server for openstack transactions
Thanks Morgan. In my embedded situation, There is no hard drive where I run the Openstack controller, keystone, and other control functions, thus, my only choice has to be to use an in-core-db (cache) for the realtime transactions into the database, and then use another process to sync the data into the real database cluster through network located off the controller node. From: Dolph Mathews [mailto:dolph.math...@gmail.com] Sent: Monday, October 28, 2013 8:40 AM To: OpenStack Development Mailing List Cc: Morgan Fainberg Subject: Re: [openstack-dev] distibuted caching system in front of mysql server for openstack transactions It's not specific to mysql (or sql at all), but keystone is using dogpile.cache around driver calls to a similar effect. http://dogpilecache.readthedocs.org/en/latest/ It can persist to memcache, redis, etc. https://github.com/openstack/keystone/blob/master/keystone/common/cache/core.py On Fri, Oct 25, 2013 at 6:53 PM, Qing He qing...@radisys.commailto:qing...@radisys.com wrote: All, Has anyone looked at the options of putting a distributed caching system in front of mysql server to improve performance? This should be similar to Oracle Coherence, or VMware VFabric SQLFire. Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- -Dolph ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [TripleO][Nova][neutron][Heat][Oslo][Ceilometer][Havana]Single Subscription Point for event notification
All, I found multiple places/components you can get event alarms, e.g., Heat, Ceilometer, Oslo, Nova etc, notification. But I fail to find any documents as to how to do it in the respective component documents. I 'm wondering if there is document as to if there is a single API entry point where you can subscribe and get event notification from all components, such as Nova, Neutron. Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO][Nova][neutron][Heat][Oslo][Ceilometer][Havana]Single Subscription Point for event notification
Sandy, Thanks for your comprehensive report card and detailed explanation! That helps a lot! I'll follow the route of using Yagi for now. Qing -Original Message- From: Sandy Walsh [mailto:sandy.wa...@rackspace.com] Sent: Monday, October 28, 2013 4:56 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [TripleO][Nova][neutron][Heat][Oslo][Ceilometer][Havana]Single Subscription Point for event notification Here's the current adoption of notifications in OpenStack ... hope it helps! http://www.sandywalsh.com/2013/09/notification-usage-in-openstack-report.html -S From: Qing He [qing...@radisys.com] Sent: Monday, October 28, 2013 8:48 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [TripleO][Nova][neutron][Heat][Oslo][Ceilometer][Havana]Single Subscription Point for event notification Thanks Angus! Yes, if this rpc notification mechanism works for all other components, e.g., Neutron, in addition to Nova, which seems to be the only documented component working with this notification system. For example, can we do something like Network.instance.shutdown/.end Or Storage.instance.shutdown/.end Or Image.instance.shutdown/.end ... -Original Message- From: Angus Salkeld [mailto:asalk...@redhat.com] Sent: Monday, October 28, 2013 4:36 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [TripleO][Nova][neutron][Heat][Oslo][Ceilometer][Havana]Single Subscription Point for event notification On 28/10/13 22:30 +, Qing He wrote: All, I found multiple places/components you can get event alarms, e.g., Heat, Ceilometer, Oslo, Nova etc, notification. But I fail to find any documents as to how to do it in the respective component documents. I 'm wondering if there is document as to if there is a single API entry point where you can subscribe and get event notification from all components, such as Nova, Neutron. Hi, If you are talking about rpc notifications, then this is one wiki page I know about: https://wiki.openstack.org/wiki/SystemUsageData (I have just added some heat notifications to it). -Angus Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] distibuted caching system in front of mysql server for openstack transactions
All, Has anyone looked at the options of putting a distributed caching system in front of mysql server to improve performance? This should be similar to Oracle Coherence, or VMware VFabric SQLFire. Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux
Thanks, Balaji. Did you keep it upto date with openstack releases or do you still stay with that Diablo? Qing From: Balaji Patnala [mailto:patnala...@gmail.com] Sent: Wednesday, October 23, 2013 3:17 AM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux Hi Qing, Freescale SoCs like P4080 and T4240 etc are supported for OpenStack as well. We have been using them from OpenStack Diablo release onwards. We demonstrated at ONS 2013, Interop 2013 and China Road Show. Regards, Balaji.P On 23 October 2013 08:57, Qing He qing...@radisys.commailto:qing...@radisys.com wrote: Matt, Great. Yes, what processor and free scale version you are running on? Do you have something for tryout? Thanks, Qing From: Matt Riedemann [mailto:mrie...@us.ibm.commailto:mrie...@us.ibm.com] Sent: Tuesday, October 22, 2013 8:11 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux Yeah, my team does. We're using openvswitch 1.10, qpid 0.22, DB2 10.5 (but MySQL also works). Do you have specific issues/questions? We're working on getting continuous integration testing working for the nova powervm driver in the icehouse release, so you can see some more details about what we're doing with openstack on power in this thread: http://lists.openstack.org/pipermail/openstack-dev/2013-October/016395.html Thanks, MATT RIEDEMANN Advisory Software Engineer Cloud Solutions and OpenStack Development Phone: 1-507-253-7622 | Mobile: 1-507-990-1889 E-mail: mrie...@us.ibm.commailto:mrie...@us.ibm.com [IBM] 3605 Hwy 52 N Rochester, MN 55901-1407 United States From:Qing He qing...@radisys.commailto:qing...@radisys.com To:OpenStack Development Mailing List openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org, Date:10/22/2013 07:43 PM Subject:Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux Thanks Matt. I'd like know if anyone has tried to run the controller, API server and MySql database, msg queue, etc-the brain of the openstack, on ppc. Qing From: Matt Riedemann [mailto:mrie...@us.ibm.com] Sent: Tuesday, October 22, 2013 4:17 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux We run openstack on ppc64 with RHEL 6.4 using the powervm nova virt driver. What do you want to know? Thanks, MATT RIEDEMANN Advisory Software Engineer Cloud Solutions and OpenStack Development Phone: 1-507-253-7622 | Mobile: 1-507-990-1889 E-mail: mrie...@us.ibm.commailto:mrie...@us.ibm.com [IBM] 3605 Hwy 52 N Rochester, MN 55901-1407 United States From:Qing He qing...@radisys.commailto:qing...@radisys.com To:OpenStack Development Mailing List openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org, Date:10/22/2013 05:49 PM Subject:[openstack-dev] [nova] Openstack on power pc/Freescale linux All, I'm wondering if anyone tried OpenStack on Power PC/ free scale Linux? Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev inline: image001.gif___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] Openstack on power pc/Freescale linux
All, I'm wondering if anyone tried OpenStack on Power PC/ free scale Linux? Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux
Thanks Matt. I'd like know if anyone has tried to run the controller, API server and MySql database, msg queue, etc-the brain of the openstack, on ppc. Qing From: Matt Riedemann [mailto:mrie...@us.ibm.com] Sent: Tuesday, October 22, 2013 4:17 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux We run openstack on ppc64 with RHEL 6.4 using the powervm nova virt driver. What do you want to know? Thanks, MATT RIEDEMANN Advisory Software Engineer Cloud Solutions and OpenStack Development Phone: 1-507-253-7622 | Mobile: 1-507-990-1889 E-mail: mrie...@us.ibm.commailto:mrie...@us.ibm.com [IBM] 3605 Hwy 52 N Rochester, MN 55901-1407 United States From:Qing He qing...@radisys.commailto:qing...@radisys.com To:OpenStack Development Mailing List openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org, Date:10/22/2013 05:49 PM Subject:[openstack-dev] [nova] Openstack on power pc/Freescale linux All, I'm wondering if anyone tried OpenStack on Power PC/ free scale Linux? Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev inline: image001.gif___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon] dashboard not showing all hard drive
Hi, My system hard drive of 250G was divided into two volumes, one 50G and the rest. But the dashboard only shows 50G, I'm wondering if anyone knows how to make it show the other 200G? Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Data Forwarding Nodes
Hi, There is a section in Openstack Network installation Guide called Install Software on Data Forwarding Nodes. I'm wondering What is difference between the concept of Data Forwarding Nodes here and the SDN control and forwarding plane? Is it possible to have a node in openstack act as a SDN control plane while another, as forwarding plane (termed Data Forwarding Nodes here)? Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] Does Heat support checkpointing for guest application
Steven, Thanks! Will look into it. Qing From: Steven Dake [mailto:sd...@redhat.com] Sent: Friday, September 20, 2013 12:48 PM To: OpenStack Development Mailing List Cc: Qing He Subject: Re: [openstack-dev] [Heat] Does Heat support checkpointing for guest application On 09/13/2013 02:18 PM, Qing He wrote: All, I'm wondering if Heat provide service for checkpointing the guest application for HA/redundancy similar to what corosync/pacemaker/openais provided for bare medal applications. Thanks, Qing Qing, Heat is an orchestration framework, whereas corosync is a distributed data transfer service. I think Marconi would better solve the problem you have. http://wiki.openstack.org/marconi Regards -steve ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Issues with IPTables
The follow up question is: Has anyone walked through the guides faithfully posted there and see if it works without back door tricks/tricks not documented there? -Original Message- From: Qing He Sent: Monday, September 16, 2013 10:37 AM To: 'Solly Ross' Cc: OpenStack Development Mailing List Subject: RE: Issues with IPTables Solly, It would be great if you can share the notes. The reason I asked the question is that I'm trying to decide If I need to allocate development time in installation following the installation guide. The usual wisdom is that installation with detailed instruction would take no time. However, your experience and mine showed the contrary. I have not finished mine following the Ubuntu installation guide. Thus, I was interested in knowing your effort spent on it so that I would know that it was not just me who had issues with the supposedly plug and play installation with the packages. Thanks, Qing -Original Message- From: Solly Ross [mailto:sr...@redhat.com] Sent: Monday, September 16, 2013 10:24 AM To: Qing He Cc: OpenStack Development Mailing List Subject: Re: Issues with IPTables Quite a while. RDO's documentation for configuring multinode Packstack with Neutron was a bit lacking, so after attempting to get that working for a while, I switched to following the Basic Install Guide (http://docs.openstack.org/trunk/basic-install/content/basic-install_intro.html). I also found the basic install guide catered for Fedora (http://docs.openstack.org/trunk/basic-install/yum/content/basic-install_intro.html), but that is sorely lacking in the actual instruction department, and is missing several steps. If you would like, I can attach the raw draft of my notes. Eventually, some of the changes or clairifications should make their way into the actual OpenStack Docs. Best Regards, Solly Ross - Original Message - From: Qing He qing...@radisys.com To: sr...@redhat.com Sent: Monday, September 16, 2013 1:14:42 PM Subject: RE: Issues with IPTables Solly, A side question, how long did this process take you? Thanks, Qing -Original Message- From: Solly Ross [mailto:sr...@redhat.com] Sent: Monday, September 16, 2013 10:11 AM To: OpenStack Development Mailing List Subject: [openstack-dev] Issues with IPTables In a enfort to improve/verify the Openstack Documentation with regards to RHEL and Fedora, I've been attempting to follow the basic install guides. I've managed to create a working installation and set of instructions. However, to do so I needed to disable the Neutron IPTables firewall, as it was blocking non-VM traffic. Namely, it was blocking the GRE packets being used by Neutron. Did I miss something, or is this a bug? Best Regards, Solly Ross ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Heat] Does Heat support checkpointing for guest application
All, I'm wondering if Heat provide service for checkpointing the guest application for HA/redundancy similar to what corosync/pacemaker/openais provided for bare medal applications. Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat] Propose Liang Chen for heat-core
+1 -Original Message- From: Angus Salkeld [mailto:asalk...@redhat.com] Sent: Thursday, August 22, 2013 4:33 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [heat] Propose Liang Chen for heat-core On 22/08/13 16:57 +0100, Steven Hardy wrote: Hi, I'd like to propose that we add Liang Chen to the heat-core team[1] Liang has been doing some great work recently, consistently providing good review feedback[2][3], and also sending us some nice patches[4][5], implementing several features and fixes for Havana. Please respond with +1/-1. +1 Thanks! [1] https://wiki.openstack.org/wiki/Heat/CoreTeam [2] http://russellbryant.net/openstack-stats/heat-reviewers-90.txt [3] https://review.openstack.org/#/q/reviewer:cbjc...@linux.vnet.ibm.com,n, z [4] https://github.com/openstack/heat/graphs/contributors?from=2013-04-18t o=2013-08-18type=c [5] https://review.openstack.org/#/q/owner:cbjc...@linux.vnet.ibm.com,n,z ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron]can you create network between a VM and a physical machine in neutron?
Thanks Aaron! From: Aaron Rosen [mailto:aro...@nicira.com] Sent: Wednesday, August 21, 2013 12:24 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [Neutron]can you create network between a VM and a physical machine in neutron? Hi, Yes, if you use the providernetwork extension you can create a network on a vlan and have physical hosts accessible on that vlan. If using the NVP plugin another option is to use its networkgw extension to do this in conjunction with overlay networks. Aaron On Wed, Aug 21, 2013 at 11:25 AM, Qing He qing...@radisys.commailto:qing...@radisys.com wrote: All, I'm trying to find way to create a network with a mixture of VM and physical machines. Is this possible? Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] can openstack compute manage both physical and machine machines?
Thanks, Yapeng! From: Yapeng Wu [mailto:yapeng...@huawei.com] Sent: Wednesday, August 21, 2013 1:20 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [Nova] can openstack compute manage both physical and machine machines? Qing, you can take a look at this link: https://wiki.openstack.org/wiki/Baremetal Yapeng From: Qing He [mailto:qing...@radisys.com]mailto:[mailto:qing...@radisys.com] Sent: Wednesday, August 21, 2013 2:23 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [Nova] can openstack compute manage both physical and machine machines? All, From the documents, It seems to me Nova can only manage virtual machines, but not mixed with physical machines. Am I wrong? Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] clay.gerrard: Your email has virus?
Clay, Is your computer affected by some virus? I don't believe post has anything to do with OpenStack! -Original Message- From: Clay Gerrard [mailto:clay.gerr...@gmail.com] Sent: Saturday, July 20, 2013 9:32 PM To: stacy...@eazymail.org; m...@not.mn; sale-708497...@craigslist.org; cth...@gmail.com; openstack-dev@lists.openstack.org; supp...@rentmethod.com; brandon.n.stell...@wellsfargo.com; anthony.chris...@cbnorcal.com; swplot...@amherst.edu Subject: [openstack-dev] clay.gerrard http://domeincheck.belgon.nl/pfape/yob.cckwcysypwqaxpjciyf ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Netron] lbaas installation guide
In the network installation guide( http://docs.openstack.org/grizzly/openstack-network/admin/content/install_ubuntu.html ) there is a sentence “quantum-lbaas-agent, etc (see below for more information about individual services agents).” in the pluggin installation section. However, lbaas is never mentioned again after that in the doc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] lbaas installation guide
By the way, I'm wondering if lbaas has a separate doc somewhere else? From: Anne Gentle [mailto:a...@openstack.org] Sent: Friday, July 19, 2013 6:33 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [Neutron] lbaas installation guide Thanks for bringing it to the attention of the list -- I've logged this doc bug. https://bugs.launchpad.net/openstack-manuals/+bug/1203230 Hopefully a Neutron team member can pick it up and investigate. Anne On Fri, Jul 19, 2013 at 7:35 PM, Qing He qing...@radisys.commailto:qing...@radisys.com wrote: In the network installation guide( http://docs.openstack.org/grizzly/openstack-network/admin/content/install_ubuntu.html ) there is a sentence quantum-lbaas-agent, etc (see below for more information about individual services agents). in the pluggin installation section. However, lbaas is never mentioned again after that in the doc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] lbaas installation guide
Thanks Anne! From: Anne Gentle [mailto:a...@openstack.org] Sent: Friday, July 19, 2013 6:33 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [Neutron] lbaas installation guide Thanks for bringing it to the attention of the list -- I've logged this doc bug. https://bugs.launchpad.net/openstack-manuals/+bug/1203230 Hopefully a Neutron team member can pick it up and investigate. Anne On Fri, Jul 19, 2013 at 7:35 PM, Qing He qing...@radisys.commailto:qing...@radisys.com wrote: In the network installation guide( http://docs.openstack.org/grizzly/openstack-network/admin/content/install_ubuntu.html ) there is a sentence quantum-lbaas-agent, etc (see below for more information about individual services agents). in the pluggin installation section. However, lbaas is never mentioned again after that in the doc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack] [cinder] Proposal for Ollie Leahy to join cinder-core
+1 From: Huang Zhiteng [mailto:winsto...@gmail.com] Sent: Wednesday, July 17, 2013 2:56 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [Openstack] [cinder] Proposal for Ollie Leahy to join cinder-core +1 for Ollie. On Wed, Jul 17, 2013 at 2:42 PM, Avishay Traeger avis...@il.ibm.commailto:avis...@il.ibm.com wrote: Walter A. Boring IV walter.bor...@hp.commailto:walter.bor...@hp.com wrote on 07/18/2013 12:04:07 AM: snip +1 to Ollie from me. +1 to John's points. If a company is colluding with other core members, from the same company, to do bad things within a project, it should become pretty obvious at some point and the project's community should take action. If someone is putting in an extra effort to provide quality code and reviews on a regular basis, then why wouldn't we want that person on the team? Besides, being a core member really just means that you are required to do reviews and help out with the community. You do get some gerrit privileges for reviews, but that's about it. I for one think that we absolutely can use more core members to help out with reviews during the milestone deadlines :) Walt, As I said, I really wasn't worried about anyone colluding or doing bad things. As you said, that would be obvious and could be handled. I was concerned about creating a limited view, and I thank you and everyone who replied for easing those concerns. And BTW, I don't think there is an HP conspiracy to take over Cinder and make it FC-only :) Thanks, Avishay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Regards Huang Zhiteng ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Event Service
All, Does open stack have pub/sub event service? I would like to be notified of the event of VM creation/deletion/Migration etc. What is the best way to do this? Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Event Service
Thanks Michael! I found it: https://wiki.openstack.org/wiki/NotificationEventExamples -Original Message- From: Michael Still [mailto:mi...@stillhq.com] Sent: Friday, July 12, 2013 6:38 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] Event Service OpenStack has a system called notifications which does what you're looking for. I've never used it, but I am sure its documented. Cheers, Michael On Sat, Jul 13, 2013 at 10:12 AM, Qing He qing...@radisys.com wrote: All, Does open stack have pub/sub event service? I would like to be notified of the event of VM creation/deletion/Migration etc. What is the best way to do this? Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-community] [User-committee] [OpenStack Marketing] openstack only deployment
Hi All, I'm wondering if anyone has deployed openstack without any proprietary software/component? Thanks, Qing ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Email is not registered problem
The emails from this list stopped coming to my email address, is this related? -Original Message- From: Jeremy Stanley [mailto:fu...@yuggoth.org] Sent: Wednesday, June 26, 2013 7:38 AM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] Email is not registered problem On 2013-06-26 17:31:26 +0800 (+0800), Wenhao Xu wrote: I am reworking on on one of my old patch today. After that, when I tried to do git review, I got the following error message: [...] remote: ERROR: committer email address wen...@zelin.io remote: ERROR: does not match your user account. remote: ERROR: remote: ERROR: The following addresses are currently registered: remote: ERROR:xuwenhao2...@gmail.com [...] I have updated my primary email address to wen...@zelin.io in launchpad, Gerrit and openstack foundation profile as well. I am wondering is there anything I missed? It's possible you've got two accounts in Gerrit, one you're updating through the WebUI (tied to your current Launchpad OpenID) and another which is associated with your SSH username but has the same SSH key along with your old E-mail address. We've run into a few like that which needed cleaning up, usually following LP account/OpenID changes. I'll look into it and follow up with you privately to resolve the issue. -- Jeremy Stanley ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Should RPC consume_in_thread() be more fault tolerant?
In this case, the exception is just hard to debug, and not something we expected in our design. The thorough solution would be to debug further to see the root cause, and deal with it as I suggested in the code review. However, If it is time consuming to debug, we can put the patch in there with logging to record the circumstances the 'unexpected' exception occurs, so that we can put in new patches to deal it when it becomes expected. After all, this is an iterative process. When the software evolves, a lot of unexpected has become expected. -Original Message- From: Raymond Pekowski (Code Review) [mailto:rev...@openstack.org] Sent: Tuesday, June 25, 2013 9:52 AM Cc: Dirk Mueller; Andrea Rosa; Ben Nemec; Chris Behrens; Eric Windisch; Russell Bryant; Qing He Subject: Change in openstack/oslo-incubator[master]: Make AMQP based RPC consumer threads more robust Raymond Pekowski has posted comments on this change. Change subject: Make AMQP based RPC consumer threads more robust .. Patch Set 12: By definition, unexpected exceptions are unexpected, so there is nothing yet to do root cause analysis on. We could argue as to what the appropriate action to take is, but that has already been discussed on the mailing list started by this thread: http://lists.openstack.org/pipermail/openstack-dev/2013-June/010040.html Please comment on that thread since you don't agree with the consensus that was reached. -- To view, visit https://review.openstack.org/32235 To unsubscribe, visit https://review.openstack.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I0d6ec8a5e3a310314da201656ee862bb40b41616 Gerrit-PatchSet: 12 Gerrit-Project: openstack/oslo-incubator Gerrit-Branch: master Gerrit-Owner: Raymond Pekowski raymond_pekow...@dell.com Gerrit-Reviewer: Andrea Rosa andrea.r...@hp.com Gerrit-Reviewer: Ben Nemec openst...@nemebean.com Gerrit-Reviewer: Chris Behrens cbehr...@codestud.com Gerrit-Reviewer: Dirk Mueller d...@dmllr.de Gerrit-Reviewer: Eric Windisch e...@cloudscaling.com Gerrit-Reviewer: Jenkins Gerrit-Reviewer: Qing He qing...@radisys.com Gerrit-Reviewer: Raymond Pekowski raymond_pekow...@dell.com Gerrit-Reviewer: Russell Bryant rbry...@redhat.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Should RPC consume_in_thread() be more fault tolerant?
Agree! Let someone know and keep going unless someone wants to interrupt it or do something. (Does there exist a mechanism already to do this?) -Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: Tuesday, June 25, 2013 12:21 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Should RPC consume_in_thread() be more fault tolerant? On 06/25/2013 03:15 PM, Ray Pekowski wrote: On Jun 25, 2013 1:09 PM, Qing He qing...@radisys.com mailto:qing...@radisys.com wrote: Basically, when 'unexpected' happens, someone (e.g., operator) needs to know about it and look into it to see if it is something benign or fatal. If it is masked, the system may degrade overtime unnoticed into unusable. The approach implemented in the patch is to log the exception and retry at a rate of one per second. An alternative would be a log and a sys.exit() to kill the entire process. Be aware that the code affected by this patch is rpc created dispatcher like threads. Let's have a vote on which option is preferrable. I like it how it's implemented, *not* killing the process ... -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Should RPC consume_in_thread() be more fault tolerant?
Does the log alert operator? Something like SNMP trap? From: Ray Pekowski [mailto:pekow...@gmail.com] Sent: Tuesday, June 25, 2013 12:16 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] Should RPC consume_in_thread() be more fault tolerant? On Jun 25, 2013 1:09 PM, Qing He qing...@radisys.commailto:qing...@radisys.com wrote: Basically, when 'unexpected' happens, someone (e.g., operator) needs to know about it and look into it to see if it is something benign or fatal. If it is masked, the system may degrade overtime unnoticed into unusable. The approach implemented in the patch is to log the exception and retry at a rate of one per second. An alternative would be a log and a sys.exit() to kill the entire process. Be aware that the code affected by this patch is rpc created dispatcher like threads. Let's have a vote on which option is preferrable. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Should RPC consume_in_thread() be more fault tolerant?
Clarify, operator does not have to go through a long log to find the issue. Instead, he/she needs to be notified that something severe/unexpected just happened and he/she needs to check it out. From: Qing He Sent: Tuesday, June 25, 2013 1:09 PM To: 'OpenStack Development Mailing List' Subject: RE: [openstack-dev] Should RPC consume_in_thread() be more fault tolerant? Does the log alert operator? Something like SNMP trap? From: Ray Pekowski [mailto:pekow...@gmail.com]mailto:[mailto:pekow...@gmail.com] Sent: Tuesday, June 25, 2013 12:16 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] Should RPC consume_in_thread() be more fault tolerant? On Jun 25, 2013 1:09 PM, Qing He qing...@radisys.commailto:qing...@radisys.com wrote: Basically, when 'unexpected' happens, someone (e.g., operator) needs to know about it and look into it to see if it is something benign or fatal. If it is masked, the system may degrade overtime unnoticed into unusable. The approach implemented in the patch is to log the exception and retry at a rate of one per second. An alternative would be a log and a sys.exit() to kill the entire process. Be aware that the code affected by this patch is rpc created dispatcher like threads. Let's have a vote on which option is preferrable. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[OE-core] [PATCH 0/1] Added Upstream-Status to various patches
From: Qing He qing...@intel.com Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: qhe/upstat Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=qhe/upstat Thanks, Qing He qing...@intel.com --- Qing He (1): update patch upstream status meta/recipes-bsp/grub/grub-0.97/autohell.patch |2 ++ .../pciutils/pciutils-3.1.7/configure.patch|1 + .../pciutils/pciutils-3.1.7/guess-fix.patch|2 ++ .../pciutils/pciutils-3.1.7/lib-build-fix.patch|2 ++ .../pciutils-3.1.7/pcimodules-pciutils.diff|2 ++ .../setserial/setserial/add_stdlib.patch |2 ++ .../dhcp/dhcp-4.2.0/dhcp-3.0.3-dhclient-dbus.patch |2 ++ .../dhcp/dhcp-4.2.0/fix-client-path.patch |2 ++ .../dhcp/dhcp-4.2.0/fix-external-bind.patch|2 ++ .../dhcp/dhcp-4.2.0/fixincludes.patch |2 ++ .../dhcp/dhcp-4.2.0/noattrmode.patch |1 + .../iproute2/iproute2-2.6.35/configure-cross.patch |2 ++ .../libnss-mdns/files/alignment-fix.patch |2 ++ .../nfs-utils/files/fix-ac-prereq.patch|2 ++ .../nfs-utils/nfs-utils-1.0.6-uclibc.patch |2 ++ .../openssl/openssl-0.9.8r/debian/ca.patch |2 ++ .../openssl-0.9.8r/debian/config-hurd.patch|2 ++ .../openssl-0.9.8r/debian/debian-targets.patch |2 ++ .../openssl-0.9.8r/debian/engines-path.patch |2 ++ .../openssl-0.9.8r/debian/kfreebsd-pipe.patch |2 ++ .../openssl-0.9.8r/debian/make-targets.patch |2 ++ .../openssl/openssl-0.9.8r/debian/man-dir.patch|2 ++ .../openssl-0.9.8r/debian/man-section.patch|2 ++ .../openssl/openssl-0.9.8r/debian/no-rpath.patch |2 ++ .../openssl-0.9.8r/debian/no-symbolic.patch|2 ++ .../openssl/openssl-0.9.8r/debian/perl-path.diff |2 ++ .../openssl/openssl-0.9.8r/debian/pic.patch|2 ++ .../openssl/openssl-0.9.8r/debian/pkg-config.patch |2 ++ .../openssl/openssl-0.9.8r/debian/rc4-amd64.patch |2 ++ .../openssl/openssl-0.9.8r/debian/rehash-crt.patch |2 ++ .../openssl/openssl-0.9.8r/debian/rehash_pod.patch |2 ++ .../openssl-0.9.8r/debian/shared-lib-ext.patch |2 ++ .../openssl/openssl-0.9.8r/debian/stddef.patch |2 ++ .../openssl-0.9.8r/debian/version-script.patch |2 ++ .../openssl/openssl-0.9.8r/parallel-make-fix.patch |2 +- .../portmap/portmap-6.0/destdir-no-strip.patch |2 ++ .../portmap/portmap-6.0/tcpd-config.patch |2 ++ .../busybox/busybox-1.18.4/B921600.patch |2 ++ .../busybox-appletlib-dependency.patch |2 ++ .../busybox/busybox-1.18.4/get_header_tar.patch|2 ++ .../busybox-1.18.4/run-parts.in.usr-bin.patch |2 ++ .../busybox-1.18.4/udhcpc-fix-nfsroot.patch|2 ++ .../busybox/busybox-1.18.4/udhcpscript.patch |2 ++ .../coreutils-6.9/coreutils-6.9-cp-i-u.patch |2 ++ .../coreutils-6.9/coreutils-fix-install.patch |2 ++ .../coreutils/coreutils-6.9/coreutils-i18n.patch |2 ++ .../coreutils/coreutils-6.9/coreutils-ls-x.patch |2 ++ .../coreutils-6.9/coreutils-overflow.patch |2 ++ .../coreutils-6.9/fix_for_manpage_building.patch |2 ++ .../coreutils/coreutils-6.9/futimens.patch |2 ++ .../coreutils/coreutils-6.9/gnulib_m4.patch|2 ++ .../coreutils/coreutils-6.9/man-touch.patch|2 ++ meta/recipes-core/dbus/dbus-1.4.1/tmpdir.patch |2 ++ .../dropbear/dropbear-0.52/configure.patch |2 ++ .../dropbear/dropbear/allow-nopw.patch |2 ++ .../dropbear/dropbear/fix-2kb-keys.patch |2 ++ .../urandom-xauth-changes-to-options.h.patch |2 ++ .../ncurses/ncurses-5.9/tic-hang.patch |2 ++ .../readline/files/configure-fix.patch |2 ++ .../sysfsutils-2.0.0-class-dup.patch |2 ++ .../sysvinit/sysvinit-2.88dsf/crypt-lib.patch |2 ++ .../sysvinit/sysvinit-2.88dsf/install.patch|2 ++ .../tinylogin/tinylogin-1.4/add-system.patch |2 ++ .../tinylogin-1.4/adduser-empty_pwd.patch |2 ++ .../tinylogin/tinylogin-1.4/cvs-20040608.patch |2 ++ .../tinylogin-1.4/passwd_rotate_check.patch|2 ++ .../tinylogin/tinylogin-1.4/remove-index.patch |2 ++ .../tinylogin/tinylogin-1.4/use_O2_option.patch|2 ++ meta/recipes-core/udev/files/fix-alignment.patch |2 ++ meta/recipes-core/udev/files/noasmlinkage.patch|1 + meta/recipes-core/udev/files/tmpfs.patch |1 + meta/recipes-core/udev/files/udevsynthesize.patch |2 ++ .../update-rc.d/update-rc.d/add-verbose.patch |2 ++ .../util-linux-2.17.2/remove-lscpu.patch |2 ++ .../util-linux-2.17.2/uclibc-compile.patch |2 ++ .../util-linux-ng-2.16-mount_lock_path.patch |2 ++ .../util-linux-ng
Re: [OE-core] [PATCH 2/2] quilt: fix test for target build
On Thu, 2011-04-14 at 23:23 +0800, Khem Raj wrote: The reason to touch this part of code is that the test itself doesn't work for newer versions of GNU patch, see: ??http://lists.nongnu.org/archive/html/quilt-dev/2010-06/msg2.html This surely fixes the configure error, but is logically not suitable for cross compiling. As I understand you are trying to fix quilt target recipe. Then may it will be better to take the above patch for both target and native but apply this workaround conditionally only for target recipe This was once backported, but subsequently reverted, see: http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=ec740ac770d2124cbae1ab936d85b8343076c53b autoconf-native is not available at the point of quilt-native, so autoreconf is not desirable. This is also the reason for separation of quilt and quilt-native from the very beginning. Apart from that, the workaround is solely for target recipe. there are options --with-patch --with-diff also there to point these utilities The problem still lies in cross building: --with-patch=${bindir}/patch at build time, it's /usr/bin/patch which is host utility, if target ${bindir} /= /usr/bin, the file may not exist. --with-patch=${STAGING_BINDIR}/patch causes runtime error as ${STAGING_BINDIR} leaks into target scripts --with-patch=patchthis may work, but may fail (in case the target scripts unset PATH) This is the problem of such tests without the concept of a target sysroot. Thanks, Qing ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/2] quilt: fix test for target build
From: Qing He qing...@intel.com fixes [YOCTO #969] Signed-off-by: Qing He qing...@intel.com --- .../quilt/quilt/gnu_patch_test_fix_target.patch| 66 meta/recipes-devtools/quilt/quilt_0.48.bb |6 +- 2 files changed, 70 insertions(+), 2 deletions(-) create mode 100644 meta/recipes-devtools/quilt/quilt/gnu_patch_test_fix_target.patch diff --git a/meta/recipes-devtools/quilt/quilt/gnu_patch_test_fix_target.patch b/meta/recipes-devtools/quilt/quilt/gnu_patch_test_fix_target.patch new file mode 100644 index 000..784fe76 --- /dev/null +++ b/meta/recipes-devtools/quilt/quilt/gnu_patch_test_fix_target.patch @@ -0,0 +1,66 @@ +The test of patch and diff should not be run for cross build, +rather, assume them as gnu version is rather safe. This is a +workaround to remove it altogether. + +Signed-off-by: Qing He qing...@intel.com + +diff --git a/configure.ac b/configure.ac +index 026a36c..7b45ca4 100644 +--- a/configure.ac b/configure.ac +@@ -245,55 +245,6 @@ fi + QUILT_COMPAT_PROG_PATH(DIFF, diff) + QUILT_COMPAT_PROG_PATH(PATCH, patch) + +-# Sun diff and others will not work because GNU patch options are used. +-AC_MSG_CHECKING([the version of $DIFF]) +-if $DIFF --version 2/dev/null | grep GNU /dev/null; then +- set -- `$DIFF --version 2/dev/null | $AWK '{ print $NF; exit }'` +- diff_version=$1 +- AC_MSG_RESULT($diff_version) +- saved_IFS=$IFS; IFS='.' +- set -- $diff_version +- IFS=$saved_IFS +- set -- `echo $1 | $TR -cd 0-9` `echo $2 | $TR -cd 0-9` +- if test 0$1 -lt 2 || test 0$1 -eq 2 -a 0$2 -lt 7 ; then +-diff_version= +- fi +-else +- AC_MSG_RESULT(no GNU diff) +-fi +-if test -z $diff_version ; then +- AC_MSG_ERROR([ +-$PACKAGE_NAME requires at least version 2.7 of GNU diffutils. You can +-download a current version of patch from ftp.gnu.org, or if you already +-have GNU diff then you can supply its path with the '--with-diff=' option. +-]) +-fi +- +- +-# Sun's patch, and others, do not work because GNU patch options are used. +-AC_MSG_CHECKING([the version of $PATCH]) +-if $PATCH --version 2 /dev/null | grep GNU /dev/null; then +- set -- `$PATCH --version 2 /dev/null` +- patch_version=$2 +- AC_MSG_RESULT($patch_version) +- saved_IFS=$IFS; IFS='.' +- set -- $patch_version +- IFS=$saved_IFS +- set -- `echo $1 | $TR -cd 0-9` `echo $2 | $TR -cd 0-9` +- if test 0$1 -lt 2 || test 0$1 -eq 2 -a 0$2 -lt 4 ; then +-patch_version= +- fi +-else +- AC_MSG_RESULT(no GNU patch) +-fi +-if test -z $patch_version ; then +- AC_MSG_ERROR([ +-$PACKAGE_NAME requires at least version 2.4 of GNU patch. You can download a +-current version of patch from ftp.gnu.org, or if you already have GNU patch +-then you can supply its path with the '--with-patch=' option. +-]) +-fi +- + QUILT_COMPAT_PROG_PATH(FIND, find) + + AC_MSG_CHECKING([whether $FIND -path works]) diff --git a/meta/recipes-devtools/quilt/quilt_0.48.bb b/meta/recipes-devtools/quilt/quilt_0.48.bb index 20a708d..124e2cd 100644 --- a/meta/recipes-devtools/quilt/quilt_0.48.bb +++ b/meta/recipes-devtools/quilt/quilt_0.48.bb @@ -2,8 +2,10 @@ require quilt.inc LICENSE=GPLv2 LIC_FILES_CHKSUM = file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f RDEPENDS_${PN} += patch diffstat bzip2 util-linux -PR = r0 -SRC_URI += file://aclocal.patch +PR = r1 +SRC_URI += file://aclocal.patch \ +file://gnu_patch_test_fix_target.patch \ + SRC_URI[md5sum] = f77adda60039ffa753f3c584a286f12b SRC_URI[sha256sum] = 73fd760d3b5cbf06417576591dc37d67380d189392db9000c21b7cbebee49ffc -- 1.7.0 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: librpmio memory allocation issue
On Mar 1, 2011, at 2:45 PM, Jeff Johnson wrote: On Mar 1, 2011, at 2:33 PM, Mark Hatle wrote: On 3/1/11 1:27 PM, Jeff Johnson wrote: On Mar 1, 2011, at 2:20 PM, Mark Hatle wrote: I think jbj might have figured out the problem. Zypper is not using pcre, but is instead causing mire to use the system regex. I made some local changes in an attempt to point the #include of regex.h in mire with a #error. I'm in the process of building both RPM and Zypper now to see if this causes a build failure -- if it does, we need to figure out a Zypper solution because it's bringing in mire.h. If you can show me the Zypper code that's trying to use miRE, I can likely suggest a clean fix. I am not finding any direct inclusions of miRE within Zypper or libzypper. However, I am finding an inclusion of regex.h within libzypper. One last note: Here's the valgrind spewage from the pojy bug report: =444== Invalid read of size 1 ==444==at 0x694C5DC: regcomp (regcomp.c:502) ==444==by 0x86F139B: mireRegcomp (mire.c:364) ==444==by 0x6E46E22: defaultMachine (rpmrc.c:475) ==444==by 0x6E4743B: rpmSetMachine (rpmrc.c:841) ==444==by 0x6E475B3: rpmRebuildTargetVars.clone.1 (rpmrc.c:925) ==444==by 0x6E47DFA: rpmReadConfigFiles (rpmrc.c:1115) ==444==by 0x52E45A6: zypp::target::rpm::librpmDb::globalInit() (in /usr/lib/libzypp.so.810.1.0) ==444==by 0x52C6990: zypp::target::rpm::RpmDb::RpmDb() (in /usr/lib/libzypp.so.810.1.0) ==444==by 0x52FC023: zypp::target::TargetImpl::TargetImpl(zypp::filesystem::Pathname const, bool) (in /usr/lib/libzypp.so.810.1.0) ==444==by 0x5412F08: zypp::Target::Target(zypp::filesystem::Pathname const, bool) (in /usr/lib/libzypp.so.810.1.0) ==444==by 0x5425BA3: zypp::zypp_detail::ZYppImpl::initializeTarget(zypp::filesystem::Pathname const, bool) (in /usr/lib/libzypp.so.810.1.0) ==444==by 0x5420E2E: zypp::ZYpp::initializeTarget(zypp::filesystem::Pathname const, bool) (in /usr/lib/libzypp.so.810.1.0) ==444== Address 0xb2a9f88 is not stack'd, malloc'd or (recently) free'd ==444== The only way that backtrace can happen (that I can see) is if RPM, not zypper, is mis-compiled using an unfixed (to redefine colliding symbols) system: PCRE with #include pcreposix.h which leaves you two choices: 1) fix you system PCRE pcreposix.h 2) build --with-pcre=internal This helps a lot, with the patching of system PCRE, the problem seems gone. The RPM we are using is rpm-5.4.0, which doesn't have an internal pcre shipped, so I diffed the system header with the internal header, and saw the #define regcomp pcreposix_regcomp artifact. It's then much clearer to understand what actually happened, regex_t from pcreposix.h is used bug regcomp from libc is what get called at runtime, that causes the failure. Interestingly, this patch is also found in Debian, but no versions of vanilla PCRE. I tried to find some original discussion on the issue, but got no meaningful result, is there any references? And why PCRE upstream is sticking to this? From what I know of zypper (mostly libsatsolver and tools), the code rips everything out-of-an-rpmdb and uses as little as possible from RPM libraries. But I haven't looked for 2+ years. Doesn't know much about zypper internals, but the issue above is triggered with only NULL passing around. Thanks, Qing __ RPM Package Managerhttp://rpm5.org Developer Communication Listrpm-devel@rpm5.org
[PATCH] Fix parallel build for shared library
When I tried to parallel make while enabling shared in Configure, the following error is encountered. | make: *** No rule to make target `libcrypto.a', needed by `libcrypto.so.0.9.8'. Stop. The attached patch adds the dependency rules for libcrypto.a and libssl.a, fixing the above error message. Signed-off-by: Qing He qing...@intel.com --- This is the version against 0.9.8o diff --git a/Makefile.org b/Makefile.org index e87d623..9fc8297 100644 --- a/Makefile.org +++ b/Makefile.org @@ -350,6 +350,9 @@ all_testapps: build_libs build_testapps build_testapps: @dir=crypto; target=testapps; $(BUILD_ONE_CMD) +libcrypto.a: build_crypto +libssl.a: build_ssl + build_shared: $(SHARED_LIBS) libcrypto$(SHLIB_EXT): libcrypto.a $(SHARED_FIPS) @if [ $(SHLIB_TARGET) != ]; then \ __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
subscribe
-- To UNSUBSCRIBE, email to debian-chinese-big5-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/r2u9f6fdb821004171134x86dea96er30b2d2e493f29...@mail.gmail.com
subscribe
姓名:何庆,rool 年龄:23 地区:成都 职业/学历:本科 代号: 想负责的工作:暂时还不知道自己能做什么 经验与心得: 如何跟 Debian 结缘:看见有Linux又看见ubuntu再看到debian 其他:
Re: [PATCH] x86/kvm: Show guest system/user cputime in cpustat
On Thu, 2010-03-11 at 17:17 +0800, Sheng Yang wrote: On Thursday 11 March 2010 15:50:54 Avi Kivity wrote: On 03/11/2010 09:46 AM, Sheng Yang wrote: On Thursday 11 March 2010 15:36:01 Avi Kivity wrote: On 03/11/2010 09:20 AM, Sheng Yang wrote: Currently we can only get the cpu_stat of whole guest as one. This patch enhanced cpu_stat with more detail, has guest_system and guest_user cpu time statistics with a little overhead. Signed-off-by: Sheng Yangsh...@linux.intel.com --- This draft patch based on KVM upstream to show the idea. I would split it into more kernel friendly version later. The overhead is, the cost of get_cpl() after each exit from guest. This can be very expensive in the nested virtualization case, so I wouldn't like this to be in normal paths. I think detailed profiling like that can be left to 'perf kvm', which only has overhead if enabled at runtime. Yes, that's my concern too(though nested vmcs/vmcb read already too expensive, they should be optimized...). Any ideas on how to do that? Perhaps use paravirt_ops to covert the vmread into a memory read? We store the vmwrites in the vmcs anyway. When Qing(CCed) was working on nested VMX in the past, he found PV vmread/vmwrite indeed works well(it would write to the virtual vmcs so vmwrite can also benefit). Though compared to old machine(one our internal patch shows improve more than 5%), NHM get less benefit due to the reduced vmexit cost. One of the hurdles to PVize vmread/vmwrite is the fact that the memory layout of physical vmcs remains unknown. Of course it can use the custom vmcs layout utilized by nested virtualization, but that looks a little weird, since different nested virtualization implementation may create different custom layout. I once used another approach to partially accelerate the vmread/vmwrite in nested virtualization case, which also gives good performance gain (around 7% on pre-nehalem, based on this, PV vmread/vmwrite had another 7%). That is to make a shortcut to handle EXIT_REASON_VM{READ,WRITE}, without even turning on the IF. Thanks, Qing -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC] Nested VMX support - kernel
Orit, First, thank you for this work, it's very interesting. I tried the patchset but met some problem. It's a kernel panic in L2 guest, and L1 L0 remains operable: BUG: unable to handle kernel paging request at 0104b00d IP: [c0105282] math_state_restore+0xe/0x2f *pde = For my environment, the L1 hypervisor is 32 bit KVM (kernel version is 2.6.25), the complete serial.log of L2 is attached. Do you know how I can get over this hang? Thanks, Qing On Mon, 2009-08-17 at 21:48 +0800, or...@il.ibm.com wrote: From: Orit Wasserman or...@il.ibm.com This patch implements nested VMX support. It enables a guest to use the VMX APIs in order to run its own nested guest (i.e., it enables running other hypervisors which use VMX under KVM). The current patch supports running Linux under a nested KVM. Additional patches for running Windows under nested KVM, and Linux and Windows under nested VMware server(!), are currently running in the lab. We are in the process of forward-porting those patches to -tip. The current patch only supports a single nested hypervisor, which can only run a single guest. SMP is not supported yet when running nested hypervisor (work in progress). Only 64 bit nested hypervisors are supported. Currently only EPT mode in both host and nested hypervisor is supported (i.e., both hypervisors must use EPT). This patch was written by: Orit Wasserman, or...@il.ibm.com Ben-Ami Yassour, ben...@il.ibm.com Abel Gordon, ab...@il.ibm.com Muli Ben-Yehuda, m...@il.ibm.com With contributions by Anthony Liguori, aligu...@us.ibm.com Mike Day, md...@us.ibm.com This work was inspired by the nested SVM support by Alexander Graf and Joerg Roedel. Signed-off-by: Orit Wasserman or...@il.ibm.com Linux version 2.6.25 (r...@localhost.localdomain) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Mar 18 13:12:03 CST 2009 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e8000 - 0010 (reserved) BIOS-e820: 0010 - 31ff (usable) BIOS-e820: 31ff - 3200 (ACPI data) BIOS-e820: fffbd000 - 0001 (reserved) 0MB HIGHMEM available. 799MB LOWMEM available. Scan SMP from c000 for 1024 bytes. Scan SMP from c009fc00 for 1024 bytes. Scan SMP from c00f for 65536 bytes. found SMP MP-table at [c00fb540] 000fb540 Zone PFN ranges: DMA 0 - 4096 Normal 4096 - 204784 HighMem204784 - 204784 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 - 204784 DMI 2.4 present. Using APIC driver default ACPI: RSDP 000FB660, 0014 (r0 QEMU ) ACPI: RSDT 31FF, 002C (r1 QEMU QEMURSDT1 QEMU1) ACPI: FACP 31FF002C, 0074 (r1 QEMU QEMUFACP1 QEMU1) ACPI: DSDT 31FF0100, 24A4 (r1 BXPC BXDSDT1 INTL 20061109) ACPI: FACS 31FF00C0, 0040 ACPI: APIC 31FF25A8, 00E0 (r1 QEMU QEMUAPIC1 QEMU1) ACPI: PM-Timer IO Port: 0xb008 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:2 APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] disabled) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] disabled) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] disabled) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] disabled) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0c] disabled) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0d] disabled) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0e] disabled) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0f] disabled) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 4000 (gap: 3200:cdfbd000) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 203185 Kernel command line: ro root=LABEL=/ rhgb console=ttyS0 console=tty0 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 16384 bytes) Detected 3200.275 MHz processor. Console: colour VGA+ 80x25 console [tty0] enabled console