nova team mailing list archive
Mailing list archive
Re: Nova Installation and Projects
I've moved the "easy" items to blueprints here:
Note that they are tagged with 'austin' release series (which is
the first cycle up until November) and also the low-hanging-fruit
For blueprints that only had a one-line description, I pasted it into
the summary. For example:
For longer items, I linked to a new etherpad:
I think this should work well since we can keep everything listed in
one place (who, what, dependencies, ...), but have the flexibility
of collaborative design through the etherpad spec URLs when
I'll go through and convert the rest of the items this afternoon.
If there are any new items folks want to put on the TODO (whether
they are large or small, need to be done now or later), just create
a quick blueprint for them so no one forgets. :) As new developers
try to get involved, having a long list of easy items is great since
it gives them a productive reason to start looking at code.
On Mon, Aug 02, 2010 at 10:22:51AM -0700, Vishvananda Ishaya wrote:
> I'm aware that the blueprints are for this, but i find the blueprint
> whiteboards very annoying for collaborative discussion. The idea was to
> get everything into the etherpad and move them to blueprints as they
> solidify. That said, there is quite a bit of basic info on there so If
> you want to start moving stuff over, feel free.
> On Mon, Aug 2, 2010 at 10:10 AM, Eric Day <eday@xxxxxxxxxxxx> wrote:
> The tasks that you guys wrote out in the etherpad are exactly
> what the Blueprints are meant for. If no one objects, I am
> going to transfer those to blueprints so we can track them
> with dates and dependencies. We can also link to wiki pages
> for more details like you were going to as items shape up
> (http://wiki.openstack.org/BluePrints). We can also assign folks to
> blueprints to get summaries of who's doing what as well.
> On Sat, Jul 31, 2010 at 03:37:38PM -0700, Vishvananda Ishaya wrote:
> > Hey Guys,
> > I'd really like to streamline the install process in the wiki The
> code is
> > changing very rapidly, but it is a large barrier of entry for
> people new
> > to the community. There is a wiki page for getting to the point
> > unit tests run and you can actually run the workers under OSX (fake
> > virutalization) or Ubuntu. The simple instructions are here:
> > http://wiki.openstack.org/InstallationNova20100729
> > I'd like to add some more for the easiest process to actually
> running a vm
> > (on Ubuntu only at the moment) and ssh-ing in from the various
> > as well. Please correct any errors, or simplify the instructions
> if you
> > see improvements.
> > It would be great to have the equivalent for installing from the
> ppa now
> > that we are actually building packages.
> > - how to add the ppa # we need to make sure redis2.0, newer
> libvirt, and
> > patched python-twisted are in the ppa
> > - installing packages
> > - creating users
> > - getting credentials
> > - running a system and logging in.
> > I also want to start putting together a list of things that need to
> > coded. It can be a grab bag for developers that want to help but
> > have a specific bug/feature to work on. I've created an etherpad
> for that
> > purpose here:
> > http://etherpad.openstack.org/hyrdG8yTl5
> > Please contribute ideas. We can move it to the wiki once we have
> > dumped everything.
> > We're making some excellent progress, lets keep it up!
> > _______________________________________________
> > Mailing list: https://launchpad.net/~nova
> > Post to : nova@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~nova
> > More help : https://help.launchpad.net/ListHelp