Re: [Openstack] Cloud Computing StackExchange site proposal

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

[Openstack] Reminder: OpenStack team meeting - 21:00 UTC

Hello everyone, Our general meeting will take place at 21:00 UTC this Tuesday in #openstack-meeting on IRC. PTLs, if you can't make it, please name a substitute on [2]. We will look at general progress towards essex-2, improving visibility over the global Essex plans and the status of the client

[Openstack] Database stuff

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 r

Re: [Openstack] Database stuff

Soren: On Nov 29, 2011, at 10:20 AM, Soren Hansen wrote: [snip] > > 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

Re: [Openstack] Database stuff

On Tue, 2011-11-29 at 16:20 +0100, Soren Hansen wrote: > > It seems I've talked myself into preferring option e). It's too much > work to do on my own, though, and it's going to be disruptive, so we > need to do it real soon. I think it'll be worth it, though. I agree. This will also make it eas

Re: [Openstack] Database stuff

Hey Soren, On Nov 29, 2011, at 7:20 AM, Soren Hansen wrote: > 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 t

Re: [Openstack] Database stuff

I think option e is our best bet. It's the *only* option if we want to efficiently separate our services (as Jason has pointed out). Waldon On Nov 29, 2011, at 10:52 AM, Devin Carlen wrote: > Hey Soren, > > On Nov 29, 2011, at 7:20 AM, Soren Hansen wrote: > >> SQLAlchemy does support looking

Re: [Openstack] Database stuff

On Tue, 2011-11-29 at 16:20 +0100, Soren Hansen wrote: > It seems I've talked myself into preferring option e). It's too much > work to do on my own, though, and it's going to be disruptive, so we > need to do it real soon. I think it'll be worth it, though. (e) sounds right to me. But hopefully d

Re: [Openstack] openstack Diablo Installation manual [Simplified Chinese]

HelloOn Tue, 2011-11-29 at 11:29 +0800, darkfower wrote: > I come from China，In my spare time I wrote a openstack > Diablo version of the simplified Chinese installation > documentation,Hope to Chinese friends have help That's really good news! Which manual did you translate exactly? Can

Re: [Openstack] Database stuff

e) sounds good as long as we don't remove the ability to joinload up front. Sometimes we need to join. Sometimes we can be lazy. With 'list instances with details', we need to get all instances from the DB and join network information in a single DB query. Doing 1 + (n*x) DB queries to suppo

Re: [Openstack] Database stuff

I'm really glad to hear all these votes for e), 'cause that's what I'd like to see too :-) d On 29 Nov 2011 - 11:18, Brian Waldon wrote: > I think option e is our best bet. It's the *only* option if we want to > efficiently separate our services (as Jason has pointed out). > > Waldon > > > On Nov

Re: [Openstack] Database stuff

For this I think we need to separate the models from the queries. A query method should be able to populate as many of the models as needed to return the data collected. I also think separating the queries from the models themselves will help us make the storage engine replaceable, and will allo

Re: [Openstack] Database stuff

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

[Openstack] Proposal for Lorin Hochstein to join nova-core

Lorin has been a great contributor to Nova for a long time and has been participating heavily in reviews over the past couple of months. I think he would be a great addition to nova-core. Vish ___ Mailing list: https://launchpad.net/~openstack Post to

[Openstack] Proposal for Mark McLoughlin to join nova-core

Mark is maintaining openstack for Fedora and has made some excellent contributions to nova. He has also been very prolific with reviews lately. Lets add him to core and make his reviews count towards potential merges! Vish ___ Mailing list: https://la

Re: [Openstack] Cloud Computing StackExchange site proposal

On Fri, Nov 18, 2011 at 10:38 AM, Anne Gentle wrote:> We had put forward an OpenStack StackExchange proposal earlier this year> which was rejected Hi Anne, Where do I find this previous discussion? Thank you, Lloyd ___ Mailing list: https://launchpad

Re: [Openstack] OpenStack Security Group Extension Prohibits same group source in rules

+1. This sounds like a bug. FYI there are some issues related to adding source group rules that specify ports that need to be fixed. We have also discussed whether or not the same group should be allow all by default. In ec2 it does. I personally like having it explicit like this, but I don't

Re: [Openstack] Cloud Computing StackExchange site proposal

On Tue, Nov 29, 2011 at 2:35 AM, Thierry Carrez 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

Re: [Openstack] boot from ISO

Hi Donal, hi all, I'm trying to test the Boot From ISO feature. So I've set a XenServer host and installed a Ubuntu 11.10 PV DomU in it. Then I used the following commands but, as you can see in the attached nova-compute log excerpt, there was a problem. glance add name=fedora_iso disk_form

Re: [Openstack] Database stuff

