nova-network team mailing list archive

[Dan Wendlandt <dan@xxxxxxxxxx>]

Weekly meetings can be good as a forcing function, but given that we
already have the main openstack meeting to hopefully provide that facility,
I think a few emails to the nova-network list are probably sufficient to
keep the team up-to-date.

Maybe target sending out the list of currently targeted nova-network
related blueprints + bugs near the beginning of a milestone to help people
identify potential conflicts, then help people be aware of pending reviews
as the milestone winds down?

Dan


On Mon, Nov 14, 2011 at 6:11 PM, Matt Dietz <matt.dietz@xxxxxxxxxxxxx>wrote:

>  Looks good. I've made some updates to the etherpad based on what I know
> or have been working on.
>
>  Huge win on the melange stuff, IMO
>
>  I'm –1 on the idea of weekly meeting: I like to pretend everyone is
> going to be communicative without coaxing. I'm usually in the minority with
> that opinion, however.
>
>   From: Trey Morris <trey.morris@xxxxxxxxxxxxx>
> Date: Mon, 14 Nov 2011 18:19:03 -0600
> To: <nova-network@xxxxxxxxxxxxxxxxxxx>
> Subject: [Nova-network] organization
>
>  Team,
>
> I'd like to get a general status from the parties working on networking in
> nova to help prevent conflict and attempt to determine the legion of
> network related goals. I've created an etherpad so this information doesn't
> get lost in the email storm:
> http://etherpad.openstack.org/nova-network-team. If everyone can keep it
> at least somewhat up to date I think it will help tremendously with
> information sharing. I've already added my current short term goals. Dan,
> Brad, Troy: I think it would be fantastic to have the sections for quantum
> and melange populated with status information useful from a nova point of
> view.
>
> The most recent big networking news is merging melange with nova being
> second thought-ed, and as a result melange has become its own openstack
> project. This has led to obsoletion of several melange related nova-network
> blueprints. I've discussed this with Troy Toman and I will be
> updating/removing these blueprints to that effect soon.
>
> https://blueprints.launchpad.net/~nova-network
> I believe I have captured most of the networking blueprints and had them
> assigned to the nova-network team. Vish had the idea of setting the
> "drafter" field to nova-network thereby keeping the blueprint editable and
> easily viewable by the nova-network team after it has been assigned to
> someone on the team or otherwise. If I've missed any blueprints or as new
> blueprints are created, please update them and set the "drafter" to
> nova-network.
>
> Weekly meeting: useful? Not? Other thoughts?
>
>
> -tr3buchet
> -- Mailing list: https://launchpad.net/~nova-network Post to :
> nova-network@xxxxxxxxxxxxxxxxxxx Unsubscribe :
> https://launchpad.net/~nova-network More help :
> https://help.launchpad.net/ListHelp
>
> --
> Mailing list: https://launchpad.net/~nova-network
> Post to     : nova-network@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~nova-network
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira Networks: www.nicira.com
twitter: danwendlant
~~~~~~~~~~~~~~~~~~~~~~~~~~~