Doug, thanks for writing this up.
Looking at your list, I created a patch and only changed oslo.log:
https://review.openstack.org/130444
Please double check that I didn't miss anything,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX Products GmbH, Maxfel
On 10/22/2014 04:46 PM, Zhi Yan Liu wrote:
> Replied in inline.
>
> On Wed, Oct 22, 2014 at 9:33 PM, Flavio Percoco wrote:
>> On 10/22/2014 02:30 PM, Zhi Yan Liu wrote:
>>> Greetings,
>>>
>>> On Wed, Oct 22, 2014 at 4:56 PM, Flavio Percoco wrote:
Greetings,
Back in Havana a, parti
Hi Phil,
Thanks for your feedback, and patience of this long history reading :)
See comments inline.
On Wed, Oct 22, 2014 at 5:59 PM, Day, Phil wrote:
>> -Original Message-
>> From: henry hly [mailto:henry4...@gmail.com]
>> Sent: 08 October 2014 09:16
>> To: OpenStack Development Mailing
John,
As a (new) OpenStack developer, I just discovered the
"CINDER_SECURE_DELETE" option.
As an *implicit* default, I entirely approve. Production OpenStack
installations should *absolutely* insure there is no information leakage
from one instance to the next.
As an *explicit* default, I am no
Hi Boris,
I am still getting my feet wet with rally so some concepts are new, and did not
quite get your statement regarding the different load generators. I am
presuming you are referring to the Scenario runner and the different “types” of
runs.
What I was looking at is the runner, where we sp
Hi,
Because I am not able to find a meeting room to have deep diving OpenStack
cascading before design summit. You are welcome to have a f2f conversation
about the cascading before design summit. I planned to stay at Paris from
Oct.30 to Nov.8, if you have any doubt or question, please feel fre
+1 many thanks to Kyle for putting this as a priority, its most welcome.
/Alan
-Original Message-
From: Erik Moe [mailto:erik@ericsson.com]
Sent: October-22-14 5:01 PM
To: Steve Gordon; OpenStack Development Mailing List (not for usage questions)
Cc: iawe...@cisco.com
Subject: Re: [op
Thanks for creating the page.
I have added a section to it with information about Kosher restaurants
as well.
Well done and thank you for the invaluable information
Maish
On 14/10/2014 20:02, Anita Kuno wrote:
> On 10/14/2014 12:40 PM, Sylvain Bauza wrote:
>> Le 14/10/2014 18:29, Anita Kuno a éc
Hello.
We have only one voting gate for changes submitted to fuel-library which
checks deployment of Openstack nodes with Puppet manifests from
fuel-library.
But we must to check for two more important potential 'smoke sources':
1) Master node build:
* nailgun::*_only classes - for docker builds
I am trying to login into VM from host using ssh key pair instead of
password. I have created VM using keypair *khayamkey* and than tried to
login into vm using following command
ssh -l tux -i khayamkey.pem 10.3.24.56
where *tux* is username for VM, but I got following error
On 22 Oct 2014, at 21:03, Adam Lawson wrote:
> What is current best practice to restore a failed Fuel node?
It’s documented here:
http://docs.mirantis.com/openstack/fuel/fuel-5.1/operations.html#restoring-fuel-master
Regards,
--
Tomasz 'Zen' Napierala
Sr. OpenStack Engineer
tnapier...@miranti
Hi!
I am working on a bug "ping still working once connected even after related
security group rule is deleted" (
https://bugs.launchpad.net/neutron/+bug/1335375). The gist of the problem
is the following: when we delete a security group rule the corresponding
rule in iptables is also deleted, but
I've proposed a spec to Ceilometer
https://review.openstack.org/#/c/129669/
for a suite of declarative HTTP tests that would be runnable both in
gate check jobs and in local dev environments.
There's been some discussion that this may be generally applicable
and could be best served by a ge
>
>
>1. I feel like we should not require user to unpack the plugin before
>installing it. Moreover, we may chose to distribute plugins in our own
>format, which we may potentially change later. E.g. "lbaas-v2.0.fp". I'd
>rather stick with two actions:
>
>
>- Assembly (externall
On 23 October 2014 08:30, Preston L. Bannister wrote:
> John,
>
> As a (new) OpenStack developer, I just discovered the "CINDER_SECURE_DELETE"
> option.
>
> As an *implicit* default, I entirely approve. Production OpenStack
> installations should *absolutely* insure there is no information leakag
Hi,
> -Original Message-
> From: joehuang [mailto:joehu...@huawei.com]
> Sent: 23 October 2014 09:59
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack
> cascading
>
> Hi,
>
> Because I am not
Hi!
This is an interesting topic, I don't know if there's any way to
target connection tracker rules by MAC, but that'd be the ideal solution.
I also understand the RETURN for RELATED,ESTABLISHED is there for
performance reasons, and removing it would lead to longer table evaluation,
and deg
Recently, we have identified clients with problems due to the
bad scalability of security groups in Havana and Icehouse, that
was addressed during juno here [1] [2]
This situation is identified by blinking agents (going UP/DOWN),
high AMQP load, nigh neutron-server load, and timeout fr
Hi, Phil,
I am sorry that no enough information for you to understand the cascading in
the document. If we can talk f2f, I can explain much more in detail. But in
short, I will give a simplified picture how a virtual machine will be booted:
The general process to boot a VM is like this:
Nova A
On Wed, Oct 22 2014, Doug Hellmann wrote:
> 2014-11-05 11:00 - Oslo graduation schedule
> 2014-11-05 11:50 - oslo.messaging
> 2014-11-05 13:50 - A Common Quota Management Library
> 2014-11-06 11:50 - taskflow
> 2014-11-06 13:40 - Using alpha versioning for Oslo libraries
> 2014-11-06 16:
On 10/09/2014 03:36 PM, Duncan Thomas wrote:
On 9 October 2014 07:49, henry hly wrote:
Hi Joshua,
...in fact hierarchical scale
depends on square of single child scale. If a single child can deal
with 00's to 000's, cascading on it would then deal with 00,000's.
That is faulty logic - maybe t
On 10/22/2014 11:04 AM, Steven Dake wrote:
A few weeks ago in IRC we discussed the criteria for joining the core
team in Kolla. I believe Daneyon has met all of these requirements by
reviewing patches along with the rest of the core team and providing
valuable comments, as well as implementing n
On 10/23/2014 08:56 AM, Flavio Percoco wrote:
> On 10/22/2014 08:15 PM, Doug Hellmann wrote:
>> The application projects are dropping python 2.6 support during Kilo, and
>> I’ve had several people ask recently about what this means for Oslo. Because
>> we create libraries that will be used by sta
Kyle,
Gentle reminder... when you get a chance!..
Anne,
In case, if i need to send it to different group or email-id to reach Kyle
Mestery, pls. let me know. Thanks for your help.
Regards,
Vad
--
On Tue, Oct 21, 2014 at 8:51 AM, Vadivel Poonathan <
vadivel.openst...@gmail.com> wrote:
> Hi Kyle
On Thu, Oct 23, 2014 at 1:30 AM, Preston L. Bannister
wrote:
> John,
>
> As a (new) OpenStack developer, I just discovered the
> "CINDER_SECURE_DELETE" option.
>
> As an *implicit* default, I entirely approve. Production OpenStack
> installations should *absolutely* insure there is no informatio
On Thu, Oct 23, 2014 at 8:50 AM, John Griffith
wrote:
>
>
> On Thu, Oct 23, 2014 at 1:30 AM, Preston L. Bannister <
> pres...@bannister.us> wrote:
>
>> John,
>>
>> As a (new) OpenStack developer, I just discovered the
>> "CINDER_SECURE_DELETE" option.
>>
>
OHHH... Most importantly, I almost forgo
All,
Recently we launched a couple new Fuel related projects
(fuel_plugin_builder, fuel_agent, fuel_upgrade, etc.). Those projects are
written in python and they use different approaches to organizing CLI,
configuration, different third party libraries, etc. Besides, we have some
old Fuel projects
On Mon, Oct 20, 2014 at 2:44 PM, Mike Bayer wrote:
> As I’ve established oslo.db blueprints which will roll out new SQLAlchemy
> connectivity patterns for consuming applications within both API [1] and
> tests [2], one of the next big areas I’m to focus on is that of querying.
> If one looks
Vad:
The third-party CI is required for your upstream driver. I think
what's different from my reading of this thread is the question of
what is the requirement to have a driver listed in the upstream
documentation which is not in the upstream codebase. To my knowledge,
we haven't done this. Thus,
Hi Mike,
I would like to add a bit more details about current implementation and how
it can be done.
*Implement installation as a scripts inside of tar ball:*
Cons:
* install script is really simple right now, but it will be much more
complicated
** it requires to implement logic where we can ask
Hi
When I fix some bugs, I found that some code in
nova/compute/api.py
sometimes we use db ,sometimes we use objects do we have any
criteria for it? I knew we can't access db in compute layer code, how about
others ? prefer object or db direct access? thanks
def service_
Works for me.
Tim
P. S. Pardon the brevity. Sent from my mobile.
> On Oct 22, 2014, at 5:01 PM, "Sean Roberts" wrote:
>
> We are scheduled for Monday, 03 Nov, 14:30 - 16:00. I have a conflict with
> the “Meet the Influencers” talk that runs from 14:30-18:30, plus the GBP
> session is on Tu
I have another example, nailgun and UI are bundled in FuelWeb being quite
independent components. Nailgun is python REST API, while UI is HTML/CSS/JS
+ libs. I also support the idea making CLI a separate project, it is
similar to FuelWeb UI, it uses the same REST API. Fuelclient lib is also
good id
On Thu, Oct 23, 2014 at 10:31 AM, Kyle Mestery wrote:
> Vad:
>
> The third-party CI is required for your upstream driver. I think
> what's different from my reading of this thread is the question of
> what is the requirement to have a driver listed in the upstream
> documentation which is not in
Just a joke: Can we drop supporting Python 2.6, when several project still
have hooks for Python 2.4?
https://github.com/openstack/python-novaclient/blob/master/novaclient/exceptions.py#L195-L203
https://github.com/openstack/python-cinderclient/blob/master/cinderclient/exceptions.py#L147-L155
On
On Thu, 2014-10-23 at 18:56 +0300, Andrey Kurilin wrote:
> Just a joke: Can we drop supporting Python 2.6, when several project
> still have hooks for Python 2.4?
>
> https://github.com/openstack/python-novaclient/blob/master/novaclient/exceptions.py#L195-L203
> https://github.com/openstack/python
I second Anne’s and Kyle comments. Actually, I like very much the wiki part to
provide some visibility for out-of-tree plugins/drivers but not into the
official documentation.
Thanks,
Edgar
From: Anne Gentle mailto:a...@openstack.org>>
Reply-To: "OpenStack Development Mailing List (not for usa
I forgot to mention that I can help to coordinate the creation and maintenance
of the wiki for non-upstreamed drivers for Neutron.
We need to be sure that we DO NOT confuse users with the current information
here:
https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers
I have been maintainin
Hi Kyle and Anne,
Thanks for the clarifications... understood and it makes sense.
However, per my understanding, the drivers (aka plugins) are meant to be
developed and supported by third-party vendors, outside of the OpenStack
community, and they are supposed to work as plug-n-play... they are n
The Keystone team has released python-keystoneclient 0.11.2 [1]. This version
includes a number of bug fixes.
Details of new features and bug fixes included in the 0.11.2 release of
python-keystoneclient can be found on the milestone information page [2].
[1] https://pypi.python.org/pypi/pytho
Hi folks,
I've been looking at the convergence stuff, and become a bit concerned
that we're more or less flying blind (or at least I have been) in trying
to figure out the design, and also that some of the first implementation
efforts seem to be around the stuff that is _most_ expensive to chan
On 10/22/2014 08:11 PM, Sam Morrison wrote:
On 23 Oct 2014, at 5:55 am, Andrew Laski wrote:
While I agree that N is a bit interesting, I have seen N=3 in production
[central API]-->[state/region1]-->[state/region DC1]
\->[state/region DC2]
-->[s
On Thu, Oct 23, 2014 at 12:35 PM, Vadivel Poonathan
wrote:
> Hi Kyle and Anne,
>
> Thanks for the clarifications... understood and it makes sense.
>
> However, per my understanding, the drivers (aka plugins) are meant to be
> developed and supported by third-party vendors, outside of the OpenStack
>When I fix some bugs, I found that some code in
> nova/compute/api.py
> sometimes we use db ,sometimes we use objects do we have
> any criteria for it? I knew we can't access db in compute layer code,
> how about others ? prefer object or db direct access? thanks
Prefer
On Thu, Oct 23, 2014 at 9:49 AM, Edgar Magana
wrote:
> I forgot to mention that I can help to coordinate the creation and
> maintenance of the wiki for non-upstreamed drivers for Neutron.
>
>>[vad] Edgar, that would be nice!... but not sure whether it has to wait
till the outcome of the design d
Preventing plugin developers from implementing their own installer is
a pro, not a con, you've already listed one reason in cons against
install scripts inside plugin tarball: if we centralize plugin
installation and management logic in fuel, we can change it once for
all plugins and don't have to
As discussed during the neutron-drivers meeting this week [1], we've
going to use one of the Neutron 40 minute design summit slots for
lightning talks. The basic idea is we will have 6 lightning talks,
each 5 minutes long. We will force a 5 minute hard limit here. We'll
do the lightning talk round
If you exec conntrack inside the namespace with ip netns exec does it still
show both connections?
Vish
On Oct 23, 2014, at 3:22 AM, Elena Ezhova wrote:
> Hi!
>
> I am working on a bug "ping still working once connected even after related
> security group rule is deleted"
> (https://bugs.la
On Oct 23, 2014, at 6:27 AM, Chris Dent wrote:
>
> I've proposed a spec to Ceilometer
>
> https://review.openstack.org/#/c/129669/
>
> for a suite of declarative HTTP tests that would be runnable both in
> gate check jobs and in local dev environments.
>
> There's been some discussion that
On Oct 23, 2014, at 2:56 AM, Flavio Percoco wrote:
> On 10/22/2014 08:15 PM, Doug Hellmann wrote:
>> The application projects are dropping python 2.6 support during Kilo, and
>> I’ve had several people ask recently about what this means for Oslo. Because
>> we create libraries that will be use
On Oct 23, 2014, at 12:30 PM, Kevin L. Mitchell
wrote:
> On Thu, 2014-10-23 at 18:56 +0300, Andrey Kurilin wrote:
>> Just a joke: Can we drop supporting Python 2.6, when several project
>> still have hooks for Python 2.4?
>>
>> https://github.com/openstack/python-novaclient/blob/master/novacli
Hi
The summit planning etherpad [0] is now available to continue discussion topics
for the Poppy design session in Paris (to be held on Tuesday Nov 4th, at 2pm)
The planning etherpad will be kept open until next Thursday, during which we
will finalize what will be discussed during the Poppy Des
In order to help ease an ongoing struggle with session size limit issues,
Horizon is planning on changing the default session store from signed
cookie to simple server side session storage using sqlite. The size limit
for cookie based sessions is 4K and when this value is overrun, the result
is tru
On Thu, Oct 23, 2014 at 7:51 AM, John Griffith
wrote:
>
> On Thu, Oct 23, 2014 at 8:50 AM, John Griffith
> wrote:
>>
>> On Thu, Oct 23, 2014 at 1:30 AM, Preston L. Bannister <
>> pres...@bannister.us> wrote:
>>
>>> John,
>>>
>>> As a (new) OpenStack developer, I just discovered the
>>> "CINDER_SE
Hi Khayam,
Read below warning message carefully.
Open /home/openstack/.ssh/known_hosts file from where you are trying to connect
to the VM, delete line #1 and try it again.
TP
From: Khayam Gondal mailto:khayam.gon...@gmail.com>>
Date: Thursday, October 23, 2014 at 2:32 AM
To: "openst...@lists.
All in all this is been a long time coming. The cookie-based option was useful
as a batteries-included, simplest-case scenario. Moving to SQLite is a
reasonable second choice since most systems Horizon might be deployed on
support sqlite out of the box.
I would make a couple notes:
1) If
There are two categories of problems:
1. some networks don't pass VLAN tagged traffic, and it's impossible to
detect this from the API
2. it's not possible to pass traffic from multiple networks to one port on
one machine as (e.g.) VLAN tagged traffic
(1) is addressed by the VLAN trunking network
On Thu, 2014-10-23 at 17:19 -0400, Doug Hellmann wrote:
> I’m not aware of any Oslo code that presents a problem for those
> plugins. We wouldn’t want to cause a problem, but as you say, we don’t
> have anywhere to test 2.4 code. Do you know if the Xen driver uses any
> of the Oslo code?
I missed
Hi Miguel,
while we'd need to hear from the stable team, I think it's not such a bad
idea to make this tool available to users of pre-juno openstack releases.
As far as upstream repos are concerned, I don't know if this tool violates
the criteria for stable branches. Even if it would be a rather l
On Thu, Oct 23, 2014 at 3:44 PM, Preston L. Bannister
wrote:
>
> On Thu, Oct 23, 2014 at 7:51 AM, John Griffith
> wrote:
>>
>> On Thu, Oct 23, 2014 at 8:50 AM, John Griffith
>> wrote:
>>>
>>> On Thu, Oct 23, 2014 at 1:30 AM, Preston L. Bannister <
>>> pres...@bannister.us> wrote:
>>>
John,
On Thu, Oct 23, 2014 at 3:04 PM, John Griffith
wrote:
The debate about whether to wipe LV's pretty much massively depends on the
>> intelligence of the underlying store. If the lower level storage never
>> returns accidental information ... explicit zeroes are not needed.
>>
>
> On Thu, Oct 23,
Hey German/Susanne,
To continue our conversation from our IRC meeting could you all provide
more insight into you usage requirements? Also, I'd like to clarify a few
points related to using logging.
I am advocating that logs be used for multiple purposes, including
billing. Billing requirements a
On 10/23/2014 04:24 PM, Preston L. Bannister wrote:
On Thu, Oct 23, 2014 at 3:04 PM, John Griffith mailto:john.griffi...@gmail.com>> wrote:
The debate about whether to wipe LV's pretty much massively
depends on the intelligence of the underlying store. If the
lower level
Hi,
In neutron, user with “admin” role can specify the provider network parameters
when creating a network.
—provider:network_type
—provider:physical_network
—provider:segmentation_id
localadmin@qa4:~/devstack$ neutron net-create test-network
--provider:network_type vlan --provider:physical_n
On 2014-10-23 7:00 PM, Danny Choi (dannchoi) wrote:
In neutron, user with “admin” role can specify the provider network
parameters when creating a network.
—provider:network_type
—provider:physical_network
—provider:segmentation_id
localadmin@qa4:~/devstack$ neutron net-create test-network
--p
Today, OpenStack makes placement decision mainly based on Compute demands
(Scheduler is part of Nova). It also uses some info provided about platform's
Compute capabilities. But for a given application (consists of some VMs, some
Network appliances, some storage etc), Nova/Scheduler has no way t
On 2014-10-23 17:18:04 -0400 (-0400), Doug Hellmann wrote:
> I think we have to actually wait for M, don’t we (K & L represents
> 1 year where J is supported, M is the first release where J is not
> supported and 2.6 can be fully dropped).
[...]
Roughly speaking, probably. It's more accurate to sa
Hello,
At the Atlanta summit there was a session on removing python2.6
testing/support from the OpenStack Kilo release [0]. The Infra team is
working on enacting this change in the near future.
The way that this will work is python26 jobs will be removed from
running on master and feature branche
On 10/23/2014 07:57 PM, Elzur, Uri wrote:
Today, OpenStack makes placement decision mainly based on Compute
demands (Scheduler is part of Nova). It also uses some info provided
about platform’s Compute capabilities. But for a given application
(consists of some VMs, some Network appliances, some
On Thu, Oct 23, 2014 at 6:12 PM, Mathieu Gagné wrote:
> On 2014-10-23 7:00 PM, Danny Choi (dannchoi) wrote:
>
>>
>> In neutron, user with “admin” role can specify the provider network
>> parameters when creating a network.
>>
>> —provider:network_type
>> —provider:physical_network
>> —provider:se
On 10/23/14 6:22 AM, Elena Ezhova wrote:
> Hi!
>
> I am working on a bug "ping still working once connected even after
> related security group rule is
> deleted" (https://bugs.launchpad.net/neutron/+bug/1335375). The gist of
> the problem is the following: when we delete a security group rule the
Hi all
I have felt some grumblings about usability issues with Heat
templates/client/etc..
and wanted a way that users could come and give us feedback easily (low
barrier). I started an etherpad (
https://etherpad.openstack.org/p/heat-useablity-improvements) - the first
win is it is spelt wrong :-
Hi Angus,
quite a noble intent, one that requires lots of attempts like this you
have started.
On 10/23/2014 09:32 PM, Angus Salkeld wrote:
> I have felt some grumblings about usability issues with Heat
> templates/client/etc..
> and wanted a way that users could come and give us feedback easily
On Fri, Oct 24, 2014 at 4:00 PM, Stefano Maffulli
wrote:
> Hi Angus,
>
> quite a noble intent, one that requires lots of attempts like this you
> have started.
>
> On 10/23/2014 09:32 PM, Angus Salkeld wrote:
> > I have felt some grumblings about usability issues with Heat
> > templates/client/et
Angus,
There are two groups which may be relevant regarding ‘consumers’ of Heat
-Application eco system working group at
https://wiki.openstack.org/wiki/Application_Ecosystem_Working_Group
-API working group at https://wiki.openstack.org/wiki/API_Working_Group
There are some d
75 matches
Mail list logo