On Tue, Nov 29, 2011 at 10:49 AM, Jason Kölker wrote: > On Tue, 2011-11-29 at 16:20 +0100, Soren Hansen wrote: >> >> It seems I've talked myself into preferring option e). It's too much >> work to do on my own, though, and it's going to be disruptive, so we >> need to do it real soon. I think it'l

Re: [Openstack] Database stuff

+10 On Tue, Nov 29, 2011 at 12:55 PM, Vishvananda Ishaya 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

Re: [Openstack] Database stuff

On 29 Nov 2011 - 17:54, Aaron Lee wrote: > For this I think we need to separate the models from the queries. +1 > A query method should be able to populate as many of the models as > needed to return the data collected. I also think separating the > queries from the models themselves will help us

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 wrote: >

Re: [Openstack] Proposal for Lorin Hochstein to join nova-core

+1 On Nov 29, 2011, at 1:03 PM, Vishvananda Ishaya wrote: > Lorin has been a great contributor to Nova for a long time and has been > participating heavily in reviews over the past couple of months. I think he > would be a great addition to nova-core. > > Vish > __

Re: [Openstack] Proposal for Lorin Hochstein to join nova-core

+1 - Brian Schott, CTO Nimbis Services, Inc. brian.sch...@nimbisservices.com ph: 443-274-6064 fx: 443-274-6060 On Nov 29, 2011, at 1:03 PM, Vishvananda Ishaya wrote: > Lorin has been a great contributor to Nova for a long time and has been >

Re: [Openstack] Proposal for Mark McLoughlin to join nova-core

+1 On Nov 29, 2011, at 1:05 PM, Vishvananda Ishaya wrote: > Mark is maintaining openstack for Fedora and has made some excellent > contributions to nova. He has also been very prolific with reviews lately. > Lets add him to core and make his reviews count towards potential merges! > > Vish >

Re: [Openstack] Proposal for Lorin Hochstein to join nova-core

+1 Lorin if you are also interested in being a nova-doc or doc-core member please let me know! On Tue, Nov 29, 2011 at 12:03 PM, Vishvananda Ishaya wrote: > Lorin has been a great contributor to Nova for a long time and has been > participating heavily in reviews over the past couple of months.

Re: [Openstack] Proposal for Lorin Hochstein to join nova-core

+1 -Original Message- From: "Vishvananda Ishaya" Sent: Tuesday, November 29, 2011 1:03pm To: "openstack (openstack@lists.launchpad.net)" Subject: [Openstack] Proposal for Lorin Hochstein to join nova-core Lorin has been a great contributor to Nova for a long time and has been participa

Re: [Openstack] Database stuff

+1 on the thoughts here. Exactly what I meant by my reply. Not sure what the interface should look like for #2, but we must be able to do it somehow. - Chris On Nov 29, 2011, at 11:55 AM, Vishvananda Ishaya wrote: > e) is the right solution imho. The only reason joinedloads slipped in is for

[Openstack] Lloyd Learning Docs & website content processes

I had a good call with Anne Gentle a few hours ago, 08:00 PT, and got a first introduction to the fantastic documentation work, and infrastructure to support it. There is a lot for me to get up to speed on, and Anne has generously agreed to continue to mentor me. We'll have another one-on-one call

Re: [Openstack] Proposal for Mark McLoughlin to join nova-core

Yeah, been noticing this too and thinking about nominating him. +1 from me! - Chris On Nov 29, 2011, at 12:05 PM, Vishvananda Ishaya wrote: > Mark is maintaining openstack for Fedora and has made some excellent > contributions to nova. He has also been very prolific with reviews lately. > L

Re: [Openstack] Cloud Computing StackExchange site proposal

The options have been discussed on the OpenStack mailing list at length and the forums.openstack.org was the one chosen by consensus. Here's part of the thread: https://lists.launchpad.net/openstack/msg02169.html and you can read more archives there as well. We also requested a new site from Stack

Re: [Openstack] Database stuff

2011/11/29 Vishvananda Ishaya : > 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.i

Re: [Openstack] Cloud Computing StackExchange site proposal

On Tue, 2011-11-29 at 10:10 -0800, Lloyd Dewolf wrote: > Where do I find this previous discussion? around here: https://lists.launchpad.net/openstack/msg02169.html What do you think of the requirements we're gathering for the Q&A system? I'd like your opinion on that as we move on. thanks stef

Re: [Openstack] Database stuff

2011/11/29 Chris Behrens : > e) sounds good as long as we don't remove the ability to joinload up > front.  Sometimes we need to join.  Sometimes we can be lazy.  With > 'list instances with details', we need to get all instances from the > DB and join network information in a single DB query.  Doi

