Phil,
I am reviewing the existing “check_instance_lock” implementation to see
how it might be leveraged. Off the cuff, it looks pretty much what we
need. I need to look into the permissions to better understand how one
can “lock” and instance.
Thanks for the guidance.
Justin Hopper
Software
the instance lock is a mechanism that prevent non-admin user to operate on
the instance (resize, etc, looks to me snapshot is not currently included)
the permission is a wider concept that major in API layer to allow or
prevent user in using the API , guess instance lock might be enough for
Hi List,
I had few Qs on the implementation of manage_existing and unmanage API
extns
1) For LVM case, it renames the lv.. isn't it better to use name_id (one
used during cinder migrate to keep id same for a diff backend name/id) to
map cinder name/id to backend name/id and thus avoid
On 08/04/14 01:50, Robert Collins wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdon
-1, there's a typo in jdob's nick ;-)
In all seriousness, I support all of them being added to core.
On 4 April 2014 08:55, Chris Jones c...@tenshu.net wrote:
Hi
+1 for your
Sean,
I've added Salvatore's code review of Hide ipv6 subnet API attributes to
our discussion list.
https://review.openstack.org/#/c/85869/
Xuhan
On Tue, Apr 8, 2014 at 4:49 AM, Collins, Sean
sean_colli...@cable.comcast.com wrote:
Hi,
I've added a section for tomorrow's agenda, please
On Mon, 2014-04-07 at 15:24 -0400, Doug Hellmann wrote:
We can avoid adding to the problem by putting each new library in its
own package. We still want the Oslo name attached for libraries that
are really only meant to be used by OpenStack projects, and so we need
a naming convention. I'm not
On Apr 8, 2014, at 3:28 AM, Mark McLoughlin mar...@redhat.com wrote:
On Mon, 2014-04-07 at 15:24 -0400, Doug Hellmann wrote:
We can avoid adding to the problem by putting each new library in its
own package. We still want the Oslo name attached for libraries that
are really only meant to be
Howdy Stackers!
There is a security group problem has been bothering me, but I do not know
whether is appropriate to consult in there! For a security group rule, it will
convert to iptable rules in compute node, but a iptable rule '-m state --state
RELATED,ESTABLISHED -j RETURN' confuse me,
Hi Sean,
That's OK for me, thanks for your work.
Thanks Best Regards
Yu Da Zhao(于大钊)
--
Cloud Solutions OpenStack Development
China Systems Technology Laboratory in Beijing
Email: d...@cn.ibm.com
Tel: (86)10-82450677
+1 for the -core changes
jdon sounds like a pretty cool Mafia name, +1 for Don Jay
On 04/08/2014 09:10 AM, Tomas Sedovic wrote:
On 08/04/14 01:50, Robert Collins wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdon
-1, there's a typo in jdob's nick ;-)
In all seriousness, I
Hi Neutron stackers,
I have a question about how to fix the problem of DHCP port address being
SNAT by L3 agent.
I have my neutron DHCP agent and L3 agent running on the same network node,
and I disabled namespace usage in both agent configuration. I have one
router created with one external
+1 to this:
nova:
config:
default.compute_manager:
ironic.nova.compute.manager.ClusterComputeManager
cells.driver: nova.cells.rpc_driver.CellsRPCDriver
Adding a generic mechanism like this and having everything configurable
seems like a best option to me.
On 04/08/2014 01:51
Thanks Mainn for putting this together, looks like a fairly precise list
of things
we need to do in J.
On 04/07/2014 03:36 PM, Tzu-Mainn Chen wrote:
Hi all,
One of the topics of discussion during the TripleO midcycle meetup a few weeks
ago was the direction we'd like to take Tuskar during
Sean,
Sure. Thanks for fixing this.
Xuhan
On Tue, Apr 8, 2014 at 3:42 PM, Da Zhao Y Yu d...@cn.ibm.com wrote:
Hi Sean,
That's OK for me, thanks for your work.
Thanks Best Regards
Yu Da Zhao(于大钊)
--
Cloud Solutions OpenStack
Hi,
I have some issues when running unit tests in OpenStack. I would like to help,
but I don't know where I should start and how I can fix these bugs. My use case
is to run unit tests and rerun a single test if one or more tests failed. Well,
it should be the most basic use case, no?
(1)
From: Steven Dake sd...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 07/04/2014 21:45
Subject: Re: [openstack-dev] [heat] Managing changes to the Hot
Specification (hot_spec.rst)
On 04/07/2014 11:01 AM, Zane Bitter
Hi, Stackers,
For Amazon, after calling ModifyInstanceAttribute API , the instance
must be stopped.
In fact, the hypervisor can online-adjust these attribute. But amzon
and openstack do not support it.
So I want to know what are your advice about introducing
Hi!
In this method q is query argument and used for filtering response.
In code you may set this parameter with list of dicts, like this:
q=[{field: resource_id, value: a, op: eq}]
More examples of queries at
Hi Victor,
This page is worth it : https://wiki.openstack.org/wiki/Testr
Comments inline.
-Sylvain
2014-04-08 10:13 GMT+02:00 victor stinner victor.stin...@enovance.com:
Hi,
I have some issues when running unit tests in OpenStack. I would like to
help, but I don't know where I should start
Made a typo,
2014-04-08 10:41 GMT+02:00 Sylvain Bauza sylvain.ba...@gmail.com:
IMO it's a huge bug in the testr tool: testr run command should not
write binary data into stdout. It makes development very hard.
That's happening when testr is trying to locate all unittests classes.
Oh, I already got feedback from colleagues :-) Thanks.
(1) First problem: if a Python module cannot be loaded, my terminal is
flooded with a binary stream which looks like:
...
On Mon, Apr 07 2014, Doug Hellmann wrote:
We can avoid adding to the problem by putting each new library in its
own package. We still want the Oslo name attached for libraries that
are really only meant to be used by OpenStack projects, and so we need
a naming convention. I'm not entirely
On 07/04/14 18:05, Jan Provazník wrote:
On 04/07/2014 03:49 PM, Roman Podoliaka wrote:
2. HA the neutron node. For each neutron services/agents of
interest (neutron-dhcp-agent, neutron-l3-agent,
neutron-lbaas-agent ... ) fix any issues with running these in
HA - perhaps there are none \o/?
On 07/04/14 16:49, Roman Podoliaka wrote:
Hi all,
Perhaps, we should file a design session for Neutron-specific questions?
that's a good idea - unfortunately I won't be at summit... if there is
more interest and you do go ahead with this please let me know I will
try and join by hangout for
On 07/04/14 15:56, Dmitriy Shulyak wrote:
Hi Marios, thanks for raising this.
There is in progress blueprint that should address some issues with neutron
ha deployment -
https://blueprints.launchpad.net/neutron/+spec/l3-high-availability.
Right now neutron-dhcp agent can be configured as
Sylvain Bauza wrote:
(2) When a test fails, it's hard to find the command to rerun a single
failing test.
(...)
See the wiki page I gave to you. Some helpful tricks are there. That said, I
never had the issue you mentioned related to only checking one unittest by
providing the path.
When
On Wed, Apr 02, 2014 at 08:24:00AM -0500, Dolph Mathews wrote:
On Mon, Mar 31, 2014 at 10:40 PM, Adam Young ayo...@redhat.com wrote:
On 03/28/2014 03:01 AM, Tom Fifield wrote:
Thanks to those projects that responded. I've proposed sessions in swift,
ceilometer, tripleO and horizon.
On Fri, Mar 28, 2014 at 03:01:30PM +0800, Tom Fifield wrote:
Thanks to those projects that responded. I've proposed sessions in
swift, ceilometer, tripleO and horizon.
I just created a session for Heat:
http://summit.openstack.org/cfp/details/247
Historically Heat sessions have been quite
Guys, thank you very much for your comments,
I thought a lot about why we need to be so limited in IPA use cases. Now it
much clearer for me. Indeed, having some kind of agent running inside host
OS is not what many people want to see. And now I'd rather agree with that.
But there are still some
-Original Message-
From: Robert Collins [mailto:robe...@robertcollins.net]
Sent: 07 April 2014 21:01
To: OpenStack Development Mailing List
Subject: [openstack-dev] [TripleO] config options, defaults, oh my!
So one interesting thing from the influx of new reviews is lots of patches
Hi,
Le mardi 8 avril 2014, 10:54:24 Julien Danjou a écrit :
On Mon, Apr 07 2014, Doug Hellmann wrote:
We can avoid adding to the problem by putting each new library in its
own package. We still want the Oslo name attached for libraries that
are really only meant to be used by OpenStack
Vishvananda Ishaya wrote:
I dealt with this myself the other day and it was a huge pain. That said,
changing all the packages seems like a nuclear option.
Yeah, package renaming is usually a huge pain for distributions, and we
already forced them through some oslo reversioning/renaming
https://bugs.launchpad.net/nova/+bug/1303983
--
Russell Bryant
Wow - was there really a need to get that change merged within 12 hours and
before others had a chance to review and comment on it ?
I see someone has already queried (post the merge) if there isn't a performance
impact.
I've
On 04/08/2014 06:03 AM, Day, Phil wrote:
-Original Message-
From: Robert Collins [mailto:robe...@robertcollins.net]
Sent: 07 April 2014 21:01
To: OpenStack Development Mailing List
Subject: [openstack-dev] [TripleO] config options, defaults, oh my!
So one interesting thing from the
Its more than just non-admin, it also allows a user to lock an instance so
that they don’t accidentally perform some operation on a VM.
At one point it was (by default) an admin only operation on the OSAPI, but its
always been open to all users in EC2. Recently it was changed so that admin
-Original Message-
From: Russell Bryant [mailto:rbry...@redhat.com]
Sent: 07 April 2014 19:12
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Server Groups are not an optional
element, bug or feature ?
...
I consider it a complete working feature.
Abusive usage : If user can request anti-affinity VMs, then why doesnt
he uses that? This will result in user constantly requesting all his VMs
being in the same anti-affinity group. This makes scheduler choose one
physical host per VM. This will quickly flood the infrastructure and mess
up
(Follow-up of the [olso] use of the oslo namespace package thread)
Hi,
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 it into smaller parts and distribute
Hi Justin,
Glad you like the idea of using lock ;-)
I still think you need some more granularity that user or admin - currently for
Trove to lock the users VMs as admin it would need an account that has admin
rights across the board in Nova, and I don't think folks would want to delegate
On a large cloud you're protect against this to some extent if the number of
servers is number of instances in the quota.
However it does feel that there are a couple of things missing to really
provide some better protection:
- A quota value on the maximum size of a server group
-
Hi Victor,
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 it into smaller parts and
distribute it on PyPI with a stable API? I don't know Olso Incubator
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/04/14 12:35, Victor Stinner wrote:
(Follow-up of the [olso] use of the oslo namespace package
thread)
Hi,
The openstack.common module also known as Oslo Incubator or
OpenStack Common Libraries has 44 dependencies. IMO we reach a
On Tue, Apr 8, 2014 at 6:03 AM, Day, Phil philip@hp.com wrote:
-Original Message-
From: Robert Collins [mailto:robe...@robertcollins.net]
Sent: 07 April 2014 21:01
To: OpenStack Development Mailing List
Subject: [openstack-dev] [TripleO] config options, defaults, oh my!
So one
On 2014/07/04 15:36, Tzu-Mainn Chen wrote:
Hi all,
One of the topics of discussion during the TripleO midcycle meetup a few weeks
ago was the direction we'd like to take Tuskar during Juno. Based on the ideas
presented there, we've created a tentative list of items we'd like to address:
On 2014/08/04 01:50, Robert Collins wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdon
jdon - jdob
+1 for all the folks.
-- Jarda
On 4 April 2014 08:55, Chris Jones c...@tenshu.net wrote:
Hi
+1 for your proposed -core changes.
Re your question about whether we should
On 04/08/2014 06:16 AM, Day, Phil wrote:
https://bugs.launchpad.net/nova/+bug/1303983
--
Russell Bryant
Wow - was there really a need to get that change merged within 12 hours and
before others had a chance to review and comment on it ?
It was targeted against RC2 which we're trying to
On 2014/03/04 13:02, Robert Collins wrote:
Getting back in the swing of things...
Hi,
like most OpenStack projects we need to keep the core team up to
date: folk who are not regularly reviewing will lose context over
time, and new folk who have been reviewing regularly should be trusted
On 04/08/2014 06:29 AM, Day, Phil wrote:
-Original Message-
From: Russell Bryant [mailto:rbry...@redhat.com]
Sent: 07 April 2014 19:12
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Server Groups are not an optional
element, bug or feature ?
...
For an user with role as Member , how to get the contents of extra column
from user table in keystone DB using python keystone
API. Also for a user who is already logged in from horizon how can this column
be extracted on Django side.
Thanks,
Hi
+1
Cheers,
--
Chris Jones
On 8 Apr 2014, at 00:50, Robert Collins robe...@robertcollins.net wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdon
On 4 April 2014 08:55, Chris Jones c...@tenshu.net wrote:
Hi
+1 for your proposed -core changes.
Re your
Hi
On 8 Apr 2014, at 11:20, Sean Dague s...@dague.net wrote:
I think Phil is dead on. I'll also share the devstack experience here.
Until we provided the way for arbitrary pass through we were basically
getting a few patches every week that were let me configure this
variable in the
On Tue, Apr 8, 2014 at 9:17 AM, Deepak Shetty dpkshe...@gmail.com wrote:
Hi List,
I had few Qs on the implementation of manage_existing and unmanage API
extns
1) For LVM case, it renames the lv.. isn't it better to use name_id (one
used during cinder migrate to keep id same for a diff
Hey folks,
the nomination period was already ended and there is only one
candidate, so, there is no need to setup voting.
The Climate PTL for Juno wiki page [0] updated.
So, the Climate PTL for Juno cycle is Dina Belova, congratulations!
Thanks.
[0]
On 04/08/2014 01:50 AM, Robert Collins wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdon
+1
Imre
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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 think we could get around the nose issue by using a testr
Zane Bitter wrote:
(1) Create a network
Instinctively, I want a Network to be something like a virtual VRF
(VVRF?): a separate namespace with it's own route table, within which
subnet prefixes are not overlapping, but which is completely independent
of other Networks that may contain
Version 1.6.1 of cliff has been released. This is a bug-fix release to
correct an issue with the shell output formatter, and isn't a critical
upgrade unless you are using the shell output for interpreting cliff
output in bash scripts.
Doug
___
On 08/04/14 00:50, Robert Collins wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdon
+1 for all
On 4 April 2014 08:55, Chris Jones c...@tenshu.net wrote:
Hi
+1 for your proposed -core changes.
Re your question about whether we should retroactively apply the
Guys, thank you very much for your comments,
I thought a lot about why we need to be so limited in IPA use cases. Now it
much clearer for me. Indeed, having some kind of agent running inside host OS
is not what many people want to see. And now I'd rather agree with that.
But there are still
On Tue, Apr 08 2014, victor stinner wrote:
I would like to use testr because many Olso Incubator tests use
testscenarios (which doesn't work with nosetests).
What about using both for now, nosetests + testr for the files you need
that have testscenarios?
--
Julien Danjou
;; Free Software
On Mon, Apr 7, 2014 at 7:50 PM, Robert Collins
robe...@robertcollins.net wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdob
+1 to all. I've valued the feedback from these individuals as both
fellow reviewers and on my submitted patches.
--
-- James Slagle
--
On Tue, 2014-04-08 at 10:49 +, Day, Phil wrote:
On a large cloud you’re protect against this to some extent if the
number of servers is number of instances in the quota.
However it does feel that there are a couple of things missing to
really provide some better protection:
-
On 04/08/2014 01:50 AM, Robert Collins wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdon
+1 to all
Jan
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Excerpts from Day, Phil's message of 2014-04-08 03:03:41 -0700:
-Original Message-
From: Robert Collins [mailto:robe...@robertcollins.net]
Sent: 07 April 2014 21:01
To: OpenStack Development Mailing List
Subject: [openstack-dev] [TripleO] config options, defaults, oh my!
So
On Tue, Apr 8, 2014 at 6:12 AM, Victor Stinner
victor.stin...@enovance.com wrote:
Hi,
Le mardi 8 avril 2014, 10:54:24 Julien Danjou a écrit :
On Mon, Apr 07 2014, Doug Hellmann wrote:
We can avoid adding to the problem by putting each new library in its
own package. We still want the Oslo
Donald linked to a pip bug later in this thread, so we might be able
to help by working on a fix. I haven't investigated that, but I assume
if it was easy the pypa team would have already fixed it.
When you saw the problem, were you running a current version of
devstack with Sean's change to
On Tue, Apr 8, 2014 at 3:28 AM, Mark McLoughlin mar...@redhat.com wrote:
On Mon, 2014-04-07 at 15:24 -0400, Doug Hellmann wrote:
We can avoid adding to the problem by putting each new library in its
own package. We still want the Oslo name attached for libraries that
are really only meant to
Great, thanks Assaf.
I will keep following it. I've added a link to this bp on this page:
https://wiki.openstack.org/wiki/NovaNeutronGapHighlights#Multi-Host, might
help people to get the status.
On Mon, Apr 7, 2014 at 11:37 AM, Assaf Muller amul...@redhat.com wrote:
- Original Message
2014-04-08 20:08 GMT+08:00 Russell Bryant rbry...@redhat.com:
On 04/08/2014 06:16 AM, Day, Phil wrote:
https://bugs.launchpad.net/nova/+bug/1303983
--
Russell Bryant
Wow - was there really a need to get that change merged within 12 hours
and before others had a chance to review and
It would be incredibly useful to get some of the packagers into this
conversation too.
Matt
On 4/8/14 4:51 AM, Steven Hardy sha...@redhat.com wrote:
On Wed, Apr 02, 2014 at 08:24:00AM -0500, Dolph Mathews wrote:
On Mon, Mar 31, 2014 at 10:40 PM, Adam Young ayo...@redhat.com wrote:
On
Certainly adding an explicit shutdown or terminate call to the driver
seems reasonable - a blueprint to this effect would be welcome.
On 7 April 2014 06:13, Deepak Shetty dpkshe...@gmail.com wrote:
To add:
I was looking at Nova code and it seems there is a framework for cleanup
using the
From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com]
Sent: Tuesday, April 08, 2014 9:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ironic][Agent]
Guys, thank you very much for your comments,
I thought a lot about why we need to be so
Hi all,
I have been trying to install heat with devstack. As shown here
http://docs.openstack.org/developer/heat/getting_started/on_devstack.html
I added the IMAGE_URLS to the locarc file. Then I ran unstack.sh and then
stack.sh. Now, when I run heat stack-list, I get the following error:
How many of the modules affected by this are slated to be moved to
their own libraries during Juno? I would expect those libraries to be
using testr, so can we just make the change as we graduate them?
Doug
On Tue, Apr 8, 2014 at 9:12 AM, victor stinner
victor.stin...@enovance.com wrote:
Hi,
On 8 April 2014 11:51, Dan Prince dpri...@redhat.com wrote:
- Original Message -
From: Robert Collins robe...@robertcollins.net
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Sent: Monday, April 7, 2014 4:00:30 PM
Subject: [openstack-dev] [TripleO] config
On 9 April 2014 00:48, Chris Jones c...@tenshu.net wrote:
Hi
On 8 Apr 2014, at 11:20, Sean Dague s...@dague.net wrote:
I think Phil is dead on. I'll also share the devstack experience here.
Until we provided the way for arbitrary pass through we were basically
getting a few patches every
On Tue, Apr 8, 2014 at 10:01 AM, Julien Danjou jul...@danjou.info wrote:
On Tue, Apr 08 2014, Doug Hellmann wrote:
I would like for us to continue to use the oslo prefix in some cases,
because it makes naming simple libraries easier but more importantly
because it is an indicator that we
-Message d'origine-
De : Jay Pipes [mailto:jaypi...@gmail.com]
Envoyé : mardi 8 avril 2014 15:25
À : openstack-dev@lists.openstack.org
Objet : Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible
or not ?
On Tue, 2014-04-08 at 10:49 +, Day, Phil wrote:
Reposting this, after discussing with Sean Dague…
For background, I have developed a REST client lib to talk to a H/W device with
REST server for VPNaaS in Neutron. To support unit testing of this, I created a
UT module and a mock REST server module and used the httmock package. I found
it
On Tue, Apr 8, 2014 at 6:35 AM, Victor Stinner
victor.stin...@enovance.com wrote:
(Follow-up of the [olso] use of the oslo namespace package thread)
Hi,
The openstack.common module also known as Oslo Incubator or OpenStack
Common Libraries has 44 dependencies. IMO we reach a point where it
- Original Message -
On Tue, 2014-04-08 at 10:49 +, Day, Phil wrote:
On a large cloud you’re protect against this to some extent if the
number of servers is number of instances in the quota.
However it does feel that there are a couple of things missing to
really provide
Hi,
how fresh is your devstack? AFIK heat became enabled by default not so long
ago. Try pulling the latest devstack master before running stack.sh.
Best,
Pavlo.
On Tue, Apr 8, 2014 at 5:00 PM, Peeyush Gupta gpeey...@ymail.com wrote:
Hi all,
I have been trying to install heat with
Maybe those changes should be added to our cgit stylesheet?
Doug
On Mon, Apr 7, 2014 at 9:23 PM, Zhongyue Luo zhongyue@intel.com wrote:
Hi,
I know I'm not the only person who had this problem so here's two simple
steps to get the lines and line numbers aligned.
1. Install the stylebot
On 04/08/2014 07:25 AM, Jay Pipes wrote:
On Tue, 2014-04-08 at 10:49 +, Day, Phil wrote:
On a large cloud you’re protect against this to some extent if the
number of servers is number of instances in the quota.
However it does feel that there are a couple of things missing to
really
There's been some work in Glance on this already. In addition to the BP Mark
mentioned for import, please take a look at these so we don't duplicate efforts:
https://wiki.openstack.org/wiki/Glance-tasks-import
https://blueprints.launchpad.net/glance/+spec/new-download-workflow
I'm very wary of trying to make the decision in TripleO of what should and
shouldn't be configurable in some other project.For sure the number of
config options in Nova is a problem, and one that's been discussed many times
at summits. However I think you could also make the
On Tue, Apr 08 2014, Doug Hellmann wrote:
I would like for us to continue to use the oslo prefix in some cases,
because it makes naming simple libraries easier but more importantly
because it is an indicator that we intend those libraries to be much
more useful to OpenStack projects than to
Hi Everyone,
Individuals are travelling this week and therefore will need to postpone the
Hyper-V discussion until next week.
p
Peter J. Pouliot CISSP
Sr. SDET OpenStack
Microsoft
New England Research Development Center
1 Memorial Drive
Cambridge, MA 02142
P: 1.(857).4536436
E:
On Tue, 2014-04-08 at 08:30 +, Zhangleiqiang (Trump) wrote:
Hi, Stackers,
For Amazon, after calling ModifyInstanceAttribute API , the instance
must be stopped.
In fact, the hypervisor can online-adjust these attribute. But amzon
and openstack do not support it.
On 04/08/2014 03:13 AM, victor stinner wrote:
Hi,
I have some issues when running unit tests in OpenStack. I would like to help,
but I don't know where I should start and how I can fix these bugs. My use case
is to run unit tests and rerun a single test if one or more tests failed. Well,
it
Hi,
Le 2014-04-08 17:11, Ben Nemec a écrit :
It should be possible to switch back to testr for the py33 tests if we
use the regex syntax for filtering out the tests that don't work in
py3. The rpc example is
https://github.com/openstack/oslo-incubator/blob/master/tox.ini#L21
and if you look at
On 04/07/2014 11:57 PM, Peng Wu wrote:
Thanks for the comments.
Maybe we could just search the English log. :-)
Right, but the problem is that the English log is not guaranteed to
remain the same. An (extremely contrived) example:
Say we have a log message like Failed to not find entity:
Hello infra and devstack,
I would like to start thread about adding of nosql databases support to
devstack for development and gating purposes.
Currently there is necessity of HBase and Cassandra in MagnetoDB project
for running tempest tests.
We have implemented Cassandra as part of MagnetoDB
As March has come to a close, and Juno is open for development, I would
like to look at our review stats and see if the core review team should be
adjusted to reflect current activity. Also, since I believe that our
development pace needs to accelerate, I would like to increase the size of
the
On Apr 7, 2014, at 7:01 PM, Brian Curtin br...@python.org wrote:
https://wiki.openstack.org/wiki/Meetings#python-openstacksdk_Meeting
Date/Time: Tuesday 25 March - 1900 UTC / 1400 CDT
I don't have a time machine, so let's do this today!
Tuesday, 8 April - 1900 UTC
IRC channel:
So, I'd like to formally propose that Ruby (rloo), Haomeng (whaom), and
Yuriy (yuriyz) be added to the core team at this time. I believe they have
all been very helpful over the last few months.
+1 for all! Good stuff :)
Cheers,
Lucas
___
On Tue, Apr 8, 2014 at 11:21 AM, Mehdi Abaakouk sil...@sileht.net wrote:
Hi,
Le 2014-04-08 17:11, Ben Nemec a écrit :
It should be possible to switch back to testr for the py33 tests if we
use the regex syntax for filtering out the tests that don't work in
py3. The rpc example is
+1 for those guys.
On Tue, Apr 8, 2014 at 6:35 PM, Lucas Alvares Gomes
lucasago...@gmail.comwrote:
So, I'd like to formally propose that Ruby (rloo), Haomeng (whaom), and
Yuriy (yuriyz) be added to the core team at this time. I believe they have
all been very helpful over the last few
On 04/08/2014 10:21 AM, Mehdi Abaakouk wrote:
Hi,
Le 2014-04-08 17:11, Ben Nemec a écrit :
It should be possible to switch back to testr for the py33 tests if we
use the regex syntax for filtering out the tests that don't work in
py3. The rpc example is
Hi Mike,
For all neutron-related fuel developments please feel free to reach to to
the neutron team for any help you might need either by using the ML or
pinging people in #openstack-neutron.
Regarding the fuel blueprints you linked in your first post, I am looking
in particular at
1 - 100 of 170 matches
Mail list logo
