I see very little under Mendeley on OpenStack. Linking these two up may help in
this area.
Also, anyone have ins at Internet2? Seems like it would be a good fit.
verba volant, scripta manent
Sent from my cloud edge device
On 2011-10-13, at 5:49 AM, Prem Sankar G premsan...@gmail.com wrote:
On Thu, Oct 13 2011, Monty Taylor wrote:
If you'd like to give it a spin, do:
pip install git-review
And continue using git review to submit changes as usual. There is a
current outstanding bug (thanks setuptools!) in that man pages do not
get properly installed when installing via pip
Anybody have any contacts with the NSF FutureGrid project:
https://portal.futuregrid.org/
It looks like adding support for OpenStack is already on their todo list:
* https://portal.futuregrid.org/projects/83
* https://portal.futuregrid.org/openstack-futuregrid
Also, is anybody from OpenStack
*Hi Vish,*
In our openstack deployment we observe this:
Since linux_net.py/initialize_gateway_device() does this
# NOTE(vish): If the public interface is the same as the
# bridge, then the bridge has to be in promiscuous
# to forward packets properly.
On Fri, Oct 14 2011, James E. Blair wrote:
Another idea though is to add a small dotfile into each repository
indicating the canonical location of that repo's gerrit. Unlike storing
an entire tool like rfc.sh in the repo, it seems that just adding that
bit of static data to the repo seems
I'd much prefer storing data in git config rather than in a dot file.
On Oct 14, 2011, at 7:33 AM, Julien Danjou wrote:
On Fri, Oct 14 2011, James E. Blair wrote:
Another idea though is to add a small dotfile into each repository
indicating the canonical location of that repo's gerrit.
On Fri, Oct 14 2011, John Dickinson wrote:
I'd much prefer storing data in git config rather than in a dot file.
A dot file is commit-able. Git config is not.
So in this case, providing the dot file wins. Think about like a
.gitignore file.
--
Julien Danjou
// eNovance
Hi all. I'm trying to set up a Dashboard with my nova instalation (Diablo)
and I'm getting some errors.
My environment:
Ubuntu 11.04 Server 64
OpenStack: ppa:openstack-release/2011.3
Keystone: ppa:keystone-core/trunk
Swift: ppa:swift-core/ppa
Dashboard: https://github.com/4P/openstack-dashboard
But it's metadata about the code (a particular review pattern with a particular
vcs). VCS info does not belong in the code. I'll admit that I like a dotfile in
the repo much better than I like rfc.sh in the repo, but I'd prefer to keep
info about remotes, review processes, and other repo
On Fri, Oct 14 2011, John Dickinson wrote:
But it's metadata about the code (a particular review pattern with a
particular vcs). VCS info does not belong in the code. I'll admit that I
like a dotfile in the repo much better than I like rfc.sh in the repo, but
I'd prefer to keep info about
On Thu, 2011-10-13 at 13:03 -0400, Monty Taylor wrote:
Amongst things git-review does:
Rebases against the branch you're submitting to, rather than against
the place you cloned from
Allows you to skip rebasing if you want
Submit against a named branch
Explicitly set the topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/14/2011 07:50 AM, Lorin Hochstein wrote:
Anybody have any contacts with the NSF FutureGrid project:
https://portal.futuregrid.org/
It looks like adding support for OpenStack is already on their todo list:
*
I gave up to configure a OpenStack Diablo with Keystone (everything is still
very new). So, I would like to get an older Dashboard, compatible with
Cactus (although I'm using diablo) so I don't have to use Keystone. How can
I get it? The tutorial is wrong.
sudo bzr init-repo .
sudo bzr branch
FWIW I've tested the setup you describe and I'm not seeing duplicate ICMP
replies. Unfortunately I can't offer an explanation.
Adrian
From: openstack-bounces+adrian_f_smith=dell@lists.launchpad.net
[mailto:openstack-bounces+adrian_f_smith=dell@lists.launchpad.net] On
Behalf Of Shyam
I wouldn't mind finding that either, or a preferrably, in my case, keystone
package compatible with the Ubuntu oneiric diablo packages!
Thanks,
Kiall
On Oct 14, 2011 4:24 p.m., Jorge Luiz Correa corre...@gmail.com wrote:
I gave up to configure a OpenStack Diablo with Keystone (everything is
Strange, I haven't seen this. It sounds like maybe you have a mac address
conflict somehow. The only time I've seen duplicate icmp responses is when I
was running inside of virtualbox and due to the way vagrant was setting up vms,
I had multiple vms with same mac.
Vish
On Oct 14, 2011, at
yeah repo is pretty nice. I've been using it in conjunction with regular git
commands. Really though, all these tools do is shorthand a few git commands.
Why not just use the git?
I don't think our official docs should reflect the use of a tool like
git-review; they should describe the entire git
Mark McLoughlin mar...@redhat.com writes:
Chuck pointed out on IRC that I forgot to mention the other projects.
I totally think we should do the same for all projects, I was just using
Nova as a testcase.
Yep.
Each project will have a branch named after the previous release. For
I agree in principle. I do think that we should have clear documentation
of all of the git commands so that people can know what's going on and
choose what to do appropriately.
On the other hand, there are many people who do not want to learn all of
the ins and outs of what's going on and want
Vish,
We are not sure if this particular issue may cause any problem, but just
wanted to understand what is wrong.
To provide a bit more data about this particular environment:
- Dedicated servers config at RAX
- FlatDHCP mode with primary NIC (eth0) bridged and used
On 10/14/2011 09:46 AM, Julien Danjou wrote:
On Fri, Oct 14 2011, John Dickinson wrote:
But it's metadata about the code (a particular review pattern with a
particular vcs). VCS info does not belong in the code. I'll admit that I
like a dotfile in the repo much better than I like rfc.sh in the
On 10/14/2011 08:59 AM, Shyam Kaushik wrote:
*Hi Vish,*
In our openstack deployment we observe this:
Since linux_net.py/initialize_gateway_device()
http://linux_net.py/initialize_gateway_device() does this
# NOTE(vish): If the public interface is the same as the
#
On Fri, 2011-10-14 at 18:01 +, Chris Bohannon wrote:
Should we post them on the wiki?
Thanks,
Chris
Just post them (wherever convenient) and drop a note on openstack@lists.
I was in part just trying to confirm that the topic/discussion hadn't
moved to another mailing list/channel.
I don't know, but there are several obvious next steps:
- Document publicly the criteria for a project to fit
- Identify resources available to participating projects
- Formalize it with the PPB and unleash it
- Build the Satellite community
A big question we didn't discuss is what the
Let's not raise the bar too high for Satellite The points mentioned (CI,
QA, etc.) should be clearly documented with a y/n for the projects to aid
selection but I would much rather try out a non-CI tool in the directory than
have to write it all myself from scratch.
Ultimately, the aim
On 10/14/2011 02:44 PM, Russell Bryant wrote:
On 10/14/2011 09:46 AM, Julien Danjou wrote:
On Fri, Oct 14 2011, John Dickinson wrote:
But it's metadata about the code (a particular review pattern with a
particular vcs). VCS info does not belong in the code. I'll admit that I
like a dotfile
OpenStack Community Newsletter – October 14, 2011
HIGHLIGHTS
* Join the OpenStack Foundation mailing list
http://www.openstack.org/blog/2011/10/join-the-openstack-foundation-mailing-list/
* The OpenStack Academic Initiative is starting up
Chris B and I have a chat with folks at SourceForge on Monday about
getting an OpenStack forge community site going... of course I will
keep everyone informed.
Cheers,
-jay
On Fri, Oct 14, 2011 at 12:24 PM, David Medberry
david.medbe...@canonical.com wrote:
Hi,
I've not seen anything
On Fri, Oct 14, 2011 at 3:22 PM, Bryan Taylor btay...@rackspace.com wrote:
I don't know, but there are several obvious next steps:
- Document publicly the criteria for a project to fit
Not really sure there needs to be criteria, really...
- Identify resources available to participating
On Oct 14, 2011 10:54 p.m., Jay Pipes jaypi...@gmail.com wrote:
I would advise NOT having any particular governance model for
Satellite projects. The projects themselves should self-govern by the
cultural norms of the programming language communities that are
relevant to the project; since
On Fri, Oct 14, 2011 at 6:06 PM, Kiall Mac Innes ki...@managedit.ie wrote:
On Oct 14, 2011 10:54 p.m., Jay Pipes jaypi...@gmail.com wrote:
I would advise NOT having any particular governance model for
Satellite projects. The projects themselves should self-govern by the
cultural norms of the
Hi,
I think your configration is well,
check this flag in your nova.conf,
--api_paste_config=/YOUR_ENVIRONMENT/nova-api-paste.ini, Is it in your conf?
In nova-api-paste.ini, there is an authtoken filter for keystone. If you
can't find this, there are example in
On 10/14/2011 04:52 PM, Jay Pipes wrote:
On Fri, Oct 14, 2011 at 3:22 PM, Bryan Taylor btay...@rackspace.com wrote:
I don't know, but there are several obvious next steps:
- Document publicly the criteria for a project to fit
Not really sure
Hi,
I see that until now there was none Brazilian users group.
It can be nice have one group that can join efforts to translate interfaces,
manuals and talk openstack and cloud solutions.
To make this real i create the group at google below.
https://groups.google.com/group/openstack-br
Cheers
34 matches
Mail list logo
