On 04/20/2015 12:10 PM, Victor Stinner wrote:
If there's nothing majorly wrong mid-L, I'd like to release 1.0.0 just
to get us into 'ok its stable' mentality.
I read that many packages modify the source code of libraries and
applications to avoid a dependency to pbr at runtime. What's the
On 21 April 2015 at 09:27, Thomas Goirand z...@debian.org wrote:
On 04/20/2015 12:10 PM, Victor Stinner wrote:
If there's nothing majorly wrong mid-L, I'd like to release 1.0.0 just
to get us into 'ok its stable' mentality.
I read that many packages modify the source code of libraries and
On Tue, Apr 21, 2015 at 8:38 AM, Fox, Kevin M kevin@pnnl.gov wrote:
As an Op, a few things that come to mind in that category are:
* RDO packaging (stated earlier). If its not easy to install, its not
going to be deployed as much. I haven't installed it yet, because I haven't
had time
Thanks Kevin, all good suggestions. Re Horizon UI, yes, we even have a
blueprint to track that, but seems the owner didn't complete it. FWIW, I
would suggest to put it on the todo list of L.
[1] https://blueprints.launchpad.net/zaqar/+spec/marconi-horizon-integration
On 21/04/15 10:38, Fox,
On 20 April 2015 at 07:40, Boris Pavlovic bo...@pavlovic.me wrote:
Dan,
IMHO, most of the test coverage we have for nova's neutronapi is more
than useless. It's so synthetic that it provides no regression
protection, and often requires significantly more work than the change
that is
Hi,
We have around 142 bugs without fix for now in our modules [1].
Some folks in our group raised an idea where we could do a bug triage
day sometimes.
I've created an etherpad so we can have a list of people interested to
participate [2] in this work.
Feel free to bring your name, and we will
On 21/04/15 11:01, Angus Salkeld wrote:
On Tue, Apr 21, 2015 at 8:38 AM, Fox, Kevin M kevin@pnnl.gov
mailto:kevin@pnnl.gov wrote:
As an Op, a few things that come to mind in that category are:
* RDO packaging (stated earlier). If its not easy to install, its
not going
On 20 April 2015 at 13:02, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Mon, 2015-04-20 at 13:57 -0600, Chris Friesen wrote:
However, minor changes like that could still possibly break clients
that are not
expecting them. For example, a client that uses the json response as
On Mon, Apr 20, 2015 at 03:10:40PM -0700, Ian Wells wrote:
On 20 April 2015 at 13:02, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Mon, 2015-04-20 at 13:57 -0600, Chris Friesen wrote:
However, minor changes like that could still possibly break clients
that are not
It'd be nice to having something like https://coveralls.io/features
which afaik just reports back on pull requests (and doesn't try to
enforce much of anything, aka non-voting).
For example: https://github.com/aliles/funcsigs/pull/13
In general it'd be neat if we could more easily
Hi,
I notified Glance (and probably other projects) are running the db_sync
with 'utf8_general_ci' by default.
* Can we change it? I've looked in Glance oslo.db, I've not seen anything.
* Can we configure it to stop enforcing this collation? Some deployments
are running 'utf8_unicode_ci'
* why
I've been spending some time getting quintupleo working on top of a Juno
RDO OpenStack. I'm at a point now where I think it is worth putting
effort into making it easy for anyone to try this.
Ben Nemec has done the hard work of proving this is possible[1]
resulting in the repo he uses to
Hi everybody - I'd like to call attention to the PyCon-AU OpenStack miniconf.
http://2015.pycon-au.org/cfp
Pycon-au is an excellent conference, and the OpenStack miniconf is now
in its third year - we're really getting into the swing of things.
Please submit a paper to the main conference CFP -
Ian,
If you were thinking instead to provide coverage *tools* that were easy for
developers to use,
Hm, seems like you missed the point. This gate job can be run like unit
tests tox -e cover. That will point you on the missing lines that are
introduced in your patch.
As a dev, I would not
On Mon, Apr 20, 2015 at 12:07 PM, Fox, Kevin M kevin@pnnl.gov wrote:
Another parallel is Manilla vs Swift. Both provides something like a share
for users to store files.
The former is a multitenant api to provision non multitenant file shares.
The latter is a multitenant api to provide
On 20 April 2015 at 04:54, Morgan Fainberg morgan.fainb...@gmail.com wrote:
Could you enlarge on what 'coordinating the requirements' means?
This is simply a choice to adhere to the global-requirements for a given
release (e.g. Liberty) that nova (and other projects) adhere to. We won't be
Hi Ramy,
While I agree, in principal, with this line of thinking and goal, my
concern will be how much extra work is it going to create for existing CI
owners?
Our Ci system has been stable for a long time, and we put in a good amount
of effort to get it to that point. Our CI is not based upon
Hi Devstack people,
I have developed two devstack plugins (for neutron-lbaas and octavia), and I
think I am stretching the capabilities of the devstack plugin architecture.
Neutron-lbaas is the load balancer framework for OpenStack. By default it uses
a fairly simple haproxy-based agent to
On 20 April 2015 at 15:23, Matthew Treinish mtrein...@kortar.org wrote:
On Mon, Apr 20, 2015 at 03:10:40PM -0700, Ian Wells wrote:
It would be nice to have a consistent policy here; it would make future
decision making easier and it would make it easier to write specs if we
knew what was
I think this is a good idea. We'd need an etherpad or may I suggest google
spreadsheet of the bugs so people can pick them off, especially since we're
all on different TZs and many of us will not be able to dedicate the full 8
hours to it.
On Mon, Apr 20, 2015 at 3:20 PM, Emilien Macchi
As an Op, a few things that come to mind in that category are:
* RDO packaging (stated earlier). If its not easy to install, its not going to
be deployed as much. I haven't installed it yet, because I haven't had time to
do much other then yum install it...
* Horizon UI
* Heat Resources.
On Tue, Apr 21, 2015 at 12:33 PM, x Lyn xuanlangj...@gmail.com wrote:
Since cloudwatch is deprecated, is there any plan to remove it away from
codes? Or still has some functions depend on this service?
No plans as yet, but all you have to do is not run the binary (heat-api-cw).
2015-04-18
Hi,
You can go through below link to get started.
http://docs.openstack.org/developer/swift/development_saio.html
Thanks
Madhuri Kumari
On Tue, Apr 21, 2015 at 2:09 PM, Subbulakshmi Subha
subbulakshmisubh...@gmail.com wrote:
Hi,
I am trying to simulate openstack swift.could you please
On 04/21/2015 03:45 AM, Kaneko Takehiro wrote:
Andreas,
Our project repository matches the project in Launchpad but the bug
status doesn't change(Triaged = In Progress).
Bug: https://bugs.launchpad.net/python-rack/+bug/1446058
Gerrit: https://review.openstack.org/#/c/175272/
that first
Since cloudwatch is deprecated, is there any plan to remove it away from
codes? Or still has some functions depend on this service?
2015-04-18 2:29 GMT+08:00 Zane Bitter zbit...@redhat.com:
On 17/04/15 13:54, Matt Fischer wrote:
On Fri, Apr 17, 2015 at 11:03 AM, Zane Bitter zbit...@redhat.com
I want to simulate it one javasim,so I want to know how are objects stored
in the partitions in swift.I computed the md5 hash of the objects url, n
the medium of storage is hashmap,so I want to know how doea it store it
there?is there any algorithm for it?
On 21-Apr-2015 10:59 AM, Madhuri Rai
Hi Mike,
Could you please take a look at the results and consider re-integrating
the driver? We the Oracle ZFSSA team would like to target the Kilo RC
deadline if possible.
Thank you,
Diem.
On 4/20/15 3:47 PM, Diem Tran wrote:
Hi Mike,
Oracle ZFSSA iSCSI CI is now reporting test results.
Hi, Edgar
Some docs are still in private branch. Can we move to public branch for
reviewing submitting patches?
Thanks,
-Ruijing
From: Edgar Magana [mailto:edgar.mag...@workday.com]
Sent: Saturday, April 18, 2015 2:25 AM
To: OpenStack Development Mailing List (not for usage questions)
Hi,
I am trying to simulate openstack swift.could you please help me with
getting started.what are all the details I should be knowing to store
objects on swift?
__
OpenStack Development Mailing List (not for usage
Andreas,
Our project repository matches the project in Launchpad but the bug status
doesn't change(Triaged = In Progress).
Bug: https://bugs.launchpad.net/python-rack/+bug/1446058
Gerrit: https://review.openstack.org/#/c/175272/
The following change has been merged.(
On Mon, Apr 20, 2015 at 1:18 PM, Duncan Thomas duncan.tho...@gmail.com
wrote:
Hi Diem
It appears the CI failed to pass on any of the 5 reviews you linked to.
Are there any examples of the CI passing?
I don't see any passing runs in the last 20 comments left by 'Oracle ZFSSA
CI'
Morgan,
Thank you for your input. I improved coverage job in this patch:
https://review.openstack.org/#/c/175557/1
Now:
* It is based on missing lines and not coverage percentage.
* It shows nice messages and coverage diffs:
Allowed to introduce missing lines : 8
Missing lines in master
Hi Diem
It appears the CI failed to pass on any of the 5 reviews you linked to. Are
there any examples of the CI passing?
On 20 April 2015 at 20:47, Diem Tran diem.t...@oracle.com wrote:
Hi Mike,
Oracle ZFSSA iSCSI CI is now reporting test results. It is configured to
run against the ZFSSA
On 04/17/2015 08:45 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
tl;dr neutron has special semantics for policy targets that relies on
private symbols from oslo.policy, and it's impossible to introduce
this semantics into oslo.policy itself due to backwards
On 21 April 2015 at 03:24, Sean Dague s...@dague.net wrote:
On 04/20/2015 11:20 AM, Morgan Fainberg wrote:
...
Re publishing milestones: TBD. I wanted to discuss that with release
management team and see if that made sense. I believe it does make
sense, but have not determined that for sure.
Awesome, thanks Josh.
On 04/20/2015 07:14 AM, Joshua Hesketh wrote:
Hi Sean,
Thanks for your work on this. I'll take a closer look tomorrow and remove the
downgrade testing from turbo-hipster in line with the TC decision.
Cheers,
Josh
From:
You rock, Ramy. Seriously, awesome work.
-jay
On 04/20/2015 01:17 AM, Asselin, Ramy wrote:
All Third-Party CI operators:
We’ve got 85 Third Party CI systems registered in the wiki[1], all of
them running a variety of closed open-source solutions.
Instead of individually maintaining all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/20/2015 12:20 PM, Miguel Angel Ajo Pelayo wrote:
Thank you Irena,
I believe this last minute change deserves an explanation, I asked
Irena to write to the list on my behalf (thank you!).
I got a surgery to one of my kids scheduled on
Hi all,
Another milestone of Mistral (Kilo RC1) is released!
Below are the links to Mistral and Mistral Client release pages where you can
find downloadables and info about fixed bugs.
Mistral: https://launchpad.net/mistral/kilo/kilo-rc1
https://launchpad.net/mistral/kilo/kilo-rc1
Mistral
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/20/2015 02:22 PM, Victor Stinner wrote:
I believe Redhat patch it out. I don't think they should need
to, since we have explicit knobs for distros to use.
pbr pulls pip which we don't want in RHEL. Example of patches in
RDO:
This is a reminder about a team meeting today that we’ll hold at
#openstack-mistral at 16.20 UTC.
Agenda:
Review action items
Current status (progress, issues, roadblocks, further plans)
What's left to do in Kilo? (critical bugs, docs etc.)
Open discussion
[0]
I don't think its a bug in the applications.
swift gets its version using pkg_resources, or falls back to pbr:
https://github.com/openstack/swift/blob/master/swift/__init__.py
I mean that other applications may do something similar?
Victor
On 04/20/2015 08:22 AM, Victor Stinner wrote:
I believe Redhat patch it out. I don't think they should need to,
since we have explicit knobs for distros to use.
pbr pulls pip which we don't want in RHEL. Example of patches in RDO:
On 04/20/2015 03:19 AM, Jaume Devesa wrote:
Hi Ramy,
Soon I'll be the responsible of the Midokura's third-party CI, which has been
mute for a while because a flaky physical resources that our sys admins
couldn't take care because they are overloaded of work...
Count on me!
I do hope luqas
On 19 April 2015 at 02:23, Jay Pipes jaypi...@gmail.com wrote:
On 04/13/2015 12:39 PM, Carl Baldwin wrote:
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
On 04/20/2015 07:13 AM, Sean Dague wrote:
On 04/18/2015 09:30 PM, Boris Pavlovic wrote:
Hi stackers,
Code coverage is one of the very important metric of overall code
quality especially in case of Python. It's quite important to ensure
that code is covered fully with well written unit tests.
On 19/Apr/2015 .::. 14:18, Emilien Macchi wrote:
We are adding Puppet 4.0 unit testing jobs support as non-voting for
now: https://review.openstack.org/175145
The workflow will be:
* have the non-voting jobs in check pipeline
* make the test work for our modules
First, rspec-puppet have to
I believe Redhat patch it out. I don't think they should need to,
since we have explicit knobs for distros to use.
pbr pulls pip which we don't want in RHEL. Example of patches in RDO:
https://github.com/redhat-openstack/nova/commit/a19939c8f9a7b84b8a4d713fe3d26949e5664089
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/20/2015 12:34 AM, Brant Knudson wrote:
On Sun, Apr 19, 2015 at 3:07 PM, Brant Knudson b...@acm.org
mailto:b...@acm.org wrote:
Ever since the stable/icehouse branch was created for
python-keystoneclient it's been broken. There are a
Hi Boris,
thanks for your proposal.
As for the agenda, I really think it's important to have it in advance. How
are we going to prepare it? Google docs? Who is going to be responsible for
that?
As for the meeting time, I'm ok with 15:00 UTC, as well as with some
earlier time that would satisfy
Hi all,
as some of you probably know, Rally has recently adopted a release-based
software development model. The latest release is 0.0.3 (appeared on Apr
14).
We have set as our goal to have a new release every 2-3 weeks. Since this
is quite ambitious and not so easy to achieve, we are also
Hi,
Debian are hitting this issue https://bugs.launchpad.net/glance/+bug/1445827.
Currently glance and glance_store include ordereddict in their
requirements.txt. Since Glance no longer gates on py26 I think it should
be ok to remove that requirement from glance and glance_store
(both repos
confirmed
On 04/20/2015 05:56 AM, Thierry Carrez wrote:
Hello list,
I'm announcing my candidacy for the Technical Committee elections.
I have been serving as the chair of the Technical Committee since its
inception, but I think we are at a critical point in the evolution of
the role of
Greetings,
I'd like my first action as Zaqar's PTL to be based on reflections and
transparency with regards to what our past has been, to what our
present is and to what our future could be as a project and community.
Therefore, I'm sending this call for adoption and support before
taking other
Tagging as `[all]`, sorry about that!
On 20/04/15 14:54 +0200, Flavio Percoco wrote:
Greetings,
I'd like my first action as Zaqar's PTL to be based on reflections and
transparency with regards to what our past has been, to what our
present is and to what our future could be as a project and
Thank you Irena,
I believe this last minute change deserves an explanation, I asked Irena to
write to the list on my behalf (thank you!).
I got a surgery to one of my kids scheduled on Wednesday (it’s something
very mild near the ear), also it’s holiday for a few of the participants that
Hi Sean,
Thanks for your work on this. I'll take a closer look tomorrow and remove the
downgrade testing from turbo-hipster in line with the TC decision.
Cheers,
Josh
From: Sean Dague s...@dague.net
Sent: Monday, 20 April 2015 8:38 PM
To: OpenStack
On 04/20/2015 09:26 AM, Kaneko Takehiro wrote:
Hi,
I'm managing a stackforge project and want to integrate Gerrit with
Launchpad.
Links;
Git: https://git.openstack.org/cgit/stackforge/rack/
Launchpad: https://launchpad.net/python-rack
Project name 'rack' is duplicated in Launchpad so I
Andreas,
I missed it.
Thanks for your help.
Takehiro
2015-04-20 16:40 GMT+09:00 Andreas Jaeger a...@suse.com:
On 04/20/2015 09:26 AM, Kaneko Takehiro wrote:
Hi,
I'm managing a stackforge project and want to integrate Gerrit with
Launchpad.
Links;
Git:
Sean Dague wrote:
Proposed actions are to do both of:
- oslo.messaging release with heartbeats off by default (simulates 1.8.0
behavior before the heartbeat code landed)
- oslo.messaging requiring py-amqp = 1.4.0, so that if you enable the
heartbeating, at least you are protected from the
Hi,
Agree with all proposes. But maybe it's make sense to do a bigger interval
between mitings to make as much as possible work for the next meting. For
example Monday/Thursday. Its not principal for me.
-Thanks, Roman Vasilets.
On Fri, Apr 17, 2015 at 4:26 PM, Boris Pavlovic bo...@pavlovic.me
If there's nothing majorly wrong mid-L, I'd like to release 1.0.0 just
to get us into 'ok its stable' mentality.
I read that many packages modify the source code of libraries and applications
to avoid a dependency to pbr at runtime. What's the status of this issue? Is
pbr still used/required
On 04/19/2015 12:54 PM, Morgan Fainberg wrote:
On Sunday, April 19, 2015, Robert Collins robe...@robertcollins.net
mailto:robe...@robertcollins.net wrote:
On 18 April 2015 at 15:20, Morgan Fainberg
morgan.fainb...@gmail.com javascript:; wrote:
Hi everyone,
I
Yes. Totally agree. I hate it that I have to spend a giant amount of
effort on one of my clouds to get a working network to my VMs when on
the other cloud I get a VM that can talk to the network.
Guess which one I think should be the default behavior?
Whichever one you choose to deploy with
Sorry, I have incorrectly read the proposed meeting days. Meetings of
Monday and Wednesday are okay, but I agree with Roman that Monday/Thursday
would be a bit better.
Best regards,
Mikhail Dubov
Engineering OPS
Mirantis, Inc.
E-Mail: mdu...@mirantis.com
Skype: msdubov
On Mon, Apr 20, 2015 at
This proposed patch to drop the db downgrades in Nova master is making
Turbo Hipster face plant - https://review.openstack.org/#/c/175010/
It appears that turbo hipster is walking all the way up, then walking
back down through migrations, which clearly, is no longer a thing.
It would be nice to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
UPD: dibbler packages are now available in all Fedora updates
repositories, starting from Fedora 20, plus EPEL7.
Packages are called: dibbler-[client|docs|requestor|relay|server].
Specifically, you can locate them at:
On 20 April 2015 at 22:10, Victor Stinner vstin...@redhat.com wrote:
If there's nothing majorly wrong mid-L, I'd like to release 1.0.0 just
to get us into 'ok its stable' mentality.
I read that many packages modify the source code of libraries and
applications to avoid a dependency to pbr at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/17/2015 07:49 PM, Salvatore Orlando wrote:
== 2. filling in admin context with admin roles ==
Admin context object is filled with .roles attribute that is a list
of roles considered granting admin permissions [4]. The attribute
would then
So, we've fixed up the semver logic.
I went through the review backlog and merged the stuff that was good.
One thing in particular was problematic - prompting me to put up
https://review.openstack.org/#/c/174646/ - the commit this backs out
added per-platform requirements.txt files, which in
On 20 April 2015 at 10:03, Ihar Hrachyshka ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/17/2015 07:49 PM, Salvatore Orlando wrote:
== 2. filling in admin context with admin roles ==
Admin context object is filled with .roles attribute that is a list
Hi Ramy,
Soon I'll be the responsible of the Midokura's third-party CI, which has been
mute for a while because a flaky physical resources that our sys admins
couldn't take care because they are overloaded of work...
Count on me!
On Mon, 20 Apr 2015 05:17, Asselin, Ramy wrote:
All Third-Party
Hello list,
I'm announcing my candidacy for the Technical Committee elections.
I have been serving as the chair of the Technical Committee since its
inception, but I think we are at a critical point in the evolution of
the role of the Technical Committee, and if you allow it, I'd like to be
- We should start making agenda for each meeting and publish it to
Rally wiki
+1
- We should do 2 meeting per week:
We can do both things in one meeting.
__
OpenStack Development Mailing List (not for usage
Hi,
I'm managing a stackforge project and want to integrate Gerrit with
Launchpad.
Links;
Git: https://git.openstack.org/cgit/stackforge/rack/
Launchpad: https://launchpad.net/python-rack
Project name 'rack' is duplicated in Launchpad so I named our project
'python-rack'.
How can I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nah, pointing --config-dir, either as one or as one of many arguments,
is just plain wrong. We want to have a way to set different
configuration values for different services, so merging all
configuration files into single pile of Neutron
Hi,
This week neutron QoS meeting will take place on Tuesday, April 21 at 14:00
UTC on #openstack-meeting-3.
Next week, the meeting is back to its original slot: Wed at 14:00 UTC on
#openstack-meeting-3.
Please join if you are interested.
On 04/18/2015 09:30 PM, Boris Pavlovic wrote:
Hi stackers,
Code coverage is one of the very important metric of overall code
quality especially in case of Python. It's quite important to ensure
that code is covered fully with well written unit tests.
One of the nice thing is coverage
Hi,
Tomorrow is our weekly meeting.
Please look at the agenda [1].
Feel free to bring new topics and reviews/bugs if needed.
Also, if you had any action, make sure you can give a status during the
meeting or in the etherpad directly.
See you tomorrow,
[1]
I do agree with your suggestion. I will update the wiki and we will be using
the #openstack-sprint IRC channel
Cheers!
Edgar
From: Anne Gentle
annegen...@justwriteclick.commailto:annegen...@justwriteclick.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
CAD85om3RJg4fDHDKPZpmcboF+=aknm9wqo08bas0eov8dey...@mail.gmail.com
On 2015-04-17 16:26:29 +0300 (-0300), Boris Pavlovic wrote:
[...]
- Move meetings from #openstack-meeting to #openstack-rally chat.
[...]
Please don't. This means anyone who wants to be around in case an
important topic comes up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/17/2015 12:56 AM, Carl Baldwin wrote:
Stephen,
On Thu, Apr 16, 2015 at 4:21 PM, Ma, Stephen B. stephen...@hp.com
wrote:
As it stands currently, neutron on the stable/juno branch behaves
as if https://review.openstack.org/#/c/164329/ was
Gordon,
+1. i don't think this would be a good idea as a non-voting job either as
it can/will lead to lazy reviews.
It is similar to say let's remove unit/functional/pep8/pylint/any other
testing because it will lead to lazy reviews.
Best regards,
Boris Pavlovic
On Mon, Apr 20, 2015 at
RDO packaging would go a long way for us.
Also what about oslo support? We have a second rabbit for
sahara/trove/designate for reasons I wont get into here on one cloud that could
just be made to use Zaqar instead?
I do believe Zaqar is very important. Its been a long bumpy road, but you folks
Hey Everyone!
Here’s a link to the hangout:
https://plus.google.com/hangouts/_/hoaevent/AP36tYenNDpCZC-E2cbqw7050E-AG7RI8SL6bWjGMyuYGKGkCJIcpw?authuser=0hl=en
https://plus.google.com/hangouts/_/hoaevent/AP36tYenNDpCZC-E2cbqw7050E-AG7RI8SL6bWjGMyuYGKGkCJIcpw?authuser=0hl=en
And here’s the link
Dan,
IMHO, most of the test coverage we have for nova's neutronapi is more
than useless. It's so synthetic that it provides no regression
protection, and often requires significantly more work than the change
that is actually being added. It's a huge maintenance burden with very
little value,
Well, I think there are very few cases where *less* coverage is better.
IMHO, most of the test coverage we have for nova's neutronapi is more
than useless. It's so synthetic that it provides no regression
protection, and often requires significantly more work than the change
that is actually
On 04/17/2015 11:31 PM, Morgan Fainberg wrote:
As a quick update, for the Liberty cycle, keystone will be using the first
milestone as our Spec Proposal Freeze (SPF), with Feature Proposal Freeze (API
Impacting features must be code complete / ready for review / gating) at the
second
Congratulations!!
The same for you JJ!
Edgar
From: Jay Lau jay.lau@gmail.commailto:jay.lau@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Sunday, April 19, 2015 at 10:52 PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/20/2015 10:26 AM, Ihar Hrachyshka wrote:
On 04/20/2015 12:34 AM, Brant Knudson wrote:
On Sun, Apr 19, 2015 at 3:07 PM, Brant Knudson b...@acm.org
mailto:b...@acm.org wrote:
Ever since the stable/icehouse branch was created for
On Mon, Apr 20, 2015 at 8:44 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/20/2015 12:20 PM, Miguel Angel Ajo Pelayo wrote:
Thank you Irena,
I believe this last minute change deserves an explanation, I asked
Irena to write to the
Hello Glance folks, and not Glance folks :D
Here's a thought. I believe, based on the size of our
project/community/reviewers team, we should just give access to all
glance-cores to glance-drivers. Few considerations:
1) Many of our reviewers have been part of Glance even before I became
part
This proposed patch requiring a data migration in Nova master is making
Turbo Hipster face plant - https://review.openstack.org/#/c/174480/
This is because we will require Kilo deployers to fully migrate their
flavor data from system_metadata to instance_extra before they upgrade
to the next
On 04/20/2015 08:54 AM, Flavio Percoco wrote:
Greetings,
I'd like my first action as Zaqar's PTL to be based on reflections
and transparency with regards to what our past has been, to what
our present is and to what our future could be as a project and
community. Therefore, I'm sending this
Date: Mon, 20 Apr 2015 07:13:31 -0400
From: s...@dague.net
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all][code quality] Voting coverage job (-1 if
coverage get worse after patch)
On 04/18/2015 09:30 PM, Boris Pavlovic
Hi Kiall,
Will appreciate if you can provide your comments on the email below.
Regards, Anik
From: Anik anik...@yahoo.com
To: openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org
Sent: Saturday, April 11, 2015 5:37 AM
Subject: Re: [openstack-dev] Multi Region
Let's not mix the bad unit tests in Nova with the fact that code should
be fully covered by well written unit tests.
I'm not using bad tests in nova to justify not having coverage testing.
I'm saying that the argument that more coverage is always better has
some real-life counter examples.
+1, Jeremy. Excellent points.
-jay
On 04/20/2015 10:59 AM, Jeremy Stanley wrote:
CAD85om3RJg4fDHDKPZpmcboF+=aknm9wqo08bas0eov8dey...@mail.gmail.com
On 2015-04-17 16:26:29 +0300 (-0300), Boris Pavlovic wrote:
[...]
- Move meetings from #openstack-meeting to #openstack-rally chat.
[...]
Hi,
In the following patch, I had a question about setting the IPXE tag by
default.
https://review.openstack.org/#/c/172040/
Basically, I'm unsure if we want to set this tag by default. I freely
admit that I'm not an expert in PXE, but my thinking is that rather than
enabling it by default, we
On 20/04/15 18:01, Clint Byrum wrote:
Excerpts from Boris Pavlovic's message of 2015-04-18 18:30:02 -0700:
Hi stackers,
Code coverage is one of the very important metric of overall code quality
especially in case of Python. It's quite important to ensure that code is
covered fully with well
1 - 100 of 133 matches
Mail list logo
