On 10/12/2011 07:55 PM, Mark Nottingham wrote:
The duplication of effort can be solved by having an intermediary do the translation. Repose already does this.
That's where there be dragons. Inferring that the user wants to go to version N of the
Sure
Just here :)
http://docs.openstack.org/
Le 13 oct. 2011 à 08:09, l jv a écrit :
hi
Is there anyone have some doc of openstack?
thanks :)
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Hi James,
On Wed, 2011-10-12 at 13:58 -0400, James E. Blair wrote:
Mark McLoughlin mar...@redhat.com writes:
Hey,
I've posted a proposal for how the stable branch could work here:
http://wiki.openstack.org/StableBranch
and a proposed diablo branch for nova:
If you are reffering to the Python client
(https://github.com/cloudbuilders/openstackx), the only thing I've found so far
is that the project is now officially the python-novaclient :
https://github.com/rackspace/python-novaclient
Will this help you ?
Le 13 oct. 2011 à 09:25, l jv a écrit :
？
Stefano Maffulli wrote:
The UDS is also the model for OpenStack Developer Summit and
participating to it would be a good occasion to learn how they run it.
Note that we made a few improvements to the UDS model over time:
- Have 25min sessions for small topics to keep the event within 3 days
Stefano Maffulli wrote:
I got lots of interesting responses in private email. I put a page up on
the wiki and I'll mention it in this week newsletter.
http://wiki.openstack.org/AcademicInitiative
in order to move the initiative forward we'll need a coordinator and a
more stable point
* Mark McLoughlin (mar...@redhat.com) wrote:
On Wed, 2011-10-12 at 13:58 -0400, James E. Blair wrote:
Mark McLoughlin mar...@redhat.com writes:
Anyone can propose a cherry-pick to the maintainers. This helps ensure
that the maintainers don't miss anything. To catch the maintainers
Hi,
This is a great idea. I feel this would create a good Openstack
ecosystem. Count me in as co-ordinator.
Regards,
Prem
On Tue, Oct 11, 2011 at 9:34 PM, Stefano Maffulli stef...@openstack.orgwrote:
hello folks,
a group of people interested in academia met in Boston during the
Chris Wright chr...@sous-sol.org writes:
* Mark McLoughlin (mar...@redhat.com) wrote:
On Wed, 2011-10-12 at 13:58 -0400, James E. Blair wrote:
Mark McLoughlin mar...@redhat.com writes:
Anyone can propose a cherry-pick to the maintainers. This helps ensure
that the maintainers don't miss
Hello everyone,
With release and design summit duties I had to pause my Nova bug
triaging activities, which resulted in a rather dramatic surge in
untriaged bugs, as evidenced by the following graph:
http://webnumbr.com/untouched-nova-bugs
Nova is not the only core project affected though:
On Thu, 2011-10-13 at 09:16 -0400, James E. Blair wrote:
Chris Wright chr...@sous-sol.org writes:
* Mark McLoughlin (mar...@redhat.com) wrote:
On Wed, 2011-10-12 at 13:58 -0400, James E. Blair wrote:
Mark McLoughlin mar...@redhat.com writes:
Anyone can propose a cherry-pick to the
OK, thanks. I guess that was a problem I was going to run into next. But
how do you generate the EC2_* shell variables that euca tools need when
using keystone? With the old nova auth this was done with 'nova-manage
project zipfile' but that does not work with keystone because there are
no
Hi,
We're using modified novarc generated by nova-manage without keystone.
I'm not sure that nova-manage works well with keystone but parhaps it can't.
So we registered some users and credentials to keystone, and modified EC_*
variables in novarc to fit them.
I think that we have to make
Hey all,
There were many exciting and productive conversations around packaging
and the role of OpenStack as an upstream entity in producing distro
packages. Turns out, the general consensus was that the project was
spending a bunch of effort to produce packages that no one was using or
really
14 matches
Mail list logo
