OpenStack Compute (nova)

Code review comment for lp:~nii/nova/nova-deployment-tool

nova-deployment-tool
Merge into trunk

Revision history for this message

Shigetoshi Yokoyama (yoko) wrote on 2011-01-13:

> > I don't really see a problem with it going into contrib. We don't
> > really have a good other location for items like this.
>
> I believe we do. It's called "outside".
>
> If people can check out trunk and find 7 different sets of deployment tools,
> none of which work, because none of them are kept up-to-date, everybody loses.
> The user wanting use install and run Nova doesn't get what they want, and we
> potentially lose a new user. If people want to get stuff into our trunk, they
> have to commit to keeping it up-to-date. Getting a nova-core person to vouch
> for that commitment guarantees that someone who actively follows what goes on
> in trunk every day looks after it.
>
> A quick glance at this tool reveals that it's already out of date. It's still
> referencing a bunch of libvirt templates that no longer exist, and the one
> that remains isn't installed where this tool expects it to. I don't blame the
> author, because this project moves so fast, it's really, really hard to keep
> this stuff up-to-date.

I have a commitment to make the code up-to-date when we release for Bexar. So,
I am expecting to be very tough days just before 3rd of Mar. As Soren says, I
think it's really, really hard to keep this stuff up-to-date anytime, even after
the release.

However, I believe that if it is up-to-date to the release version,
tools 'inside' the release makes sense in terms of user benefits. We should
inform aim of tool by which users can know which is fit to their needs.

I did not know any other ways than to follow the procedure, which I was taught,
in order to contribute to the community.

1) Write a Blueprint
2) Present it at the developer conference
3) Get an Approval to it
4) Upload codes
5) Propose merge to trunk by 6th of Jan.
6) Get an Approval to it

I am now asking Todd to become a volunteer following Sore's advice. Please
help me to find a way to contribute the code for openstack users' value.

I was thinking that the tool would make installation easier and help everybody
wins. -- yoko

> > I don't really see a problem with it going into contrib. We don't
> > really have a good other location for items like this.
> 
> I believe we do. It's called "outside".
> 
> If people can check out trunk and find 7 different sets of deployment tools,
> none of which work, because none of them are kept up-to-date, everybody loses.
> The user wanting use install and run Nova doesn't get what they want, and we
> potentially lose a new user. If people want to get stuff into our trunk, they
> have to commit to keeping it up-to-date. Getting a nova-core person to vouch
> for that commitment guarantees that someone who actively follows what goes on
> in trunk every day looks after it.
> 
> A quick glance at this tool reveals that it's already out of date. It's still
> referencing a bunch of libvirt templates that no longer exist, and the one
> that remains isn't installed where this tool expects it to. I don't blame the
> author, because this project moves so fast, it's really, really hard to keep
> this stuff up-to-date.

I have a commitment to make the code up-to-date when we release for Bexar. So,
I am expecting to be very tough days just before 3rd of Mar. As Soren says, I 
think it's really, really hard to keep this stuff up-to-date anytime, even after 
the release.

However, I believe that if it is up-to-date to the release version,
tools 'inside' the release makes sense in terms of user benefits. We should 
inform aim of tool by which users can know which is fit to their needs.

I did not know any other ways than to follow the procedure, which I was taught, 
in order to contribute to the community.

1) Write a Blueprint
2) Present it at the developer conference
3) Get an Approval to it
4) Upload codes
5) Propose merge to trunk by 6th of Jan.
6) Get an Approval to it

I am now asking Todd to become a volunteer following Sore's advice. Please 
help me to find a way to contribute the code for openstack users' value.

I was thinking that the tool would make installation easier and help everybody
wins.  -- yoko

« Back to merge proposal