I know about the flow but what i'm questioning is:
admin endpoint is mapped to br-mgmt subnet (you do have the HAproxy as
below defined in 6.1. In 6.0 and before you had no HAproxy)
listen keystone-2
bind 192.168.20.3:35357
option httpchk
option httplog
option httpclose
server node-1
Hi Anne,
2015-07-09 12:22 GMT+09:00 Anne Gentle :
> On Wed, Jul 8, 2015 at 9:48 PM, GHANSHYAM MANN
> wrote:
>> On Thu, Jul 9, 2015 at 9:39 AM, Ken'ichi Ohmichi
>> wrote:
>> > 2015-07-08 16:42 GMT+09:00 Ken'ichi Ohmichi :
>> >> 2015-07-08 14:07 GMT+09:00 GHANSHYAM MANN :
>> >>> On Wed, Jul 8, 201
Hello,
The scenario I mentioned in the weekly meeting is described in the following
google doc:
https://docs.google.com/presentation/d/1s0tRI3GtzSR5Dcl0YGSZ2upEwdqPsqU0d6-rq0CRMQo/edit#slide=id.gb6e146160_0_25
To reduce the complexity, I suggest we focus on the scenario 1 in the current
phase.
That is a semantic change to the api that will break anybody who has
tooling expecting the current behavior. Since there are perfectly sensible
uses of the current behavior, that is not a good thing.
On 10 Jul 2015 07:33, "hao wang" wrote:
> Cinder now doesn't check the existing resource when use
Good news everybody, mock 1.1.0 is now out. This backports all the
improvements over the last couple of years, making it fully
synchronised with cPython master. Yay.
Bad news. Lots of unit tests jobs have suffered falled from this.
But - none of the things I've looked into so far are bugs in mock
On Fri, Jul 10, 2015 at 10:28:06AM +0300, Duncan Thomas wrote:
> That is a semantic change to the api that will break anybody who has
> tooling expecting the current behavior. Since there are perfectly sensible
> uses of the current behavior, that is not a good thing.
Hi Duncan,
I don't think tha
I'd like to switch the status of ~200 bugs at once to adjust the
bookkeeping in LaunchPad. This will concern "Confirmed" and "Triaged"
bugs which have an assignee [1]. AFAIK they should be "In Progress".
I'm concerned if this would affect some reports I'm not aware of in
a bad way. So, if you thin
Robert Collins wrote:
> Good news everybody, mock 1.1.0 is now out. This backports all the
> improvements over the last couple of years, making it fully
> synchronised with cPython master. Yay.
>
> Bad news. Lots of unit tests jobs have suffered falled from this.
>
> But - none of the things I've
Feel free to start the work. Right now I’m working on c-vol’s create_volume
flow. Review is there: https://review.openstack.org/#/c/193167/
From: hao wang [mailto:sxmatch1...@gmail.com]
Sent: Friday, July 10, 2015 4:47 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: R
How do we test to see what is failing in each project with the new version?
Also, I'm responsible for the reference to the private mock method in
Neutron. That particular reference is to prevent people from patching the
same target twice because mock.patch.stopall() unwinds patches in a
non-determ
On 10 July 2015 at 20:23, Kevin Benton wrote:
> How do we test to see what is failing in each project with the new version?
Look at any CI failure in the last 5 hours or so.
Or run tox :).
> Also, I'm responsible for the reference to the private mock method in
> Neutron. That particular referen
Kevin Benton wrote:
> How do we test to see what is failing in each project with the new version?
Just watch one of the thousands tests currently failing in zuul:
http://status.openstack.org/zuul/
Or see the recent periodic stable maint jobs fail reports at:
http://lists.openstack.org/pipermail/o
Hi,
We've been testing a multi-node setup with our driver and ended up in a
strange situation:
- having a driver configured on multiple cinder nodes (But not all)
- having a volume type (available)
- creating a volume with specified volume type causes the volume to be
created (attempted) on a node
On 10 July 2015 at 20:18, Thierry Carrez wrote:
> Robert Collins wrote:
>> Good news everybody, mock 1.1.0 is now out. This backports all the
...
>> 1.1.0 makes that an error, for methods with assert prefixes - unless
>> unsafe is specifically requested. So a big chunk of the failing tests
>> are
Joshua Harlow wrote:
> Hi all,
>
> I was thinking about those who are packaging with venvs (and using the
> version of a project in the venv file name); like what anvil[1] is now
> capable of (and does this in the gate now[2]) or packaging via rpms
> (which anvil also does) and they are going to b
Ah, I apologise, I missed the but where it defaults to force=true. I
withdraw the objection.
I've no strung feelings about the change either way, in that case.
On 10 Jul 2015 10:58, "Gorka Eguileor" wrote:
> On Fri, Jul 10, 2015 at 10:28:06AM +0300, Duncan Thomas wrote:
> > That is a semantic ch
Thanks. I didn't realize it was already breaking everything. I thought it
might have been stuck in requirements bump patch somewhere.
>Thats fixed in 1.1.0. So you should be able to unwind that. If you need a
short term workaround, its in mock.mock now.
Yeah, I know it's fixed, I reported the ups
Hi all.
I have a brief question about nova and nova-docker.
In nova-docker I add a piece of code when I raise an exception, in
particular in 'novadocker/virt/docker/driver.py', function
'_start_container':
*
exitcode=self.docker.inspect_container(container_id)['State']['ExitCode']*
*if exi
On 10 July 2015 at 20:50, Kevin Benton wrote:
> Thanks. I didn't realize it was already breaking everything. I thought it
> might have been stuck in requirements bump patch somewhere.
>
>>Thats fixed in 1.1.0. So you should be able to unwind that. If you need a
>> short term workaround, its in moc
Adam Lawson wrote:
> The alternative of course is to just number the releases since names
> ultimately don't mean anything but it seems there are problems with that
> level of simplicity. I personally prefer Tristan's suggestion to keep it
> as simple as possible. In a few years we'll run out of le
On 10/07/15 10:19, Thierry Carrez wrote:
Part of the confusion here is that we are not naming "releases". We are
naming release *cycles*. We are giving a name to a period of time,
basically. In that period of time, various version numbers for various
components will be released. Saying "Glance 1
Hi, Duncan
As Gorka said, we are trying not to impact default API behavior, just give
a choice to client that it can restrict cloud admin to update quota lower
than current usage.
2015-07-10 16:47 GMT+08:00 Duncan Thomas :
> Ah, I apologise, I missed the but where it defaults to force=true. I
>
Sure, I have got this review link. :)
2015-07-10 16:10 GMT+08:00 Dulko, Michal :
> Feel free to start the work. Right now I’m working on c-vol’s
> create_volume flow. Review is there:
> https://review.openstack.org/#/c/193167/
>
>
>
> *From:* hao wang [mailto:sxmatch1...@gmail.com]
> *Sent:* Fri
No prob. The fixes for Neutron were relatively trivial.
https://review.openstack.org/#/c/200420/
The only one that was a bit surprising was the failure of autospec in this
file:
https://review.openstack.org/#/c/200420/4/neutron/tests/unit/services/metering/agents/test_metering_agent.py
It was com
On 10 July 2015 at 22:07, Kevin Benton wrote:
> No prob. The fixes for Neutron were relatively trivial.
> https://review.openstack.org/#/c/200420/
>
> The only one that was a bit surprising was the failure of autospec in this
> file:
> https://review.openstack.org/#/c/200420/4/neutron/tests/unit/s
On 07/10/2015 03:45 AM, Robert Collins wrote:
> Good news everybody, mock 1.1.0 is now out. This backports all the
> improvements over the last couple of years, making it fully
> synchronised with cPython master. Yay.
>
> Bad news. Lots of unit tests jobs have suffered falled from this.
>
> But -
On 07/10/2015 04:09 AM, Markus Zoeller wrote:
> I'd like to switch the status of ~200 bugs at once to adjust the
> bookkeeping in LaunchPad. This will concern "Confirmed" and "Triaged"
> bugs which have an assignee [1]. AFAIK they should be "In Progress".
>
> I'm concerned if this would affect som
Daniel
Yes, if you want to do some administrative stuff you need to have access to
management network to be able to work with internal and admin endpoints.
On Fri, Jul 10, 2015 at 9:58 AM, Daniel Comnea
wrote:
> I know about the flow but what i'm questioning is:
>
> admin endpoint is mapped to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/10/2015 05:15 AM, Gareth wrote:
> Hi guys
>
> My problem looks simple:
>
> Running "tox -e pep8", the result says ok, not pep8 mistakes.
> Running "pep8 .", a lot of pep8 mistkes come out.
>
> But in your project's tox.ini, there isn't such
Sorry to leave this unanswered.
It happens every time (as far as we've tested so far).
A pragmatic fix appears to be to explicitly requery the IPAllocation
table, as you can see in the two commits here:
https://github.com/Metaswitch/calico/commit/5512ce7dd50db414f161bddcef17b0846a1466ac
https:
>Running "pep8 .", a lot of pep8 mistkes come out.
1) `pep8 .` checks all files in directory(including build files, envs and
etc).
2) `pep8 .` doesn't use tox.ini file, which can contain list of ignored
rules. For example, it can looks like:
[flake8]
ignore = H703
3) Most of OpenStack projects us
Hello Cinder Community!
The Quobyte Cinder CI [1] is back reporting since tuesday late afternoon UTC.
It is working stably with 8 test failing because of a Nova [2] and a
Driver/Cinder bug [3].
Result logs can be reviewed at [4] (FYI: these also contain sandbox test logs).
Over the last weekend
Hi all,
Recent breakage makes me finally raise the question that bothered me for
some time: are there possible alternatives to mock library we could use?
A couple reasons for that:
1. Devs don't seem to care about semver, backward compatibility and all
this boring stuff. Releasing a minor ve
Here is a fix for Swift:
https://review.openstack.org/200474
Victor
On 10/07/2015 09:45, Robert Collins wrote:
Good news everybody, mock 1.1.0 is now out. This backports all the
improvements over the last couple of years, making it fully
synchronised with cPython master. Yay.
Bad news. Lots of
On 10 July 2015 at 23:04, Dmitry Tantsur wrote:
> Hi all,
>
> Recent breakage makes me finally raise the question that bothered me for
> some time: are there possible alternatives to mock library we could use?
There are. Personally, mock is probably about equal evil-wise to any
mocking library -
On 10/07/2015 10:42, Robert Collins wrote:
Releasing this on a Friday sounds like bad timing, especially without
advance notice that we'd have to rush to fix the dozens of new issues it
would expose.
There would never be a good time to release such things. The whole
point of the constraints sys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
as you probably know, QoS feature is on horizon for Liberty and uses a
separate feature/qos branch. It's expected that after it's complete,
the branch is merged back into master.
Note that it will probably be the first (or the second, if
fe
On 2015-07-10 03:15:08 + (+), Gareth wrote:
> My problem looks simple:
>
> Running "tox -e pep8", the result says ok, not pep8 mistakes.
> Running "pep8 .", a lot of pep8 mistkes come out.
>
> But in your project's tox.ini, there isn't such a long ignore list. So what
> makes this differe
On 07/10/2015 01:13 PM, Robert Collins wrote:
On 10 July 2015 at 23:04, Dmitry Tantsur wrote:
Hi all,
Recent breakage makes me finally raise the question that bothered me for
some time: are there possible alternatives to mock library we could use?
There are. Personally, mock is probably abou
On 2015-07-10 13:21:56 +0200 (+0200), Victor Stinner wrote:
> I see "mock===1.0.1" in upper-constraints.txt, but the python27
> check job of Swift was broken by the release of mock 1.1.
>
> Can someone please explain me why Swift check job failed?
As far as I'm aware, only DevStack is making use
On 2015-07-10 19:45:10 +1200 (+1200), Robert Collins wrote:
[...]
> Python 2.6 support was dropped in 1.1.0, so we need to use markers
> to select 1.0.1 for the remaining 2.6 gate jobs. (We should kill
> those of asap).
[...]
Unless we convince ourselves it's worthwhile to EOL Juno early, we
can't
Hi folks,
Ability to manage multiple versions of application packages and their
dependencies was always an important item in Murano roadmap, however we
still don't have a clear spec for this feature.
Yesterday we hosted a small design session to come up with a plan on what
can be done in Liberty t
On 10 July 2015 at 23:34, Dmitry Tantsur wrote:
> On 07/10/2015 01:13 PM, Robert Collins wrote:
> I see that a lot of code started breaking due to
>
> side_effect = Exception()
>
> no longer working. Which was a declared way for some time, at least to my
> best knowledge. And I do realize it's j
On 07/10/2015 02:00 PM, Robert Collins wrote:
On 10 July 2015 at 23:34, Dmitry Tantsur wrote:
On 07/10/2015 01:13 PM, Robert Collins wrote:
I see that a lot of code started breaking due to
side_effect = Exception()
no longer working. Which was a declared way for some time, at least to my
Thanks Mike for the heads up
I fixed it for GlusterFS CI [1]
Post the fix, glusterfs CI jobs are running fine [2] See Jul 10, 10:43 AM
onwards
thanx,
deepak
[1]: https://review.openstack.org/#/c/200399/2
[2]:
https://jenkins07.openstack.org/job/check-tempest-dsvm-full-glusterfs-nv/
On Fri, Jul
+1
On 7/10/15, 1:32 PM, "Sean Dague" wrote:
>On 07/10/2015 04:09 AM, Markus Zoeller wrote:
>> I'd like to switch the status of ~200 bugs at once to adjust the
>> bookkeeping in LaunchPad. This will concern "Confirmed" and "Triaged"
>> bugs which have an assignee [1]. AFAIK they should be "In Pro
On 07/09/2015 06:14 PM, Andrew Woodward wrote:
We often have bugs which create really poor User eXperience (UX) but our
current bug priority criteria prevent nearly all of them from being
higher than medium (as they nearly always have workarounds). We need to
identify what should qualify as a cri
+1 Welcome Tom!
-Original Message-
From: Adrian Otto [mailto:adrian.o...@rackspace.com]
Sent: July-09-15 10:21 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [magnum] Tom Cammann for core
Team,
Tom Cammann (tcammann) has become a valued Magnum contributor, and consis
+1 welcome aboard Tom!
Regards
-steve
On 7/9/15, 7:20 PM, "Adrian Otto" wrote:
>Team,
>
>Tom Cammann (tcammann) has become a valued Magnum contributor, and
>consistent reviewer helping us to shape the direction and quality of our
>new contributions. I nominate Tom to join the magnum-core team
Hi Eduard,
What extra_specs do you configured in this volume_type?
Yes you can force a volume to an specific node, or backend. You must
configure the volume_backend_name on cinder.conf, and add an extra spec
"volume_backend_name='same_as_in_cinder_conf'" on the volume type you
created.
For examp
Hi all,
i trying to install openstack with puppet. i saw two repositories are
active related to puppet-openstack. i need some advice to go on with which
repository.
1. https://github.com/stackforge/puppet-openstack-cloud
2. https://github.com/puppetlabs/puppetlabs-openstack
i just confused whic
I'm looking at Nova unit tests, there are at least 3 issues.
The first one is assert_has_calls *used* to work with a single value
m.assert_has_calls(foo)
The documentation says m.assert_has_calls([foo]) is what you should use,
but the other form used to work. That appears to be tightened up.
It
Hi Mike,
Unfortunately, we don't get a lot of stats [1] because we don't run it
often. I've added 'check experimental' comment to latest
python-cinderclient review request to get more stats.
Review request to make this voting: https://review.openstack.org/#/c/200522/
[1]
http://graphite.openstac
Hi,
Potential bug, but still investigating:
- configured a driver on cinder (besides lvm) - all ok
[service1]
volume_driver = cinder.volume.drivers.openvstorage.OVSVolumeDriver
volume_backend_name = service1
vpool_name = service1
- removed it, restarted services - all ok (cinder service-list shows
Sean Dague wrote on 07/10/2015 12:32:00 PM:
> From: Sean Dague
> To: openstack-dev@lists.openstack.org
> Date: 07/10/2015 12:32 PM
> Subject: Re: [openstack-dev] [nova] Switching the bug status of ~200
> bugs at once; Problem?
>
> On 07/10/2015 04:09 AM, Markus Zoeller wrote:
> > I'd like to s
On 07/10/2015 09:34 AM, Markus Zoeller wrote:
> Sean Dague wrote on 07/10/2015 12:32:00 PM:
>
>> From: Sean Dague
>> To: openstack-dev@lists.openstack.org
>> Date: 07/10/2015 12:32 PM
>> Subject: Re: [openstack-dev] [nova] Switching the bug status of ~200
>> bugs at once; Problem?
>>
>> On 07/1
Markus Zoeller wrote:
> The bugs I'm referring to are *not* set to "In Progress" but have an
> assignee. I think this is an inconsistency which I try to resolve.
> I can treat them like "In Progress" bugs and remove the assignee
> if there is no activity in the last 60 days. Is this what you say?
On 07/10/2015 09:05 AM, cool dharma06 wrote:
> Hi all,
>
> i trying to install openstack with puppet. i saw two repositories are
> active related to puppet-openstack. i need some advice to go on with
> which repository.
>
> 1. https://github.com/stackforge/puppet-openstack-cloud
I personally k
On Fri, Jul 10, 2015 at 4:28 PM, Ivan Kolodyazhny wrote:
> Review request to make this voting
I'm sorry for typo. Of course, it's a review request to make this job
non-voting in check queue.
Regards,
Ivan Kolodyazhny
__
Op
Alex, could you enable the comments for all on your document?
Thanks!
Simon
On Thu, Jul 9, 2015 at 11:07 AM, Bogdan Dobrelya
wrote:
> > Hello everyone,
> >
> > I took some time this morning to write out a document[0] that outlines
> > one possible ways for us to manage our upstream modules in a
Done. Sorry about that.
-Alex
On Fri, Jul 10, 2015 at 9:22 AM, Simon Pasquier
wrote:
> Alex, could you enable the comments for all on your document?
> Thanks!
> Simon
>
> On Thu, Jul 9, 2015 at 11:07 AM, Bogdan Dobrelya
> wrote:
>
>> > Hello everyone,
>> >
>> > I took some time this morning to
Please find the response inline.
>
> Hi Glance experts,
>
> I'd like to send this mail again, hope I can get help and suggest from
> glance experts. The question is from a bug
> https://bugs.launchpad.net/glance/+bug/1462315,
>
> If an image-member is deleted, then create it again with the same
> p
hi,
trying to add a little of context to the request of daniel :)
we are playing with nova-docker, and we realized that
1) it's unclear (or not supported) passing enviroment variable through
userdata. probably the current version of IBM Cloud Manager with OpenStack
V4.3 indeed does implement a m
Hi,
If I understand correctly, you want to be able to install modified Murano
from your own repository. There is a devstack integration script in Murano
repository which does this. Here are lines where you can point to specific
repository for Murano installation in devstack:
https://github.com/ope
Okay Vladimir, thanks for confirmation!
So then you happy to stick my sketch proposal (of course needs re-wording)
into documentation?
Dani
On Fri, Jul 10, 2015 at 11:31 AM, Vladimir Kuklin
wrote:
> Daniel
>
> Yes, if you want to do some administrative stuff you need to have access
> to manage
How about using domain-based role assignments in keystone and requiring
domain-level authorization in policy, and then only returning data about
the collection of tenants that belong to the authorized domain? That way
you don't have an API that violates multi-tenant isolation, consumable only
by cl
Hi Alex,
Thank you for the great summary.
I have a concern about item #8. Can we add an option to Murano to use
previous storage engine rather then Glance v3? We need to make sure that v3
API in Glance is set by default before we do a hard dependency on it in
Murano.
Thanks
Gosha
On Fri, Jul 10
I can't understand how the impact on performance, image-members still have
an idx. Is there any other concern on the patch ? How to get result from
"rally gate job" ?
Can you give me suggestion on how to move forward ? Thanks .
Best regards,
LongQuan
From: Nikhil Komawar
To: "Ope
> From a 2 min look, this seems to wrap docker commands instead of using
> the new plugin
The plugin is here:
https://github.com/shettyg/ovn-docker/blob/master/ovn-docker-overlay-driver
>
> I would very much welcome to join efforts so that we define a vendor neutral,
> Neutron based generic conta
Hello Emmanuel,
There is no strong reason to keep it disabled. Thanks for pointing this
out.
I agree that it is better to have enabled.
So, I already did a change for it - https://review.openstack.org/#/c/200585/
Regards,
Valeriy Ponomaryov
On Wed, Jul 8, 2015 at 12:10 PM, Emmanuel Cazenave wr
On Fri, Jul 10, 2015 at 8:16 AM, Gurucharan Shetty wrote:
>> From a 2 min look, this seems to wrap docker commands instead of using
>> the new plugin
> The plugin is here:
> https://github.com/shettyg/ovn-docker/blob/master/ovn-docker-overlay-driver
>
>
>>
>> I would very much welcome to join effo
Dani
You are always welcome - I am adding fuel documentation team into the
thread.
On Fri, Jul 10, 2015 at 5:45 PM, Daniel Comnea
wrote:
> Okay Vladimir, thanks for confirmation!
>
> So then you happy to stick my sketch proposal (of course needs re-wording)
> into documentation?
>
> Dani
>
> On
Hi Chen,
As I remember, proxy users were added for security reasons. When one user
creates cluster in Sahara he should not get access to data of other users.
Thanks,
Andrew.
On Thu, Jul 9, 2015 at 11:12 PM, Li, Chen wrote:
> Hi Sahara guys,
>
>
>
>
>
> When sahara create a transient cluster,
Guys, we are next to moving fuel_agent directory into a separate
repository. Action flow is going to be as follows:
1) Create verify jobs on our CI https://review.fuel-infra.org/#/c/9186
(DONE)
2) Freeze fuel_agent directory in https://github.com/stackforge/fuel-web
(will announce in a separate ma
Response inline.
>
> I can't understand how the impact on performance, image-members still
> have an idx. Is there any other concern on the patch ? How to get
> result from "rally gate job" ?
>
> Can you give me suggestion on how to move forward ? Thanks .
>
Your change isn't. But including dele
We sometimes want the ability to write policy across tenants, e.g. VMs from
Coke and Pepsi must always be deployed on different hosts.
I didn't think there were any roles that could see everything without
all_tenants=true. If there are such roles, I'd be happy to remove the
all_tenants=true from
Le 10/07/2015 13:39, Jeremy Stanley a écrit :
On 2015-07-10 13:21:56 +0200 (+0200), Victor Stinner wrote:
I see "mock===1.0.1" in upper-constraints.txt, but the python27
check job of Swift was broken by the release of mock 1.1.
Can someone please explain me why Swift check job failed?
As far
Hi everyone,
latest Fuel Library CI update:
* Currently we have two tests based on Kilo ISO enabled in voting mode:
- master.fuel-library.pkgs.ubuntu.ha_neutron_vlan
- fuellib_review_pkgs_master_node
Both run Ubuntu deployment and pass on current master (see [1] and [2]).
Note that you need
Folks
I am writing this email to discuss very important topic which appeared to
be rather hot with several bugs associated with it.
For example these ones:
https://bugs.launchpad.net/fuel/+bug/1472018
https://bugs.launchpad.net/fuel/+bug/1468053
There were several fixes applied. One of them was
python's mock library had an update yesterday that exposed some issues with
unit tests that are using the mock assert calls. The radware tests were using
a method called assert_called_once, which actually is not a real assert method
off a mock. assert_called_once_with is, though. However, bef
On 2015-07-10 18:15:18 +0200 (+0200), Victor Stinner wrote:
> Is there a plan to use pinned versions on other gates to avoid similar
> issues in the future? (Decide when we upgrade a dependency)
Sachi has a design underway for applying constraints files to tox
envs as well: https://review.openstac
Ok, guys.
Looks like there are no any objections. At the moment I need to create
actual version of upstream repository which is going to be sucked in by
OpenStack Infra. Please, be informed that all patches changing
fuel-web/fuel_agent that will be merged after this moment will need to be
ported i
I've been working on assembling a QoS[1] POC since last day of the
coding sprint in Israel [2],
Ihar has reported to the list our plan to get into master [3].
I've been able to validate and integrate lots of the patches, and find
the gaps, while still
finishing the top-down assembly may requi
Vladimir,
You have identified the root cause of the problem:
> The key issue here is that our CI tests are using some code not from
packages of particular releases, but from other sources, e.g. pypi for
python.
Using frozen pypi, rubygems, nodejs and other language specific package
mirrors is a
Thierry Carrez wrote on 07/10/2015 03:43:06 PM:
> From: Thierry Carrez
> To: openstack-dev@lists.openstack.org
> Date: 07/10/2015 03:43 PM
> Subject: Re: [openstack-dev] [nova] Switching the bug status of ~200
> bugs at once; Problem?
>
> Markus Zoeller wrote:
> > The bugs I'm referring to are
On 7/7/2015 12:35 PM, John Garbutt wrote:
Hi,
Friday is: non-priority feature review bash day
https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule#Dates_overview
The idea is the whole nova community is invited to concentrate on
reviewing some some of the low priority blueprints that
Hi Vivek,
Hope things are well. With the Midccyle next week I am wondering if you made
any progress and/or how we can best help with the panels.
Thanks,
German
From: "Jain, Vivek" mailto:vivekj...@ebay.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openst
On 3/16/2015 8:48 AM, Attila Fazekas wrote:
Hi Mike,
The points was, there is no real need or real use case for archiving the db
as the nova-mange does.
What is the exact use case ? Auditing ? Accounting ?
* Keystone allows permanent delete, if you need to do auditing probably
the user ac
Hi all,
Min Pae[1] and I just did a HP + Y! brownbag about taskflow and since I
don't want to make anyone feel like they needed to be in the *exclusive*
set of folks that were allowed to be involved in that I wanted to share
the slide-set from that so that others can look at it or view it on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OK, we got 1.1.1 released today, and now gate is broken in some other wa
y:
"ImportError: No module named funcsigs"
Apparently there is a missing dependency, or it fails to apply, in the
package. I see jobs failing with it, as well as my local tox
In my opinion there is only one major actual bug left on Launch Instance. That
is the webroot bug [0] and this actually affects all of the angular work, not
just Launch Instance. There was a working fix for it ready earlier this week,
but then additional considerations for the approach on it w
On 11 July 2015 at 10:14, Ihar Hrachyshka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> OK, we got 1.1.1 released today, and now gate is broken in some other wa
> y:
>
> "ImportError: No module named funcsigs"
>
> Apparently there is a missing dependency, or it fails to apply, in
On 11 July 2015 at 04:50, Jeremy Stanley wrote:
> On 2015-07-10 18:15:18 +0200 (+0200), Victor Stinner wrote:
>> Is there a plan to use pinned versions on other gates to avoid similar
>> issues in the future? (Decide when we upgrade a dependency)
>
> Sachi has a design underway for applying constr
Hi,
I have a Neutron plugin (actually a mechanism_driver under ML2) developed
for Alcatel-Lucent Omniswitches and is currently being used. But it is not
part of Neutron upstream, nor listed in the docs/wiki section. I tried to
make it part of Kilo release, but that was when the decomposition propo
Thanks Nikolay and Gosha.
As Gosha mentioned I'd like to be able to integrate my local changes to
Murano into my devstack installation.
I figured for UI changes I can probably make the changes directly to the
file and restart my apache2 service.
However, I am looking for an easy way to test back
There are a lot of failures on nova changes since yesterday and rechecks
today don't seem to be coming back (after rechecking several hours ago).
Known issues?
--
Thanks,
Matt Riedemann
__
OpenStack Development Mailing
We've had a number of bugs recently that can be tracked back to older
pbr and setuptools versions being used.
The reason this happens is that we have a policy that we *don't*
version the setup_requires pbr dependency.
However, I've been looking into this, and I've only been able to find
two bugs
On 12:30 Jul 10, hao wang wrote:
> Cinder now doesn't check the existing resource when user lower the quota.
> It's reasonable for admin can adjust the quota limit to lower level than
> current usage.
> But it also bring confusion that I have received to end user, they saw the
> current usage
> was
On 10 July 2015 at 01:59, Morgan Fainberg wrote:
> Or a database per python major version (or at least gracefully handle the
> incompatibility).
So that would partition the data, and the whole point of test
*repository* is that it builds a database across all your tests to
answer useful question
On 9 July 2015 at 18:34, Flavio Percoco wrote:
> On 08/07/15 22:52 +, Jeremy Stanley wrote:
>>
>> On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote:
>>>
>>> So - I'm looking to:
>>>
>>> A) have a discussion and identify any issues with moving testr out of
>>> the venvs. (Note: this do
1 - 100 of 109 matches
Mail list logo
