That sounds essentially correct. Note that all 15 vms aren't used in a
normal devtest run, but we create them all anyway because of some
difficulties adding new environments in some situations (namely CI, I
believe).
On 08/05/2014 11:27 AM, LeslieWang wrote:
> Hi Ben,
> Thanks for your reply.
>
LGTM. Plenty of things I could add to your list, but they're all
post-import. :-)
-Ben
On 08/07/2014 01:58 PM, Yuriy Taraday wrote:
> Hello, oslo cores.
>
> I've finished polishing up oslo.concurrency repo at [0] - please take a
> look at it. I used my new version of graduate.sh [1] to generate
On 08/06/2014 05:35 PM, Yuriy Taraday wrote:
> Oh, looks like we got a bit of a race condition in messages. I hope you
> don't mind.
>
>
> On Wed, Aug 6, 2014 at 11:00 PM, Ben Nemec wrote:
>
>> On 08/06/2014 01:42 PM, Yuriy Taraday wrote:
>>> On Wed, Aug 6
Unfortunately this is a known issue. We're working on a fix:
https://bugs.launchpad.net/oslo/+bug/1327946
On 08/07/2014 03:57 AM, Alex Xu wrote:
> When I startup nova-network, it stuck at trying get lock for ebtables.
>
> @utils.synchronized('ebtables', external=True)
> def ensure_ebtables_rules
On 08/06/2014 01:42 PM, Yuriy Taraday wrote:
> On Wed, Aug 6, 2014 at 6:20 PM, Ben Nemec wrote:
>
>> On 08/06/2014 03:35 AM, Yuriy Taraday wrote:
>>> I'd like to stress this to everyone: I DO NOT propose squashing together
>>> commits that should belong to
On 08/06/2014 12:41 AM, Yuriy Taraday wrote:
> On Wed, Aug 6, 2014 at 1:17 AM, Ben Nemec wrote:
>
>> On 08/05/2014 03:14 PM, Yuriy Taraday wrote:
>>> On Tue, Aug 5, 2014 at 10:48 PM, Ben Nemec
>> wrote:
>>>
>>>> On 08/05/2014 10:51 AM, ZZelle wr
ng to use this feature, and history suggests if it can be abused, it
will be.
>
> On Wed, Aug 6, 2014 at 12:03 PM, Martin Geisler wrote:
>
>> Ben Nemec writes:
>>
>>> On 08/05/2014 03:14 PM, Yuriy Taraday wrote:
>>>>
>>>> When you're dev
On 08/05/2014 03:14 PM, Yuriy Taraday wrote:
> On Tue, Aug 5, 2014 at 10:48 PM, Ben Nemec wrote:
>
>> On 08/05/2014 10:51 AM, ZZelle wrote:
>>> Hi,
>>>
>>>
>>> I like the idea ... with complex change, it could useful for the
>>> understa
On 08/05/2014 10:51 AM, ZZelle wrote:
> Hi,
>
>
> I like the idea ... with complex change, it could useful for the
> understanding to split it into smaller changes during development.
I don't understand this. If it's a complex change that you need
multiple commits to keep track of locally, why
We should take this discussion off the dev list. It's really a usage
question for instack from what I see. Can you possibly hop on #tripleo
on freenode to discuss?
For reference, I believe I've seen the same problem using instack for
icehouse with a qpid version that's too new. Not sure if that
On 08/04/2014 09:46 AM, LeslieWang wrote:
> Dear all,
> Looking at devtest pages at TripleO wiki
> http://docs.openstack.org/developer/tripleo-incubator/devtest.html. I thought
> all variables and configurations of devtest are for true bare-metal because I
> see diskimage-builder options of both
On 2014-07-17 09:37, Russell Bryant wrote:
> On 07/16/2014 10:30 AM, John Garbutt wrote:
>> On 16 July 2014 14:07, Thierry Carrez wrote:
>>> Daniel P. Berrange wrote:
On Wed, Jul 16, 2014 at 11:57:33AM +, Tim Bell wrote:
> It seems a pity to archive the comments and reviewer lists alo
On 2014-07-23 13:25, gordon chung wrote:
>> I left a comment on one of the commits, but in general here are my thoughts:
>> 1) I would prefer not to do things like switch to oslo.i18n outside of
>> Gerrit. I realize we don't have a specific existing policy for this, but
>> doing that signifi
I left a comment on one of the commits, but in general here are my
thoughts:
1) I would prefer not to do things like switch to oslo.i18n outside of
Gerrit. I realize we don't have a specific existing policy for this, but
doing that significant work outside of Gerrit is not desirable IMHO. It
n
For everyone's reference, the tripleo-specs stats can be found here:
http://www.nemebean.com/reviewstats/tripleo-specs-30.txt
Note that looking at the stats, over 30 days 1 review per week is only
4, which most of our cores are already doing anyway. I'm not sure
codifying a requirement to do at l
7;s where we hang out.
>
> Ben,
> I can help as well.
>
> thanks,
> -- dims
>
> On Tue, Jul 22, 2014 at 6:38 AM, Yuriy Taraday wrote:
>> Hello, Ben.
>>
>> On Mon, Jul 21, 2014 at 7:23 PM, Ben Nemec wrote:
>>>
>>> Hi all,
>>>
&
Hi all,
The oslo.serialization and oslo.concurrency graduation specs are both
approved, but unfortunately I haven't made as much progress on them as I
would like. The serialization repo has been created and has enough acks
to continue the process, and concurrency still needs to be started.
Also
nts to use this as a dropin they can still do "from
oslo.serialization import jsonutils as json"
>
> /Ihar
>
>
>> -Josh
>
>> On Jul 15, 2014, at 10:42 AM, Ben Nemec
>> wrote:
>
>>> And the link, since I forgot it before:
>>> https:
And the link, since I forgot it before:
https://github.com/cybertron/oslo.serialization
On 07/14/2014 04:59 PM, Ben Nemec wrote:
> Hi oslophiles,
>
> I've (finally) started the graduation of oslo.serialization, and I'm up
> to the point of having a repo on github that
On 07/14/2014 04:21 PM, Matt Riedemann wrote:
>
>
> On 7/14/2014 4:09 PM, Matt Riedemann wrote:
>> I opened bug 1341777 [1] against glance but it looks like it's due to
>> the default log level for requests.packages.urllib3.connectionpool in
>> oslo's log module.
>>
>> The problem is this warning
Hi oslophiles,
I've (finally) started the graduation of oslo.serialization, and I'm up
to the point of having a repo on github that passes the unit tests.
I realize there is some more work to be done (e.g. replacing all of the
openstack.common files with libs) but my plan is to do that once it's
+1. In my experience they've both demonstrated that they know what
they're doing.
I think the bikeshedding/grammar nits on specs is kind of a separate
issue that will need to be worked out in general. It's still very early
on in this new *-specs repo world, and I think everyone's still trying
to
FWIW, I believe TripleO will need this if we're going to be able to do
https://blueprints.launchpad.net/tripleo/+spec/tripleo-on-openstack
Being able to have instances without IPs assigned is basically required
for that.
-Ben
On 07/11/2014 04:41 PM, Brent Eagles wrote:
> Hi,
>
> A bug titled "C
On 07/08/2014 11:05 PM, Joe Gordon wrote:
> On Tue, Jul 8, 2014 at 8:54 PM, James Polley wrote:
>
>> It may not have been clear from the below email, but clarkb clarifies on
>> https://bugs.launchpad.net/openstack-ci/+bug/1294381 that the infra team
>> is no longer maintaining pypi-mirror
>>
>> T
ut I
think it shows a workable way forward with this.
I'll get a spec written up so we can have a formal discussion over
requirements and implementation.
Thanks.
-Ben
>
> -Rob
>
>
>
> On 4 July 2014 15:12, Ben Nemec wrote:
>> I've recently been looking in
I've recently been looking into using dracut to build the
deploy-ramdisks that we use for TripleO. There are a few reasons for
this: 1) dracut is a fairly standard way to generate a ramdisk, so users
are more likely to know how to debug problems with it. 2) If we build
with dracut, we get a lot o
+27, -2401
Wow, that's pretty painless. Were there earlier patches to Neutron to
prepare for the transition or was it really that easy?
On 07/03/2014 07:34 AM, Salvatore Orlando wrote:
> No I was missing everything and kept wasting time because of alembic.
>
> This will teach me to keep my mout
Please don't send review requests to the list. The preferred methods
are discussed here:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
Thanks.
-Ben
On 07/01/2014 03:45 AM, Xurong Yang wrote:
> Hi folks,
>
> Could anyone please review this spec for adding a new A
I'm far from an oslo.messaging expert, but a few general thoughts below.
On 06/30/2014 02:34 PM, Alexei Kornienko wrote:
> Hello,
>
>
>> My understanding is that your analysis is mostly based on running a
>> profiler against the code. Network operations can be bottlenecked in
>> other places.
>>
default. This way we can reduce the amount of cut
>> and pasted code (thank you to Ben Nemec for this idea).
>
> All sounds good to me, apart from a pet peeve on 'contrib' directories.
>
> What does 'contrib' mean? 'contributed'? What exa
Whoops, sorry, I didn't realize a tox.ini was required to release the
project. We do actually need to push this to pypi because it's going to
be a dep of diskimage-builder, so although there is currently no Python
code in the project it needs to be pip installable anyway (similar to
tripleo-image-
On 06/23/2014 10:30 AM, Monty Taylor wrote:
> On 06/23/2014 11:24 AM, Ben Nemec wrote:
>> On 06/23/2014 10:02 AM, Doug Hellmann wrote:
>>> On Mon, Jun 23, 2014 at 10:38 AM, Ben Nemec wrote:
>>> On 06/23/2014 08:41 AM, Julien Danjou wrote:
>>>>>> Hi th
On 06/23/2014 10:02 AM, Doug Hellmann wrote:
> On Mon, Jun 23, 2014 at 10:38 AM, Ben Nemec wrote:
> On 06/23/2014 08:41 AM, Julien Danjou wrote:
>>>> Hi there,
>>>>
>>>> We discovered a problem in pylockfile recently, and after
>>>> discus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/23/2014 08:41 AM, Julien Danjou wrote:
> Hi there,
>
> We discovered a problem in pylockfile recently, and after
> discussing with its current maintainer, it appears that more help
> and workforce would be require:
>
> https://github.com/smonta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/23/2014 06:18 AM, Sean Dague wrote:
> On 06/22/2014 03:04 PM, Jay Pipes wrote:
>> On 06/20/2014 02:07 PM, Sean Dague wrote:
>>> After seeing a bunch of code changes to enforce new hacking
>>> rules, I'd like to propose dropping some of the rules
On 06/18/2014 05:45 AM, Elena Ezhova wrote:
> Hello!
>
> I have been exploring bugs connected with using devstack with zmq [1], [2],
> [3] and experimenting with various configurations in attempt to make zmq
> work with projects which have moved to oslo.messaging. It turned out that
> there is a n
Hi Oslo liaisons (and anyone else reading this because of the [all] tag),
For the oslo.log graduation, we're trying to make the default logging
parameters generic enough to be useful to all projects, instead of the
generally Nova-centric ones we have today.
The reason I'm sending this is to bring
On 06/17/2014 10:43 AM, Stefano Maffulli wrote:
> [trimming reply-to to OpenStack Development since I don't think that
> infra is the right venue to discuss this]
>
> On 06/13/2014 10:08 AM, trinath.soman...@freescale.com wrote:
>> I have two scenarios to deal with.
>>
>> [1] A change takes two mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/17/2014 09:52 AM, John Griffith wrote:
> On Tue, Jun 17, 2014 at 6:51 AM, Armando M.
> wrote:
>
>> I wonder what the turnaround of trivial patches actually is, I
>> bet you it's very very small, and as Daniel said, the human
>> burden is rather
On 06/16/2014 06:18 PM, Ryan Brady wrote:
>
>
> - Original Message -
>> From: "Gregory Haynes"
>> To: "openstack-dev"
>> Sent: Monday, June 16, 2014 5:49:25 PM
>> Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
>>
Id also like to propose that if we decide ag
On 06/16/2014 05:46 PM, Ben Nemec wrote:
> On 06/16/2014 04:46 PM, Joe Gordon wrote:
>> On Mon, Jun 16, 2014 at 2:33 PM, Sean Dague wrote:
>>
>>> On 06/16/2014 05:06 PM, Ben Nemec wrote:
>>>> On 06/16/2014 12:01 PM, Sean Dague wrote:
>>>>> On 06
On 06/16/2014 04:46 PM, Joe Gordon wrote:
> On Mon, Jun 16, 2014 at 2:33 PM, Sean Dague wrote:
>
>> On 06/16/2014 05:06 PM, Ben Nemec wrote:
>>> On 06/16/2014 12:01 PM, Sean Dague wrote:
>>>> On 06/16/2014 12:44 PM, Ben Nemec wrote:
>>>>> On 06/16/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/16/2014 12:01 PM, Sean Dague wrote:
> On 06/16/2014 12:44 PM, Ben Nemec wrote:
>> On 06/16/2014 08:37 AM, Thierry Carrez wrote:
>>> Sean Dague wrote:
>>>> Hacking 0.9 series was released pretty late for Juno. T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/16/2014 08:37 AM, Thierry Carrez wrote:
> Sean Dague wrote:
>> Hacking 0.9 series was released pretty late for Juno. The entire
>> check queue was flooded this morning with requirements proposals
>> failing pep8 because of it (so at 6am EST we we
On 06/13/2014 11:03 AM, John Griffith wrote:
> On Fri, Jun 13, 2014 at 9:52 AM, Ben Nemec wrote:
>
>> Please don't send review requests to the openstack-dev list. The
>> correct procedure is outlined here:
>>
>> http://lists.openstack.org/pipermail/opens
Please don't send review requests to the openstack-dev list. The
correct procedure is outlined here:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
Thanks.
-Ben
On 06/12/2014 10:20 PM, Yuzhou (C) wrote:
> Hi all,
>
> I have submit a blueprint about deferred d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/12/2014 06:40 AM, Sean Dague wrote:
> Current gate-tempest-dsvm-virtual-ironic has only a 65% pass rate
> *in the gate* over the last 48 hrs -
> http://logstash.openstack.org/#eyJzZWFyY2giOiJidWlsZF9uYW1lOmdhdGUtdGVtcGVzdC1kc3ZtLXZpcnR1YWwtaXJvb
On 06/12/2014 02:50 AM, bt...@163.com wrote:
> Hi，everybody.
> I use packstack to install openstack, but I have found a few questions:
> (Centos 6.5 os)
> 1) The directory /var/lib/glance is not big enough to store the images.
> I modify the config files in the file /etc/glance/glance-
Please do not cross-post questions between openstack and openstack-dev.
This doesn't sound development-related, so the appropriate place for
this discussion is the openstack list.
Thanks.
-Ben
On 06/12/2014 03:52 AM, 严超 wrote:
> Hi, All:
> I print *"nova --debug list "*, and got nothin
Please don't send review requests to the list. See the preferred
methods here:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
Thanks.
-Ben
On 06/12/2014 10:07 AM, Robert Li (baoli) wrote:
> Hi,
>
> The SR-IOV work depends on this fix. It has got +1’s for quite so
On 06/10/2014 10:09 AM, Duncan Thomas wrote:
> On 10 June 2014 15:07, Mark McLoughlin wrote:
>
>> Exposing which configurations are actively "tested" is a perfectly sane
>> thing to do. I don't see why you think calling this "certification" is
>> necessary to achieve your goals.
>
> What is cert
Hi all,
While the oslo-specs repository has been available for a while and a
number of specs proposed, we hadn't agreed on a process for actually
approving them (i.e. the normal 2 +2's or something else). This was
discussed at the Oslo meeting last Friday and the method decided upon by
the people
Please don't send review requests to the list. The preferred methods of
requesting reviews are explained here:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
Thanks.
-Ben
On 06/07/2014 12:31 AM, Kanzhe Jiang wrote:
> The serviceBase and insertion spec has been up
Great! I know I'm not much use reviewing oslo.messaging patches, so now
I can feel slightly less guilty about it. :-)
-Ben
On 06/06/2014 09:57 AM, Mark McLoughlin wrote:
> Mehdi has been making great contributions and reviews on oslo.messaging
> for months now, so I've added him to oslo.messagin
Please don't make review requests on openstack-dev. See
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
for details.
Thanks.
-Ben
On 06/05/2014 10:51 PM, Jian Hua Geng wrote:
>
>
> Hi All,
>
> Can anyone help to review this patch
> https://review.openstack.org/#
On 06/05/2014 04:48 AM, Thierry Carrez wrote:
> Hey everyone,
>
> With all those mid-cycle sprints being proposed I found it a bit hard to
> track them all (and, like, see if I could just attend one). I tried to
> list them all at:
>
> https://wiki.openstack.org/wiki/Sprints
>
> I'm pretty sure
This sounds like a reasonable thing to open a bug against Horizon on
Launchpad.
On 06/04/2014 06:25 PM, Martinx - ジェームズ wrote:
> Hello Stackers!
>
> I'm using SPICE Consoles now but, there is no button to send "Ctrl + Alt +
> Del" to a Windows Instance, so, it becomes very hard to log in into tho
. What I am trying to accomplish is to pass
>> the flat_injected file through the instance metadata during the
>> boot time and use it during the config drive network
>> configuration rather setting the flag at the hypervisor level.
>>
>> Regards, Yashwanth Vempati
&g
On 05/30/2014 06:58 AM, Jaromir Coufal wrote:
> On 2014/30/05 10:00, Thomas Spatzier wrote:
>> Excerpt from Zane Bitter's message on 29/05/2014 20:57:10:
>>
>>> From: Zane Bitter
>>> To: openstack-dev@lists.openstack.org
>>> Date: 29/05/2014 20:59
>>> Subject: Re: [openstack-dev] [TripleO] [Ironic
On 05/30/2014 05:29 PM, ebaysf, yvempati wrote:
> Hello all,
> I am new to the openstack community and I am looking for feedback.
>
> We would like to implement a feature that allows user to pass flat_injected
> flag through instance metadata. We would like to enable this feature for
> images th
This is a development list, please ask usage questions on the users
list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 05/28/2014 07:58 AM, Ajaya Agrawal wrote:
> Hi All,
>
> We want to introduce a role of project admin in our cloud who can add users
> only in t
+1 to code names. I didn't feel strongly enough about it to object to
the name change for oslo-specs, but we do refer to the program as "oslo"
pretty much _everywhere_ else.
-Ben
On 05/23/2014 05:27 AM, James E. Blair wrote:
> Hi,
>
> With apologies to the specs repos we just created, the more
On 05/23/2014 12:23 PM, Nachi Ueno wrote:
> Hi folks
>
> I believed we should link bug or bp for any commit except automated
> commit by infra.
> However, I found also there is no written policy for this.
> so may be, I'm wrong for here.
>
> The reason, we need bug or bp linked , is
>
> (1) Tria
On 05/22/2014 06:31 PM, Johannes Erdfelt wrote:
> I noticed recently that some tests are being skipped in the Nova gate.
>
> Some will always be skipped, but others are conditional.
>
> In particular the ZooKeeper driver tests are being skipped because an
> underlying python module is missing.
>
This is a discussion that definitely belongs on the users list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 05/23/2014 01:36 AM, Aaron Rosen wrote:
> Do you have a loadbalancer or something that limits the request time in the
> path? That would be my guess, you
For everyone's awareness, Alexis proposed a spec related to this:
https://review.openstack.org/#/c/94910
-Ben
On 05/20/2014 05:05 PM, James Polley wrote:
> I spoke to JP offline and confirmed that the link to 85418 should have been
> a link to https://review.openstack.org/#/c/88252
>
> I think t
On 05/21/2014 12:11 PM, Igor Kalnitsky wrote:
>> So, write:
>>
>> LOG.debug(u'Could not do whatever you asked: %s', exc)
>>
>> or just:
>>
>> LOG.debug(exc)
>
> Actually, that's a bad idea to pass an exception instance to
> some log function: LOG.debug(exc). Let me show you why.
>
> Here
On 05/14/2014 09:38 AM, Victor Stinner wrote:
> Le mardi 13 mai 2014, 07:31:34 Doug Hellmann a écrit :
>> Since we think we have been able to solve all of the issues we were
>> having with namespace packages before, ...
>
> I just tried to start my DevStack and again, I had issues with a "builtin"
Hi,
As you can see on https://review.openstack.org/#/c/77924/ I was
fortunate enough to find a new way to trigger a Jenkins loop. In
talking to infra, it seems the problem occurs when a comment is added to
an older patch set (as in patch set 2 of a change with 3 patch sets) of
a change that
This is a development list, and your question sounds more usage-related.
Please ask your question on the users list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 05/09/2014 06:57 AM, Shyam Prasad N wrote:
Hi,
I have a two node swift cluster receiving contin
Hi,
This is a development list, and your question sounds more usage-related.
You'll probably have better luck asking on the users list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 05/08/2014 09:04 AM, Taurus H wrote:
Hi,all!
I encountered the foll
On 05/06/2014 01:13 PM, Joe Gordon wrote:
On Mon, May 5, 2014 at 10:56 AM, Ben Nemec mailto:openst...@nemebean.com>> wrote:
On 05/05/2014 10:02 AM, ChangBo Guo wrote:
Hi Stackers,
I find some common code style would be avoided while I'm
rev
On 05/05/2014 10:02 AM, ChangBo Guo wrote:
Hi Stackers,
I find some common code style would be avoided while I'm reviewing code
,so think these check would
be nice to move into local hacking. The local hacking can ease reviewer
burden.
The idea from keystone blueprint [1].
Hacking is a great st
On 04/09/2014 11:11 AM, Doug Hellmann wrote:
I have started writing up some general steps for adding oslo libs to
projects, and I would like some feedback about the results. They can't
go into too much detail about specific changes in a project, because
those will vary by library and project. I w
On 04/29/2014 02:48 PM, Doug Hellmann wrote:
I have exported the gettextutils code and related files to a new git
repository, ready to be imported as oslo.i18n. Please take a few
minutes to look over the files and give it a sanity check.
https://github.com/dhellmann/oslo.i18n
Thanks,
Doug
No
On 05/01/2014 12:27 PM, Hao Wang wrote:
Hi,
I have got one question: if there is something wrong with a test case,
and it causes the review can proceed, what should I do?
You mean you hit a bug in a test case? If so, see the link Jenkins
posted to the review:
https://wiki.openstack.org/wiki
On 05/01/2014 12:11 PM, Thomas Goirand wrote:
Hi,
I've searched launchpad, and didn't find out. This didn't work:
https://launchpad.net/oslo.config/+bugs
Should I report bugs at:
https://launchpad.net/oslo/+bugs
Yes. All of the Oslo projects are tracked under the same LP project
because Lau
Hi,
As requested, I have put together some etherpads for my summit sessions.
The first is for the TripleO development and test environment discussion:
https://etherpad.openstack.org/p/juno-summit-tripleo-environment
And for the unit testing topic I added to the bottom of Derek's etherpad
fo
Please don't send review requests to the list. The preferred methods
are discussed here:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
Thanks.
-Ben
On 04/29/2014 04:45 AM, sxmatch wrote:
Hi,guys:
There is a nova-specs "add force detach volume to nova"
（https
On 04/29/2014 03:16 AM, Macdonald-Wallace, Matthew wrote:
Hi all,
I have a patch in flight at the moment [0] to install check_mk server and
compliment the already merged installation of check_mk agent [1] so my thoughts
are now turning to how we would recommend adding new service checks.
The
This is a development list, and your question sounds usage-related. I
suggest asking again on the users list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 04/29/2014 12:53 AM, abhishek jain wrote:
Hi all
I'm getting follwoing error when trying to run nova-c
On 04/28/2014 01:04 AM, Robert Collins wrote:
I've collated the votes and put a proposed selection of talks (some
sessions merged) up; I'm going to push a draft timetable as soon as I
finish clicking on the clicky thing .:).
If your session has been selected you now need to:
- ensure there is
On 04/15/2014 10:32 PM, Clint Byrum wrote:
Excerpts from Steve Baker's message of 2014-04-15 16:30:32 -0700:
On 15/04/14 13:30, Clint Byrum wrote:
Excerpts from Ben Nemec's message of 2014-04-14 15:41:23 -0700:
Right now the os-*-config projects default to looking for their files in
/opt/stack
Makes sense to me, +1.
On 04/21/2014 11:39 AM, Doug Hellmann wrote:
I propose that we add Victor Stinner (haypo on freenode) to the Oslo
core reviewers team.
Victor is a Python core contributor, and works on the development team
at eNovance. He created trollius, a port of Python 3's tulip/async
This is a development list and your question sounds like a usage one. I
suggest you ask it on the users list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 04/21/2014 05:34 AM, Arindam Choudhury wrote:
Hi,
As per I understand, onwards qemu 1.3 release all qe
The best way to resolve this is to contact Alan directly on either IRC
or email. Nobody else can remove his -2.
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
Thanks.
-Ben
On 04/21/2014 01:56 AM, ZhiQiang Fan wrote:
Hi, Ceilometer dev cores,
There is a patch
Please don't make review requests on the list. Details here:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
Thanks.
-Ben
On 04/20/2014 02:44 PM, Macdonald-Wallace, Matthew wrote:
Hi all,
Can I please ask for some reviews on the following:
https://review.opens
This is a development list, and this sounds like a usage question so I
would suggest that you ask on the users list instead:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 04/18/2014 09:36 PM, shenwei9008 wrote:
I hava a problem that in windows 7 VM about the n
This is a development list, and your question sounds more appropriate
for the users list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 04/16/2014 01:35 PM, Arunkumar Achutha wrote:
Hi,
While installing cinder in openstack i was encountered the
followin
On 04/16/2014 08:11 AM, Jay Pipes wrote:
On Wed, 2014-04-16 at 14:55 +0800, Chen CH Ji wrote:
Hi
There are 3 types of unit test existing now (stub, mox
and mock)
Several code reviewers suggest to use mock instead of
using the other 2 and I am following it, but I
On 04/15/2014 02:44 PM, Clint Byrum wrote:
Excerpts from Ben Nemec's message of 2014-04-14 09:26:17 -0700:
tldr: I propose we use bash explicitly for all diskimage-builder scripts
(at least for the short-term - see details below).
This is something that was raised on my linting changes to enabl
On 04/15/2014 01:44 PM, Robert Collins wrote:
I've been watching the nova process, and I think its working out well
- it certainly addresses:
- making design work visible
- being able to tell who has had input
- and providing clear feedback to the designers
I'd like to do the same thing fo
Right now the os-*-config projects default to looking for their files in
/opt/stack, with an override env var provided for other locations. For
packaging purposes it would be nice if they defaulted to a more
FHS-compliant location like /var/lib. For devtest we could either
override the env va
would like to stop
trying to support not-bash unless someone else wants to step up and own
that effort.
Thanks for the input.
-Ben
Doug
On Mon, Apr 14, 2014 at 12:26 PM, Ben Nemec wrote:
tldr: I propose we use bash explicitly for all diskimage-builder scripts (at
least for the short-term
tldr: I propose we use bash explicitly for all diskimage-builder scripts
(at least for the short-term - see details below).
This is something that was raised on my linting changes to enable set -o
pipefail. That is a bash-ism, so it could break in the
diskimage-builder scripts that are run us
This sounds like a question for either the users list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
or the operators list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Thanks.
-Ben
On 04/10/2014 09:07 PM, Sumit Gaur wrote:
Hi
I understand that Sw
This sounds like a question for the users list, since you're using
distro packages:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 04/10/2014 01:45 AM, Martinx - ジェームズ wrote:
Guys,
I'm trying to create an Instance here at my lab but, I'm seeing the
following e
On 04/08/2014 02:47 PM, Gregory Haynes wrote:
On Tue, Apr 8, 2014, at 12:30 PM, Jay Dobies wrote:
On 04/07/2014 07:50 PM, Robert Collins wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdon
I'm comfortable with committing to at least 3 reviews a day and promise
to wield the aw
On 04/08/2014 11:24 AM, Victor Stinner wrote:
Hi,
Le mardi 8 avril 2014, 10:05:31 Doug Hellmann a écrit :
The openstack.common module also known as "Oslo Incubator" or "OpenStack
Common Libraries" has 44 dependencies. IMO we reach a point where it
became
too huge. Would it be possible to split
On 04/08/2014 08:12 AM, victor stinner wrote:
Hi,
Olso Incubator runs tests using testr on Python 2, but it uses nosetests on
Python 3 to only run a subset of the test suite (modules and tests ported to
Python 3). In my latest patch for Oslo Incubator (gettext), Ben Nemec wrote:
"I thi
501 - 600 of 771 matches
Mail list logo
