Thanks for all the help Chris and all the best.
Now on the lookout for another cells core I can harass and pass obscure bugs
too. It was always reassuring knowing you’d probably already come across the
issue and could point me to a review or git branch with a fix.
Cheers,
Sam
On 23 Oct
On Thu, 23 Oct 2014 05:53:21 +
Shaunak Kashyap shaunak.kash...@rackspace.com wrote:
Thanks Chris. And am I correct in assuming that no weekly api-wg
meetings are currently going on? I don’t see anything here anyway:
https://wiki.openstack.org/wiki/Meetings.
They haven't started yet. Not
On Tue, Oct 21, 2014 at 2:48 PM, Dan Genin daniel.ge...@jhuapl.edu wrote:
So then it is probably best to leave existing Cinder LVM code in
lib/cinder_backends/lvm alone and create a similar set of lvm scripts for
Nova,
perhaps in lib/nova_backends/lvm?
Dan
On 10/21/2014 03:10 PM, Duncan
On Tue, Oct 21, 2014 at 9:17 AM, Duncan Thomas duncan.tho...@gmail.com
wrote:
For LVM-thin I believe it is already disabled? It is only really
needed on LVM-thick, where the returning zeros behaviour is not done.
On 21 October 2014 08:29, Avishay Traeger avis...@stratoscale.com wrote:
I
-Original Message-
From: Andrew Laski [mailto:andrew.la...@rackspace.com]
Sent: 22 October 2014 21:12
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Cells conversation starter
On 10/22/2014 12:52 AM, Michael Still wrote:
Looks good, sorry for missing the meeting!
On 10/22/2014 09:11 PM, Doug Hellmann wrote:
On Oct 20, 2014, at 1:22 PM, Doug Hellmann d...@doughellmann.com wrote:
After today’s meeting, we have filled our seven session slots. Here’s the
proposed list, in no particular order. If you think
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 stable versions of projects that
still need to run on
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,
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 fla...@redhat.com wrote:
On 10/22/2014 02:30 PM, Zhi Yan Liu wrote:
Greetings,
On Wed, Oct 22, 2014 at 4:56 PM, Flavio Percoco fla...@redhat.com wrote:
Greetings,
Back in Havana
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 philip@hp.com wrote:
-Original Message-
From: henry hly [mailto:henry4...@gmail.com]
Sent: 08 October 2014 09:16
To: OpenStack
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 not
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
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
+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:
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
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
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 alaw...@aqorn.com 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
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
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 (externally): fpb
On 23 October 2014 08:30, Preston L. Bannister pres...@bannister.us 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
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
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
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
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:30 -
On 10/09/2014 03:36 PM, Duncan Thomas wrote:
On 9 October 2014 07:49, henry hly henry4...@gmail.com 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
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
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 stable
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 pres...@bannister.us
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
On Thu, Oct 23, 2014 at 8:50 AM, John Griffith john.griffi...@gmail.com
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
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
On Mon, Oct 20, 2014 at 2:44 PM, Mike Bayer mba...@redhat.com 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.
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.
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
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
Works for me.
Tim
P. S. Pardon the brevity. Sent from my mobile.
On Oct 22, 2014, at 5:01 PM, Sean Roberts seanrobert...@gmail.com 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
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
On Thu, Oct 23, 2014 at 10:31 AM, Kyle Mestery mest...@mestery.com 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
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
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 a...@openstack.orgmailto:a...@openstack.org
Reply-To: OpenStack Development Mailing
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
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
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]
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
On 10/22/2014 08:11 PM, Sam Morrison wrote:
On 23 Oct 2014, at 5:55 am, Andrew Laski andrew.la...@rackspace.com 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
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 edgar.mag...@workday.com
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
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 eezh...@mirantis.com wrote:
Hi!
I am working on a bug ping still working once connected even after related
security group rule is deleted
On Oct 23, 2014, at 6:27 AM, Chris Dent chd...@redhat.com 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
On Oct 23, 2014, at 2:56 AM, Flavio Percoco fla...@redhat.com 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
On Oct 23, 2014, at 12:30 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com
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?
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
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
On Thu, Oct 23, 2014 at 7:51 AM, John Griffith john.griffi...@gmail.com
wrote:
On Thu, Oct 23, 2014 at 8:50 AM, John Griffith john.griffi...@gmail.com
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
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 khayam.gon...@gmail.commailto:khayam.gon...@gmail.com
Date: Thursday, October 23, 2014 at 2:32 AM
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)
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
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 the
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
On Thu, Oct 23, 2014 at 3:44 PM, Preston L. Bannister pres...@bannister.us
wrote:
On Thu, Oct 23, 2014 at 7:51 AM, John Griffith john.griffi...@gmail.com
wrote:
On Thu, Oct 23, 2014 at 8:50 AM, John Griffith john.griffi...@gmail.com
wrote:
On Thu, Oct 23, 2014 at 1:30 AM, Preston L.
On Thu, Oct 23, 2014 at 3:04 PM, John Griffith 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 storage never
returns accidental information ... explicit zeroes are not needed.
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
On 10/23/2014 04:24 PM, Preston L. Bannister wrote:
On Thu, Oct 23, 2014 at 3:04 PM, John Griffith john.griffi...@gmail.com
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
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
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
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
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 say
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
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é mga...@iweb.com 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
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
76 matches
Mail list logo