Re: [Openstack] Database stuff

Inline On Nov 29, 2011, at 11:16 AM, Soren Hansen wrote: > 2011/11/29 Vishvananda Ishaya : >> 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 rela

Re: [Openstack] Cloud Computing StackExchange site proposal

It was here: http://area51.stackexchange.com/proposals/31788 It was rejected on the grounds of being able to be covered on StackOverflow and ServerFault. Vish On Nov 29, 2011, at 10:10 AM, Lloyd Dewolf wrote: > On Fri, Nov 18, 2011 at 10:38 AM, Anne Gentle > wrote:> We had put forward an Ope

Re: [Openstack] openstack Diablo Installation manual [Simplified Chinese]

Great, thanks for your contribution! I am guessing that you did not translate but wrote an independent one, that's fine with us. I've worked with FLOSS Manuals, an open source documentation community, where we would encourage new content in another language and not consider English to be the only s

[Openstack] Documentation translations

Hi all, As a follow-up to the interest in simplified Chinese manuals, I would also like to experiment with English-as-source translations. I had been delaying a "frozen" set of English source files but I think we could just pick a date and start translating if there is enough interest and we identi

Re: [Openstack] Database stuff

2011/11/29 Vishvananda Ishaya : > On Nov 29, 2011, at 11:16 AM, Soren Hansen wrote: >> The way I'd attack these expensive-if-done-one-at-a-time-but-dirt-cheap- >> if-done-as-one-big-query is to have a method in the generic layer that >> is taylored for this use case. E.g. >> >> def instances_get_al

Re: [Openstack] Database stuff

On 29 Nov 2011 - 13:15, Jay Pipes wrote: > On Tue, Nov 29, 2011 at 10:49 AM, Jason K??lker > wrote: > > On Tue, 2011-11-29 at 16:20 +0100, Soren Hansen wrote: > >> > >> It seems I've talked myself into preferring option e). It's too much > >> work to do on my own, though, and it's going to be dis

Re: [Openstack] Cloud Computing StackExchange site proposal

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 of

Re: [Openstack] Database stuff

2011/11/29 Jay Pipes : > There's a very good reason this hasn't happened so far: handling > highly relational datasets with a non-relational data store is a bad > idea. In fact, I seem to remember that is exactly how Nova's data > store started out life (*cough* Redis *cough*) To be fair, we're on

Re: [Openstack] Database stuff

On Tue, Nov 29, 2011 at 2:58 PM, Soren Hansen wrote: > 2011/11/29 Jay Pipes : >> There's a very good reason this hasn't happened so far: handling >> highly relational datasets with a non-relational data store is a bad >> idea. In fact, I seem to remember that is exactly how Nova's data >> store st

Re: [Openstack] Database stuff

On Nov 29, 2011, at 11:55 AM, Vishvananda Ishaya wrote: … some stuff I agree with, then... > something like db.interfaces_get_by_instance(id, hint='fixed_ip'), This is very similar to ActiveRecord. In a case like this you would say Instance.find(id, :include => :fixed_ip) If you are includin

Re: [Openstack] [nova-testing] Efforts for Essex

It's been a bit over a week since I started this thread. So far we've agreed that running the test suite is too slow, mostly because there are too many things in there that aren't unit tests. We've also discussed my fake db implementation at length. I think we've generally agreed that it isn't com

Re: [Openstack] Proposal for Lorin Hochstein to join nova-core

+1 On Tue, Nov 29, 2011 at 1:03 PM, Vishvananda Ishaya wrote: > Lorin has been a great contributor to Nova for a long time and has been > participating heavily in reviews over the past couple of months.  I think he > would be a great addition to nova-core. > > Vish > ___

Re: [Openstack] Database stuff

2011/11/29 Jay Pipes : > On Tue, Nov 29, 2011 at 2:58 PM, Soren Hansen wrote: >> 2011/11/29 Jay Pipes : >>> There's a very good reason this hasn't happened so far: handling >>> highly relational datasets with a non-relational data store is a bad >>> idea. In fact, I seem to remember that is exactl

Re: [Openstack] Cloud Computing StackExchange site proposal

Thanks Vish. Now my failed search makes more sense. Awesome how they delete it -- invitation to resubmit every month, jokes. On Tue, Nov 29, 2011 at 11:35 AM, Vishvananda Ishaya wrote: > It was here: > http://area51.stackexchange.com/proposals/31788 > It was rejected on the grounds of being able

Re: [Openstack] Database stuff

On Tue, Nov 29, 2011 at 3:43 PM, Soren Hansen wrote: > 2011/11/29 Jay Pipes : >>> Besides, we don't really use transactions. I could easily read the >>> same data from two separate nodes, make different (irreconcilable) >>> changes on both nodes, and write them back, and the last one to write >>>

