[Openstack] Announcing the OpenStack Dashboard

Hello all, I'd like to take this opportunity to formally announce the OpenStack Dashboard. It's been available on Launchpad for a little while now so I could gather a bit of initial feedback about it. Enough people have played with it and found it useful that it makes sense to unveil it to a

Re: [Openstack] Using useful commit messages while merging code into trunk

Sorry, that was my useless commit message, based on the message from Vish to the list yesterday - not enough context provided! Will not happen again, I promise. :) Anne * * *Anne Gentle* my blog | my book

Re: [Openstack] Using useful commit messages while merging code into trunk

On Sat, Feb 26, 2011 at 1:17 PM, Christian Berendt wrote: > We should always set a correct commit message in the merge propsal and > we should don't merge code with useless commit messages. ++ :) -jay ___ Mailing list: https://launchpad.net/~openstack

[Openstack] Using useful commit messages while merging code into trunk

Hi. Sometimes there are very useless commit messages after merging a propsal into trunk. Example: " 748. Did a pull from trunk to be sure I had the latest, then deleted the test directory. I guess it appeared when I started using venv. Doh. (detail)" or my own: " 747. reverted my changes from

Re: [Openstack] Working on fixing code after a review? Please mark merge proposal Work In Progress!

On Fri, Feb 25, 2011 at 11:07 PM, Ewan Mellor wrote: > This is all great stuff Jay, but it's going to get lost if it's just in > email.  http://wiki.openstack.org/LifeWithBzrAndLaunchpad has some of this > on, but it's nothing like as clear and succinct as you've got it below. Cheers. > Could

Re: [Openstack] multi_nic and mac addresses

I think that new table for NIC mac addresses is good idea, but we need in table not only instance id, but network id for interface too. It will be good for implementation multi-nic in libvirt for example. ___ Mailing list: https://launchpad.net/~openstack

Re: [Openstack] Working on fixing code after a review? Please mark merge proposal Work In Progress!

2011/2/25 Salvatore Orlando : > I realized my previous mail was a bit unclear... > > I meant to say "can we avoid showing branches which are proposed to merge > into something different than lp:nova?" Sure. On lp:nova's page[1], it says: 34 branches proposed for merging into this one. "34 branche