What is going on with this? If I do a fresh clone of heat and run `tox
-epep8` then I get that complaint. If I then run the recommended command
to fix it, and then `tox -epep8` again, I get the same complaint again ---
and with different differences exhibited! The email below carries a
types
Hi Andreas,
Thank you for this initiative.
We were looking on similar problem for mixing OVS and SR-IOV on same network
adapter, which also requires mac addresses registration of OVS ports.
Please let me know if you would like to collaborate on this effort.
BR,
Irena
-Original Message-
Guessing this is due to the new tox feature which randomizes python's
hash seed.
Excerpts from Mike Spreitzer's message of 2014-08-24 00:10:42 -0700:
> What is going on with this? If I do a fresh clone of heat and run `tox
> -epep8` then I get that complaint. If I then run the recommended comma
On 21 August 2014 12:12, Ihar Hrachyshka wrote:
> Let the ones that are primarily interested in
> good quality of that code (vendors) to drive development. And if some
> plugins become garbage, it's bad news for specific vendors; if neutron
> screws because of lack of concentration on core featur
On Fri, Aug 22, 2014 at 02:33:27PM +0200, Thierry Carrez wrote:
[Snip some well articulated thoughts.]
> Enter the Czar system: each project should have a number of liaisons /
> official contacts / delegates that are fully responsible to cover one
> aspect of the project. We need to have Bugs cza
Hi,
With the ongoing development of LBaaS v2, support for v2 of LBaaS in
neutronclient is also being developed, as can be seen in [1].
The current implementation adds a new syntax for v2; Whereas the v1
syntax is 'neutron lb--', the new v2 syntax is 'neutron
lbaas--'.
We fear that this can lead t
The differences do not look to me like ones that would follow from a
difference in hash seed.
Clint Byrum wrote on 08/24/2014 05:00:21 AM:
> From: Clint Byrum
> To: openstack-dev ,
> Date: 08/24/2014 05:02 AM
> Subject: Re: [openstack-dev] [heat] "heat.conf.sample is not up to date"
>
> Gues
Hi Kevin:
Thanks, this is a great idea! I may try just a slight variation of this
concept. Maybe your idea could be the recommended way to create a 3rd party CI
for plugins that are just being introduced and need to limit the scope of
testing to a small set of plugin-related commits (or plugins
Ihar Hrachyshka wrote:
> Now, maybe putting the module into requirements.txt is an overkill
> (though I doubt it). In that case, we could be interested in getting
> the info in some other centralized way.
Maru is of the opinion that it is overkill. I feel the same way, but I am not
involved much
I'm following this as well since I have the exact same problem in a
docstring patch for heat.
On Sun, Aug 24, 2014 at 9:30 AM, Mike Spreitzer wrote:
> The differences do not look to me like ones that would follow from a
> difference in hash seed.
>
> Clint Byrum wrote on 08/24/2014 05:00:21 AM
On Sunday, August 24, 2014, Anne Gentle wrote:
> I'm following this as well since I have the exact same problem in a
> docstring patch for heat.
>
>
Keystone saw an oddity with the new sample config generator (changing how
options are sorted and therefore changing the way the sample config is
ren
Morgan Fainberg wrote on 08/24/2014 12:01:37
PM:
> ...
>
> Keystone saw an oddity with the new sample config generator
> (changing how options are sorted and therefore changing the way the
> sample config is rendered). This could be a similar / related issue.
>
> Most of the projects stoppe
On Sun, Aug 24, 2014 at 11:10 AM, Mike Spreitzer wrote:
> What I really need to know is what to do when committing a change that
> really does require a change in the sample configuration file. Of course I
> tried running generate_sample.sh, but `tox -epep8` still complains. What is
> the right
Would this work? We used to have warnings in Neutron docs indicating that
instances should not be attached to external networks:
"It is important to understand that you should not attach the instance to
Ext-Net directly. Instead, you must use a floating IP to make it accessible
from the external n
On Aug 24, 2014, at 5:14 PM, Henry Gessau wrote:
> Ihar Hrachyshka wrote:
>> Now, maybe putting the module into requirements.txt is an overkill
>> (though I doubt it). In that case, we could be interested in getting
>> the info in some other centralized way.
>
> Maru is of the opinion that it
When we deploy devstack, we get the files with authentication credentials
created in devstack/accr directory. I was playing around the command line
clients with one of my script which can use the auth files created to
execute different auth credentials, when the idea about having os-auth-file
as an
On Sun, Aug 24, 2014, at 06:37 AM, John Schwarz wrote:
> Hi,
>
> With the ongoing development of LBaaS v2, support for v2 of LBaaS in
> neutronclient is also being developed, as can be seen in [1].
> The current implementation adds a new syntax for v2; Whereas the v1
> syntax is 'neutron lb--', th
Hi,
The amount of tests that we are having to add skips to for the One Convergence
plugin has grown quite a bit lately.
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/unit/oneconvergence/test_nvsd_plugin.py#n58
This is the only plugin that inherits from the NeutronDbPluginV2
So I have the spec changes all fixed up and pending reviews
https://review.openstack.org/#/c/113638/
https://review.openstack.org/#/c/116530/
https://review.openstack.org/#/c/116531/
https://review.openstack.org/#/c/116532/
Once these are merged, i will start pinging people on blueprints that are
On 08/23/2014 06:35 PM, Clint Byrum wrote:
I agree as well. PTL is a servant of the community, as any good leader
is. If the PTL feels they have to drop the hammer, or if an impass is
reached where they are asked to, it is because they have failed to get
everyone communicating effectively, not b
I am looking for policy overview/impact covering heat, neutron, nova, olso,
mistral, and rubric. Are there any others that want to join us and discuss how
policy impacts their project? I would welcome some discussion around
Opendaylight policy as well.
We have 21 people signed up to join us so
On 23 August 2014 00:55, Ihar Hrachyshka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi all,
>
> this week is quite bumpy for unit testing in gate. First, it was
> upgrade to new 'tox' version that broke quite some branches.
>
> And today new testtools 0.9.36 were released and w
On 08/22/2014 09:02 PM, Anne Gentle wrote:
/flame-on
Let's call spades, spades here. Czar is not only overkill, but
the wrong metaphor.
/flame-off
I'm with Rocky on the anti-czar-as-a-word camp. We all like clever
names to shed the "corporate" stigma but this word ain't it.
On 08/23/2014 02:01 AM, Clint Byrum wrote:
I don't know how Zaqar does its magic, but I'd love to see simple signed
URLs rather than users/passwords. This would work for Heat as well. That
way we only have to pass in a single predictably formatted string.
Excerpts from Zane Bitter's message of 2
Ruslan Kamaldinov wrote on 08/24/2014 12:30:04
PM:
> From: Ruslan Kamaldinov
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 08/24/2014 12:32 PM
> Subject: Re: [openstack-dev] [heat] "heat.conf.sample is not up to date"
>
> On Sun, Aug 24, 2014 at 11:10 AM, M
I think this will depend on the deployment type for the L3 agent. If the
gateway_external_network_id is left blank for the L3 agent, the external
network is vlan tagged just like any regular network and doesn't have an
independent bridge.[1] In that deployment scenario it should work fine.
On Sun
I also feel that "graceful power off" is one of the feature that we want in
ironic. But until then, you can see if the below works for you:
You can set the following property to false which will prevent ironic to
sync the power state. It will instead update the node with the latest
power status
27 matches
Mail list logo
