We are eager to announce the release of:
oslo.policy 0.3.2: RBAC policy enforcement library for OpenStack
This release is part of the kilo series.
For more details, please see the git log history below and:
http://launchpad.net/oslo.policy/+milestone/0.3.2
Please report issues through
The loading seems to me in a sorted order, so we can do 1.conf 2.conf etc.
https://github.com/openstack/oslo.config/blob/1.9.3/oslo_config/cfg.py#L1265-L1268
On 04/13/2015 02:45 PM, Kevin Benton wrote:
What is the order of priority between the same option defined in two
files with
Hello Team,
As per discussion in the latest GBP meeting [0] I'm hunting down all the
backward incompatible changes made on DB migrations regarding the removal
of unnamed constraints.
In this report [1] you can find the list of affected commits.
The problem is that some of the affected commits
Correction. Also included in the list of released projects for 2014.2.3,
Sahara: https://launchpad.net/sahara/juno/2014.2.3
Apologies,
Adam
On Mon, Apr 13, 2015 at 10:30 AM, Adam Gandelman gandelma...@gmail.com
wrote:
Hello everyone,
The OpenStack Stable Maintenance team is happy to announce
Thanks, I have got a patchset out for review.
I have removed the exception that was being thrown back to the agent and
have reduced the fix to just logging a meaningful message in the neutron
server logs.
Appreciate your comments on the same.
Thanks,
Sudipto
On Monday 13 April 2015 11:56 AM,
Jay,
Thanks for staying on top of updating opening Liberty specs, and for all
your help with specs during Kilo!
-Deva
On Fri, Apr 10, 2015 at 10:40 AM Jay Faulkner j...@jvf.cc wrote:
Hi,
Just a note to let you know Liberty specs are open for Ironic.
Template Changes
There are
Hello everyone,
We have our release candidate for the Manila Kilo release. The RC1
tarball, as well as a lists of last-minute features and fixed bugs since
kilo-3 are available at:
https://launchpad.net/manila/kilo/kilo-rc1
Unless release-critical issues are found that warrant a release
Hi Deepak,
Your steps look good for e except #3.1 - add unit-tests for new migrations
Regards,
Ivan Kolodyazhny
On Mon, Apr 13, 2015 at 8:20 PM, Deepak Shetty dpkshe...@gmail.com wrote:
Hi Stackers,
As part of my WIP work for implementing
On Apr 10, 2015, at 11:04 AM, Boris Pavlovic bo...@pavlovic.me wrote:
Hi,
I believe that specs are too detailed and too dev oriented for managers,
operators and devops.
They actually don't want/have time to write/read all the stuff in specs and
that's why the communication between
+1.
On Mon, Apr 13, 2015 at 4:09 PM, Sergii Golovatiuk
sgolovat...@mirantis.com wrote:
Strong +1
Nastya forgot to mention Andey's participation in Ubuntu 14.04 feature.
With Andrey's help the feature went smooth and easy ;)
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC
My apologies to the list. This was not intended to be broadcast.
From: Joe Mcbride
Sent: Monday, April 13, 2015 12:42 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] - Joining the team -
My 2c:
Yes Mistral moved to YAQL 1.0 based on Murano team recommendations :)
some questions/comments before we decide how to proceed:
1) Let’s clarify the impact: this problem doesn’t affect Murano directly; but
it impacts Murano-Congress-Mistral initiative, correct?
Is this a voting gate?
1) yaql 1.0 is not a drop-in replacement for yaql 0.2 but only one version
can be installed on any given system. Unless we use virtualenv, Docker or
anything else to isolate applications. So if Murano and Mistral uses
different yaql versions they will unable to live together on the same host
2)
We are excited to announce the release of:
oslo.db 1.8.0: Oslo Database library
For more details, please see the git log history below and:
http://launchpad.net/oslo.db/+milestone/1.8.0
Please report issues through launchpad:
http://bugs.launchpad.net/oslo.db
Changes in oslo.db
What is the order of priority between the same option defined in two files
with --config-dir?
With '--config-file' args it seemed that it was that the latter ones took
priority over the earlier ones. So an admin previously had the ability to
abuse that by putting all of the desired global
Hello,
For Clear Linux* for Intel Architecture we do not allow to package
things in /etc, instead we leave /etc completely empty and for
user/admin modifications only.
Typically we achieve this by moving sane distro defaults to be
compiled in defaults, or read from alternative locations somewhere
Excerpts from Brant Knudson's message of 2015-04-12 20:14:00 -0500:
There were several problems with the keystoneclient stable/juno branch that
have been or are in the process of being fixed since its creation.
Hopefully this note will be useful to other projects that create stable
branches
On 4/12/2015 12:23 AM, Gary Kotton wrote:
Hi,
Can a core please take a look at
https://review.openstack.org/#/c/171037. The CI is broken due to
commit e7ae5bb7fbdd5b79bde8937958dd0a645554a5f0.
Thanks
Gary
__
OpenStack
On Tue, 2015-04-07 at 21:06 +, Gregory Haynes wrote:
Hello,
Id like to propse a standard for consistently documenting our
diskimage-builder elements. I have pushed a review which transforms the
apt-sources element to this format[1][2]. Essentially, id like to move
in the direction of
I think removing all occurrences of create_port inside of another
transaction is something we should be doing for a couple of reasons.
First, it's a recipe for the cherished lock wait timeout deadlocks
because create_port makes yielding calls. These are awful to troubleshoot
and are pretty
My $2 cents:
I like the 3rd party backend however instead of ZK wouldn't Consul [1] fit
better due to lighter/ out of box multi DC awareness?
Dani
[1] Consul - https://www.consul.io/
On Mon, Apr 13, 2015 at 9:51 AM, Wangbibo wangb...@huawei.com wrote:
Hi Kevin,
Totally agree with you
On Mon, Apr 13, 2015 at 3:39 PM, Doug Wiegley doug...@parksidesoftware.com
wrote:
Hi all,
I'd like to nominate Philip Toohill as a neutron-lbaas core. Good guy, did
a bunch of work on the ref impl for lbaasv2, and and I'll let the
numbers[1] speak for themselves.
Existing lbaas cores,
Excerpts from Sean Dague's message of 2015-04-13 07:15:57 -0400:
So, under the current model I think we're paying a pretty high strategy
tax in OSC use in devstack. It's adding minutes of time in a normal run.
I don't know all the internals of OSC and what can be done to make it
better. But I
Hi all,
I'd like to nominate Philip Toohill as a neutron-lbaas core. Good guy, did a
bunch of work on the ref impl for lbaasv2, and and I'll let the numbers[1]
speak for themselves.
Existing lbaas cores, please vote. All three of us. :-)
[1]
?+1
From: Kyle Mestery mest...@mestery.com
Sent: Monday, April 13, 2015 3:44 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron][lbaas] adding lbaas core
On Mon, Apr 13, 2015 at 3:39 PM, Doug Wiegley
Excerpts from Doug Hellmann's message of 2015-04-13 15:28:22 -0400:
We are excited to announce the release of:
oslo.db 1.8.0: Oslo Database library
The upload job failed for the sdist so some installations using older
versions of pip may have also failed. Users with newer versions of pip
Hi everyone,
The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday April 14th, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone
I'm of the opinion, which may not be the popular opinion, that barbican is the
secret store for openstack. It is in openstack, it is meant to be used by
other openstack services. v1 lives in the same code base as v2. Version
transitions such as these are going to end up having requirements
Excerpts from Dan Prince's message of 2015-04-13 14:07:28 -0700:
On Tue, 2015-04-07 at 21:06 +, Gregory Haynes wrote:
Hello,
Id like to propse a standard for consistently documenting our
diskimage-builder elements. I have pushed a review which transforms the
apt-sources element to
On Apr 13, 2015, at 3:38 PM, Brandon Logan brandon.lo...@rackspace.com
wrote:
I'm of the opinion, which may not be the popular opinion, that barbican is
the secret store for openstack. It is in openstack, it is meant to be used
by other openstack services. v1 lives in the same code
On 13 April 2015 at 22:04, Thierry Carrez thie...@openstack.org wrote:
This observation led to yet more IRC discussion and eventually
https://etherpad.openstack.org/p/stable-omg-deps
In short, the proposal is that we:
- stop trying to use install_requires to reproduce exactly what
works,
Did the following get addressed?
https://aphyr.com/posts/316-call-me-maybe-etcd-and-consul
Seems like quite a few things got raised in that post about etcd/consul.
Maybe they are fixed, idk...
https://aphyr.com/posts/291-call-me-maybe-zookeeper though worked as
expected (and without
I think what we are trying to do is two separate things.
One is to define the dependencies that packagers use. This would likely
be minimum versions with caps that are known to fail (not assumed).
The second is to define a set of verifiably known working deps. This
would likely need an update
Just letting everyone know I just upgraded etherpad.openstack.org to the
latest etherpad-lite version to address CVE-2015-3297.
If you see any javascript load errors you may need to do a hard refresh
of your etherpads (sorry about this, I will have to figure out a way to
invalidate cached js
Thanks a lot, henry :)
On Mon, Apr 13, 2015 at 6:57 PM, Henry Gessau ges...@cisco.com wrote:
On Mon, Apr 13, 2015, henry hly henry4...@gmail.com wrote:
http://developer.openstack.org/api-ref-networking-v2.html
The above api document seems lost most of the content, leaving only
port, network,
On Mon, Apr 13, 2015 at 5:20 PM, Doug Hellmann d...@doughellmann.com
wrote:
Excerpts from Sean Dague's message of 2015-04-13 07:15:57 -0400:
I *believe* the time is scanning the plugins. It doesn't actually
load them, but it has to look through all of the entry point
registries to find what
On 9 April 2015 at 00:59, Doug Hellmann d...@doughellmann.com wrote:
Another data point on how slow our libraries/CLIs can be:
$ time openstack -h
snip
real0m2.491s
user0m2.378s
sys 0m0.111s
pbr should be snappy - taking 100ms to get the version is wrong.
I have
On 9 April 2015 at 01:12, Flavio Percoco fla...@redhat.com wrote:
On 08/04/15 08:59 -0400, Doug Hellmann wrote:
I have always considered pbr a packaging/installation time tool, and not
something that would be used at runtime. Why are we using pbr to get the
version of an installed package,
Tooz provides a mechanism for grouping agents and agent status/liveness
management, multiple coordinator services may be required in large scale
deployment, especially for 100k nodes level. We can't make assumption that only
one coordinator service is enough to manage all nodes, that means tooz
The thing is, is that you *should* be able to call core_plugin.create_port
in a transaction.
Well it depends on what you mean by that. If you mean create_port should be
part of the same transaction, I disagree because it leads to either
inconsistency or a loss of veto power for drivers with
2) Incorrect cap in requirements.txt
python-keystoneclient in stable/juno was capped at =1.1.0, and 1.1.0 is
the version tagged for the stable branch. When you create a review in
stable/juno it installs python-keystoneclient and now the system has got a
version like 1.1.0.post1, which
- Original Message -
I think removing all occurrences of create_port inside of another transaction
is something we should be doing for a couple of reasons.
The issues you're pointing out are very much real. It's a *huge* pain to
workaround
this issue and you can look for an example
On Thu, Apr 09, 2015 at 11:05:10AM +0900, Ken'ichi Ohmichi wrote:
2015-04-09 4:14 GMT+09:00 Sean Dague s...@dague.net:
On 04/08/2015 02:58 PM, David Kranz wrote:
On 04/08/2015 02:36 PM, Matthew Treinish wrote:
On Wed, Apr 08, 2015 at 01:08:03PM -0400, David Kranz wrote:
Since tempest no
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) Vancouver design summit - more thoughts?
2) Opens
(Light agenda this week, could be a quick meeting)
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
Hi Matt,
Our team at Rackspace is looking to add a developer, focused on building out
and deploying Designate (DNSaaS for Openstack). When we go live, we expect to
have the largest public deployment, so scaling and migration challenges will be
particularly interesting technical problems to
I am on PTO - if someone else wishes to chair the weekly meeting please feel
free to do so.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.__
OpenStack Development Mailing List (not for usage
Hi Stackers,
As part of my WIP work for implementing
https://blueprints.launchpad.net/nova/+spec/volume-snapshot-improvements I
am required to add a new table to cinder (snapshot_admin_metadata) and I
was looking for some inputs on whats are the steps to add a new table to
existing DB
From
Hello everyone,
The OpenStack Stable Maintenance team is happy to announce the release
of the 2014.2.3 stable Juno release. We have been busy reviewing and
accepting backported bugfixes to the stable/juno branches according
to the criteria set at:
https://wiki.openstack.org/wiki/StableBranch
A
Hi, I'm getting back from a little time off over the weekend.
Artem Dmytrenko and Jaume Devesa have done great work [1] with me over
the last year figuring out how to integrate routing protocols with
Neutron. We have had to exhibit some patience as this work has not
yet bubbled to the top of the
Guys,
I would like to nominate Andrey Skedzinskiy[1] for
fuel-qa[2]/fuel-devops[3] core team.
Andrey is one of the strongest reviewers, under his watchful eye are such
features as:
- updrade/rollback master node
- collect usage information
- OS patching
- UI tests
and others
Please vote for
-Original Message-
From: Attila Fazekas [mailto:afaze...@redhat.com]
Sent: Monday, April 13, 2015 3:19 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] Neutron scaling datapoints?
- Original Message -
From: joehuang
Worth noting we've already switched to using PyMySQL in nodepool,
storyboard and some of the subunit2sql tooling. It's been working
out great so far.
Great. Did you notice a performance regression? Mike wrote that PyMySQL is much
slower than MySQL-Python.
Victor
On 13/4/2015, at 3:53, Robert Collins robe...@robertcollins.net wrote:
On 13 April 2015 at 13:09, Robert Collins robe...@robertcollins.net wrote:
On 13 April 2015 at 12:53, Monty Taylor mord...@inaugust.com wrote:
What we have in the gate is the thing that produces the artifacts that
- Original Message -
From: joehuang joehu...@huawei.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Sunday, April 12, 2015 1:20:48 PM
Subject: Re: [openstack-dev] [neutron] Neutron scaling datapoints?
Hi, Kevin,
Andrew shows great attention to the details. +1 for him.
On Mon, Apr 13, 2015 at 11:22 AM, Anastasia Urlapova aurlap...@mirantis.com
wrote:
Guys,
I would like to nominate Andrey Skedzinskiy[1] for
fuel-qa[2]/fuel-devops[3] core team.
Andrey is one of the strongest reviewers, under his
What bad news.. Chris helped me a lot, we lost a mentor and friend.
May God bless his/her soul.
WingWJ
On Mon, Apr 13, 2015 at 1:03 PM, Gary Kotton gkot...@vmware.com wrote:
Hi,
I am very saddened to read this. Not only will Chris be missed on a
professional level but on a personal level. He
Hi Kevin,
Totally agree with you that heartbeat from each agent is something that we
cannot eliminate currently. Agent status depends on it, and further scheduler
and HA depends on agent status.
I proposed a Liberty spec for introducing open framework/pluggable agent status
drivers.[1][2] It
From now on magnum had container create and delete api .The container create
api will pull docker image from docker-registry.But the container delete api
didn't delete image.It will let the image remain even though didn't had
container use it.Is it much better we can clear the image in
Interesting topic, pulling image is time consuming, so someone might not
want to delete the container; But for some cases, if the image was not
used, then it is better to remove them from disk to release space. You may
want to send out an email to [openstack][magnum] ML to get more feedback ;-)
I would like to see some form of this merged at least as an error message.
If a server has a bad CMOS battery and suffers a power outage, it's clock
could easily be several years behind. In that scenario, the NTP daemon
could refuse to sync due to a sanity check.
On Wed, Apr 8, 2015 at 10:46 AM,
- Original Message -
From: Kevin Benton blak...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Sunday, April 12, 2015 4:17:29 AM
Subject: Re: [openstack-dev] [neutron] Neutron scaling datapoints?
So IIUC
Robert Collins wrote:
On 13 April 2015 at 13:09, Robert Collins robe...@robertcollins.net wrote:
On 13 April 2015 at 12:53, Monty Taylor mord...@inaugust.com wrote:
What we have in the gate is the thing that produces the artifacts that
someone installing using the pip tool would get. Shipping
http://developer.openstack.org/api-ref-networking-v2.html
The above api document seems lost most of the content, leaving only
port, network, subnet?
__
OpenStack Development Mailing List (not for usage questions)
+1
On Fri, Apr 10, 2015 at 1:35 PM, Roman Prykhodchenko m...@romcheg.me wrote:
+1. Sebastian does great job in reviews!
10 квіт. 2015 о 12:05 Igor Kalnitsky ikalnit...@mirantis.com
написав(ла):
Hi Fuelers,
I'd like to nominate Sebastian Kalinowski for the both fuel-web-core
[1]
While I was working on the grenade refactor I was considering using
openstack client for some resource create / testing. Doing so made me
realize that osc is sluggish. From what I can tell due to the way it
loads the world, there is a minimum 1.5s overhead on every command
execution. For instance,
On 11/04/15 14:02, Dan Prince wrote:
Looks like our SSL certificate has expired for the currently active CI
cloud. We are working on getting a new one generated and installed.
Until then CI jobs won't get processed.
A new cert has been installed in the last few minutes and ZUUL has
started
On Mon, Apr 13, 2015, henry hly henry4...@gmail.com wrote:
http://developer.openstack.org/api-ref-networking-v2.html
The above api document seems lost most of the content, leaving only
port, network, subnet?
In the navigation bar on the left there is a link to the rest of the Neutron
API,
Hi all,
Currently all patches in Cinderclient are getting -1 from Jenkins
because gate-tempest-dsvm-neutron-src-python-cinderclient-juno is
failing.
I opened a LP bug [1] on this, but basically the issue comes from Heat's
requirements cap on Cinderclient [2] to an upper bound of 1.1.1 when
+1
On Mon, Apr 13, 2015 at 11:37 AM, Alexander Kislitsky
akislit...@mirantis.com wrote:
Andrew shows great attention to the details. +1 for him.
On Mon, Apr 13, 2015 at 11:22 AM, Anastasia Urlapova
aurlap...@mirantis.com wrote:
Guys,
I would like to nominate Andrey Skedzinskiy[1] for
+1
On Mon, Apr 13, 2015 at 2:07 PM, Evgeniy L e...@mirantis.com wrote:
+1
On Fri, Apr 10, 2015 at 1:35 PM, Roman Prykhodchenko m...@romcheg.me
wrote:
+1. Sebastian does great job in reviews!
10 квіт. 2015 о 12:05 Igor Kalnitsky ikalnit...@mirantis.com
написав(ла):
Hi Fuelers,
Hi,
I made some investigation on the topic[1] and see several issues on this
way.
1. Plugin's create_port() is wrapped up in top level transaction for
create floating ip case[2], so it becomes more complicated to do IPAM
calls outside main db transaction.
- for create floating ip case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/10/2015 09:18 PM, Brandon Logan wrote:
Hi Ihar, I'm not against the lazy loading solution, just wondering
what the real issue is here. Is your problem with this that
python-barbicanclient needs to be in the requirements.txt? Or is
the
Hi everyone,
Although we'll discuss in Vancouver future changes in the release
schedule/model, for Liberty we'll still use a default 6-month cycle
with intermediary milestones.
Looking at the date for the Tokyo summit (Oct 27-30), that leaves two
options for the Liberty release date: Oct 15 or
I think there is a lot to discuss here and I would love to push for a
solution implemented in Liberty. I have a proposed summit session on this
topic (Asynchrounous Error Reporting). I also discussed this briefly at the
Kilo summit. I will work on formalizing some of these ideas and hopefully
we
+1
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Mon, Apr 13, 2015 at 1:09 PM, Dmitry Pyzhov dpyz...@mirantis.com wrote:
+1
On Mon, Apr 13, 2015 at 2:07 PM, Evgeniy L e...@mirantis.com wrote:
+1
On Fri, Apr 10, 2015 at 1:35 PM, Roman Prykhodchenko m...@romcheg.me
Hi,
1) I want to nominate Vladimir Sharshov to fuel-astute core. We hardly need
more core reviewers here. At the moment Vladimir is one of the main
contributors and reviewers in astute.
2) I want to nominate Alexander Kislitsky to fuel-stats core. He is the
lead of this feature and one of the
While we now have devstack external plugins, grenade (our upgrade
testing framework) was really monolithic. It grew out of a last minute
set of test scripts for Folsom that discovered a number of our database
migrations didn't work with real data in them, and that nova compute had
the annoying
+1
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Strong +1
Nastya forgot to mention Andey's participation in Ubuntu 14.04 feature.
With Andrey's help the feature went smooth and easy ;)
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Mon, Apr 13, 2015 at 12:37 PM, Vladimir Kuklin vkuk...@mirantis.com
wrote:
+1
On Mon,
We are facing an issue with Mistral devstack installation in our gate job
testing murano-congress-mistral integration (policy enforcement) [1] .
Mistral devstack scripts are failing with following import error [2]
Hi, Filip!
Recently Mistral has moved to new YAQL, and it seems this
Dumb question from me, is there an easy way to get a view that filters out
specs that haven't been re-submitted against the liberty directory?
You can use a regex in the files: filter, so I think you mean:
I like Duncan's idea. To have a dash in horizon where admin can see error
events. It can hide backend details from tenants and would save the time
of browsing through logs seeking for the operations that caused errors
(the request id also should be logged in the metadata to allow further
+1
On Mon, Apr 13, 2015 at 1:37 PM, Vladimir Kuklin vkuk...@mirantis.com
wrote:
+1
On Mon, Apr 13, 2015 at 11:37 AM, Alexander Kislitsky
akislit...@mirantis.com wrote:
Andrew shows great attention to the details. +1 for him.
On Mon, Apr 13, 2015 at 11:22 AM, Anastasia Urlapova
Hello
We are facing an issue with Mistral devstack installation in our gate
job testing murano-congress-mistral integration (policy enforcement) [1]
. Mistral devstack scripts are failing with following import error [2]
2015-04-12 14:06:25.236 | Traceback (most recent call last):
2015-04-12
On 2015-04-13 04:03:49 -0400 (-0400), Victor Stinner wrote:
Great. Did you notice a performance regression?
Nope. Worth noting, we implemented it primarily for its lack of
compiled extensions, and to a lesser because it supports Python 3.x.
I suspect if we do later run into any unexpected
Hi Nikolay Filip,
indeed, root cause of the issue is that Murano Mistral use different
version of yaql library. Murano installs yaql 0.2.4 and overrides
1.0.0b2 already installed and expected by Mistral.
We decided that we are not going to switch to the yaql 1.0.0 in Kilo
since we already
On Mon, Apr 13, 2015 at 8:44 AM, Pavel Bondar pbon...@infoblox.com wrote:
Hi,
I made some investigation on the topic[1] and see several issues on this
way.
1. Plugin's create_port() is wrapped up in top level transaction for
create floating ip case[2], so it becomes more complicated to do
Have we found the last of them? I wonder. I suppose any higher level
service like a router that needs to create ports under the hood (under
the API) will have this problem. The DVR fip namespace creation comes
to mind. It will create a port to use as the external gateway port
for that
Thanks for joining us today at #openstack-mistral
Meeting minutes:
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-04-13-16.20.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-04-13-16.20.html
Meeting log:
Hi,
This is a reminder about our team meeting today at 16.20 UTC at
#openstack-meeting.
Agenda:
Review AIs
Current Status
RC1 progress
Open Discussion
Thanks
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development
Hi Gorka,
Glance is seeing something very similar [3].
I've updated the two bugs ([1],[3]) with some extra info.
Both issues seem to have started around April 7th.
Would anyone from infra be able to take a quick look?
Thanks,
-Stuart
[3] https://bugs.launchpad.net/glance/+bug/1442682
- Original Message -
From: Kevin L. Mitchell kevin.mitch...@rackspace.com
To: openstack-dev@lists.openstack.org
Sent: Friday, April 10, 2015 5:47:26 PM
Subject: Re: [openstack-dev] [nova][database][quotas] reservations table ??
On Fri, 2015-04-10 at 02:38 -0400, Attila Fazekas
We are jubilant to announce the release of:
tooz 0.13.2: Coordination library for distributed systems.
This release is part of the stable/kilo series.
For more details, please see the git log history below and:
http://launchpad.net/python-tooz/+milestone/0.13.2
Please report issues
I proposed https://review.openstack.org/#/c/172522/ to fix this for all
projects whose versions are restricted by global requirements.
On Mon, Apr 13, 2015 at 5:55 PM, stuart.mcla...@hp.com wrote:
Hi Gorka,
Glance is seeing something very similar [3].
I've updated the two bugs ([1],[3])
Thanks Pavel. I see an additional case in L3_NAT_dbonly_mixin, where it
starts the transaction in create_router, then eventually gets to
create_port:
create_router (starts tx)
-self._update_router_gw_info
-_create_gw_port
-_create_router_gw_port
-create_port(plugin)
So that also would
George
What has been said is that:
1) With an async API, there is no error from the client in the request.
e.g. for a create, the request returns success well before the backend has
been contacted about the request. There is no path back to the client with
which to send an error.
2) Quite often
We already do this somewhat in gentoo (at least for some daemon
initialization stuff) in /etc/conf.d/$DAEMON_NAME.conf. Adding a
--config-dir option to that would be very simple. Gentoo at least will
also make the first --config-dir option (/etc/neutron) optional as well
since we have some users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/13/2015 05:42 PM, Matthew Thode wrote:
We already do this somewhat in gentoo (at least for some daemon
initialization stuff) in /etc/conf.d/$DAEMON_NAME.conf. Adding a
--config-dir option to that would be very simple. Gentoo at least
Hi all!
This time I'm trying to roughly follow OpenStack release procedures, so
ironic-discoverd just got a stable/1.1 branch, which is equivalent to
RC. I'm proud to say that the upcoming 1.1.0 release (which is scheduled
on Apr 30, just like other projects) is mostly about polishing
Sean,
Nice work on this. So now it's clear that starting time of libs makes
sense.
One way to improve this is to use https://github.com/boris-42/profimp that
allows to trace any python import
and not to import all modules when they are not required.
Btw I already saw few patches that are
1 - 100 of 104 matches
Mail list logo
