← Back to team overview

nova team mailing list archive

Re: nova class architecture/interaction diagram


On Mon, Oct 18, 2010 at 7:07 AM, Anne Gentle <anne@xxxxxxxxxxxxx> wrote:

> Wow, thanks Andy. I have a Mac so I can help with the graffle file if
> anyone has suggestions or edits, just write back to the list.

It's actually a bit more useful when opened in omnigraffle as it has layers
that can be turned on and off to specify different parts.

> How do you suggest we get this info onto the wiki or onto
> nova.openstack.org? Are there logical ways to divide the nova.png so that
> people can see it on one screen?

Not a whole lot, I think it is mostly a zoom-and-move thing, what I did plan
on doing was adding some larger sized labels so that is easy to visually
pick out where you want to go.

As for getting it on the wiki... technically OmniGraffle exports to SVG, but
I haven't looked into that too far. Ideally it could be somewhat
interactive. One thought I had for it was that it gave a good canvas to draw
operation flow examples, for example an admin request coming in that
broadcast's the upgrade command to all or a subsection of ComputeManagers
and what happens from there.

Once I finish writing up a couple mini-proposals regarding the rolling
upgrade procedures I'll revisit the diagram to add some of the features I
had in mind.

> I'll study this further tomorrow but wanted to send a quick note of
> appreciation.
> Anne
> **
> *Anne Gentle*
> anne@xxxxxxxxxxxxx
> <http://www.facebook.com/conversationandcommunity>
> my blog <http://justwriteclick.com/> | my book<http://xmlpress.net/publications/conversation-community/>|
> LinkedIn <http://www.linkedin.com/in/annegentle> | Delicious<http://del.icio.us/annegentle>|
> Twitter <http://twitter.com/annegentle>
> On Sun, Oct 17, 2010 at 2:18 AM, Andy Smith <andyster@xxxxxxxxx> wrote:
>> In researching a solution to give us reliable rolling upgrades it seemed
>> helpful to have an overview of the current layout of the code.
>> It is incomplete (missing objectstore, only begins to deal with the public
>> api side of things, no db interaction, somewhat haphazardly laid out), but I
>> think it is a good basis for a visual language to describe this stuff. I
>> looked at UML and call graph generation stuff prior to making it but nothing
>> really captured the various metaphors we're working with.
>> It's a graffle file (and an exported png) so tough to update without a
>> mac, but I would be happy to hear people's thoughts.
>> http://term.ie/data/nova.graffle
>> http://term.ie/data/nova.png
>> --andy
>> _______________________________________________
>> Mailing list: https://launchpad.net/~nova <https://launchpad.net/%7Enova>
>> Post to     : nova@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~nova <https://launchpad.net/%7Enova>
>> More help   : https://help.launchpad.net/ListHelp