Re: [Openstack] Database stuff

2011/11/29 Jay Pipes : > On Tue, Nov 29, 2011 at 3:43 PM, Soren Hansen wrote: >> 2011/11/29 Jay Pipes : Besides, we don't really use transactions. I could easily read the same data from two separate nodes, make different (irreconcilable) changes on both nodes, and write them back, a

Re: [Openstack] boot from ISO

Off the top of my head, I'd look to see if the compute node can see that ISO SR. DL From: Michaël Van de Borne [mailto:michael.vandebo...@cetic.be] Sent: 29 November 2011 18:15 To: Donal Lafferty; openstack@lists.launchpad.net Subject: Re: [Openstack] boot from ISO Hi Donal, hi all, I'm trying

Re: [Openstack] Proposal for Mark McLoughlin to join nova-core

+1 -Original Message- From: "Vishvananda Ishaya" Sent: Tuesday, November 29, 2011 1:05pm To: "openstack (openstack@lists.launchpad.net)" Subject: [Openstack] Proposal for Mark McLoughlin to join nova-core Mark is maintaining openstack for Fedora and has made some excellent contribu

[Openstack] openstack.common module (was: Re: [RFC] Common config options module)

On Mon, 2011-11-28 at 20:57 +, Mark McLoughlin wrote: > Hi Jason, > > On Mon, 2011-11-28 at 10:24 -0600, Jason Kölker wrote: > > On Mon, 2011-11-28 at 08:06 -0800, Monty Taylor wrote: > > > > The idea is to unify option handling across projects with this new API. > > > > The module would even

[Openstack] development document: how to write a filter module to swift

http://wiki.openstack.org/development/swift/filter it's not perfect but i think this can help some people at the beginning. if someone can help me to move this document to Swift Developer Documentation i will say thank you. __

[Openstack] some of my understand of swift object replication (chinese and english)

1。 当 proxy 传输成功节点数量 只有 2 的时候， 谁去补全第三个节点？ 怎么补的？ when there is just 2 object server transfer success, who will fill up the failed one?how? 如果只有三个节点， 两个挂了， 写入失败 if there are 3 object server, 2 node failed, upload fail. 如果只有三个节点， 一个挂了， 三次写入都成功， 另一次失败的写入会被 proxy 转写到 另外的两个节点中的一个， 由于 partition 不同， 所以虽

Re: [Openstack] Cloud Computing StackExchange site proposal

On Tue, Nov 29, 2011 at 11:54 AM, Stefano Maffulli 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

Re: [Openstack] Cloud Computing StackExchange site proposal

On Tue, 2011-11-29 at 16:06 -0800, Michael Pittaro wrote: > A lot of knowledge discovery happens on a Q&A 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 r

Re: [Openstack] Cloud Computing StackExchange site proposal

On Tue, Nov 29, 2011 at 11:16 AM, Stefano Maffulli wrote: > On Tue, 2011-11-29 at 10:10 -0800, Lloyd Dewolf wrote: >> Where do I find this previous discussion? > > around here: > https://lists.launchpad.net/openstack/msg02169.html > > What do you think of the requirements we're gathering for the Q

[Openstack] Meetup in Seattle 11/30, 6:30pm at Opscode HQ

Seattle Area Stackers, We're having an informal meetup at the Opscode HQ (http://www.opscode.com/about/#contact) tomorrow. Rob __ Rob Hirschfeld Principal Cloud Solution Architect Dell | Cloud Edge, Data Center Solutions blog robhirschfeld.com, twitter @zehicle _

Re: [Openstack] [nova-testing] Efforts for Essex

Hi folks >Jay Thank you for your pointing this!:) Hey OpenStackers,please help forward-porting :P >Soren >Anything else around unit testing anyone wants to get into The Great Big Plan[tm]? And also, we should have a policy for unit test. Something like this - New code should have a concrete spe

Re: [Openstack] Proposal for Mark McLoughlin to join nova-core

+1 On 11/29/2011 02:12 PM, Dan Prince wrote: > +1 > > > > -Original Message- > From: "Vishvananda Ishaya" > Sent: Tuesday, November 29, 2011 1:05pm > To: "openstack (openstack@lists.launchpad.net)" > > Subject: [Openstack] Proposal for Mark McLoughlin to join nova-core > > Mark is m

[Openstack] How to using keystone with ldap

Now I according to keystone/test/etc/ldap.conf.template to set ldap configuration in my keystone.conf But I have no idea that wich dn in ldap keystone used and there is no dn in keystone.ldif . How to set it? Anyone using keystone with ldap can help me? -- 非淡薄无以明志，非宁静无以致远 ___