Hi!
You probably want to check out jclouds as well. It's extremely mature,
is in production all over the world and has support for openstack
compute and storage.
http://www.jclouds.org/
Monty
On 07/18/2012 08:50 AM, Jyothsna Padavala wrote:
Thanks Vincent for your reply.
I lean towards
On 07/12/2012 04:36 PM, Vishvananda Ishaya wrote:
On Jul 12, 2012, at 2:22 PM, Narayan Desai wrote:
I think that the long term maintenance or removal of nova-volume in
its existing form is orthogonal to the actual issue of continuity from
one release to the next.
Agreed. Discussion
On 07/10/2012 04:23 PM, Matt Ray wrote:
Bluntness appreciated, this process is already in motion.
http://opscode.com/openstack was launched 2 weeks ago and I promptly
left for conferences and vacation. I am consolidating GitHub repos
here:
Awesome.
On 07/03/2012 08:43 AM, Doug Hellmann wrote:
On Jul 2, 2012, at 6:40 PM, Monty Taylor mord...@inaugust.com
wrote:
Hey all!
One of the tasks from the last ODS was to implement a single
global dependency list. Turns out the more you think about it, the
more important it is... because
On 07/03/2012 10:09 AM, Eric Windisch wrote:
I have to agree with others that copying files around is not ideal, and
I can see the maintenance of this getting more involved as Nova becomes
more coupled with common.
Additionally, we'd make the copy only copy in the versions from
: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-
bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
Monty Taylor
Sent: Tuesday, July 03, 2012 7:54 AM
To: Eric Windisch
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Single global
tl;dr - Screw the rules, I agree
Let's at least add it to the poll.
Also - I think we should further amend the rules such that we select the
NEXT release by the summit for the current release. That means two things:
At the g summit, we'd tell everyone where the next summit is:
At the g summit,
On 07/03/2012 05:07 PM, Duncan McGreggor wrote:
On Tue, Jul 3, 2012 at 5:39 PM, Dan Wendlandt d...@nicira.com wrote:
Lately, Quantum reviewers have been doing their best to enforce python style
guidelines above and beyond the programmatically enforced pep8 checks. This
has happened for many
On 07/03/2012 07:29 PM, Brian Waldon wrote:
On Jul 3, 2012, at 5:21 PM, Monty Taylor wrote:
tl;dr - Screw the rules, I agree
Let's at least add it to the poll.
Also - I think we should further amend the rules such that we select the
NEXT release by the summit for the current release
the circle of reviewers on these
centralized projects that have the power to block everyone yet are so
easy to ignore...
TOTALLY agree - especially on expanding the circle of reviewers.
All the best,
- Gabriel
-Original Message- From: Monty Taylor
[mailto:mord...@inaugust.com] Sent
Interestingly enough - gerrit supports submodules pretty well... and it
does exactly what Eric said below ... if both the project and
superproject are in gerrit, and a change is made to the project, gerrit
can automatically update the superproject reference.
Here's the thing though (and one of
On 07/03/2012 07:33 PM, James E. Blair wrote:
Brian Waldon brian.wal...@rackspace.com writes:
TL;DR - Screw the rules, let's call the next release 'Grizzly'
As California is rather lacking in the 'municipality names starting
with a G that we should use for an OpenStack release'
On 07/02/2012 06:46 AM, John Garbutt wrote:
Hi,
I noticed I can now run the pep8 tests like this (taken from Jenkins job):
tox -v -epep8
...
pep8: commands succeeded
congratulations :)
But the old way to run tests seems to fail:
./run-tests.sh -p
On 07/02/2012 05:14 AM, Daniel P. Berrange wrote:
I must say that this has been driving me mad this last week. IIUC, only
members of the core review team have permission to retrigger Jenkins,
but I feel it is putting too much burden on them to have to track every
patch with a bogus Jenkins
On 07/02/2012 06:02 AM, Leander Bessa Beernaert wrote:
Thanks, that let me see the real problem now:
./tools/with_venv.sh nosetests -svx nova
nose.config: INFO: Set working dir to /home/gsd/nova/nova/tests
nose.config: INFO: Working directory /home/gsd/nova/nova/tests is a
On 07/02/2012 06:46 AM, John Garbutt wrote:
Hi,
I noticed I can now run the pep8 tests like this (taken from Jenkins job):
tox -v -epep8
...
pep8: commands succeeded
congratulations :)
But the old way to run tests seems to fail:
./run-tests.sh -p
so i'm not sure what's happening there :s
global libvirt
if libvirt is None:
libvirt = __import__('libvirt')
Regards,
Leander
On Mon, Jul 2, 2012 at 1:27 PM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
On 07/02/2012 06:02 AM
to fix things.
Thanks for your help,
John
-Original Message-
From: Monty Taylor [mailto:mord...@inaugust.com]
Sent: 02 July 2012 1:28
To: John Garbutt
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] PEP8 checks
On 07/02/2012 06:46 AM, John Garbutt wrote:
Hi,
I
Run:
sudo pip install tox
And you will get the tox command.
Does ./run_tests.sh -N nova.tests.test_libvirt work fine when you
_don't_ have libvirt? It needs to skip the test if you don't have
libvirt installed, and it needs to run it and pass if you do.
Jenkins is going to run tox -v -epy27
Hey all!
One of the tasks from the last ODS was to implement a single global
dependency list. Turns out the more you think about it, the more
important it is... because of the way we use devstack as part of the
gate, we actually _currently_ have a de facto global dependency list,
it's just not
Hey all!
(It must be a busy day - I'm writing you all so many emails...)
A little while ago, after chatting with Anne Gentle, we started
publishing the sphinx documentation to
docs.openstack.org/developer/$project ... instead of to
$project.openstack.org. That went really well and we're happy
Yeah - transient error. We're seeing more of them recently (see Jim's
recent email to the list in the Jenkins and transient failures thread)
But - we're working on it. We've got several different things in work to
prevent these from happening. Sorry for the annoyance ... hopefully will
all be
Hi!
We were doing some maintenance this afternoon on jenkins and gerrit -
you were unlucky enough to push right in the middle of that.
Try amending your commit (git commit --amend) and change the commit
message a little (put a space after the comma here:
lp:1019348,update and then run git review
Hey! I agree with most of this in general. A few comments about a
section I just happened to read:
On 06/27/2012 06:52 AM, Daniel P. Berrange wrote:
snip
Including external references
-
The commit message is primarily targetted towards human interpretation,
but
On 06/29/2012 04:06 AM, Alan Pevec wrote:
On Thu, Jun 28, 2012 at 9:56 PM, Monty Taylor mord...@inaugust.com wrote:
https://review.openstack.org/9109
Why is setuptools_git added in pip-requires, I thought that's for
run-time, not build-time dependencies?
Hey Alan!
We use pip-requires
isn't really
build-time vs. run-time as much as it has to do with our use of virtualenv.
HOWEVER - I think I just had an idea of how to make this slighly
cleaner. Let me poke at it.
On 6/29/12 4:06 AM, Alan Pevec ape...@gmail.com wrote:
On Thu, Jun 28, 2012 at 9:56 PM, Monty Taylor mord
On 06/29/2012 10:48 AM, Alan Pevec wrote:
On Fri, Jun 29, 2012 at 7:19 PM, Monty Taylor mord...@inaugust.com wrote:
We use pip-requires as part of building the virtualenvs. Once we start
using it, setuptools-git is pretty much required for running setup.py,
so many common actions in our
On 06/29/2012 10:48 AM, Alan Pevec wrote:
On Fri, Jun 29, 2012 at 7:19 PM, Monty Taylor mord...@inaugust.com wrote:
We use pip-requires as part of building the virtualenvs. Once we start
using it, setuptools-git is pretty much required for running setup.py,
so many common actions in our
On 06/28/2012 07:32 AM, Daniel P. Berrange wrote:
Today we face a situation where Nova GIT master fails to pass all
the libvirt test cases. This regression was accidentally introduced
by the following changeset
https://review.openstack.org/#/c/8778/
If you look at the history of
build_sphinx, right?
(if it was a gating spellcheck I'll be in big trouble :))
On Tue, Jun 26, 2012 at 4:02 PM, Monty Taylor mord...@inaugust.com wrote:
Hey guys!
We have all of the projects properly and consistently building and
uploading sphinx docs from in tree. This is pretty exciting
On 06/28/2012 12:05 PM, Vishvananda Ishaya wrote:
On Jun 28, 2012, at 8:13 AM, Monty Taylor wrote:
Which adds an additional testing environment that has system software
enabled and also installs additional optional things. With that
environment, we should be able to run a jenkins gate
Hey all!
Using quantum as a little bit of a guinea pig, we've been poking at
setuptools-git, which is a setuptools plugin which adds git vcs support
to setuptools. Why would we care? Well, setuptools itself has baked in
support for cvs and svn (yay! such future thought!) One of the nice bits
is
On 06/28/2012 01:49 PM, Dan Prince wrote:
- Original Message -
From: Monty Taylor mord...@inaugust.com To:
openstack@lists.launchpad.net Sent: Thursday, June 28, 2012
11:13:28 AM Subject: Re: [Openstack] Jenkins vs SmokeStack tests
Gerrit merge blockers
On 06/28/2012 07
Hey guys!
We have all of the projects properly and consistently building and
uploading sphinx docs from in tree. This is pretty exciting, because it
means one more resource we can expect to work.
So related to that, we were talking about putting in a gating job for
each project to prevent
Hi!
On 06/19/2012 09:43 AM, Alexey Ababilov wrote:
Hi!
Unfortunately, nova, keystone, and glance clients are very inconsistent.
A lot of code is copied between all these clients instead of moving it
to a common library. The code was edited without synchronization between
clients, so, they
We're trying to figure out how we release client libraries. We're really
close - but there are some sticking points.
First of all, things that don't really have dissent (with reasoning)
- We should release client libs to PyPI
Client libs are for use in other python things, so they should be
to manage it the same way.
On Mon, Jun 18, 2012 at 5:11 PM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
We're trying to figure out how we release client libraries. We're really
close - but there are some sticking points.
First of all, things that don't really
-versioning here:
https://review.openstack.org/#/c/8427/
We need to get (aiui) one thing landed to zuul so that we can
appropriately trigger on tag events... but that's the plan in my brain hole.
On Jun 18, 2012, at 2:11 PM, Monty Taylor wrote:
We're trying to figure out how we release client
We're trying to figure out how we release client libraries. We're really
close - but there are some sticking points.
First of all, things that don't really have dissent (with reasoning)
- We should release client libs to PyPI
Client libs are for use in other python things, so they should be
On 06/13/2012 10:58 AM, Juan J. Martinez wrote:
On 13/06/12 15:42, Dan Prince wrote:
Okay. It looks like Swift also still depends on swiftclient. Long term it
would be nice if we could build and unit test swift without relying on the
swiftclient package. Could we:
I can't see the
On 06/11/2012 12:04 PM, John Garbutt wrote:
Hi,
I am trying to run tests like test_xenapi and test_libvirt by themselves
do things like:
nosetests test_xenapi
But it does work, I get DB errors relating to missing tables. However, I can
successfully run all the tests.
The way I
On 06/11/2012 07:06 PM, Gabriel Hurley wrote:
I just thought I'd call out that Glance's swift storage module is
currently broken, and apparently this escaped the devstack gate even
though devstack actually fails to complete if swift is enabled. Are
we not testing with swift in the
Hey guys!
We just upgraded to a new version of gerrit. This is based on the new
upstream version 2.4, but in addition we've landed two additional
features on top of that - so there's tons of new toys to play with.
First of all, in 2.4 upstream has added a new button Rebase Change ...
which you
Hey guys!
In a fit of things coming together... today has been an unnaturally good
and productive day for us, so I thought I'd mention a bunch of stuff
(most things long-in-work and just sort of came together nicely today)
- builders are now updated to run precise - except for the python2.6
On 06/05/2012 07:54 AM, Gary Kotton wrote:
Hi Monty and Dan,
Background: A short while ago I started to port bug fixes for Quantum
from Folsom-1 to Stable Essex. Jenkins did not accept the patches due to
the fact that the automatic tests did not pass. The failures are due to
2 reasons:
1.
Hey guys!
One of the things that came out of ODS is the idea of having a single
global dependency list. There are two bits to that - the mechanics of
managing the list (which I think we may have sorted) and then, you know,
making the list. In compiling the list of what the current global list
is,
, 2012 at 2:38 PM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
Well - there are two choices... you can upgrade to 1.1, or you can put
in an entry into tox.ini, changing:
deps=pep8
to
deps = pep8==0.6.1
We're working on getting
On 05/28/2012 04:32 PM, Paul Belanger wrote:
On 12-05-25 03:58 PM, Monty Taylor wrote:
Hey guys!
We just finished rolling out the first in a sequence of upcoming changes
to gerrit and jenkins based on needs described at the design summit.
We now have the basic jobs for all of the projects
On 05/28/2012 12:42 AM, Robert Collins wrote:
I think you need to change your integration logic :)
Heh. It always seems that way at first glance.
Define the LP ids you want to have access however you want to do it;
when an openid login occurs, call the LP mapping IP with the openid
On 05/27/2012 10:43 PM, William Grant wrote:
On 28/05/12 12:27, James E. Blair wrote:
With respect to the OpenStack Gerrit, it's not that the consumer is
buggy, it's that since we're trying to _integrate_ with Launchpad, we
need to know the _Launchpad_ user of the person who is authenticating
Hey guys!
We just finished rolling out the first in a sequence of upcoming changes
to gerrit and jenkins based on needs described at the design summit.
We now have the basic jobs for all of the projects (except for horizon,
because it's slightly different and I want to spend a little more time
Gimme a day or two - we're about to roll out a thing which adds all of
the standard jobs for everything driven from files in git ... so this
all gets much easier real soon.
On 05/16/2012 07:21 PM, Yong Sheng Gong wrote:
Hi,
I cannot find the quantum-client coverage report on jenkins sie:
On 05/08/2012 09:56 PM, Thierry Carrez wrote:
Gabriel Hurley wrote:
Having worked with all three tools, I would strongly suggest Transifex,
particularly given that we as a community have to do almost no work to
maintain it, it's the only tool that supports OpenStack as a project hub
with
Honestly, I think we might want to delete write_requirements()
altogether. I don't think it's beneficial... asign this to me and I'll
get it fixed up.
On 05/04/2012 11:30 AM, Mark McLoughlin wrote:
Could do with more details here, I'm not sure I follow what the issue is
** Changed in:
On 05/03/2012 05:24 AM, Thierry Carrez wrote:
(snip things I pretty much agree with)
(I'm not sure gerrit is right for this. Why not just do it in
folk's github forks? I think all people are looking for is for
people to be more aware of feature branches. How about if you put
On 05/03/2012 08:50 AM, Mark McLoughlin wrote:
On Thu, 2012-05-03 at 16:46 +0100, Mark McLoughlin wrote:
Hey,
On Thu, 2012-05-03 at 14:24 +0200, Thierry Carrez wrote:
Mark McLoughlin wrote:
And how about feature branches?
- Feature branches are relatively short-lived (i.e. weeks or
On 04/27/2012 06:11 AM, Jim Meyering wrote:
Daniel P. Berrange wrote:
On Fri, Apr 27, 2012 at 12:04:34PM +0200, Thierry Carrez wrote:
To avoid Launchpad list slowness, we would run the new openstack-dev
list off lists.openstack.org. Given the potential hassle of dealing with
spam and
Hey everyone!
On 04/27/2012 05:04 AM, Thierry Carrez wrote:
To avoid Launchpad list slowness, we would run the new openstack-dev
list off lists.openstack.org. Given the potential hassle of dealing with
spam and delivery issues on mission-critical MLs, we are looking into
the possibility of
On 04/27/2012 09:44 AM, Duncan McGreggor wrote:
On Fri, Apr 27, 2012 at 8:46 AM, Monty Taylor mord...@inaugust.com wrote:
Hey everyone!
On 04/27/2012 05:04 AM, Thierry Carrez wrote:
To avoid Launchpad list slowness, we would run the new openstack-dev
list off lists.openstack.org. Given
Hey!
On 04/27/2012 06:20 PM, Loic Dachary wrote:
Hi,
I would like to create a repository ceilometer in
https://github.com/stackforge to host the code for the newborn Metering
project ( https://launchpad.net/ceilometer , first meeting held this thursday
Hey guys,
Quick follow up from the summit on things that should happen in projects
from the setup module of openstack common as I understand it. (to make
sure we're all on the same page)
There are currently 5 essential things in openstack.common.setup:
parse_requirements
parse_dependency_links
On 04/26/2012 10:14 AM, Sean Dague wrote:
On 04/25/2012 05:17 PM, Vishvananda Ishaya wrote:
The main issue is when the relevant tables are moved into a separate
service a la quantum or cinder. We can't keep referential integrity
across multiple databases, so the foreign keys in this case
On 04/24/2012 10:08 PM, Lorin Hochstein wrote:
On Apr 24, 2012, at 4:11 PM, Joe Gordon wrote:
Hi All,
I would like to propose a minimum required code coverage level per
file in Nova. Say 80%. This would mean that any new feature/file
should only be accepted if it has over 80% code
Barbara wrote:
If you let me know in a bit more detail what you're looking for, I can
probably whip something up. Email me direct?
Justin
On Wed, Apr 25, 2012 at 6:59 AM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
On 04/24/2012 10:08 PM, Lorin
I agree with Mark. In my world, all options should have sane defaults.
--
You received this bug notification because you are a member of OpenStack
Common Drivers, which is the registrant for openstack-common.
https://bugs.launchpad.net/bugs/983734
Title:
Keystone fails badly if you miss one
Public bug reported:
virtualenv 1.7 has a bug which causes problems in re-using virtualenvs,
especially seen when used in the context of the tool tox (which we use
for all of the test builders in OpenStack) The bug has been fixed in a
point release, and the patch to do it is here:
On 04/13/2012 04:36 AM, Kiall Mac Innes wrote:
The new gerrit version also supports per user namespaces, if enabled.
These allow users to create private branches with full push privileges etc..
Have these been enabled?
They have not - we need to verify what the behavior looks like over
It should Just Work™
On 04/11/2012 02:29 PM, Vishvananda Ishaya wrote:
Yay! Awesome work Dean!
Monty/Jim: Has the ci infrastructure been updated to use the stable/essex
branch for integration tests on the stable/essex merges?
Vish
On Apr 11, 2012, at 1:57 PM, Dean Troyer wrote:
The
On 04/09/2012 04:11 PM, Jay Pipes wrote:
On 04/09/2012 07:07 PM, Jorge Williams wrote:
On Apr 9, 2012, at 6:03 PM, Justin Santa Barbara wrote:
How about we discuss this further at the summit :-)
I think that's a sensible proposal. We're not likely to reach a good
conclusion here. I
Hi!
jclouds is an open source java library for connecting to clouds. As
such, it supports connecting to OpenStack based clouds. The OpenStack CI
team have been working with jclouds on both support for OpenStack as
well as a plugin for jenkins so that we can have more direct control of
build
- but you know - face to
face about this stuff often winds up being super-big win.
Yay for Open Source!
Monty
On Sun, Apr 8, 2012 at 6:37 PM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
Hi!
jclouds is an open source java library for connecting to clouds
8, 2012 at 6:37 PM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
Hi!
jclouds is an open source java library for connecting to clouds. As
such, it supports connecting to OpenStack based clouds. The
OpenStack CI
team have
On 04/05/2012 01:22 AM, Justin Santa Barbara wrote:
I've got Compute functionality working with the OpenStack Jenkins
plugin, so it can launch nova instances as on-demand slaves now, run
builds on them, and archive the results into swift. I'd like to open
GitHub issues to track your
Hello all!
Someone has spun up a nice new node using the puppet modules that we use
for OpenStack CI. That's GREAT - and I'm thrilled that you're finding
things useful. You're also helped us notice a bug/design flaw though in
one of our modules. The configuration of where to send sysadmin email
weechat (0.3.7-1) unstable; urgency=low
* New upstream release
* Bump Standards-Version to 3.9.3
* Update debian/copyright: new year
* Add new doc-base files:
- Developer's Guide in English
- Relay Protocol in English
- Quickstart in Spanish
* Update Vcs-Git and Vcs-Browser
On 04/03/2012 03:50 PM, Iain Lane wrote:
This should be fine, but looking at the changelog[0] the number of
changes is rather large. How much testing have you given this?
[0] http://www.weechat.org/files/changelog/ChangeLog-0.3.7.html
I've been using it as my personal IRC client (and I work
Public bug reported:
Please sync weechat 0.3.7-1 (universe) from Debian testing (main)
Explanation of FeatureFreeze exception:
0.3.7 is the upstream stable release and would be stellar to get in to the
Precise LTS. Additionally to being the current stable, 0.3.7 introduced a new
remote
On it.
On 03/15/2012 11:53 PM, Dan Wendlandt wrote:
Hi Sumit,
I don't expect that this is a problem with your commit in particular.
I'm CC'ing Monty and James, as my best guess is that this is a backend
CI issue. Here's the error:
Successfully installed quantum
Cleaning up...
** Changed in: openstack-ci
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/917851
Title:
replace m2crypto with shelling to openssl
To manage
** Changed in: openstack-ci
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917851
Title:
replace m2crypto with shelling to openssl
To manage notifications
One of our devs packaged it for Ubuntu:
https://lists.launchpad.net/openstack/msg07061.html
and it's going to be in the upcoming ubuntu precise release:
http://packages.ubuntu.com/precise/git-review
I'm not aware of anyone uploading it to debian yet - but it shouldn't be
hard to either install
One of our devs packaged it for Ubuntu:
https://lists.launchpad.net/openstack/msg07061.html
and it's going to be in the upcoming ubuntu precise release:
http://packages.ubuntu.com/precise/git-review
I'm not aware of anyone uploading it to debian yet - but it shouldn't be
hard to either install
Hey guys!
I've been working on aligning how we call testing stuff inside of
project repos so that we can templatize more things in Jenkins and
eventually get the job content itself properly in to a git repo and in
gerrit. (mmm... recursive dogfood)
Of course, doing things in order would be nice,
Hey!
I've got two things I'd love to add - although I know I missed the
cutoff (I can do them next week as well if we're skipping this week)
- I'd like to get buy in on:
http://wiki.openstack.org/ProjectTestingInterface
- My team has been working on a second copy of the OpenStack CI
Hi!
On 02/14/2012 07:29 PM, Joe Gordon wrote:
Hi Developers,
I have been looking at https://bugs.launchpad.net/nova/+bug/931608,
run_tests.sh (-x | --stop) is broken. A fix was committed but it only
stopped ./run_tests.sh -x from failing, and not restoring the
./run_tests.sh -x
Hi all!
It's been a rough week from a CI and dev infrastructure perspective. I
wanted to let people know what happened, what we did about it, and where
it's going.
First of all, we had 4 different things happen all this week. (when it
rains is pours)
Rackspace Cloud changed the compute service
Hi!
Awesome, and thanks for the work!
Just in case you didn't know about it:
http://www.jclouds.org/
Is a Java library with multi-cloud support, including OpenStack, which
might be a fun place for you to hack - and I know Adrian loves contributors.
On the other hand, any amount of Java story
Yup. Absolutely crazy.
This was in the direction of solving an issue on OSX. Of course, I don't
have that, so I'm pretty sure I applied the theory poorly.
I will make a new patch and make a test case that I can use to prove the
problem and the solution.
Thank you.
On 02/09/2012 07:16 PM, Pete
On 02/07/2012 06:44 AM, Alan Pevec wrote:
On Tue, Feb 7, 2012 at 6:51 AM, Maru Newby mne...@internap.com wrote:
-1 on multi-distribution devstack. Being cross-platform is arguably a place
where chef/puppet/cfengine automation comes into play, and that's not where
devstack's self-declared
On 02/07/2012 08:32 PM, Jay Pipes wrote:
Thanks for the update, Matt. Comments inline...
On 02/07/2012 10:16 PM, Matt Ray wrote:
I think Jay did a good job outlining the lineages and scope of the
assorted cookbook efforts so far. My Anso-based fork at
I think the thing you are discussing already exists.
devstack is currently part of and managed by all of the normal OpenStack
development infrastructure. The canonical repository for it is
https://review.openstack.org/p/openstack-dev/devstack which is mirrored
to
On 02/06/2012 10:37 AM, Jesse Andrews wrote:
I think having a session on devstack at the summit would be valuable.
++
I'm still torn on it being python vs. bash because I see
non-developers using it all the time because they can take snippets of
the shell script and use it.
I'm similarly
On 02/06/2012 06:07 PM, Jay Pipes wrote:
Hi Stackers,
tl;dr
-
There are myriad Chef cookbooks out there in the ecosystem and locked
up behind various company firewalls. It would be awesome if we could
agree to:
* Align to a single origin repository for OpenStack cookbooks
*
Hey all!
We've been going through cleaning up some of the infrastructure. One of
the things that popped out was that the management of the config for the
planet.openstack.org blog aggregator was still done via bzr.
That seemed silly.
So now you can clone openstack/openstack-planet and submit
On 01/31/2012 10:24 AM, Thierry Carrez wrote:
David Kranz wrote:
The meetings logs at
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/ only
have one entry (Jan 24) since Jan 18. I think there was an openstack-qa
meeting on the 25th. Is this the right link to find meeting logs?
On 01/27/2012 04:59 AM, Thierry Carrez wrote:
Robbie Williamson wrote:
http://jenkins.qa.ubuntu.com/view/Precise%20OpenStack%20Testing/
Great work!
Would be cool to syndicate those Jenkins instances into a general health
dashboard that we could use to get at a glance the health of
On 01/27/2012 08:48 AM, Kiall Mac Innes wrote:
Hiya,
For those of you who prefer to avoid pip installing as much as
possible in favor of native packages, I've packaged up the git-review
tool for Ubuntu (Just oneiric for now, if there is interest I'll package
for lucid too).
PPA @
Hey!
I actually think we can leave nose and pep8 out of the install_requires
as well, since that's really only going to get used by pip. BUT - it's
not going to hurt anything.
Monty
On 01/24/2012 04:16 PM, Dan Wendlandt wrote:
Hi Monty,
Here's a patch to remove what I believe are the
On 01/18/2012 06:12 AM, Dan Wendlandt wrote:
Thanks Monty! Inline
Dan
On Mon, Jan 16, 2012 at 4:35 PM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
Hey guys -
Quick status update from me here:
First of all, Jim's patch is win:
https
On 01/17/2012 02:16 PM, Jay Pipes wrote:
On Mon, Jan 16, 2012 at 9:48 PM, Ewan Mellor ewan.mel...@eu.citrix.com
wrote:
While I’m here, any chance we can have a unit test running on Python 2.6?
Monty and Jim have been working on getting parallel 2.7 and 2.6 tests
going with the tox
1001 - 1100 of 2124 matches
Mail list logo
