On Tue, 17 Apr 2018 16:58:22 +0800, Chen Ch Ji wrote:
For the question on AE documentation, it's open source in [1] and the
documentation for how to build and use is [2]
once our code is upstream, there are a set of documentation change which
will cover this image build process by
adding some l
On Mon, 16 Apr 2018 14:56:06 +0800, Chen Ch Ji wrote:
>>>The "iso file" will not be inside the guest, but rather passed to
the guest as a block device, right?
Cloud init expects to find a config drive with following requirements
[1], in order to make cloud init able to consume config drive , we
+openstack-operators (apologies that I forgot to add originally)
On Mon, 9 Apr 2018 10:09:12 -0700, Melanie Witt wrote:
Hey everyone,
Let's collect forum topic brainstorming ideas for the Forum sessions in
Vancouver in this etherpad [0]. Once we've brainstormed, we'll select
Howdy everyone,
The meetbot was restarted in the middle of our meeting, so the log and
minutes could not be collected (after the restart) and will not be found
at http://eavesdrop.openstack.org/meetings/nova/2018/.
Here's a link to the #openstack-meeting channel log for the meeting if
you ar
On Thu, 12 Apr 2018 09:31:45 +1000, Michael Still wrote:
The more I think about it, the more I dislike how the proposed driver
also "lies" about it using iso9660. That's definitely wrong:
if CONF.config_drive_format in ['iso9660']:
# cloud-init only support iso9660 and vfa
Hey everyone,
Let's collect forum topic brainstorming ideas for the Forum sessions in
Vancouver in this etherpad [0]. Once we've brainstormed, we'll select
and submit our topic proposals for consideration at the end of this
week. The deadline for submissions is Sunday April 15.
Thanks,
-mela
Howdy everyone,
We recently updated the tox pep8 and fast8 environments to default to
using python3 [0] because it has stricter checks and we wanted to make
sure we don't let pep8 errors get through the CI gate [1].
Because of this, you'll need the python3 and python3-dev packages in
your en
+openstack-operators
Operator feedback wanted: do you have users that pass rotation parameter
'0' to the createBackup API in order to delete backups? Do you have
users using the createBackup API in general?
On Fri, 30 Mar 2018 10:44:40 +0800, Alex Xu wrote:
There is spec proposal to fix a bug
On Tue, 03 Apr 2018 18:53:33 -0400, Doug Hellmann wrote:
Excerpts from melanie witt's message of 2018-04-03 15:30:07 -0700:
On Tue, 3 Apr 2018 15:26:17 -0700, Melanie Witt wrote:
On Wed, 4 Apr 2018 07:54:59 +1000, Michael Still wrote:
Thanks to jichenjc for fixing the pep8 failures
On Tue, 3 Apr 2018 15:26:17 -0700, Melanie Witt wrote:
On Wed, 4 Apr 2018 07:54:59 +1000, Michael Still wrote:
Thanks to jichenjc for fixing the pep8 failures I was seeing on master.
I'd decided they were specific to my local dev environment given no one
else was seeing them.
As I said i
On Wed, 4 Apr 2018 07:54:59 +1000, Michael Still wrote:
Thanks to jichenjc for fixing the pep8 failures I was seeing on master.
I'd decided they were specific to my local dev environment given no one
else was seeing them.
As I said in the patch that fixed the issue [1], I think its worth
expl
On Mon, 26 Mar 2018 19:00:06 -0700, Melanie Witt wrote:
Howdy everyone,
I'd like to propose that we add Eric Fried to the nova-core team.
Eric has been instrumental to the placement effort with his work on
nested resource providers and has been actively contributing to many
other are
On Thu, 29 Mar 2018 10:09:09 +, Gary Kotton wrote:
Here is an example where the CI has run on a recent patch - yesterday
-https://review.openstack.org/557256
Thanks. Just curious, how is the CI passing if the driver is currently
broken for detach_volume? I had thought maybe particular tes
On Thu, 29 Mar 2018 10:44:52 +0300, Radoslav Gerganov wrote:
On 28.03.2018 19:07, melanie witt wrote:
We were reviewing a bug fix for the vmware driver [0] today and we noticed it
appears that the VMware NSX CI is no longer running, not even on only the
nova/virt/vmwareapi/ tree.
From the
On Wed, 21 Mar 2018 21:48:40 -0700, Melanie Witt wrote:
On Tue, 20 Mar 2018 16:47:58 -0700, Melanie Witt wrote:
The past several cycles, we've had a spec review day in the cycle where
reviewers focus on specs and iterating quickly with spec authors for the
day. Spec freeze is April 19
Hi Stackers,
This is just an standalone announcement that review runways [0] are now
live and in active use. Details and instructions are documented on the
etherpad.
For approved blueprint code authors, please consult the etherpad
instructions and add your blueprint to the Queue when your co
On Wed, 28 Mar 2018 19:21:24 +0300, Andrey Kurilin wrote:
This is a nice goal which revises me the first my patch to OpenStack
community. It was a patch to Nova and it was related to removing mox :)
PS: https://review.openstack.org/#/c/59694/
PS2: it was abandoned due to several -2 :)
You w
Hello everyone,
We were reviewing a bug fix for the vmware driver [0] today and we
noticed it appears that the VMware NSX CI is no longer running, not even
on only the nova/virt/vmwareapi/ tree.
From the third-party CI dashboard, I see some claims of it running but
when I open the patches, I
Howdy everyone,
I'd like to propose that we add Eric Fried to the nova-core team.
Eric has been instrumental to the placement effort with his work on
nested resource providers and has been actively contributing to many
other areas of openstack [0] like project-config, gerritbot,
keystoneauth,
Hey everyone,
This cycle there is a community goal to remove the use of mox/mox3 for
testing [0]. In nova, we're tracking our work at this blueprint:
https://blueprints.launchpad.net/nova/+spec/mox-removal
If you propose patches contributing to this goal, please be sure to add
something li
On Mon, 26 Mar 2018 14:12:52 -0500, Matt Riedemann wrote:
On 3/26/2018 6:24 AM, ChangBo Guo wrote:
What's your use case for ListOpt, just make sure the value(a list) is
part of 'choices' ? Maybe we need another parameter to distinguish
It came up because of this change in nova:
https://rev
On Tue, 20 Mar 2018 16:44:57 -0700, Melanie Witt wrote:
As mentioned in the earlier "Rocky PTG summary - miscellaneous topics
from Friday" email, this cycle we're going to experiment with a
"runways" system for focusing review on approved blueprints in
time-boxes. The
On Thu, 22 Mar 2018 16:12:47 -0500, Matt Riedemann wrote:
On 3/22/2018 2:59 PM, melanie witt wrote:
And (MHO) I'm not sure we need help in reviewing more specs.
I wholly disagree here. If you're on the core team, or want to be on the
core team, you should be reviewing specs, because
On Thu, 22 Mar 2018 13:26:48 -0500, Eric Fried wrote:
I think the only concern around moving spec freeze out would be that I
thought the original purpose of the spec freeze was to set expectations
early about what was approved and not approved instead of having folks
potentially in the situatio
On Thu, 22 Mar 2018 15:40:20 +, John Garbutt wrote:
On 20 March 2018 at 23:44, melanie witt <mailto:melwi...@gmail.com>> wrote:
We were thinking of starting the runways process after the spec
review freeze (which is April 19) so that reviewers won't be split
betwee
On Thu, 22 Mar 2018 10:38:38 -0500, Matt Riedemann wrote:
On 3/20/2018 6:44 PM, melanie witt wrote:
We were thinking of starting the runways process after the spec review
freeze (which is April 19) so that reviewers won't be split between spec
reviews and reviews of work in runways.
I&#x
On Tue, 20 Mar 2018 16:47:58 -0700, Melanie Witt wrote:
The past several cycles, we've had a spec review day in the cycle where
reviewers focus on specs and iterating quickly with spec authors for the
day. Spec freeze is April 19 so I wanted to get some input from all of
you about what day
On Tue, 20 Mar 2018 19:12:58 -0500, Matt Riedemann wrote:
* XenAPI: support non file system based SR types - e.g. LVM, ISCSI
* Currently xenapi is only file system-based, cannot yet support
LVM, ISCSI that are supported by XenServer
* We agreed that a specless blueprint is fine f
Hi everybody,
The past several cycles, we've had a spec review day in the cycle where
reviewers focus on specs and iterating quickly with spec authors for the
day. Spec freeze is April 19 so I wanted to get some input from all of
you about what day would work best for a spec review day.
I wa
Hello Stackers,
As mentioned in the earlier "Rocky PTG summary - miscellaneous topics
from Friday" email, this cycle we're going to experiment with a
"runways" system for focusing review on approved blueprints in
time-boxes. The goal here is to use a bit more structure and process in
order to
Howdy all,
I've put together an etherpad [0] with summaries of the items from the
Friday miscellaneous session from the PTG at the Croke Park Hotel "game
room" across from the bar area. I didn't summarize all of the items, but
attempted to do so for most of them, namely the ones that had
disc
On Fri, 16 Mar 2018 19:24:01 +0200, Peter Penchev wrote:
On Fri, Mar 16, 2018 at 09:23:11AM -0700, melanie witt wrote:
On Fri, 16 Mar 2018 17:33:30 +0200, Peter Penchev wrote:
Would there be any major opposition to adding a StorPool shared
storage image backend, so that our customers are not
Hello everyone,
Here's the summary etherpad [0] for the nova/ironic session from the PTG
in the Croke Park Hotel breakfast area, also included as a plain text
export on this email. Please feel freed to edit or reply to this thread
to add/correct anything I've missed.
Cheers,
-melanie
[0] ht
On Fri, 16 Mar 2018 17:33:30 +0200, Peter Penchev wrote:
Would there be any major opposition to adding a StorPool shared
storage image backend, so that our customers are not limited to
volume-backed instances? Right now, creating a StorPool volume and
snapshot from a Glance image and then bootin
I realized I forgot to add the [cinder] tag to the subject line when I
sent this originally. Sorry about that.
Hello all,
Here’s the PTG summary etherpad [0] for the nova/cinder session from the
PTG, also included as a plain text export on this email.
Cheers,
-melanie
[0] https://etherpad.o
Hello Stackers,
I've put together an etherpad [0] for the summary of the nova/neutron
session from the PTG in the Croke Park Hotel breakfast area and included
it as a plain text export on this email. Please feel free to edit or
reply to this thread to add/correct anything I've missed.
Cheers
On Thu, 15 Mar 2018 19:53:16 +, Kendall Nelson wrote:
Jay's correct the Updates are happening. Project Updates are their own
thing separate from the standard submission. Anne Bertucio had sent an
email out to all PTLs (shortly before the election so it went to you and
not Melanie) saying
On Thu, 15 Mar 2018 09:54:59 +0800, Zhenyu Zheng wrote:
Thanks for the recap, got one question for the "block creation":
* An attempt to create an instance should be blocked if the project
has instances in a "down" cell (the instance_mappings table has a
"project_id" column) because
Hello all,
Here’s the PTG summary etherpad [0] for the nova/cinder session from the PTG,
also included as a plain text export on this email.
Cheers,
-melanie
[0] https://etherpad.openstack.org/p/nova-ptg-rocky-cinder-summary
*Nova/Cinder: Rocky PTG Summary
https://etherpad.openstack.org/p/nov
Hi everyone,
I’ve created a summary etherpad [0] for the nova cells session from the PTG and
included a plain text export of it on this email.
Thanks,
-melanie
[0] https://etherpad.openstack.org/p/nova-ptg-rocky-cells-summary
*Cells: Rocky PTG Summary
https://etherpad.openstack.org/p/nova-ptg
Howdy Stackers,
I’ve created a summary etherpad [0] of the Queens retrospective session from
the PTG and included a plain text export of it on this email.
Thank you to all who participated and please do add comments to the etherpad
where I might have missed a perspective or interpretation in my
Hi everyone,
Just wanted to send a fresh email that we’re having the nova/neutron and
nova/ironic cross-project sessions going on today at the Croke Park Hotel.
Nova/neutron is in-progress now at the breakfast area of the restaurant and
nova/ironic will start at 4:00 PM, probably also in the br
> On Mar 1, 2018, at 11:24, melanie witt wrote:
>
> Because it’s uncomfortably cold in Davin Suite, I’ve booked Hogan Suite (the
> lunch room) for us to use after lunch for the rest of today.
>
> So please be sure to go to Hogan Suite this afternoon for the Nova/Ironic a
On Mar 1, 2018, at 11:24, melanie witt wrote:
Because it’s uncomfortably cold in Davin Suite, I’ve booked Hogan Suite
(the lunch room) for us to use after lunch for the rest of today.
So please be sure to go to Hogan Suite this afternoon for the Nova/Ironic
and Nova/Neutron sessions.
Update
Hey everyone,
Because it’s uncomfortably cold in Davin Suite, I’ve booked Hogan Suite (the
lunch room) for us to use after lunch for the rest of today.
So please be sure to go to Hogan Suite this afternoon for the Nova/Ironic and
Nova/Neutron sessions.
Cheers,
-melanie
Hey everyone,
We have time scheduled on Thursday morning 11:10-11:20 AM for a team photo at
the PTG. For those in the Nova room (Davin Suite), we’ll walk together to the
registration area before 11:10 AM to meet before we’ll be escorted down to the
pitch (sports field) to take the photo. If you
Howdy everyone,
This is just a reminder that we have some time scheduled to chat with the
Cyborg team at 2pm this afternoon at the Cyborg room (Suite 665).
From our PTG etherpad agenda[1] :
"Cyborg (previously known as Nomad) is an OpenStack project that aims to
provide a general purpose manag
Greetings Stackers,
FYI we also have a retrospective etherpad [1] for Queens which we’ll cover at
the PTG on Wednesday at 9:00 - 10:00 AM.
Please add your thoughts to the etherpad on what you think went well in Queens
and what you think could use some improvement going forward into the Rocky
c
Howdy Stackers,
I’ve set up the review priorities etherpad [1] for us to use during the Rocky
cycle. It’s the same format we had back in Pike with the exception of a couple
of new sections I’ve added: "Non-priority approved blueprints” and "Co-authors
wanted”. The idea of the etherpad is to org
> On Feb 16, 2018, at 06:11, Balázs Gibizer wrote:
>
> Hi,
>
> On the weekly meeting melwitt suggested [1] to have people signed up for
> certain bug tags. I've already been trying to follow the bugs tagged with the
> 'notifications' tag so I sign up for this tag.
>
> Cheers,
> gibi
>
> [1]h
> On Jan 8, 2018, at 10:33, Matt Riedemann wrote:
>
> As the Queens release winds to a close, I've started thinking about topics
> for Rocky that can be discussed at the PTG.
>
> I've created an etherpad [1] for just throwing various topics in there,
> completely free-form at this point; just
> On Feb 12, 2018, at 16:06, Zhipeng Huang wrote:
>
> Let's settle on Tuesday afternoon session then, thanks a lot :)
Do we have a proposed time and place for the session already? I checked the
cyborg etherpad [1] and it looks like we’re thinking 2:00pm on Tuesday. Do we
need to reserve a room
> On Feb 12, 2018, at 16:26, melanie witt wrote:
>
> Hey Stackers,
>
> This is just a heads up that the github mirror of the nova-specs repo has
> been temporarily broken for the past few months and doesn’t have the
> specs/rocky/ directory in it. Fixing it is on the T
Hey Stackers,
This is just a heads up that the github mirror of the nova-specs repo has been
temporarily broken for the past few months and doesn’t have the specs/rocky/
directory in it. Fixing it is on the TODO list for the next scheduled
maintenance window, but until then, please git clone th
Hello Stackers,
I would like to announce my candidacy for Nova PTL in the Rocky cycle.
I have been a core reviewer on Nova since May 2015 and have been working with
OpenStack since mid 2012 (ancient times!) and you may know me on IRC as
melwitt. I have been both a user and a developer on OpenSt
> On Jan 29, 2018, at 16:45, Arun SAG wrote:
>
> If anyone is running into db race while running database in
> master-slave mode with async replication, The bug has been identified
> and getting fixed here
> https://bugs.launchpad.net/oslo.db/+bug/1746116
Thanks for your persistence in tracking
Hello Stackers,
This is a heads up to any of you using the AggregateCoreFilter,
AggregateRamFilter, and/or AggregateDiskFilter in the filter scheduler.
These filters have effectively allowed operators to set overcommit
ratios per aggregate rather than per compute node in <= Newton.
Beginning
On Fri, 05 Jan 2018 10:43:59 -0800, Clark Boylan wrote:
To expand a bit more on that what we are attempting to do is port the log
handling code in devstack-gate [0] to zuul v3 jobs living in tempest [1]. The
new job in tempest itself relies on the ansible process-test-results role
which can b
On Thu, 4 Jan 2018 08:46:38 -0600, Matt Riedemann wrote:
The main issue is for newer jobs like tempest-full, the logs are under
controller/logs/ and we lose the log analyze formatting for color, being
able to filter on log level, and being able to link directly to a line
in the logs.
I also n
On Fri, 15 Dec 2017 18:38:00 -0800, Arun Sag wrote:
Here are the sequence of actions happen in nova-network
1. allocate_for_instance calls -> allocate_fixed_ips
2. FixedIPs are successfully associated (we can see this in the log)
3. allocate_for_instance calls get_instance_nw_info, which in turn
On Fri, 29 Sep 2017 13:49:55 -0500, Matt Riedemann wrote:
For awhile now actually.
Someone was asking about when archive_deleted_rows would actually work,
and the answer is, it should since at least mitaka:
https://review.openstack.org/#/q/I77255c77780f0c2b99d59a9c20adecc85335bb18
And starti
On Wed, 20 Sep 2017 13:47:18 -0500, Matt Riedemann wrote:
Presumably there was a good reason why the instance failed to build on a
host originally, but that could be for any number of reasons: resource
claim failed during a race, configuration issues, etc. Since we don't
really know what origin
On Thu, 14 Sep 2017 11:15:26 -0600, Ed Leafe wrote:
On Sep 14, 2017, at 10:30 AM, melanie witt wrote:
I was thinking, if it's possible to assign more than one resource class to an Ironic
node, maybe you could get similar behavior to the old non-exact filters. So if you have
an od
On Thu, 7 Sep 2017 14:57:24 -0500, Matt Riedemann wrote:
Some more background information is in the ironic spec here:
https://review.openstack.org/#/c/500429/
Also, be aware of these release notes for Pike related to baremetal
scheduling:
http://docs-draft.openstack.org/77/501477/1/check/gat
On Tue, 22 Aug 2017 20:18:18 -0500, Matt Riedemann wrote:
So to the existing core team members, please respond with a yay/nay and
after about a week or so we should have a decision (knowing a few cores
are on vacation right now).
+1
___
On Tue, 18 Jul 2017 09:22:31 +0900, Ghanshyam Mann wrote:
Yes, this is same case when we do fetch patch set using git checkout,
i do not think its something to do with gite review -d.
Doing that shouldn't change the author, at least in my experience. I
constantly 'git fetch' or 'git review -d
On Thu, 8 Jun 2017 08:58:20 -0500, Matt Riedemann wrote:
Nova stores the output of the Cinder os-initialize_connection info API
in the Nova block_device_mappings table, and uses that later for making
volume connections.
This data can get out of whack or need to be refreshed, like if your
ceph
Hey Folks,
I wanted to give everyone a heads up that we have found and fixed a bug
[1] on master where the number of database connections had increased so
much that we were starting to hit a "OperationalError
(pymysql.err.OperationalError) (1040, u'Too many connections')" in the
gate on some
On Wed, 15 Feb 2017 16:34:57 -0500, Corey Bryant wrote:
I think I figured it out. I'll submit a patch in a little bit.
Great, post a link to the patch after you upload it and we'll review.
Also note earlier I forgot to mention --name should also be optional for
the command (everything except
On Wed, 15 Feb 2017 16:12:14 -0500, Corey Bryant wrote:
This works but you have to specify all of the args (--cell_uuid, --name,
--transport-url and --database_connection). Otherwise you'll hit
this: http://paste.ubuntu.com/24003055/
Corey,
Thanks for pointing that out.
It looks like the com
On Wed, 1 Feb 2017 08:06:41 -0500, Davanum Srinivas wrote:
Three more from this morning, at least the first one looks new:
http://logs.openstack.org/04/426604/3/gate/gate-tempest-dsvm-neutron-full-ubuntu-xenial/708771d/logs/testr_results.html.gz
tempest.api.compute.images.test_list_image_filters
Hi all,
Apologies for the late notice, but there won't be a cells meeting this
afternoon being that everyone is busy scrambling for the feature freeze
deadline this week. Let's catch up after FF.
Thanks,
-melanie
__
Open
On Fri, 13 Jan 2017 14:04:27 -0700, Alex Schultz wrote:
Just from the puppet standpoint, it's much easier to create the cell
and populate it after the fact and run some command to sync stuff
after the nodes have been added. This also would be easier to consume
for scale up/scale down actions. I
On Fri, 6 Jan 2017 12:15:34 -0500, William M Edmonds wrote:
Why would someone need to change the defaults via REST API calls? I
agree that we should plan for that now if we think that will eventually
be needed, but I'm not seeing why it would be needed.
The REST API already allows people to cha
On Tue, 6 Dec 2016 16:04:14 -0500, Jay Pipes wrote:
We're discussing only doing:
GET /resource_providers?
Once we start doing claims in the scheduler, we'll have the ability to do:
POST /allocations
{
}
Thanks. FWIW, I'm not against simple non-JSON query params.
The last time we di
On Tue, 6 Dec 2016 15:42:18 -0500, Jay Pipes wrote:
On 12/06/2016 03:28 PM, Ed Leafe wrote:
On Dec 6, 2016, at 2:16 PM, Jay Pipes wrote:
I would prefer:
GET /resource_providers?resources=DISK_GB:40,VCPU:2,MEMORY_MB:2048
to "group" the resources parameter together. When we add in trait
looku
On Tue, 22 Nov 2016 19:42:32 -0500, Emilien Macchi wrote:
On Tue, Nov 22, 2016 at 6:36 PM, melanie witt wrote:
In the Nova configuration, the 'my_ip' setting is the IP address the host
uses to connect to the management network [1]. This is the IP Nova uses to
set up iptables rul
Hi all,
In the Nova configuration, the 'my_ip' setting is the IP address the
host uses to connect to the management network [1]. This is the IP Nova
uses to set up iptables rules for the metadata service listening on port
8775.
By default, 'my_ip' is set to the result of
oslo_utils.netutils
On Tue, 22 Nov 2016 11:39:54 -0500, Andrew Laski wrote:
It has been a true pleasure working with you all these past few years
and I'm thankful to have had the opportunity. As I've told people many
times when they ask me what it's like to work on an open source project
like this: working on propri
On Tue, 15 Nov 2016 18:10:40 -0600, Chris Friesen wrote:
I'm in favor of your change, since the existing behaviour doesn't make
sense.
But at some point I guess consistency trumps correctness, and if a new
microversion is necessary to mark the new behaviour then a spec is
required, and at that p
On Mon, 14 Nov 2016 17:34:28 -0600, Matt Riedemann wrote:
Why do we want to return a list of uuids for servers created? I thought
that's why we have the 'return_reservation_id' request parameter for the
server multiple-create scenario so that you can get a single reservation
ID back and all of th
On Mon, 14 Nov 2016 22:48:01 +0100, Sławek Kapłoński wrote:
Are You sure that but
https://bugs.launchpad.net/nova/+bug/1458122 is still valid? I tried to
spawn instances with min=3 and max=11 when quota was set to 10 and I had
spawned 10 instances properly (no any in error state). I also checked
On Tue, 8 Nov 2016 14:25:08 -0600, Matt Riedemann wrote:
While talking about that in the session, there was some brainstorming on
doing limit checks differently in the API. Basically, do away with
reservations, do a quick DB query to check quota before an operation
begins, and if it's OK go forwa
I am working on a POC with this approach and will test all possible
scenarios (boot, resize, reboot, compute service stop/start,
shelved-unshelved etc).
Please let me know your opinion about the same or you have any other
solution in mind.
Hi Abhishek,
FWIW, I'm working on a patch to prop
On Wed, 18 May 2016 14:30:00 -0500, Matt Riedemann wrote:
While convenient as a workaround, I'm not in favor of the idea of adding
something to the REST API so a user can force refresh the connection
info - this is a bug and leaks information out of the API about how the
cloud is configured. If y
On Tue, 19 Apr 2016 10:02:46 -0400, Sean Dague wrote:
Right, I think in the Havana timeframe, things were very different. Part
of the rationale for full parity was that applications would be written
against nova-network, and smoothly transition to neutron. But with over
90% neutron, assuming some
On Tue, 19 Apr 2016 19:31:04 +0800, Kenny Ji-work wrote:
I have installed openstack mitaka, when I execute any nova's commands
with the result displayed below:
[root@devstack scripts]# nova list
*ERROR (AttributeError): 'unicode' object has no attribute 'get'*
I installed openstack as
the http:
On Thu, 14 Apr 2016 13:17:48 -0500, Dean Troyer wrote:
My only real concern is you've implied a structure that will potentially
have many combinations of configurations and those will bitrot. How
different are x86 and s390 arch in local.conf? (I've never seen an s390
local.conf!) I do know ther
On Wed, 13 Apr 2016 12:53:12 -0500, Matt Riedemann wrote:
I'd like to propose that we make Andrey Kurilin core on python-novaclient.
He's been doing a lot of the maintenance the last several months and a
lot of times is the first to jump on any major issue, does a lot of the
microversion work, a
On Mar 23, 2016, at 16:56, melanie witt wrote:
> I may have found a workaround for the scroll jumping after reading through
> the upstream issue comments [1]: use the "Slow" setting in the preferences
> for Render. Click the gear icon in the upper right corner of the diff vi
On Mar 18, 2016, at 9:50, Andrew Laski wrote:
> I've adapted to the new interface and really like some of the new
> capabilities it provides, but having the page jump around while I'm
> commenting has been a huge annoyance.
I may have found a workaround for the scroll jumping after reading thr
On Mar 17, 2016, at 9:41, Markus Zoeller wrote:
> What are the various reasons which block you to work on bug reports?
The number one reason for me is lack of information. The main things I want to
know are, what version, what commands/API calls did you do, what was the
behavior, what behavior
On Mar 15, 2016, at 10:59, Tim Bell wrote:
> The risk I see is that we are missing input to the development process in
> view of the complexity of submitting those requirements. Clearly, setting the
> bar too low means that there is no clear requirement statement etc. However,
> I think the co
On Feb 25, 2016, at 8:35, Michał Dulko wrote:
> We've faced similar issues in Cinder and as solution we've moved
> filtering to Python code. Like in for example [1] or [2]. But no, we
> haven't had UNIQUE constraint on the DB column in these cases, only on IDs.
This is an interesting option.
I
On Feb 12, 2016, at 14:49, Jay Pipes wrote:
> This would be my preference as well, even though it's technically a
> backwards-incompatible API change.
>
> The idea behind get-me-a-network was specifically to remove the current
> required complexity of the nova boot command with regards to netw
On Jan 25, 2016, at 17:57, melanie witt wrote:
> Thanks!! That's indeed the same problem and removing the '$' from the
> exclude_regex worked for me. (ostestr --blacklist_file tests-py3.txt --regex
> "nova.tests.unit.network" ran all non-blacklisted netw
On Jan 22, 2016, at 19:14, Matthew Treinish wrote:
> Although, now that I look at the list it definitely looks like this one,
> which I had forgotten about:
>
> https://bugs.launchpad.net/os-testr/+bug/1506215
>
> It sounds like that bug proposes a direction so if you could patch os-testr
> to
Hi everyone,
I noticed because of the way we run the py34 tests in tox.ini, I'm not able to
specify a filter regex the way I normally do as a positional arg, for example:
'tox -epy34 nova.tests.unit.network' doesn't filter and it runs everything.
('tox -epy27 nova.tests.unit.network' will only
On Jan 6, 2016, at 11:41, Andrew Laski wrote:
> As explained in
> http://lists.openstack.org/pipermail/openstack-dev/2016-January/083216.html a
> recurring calendar event based on alternating weeks will now be incorrect. I
> had to fix my calendar and I expect others will want to do the same.
On Dec 10, 2015, at 15:57, Devananda van der Veen
wrote:
> So, at this point, I think we need to accept that the scheduling of
> virtualized and bare metal workloads are two different problem domains that
> are equally complex.
>
> Either, we:
> * build a separate scheduler process in Ironic,
101 - 200 of 263 matches
Mail list logo
