On 08/02/2013 01:06 PM, James Kyle wrote:
Following up on my own thread, the fix can be integrated into
../stack.sh by adding this to the localrc:
# FIXES: https://bugs.launchpad.net/neutron/+bug/1206013
OSLOCFG_REPO=https://github.com/openstack/oslo.config.git
OSLOCFG_BRANCH=1.2.0a3
On 08/02/2013 05:23 PM, Joe Gordon wrote:
Hi All,
even though Glance, has been pulled out of Nova years ago, Nova still
has a images API that proxies back to Glance. Since Nova is in the
process of creating a new, V3, API, we know have a chance to re-evaluate
this API.
* Do we still
Hey all!
Currently, there is runtime version handling code in pbr. It's been a
cause of concern for some folks because it means that pbr becomes a
runtime rather than just a build time dependency - so the suggestion has
come across that we split it out into its own library.
This becomes even
Normally I don't announce pbr releases, because you should really never
notice them (unless they're fixing a bug you happen to be hitting) BUT -
this one fixes a long-standing request that I think should make people
happy, and there are some flags that folks can take advantage of should
they want.
If you hit an error like this:
Bad md5 hash for package
https://pypi.python.org/packages/source/c/colorama/colorama-0.2.5.tar.gz#md5=c76f67ead9dc7c83700c57695ebb741e
(from https://pypi.python.org/simple/colorama/)
It means that our friends at colorama have decided to re-release
something with
On 08/05/2013 11:26 PM, Robert Collins wrote:
I wanted to get a temperature reading from everyone on this style guideline.
My view on it is that it's a useful heuristic but shouldn't be a
golden rule applied everywhere. Things like matches are designed to be
used as a dsl:
Hey Chmouel!
Good point. I think we could add a check to see if there are any changes
in the repo and skip the update if there are not. Or, we could protect
that action in a variable and have devstack-gate set that variable...
what do you guys think?
On 08/06/2013 12:56 AM, Chmouel Boudjnah
Hey all!
As you know, we're been battling the effects of the
setuptools/distribute re-merge and upgrade for about a month now. It's
mostly settled down, but there are still cases where transitive
dependencies on things that depend on things that depend on distribute
can screw us. At the moment,
On 08/06/2013 02:44 PM, Mate Lakat wrote:
Hi,
I would say, use a separated virtual environment in devstack - without
the --system-site-packages switch, of course, and set it up as a user.
Install the packages that are needed in order to be able to pip install
them (like libxslt-dev). It's
On 08/06/2013 03:46 PM, Russell Bryant wrote:
On 08/06/2013 12:20 PM, Russell Bryant wrote:
On 08/06/2013 11:53 AM, Ian Mcleod wrote:
Hello,
A blueprint has been registered regarding API additions to Nova to
enable the creation of base images from external OS install sources.
This
On 08/06/2013 11:14 PM, Robert Collins wrote:
On 7 August 2013 11:22, Jay Buffington m...@jaybuff.com wrote:
ln -s /usr/lib64/python2.6/site-packages/libvirtmod_qemu.so
$(VENV)/lib/python2.6/site-packages/
Why isn't libvirt-python on pypi? AFAICT, nothing is stopping us from
On 08/06/2013 11:39 PM, Robert Collins wrote:
On 7 August 2013 14:36, Monty Taylor mord...@inaugust.com wrote:
On 08/06/2013 11:14 PM, Robert Collins wrote:
On 7 August 2013 11:22, Jay Buffington m...@jaybuff.com wrote:
ln -s /usr/lib64/python2.6/site-packages/libvirtmod_qemu.so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/07/2013 04:51 AM, Julien Danjou wrote:
On Tue, Aug 06 2013, Monty Taylor wrote:
This would allow for clear voting by both the TC and others - is
consistent with tooling we ALL know how to use, and has the
benefit of producing a clear
On 08/07/2013 05:58 AM, Thierry Carrez wrote:
Monty Taylor wrote:
What if instead we had a repo with a bunch of ReStructureText in it -
perhaps a copy of the TC charter and then a dir for additional things
the TC has decided. That repo would be autopublished to a non-wiki
website
On 08/07/2013 12:53 PM, Joshua Harlow wrote:
I agree triple-o will help a lot here although I would disagree that
package rollback is an illusion. I would call it more of a hard
problem instead since nothing is really impossible :)
illusion with current packaging systems yum/rpm and
You may have just noticed a bunch of requirements updates patches. These
are mostly not urgent - although once jenkins comes back +1 on them,
they're safe to merge, because they will have been gated. Right now I'm
testing the script that we'll use. Moving forward, patches will be
proposed
On 08/08/2013 09:04 AM, Sean Dague wrote:
On 08/08/2013 07:33 AM, Boris Pavlovic wrote:
Hi Mark,
Sounds good. Just needs someone willing to implement it.
This is very interesting for us.
What do you think if we create a fake project that use submodules as an
example, and then just
On 08/08/2013 09:30 AM, Thierry Carrez wrote:
Mark McLoughlin wrote:
I think what Monty might be getting at is that TC decisions would no
longer happen by default with people voting at a particular TC meeting.
Rather a discussion would happen on the mailing list with people casting
their
On 08/05/2013 02:03 PM, Dean Troyer wrote:
[Moving a discussion from https://review.openstack.org/40019 to the ML
to get a wider audience]
We've been around this block more than once so let's get it all
documented in one place and see where to go next. Skip down to
# for more
Hey all!
You may have noticed recently that there are issues running devstack on
brand new machines - and if you have noticed that, you may have been asking:
- what's the problem?
- how the heck did this make it past the gate since we run devstack so
often?
Well - this is a fun one, and it's
+1
On 08/16/2013 11:04 AM, Doug Hellmann wrote:
I'd like to propose Alex Gaynor for core status on the requirements project.
Alex is a core Python and PyPy developer, has strong ties throughout the
wider Python community, and has been watching and reviewing requirements
changes for a little
On 08/16/2013 09:52 AM, Boris Pavlovic wrote:
Hi all,
We (OpenStack contributors) done a really huge and great work around DB
code in Grizzly and Havana to unify it, put all common parts into
oslo-incubator, fix bugs, improve handling of sqla exceptions, provide
unique keys, and to use
On 08/16/2013 09:31 AM, Victor Sergeyev wrote:
Hello All.
Glance cores (Mark Washenberger, Flavio Percoco, Iccha Sethi) have some
questions about Oslo DB code, and why is it so important to use it
instead of custom implementation and so on. As there were a lot of
questions it was really
On 08/16/2013 02:25 PM, Maru Newby wrote:
Neutron has been in and out of the gate for the better part of the
past month, and it didn't slow the pace of development one bit. Most
Neutron developers kept on working as if nothing was wrong, blithely
merging changes with no guarantees that they
On 08/20/2013 09:26 PM, Brant Knudson wrote:
We've been too lax about delineating public and internal interfaces in
python-keystoneclient. This makes changes and reviews difficult because
we don't know what we can change without breaking applications. For
example, we thought we could
On 09/04/2013 01:22 PM, Dolph Mathews wrote:
On Wed, Sep 4, 2013 at 10:56 AM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
Hey all!
https://review.openstack.org/#/c/42178/2 has landed in nova, which means
that nova now requires tox 1.6 or higher
Hey all,
One of the things we were working on this cycle was splitting the
version handling code out of pbr into its own library - oslo.version.
This work did not make Feature Freeze. I wanted to check in with folks
to take temperature about whether it's worth attempting to get it done
by the
On 09/06/2013 10:51 AM, Thierry Carrez wrote:
Monty Taylor wrote:
Hey all,
One of the things we were working on this cycle was splitting the
version handling code out of pbr into its own library - oslo.version.
This work did not make Feature Freeze. I wanted to check in with folks
to take
On 09/11/2013 11:09 AM, David Ripton wrote:
On 09/11/2013 06:37 AM, Steven Hardy wrote:
I'm investigating some issues, where data stored to a text column in
mysql
is silently truncated if it's too big.
It appears that the default configuration of mysql, and the sessions
established via
On 09/12/2013 04:33 PM, Steve Baker wrote:
On 09/13/2013 08:28 AM, Mike Asthalter wrote:
Hello,
Can someone please explain the plans for our 2 wadls moving forward:
* wadl in original heat
repo:
Hey everybody!
You know how, when you want to make a new project, you basically take an
existing one, like nova, copy files, and then start deleting? Nobody
likes that.
Recently, cookiecutter came to my attention, so we put together a
cookiecutter repo for openstack projects to make creating a
On 09/12/2013 07:06 PM, Nachi Ueno wrote:
Hi Folks
Is anyone interested in Kibana + ElasticSearch Integration with ceilometer?
# Note: This discussion is not for Havana.
I, for one, welcome our new ElasticSearch overlords.
I have registered BP. (for IceHouse)
On 09/15/2013 01:47 PM, Alex Gaynor wrote:
Falcon was included as a result of Marconi moving from stackforge to
being incubated. sphinxcontrib-programoutput doesn't appear to have been
added at all, it's still under
review: https://review.openstack.org/#/c/46325/
I agree with Alex and
On 09/17/2013 08:06 AM, Thomas Goirand wrote:
On 09/17/2013 06:52 PM, Thomas Goirand wrote:
On 09/16/2013 10:41 PM, Bhuvan Arumugam wrote:
It's fun out of inter dependencies. Nova depends on python-glanceclient;
python-glanceclient depends on warlock=1.0.1,2. warlock depends on
On 09/20/2013 01:24 PM, Dan Wendlandt wrote:
On Fri, Sep 20, 2013 at 1:09 PM, Joe Gordon joe.gord...@gmail..com
mailto:joe.gord...@gmail.com wrote:
On Fri, Sep 20, 2013 at 11:52 AM, Russell Bryant rbry...@redhat.com
mailto:rbry...@redhat.com wrote:
On 09/20/2013
On 09/19/2013 01:30 PM, Mark McLoughlin wrote:
On Thu, 2013-09-19 at 15:22 -0500, Dolph Mathews wrote:
On Thu, Sep 19, 2013 at 2:59 PM, Adam Young ayo...@redhat.com wrote:
I can submit a summit proposal. I was thinking of making it
more general than just the Policy piece.
On 09/20/2013 02:55 PM, Ben Nemec wrote:
On 2013-09-20 03:16, Flavio Percoco wrote:
On 19/09/13 17:10 -0400, Adam Young wrote:
On 09/19/2013 04:30 PM, Mark McLoughlin wrote:
To take the specific example of the policy API, if someone actively
wanted to help the process of moving it into a
On 09/20/2013 02:47 PM, Michael Still wrote:
Before https://review.openstack.org/#/c/46867/ if file injection of a
mandatory file fails, nova just silently ignores the failure, which is
clearly wrong. However, that review now can't land because its
revealed another failure in the file
On 09/20/2013 02:33 AM, Thomas Goirand wrote:
Hi,
Has anyone thought about having a PGP key signing party during the
summit? Guys from the Linux kernel thought it was useless, but after the
hack of kernel.org, they started to understand it was useful, and now
they do have a web of
On 09/23/2013 12:14 AM, Zhongyue Luo wrote:
Looks like this problem happens in systems that use pip1.4 but upgraded
tox to 1.6.1
http://tox.readthedocs.org/en/latest/config.html#confval-install_command=ARGV
Yes. We have been rolling out tox.ini changes to projects. I'll push one
up for
On 09/23/2013 01:20 PM, Vijay Venkatachalam wrote:
Hi,
I am new to openstack, please pardon if the questions
are dumb.
Attempting to run a neutron dev setup with openvswitch plugin with VLAN
isolation and 2 hosts.
_DISCLAIMER: _I am not using devstack.
tl;dr - easy_install sucks, so use pip
It is common practice in python to run:
python setup.py install
or
python setup.py develop
So much so that we spend a giant amount of effort to make sure that
those always work.
Fortunately for us, the underlying mechanism, setuptools, can often be a
pile
On 09/24/2013 12:11 PM, Thomas Goirand wrote:
Hi Monty,
On 09/24/2013 09:44 AM, Monty Taylor wrote:
Instead of:
python setup.py install
Run:
pip install .
No way that this happens on the packaging side. Buildd have no network
access (on purpose), and we must not do any network
Just in case these help anyone, I've make a couple of bookmarks to a
couple of queries that have really been helping me deal with both my
patches, and things I need to review.
First of all:
On 09/28/2013 12:08 AM, Gareth wrote:
On Fri, Sep 27, 2013 at 9:43 PM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
Right now the gate is extremely full, there are a number of reasons
for that. What's more important right now is to try not to make it
worse
Hey all,
oslo.version is in gerrit now, which is a split out of the version code
from pbr. I'd love if if you'd add oslo.version to your project watches
so that patches get love.
oslo.sphinx could probably use the same treatment.
Monty
___
On 09/29/2013 01:02 PM, Mike Spreitzer wrote:
Robert Collins robe...@robertcollins.net wrote on 09/29/2013 02:21:28 AM:
Host not hypervisor I think; consider nova baremetal, where hypervisor
== machine that runs tftpd and makes IPMI calls, and host == place
where the user workload will
Hey all!
The job to automatically propose syncs from the openstack/requirements
repo went live today - as I'm sure you all noticed, since pretty much
everyone got a patch of at least some size.
The job works the same way as the translations job - it will propose a
patch any time the global repo
the risks.
Thank you!
On 10/02/2013 12:02 AM, Monty Taylor wrote:
On 10/01/2013 11:45 AM, Thomas Goirand wrote:
On 10/01/2013 10:02 PM, Jonathan Dowland wrote:
On Tue, Oct 01, 2013 at 09:45:17PM +0800, Thomas Goirand wrote:
Since I have already uploaded python-troveclient (currently waiting
On 10/01/2013 08:08 PM, Robert Collins wrote:
We'd like to get tuskar projects doing releases sooner rather than
later. For python-tuskarclient, this is pretty much a no-brainer : we
just need to start doing it.
Yup. Just do it.
However, for tuskar-ui and tuskar it's more complex.
#
Hi all!
I would like to continue serving the project on the OpenStack TC.
Background
--
I've been with this bad boy since before day 1, and you can pretty much
blame me for trunk gating. You can also blame me for the bzr days - so
I'm not going to try to claim that I'm always right. :)
+1
On 10/03/2013 12:28 AM, Iccha Sethi wrote:
Hey,
I would like to nominate Fei Long Wang(flwang) for glance core. I think Fei
has been an active reviewer/contributor to the glance community [1] and has
always been on top of reviews.
Thanks for the good work Fei!
Iccha
[1]
+1
On 10/03/2013 12:25 AM, Iccha Sethi wrote:
Hey,
I would like to nominate Zhi Yan Liu(lzydev) for glance core. I think Zhi has
been an active reviewer/contributor to the glance community [1] and has
always been on top of reviews.
Thanks for the good work Zhi!
Iccha
[1]
Hey!
Got a question on IRC which seemed fair game for a quick mailing list post:
Q: I see both addCleanup and tearDown in nova's test suite - which one
should I use for new code?
A: addCleanup
All new code should 100% of the time use addCleanup and not tearDown -
this is because addCleanups
On 10/08/2013 11:22 AM, Clint Byrum wrote:
I don't meant to pick on you personally Jiří, but I have singled this
message out because I feel you have captured the objections to Robert's
initial email well.
Darn. My pop-up window showed I don't meant to pick on you personally
so I rushed to go
On 12/09/2014 03:39 AM, Sean Dague wrote:
I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely.
1 - the entire H8* group. This doesn't function on python code, it
functions on git commit message, which makes it tough to run locally. It
also would be a reason to prevent
On 02/04/2015 12:48 PM, Michael Krotscheck wrote:
I agree. StoryBoard's storyboard-webclient project has a lot of existing
code already that's pretty well documented, but without knowing what
documentation system we were going to settle on we never put any rule
enforcement in place. If someone
On 02/04/2015 06:57 AM, Daniel P. Berrange wrote:
On Wed, Feb 04, 2015 at 11:58:03AM +0100, Thierry Carrez wrote:
The first one is performance -- each call would spawn a Python
interpreter which would then call the system command. This was fine when
there were just a few calls here and there,
On 01/17/2015 03:27 AM, ZhiQiang Fan wrote:
Hi, developers
I have observed that some source code files in our projects have been
announced as Copyright xxx, All rights reserved, and then followed by a
Apache License
Is this right? any conflict?
And if one company claims that it
On 02/10/2015 10:28 AM, Alexander Tivelkov wrote:
Hi folks,
One of the key features that we are adding to Glance with the
introduction of Artifacts is the ability to have multiple versions of
the same object in the repository: this gives us the possibility to
query for the latest version of
On 02/17/2015 07:58 AM, Daniel P. Berrange wrote:
On Tue, Feb 17, 2015 at 01:16:46PM +0100, Christian Berendt wrote:
On 02/17/2015 12:05 PM, Daniel P. Berrange wrote:
In section 4.(c) the LICENSE text says
(c) You must retain, in the Source form of any Derivative Works
that
I do not like how we are selecting names for our releases right now.
The current process is autocratic and opaque and not fun - which is the
exact opposite of what a community selected name should be.
I propose:
* As soon as development starts on release X, we open the voting for the
name of
On 01/27/2015 06:05 PM, Jonathan Bryce wrote:
On Jan 27, 2015, at 3:50 PM, Monty Taylor mord...@inaugust.com wrote:
I do not like how we are selecting names for our releases right now.
The current process is autocratic and opaque and not fun - which is the
exact opposite of what a community
with
decisions, however well meaning, that take place outside of the public
context.
So please accept my apology for my language - and please engage with me
in the discussion around how to make sure people don't inadvertently
begin to feel disenfranchised.
Thanks,
Monty
On 01/27/2015 04:50 PM, Monty
On 01/27/2015 10:35 PM, James E. Blair wrote:
Lauren Sell lau...@openstack.org writes:
Hey Monty,
I’d like to weigh in here, because I think there have been some
misunderstandings around Lemming-gate. I’m glad you raised your
concerns; it’s a good test of release naming for us all to
On 01/29/2015 11:06 AM, Morgan Fainberg wrote:
As a quick preface, today there is the assumption you can upgrade and
downgrade your SQL Schema. For the most part we do our best to test all of
this in our unit tests (do upgrades and downgrades land us in the same
schema). What isn’t clearly
On 01/28/2015 06:33 PM, Johannes Erdfelt wrote:
On Wed, Jan 28, 2015, Mike Bayer mba...@redhat.com wrote:
I can envision turning this driver into a total monster, adding
C-speedups where needed but without getting in the way of async
patching, adding new APIs for explicit async, and everything
On 01/28/2015 01:29 AM, Thierry Carrez wrote:
Monty Taylor wrote:
You'll notice that I did say in my suggestion that ANYONE should be able
to propose a name - I believe that would include non-dev people. Since
the people in question are marketing people, I would imagine that if any
of them
On 03/17/2015 09:07 AM, Monty Taylor wrote:
On 03/16/2015 08:32 PM, Robert Collins wrote:
On 17 March 2015 at 13:22, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Robert Collins's message of 2015-03-17 12:54:00 +1300:
I've raised this in reviews 157135 and 153966, but I think
On 03/16/2015 08:32 PM, Robert Collins wrote:
On 17 March 2015 at 13:22, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Robert Collins's message of 2015-03-17 12:54:00 +1300:
I've raised this in reviews 157135 and 153966, but I think it deserves
a thread of its own.
I think
On 03/21/2015 01:21 AM, Chris Friesen wrote:
Hi,
I've recently been playing around a bit with API microversions and I
noticed something that may be problematic.
The way microversions are handled, there is a monotonically increasing
MAX_API_VERSION value in
On 03/05/2015 12:02 AM, Nikhil Komawar wrote:
The python-glanceclient release management team is pleased to announce:
python-glanceclient version 0.16.1 has been released on Thursday, Mar 5th
around 04:56 UTC.
For more information, please find the details at:
On 03/24/2015 06:05 PM, Kyle Mestery wrote:
On Tue, Mar 24, 2015 at 9:56 AM, Doug Hellmann d...@doughellmann.com
wrote:
Excerpts from Mark McClain's message of 2015-03-24 10:25:31 -0400:
Echoing both Thierry and John. I support Mike’s decision to enforce the
requirement. Maintaining
On 03/25/2015 05:50 PM, Maru Newby wrote:
I am excited by the release of YAPF [1], a gofmt-like too for python.
I think it has the potential to simplify style enforcement, and as
much as I appreciate our current hacking checks, I’d be much happier
not requiring developers to manually conform
On 03/27/2015 07:21 AM, Sean Dague wrote:
On 03/26/2015 06:46 PM, Robert Collins wrote:
On 27 March 2015 at 09:14, Ryan Brown rybr...@redhat.com
wrote:
Ooof, that's huge. If we can configure it to be less
aggressive I love the *idea* of having everything formatted
semantically, but that's
On 04/01/2015 05:41 AM, Thierry Carrez wrote:
Joe Gordon wrote:
I am starting this thread based on Thierry's feedback on [0]. Instead
of writing the same thing twice, you can look at the rendered html from
that patch [1]. Neutron tried to go from core to maintainer but after
input from the
On 04/02/2015 06:22 PM, Brant Knudson wrote:
On Thu, Apr 2, 2015 at 4:52 PM, Boris Pavlovic bo...@pavlovic.me wrote:
Hi stackers,
Recently, I started working on speeding up Rally cli.
What I understand immediately is that I don't understand why it takes
700-800ms
to just run rally
On 04/03/2015 08:55 AM, Maish Saidel-Keesing wrote:
I was wondering..
Is the OpenStack CI/CD Infra using Heat in any way? Do the commits
trigger a new build of DevStack/OpenStack that is based on a Heat
Template or just the provisioning of a regular instance and then
deployment of code on
Sorry for top posting - I wasn't subscribed to the doc list before
clarkb told me about this thread. Warning ... rage coming ... if you
don't want to read rage on a Saturday, I recommend skipping this email.
a) There may be a doc bug here, but I'm not 100% convinced it's a doc
bug - I'll try to
On 04/26/2015 02:21 PM, Gregory Haynes wrote:
Excerpts from Steven Dake (stdake)'s message of 2015-04-23 23:27:00 +:
Hi folks,
I have spent the last couple of days trying to bring some sanity to the
image building process for Magnum.
I have found a tool which the Atomic upstream
On 04/24/2015 06:28 PM, David Medberry wrote:
On Fri, Apr 24, 2015 at 2:14 AM, Chris Dent chd...@redhat.com wrote:
What can and should the TC at large, and you specifically, do to ensure
quality improves for the developers, end-users and operators of
OpenStack as a full system, both as a
On 04/25/2015 09:49 AM, Jeremy Stanley wrote:
On 2015-04-25 12:12:15 +1200 (+1200), Robert Collins wrote:
[...]
I'd like to make that a little more official:
- put it in our docs
- stop testing python setup.py install.
[...]
And emit a clear error message? (Even if that just means
On 04/24/2015 08:12 PM, Robert Collins wrote:
In our pbr integration tests we ensure that 'python setup.py install'
works, as well as ensuring that 'pip install' works. But see
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015525.html
- for the last 18 months in pbr we've
April 2015 at 15:27, Monty Taylor mord...@inaugust.com wrote:
On 04/25/2015 09:49 AM, Jeremy Stanley wrote:
On 2015-04-25 12:12:15 +1200 (+1200), Robert Collins wrote:
[...]
I'd like to make that a little more official:
- put it in our docs
- stop testing python setup.py install
On 04/25/2015 11:46 AM, Monty Taylor wrote:
On 04/25/2015 11:33 AM, Dave Walker wrote:
I'm not going to pretend it is graceful... but is there a situation
where _ isn't correct?
Ooh. This is a worthy avenue to explore ...
Ok. After some chatting with fungi in IRC - I've got this:
https
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/30/2015 08:06 PM, John Dickinson wrote:
On Apr 30, 2015, at 9:52 AM, Jay Pipes jaypi...@gmail.com
wrote:
On 04/30/2015 12:40 PM, John Dickinson wrote:
Swift is a scalable and durable storage engine for storing
unstructured data. It's
On 05/01/2015 09:16 PM, Jamie Lennox wrote:
Hi all,
At around the time Barbican was applying for incubation there was a
discussion about supported WSGI frameworks. From memory the decision
at the time was that Pecan was to be the only supported framework and
that for incubation Barbican
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/04/2015 08:47 PM, Emilien Macchi wrote:
On 05/04/2015 10:37 PM, Rich Megginson wrote:
On 05/04/2015 07:52 PM, Mathieu Gagné wrote:
On 2015-05-04 9:15 PM, Rich Megginson wrote:
On 05/04/2015 06:03 PM, Mathieu Gagné wrote:
On 2015-05-04
On 05/08/2015 03:45 AM, Nikhil Manchanda wrote:
Comments and answers inline.
Li Tianqing writes:
[...]
1) why we put the trove vm into user's tenant, not the trove's
tenant? User can login on that vm, and that vm must connect to
rabbitmq. It is quite insecure.
what's
On 05/04/2015 03:53 PM, Robert Collins wrote:
Hi, I'd like to talk about how often we can and should release pbr,
and what criteria we should use for 1.0.
tl;dr: release weekly [outside of organisation-wide-freezes], do a 1.0
immediately.
pbr, like all our libraries affects everything
On 05/04/2015 04:15 PM, Robert Collins wrote:
On 5 May 2015 at 08:12, Monty Taylor mord...@inaugust.com wrote:
On 05/04/2015 03:53 PM, Robert Collins wrote:
I'm fine with that in principle - I tend to release personal libraries
pretty much as soon as something interesting hits them. I have
On 05/11/2015 02:05 PM, Dean Troyer wrote:
On Mon, May 11, 2015 at 11:44 AM, Rosa, Andrea (HP Cloud Services)
andrea.r...@hp.com wrote:
Agreed. Violating the HTTP spec is something that should be avoided.
Actually it is not violating the HTTP spec, from RFC:
A payload within a DELETE
On 04/14/2015 08:21 PM, Chris Dent wrote:
On Tue, 14 Apr 2015, Sean Dague wrote:
It's time to be honest about the level of support that comes with those
other backends, deprecate the plugability, and move on to more
interesting problems. We do have plenty of them to solve. :) Perhaps in
On 04/16/2015 07:41 AM, Lucas Alvares Gomes wrote:
Hi,
We have a couple of Openstack projects that uses WSME for their REST
APIs[1], but WSME project looks abandoned. The review stats are not good,
for the last 40 days the project didn't have a single review from a core
reviewer[2], the
On 04/12/2015 08:01 PM, James Polley wrote:
On Mon, Apr 13, 2015 at 9:12 AM, Monty Taylor mord...@inaugust.com wrote:
On 04/12/2015 06:43 PM, Robert Collins wrote:
Right now we do something that upstream pip considers wrong: we make
our requirements.txt be our install_requires.
Upstream
On 04/12/2015 06:43 PM, Robert Collins wrote:
Right now we do something that upstream pip considers wrong: we make
our requirements.txt be our install_requires.
Upstream there are two separate concepts.
install_requirements, which are meant to document what *must* be
installed to import
an official installation guide; no need to
expose newbies including myself to the complexity of v2.
Bernd
-Original Message-
From: Monty Taylor [mailto:mord...@inaugust.com]
Sent: Sunday, April 12, 2015 6:22 AM
To: OpenStack Development Mailing List (not for usage questions);
openstack-d
On 04/18/2015 10:44 AM, Fox, Kevin M wrote:
Replying inline.
-Original Message- From: Monty Taylor
[mailto:mord...@inaugust.com] Sent: Friday, April 17, 2015 7:53 PM
To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev]
[Nova][Neutron] Linuxbridge as the default
On 04/14/2015 01:22 PM, Clint Byrum wrote:
Hello! There's been some recent progress on python3 compatibility for
core libraries that OpenStack depends on[1], and this is likely to open
the flood gates for even more python3 problems to be found and fixed.
Recently a proposal was made to make
On 04/17/2015 06:48 PM, Rochelle Grober wrote:
I know the DevStack issue seems to be solved, but I had to
respond.inline
From: Fox, Kevin M [mailto:kevin@pnnl.gov] Sent: Friday, April
17, 2015 12:28 To: OpenStack Development Mailing List (not for usage
questions) Subject: Re:
201 - 300 of 787 matches
Mail list logo
