On 08/28/2015 09:34 AM, Valeriy Ponomaryov wrote:
Dmitriy,
New tests, that cover new functionality already know which API version
they require. So, even in testing, it is not needed. All other existing
tests do not require API update.
Yeah, but you can't be sure that your change does not
Hi All,
The resource reservation topic pops up time to time on different forums to
cover use cases in terms of both IT and NFV. The Blazar project was intended to
address this need, but according to my knowledge due to earlier integration and
other difficulties the work has been stopped.
My
Let's get these details into the QuickStart doc so anyone else hitting this can
be clued in.
--
Adrian
On Aug 27, 2015, at 9:38 PM, Vikas Choudhary
choudharyvika...@gmail.commailto:choudharyvika...@gmail.com wrote:
Hi Stanislaw,
I also faced similar issue.Reason might be that from inside
On 08/27/2015 09:38 PM, Ben Swartzlander wrote:
Manila recently implemented microversions, copying the implementation
from Nova. I really like the feature! However I noticed that it's legal
for clients to transmit latest instead of a real version number.
THIS IS A TERRIBLE IDEA!
I recommend
-Original Message-
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
Sent: 28 August 2015 02:29
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] --detailed-description for OpenStack items
On 8/27/2015 12:23 PM, Tim Bell wrote:
Some project such as
On 27/08/15 15:32 -0400, Nikhil Komawar wrote:
As a part of our continued effort to make the v2 primary API and get
people to consume it without confusion we are planning to move ahead
with the client release (the release would set the default version of
API to 2). There haven't been any
Hi all,
I have two points.
a. For the problem in this thread, my suggestion is to introduce new
concepts to replace the existing firewall and SG.
Perhaps you have found the overlap between firewall and SG. It's trouble
for user to select.
So the new concepts are edge-firewall for N/S traffic and
Folks,
I would like to know whether info in http://paste.openstack.org will be removed
or not.
If it will be removed, I also would like to know a condition.
Thanks in advance,
Hisashi Osanai
__
OpenStack Development
Thanks everyone for the feedback!
There weren't any comments about options (1) and (4), I'm interpreting
it as a consensus that we're not doing a future branch, and as a sign
that nobody wants to even think about CI for external forks (which I'm
sure will come back to haunt us, so don't count on
Angus!
it's Awesome! Thank you for the investigation.
I had a talk with guys from Sahara team and we decided to start testing
convergence with Sahara after L release.
I suppose, that Murano can also join to this process.
Also AFAIK Sahara team plan to create functional tests with Heat-engine.
On Thu, 27 Aug 2015, Chris Dent wrote:
On Wed, 26 Aug 2015, Matthew Treinish wrote:
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/functions.sh#n571
Is 'process_testr_artifacts' going to already be in scope for the
hook script or will it be necessary to source functions.sh
Dmitriy,
New tests, that cover new functionality already know which API version they
require. So, even in testing, it is not needed. All other existing tests do
not require API update.
So, I raise hand for restricting latest.
On Fri, Aug 28, 2015 at 10:20 AM, Dmitry Tantsur dtant...@redhat.com
From: Ben Swartzlander [mailto:b...@swartzlander.org]
Sent: Thursday, August 27, 2015 8:11 PM
To: OpenStack Development Mailing List (not for usage questions)
On 08/27/2015 10:43 AM, Ivan Kolodyazhny wrote:
Hi,
Looks like we need to be able to set AZ per backend. What do
On Fri, Aug 28, 2015 at 6:35 PM Sergey Lukjanov slukja...@mirantis.com
wrote:
Hi,
great, it seems like migration to convergence could happen soon.
How many times you were running each test case? Does time changing with
number of iterations? Are you planning to test parallel stacks creation?
On Tue, Aug 25, 2015 at 09:14:33AM -0500, Matt Riedemann wrote:
Support to change the admin password on an instance via the libvirt driver
landed in liberty [1] but the hypervisor support matrix wasn't updated [2].
There is a version restriction in the driver that it won't work unless
you're
Hi,
great, it seems like migration to convergence could happen soon.
How many times you were running each test case? Does time changing with
number of iterations? Are you planning to test parallel stacks creation?
Thanks.
On Fri, Aug 28, 2015 at 10:17 AM, Sergey Kraynev skray...@mirantis.com
Ruby Loo wrote:
Our first semver release, 4.0.0, was tagged this week but a few more
things need to be ironed out still (hopefully there will be an
announcement about that in the near future).
What I wanted to mention is that according to the new process, there
will be a final release of
We're at a 18hr backup in the gate, which is really unusual given the
amount of decoupling. Even under our current load that means we're
seeing huge failure rates causing resets.
It appears one of the major culprits is the python34 tests in neutron,
which were over a 40% failure rate recently -
Ok, I belive we can take it in mind as possible resolution. The problem is
that it will take it us too long, so we can discuss it while we will plan
Mitaka development.
However it's not a decision of the problem with service broker API for now.
Nikolay Starodubtsev
Software Engineer
Mirantis
My vote is for #1. If I remember the problem right it's the best solution.
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
2015-08-20 13:16 GMT+03:00 Kirill Zaitsev kzait...@mirantis.com:
On our latest irc meeting I raised a concern about public package
Hi Ildikó,
The problem of blazar project was that active contributors moved to
different OpenStack projects or leave the community.
I want to be in the 'ressurection' process. Also, some other guys might be
interested. I remember that I saw some email in dev-list.
Nikolay Starodubtsev
Software
On 27/08/15 18:35 +, Tim Bell wrote:
That could be done but we'd need to establish an agreed name so that Horizon or the CLIs,
for example, could filter based on description. Give me all VMs with Ansys in the
description.
If we use properties, a consistent approach would be needed so the
Hi,
If I recall correctly your Horizon-based solution won't be possible, because of
how Nova's code works internally - it just passes Nova's AZ to Cinder API,
without allowing to overwrite it.
We're discussing this particular issue in another ML thread
Hi , all
When using neutron (especially with DVR), I find it difficult to debug
problems with lots of ovs rules, complicated iptables rules, network
namespaces, routing tables, ...
So I create https://github.com/yeasy/easyOVS
https://github.com/yeasy/easyOVSeasyOVS
Except your failure domain includes the cinder volume service, independent
of the resiliency of you backend, so if they're all on one node then you
don't really have availability zones.
I have historically strongly espoused the same view as Ben, though there
are lots of people who want fake
On 28/08/15 13:39, Kevin Benton wrote:
For the py34 failures, they seem to have started around the same time
as a change was merged that adjusted the way they were ran so I
proposed a revert for that patch
here: https://review.openstack.org/218244
Which leads on to
From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: Friday, August 28, 2015 2:31 PM
Except your failure domain includes the cinder volume service, independent
of the resiliency of you backend, so if they're all on one node then you don't
really have availability zones.
I have
On 08/28/2015 09:22 AM, Assaf Muller wrote:
On Fri, Aug 28, 2015 at 9:12 AM, Neil Jerram neil.jer...@metaswitch.com
mailto:neil.jer...@metaswitch.com wrote:
On 28/08/15 13:39, Kevin Benton wrote:
For the py34 failures, they seem to have started around the same time
as a
I am working with the OS::Nova::Server resource and looking at the tests
[1], it should be possible to just define 'swap_size' and get a swap
space created on the instance:
NovaCompute:
type: OS::Nova::Server
properties:
image:
{get_param: Image}
...
Has anyone written anything up about expectations for how Big Tent or
Neutron Stadium projects are expected to be
installed/distributed/packaged?
In particular, I'm wondering how we're supposed to handle changes to
Neutron components. For the networking-sfc project we need to make
additions
On 08/28/2015 08:34 AM, Kevin Benton wrote:
One of the patches that fixes one of the functional failures that has
been hitting is here: https://review.openstack.org/#/c/217927/
However, it failed in the DVR job on the 'test_router_rescheduling'
test.[1] This failure is because the logic to
I don't know if this is really a big problem. IMO, even with microversions
you shouldn't be implementing things that aren't backwards compatible
within the major version. I thought the benefit of microversions is to know
if a given feature exists within the major version you are using. I would
Hello,
The NSF-funded Chameleon project (https://www.chameleoncloud.org) uses Blazar
to provide advance reservations of resources for running cloud computing
experiments.
We would be interested in contributing as well.
Pierre Riteau
On 28 Aug 2015, at 07:56, Ildikó Váncsa
Our use case for fake AZs (and why I pushed
https://review.openstack.org/#/c/217857/ to enable that sort of behavior) is
what Michal outlined, namely that we use Ceph and do not need or want Cinder to
add itself to the mix when we're dealing with our failure domains. We already
handle that via
Why would that only impact py34 and not py27? Aren't the py27 run with
testtools?
On Fri, Aug 28, 2015 at 5:41 AM, Sean Dague s...@dague.net wrote:
On 08/28/2015 08:34 AM, Kevin Benton wrote:
One of the patches that fixes one of the functional failures that has
been hitting is here:
On 28 Aug 2015, at 14:16, Fujita, Daisuke fuzita.dais...@jp.fujitsu.com
wrote:
Hi, Ihar and Dims
Thank you for your reply.
I uploaded new a patch-set which is a single patch for oslo.log
I'd like you to do a code review.
https://review.openstack.org/#/c/218139/
After this email,
On 28 Aug 2015, at 14:08, Paul Carver pcar...@paulcarver.us wrote:
Has anyone written anything up about expectations for how Big Tent or
Neutron Stadium projects are expected to be installed/distributed/packaged?
Seems like your questions below are more about extendability than e.g.
On 2015-08-28 07:06:03 + (+), Osanai, Hisashi wrote:
I would like to know whether info in http://paste.openstack.org
will be removed or not. If it will be removed, I also would like
to know a condition.
We (the project infrastructure root sysadmins) don't expire/purge
the content on
Hi, Ihar and Dims
Thank you for your reply.
I uploaded new a patch-set which is a single patch for oslo.log
I'd like you to do a code review.
https://review.openstack.org/#/c/218139/
After this email, I'd like to add you to reviewer lists.
Thank you for your cooperation.
Best Regards,
On 08/28/2015 08:50 AM, Kevin Benton wrote:
Why would that only impact py34 and not py27? Aren't the py27 run with
testtools?
py34 is only running some subset of tests, so there are a lot of ways
this can go weird.
It may be that the db tests that are failing assume some other tests
which have
On 08/28/2015 09:32 AM, Alex Meade wrote:
I don't know if this is really a big problem. IMO, even with
microversions you shouldn't be implementing things that aren't backwards
compatible within the major version. I thought the benefit of
microversions is to know if a given feature exists
One of the patches that fixes one of the functional failures that has been
hitting is here: https://review.openstack.org/#/c/217927/
However, it failed in the DVR job on the 'test_router_rescheduling'
test.[1] This failure is because the logic to skip when DVR is enabled is
based on a check that
On Fri, Aug 28, 2015 at 8:07 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
On 28 Aug 2015, at 14:08, Paul Carver pcar...@paulcarver.us wrote:
Has anyone written anything up about expectations for how Big Tent or
Neutron Stadium projects are expected to be
installed/distributed/packaged?
On Fri, Aug 28, 2015 at 9:12 AM, Neil Jerram neil.jer...@metaswitch.com
wrote:
On 28/08/15 13:39, Kevin Benton wrote:
For the py34 failures, they seem to have started around the same time
as a change was merged that adjusted the way they were ran so I
proposed a revert for that patch
I've compiled a list of backwards incompatabilities where the new client
will impact (in some cases break) existing scripts:
https://wiki.openstack.org/wiki/Glance-v2-v1-client-compatability
On 27/08/15 15:32 -0400, Nikhil Komawar wrote:
As a part of our continued effort to make the v2
This morning I kicked off a quick spec for replacing WSME in
Ceilometer with ... something:
https://review.openstack.org/#/c/218155/
This is because not only is WSME not that great, it also results in
controller code that is inscrutable.
The problem with the spec is that it doesn't know
On 28/08/15 15:05 +0100, stuart.mcla...@hp.com wrote:
I've compiled a list of backwards incompatabilities where the new client
will impact (in some cases break) existing scripts:
https://wiki.openstack.org/wiki/Glance-v2-v1-client-compatability
Awesome!
On 27/08/15 15:32 -0400, Nikhil
To recap, we had three issues impacting the gate queue:
1) The neutron functional job has had a high failure rate for a while now.
Since it's impacting the gate,
I've removed it from the gate queue but kept it in the Neutron check queue:
https://review.openstack.org/#/c/218302/
If you'd like to
On 08/28/2015 11:20 AM, Assaf Muller wrote:
To recap, we had three issues impacting the gate queue:
1) The neutron functional job has had a high failure rate for a while
now. Since it's impacting the gate,
I've removed it from the gate queue but kept it in the Neutron check queue:
On 08/28/2015 10:36 AM, Lucas Alvares Gomes wrote:
Hi,
If you just want to shoot the breeze please respond here. If you
have specific comments on the spec please response there.
I have been thinking about doing it for Ironic as well so I'm looking
for options. IMHO after using WSME I
On Fri, Aug 28, 2015 at 1:03 AM, Peter Penchev
openstack-...@storpool.com wrote:
On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy ramy.asse...@hp.com wrote:
Hi Peter,
Your log files require downloads. Please fix it such that they can be viewed
directly [1]
Hi, and thanks for the fast reply!
On Aug 28, 2015 6:49 AM, Sean Dague s...@dague.net wrote:
On 08/28/2015 09:32 AM, Alex Meade wrote:
I don't know if this is really a big problem. IMO, even with
microversions you shouldn't be implementing things that aren't backwards
compatible within the major version. I thought the
Hi,
If you just want to shoot the breeze please respond here. If you
have specific comments on the spec please response there.
I have been thinking about doing it for Ironic as well so I'm looking
for options. IMHO after using WSME I would think that one of the most
important criteria we
On Wed, Aug 19, 2015 at 6:51 PM, Sylvain Bauza sba...@redhat.com wrote:
Hi,
I was writing some tests so I added a contextlib.nested to a checked
TestCase [1]. Unfortunately, contextlib.nested is no longer available in
Python3 and there is no clear solution on how to provide a compatible
On Fri, Aug 28 2015, Chris Dent wrote:
This morning I kicked off a quick spec for replacing WSME in
Ceilometer with ... something:
https://review.openstack.org/#/c/218155/
This is because not only is WSME not that great, it also results in
controller code that is inscrutable.
The
I've compiled a list of backwards incompatabilities where the new client
will impact (in some cases break) existing scripts:
https://wiki.openstack.org/wiki/Glance-v2-v1-client-compatability
Awesome!
To be honest there's a little more red there than I'd like.
Of the 72 commands I tried,
On 08/28/2015 04:36 PM, Lucas Alvares Gomes wrote:
Hi,
If you just want to shoot the breeze please respond here. If you
have specific comments on the spec please response there.
I have been thinking about doing it for Ironic as well so I'm looking
for options. IMHO after using WSME I would
*i just want to understand as to how the request goes from the api-call to
the nova-api and so on after that.*
To answer so on after that, in addition to josh answer, you can also look
into
http://ilearnstack.com/2013/04/26/request-flow-for-provisioning-instance-in-openstack/
.
Now to answer
Hello, Jamie,
I hope I am wrong :)
One comment for your patch.
using region name to filter the endpoint for the token validation may not work
if no-catalog is configured in keystone server. include_service_catalog =
True(BoolOpt) (Optional) Indicate whether to set the
I'm also going to be working on this and pushing one or more patches so
it can load service plugins with extensions. Testing with neutron lbaas
has yielded no success so far.
On Fri, 2015-08-28 at 16:25 -0700, Kevin Benton wrote:
This weekend or early next week I will be pushing a couple of
Hi Cao,
I have reviewed the specification linked above. Thank you for introducing
such an interesting and important feature. But as I commented inline, I
think it still need some further work to do. Such as how to get those logs
stored? To admin and tenant, I think it's different.
And performance
We are going to merge this work. I understand and respect Hongbin's position,
but I respectfully disagree. When we are presented with ways to implement low
overhead best practices like versioned objects, we will. It's not that hard to
bump the version of an object when you change it. I like
On Fri, Aug 28, 2015 at 2:42 PM, Emilien Macchi emil...@redhat.com wrote:
So this week we managed to iterate to have more components part of
Puppet OpenStack Integration CI.
Everything is work in progress but let me share the status:
* one single Puppet run of the scenario001.pp is enough to
Hi,
I think you may have some misunderstanding on the PoC design. (the proxy node
only to listen the RPC to compute-node/cinder-volume/L2/L3 agent…)
1) The cascading layer including the proxy nodes are assumed running in
VMs but not in physical servers (you can do that). Even in CJK
It's possible that I've misunderstood Big Tent/Stadium, but I thought
we were talking about enhancements to Neutron, not separate unrelated
projects.
We have several efforts focused on adding capabilities to Neutron. This
isn't about polluting the Neutron namespace but rather about adding
Adrian, agree with your points. But I think we should discuss it during the
next team meeting and address/answer all concerns which team members may have.
Grzegorz, can you join?
—
Egor
From: Adrian Otto adrian.o...@rackspace.commailto:adrian.o...@rackspace.com
Reply-To: OpenStack Development
I made the following some time ago,
https://wiki.openstack.org/wiki/RunInstanceWorkflows
https://wiki.openstack.org/w/images/a/a9/Curr-run-instance.png
That may be useful for u, (it may also not be that up to date),
Cheers,
Josh
Dhvanan Shah wrote:
Hi,
I'm trying to trace a request made
In an effort to clarify expectations around good practices in writing schema
and data migrations in nova with respect to live upgrades, I’ve added some
extra bits to the live upgrade devref. Please check it out and add your
thoughts:
https://review.openstack.org/#/c/218362/
On Fri, Aug 28 2015, Jay Pipes wrote:
voluptuous may be more Pythonic, as Julien mentioned, but the problem is you
can't expose the validation schema to the end user via any standard document
format (like JSONSchema). Using the jsonschema library along with standard
JSONSchema documents
I enjoy using validictory for using Jsonschema with Python
https://pypi.python.org/pypi/validictory.
Sent from my iPhone
On Aug 28, 2015, at 11:29 AM, Jay Pipes jaypi...@gmail.com wrote:
On 08/28/2015 07:22 AM, Chris Dent wrote:
This morning I kicked off a quick spec for replacing WSME
On Thu, 27 Aug 2015 15:37:24 -0400
gord at live.ca (gord chung) wrote:
polling agent --- topic queue --- notification agent --- topic queue
--- collector (direct connection to db)
or
OpenStack service --- topic queue --- notification agent --- topic
queue --- collector (direct connection
there was a little skeptism because it was originally sold as magic,
but reading the slides from Vancouver[1], it is not magic.
I think I specifically said they're not magic in my slides. Not sure
who sold you them as magic, but you should leave them a
less-than-five-stars review.
Ceilometer
On 28/08/15 12:18 PM, Roman Dobosz wrote:
So imagine we have new versions of the schema for the events, alarms or
samples in ceilometer introduced in Mitaka release while you have all
your ceilo services on Liberty release. To upgrade ceilometer you'll
have to stop all services to avoid data
Markus,
C) +1 to file a spec early, so we can discuss in Tokyo if needed.
Thanks,
dims
On Fri, Aug 28, 2015 at 11:16 AM, Markus Zoeller mzoel...@de.ibm.com
wrote:
Markus Zoeller/Germany/IBM@IBMDE wrote on 08/19/2015 02:15:55 PM:
From: Markus Zoeller/Germany/IBM@IBMDE
To: OpenStack
On Fri, Aug 28, 2015 at 5:12 PM, stuart.mcla...@hp.com wrote:
I've compiled a list of backwards incompatabilities where the new client
will impact (in some cases break) existing scripts:
https://wiki.openstack.org/wiki/Glance-v2-v1-client-compatability
Awesome!
To be honest there's a
This is a proposal to enhance the list of offical tags for our bugs
in Launchpad. During the tagging process in the last weeks it seems
to me that some of the tags are too coarse-grained. Would you see a
benefit in enhancing the official list to more fine-grained tags?
Additionally I would like
Markus Zoeller/Germany/IBM@IBMDE wrote on 08/19/2015 02:15:55 PM:
From: Markus Zoeller/Germany/IBM@IBMDE
To: OpenStack Development Mailing List \(not for usage questions\)
openstack-dev@lists.openstack.org
Date: 08/19/2015 02:31 PM
Subject: Re: [openstack-dev] [openstack][nova] Streamlining
On Fri, Aug 28, 2015 at 1:13 AM Igor Marnat imar...@mirantis.com wrote:
Dmitry,
I don't have yet enough context to discuss Fuel 9.0 release but I have
a question about 8.0.
You mentioned that the start of Fuel 8.0 release cycle inevitably
remains coupled with MOS. Does it mean that we still
On 08/28/2015 07:22 AM, Chris Dent wrote:
This morning I kicked off a quick spec for replacing WSME in
Ceilometer with ... something:
https://review.openstack.org/#/c/218155/
This is because not only is WSME not that great, it also results in
controller code that is inscrutable.
The
On 08/28/2015 08:32 AM, Julien Danjou wrote:
On Fri, Aug 28 2015, Chris Dent wrote:
This morning I kicked off a quick spec for replacing WSME in
Ceilometer with ... something:
https://review.openstack.org/#/c/218155/
This is because not only is WSME not that great, it also results in
Monty Taylor wrote:
On 08/28/2015 08:32 AM, Julien Danjou wrote:
On Fri, Aug 28 2015, Chris Dent wrote:
This morning I kicked off a quick spec for replacing WSME in
Ceilometer with ... something:
https://review.openstack.org/#/c/218155/
This is because not only is WSME not that great, it
So this week we managed to iterate to have more components part of
Puppet OpenStack Integration CI.
Everything is work in progress but let me share the status:
* one single Puppet run of the scenario001.pp is enough to deploy
OpenStack (MySQL, RabbitMQ, Keystone WSGI, Nova, Glance, Neutron
On 28/08/15 12:49 PM, Dan Smith wrote:
there was a little skeptism because it was originally sold as magic,
but reading the slides from Vancouver[1], it is not magic.
I think I specifically said they're not magic in my slides. Not sure
who sold you them as magic, but you should leave them a
On 8/28/2015 10:35 AM, Joe Gordon wrote:
On Aug 28, 2015 6:49 AM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
On 08/28/2015 09:32 AM, Alex Meade wrote:
I don't know if this is really a big problem. IMO, even with
microversions you shouldn't be implementing things that
On 08/28/2015 08:32 AM, Julien Danjou wrote:
On Fri, Aug 28 2015, Chris Dent wrote:
This morning I kicked off a quick spec for replacing WSME in
Ceilometer with ... something:
https://review.openstack.org/#/c/218155/
This is because not only is WSME not that great, it also results in
Hi fellows,
Ilya did a few good contributions to Gnocchi, especially around the
InfluxDB driver, so I'm glad to add him to the list of core reviewers.
Welcome aboard.
Cheers,
--
Julien Danjou
// Free Software hacker
// http://julien.danjou.info
signature.asc
Description: PGP signature
On 28 August 2015 at 16:57, Sean Dague s...@dague.net wrote:
On 08/28/2015 11:20 AM, Assaf Muller wrote:
To recap, we had three issues impacting the gate queue:
1) The neutron functional job has had a high failure rate for a while
now. Since it's impacting the gate,
I've removed it
On 8/28/2015 2:38 AM, Tim Bell wrote:
-Original Message-
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
Sent: 28 August 2015 02:29
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] --detailed-description for OpenStack items
On 8/27/2015 12:23 PM, Tim
My biggest concern is about 4to6 translations. I would prefer to avoid them
as longer as it possible.
From my point of view pure ipv6 is easier to implement than dual stack. I
see it like when you install Fuel node you decide once and forever what IP
version you are go with. We will have two
i should start by saying i re-read my subject line and it arguably comes
off aggressive -- i should probably have dropped 'explain' :)
On 28/08/15 01:47 PM, Alec Hothan (ahothan) wrote:
On 8/28/15, 10:07 AM, gord chung g...@live.ca wrote:
On 28/08/15 12:18 PM, Roman Dobosz wrote:
So
Ryan,
Thanks for sharing your inputs. By looking through your response, I couldn't
find the reasoning about why a young project is the perfect time to enforce a
strict object version rule. I think a young project often starts with a static
(or non-frequently changing) version until a point in
Hello! We put together our details and submitted a review for adding
the Community App Catalog project to the OpenStack governance projects
list [1]. We are looking forward to continuing to grow the catalog in
cooporation with the other projects, and building this showcase of all
the things that
If you want my inexperienced opinion, a young project is the perfect
time to start this.
^--- This ---^
I understand that something like [2] will cause a test to fail when you
make a major change to a versioned object. But you *want* that. It helps
reviewers more easily catch
On Friday, August 28, 2015 8:49 PM, Jeremy Stanley wrote:
We (the project infrastructure root sysadmins) don't expire/purge
the content on paste.openstack.org, though have deleted individual
pastes on request if someone reports material which is abusive or
potentially illegal in many
I'll leave to Kevin's more informed judgment to comment on whether it is
appropriate to merge:
[1] is a list of patches still under review on the feature branch. Some of
them fix issues (like executing API actions), or implement TODOs
This is the current list of TODOs:
It seems like Flask has a reasonable amount of support and there is a good
ecosystem around it but that aside (as Jay said)... I definitely support
exposing the schema to the end user; making it easier for the end user to
validate input / model outputs for their integration with OpenStack
services
This weekend or early next week I will be pushing a couple of more patches
to deal with some of the big TODOs (e.g. bulk). Then we can rename it and
see if we can review the merge.
I don't intend to have it fully replace our built-in WSGI solution in
Liberty. It's too late in the cycle to make
On Aug 28, 2015, at 6:10 PM, Morgan Fainberg morgan.fainb...@gmail.com wrote:
It seems like Flask has a reasonable amount of support and there is a good
ecosystem around it but that aside (as Jay said)... I definitely support
exposing the schema to the end user; making it easier for the end
Hi,
I'm trying to trace a request made for an instance and looking at the flow
in the code.
I'm just trying to understand better how the request goes from the
dashboard to the nova-api , to the other internal components of nova and to
the scheduler and back with a suitable host and launching of
I'm sending out this email to encourage Neutron core reviewers to attend
and participate in the weekly Neutron team meeting [1]. Attendance from
core reviewers has been very low for a while now, and this is the one time
each week (or bi-weekly if you attend only one of the rotating meeting) I
have
1 - 100 of 113 matches
Mail list logo
