Hi folks,
We'll be having the Sahara team meeting in #openstack-meeting-alt channel.
Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meetingiso=20150305T18
--
Sincerely yours,
Sergey Lukjanov
Sahara
I agree with Assaf, this is an issue across updates, and
we may want (if that’s technically possible) to provide
access to those functions with/without namespace.
Or otherwise think about reverting for now until we find a
migration strategy
Hi,
By this e-mail I'd like to start a discussion about current zmq driver
internal design problems I've found out.
I wish to collect here all proposals and known issues. I hope this
discussion will be continued on Liberty design summit.
And hope it will drive our further zmq driver
On 03/04/2015 03:17 PM, Wensley, Barton wrote:
Hi,
I have been exercising the numa topology related features in kilo (cpu
pinning, numa topology, huge pages) and have seen that there are issues
when an operation moves an instance between compute nodes. In summary,
the numa_topology is not
+TC topic to subject line in accordance with astute suggestions.
On Mar 4, 2015, at 8:53 AM, Adrian Otto adrian.o...@rackspace.com wrote:
OpenStack Devs,
There is an item [1] on the 2015-03-10 TC meeting agenda [2] that I would
like to highlight so discussion can commence prior to voting.
Hi core reviewers,
I have a review for murano-driver improvement that's waiting for approval
from core reviewers. Please take a look at your convenience. I just want to
remind so it won't slip your attention.
https://review.openstack.org/#/c/158924/
Thanks,
-Steven
+1, lets do this!
Lin Hua Cheng os.lch...@gmail.com wrote on 03/04/2015 12:13:22 PM:
From: Lin Hua Cheng os.lch...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 03/04/2015 12:21 PM
Subject: Re: [openstack-dev]
On Wed, Mar 04, 2015 at 05:24:53PM +, Jiang, Yunhong wrote:
Daniel, thanks for your clarification.
Another related question is, what will be the guest's real cpu model
is the cpu_model is None? This is about a reported regression at
The guest CPU will be unspecified - it will be some
+1
On 3/4/15, 08:01, Doug Hellmann d...@doughellmann.com wrote:
On Tue, Mar 3, 2015, at 06:17 PM, Dean Troyer wrote:
On Thu, Feb 26, 2015 at 3:32 PM, Doug Hellmann d...@doughellmann.com
wrote:
As we discussed in the meeting today, I’ve created a Doodle to
coordinate
a good day and time
On Wed, Mar 4, 2015 at 7:03 AM, Csaba Henk ch...@redhat.com wrote:
- Original Message -
From: Danny Al-Gaaf danny.al-g...@bisect.de
To: Csaba Henk ch...@redhat.com, OpenStack Development Mailing List
(not for usage questions)
openstack-dev@lists.openstack.org
Cc:
On Tue, 2015-03-03 at 17:42 +0200, Eduard Matei wrote:
Is there a way to specify the Juno version to be installed using
devstack.
Let's please reserve this list for discussions about the *future* of
OpenStack development, not questions about using its tools.
Please, everybody, help us stay
OpenStack Devs,
There is an item [1] on the 2015-03-10 TC meeting agenda [2] that I would like
to highlight so discussion can commence prior to voting. Magnum’s contributors
have indicated our intent to join the OpenStack namespace in accordance with
our new governance requirements [3]. I will
Excerpts from Thierry Carrez's message of 2015-03-04 02:19:48 -0800:
James Bottomley wrote:
On Tue, 2015-03-03 at 11:59 +0100, Thierry Carrez wrote:
James Bottomley wrote:
Actually, this is possible: look at Linux, it freezes for 10 weeks of a
12 month release cycle (or 6 weeks of an 8
Hi Andreas,
vpnaas (i.e. its agent) is a superset of l3-router and it includes the
functionality of the later. Hence you just need to configure either one of
them. q-l3 if you don't need vpnaas and q-vpn if you need both vpnaas and
l3.
Hope this helps.
- Sridhar
On Wed, Mar 4, 2015 at 9:18 AM,
Hello everybody,
is there a reason why devstack is only able to either deploy vpnaas or
l3-router?
Nevertheless both services are enabled in the local.conf on the
HowToInstall Page [1]. But the code says it's a either or [2] (line
725).
if is_service_enabled q-vpn; then
run_process q-vpn
Daniel, thanks for your clarification.
Another related question is, what will be the guest's real cpu model is the
cpu_model is None? This is about a reported regression at
https://bugs.launchpad.net/nova/+bug/1082414 . When the
instance.vcpu_model.mode is None, we should compare the
Since the Nova side isn't in, and won't land for Kilo, then there is no
reason for Cinder to have it for Kilo, as it will simply not work.
We can revisit this for the L release if you like.
Also, make sure you have 3rd Party CI setup for this driver, or it won't
be accepted in the L release
To put in another way I think we might say that change 154670 broke
backward compatibility on the RPC interface.
To be fair this probably happened because RPC interfaces were organised in
a way such that this kind of breakage was unavoidable.
I think the strategy proposed by Assaf is a viable
+1
Thanks Doug for setting up the Doodle.
On Wed, Mar 4, 2015 at 8:55 AM, Ian Cordasco ian.corda...@rackspace.com
wrote:
+1
On 3/4/15, 08:01, Doug Hellmann d...@doughellmann.com wrote:
On Tue, Mar 3, 2015, at 06:17 PM, Dean Troyer wrote:
On Thu, Feb 26, 2015 at 3:32 PM, Doug Hellmann
Flavio, I concur, for a lively committee need active core reviewers. Core
status is an honor and responsibility.
I agree it’s a good idea to replace inactive cores, no offense, priorities and
focus of developers change, and should they want to return, can be fast pathed
then.
Regards
Malini
We are pumped to announce the release of:
oslo.config 1.9.0: Oslo Configuration API
For more details, please see the git log history below and:
http://launchpad.net/oslo.config/+milestone/1.9.0
Please report issues through launchpad:
http://bugs.launchpad.net/oslo.config
Changes in
Hello Ceilometer,
I would like to check on the chances that spec
https://review.openstack.org/#/c/130359 will land in the K cycle. We in
Ironic have specs that are dependent on the above spec and are checking to
see if we need to bump them to L? Any information regarding this would be
helpful.
At (or maybe after) the last API-WG meeting, the idea to create an API-WG
specific channel came up again and there was consensus that it would be
beneficial to have. I registered the channel and have submitted the
appropriate changes to system-config and project-config to enable logging
of the
There has been a request to backport the fix for bug 1333852
(https://bugs.launchpad.net/trove/+bug/1333852) which was fixed in Kilo into
the Juno release.
The change includes a database change and a small change to the Trove API. The
change also requires a change to the trove client and the
I'd like to propose that we add Ihar Hrachyshka to the Neutron core
reviewer team. Ihar has been doing a great job reviewing in Neutron as
evidence by his stats [1]. Ihar is the Oslo liaison for Neutron, he's been
doing a great job keeping Neutron current there. He's already a critical
reviewer
Here's the link to the code review: https://review.openstack.org/#/c/147399/
On Wed, Mar 4, 2015 at 7:17 AM, Dolph Mathews dolph.math...@gmail.com
wrote:
On Wednesday, March 4, 2015, David Stanek dsta...@dstanek.com wrote:
On Wed, Mar 4, 2015 at 6:50 AM, Abhishek Talwar/HYD/TCS
+1
On Mar 4, 2015 12:44 PM, Kyle Mestery mest...@mestery.com wrote:
I'd like to propose that we add Ihar Hrachyshka to the Neutron core
reviewer team. Ihar has been doing a great job reviewing in Neutron as
evidence by his stats [1]. Ihar is the Oslo liaison for Neutron, he's been
doing a
Ihar has proved in several circumstances that he knows neutron source trees
way better than me, his reviews are more frequent, thorough, and useful
than those of the average core team member. Summarising, in my opinion it
is a nonsense that I am part of this team and he's not.
So I am obviously
Hi folks,
This weekend, the patch Snapshot and volume objects (
https://review.openstack.org/#/c/133566) was merged and this one broke our
HDS HBSD driver and the respective CI.
When CI tries to run tempest.api.volume.admin.test_snapshots_actions the
following error is shown:
2015-03-04
+1
On Mar 4, 2015 12:25 PM, Maru Newby ma...@redhat.com wrote:
+1 from me, Ihar has been doing great work and it will be great to have
him finally able to merge!
On Mar 4, 2015, at 11:42 AM, Kyle Mestery mest...@mestery.com wrote:
I'd like to propose that we add Ihar Hrachyshka to the
- Original Message -
From: Adrian Hoban adrian.ho...@intel.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
-Original Message-
From: Steve Gordon [mailto:sgor...@redhat.com]
Sent: Wednesday, February 11, 2015 8:49 PM
Attila Fazekas afaze...@redhat.com wrote:
Hi,
I wonder what is the planned future of the scheduling.
The scheduler does a lot of high field number query,
which is CPU expensive when you are using sqlalchemy-orm.
Does anyone tried to switch those operations to sqlalchemy-core ?
An
+1!
On 4 March 2015 at 22:29, Kevin Benton blak...@gmail.com wrote:
+1
On Mar 4, 2015 12:25 PM, Maru Newby ma...@redhat.com wrote:
+1 from me, Ihar has been doing great work and it will be great to have
him finally able to merge!
On Mar 4, 2015, at 11:42 AM, Kyle Mestery
We’re about 1 week out from the Oslo feature freeze, which is 1 week earlier
than the app freeze at the third milestone. If you have features you were
expecting to land for this cycle, please make sure the core review teams are
aware so we can prioritize those reviews.
Doug
Hey everyone,
I just wanted to make the list aware that the
stackforge/os-ansible-deployment project has submitted a change to start
logging its channel (#openstack-ansible). Please vote on the proposal
https://review.openstack.org/#/c/161412/
Cheers,
Ian
+1 !!!
On Wed, Mar 04, 2015, Kyle Mestery mest...@mestery.com wrote:
I'd like to propose that we add Ihar Hrachyshka to the Neutron core reviewer
team. Ihar has been doing a great job reviewing in Neutron as evidence by his
stats [1]. Ihar is the Oslo liaison for Neutron, he's been doing a
+1
On Mar 4, 2015, at 12:42 PM, Kyle Mestery mest...@mestery.com wrote:
I'd like to propose that we add Ihar Hrachyshka to the Neutron core reviewer
team. Ihar has been doing a great job reviewing in Neutron as evidence by his
stats [1]. Ihar is the Oslo liaison for Neutron, he's been
On 03/04/2015 01:51 AM, Attila Fazekas wrote:
Hi,
I wonder what is the planned future of the scheduling.
The scheduler does a lot of high field number query,
which is CPU expensive when you are using sqlalchemy-orm.
Does anyone tried to switch those operations to sqlalchemy-core ?
Actually,
+1 from me, Ihar has been doing great work and it will be great to have him
finally able to merge!
On Mar 4, 2015, at 11:42 AM, Kyle Mestery mest...@mestery.com wrote:
I'd like to propose that we add Ihar Hrachyshka to the Neutron core reviewer
team. Ihar has been doing a great job
Per the results from the Doodle set up by dhellmann [0] we are moving the
scheduled OpenStackClient team meeting back to 1900 UTC starting tomorrow,
05 Mar 2014, still in freenode #openstack-meeting.
The agenda for the meeting can be found at
Thanks for pulling this list together, Oleksii. More comments inline. -
Doug
On Wed, Mar 4, 2015, at 12:10 PM, ozamiatin wrote:
Hi,
By this e-mail I'd like to start a discussion about current zmq driver
internal design problems I've found out.
I wish to collect here all proposals and known
On 03/04/2015 09:27 AM, Andreas Jaeger wrote:
There has been a maintenance window in one of our providers cloud and it
seems that some of the OpenStack CI infrastructure is not working as is.
You will notice that Jenkins is not commenting on any changes submitted
to review.openstack.org, the
Mike Bayer mba...@redhat.com wrote:
Attila Fazekas afaze...@redhat.com wrote:
Hi,
I wonder what is the planned future of the scheduling.
The scheduler does a lot of high field number query,
which is CPU expensive when you are using sqlalchemy-orm.
Does anyone tried to switch
Hi,
in nova there are several options that can be defined in the flavor (extra
specs)
and/or as image properties.
This is great, however to deploy some of these options we will need offer
the
same image with different properties or let the users upload the same image
with
the right properties.
It
Looks like it's a complicated problem, and nova-scheduler can't scale-out
horizontally in active/active mode.
Maybe we should illustrate the problem in the HA docs.
http://docs.openstack.org/high-availability-guide/content/_schedulers.html
Thanks for everybody's attention.
2015-03-05 5:38
Doug,
Thank you for the response and sorry to respond you late.
Recently I could not receive e-mails from this list and your e-mail was one of
them.
I don't know the reason but I found out your response in archive.
On Mon, 02 Mar 2015 12:28:06 -0800, Doug Hellmann wrote:
We're making good
On Wed, Mar 4, 2015 at 9:51 PM, Alexandre Levine alev...@cloudscaling.com
wrote:
Christopher,
Does this
So the plan for assignment of microversion api numbers is the same as
what we currently do for db migration changes - take the next one
knowing that you may need to rebase if someone
huzzah!
thanks Ian =)
mike
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
Christopher,
If I'm not mistaken about what you mean I understand the point with the
small changes, but what's wrong with already approved, tested and ready
changes to be added as one version? Alternatively you risk getting
rather quickly to high version numbers like 2.25, 2.37 It'll lead
Hi Sean,
Yes having V3 directory/file names is very confusing now.
But current v3 sample tests cases tests v2.1 plugins. As /v3 url is
redirected to v21 plugins, v3 sample tests make call through v3 url and
test v2.1 plugins.
I think we can start cleaning up the *v3* from everywhere and change
- Original Message -
From: Thierry Carrez thie...@openstack.org
To: James Bottomley james.bottom...@hansenpartnership.com
It's certainly a lot less than you, but we have the entire system
call
man pages. It's an official project of the kernel:
Thank you for your response.
That's a fair point. But I think it's because you're not expected to
run as admin, and having a way to drop the group as admin can be of
value for e.g. debugging or cleaning up after some bugs [1].
You’re right.
Regenerate logic seems strange to me. But I’m not
On Wed, 2015-03-04 at 11:19 +0100, Thierry Carrez wrote:
James Bottomley wrote:
On Tue, 2015-03-03 at 11:59 +0100, Thierry Carrez wrote:
Second it's at a very different evolution/maturity point (20 years old
vs. 0-4 years old for OpenStack projects).
Yes, but I thought I covered this
Hi Paul.
I'd vote for (C) and a slightly later time-slot on Tuesdays - 1630 UTC (or
later).
The meetings so far was indeed quite useful. I guess the current busy Kilo
cycle is also contributing to the low turnout. As we pick up things going
forward this forum will be quite useful to discuss
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:
2015-03-04 4:45 GMT+08:00 Jay Pipes jaypi...@gmail.com:
On 03/03/2015 01:10 AM, Rui Chen wrote:
Hi all,
When we boot instance from volume, we find some ambiguous description
about flavor root_gb in operations guide,
http://docs.openstack.org/openstack-ops/content/flavors.html
/Virtual
We will face the same issue in multiple nova-scheduler process case, like
Sylvain say, right?
Two processes/workers can actually consume two distinct resources on the
same HostState.
2015-03-05 13:26 GMT+08:00 Alex Xu sou...@gmail.com:
Rui, you still can run multiple nova-scheduler process
Rui, you still can run multiple nova-scheduler process now.
2015-03-05 10:55 GMT+08:00 Rui Chen chenrui.m...@gmail.com:
Looks like it's a complicated problem, and nova-scheduler can't scale-out
horizontally in active/active mode.
Maybe we should illustrate the problem in the HA docs.
Ok, we will proceed with error-on and success-on.
Thanks for the reply!
--
Best Regards,
Nikolay
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hi,
I like the idea of explicit checks by success-on and error-on:
success-on to break retry and get SUCCESS state.
error-on to break retry but get ERROR state.
A single break-on seems confusing to me too.
Regards,
Thomas Hsiao
HP Cloud
Nikolay, thanks for sharing this…
I think that we
The option1 is a bad idea, IMO. Think about so many extra_specs in the
flavor today, you really don't want create another dozen of flavor
with root_gb=0 just for booting from volume.
For the billing concern, it really should be taken into account, but
it's not the business of OpenStack, IMHO.
I
+100Š.000
Very long overdue!
On 3/4/15, 10:23 PM, Maru Newby ma...@redhat.com wrote:
+1 from me, Ihar has been doing great work and it will be great to have
him finally able to merge!
On Mar 4, 2015, at 11:42 AM, Kyle Mestery mest...@mestery.com wrote:
I'd like to propose that we
+1
From: Armando M. [mailto:arma...@gmail.com]
Sent: 05 March 2015 03:12
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a
Neutron Core Reviewer
+1!
On 4 March 2015 at 22:29, Kevin Benton
What do the keystone logs indicate?
Steve
Akshik DBK aks...@outlook.com wrote on 03/04/2015 02:18:47 AM:
From: Akshik DBK aks...@outlook.com
To: OpenStack Development Mailing List not for usage questions
openstack-dev@lists.openstack.org
Date: 03/04/2015 02:25 AM
Subject: Re:
So, one problem here is that 'metadata' in cinder has (at least) 3
meanings. Here is an attempt to clarify (which should be on some wiki page
somewhere, I'll add it once people tell me the meaning is clear).
Volume metadata:
- This is set via the --metadata flag at create time, and there are
Hi Mike, Jay, and Walter,
Please revisit this patch https://review.openstack.org/#/c/151959/ and don't
revert this, thank you very much!
I think it's apposite to merge the SDSHypervisor driver in cinder first, and
next to request nova to add a new libvirt volume driver.
Meanwhile nova side
There has been a maintenance window in one of our providers cloud and it
seems that some of the OpenStack CI infrastructure is not working as is.
You will notice that Jenkins is not commenting on any changes submitted
to review.openstack.org, the check queue is currently stuck.
Please have
Nikolay, thanks for sharing this…
I think that we really have a semantical ambiguity here. If we leave just
“break-on” that both types of behavior have a right to exist.
I’m personally for defining that more explicitly with two separate instructions
“success-on” and “error-on”. A use case for
Hi all,
IMHO deprecation warning should be added only to commands that we recently
changed (because users can switch to new interface when they see
deprecation error) or eventually solution #2 sounds ok but is not ideal
because people can forget about warning that they saw in previous release.
Hi Steve,
here are the log details
== /var/log/shibboleth/shibd.log ==2015-03-04 14:36:05 INFO
Shibboleth.AttributeExtractor.XML [2]: skipping unmapped SAML 2.0 Attribute
with Name: urn:oid:0.9.2342.19200300.100.1.12015-03-04 14:36:05 INFO
Shibboleth.AttributeExtractor.XML [2]: skipping
James Bottomley wrote:
On Tue, 2015-03-03 at 11:59 +0100, Thierry Carrez wrote:
James Bottomley wrote:
Actually, this is possible: look at Linux, it freezes for 10 weeks of a
12 month release cycle (or 6 weeks of an 8 week one). More on this
below.
I'd be careful with comparisons with the
On Tue, 03 Mar 2015 10:28:34 -0500
Sean Dague s...@dague.net wrote:
On 03/03/2015 10:24 AM, Claudiu Belu wrote:
Hello.
I've talked with Christopher Yeoh yesterday and I've asked him
about the microversions and when will they be able to merge. He
said that for now, this commit had to
Maybe add a Changelog in the repo and maintain it?
http://keepachangelog.com/
Option #2 is OK but it can cause pain when testing -- upon each fresh
installation from ISO we would get that message and it might break some
tests though that is fixable. Option #3 is OK too. #1 is worst and I
Thanks to the entire team for participating today, we made very good
progress with knocking off a number of long standing bugs. We will
also be cutting a new stable/juno release towards the end of this week
since we ended up back porting quite a few fixes.
On Sat, Feb 28, 2015 at 10:56 AM, Sumit
Hi,
I am trying out the procedure listed in this page
https://wiki.openstack.org/wiki/GroupBasedPolicy/InstallODLIntegrationDevstack.
I was looking for an use case with Service Function chaining i.e. to use
redirect with gbp command.
Can you please point me to some link that can help me out
Hi,
I wonder what is the planned future of the scheduling.
The scheduler does a lot of high field number query,
which is CPU expensive when you are using sqlalchemy-orm.
Does anyone tried to switch those operations to sqlalchemy-core ?
The scheduler does lot of thing in the application, like
Le 04/03/2015 04:51, Rui Chen a écrit :
Hi all,
I want to make it easy to launch a bunch of scheduler processes on a
host, multiple scheduler workers will make use of multiple processors
of host and enhance the performance of nova-scheduler.
I had registered a blueprint and commit a patch
I’d like to resolve some questions:
@Przemysław:
- We can avoid that message by supplying --quiet.
- Changelog is currently managed automatically by PBR so as soon as there is a
release there will be a change log
- I think #2 can be done along with #3
@Kamil:
- The issue is that it’s not
@romcheg
- the idea is to switch partially to new client so keeping one package with
two entry points: fuel and fuel_v2. It will be convenient for us to add new
commands to fuel_v2 only and switch slowly old commands to new version and
add warnings in old client commands. It will give users time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/03/2015 04:42 PM, Eduard Matei wrote:
Hi,
Is there a way to specify the Juno version to be installed using
devstack. For now we can only specify stable/juno *git clone -b
stable/juno https://github.com/openstack-dev/devstack.git
John Griffith john.griffi...@gmail.com writes:
Should we just rename this thread to Sensitivity training for
contributors?
Culture plays a role in shaping ones expectations here. I was lucky
enough to grow up in open source culture, so I can identify an automated
response easily and I don't
On 03/03/15 16:10 +, Nikhil Komawar wrote:
If it was not clear in my previous message, I would like to again emphasize
that I truly appreciate the vigor and intent behind Flavio's proposal. We need
to be proactive and keep making the community better in such regards.
However, at the same
On Wed, Mar 4, 2015 at 6:50 AM, Abhishek Talwar/HYD/TCS
abhishek.tal...@tcs.com wrote:
While working on a bug for keystoneclient I have replaced sys.exit with
return. However, the code reviewers want that the output should be on
stderr(as sys.exit does). So how can we get the output on
Christopher,
Does this
So the plan for assignment of microversion api numbers is the same as
what we currently do for db migration changes - take the next one
knowing that you may need to rebase if someone else merges before you
mean that I should put 2.2 in my review for now instead of 2.4?
Hi All,
While working on a bug for keystoneclient I have replaced sys.exit with return.
However, the code reviewers want that the output should be on stderr(as
sys.exit does). So how can we get the output on stderr.
def do_user_password_update(kc, args):
Update user password.
user =
Am 04.03.2015 um 15:18 schrieb Csaba Henk:
Hi Danny,
- Original Message -
From: Danny Al-Gaaf danny.al-g...@bisect.de
To: Deepak Shetty dpkshe...@gmail.com
Cc: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Am 04.03.2015 um 15:12 schrieb Csaba Henk:
Hi Danny,
- Original Message -
From: Danny Al-Gaaf danny.al-g...@bisect.de To: OpenStack
Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org, ceph-de...@vger.kernel.org
Sent: Sunday, March 1, 2015 3:07:36
Hi, Daniel
I'm a bit confused of the None/'none' for CONF.libvirt.cpu_mode. Per my
understanding, None means there is no configuration provided and libvirt will
select the default value based on the virt_type, none means no cpu_mode
information should be provided. For the guest, am I
Hi,
Indeed CINDER_BRANCH=2014.2.2 did the trick.
Will properly report the issues once we start testing on 2014.2.3.
Eduard
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hi Ihar,
This is the error i see in c-vol screen:
2015-03-03 18:39:34.060 DEBUG taskflow.engines.action_engine.runner
[req-87db2771-5c25-4c9b-a3bc-f7a504468315 4af0a30fe2c14deb9f9cf341a97daa9f
1fbab1e235ff414abf249c741fb3c6c9] Exiting old state 'WAITING' in response
to event 'analyze' from
Agree with dims.
On Mon, Mar 2, 2015 at 6:14 PM, Davanum Srinivas dava...@gmail.com wrote:
Alex,
It's better do a experimental one first before trying to a non-voting:
http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/layout.yaml#n1509
-- dims
On Mon, Mar 2, 2015 at
I assume you have notifications enabled in nova.conf?
See the Enabling notifications in OpenStack section
http://www.stacktach.com/about.html
Oh, there are couple more flags that could be useful too:
notify_on_state_change=vm_and_task_state
notify_on_any_change=True
?
On Tue, Mar 3, 2015, at 06:17 PM, Dean Troyer wrote:
On Thu, Feb 26, 2015 at 3:32 PM, Doug Hellmann d...@doughellmann.com
wrote:
As we discussed in the meeting today, I’ve created a Doodle to coordinate
a good day and time for future meetings. I picked a bunch of options based
on when
I have proposed the following patch series to remove the API v3 direct
testing in tree -
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:rm_v3_paste,n,z
This also removes the /v3 entry from the paste.ini that we ship. I think
it's important that we remove
Hi Danny,
- Original Message -
From: Danny Al-Gaaf danny.al-g...@bisect.de
To: Deepak Shetty dpkshe...@gmail.com
Cc: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
ceph-de...@vger.kernel.org
Sent: Wednesday, March 4, 2015 3:05:46 PM
On Wed, Mar 04, 2015 at 07:38:42AM -0430, Flavio Percoco wrote:
I'm sorry but no. I don't think there's anything that requires extra
patience than 2 (or even more) cycles without provaiding reviews or
even any kind of active contribution.
I personally don't think adding new cores without
From: Nikhil Komawar [mailto:nikhil.koma...@rackspace.com]
Sent: Tuesday, March 03, 2015 4:10 PM
To: OpenStack Development Mailing List (not for usage questions); Daniel P.
Berrange
Cc: krag...@gmail.com
Subject: Re: [openstack-dev] [Glance] Core nominations.
If it was not clear in my
Hi all,
On Wed, Feb 18, 2015 at 04:12:11PM -0330, Brent Eagles wrote:
Hi,
snip/
Thanks Maxime. I've made some updates to the etherpad.
(https://etherpad.openstack.org/p/nova_vif_plug_script_spec)
I'm going to start some proof of concept work these evening. If I get
anything worth reading,
Am 04.03.2015 um 05:19 schrieb Deepak Shetty:
On Wed, Mar 4, 2015 at 5:10 AM, Danny Al-Gaaf
danny.al-g...@bisect.de wrote:
Am 03.03.2015 um 19:31 schrieb Deepak Shetty: [...]
[...]
I was curious to understand. IIUC Neutron provides private and
public networks and for VMs to access external
Hi Danny,
- Original Message -
From: Danny Al-Gaaf danny.al-g...@bisect.de
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
ceph-de...@vger.kernel.org
Sent: Sunday, March 1, 2015 3:07:36 PM
Subject: Re: [openstack-dev] [Manila]
1 - 100 of 101 matches
Mail list logo
