Hi nova-api team,
I'd like to get a feedback about the way to bump a microversion.
Short version:
We found a validation bug on Nova v2.1 API.
To fix the bug, do we need to bump a new microversion?
Long version:
As LP bug report[1], nova v2.0 API allows a list of server-IDs on
scheduler_hint
As discussed last week we will cancel this and next week's meeting.
Happy Holidays everyone.
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
__
OpenStack Development Mailing List (not for us
Adrian,
flannel_network_cidr and flannel_network_subnetlen are two parameters
needed for flannel. flannel_network_cidr is the network range for flannel
overlay network. flannel_network is the size of subnet assigned to each
minion. When flannel starts, it needs the two parameters. Flannel will
all
Hi,
Most of api sub-team members aren't there. So we will cancel nova api
meetings in next two weeks:
https://wiki.openstack.org/wiki/Meetings/NovaAPI
Hope everyone happy and enjoy the holidays!
Thanks
Alex
__
OpenStack Deve
Hey all,
So I just caught up on this thread and the corresponding scrollback in IRC.
First of all, sorry if this came as a surprise to anybody. As Andreas
pointed out this was highlighted in a number of docs email to this list,
but I understand why they might have been overlooked.
The resource u
Hi all,
Sorry to send this last minute; but as informally decided and having had
some momentum on Artifacts with a few decision items to be taken, it
would be nice to have a virtual sync before the holiday season begins.
I have created a poll for the same. Please vote on the doodle as soon as
pos
We also need to consider a lot for Magnum UI part as the UI part is highly
depend on those APIs. Thanks.
On Thu, Dec 17, 2015 at 9:21 AM, Adrian Otto
wrote:
> Yes, this topic is a good one for a spec. What I am planning to do here is
> copy the content from the BP to an etherpad in spec format,
Thanks Alex. This is a good idea. Please propose a review for the change
of schedule so that we can be assured the tests pass and decision would
be accepted.
On 12/18/15 9:20 AM, Alexander Tivelkov wrote:
> Hi folks,
>
> The current timeslot of our weekly IRC meeting for artifact subteam
> (14:00
Hi Tempest folks,
Thank you for your reviews on this patch:
https://review.openstack.org/#/c/195443/.
However, the current devstack configuration in gate jobs only supports one
cinder back-end, but this test is supposed to test the volume retype and
migration between two different cinder back-e
https://review.openstack.org/#/c/245042
First patch https://review.openstack.org/#/c/221648
I proposed this spec, because the function is really needed, many customers of
our company complained that they have to write/manage many templates to meet
their business(the templates are similar, can th
On Sunday, December 20, 2015, Davanum Srinivas wrote:
> Nova folks,
>
> We have this review in oslo.utils:
> https://review.openstack.org/#/c/252898/
>
> There were failed effort in the past to cleanup in Nova:
> https://review.openstack.org/#/c/164753/
> https://review.openstack.org/#/c/197601/
Hi all,
The gate-novaclient-dsvm-functional tests are failing with:
--
.tox/functional/bin/python: can't open file
'/usr/local/jenkins/slave_scripts/subunit2html.py': [Errno 2] No such file or
directory
-- [1]
This can be fixed with [2] Y'all can consider it my christmas present if we can
r
Hi all (Actually I'mm really looking a Dan, Sean and Matt)
We have a 2 changes in stable/liberty
https://review.openstack.org/#/c/248505 Add -constraints sections for CI jobs ;
and
https://review.openstack.org/#/c/248877 Remove the TestRemoteObject class
If you grab 248505 and look at the git D
Thanks Adrian and Tim, I saw that @Vilobh already uploaded a patch
https://review.openstack.org/#/c/259201/ here, perhaps we can first have a
spec and discuss there. ;-)
On Mon, Dec 21, 2015 at 2:44 AM, Tim Bell wrote:
> Given the lower level quotas in Heat, Neutron, Nova etc., the error
> feedb
I believe the code that needs fixing is in cinder backup itself, rather
than (or as well as) the client, since the client will only initiate the
operation, it will not be around for later when the token expires.
Cinder backup is also potentially a place where keystone trusts can be
fruitfully empl
Hey Paul,
At the Tokyo summit we discussed a general way to make it so that user
tokens were only expiration tested once. When the token hits nova for
example we can say it was validated, then when nova talks to glance it
sends both the user token (or enough data to represent the user token) and
a
On 17 December 2015 at 02:59, Pavlo Shchelokovskyy <
pshchelokovs...@mirantis.com> wrote:
> Hi all,
>
> I'd like to start discussion on how Ironic is using Neutron when Keystone
> is involved.
>
> Recently the patch [0] was merged in Ironic to fix a bug when the token
> with which to create the ne
Looking at the dstat logs for a recent fail [0], it did help in that
more memory is available. You now have over 1GB available but still less
than 2GB. I would try using less memory. Can you use a 1GB flavor
instead of a 2GB flavor?
[0]
http://logs.openstack.org/58/251158/4/check/gate-functional-d
Hi Clark,
Thanks for the fix. Unfortunately, it doesn't seem to help. The error still
occurred [1] after you increased the memory restriction, and as before, most of
them occurred in OVH host. Any further suggestion?
[1] http://status.openstack.org/elastic-recheck/#1521237
Best regards,
Hongbi
Greetings,
I've proposed a series of patches[1] to rename tox -eansible-functional to
tox -efunctional. While the change is trival, it is meant to workaround an
interpreter issue with tox[2]. Additionally, the change brings our tox.ini
inline with other OpenStack projects launching functional test
On Sun, Dec 20, 2015, at 07:43 AM, zhu4236926 wrote:
> Hi guys,
> I'm using cinder-clinet to backup a volume and query the status of
> the backup-volume in a loop per 3 seconds. I got the token from
> keystone when I begin to backup the volume,assuming that the token is
> expired in
> -Original Message-
> From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com]
> Sent: Tuesday, December 08, 2015 11:17 AM
>
> Hi Ifat,
>
> In short, 'event' is generated in OpenStack, 'alarm' is defined by a
> user. 'event' is a container of data passed from other OpenStack
> services through Open
Given the lower level quotas in Heat, Neutron, Nova etc., the error feedback
is very important. A Magnum "cannot create" message requires a lot of
debugging whereas a "Floating IP quota exceeded" gives a clear root cause.
Whether we quota Magnum resources or not, some error scenarios and
approp
This sounds like a source-of-truth concern. From my perspective the solution is
not to create redundant quotas. Simply quota the Magnum resources. Lower level
limits *could* be queried by magnum prior to acting to CRUD the lower level
resources. In the case we could check the maximum allowed num
Nova folks,
We have this review in oslo.utils:
https://review.openstack.org/#/c/252898/
There were failed effort in the past to cleanup in Nova:
https://review.openstack.org/#/c/164753/
https://review.openstack.org/#/c/197601/
What do we do? Suggestions please.
Thanks,
Dims
--
Davanum Sriniva
Hi devs,
I found a problem which may cause infinite update of instance's attributes in
gnocchi.
Let's see the resource definition of instance.
- resource_type: instance
metrics:
- 'instance'
- 'memory'
- 'memory.usage'
- 'memory.resident'
- 'vcpus'
Hi guys,
I'm using cinder-clinet to backup a volume and query the status of the
backup-volume in a loop per 3 seconds. I got the token from keystone when I
begin to backup the volume,assuming that the token is expired in 2 minutes, but
the backup need 5 minutes to finish, so after 3 minutes
Hello All,
We will have an IRC meeting tomorrow (Monday, 12/21) at 0900 UTC
in #openstack-meeting-4
Please review the expected meeting agenda here:
https://wiki.openstack.org/wiki/Meetings/Dragonflow
You can view last meeting action items and logs here:
http://eavesdrop.openstack.org/meetings/dr
I also have the same concern with Lee, as Magnum depend on HEAT and HEAT
need call nova, cinder, neutron to create the Bay resources. But both Nova
and Cinder has its own quota policy, if we define quota again in Magnum,
then how to handle the conflict? Another point is that limiting the Bay by
qu
Hi All,
I request you all to please go though IPAM changes and related changes in
network driver. Its been a very long time since changes are in review
state.
https://review.openstack.org/#/q/owner:+vikaschoudhary16+status:open
Thanks & Regards
Vikas Choudhary
On Sun, Dec 13, 2015 at 5:33 PM,
Hi All,
Thanks alot for your valuable feedback Jesse.
Point 1 :
I have made the appropriate Designate entry in the file here :
/playbooks/defaults/repo_packages/openstack_services.yml and uploaded it for
review here :
https://github.com/sharmaswati6/designate_files/blob/master/playbooks/defa
31 matches
Mail list logo
