Re: [Openstack] install cloud computing by openstack!!!
On Mon, May 28, 2012 at 10:12 AM, Từ Minh Mẫn tuminh...@gmail.com wrote: I reading document about install: http://docs.openstack.org/essex/openstack-compute/starter/content/Base_OS-d1e542.html I am using Window7 32bit, I want to install server1(64 bit version of Ubuntu server 12.04) on Virtual machine (VMWare Workstation 8), When I boot VMWare to install Ubuntu, I have problem: This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot – please use a kernel appropriate for your CPU Please help me to solve this problem! check this article, which has details on hardware requirements, and a link to the processor check utility. http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=1003945 mike ___ 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] install cloud computing by openstack!!!
On Fri, May 25, 2012 at 12:20 AM, Razique Mahroua razique.mahr...@gmail.com wrote: Hey :-) Please start here : http://docs.openstack.org/essex/openstack-compute/starter/content/ And let us know if you have any issues. Also join us on the IRC freenode channel openstack Razique Nuage Co - Razique Mahroua razique.mahr...@gmail.com The wiki page http://wiki.openstack.org/GetOpenStack lists many of the sources for OpenStack, and there are many links to distribution specific install guides. mike ___ 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] install cloud computing by openstack!!!
It's really a matter of which Linux distro you prefer (or know better) - the OpenStack pieces are the same everywhere. I personally work with both Ubuntu _and_ Fedora regularly - but as long as I can run vim and lxde, I'm usually happy with the environment. It's all Linux, after all. I tend to use Ubuntu for openstack development work since the devstack.py toolchain favoured that initially, but I also run Fedora on other machines. mike On Sun, May 27, 2012 at 4:11 PM, Razique Mahroua razique.mahr...@gmail.comwrote: Hey Michael, Which one did you pick ? On which environment would you like to deploy OpenStack ? Razique Michael Pittaro mik...@lahondaresearch.org 27 mai 2012 19:00 On Fri, May 25, 2012 at 12:20 AM, Razique Mahroua The wiki page http://wiki.openstack.org/GetOpenStack lists many of the sources for OpenStack, and there are many links to distribution specific install guides. mike Razique Mahroua razique.mahr...@gmail.com 25 mai 2012 09:20 Hey :-) Please start here : http://docs.openstack.org/essex/openstack-compute/starter/content/ And let us know if you have any issues. Also join us on the IRC freenode channel openstack Razique Từ Minh Mẫn tuminh...@gmail.com 25 mai 2012 09:07 Dear all, I am student of master information, I am a new member of openstack mailing list. This is the first time I study about cloud computing, please help me (step by step - if any) to implement cloud computing, to me can understand and can deployment a system by cloud computing! Thank you so much and best regard!!! -- -- Man Tu Minh Mobile : 0989998815 Email : tuminh...@gmail.com tuminh...@yahoo.com.vn ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Nuage Co - Razique Mahroua razique.mahr...@gmail.com postbox-contact.jpgimage.jpgcompose-unknown-contact.jpg___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] Minimum required code coverage per file
On Tue, Apr 24, 2012 at 1:11 PM, Joe Gordon j...@cloudscaling.com wrote: Hi All, I would like to propose a minimum required code coverage level per file in Nova. Say 80%. This would mean that any new feature/file should only be accepted if it has over 80% code coverage. Exceptions to this rule would be allowed for code that is covered by skipped tests (as long as 80% is reached when the tests are not skipped). +1 Paying attention to code coverage in unit tests has always served me well in the past. mike ___ 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] Essex on RHEL 6.2 and Cent OS 6.2
On Mon, Apr 16, 2012 at 8:19 AM, Salman A Baset saba...@us.ibm.com wrote: Hello folks, Has anyone tried to install Essex compute, and cloud controller on RHEL 6.2 or Cent OS 6.2? Any experiences? We tried to install Openstack Essex (2012) release on RHEL 6.2. Since there are no packages ready for it, we tried to use Fedora 16, 17 and 18 packages. In all cases, we found that it not only requires a large number of dependencies, as some of them are only available in the not yet released RHEL 6.3 (like dnsmasq-utils), but that it also requires python 2.7. DeStackPy has support for RHEL 6.2 and Fedora 16. It's not a production installer, but it will help you with the various dependencies. http://readthedocs.org/docs/devstackpy/en/latest/ https://github.com/yahoo/Openstack-DevstackPy The Essex release notes also have some distro information: http://wiki.openstack.org/ReleaseNotes/Essex#Known_packaged_distributions mike ___ 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-network service stuck
The clean_file_locks.py script should do the job safely - it only removes locks for processes which no longer exist. Usually, if a lock was left behind, then a process somewhere also failed, so check for that as well. mike On Sat, Apr 14, 2012 at 6:55 PM, Nathanael Burton nathanael.i.bur...@gmail.com wrote: Salman, The location for the locks is determined by the --lock_path setting in nova.conf. This is apparently set to the base path where the nova python code lives ($pybasedir) in devstack: 2012-04-14 21:35:42 DEBUG nova.service [-] lock_path : /opt/stack/nova from (pid=3700) wait /opt/stack/nova/nova/service.py:442 Since, that directory has a bunch of important files in it, certainly don't follow my previous advice and remove all the files in that directory. There is a bug (https://bugs.launchpad.net/nova/+bug/785955) about nova not cleaning up locks that should have been fixed in essex-4. As part of the fix to that Mike Pittaro wrote a cleanup locks script that should be in /opt/stack/nova/tools/clean_file_locks.py. Try running that and let us know if that fixed it. If not look for *.lock files in /opt/stack/nova Thanks, Nate On Sat, Apr 14, 2012 at 9:07 PM, Salman Malik salma...@live.com wrote: Thanks Nate for the quick reply. There is no such directory on the system (I am using devstack if that helps...) Thanks, Salman Date: Sat, 14 Apr 2012 21:00:39 -0400 Subject: Re: [Openstack] nova-network service stuck From: nathanael.i.bur...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Check in Nova's lock dir, on my system it's /var/lib/nova/tmp. Remove any files in there and restart the services. Nate On Apr 14, 2012 8:56 PM, Salman Malik salma...@live.com wrote: Hi All, I am having problem with getting nova-service to work. The last line that is shown on the screen is: 2012-04-14 19:42:39 DEBUG nova.utils [-] Attempting to grab file lock iptables for method apply... from (pid=3649) inner /opt/stack/nova/nova/utils.py:936 and the service is stuck at this point. So when I do a nova-manage service list, network service turns out to be unhappy. I haven't found much help on how to 'unlock' iptables file. Thoughts please ? 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 ___ 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] Templates for slides?
On Wed, Apr 11, 2012 at 5:47 PM, Stefano Maffulli stef...@openstack.org wrote: On Wed, 2012-04-11 at 17:21 -0700, Joshua Harlow wrote: Are there any good powerpoint/keynote templates for slides that should be used for the conference/summit (ie with openstack branding??) Or is it just show whatever u want for the template (if anything)? All speakers *for the conference* should be in contact with Laura Beck (I'll email you privately later with her email): she is your go-to point for all questions about logistics at the conference. For the summit, I don't think the standard is: use what you're familiar with :) For the benefit of those of us who only know how to use text editors, I just pushed an OpenStack themed template based on docutils / S5 to my github repository. Feel free to use or modify it: https://github.com/lhrc-mikeyp/Presentations/tree/master/OpenStackTemplate tl;dr; Summary: edit the presentation.rest file, and run rst2s5.py to generate the slides. More details in the readme. mike ___ 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] [Doc] Nova options changes and documentation
On Thu, Mar 29, 2012 at 12:59 PM, Anne Gentle a...@openstack.org wrote: Hi Docs Core team and others, David Kranz has identified changes to the nova.conf configuration options in the attached .diff file. They directly affect the configuration chapter for the Compute Admin manual as well as the networking chapter. I have also gone through all the possible flags and created this list: http://etherpad.openstack.org/newflagsessex indicate what are new in Essex. I realize this is a lot of work and I'd like ideas for how to track the doc work for all these changes. My sense is that many are already logged as doc bugs so possibly I just log more bugs based on groups of flags. ... How else can we parcel out the doc work and track it? Open to any and all ideas here. I think a blueprint for the 'Essex Flags' documentation will help track it. We can then link bugs to the blueprint, and update the blueprint with any additional notes or links. I think a single bug for each group of options will probably suffice; there will only be a few people working on this anyways. mike ___ 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] PyCon 2012 Sprints update
Just a reminder that OpenStack is sprinting at PyCon 2012 in Santa Clara, CA starting tomorrow, March 12th. You don't have to be a PyCon attendee to attend the sprints in person. However, food was budgeted for conference attendees, so plan on bringing a bag lunch or buying lunch locally. For sprint topics so far, we have: - solving the not-file-injection bootstrap of auth - an effective and agreed upon method for supporting read-write metadata (plus or minus the auth concerns) - finishing the RBAC work - defining a first draft of an API for layer 3 networking support - adding test coverage for eventlet in Nova - finishing the Consolidate Testing Infrastructure blueprint - Horizon improvements for Quantum support - Python devstack (check it out on github) There is a sprint page on the wiki at http://wiki.openstack.org/Sprints/PyCon2012 The main pycon sprint page is at https://us.pycon.org/2012/community/sprints/ Now's the time to add any other sprint topics to the wiki and review open bugs. Docs have been lagging the release, so if anyone want's to work on documentation I can help with the docs workflow since I've been through it a few times. mike ___ 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] PyCon 2012 Sprints update
On Sun, Mar 11, 2012 at 1:33 PM, Sumit Naiksatam (snaiksat) snaik...@cisco.com wrote: Hi Michael, Thanks for taking the lead on this. I was curious to know as to what the agenda is on the following sprint topic: defining a first draft of an API for layer 3 networking support Is this discussion in the context of Nova or Quantum (probably both)? I can't answer, since I didn't define the sprint topics - that's has been a collaborative effort via the wiki. The wiki's page info button will give you an idea of who added each topic. While on that, I would like to draw your attention to a Quantum blueprint proposal we have submitted a while back and have been actively developing and discussing: Blueprint: https://blueprints.launchpad.net/quantum/+spec/quantum-l3-api I'm sure this will be a topic of discussion tomorrow. Also, if it's available, could you kindly let us know what the OpenStack Sprint schedule is? Thanks, ~Sumit. The overall schedule is Sprints themselves will run Monday, March 12 to Thursday, March 15 from early morning until people leave. Realistically, sprints typically start up around 9am and run until dinner, but late-nighters and all-nighters are okay (and common). So far, there is no OpenStack specific schedule beyone tomorrow's 9am start. I suspect one will develop tomorrow, and if it does, I'll update the wiki page. mike ___ 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] eventlet weirdness
On Wed, Feb 29, 2012 at 1:02 PM, Yun Mao yun...@gmail.com wrote: Hi, we sometimes notice this error message which prevent us from starting nova services occasionally. We are using a somewhat modified diablo stable release on Ubuntu 11.10. It may very well be the problem from our patches but I'm wondering if you guys have any insight. In what condition does this error occur? There is a similar bug in here: https://bugs.launchpad.net/nova/+bug/831599 but that doesn't offer much insight to me. Helps are very appreciated. Thanks, Yun One tip - make sure you capture stdout/stderr, as well as logs. Although I haven't see this particular error, I have seen at least one case where libvirt related errors weren't in the log, but made it to the console. mike ___ 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] Orchestration meetings/futures
On Fri, Feb 24, 2012 at 11:16 AM, Joshua Harlow harlo...@yahoo-inc.com wrote: How about a big session on this at the folsom summit? This is really a very important part and should be heavily discussed (to avoid the zones code problem happening again). -Josh +1 I would like to see a session around this early in the summit, so we can coordinate more sessions. 'Orchestration' can quickly expand to cover a lot of areas, and we need to divide and conquer. mike ___ 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 i8ln?
When it comes to server software, log files are not just for developers. In my experience, the first people who look at log files are operators and users. For non-English speakers, something as simple as the absence of the word 'ERROR' or 'WARNING' in a critical message can mean the difference between a quick solution and hours of troubleshooting. I'm 100% in favor of localization of messages. If anything more formal is needed, then you can always use message ids and codes, but I personally never found that useful. mike ___ 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] Orchestration meetings/futures
On Mon, Feb 20, 2012 at 12:46 PM, Sriram Subramanian sri...@computenext.com wrote: +1 for the same slot and for both of your proposals/ suggestions. What is the current state of the Orchestration project - I don't see any entries in the wiki/ getting started guides. Did I look at wrong place? Here's a quick summary: The original proposal, circa Essex summit, is at http://wiki.openstack.org/NovaOrchestration The team meeting history is at http://wiki.openstack.org/Meetings/Orchestration The Overall 'orchestration' effort was preempted by the more urgent work done by Sandy on the scheduler and the capacity cache, described at http://wiki.openstack.org/EssexSchedulerImprovements [ I cross-posted to the orchestration list for reference, but we are no longer using it.] mike ___ 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] .Net API
On Thu, Feb 16, 2012 at 11:21 AM, Mahdi Njim njimma...@gmail.com wrote: HI My Name is Mahdi Njim and I'm a developer, We are working on openstack nova and we like to create web application that can controle it using .Net, I looked in the internet but it seems that there is no existing.Net API for openstack nova. So we started writing our one but I would to check first if there is any APIs that we missed in the internet. Thanx The only API is REST, and can be called from many programming languages. The novaclient library is a Python interface to the REST API. There is also an early Java library which also uses the REST API. https://github.com/woorea/openstack-java-sdk/ You should be able to call the API from .Net with the WCF REST Starter kit without too much effort. http://aspnet.codeplex.com/releases/view/24644 http://msdn.microsoft.com/en-us/netframework/cc950529.aspx I'm not aware of any .net libraries for OpenStack. mike ___ 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] PyCon 2012 Sprints?
On Thu, Feb 16, 2012 at 2:50 PM, Duncan McGreggor dun...@dreamhost.com wrote: On Wed, Dec 14, 2011 at 4:23 PM, Duncan McGreggor dun...@dreamhost.com wrote: I just found out that PyCon 2012 registration opened up: https://us.pycon.org/2012/registration/ and was wondering: * are there any OpenStack sprints planned for March 12 through Thursday March 15? * is there a wiki page for this yet on wiki.openstack.org? A quick search answered my question on the latter point, so I created these two pages: * http://wiki.openstack.org/Sprints * http://wiki.openstack.org/Sprints/PyCon2012 There's no content there yet, just placeholders waiting for that first bullet item... ;-) d Are any folks in the OpenStack community planning to attend the PyCon sprints? Meat-space attendance isn't required; lots of sprinting happens over IRC. I've updated the wiki with some topics proposed by various folks I've chatted with face-to-face. Feel free to add more... d I'll be attending the Sprints. I also added OpenStack to the Pycon sprints page, to to carve out our space before it's all taken. https://us.pycon.org/2012/community/sprints/projects/ mike ___ 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 make merge proposal to openstack-manuals
On Fri, Feb 3, 2012 at 1:53 AM, Dan Wendlandt d...@nicira.com wrote: 2012/2/3 masumo...@nttdata.co.jp: Hello, Could anybody tell me merge proposals to openstack-manual is same as other project (nova, swift, etc)? I am asking because I cannot see any MPs in Gerrit. yes, you can use the standard gerrit workflow: http://wiki.openstack.org/GerritWorkflow repo is: https://github.com/openstack/openstack-manuals open reviews are here: https://review.openstack.org/#q,status:open+project:openstack/openstack-manuals,n,z git review can be used to submit changes. dan There is additional specific information at : http://wiki.openstack.org/Documentation/HowTo mike ___ 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] Configure Rate limits on OS API
On Fri, Dec 30, 2011 at 11:34 AM, Jay Pipes jaypi...@gmail.com wrote: I struggled to figure out how to change this ratelimiting stuff for ages while working on Tempest. Eventually, I just removed the ratelimit middleware entirely from the pipeline since I could find no documentation whatsoever on how to change the limits. It would be awesome if this was documented in the Nova docs. I've added a bug to remind about it: https://bugs.launchpad.net/nova/+bug/910193 Cheers, There's a merge prop for the compute admin documentation at https://review.openstack.org/#change,3653 Comments appreciated. mike ___ 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] trusted computing and nova
On Thu, Dec 8, 2011 at 2:27 PM, Mark Washenberger mark.washenber...@rackspace.com wrote: Does code specific to Trusted Computing belong in Nova? It seems like it should be supported through Scheduler plugins and API plugins (if necessary). It seems like the ideas of attestation and trusted computing are tangential to the core of Nova. I can easily imagine a lot of scheduler variations that Nova should support. Adding custom code to nova for each variation would probably lead to a lot of extra complexity. However, the current trusted computing blueprint sets the precedent that each such variation deserves its own custom code (which nova developers are then presumably expected to support). I think we need to make sure the appropriate hook's are in place so it can be added, but beyond that I see an explosion of variations and dependencies. My initial impression, like yours, is that it can be accomplished in a custom scheduler. But I'm not a trusted computing expert, so I'd be interested in hearing why that wouldn't work, and what additional hooks might be needed. Context: https://blueprints.launchpad.net/nova/+spec/trusted-computing-pools http://wiki.openstack.org/TrustedComputingPools https://review.openstack.org/1899 mike ___ 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] [Orchestration] Handling error events ... explicit vs. implicit
On Wed, Dec 7, 2011 at 7:26 AM, Sandy Walsh sandy.wa...@rackspace.com wrote: For orchestration (and now the scheduler improvements) we need to know when an operation fails ... and specifically, which resource was involved. In the majority of the cases it's an instance_uuid we're looking for, but it could be a security group id or a reservation id. With most of the compute.manager calls the resource id is the third parameter in the call (after self context), but there are some oddities. And sometimes we need to know the additional parameters (like a migration id related to an instance uuid). So simply enforcing parameter orders may be insufficient and impossible to enforce programmatically. A little background: In nova, exceptions are generally handled in the RPC or middleware layers as a logged event and life goes on. In an attempt to tie this into the notification system, a while ago I added stuff to the wrap_exception decorator. I'm sure you've seen this nightmare scattered around the code: @exception.wrap_exception(notifier=notifier, publisher_id=publisher_id()) What started as a simple decorator now takes parameters and the code has become nasty. But it works ... no matter where the exception was generated, the notifier gets: * compute.host_id * method name * and whatever arguments the method takes. So, we know what operation failed and the host it failed on, but someone needs to crack the argument nut to get the goodies. It's a fragile coupling from publisher to receiver. I'm just wondering if we can get the notification message down to something more standardized, and avoid including the full argument list. That is one way to reduce the coupling. What is the minimum information we need to know when a failure occurs ? I think we have operation host it failed on, instance_id, migration_id (maybe) reservation_id, (maybe) security group id (maybe) If we can avoid cracking open the remaining arguments, a list this long might be manageable. One, less fragile, alternative is to put a try/except block inside every top-level nova.compute.manager method and send meaningful exceptions right from the source. More fidelity, but messier code. Although explicit is better than implicit keeps ringing in my head. I like explicit better than implicit, but I think we need to trigger off any and all exceptions to make all of this reliable. Or, we make a general event parser that anyone can use ... but again, the link between the actual method and the parser is fragile. The developers have to remember to update both. Opinions? -S ___ 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] Providing packages for stable releases of OpenStack
On Tue, Dec 6, 2011 at 10:11 AM, Duncan McGreggor dun...@dreamhost.com wrote: On 06 Dec 2011 - 14:28, Thierry Carrez wrote: So the general consensus so far on this discussion seems to be: (0) The 2011.3 release PPA bears false expectations and should be removed now. In the future, we should not provide such PPAs: 0-day packages for the release should be available from the last milestone PPA anyway. (1) OpenStack, as an upstream project, should focus on development rather than on providing a production-ready distribution. (2) We could provide daily builds from the stable/diablo branch for a variety of releases (much like what we do for the master branch), but those should be clearly marked not for production use and be best-effort only (like our master branch builds). (3) This should not prevent a group in the community from working on a project providing an openstack on Lucid production-ready distribution if they so wishes. This project would just be another distribution of OpenStack. This doesn't seem like enough to me. OpenStack isn't just a library; it's a fairly substantial collection of software and services, intended to be used as a product. If it can't be used as a product, what's the use? Someone made the suggestion that a new OpenStack group be started, one whose focus is on producing a production-ready, distribution-ready, release of the software. So can we add one more (need some help with wording, here...): (4) OpenStack will accept and foster a new project, one that is not focused on development, but rather the distribution and it's general stability. This distro project will be responsible for advocating on behalf of various operating systems/distros/sponsoring vendors for bugs that affect performance and stability of OpenStack, or prevent an operating system from running OpenStack. Thoughts? +1 on this idea - I think it has a lot of benefits in coordinating distro activity. mike ___ 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] Cloud Computing StackExchange site proposal
On Mon, Dec 5, 2011 at 11:44 AM, Stefano Maffulli stef...@openstack.org wrote: On Mon, 2011-12-05 at 09:51 +0100, Thierry Carrez wrote: AskBot (Python/Django, GPL) - http://askbot.com/ .. OSQA (Python) - http://www.osqa.net/ : No activity in the last 8 months Uhm... Jira activity is low http://jira.osqa.net/browse/OSQA but I see a few recent commits on trunk http://svn.osqa.net/changelog/OSQA/osqa/trunk. How did you base your estimate of 8 months inactivity? /stef Webfaction run osqa, as a replacement for their old forums. The support openid, as well as local logins. You can see it in action at http://community.webfaction.com/ mike ___ 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] Cloud Computing StackExchange site proposal
On Tue, Nov 29, 2011 at 2:35 AM, Thierry Carrez thie...@openstack.org wrote: Stefano Maffulli wrote: Leaving aside naming the tools, what would be the most important features to have? Here is my personal list, in no particular order: * good search engine * ability to promote question and best answer to FAQ * good looking and nice to use * custom domain (like ask.openstack.org) * layout customizable, to give it the openstack.org look * use Launchpad login * possibility to turn question into bug report (nice to have) anything else? Please focus on features, we'll shop around for tools at later stage. * Tagging * Use of a reputation system to encourage participation and get a better handle on authoritative answers * a method or process for flagging topics which should migrate into documentation and/or the wiki ___ 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 stuff
I like e).
I know it's heresy in some circles, but this approach can also support
the use of SqlAlchemy core, without the use of the SQLAlchemy ORM.
It's more work in some respects, but does allow writing very efficient
queries.
mike
On Tue, Nov 29, 2011 at 9:55 AM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
e) is the right solution imho. The only reason joinedloads slipped in is for
efficiency reasons.
In an ideal world the solution would be:
1) (explicitness) Every object or list of related objects is retrieved with
an explicit call:
instance = db.instance_get(id)
ifaces = db.interfaces_get_by_instance(id)
for iface in ifaces:
ip = db.fixed_ip_get_by_interface(iface['id'])
2) (efficiency) Queries are perfectly efficient and all joins that will be
used are made at once.
So the above would be a single db query that joins all instances ifaces and
ips.
Unless we're doing source code analysis to generate our queries, then we're
probably going
to have to make some tradeoffs to get as much efficiency and explicitness as
possible.
Brainstorming, perhaps we could use a hinting/caching mechanism that the
backend could support.
something like db.interfaces_get_by_instance(id, hint='fixed_ip'), which
states that you are about to make
another db request to get the fixed ips, so the backend could prejoin and
cache the results. Then the next
request could be: db.fixed_ip_get_by_interface(iface['id'], cached=True) or
some such.
I would like to move towards 1) but I think we really have to solve 2) or we
will be smashing the database with too many queries.
Vish
On Nov 29, 2011, at 7:20 AM, Soren Hansen wrote:
Hi, guys.
Gosh, this turned out to be long. Sorry about that.
I'm adding some tests for the DB api, and I've stumbled across something
that we should probably discuss.
First of all, most (if not all) of the various *_create methods we have,
return quite amputated objects. Any attempt to access related objects
will fail with the much too familiar:
DetachedInstanceError: Parent instance Whatever at 0x4f5c8d0 is not
bound to a Session; lazy load operation of attribute 'other_things'
cannot proceed
Also, with the SQLAlchemy driver, this test would pass:
network = db.network_create(ctxt, {})
network = db.network_get(ctxt, network['id'])
instance = db.instance_create(ctxt, {})
self.assertEquals(len(network['virtual_interfaces']), 0)
db.virtual_interface_create(ctxt, {'network_id': network['id'],
'instance_id': instance['id']}
self.assertEquals(len(network['virtual_interfaces']), 0)
network = db.network_get(ctxt, network['id'])
self.assertEquals(len(network['virtual_interfaces']), 1)
I create a network, pull it out again (as per my comment above), verify
that it has no virtual_interfaces related to it, create a virtual
interface in this network, and check the network's virtual_interfaces
key and finds that it still has length 0. Reloading the network now
reveals the new virtual interface.
SQLAlchemy does support looking these things up on the fly. In fact,
AFAIK, this is its default behaviour. We just override it with
joinedload options, because we don't use scoped sessions.
My fake db driver looks stuff like this up on the fly (so the
assertEquals after the virtual_interface_create will fail with that db
driver).
So my question is this: Should this be
a) looked up on the fly,
b) looked up on first key access and then cached,
c) looked up when the parent object is loaded and then never again,
d) or up to the driver author?
Or should we do away with this stuff altogether? I.e. no more looking up
related objects by way of __getitem__ lookups, and instead only allow
lookups through db methods. So, instead of
network['virtual_interfaces'], you'd always do
db.virtual_interfaces_get_by_network(ctxt, network['id']). Let's call
this option e).
I'm pretty undecided myself. If we go with option e) it becomes clear to
consumers of the DB api when they're pulling out fresh stuff from the DB
and when they're reusing potentially old results. Explicit is better
than implicit, but it'll take quite a bit of work to change this.
If we go with one of options a) through d), my order of preference is
(from most to least preferred): a), d), c), b).
There's value in having a right way and a wrong way to do this. If it's
either-or, it makes testing (as in validation) more awkward. I'd say
it's always possible to do on-the-fly lookups. Overriding __getitem__
and fetching fresh results is pretty simple, and, as mentioned earlier,
I believe this is SQLAlchemy's default behaviour (somebody please
correct me if I'm wrong). Forcing an arbitrary ORM to replicate the
behaviour of b) and c) could be incredibly awkward, and c) is also
complicated because there might be reference loops involved. Also,
reviewing correct use of something where the need
Re: [Openstack] Cloud Computing StackExchange site proposal
On Tue, Nov 29, 2011 at 11:54 AM, Stefano Maffulli stef...@openstack.org wrote: On Tue, 2011-11-29 at 10:14 -0800, Michael Pittaro wrote: * a method or process for flagging topics which should migrate into documentation and/or the wiki Sounds interesting. If I understand you correctly, you want to have a way to mark questions about topics that may be improved in the official docs. Would this be something like 'transform this question into a bug filed against the documentation project' or something different? Can you elaborate a bit more on the use case? How would this work? thanks, stef Maybe the anti-pattern I'm trying to avoid here is a better place to start :-) A lot of knowledge discovery happens on a QA site, as well as lists and forums. However, a common problem with those tools is where the all the knowledge ends up being scattered in those locations (and often replicated), and the real documentation and/or wiki never gets updated. ( This seems to be more common with lists and forums than QA sites.) This is compounded by the natural aging of a discussion or question - at some point, it's just no longer relevant. I think two pieces are required: 1) As you suggest, a way of flagging a question or discussion as a doc bug, a potential enhancement, or even a product bug. 2) A way of closing the loop, and updating the question to indicate the issue is resolved/fixed, and no longer relevant. The method I've used in the past is where the 'question' had a link to a one or more 'bugs', and when a 'bug' was fixed the 'question' got updated automatically. There are various ways to do this; I think the important point is just to close the knowledge loop in some way, and to avoid having to do it manually. mike ___ 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] Whats the process for devstack suggestions and bug reports
devstack is cool ! I'm wondering what the process for suggestions, enhancements and bug reports is ? Mike ___ 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] Whats the process for devstack suggestions and bug reports
thanks - I missed the launchpad project. On Fri, Nov 18, 2011 at 9:44 AM, Anthony Young sleepsonthefl...@gmail.comwrote: Hey Michael, There is a launchpad project here: https://launchpad.net/devstack From there you can submit blueprints and bug reports. We are in the process of moving the main repo from https://github.com/cloudbuilders/devstack to https://github.com/openstack-dev/devstack and gerrit, and that move should be complete by sometime next week. So soon you will be able to submit fixes and enhancements using the usual gerrit process. Anthony On Fri, Nov 18, 2011 at 9:27 AM, Michael Pittaro mik...@lahondaresearch.org wrote: devstack is cool ! I'm wondering what the process for suggestions, enhancements and bug reports is ? Mike ___ 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
