Hi,
MS has been down for a few days. The following patches will help us get it up
and running again:
- requirements - https://review.openstack.org/139545
- oslo.vmware - https://review.openstack.org/139296 (depends on the patch
above)
- devstack - https://review.openstack.org/139515
Hopefully
I see the difference now.
The main concern I see with the NOOP type is that creating the virtual
interface could require different logic for certain hypervisors. In that
case Neutron would now have to know things about nova and to me it seems
like that's slightly too far the other direction.
On
One reason for trying to get an more complete API into Neutron is to have a
standardized API. So users know what to expect and for providers to have
something to comply to. Do you suggest we bring this standardization work to
some other forum, OPNFV for example? Neutron provides low level
On Thursday 04 December 2014 19:08:06 Sean Dague wrote:
Sorry for the late announce, too much turkey and pie
This Friday, Dec 5th, we'll be talking with Steve Martinelli and David
Stanek about Keystone Authentication in OpenStack.
Wiki page says that the event will be Friday Dec 5th -
I agree, and I cross-posted that question to openstack-infra to make
sure the infra team sees it:
http://lists.openstack.org/pipermail/openstack-infra/2014-December/002215.html
Carl Baldwin wrote:
+1 I've been meaning to say something like this but never got around
to it. Thanks for speaking
From: James Polley [mailto:j...@jamezpolley.com]
Sent: 04 December 2014 17:17
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [TripleO] Alternate meeting time
On Thu, Dec 4, 2014 at 11:40 AM, marios
mar...@redhat.commailto:mar...@redhat.com wrote:
Hi Matt, Nova,
I'll look into this.
Gilliard
On Thu, Dec 4, 2014 at 9:51 PM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
On 12/4/2014 6:02 AM, Davanum Srinivas wrote:
+1 to @markmc's default is global value and override for project
specific key suggestion.
-- dims
On Wed, Dec
Hi All,
We have a requirement to configure Openstack Juno setup in Data Center with
two Dell Blade Server.
We are planning to use one blade server to install Centos 7 which will be
our Hypervisor
Second machine we will install Xenserver.
Inside Xenserver we will create two CentOS 7 machine
On Tue, Nov 18, 2014 at 07:06:59AM -0500, Sean Dague wrote:
Nova currently has 197 patches that have seen no activity in the last 4
weeks (project:openstack/nova age:4weeks status:open).
On a somewhat related note, nova-specs currently has 17 specs
open against specs/juno, most with -2 votes. I
I have a script that does 95% of what you want:
https://github.com/matthewoliver/swift_abandon_notifier
We are using it for swift reviews. At the moment the only thing it doesn't
do is actually abandon, it instead sends a warning email and waits n days
(2 weeks by default) for action, if it
On 12/05/2014 03:37 AM, Boris Bobrov wrote:
On Thursday 04 December 2014 19:08:06 Sean Dague wrote:
Sorry for the late announce, too much turkey and pie
This Friday, Dec 5th, we'll be talking with Steve Martinelli and David
Stanek about Keystone Authentication in OpenStack.
Wiki page
On Fri, Dec 05, 2014 at 11:16:28PM +1100, Matthew Oliver wrote:
I have a script that does 95% of what you want:
https://github.com/matthewoliver/swift_abandon_notifier
We are using it for swift reviews. At the moment the only thing it doesn't
do is actually abandon, it instead sends a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/12/14 16:59, Vadivel Poonathan wrote:
Hi Kyle and all,
Was there any conclusion in the design summit or the meetings
afterward about splitting the vendor plugins/drivers from the
mainstream neutron and documentation of out-of-tree
I got bit by another bug yesterday where there was a typo between
variables in the source tree. So I started down the process of set -o
nounset to see how bad it would be to prevent that in the future.
There are 2 major classes of issues where the code is functioning fine,
but is caught by
On Dec 5, 2014 7:07 AM, Daniel P. Berrange berra...@redhat.com wrote:
On Tue, Nov 18, 2014 at 07:06:59AM -0500, Sean Dague wrote:
Nova currently has 197 patches that have seen no activity in the last 4
weeks (project:openstack/nova age:4weeks status:open).
On a somewhat related note,
On 12/05/2014 08:05 AM, Joe Gordon wrote:
On Dec 5, 2014 7:07 AM, Daniel P. Berrange berra...@redhat.com
mailto:berra...@redhat.com wrote:
On Tue, Nov 18, 2014 at 07:06:59AM -0500, Sean Dague wrote:
Nova currently has 197 patches that have seen no activity in the last 4
weeks
Dear all TC PTL,
In the 40 minutes cross-project summit session “Approaches for scaling out”[1],
almost 100 peoples attended the meeting, and the conclusion is that cells can
not cover the use cases and requirements which the OpenStack cascading
solution[2] aim to address, the background
Hello everyone,
Because MagnetoDB project uses more frequent releases than other OpenStack
projects, i propose use following versioning strategy for MagnetoDB packages:
1:2014.2-0ubuntu1
1:2014.2~rc2-0ubuntu1
1:2014.2~rc1-0ubuntu1
1:2014.2~b2-0ubuntu1
On Fri, Dec 05, 2014 at 11:05:28AM +1100, Michael Still wrote:
One of the things that happens over time is that some of our core
reviewers move on to other projects. This is a normal and healthy
thing, especially as nova continues to spin out projects into other
parts of OpenStack.
However,
On 12/5/2014 7:41 AM, Daniel P. Berrange wrote:
On Fri, Dec 05, 2014 at 11:05:28AM +1100, Michael Still wrote:
One of the things that happens over time is that some of our core
reviewers move on to other projects. This is a normal and healthy
thing, especially as nova continues to spin out
On 12/05/2014 01:05 AM, Michael Still wrote:
One of the things that happens over time is that some of our core
reviewers move on to other projects. This is a normal and healthy
thing, especially as nova continues to spin out projects into other
parts of OpenStack.
However, it is important
On Fri, Dec 05, 2014 at 01:41:59PM +, Daniel P. Berrange wrote:
On Fri, Dec 05, 2014 at 11:05:28AM +1100, Michael Still wrote:
One of the things that happens over time is that some of our core
reviewers move on to other projects. This is a normal and healthy
thing, especially as nova
On Fri, Dec 05, 2014 at 07:44:24AM -0600, Matt Riedemann wrote:
On 12/5/2014 7:41 AM, Daniel P. Berrange wrote:
On Fri, Dec 05, 2014 at 11:05:28AM +1100, Michael Still wrote:
One of the things that happens over time is that some of our core
reviewers move on to other projects. This is a
Joe,
Related to this topic, At the summit, there was a session on Cells v2
and following up on that there have been BP(s) filed in Nova
championed by Andrew -
https://review.openstack.org/#/q/owner:%22Andrew+Laski%22+status:open,n,z
thanks,
dims
On Fri, Dec 5, 2014 at 8:23 AM, joehuang
On Fri, Dec 5, 2014 at 7:56 AM, Daniel P. Berrange berra...@redhat.com
wrote:
FWIW, markmc is already off the list [1].
Ah yes, must be that russell needs to update the config file for his script
to stop marking markmc as core.
Regards,
Daniel
--
Anyone can do it:
On 2014-12-04 18:37:48 -0700 (-0700), Carl Baldwin wrote:
+1 I've been meaning to say something like this but never got
around to it. Thanks for speaking up.
https://storyboard.openstack.org/#!/story/1172753
I think Ryan said it might be a bug in the OpenID plug-in, but if so
he didn't put
On 12/05/2014 08:41 AM, Daniel P. Berrange wrote:
On Fri, Dec 05, 2014 at 11:05:28AM +1100, Michael Still wrote:
One of the things that happens over time is that some of our core
reviewers move on to other projects. This is a normal and healthy
thing, especially as nova continues to spin out
I've moved the bug to 6.1. And I'm going to add it to our roadmap as a
separate item.
On Wed, Nov 26, 2014 at 1:31 PM, Mike Scherbakov mscherba...@mirantis.com
wrote:
Can we put it as a work item for diagnostic snapshot improvements, so we
won't forget about this in 6.1?
On Tuesday,
The Oslo team spent yesterday working on our backlog. We triaged all of our
“New” bugs and re-triaged many of the other existing open bugs, closing some as
obsolete or fixed. We reviewed many patches in the backlog as well, and landed
quite a few. We did not clear as much of the backlog for our
In my opinion, further discussion is needed. The proposal on the table is
to have 2 weekly meetings, one at the existing time of 1800UTC on Monday
and, also in the same week, to have another meeting at 0800 UTC on Tuesday.
Here are some of the problems that I see with this approach:
1. Meeting
Thanks everyone who attended the weekly meeting yesterday.
Great job in delivering on the kilo-1 deliverables for Poppy CDN.
https://launchpad.net/poppy/+milestone/kilo-1
We were able to be dev complete the following items:
- The ability to configure a service containing domains, origins,
On Wed, 2014-12-03 at 14:42 +0100, Tomas Sedovic wrote:
On 12/03/2014 11:11 AM, Steven Hardy wrote:
Hi all,
Lately I've been spending more time looking at tripleo and doing some
reviews. I'm particularly interested in helping the no-mergepy and
subsequent puppet-software-config
On Fri, Dec 5, 2014 at 4:39 PM, Russell Bryant rbry...@redhat.com wrote:
On 12/05/2014 08:41 AM, Daniel P. Berrange wrote:
On Fri, Dec 05, 2014 at 11:05:28AM +1100, Michael Still wrote:
One of the things that happens over time is that some of our core
reviewers move on to other projects.
On 12/05/2014 11:23 AM, Joe Gordon wrote:
As you are more then aware of, our policy for removing people from core
is to leave that up the the PTL (I believe you wrote that) [0]. And I
don't think numbers alone are a good metric for sorting out who to
remove. That being said no matter what
I just put up a quick pre-weekend POC at
https://review.openstack.org/#/c/139672/ - comments welcome on that
patch.
Thanks :)
On Fri, Dec 5, 2014 at 10:07 AM, Matthew Gilliard
matthew.gilli...@gmail.com wrote:
Hi Matt, Nova,
I'll look into this.
Gilliard
On Thu, Dec 4, 2014 at 9:51 PM,
On Dec 5, 2014 11:39 AM, Russell Bryant rbry...@redhat.com wrote:
On 12/05/2014 11:23 AM, Joe Gordon wrote:
As you are more then aware of, our policy for removing people from core
is to leave that up the the PTL (I believe you wrote that) [0]. And I
don't think numbers alone are a good
On 11/26/2014 08:55 PM, Don Kehn wrote:
Sure, will try and gen to it over the holiday, do you have a link to
the spec repo?
Hi Don,
Has there been any progress on a DHCP sub-group?
Regards,
Chuck
On Mon, Nov 24, 2014 at 3:27 PM, Carl Baldwin c...@ecbaldwin.net
mailto:c...@ecbaldwin.net
On Fri, Dec 5, 2014 at 6:45 AM, Sean Dague s...@dague.net wrote:
I got bit by another bug yesterday where there was a typo between
variables in the source tree. So I started down the process of set -o
nounset to see how bad it would be to prevent that in the future.
[...]
The trueorfalse
German-- but the point is that sharing apparently has no effect on the
number of permutations for status information. The only difference here is
that without sharing it's more work for the user to maintain and modify
trees of objects.
On Fri, Dec 5, 2014 at 9:36 AM, Eichberger, German
Excerpts from marios's message of 2014-12-04 02:40:23 -0800:
On 04/12/14 11:40, James Polley wrote:
Just taking a look at http://doodle.com/27ffgkdm5gxzr654 again - we've
had 10 people respond so far. The winning time so far is Monday 2100UTC
- 7 yes and one If I have to.
for me it
Excerpts from Steven Hardy's message of 2014-12-04 01:09:18 -0800:
On Wed, Dec 03, 2014 at 06:54:48PM -0800, Clint Byrum wrote:
Excerpts from Dan Prince's message of 2014-12-03 18:35:15 -0800:
On Wed, 2014-12-03 at 10:11 +, Steven Hardy wrote:
Hi all,
Lately I've been
In Juno we effectively disabled live snapshots with libvirt due to bug
1334398 [1] failing the gate about 25% of the time.
I was going through the Juno release notes today and saw this as a known
issue, which reminded me of it and was wondering if there is anything
being done about it?
As I
On 12/05/2014 01:50 PM, Matt Riedemann wrote:
In Juno we effectively disabled live snapshots with libvirt due to bug
1334398 [1] failing the gate about 25% of the time.
I was going through the Juno release notes today and saw this as a known
issue, which reminded me of it and was wondering
Sean Dague wrote:
On 12/04/2014 05:38 PM, Matt Riedemann wrote:
On 12/4/2014 4:06 PM, Michael Still wrote:
+Eric and Ian
On Fri, Dec 5, 2014 at 8:31 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
This came up in the nova meeting today, I've opened a bug [1] for it.
Since
The cells v2 effort is going to be introducing a new database into
Nova. This has been an opportunity to rethink and approach a few things
differently, including how we should handle migrations. There have been
discussions for a long time now about switching over to alembic for
migrations so
On 12/5/2014 1:32 PM, Sean Dague wrote:
On 12/05/2014 01:50 PM, Matt Riedemann wrote:
In Juno we effectively disabled live snapshots with libvirt due to bug
1334398 [1] failing the gate about 25% of the time.
I was going through the Juno release notes today and saw this as a known
issue,
On 12/5/2014 1:45 PM, Andrew Laski wrote:
The cells v2 effort is going to be introducing a new database into
Nova. This has been an opportunity to rethink and approach a few things
differently, including how we should handle migrations. There have been
discussions for a long time now about
On Fri, Dec 05, 2014, Andrew Laski andrew.la...@rackspace.com wrote:
The cells v2 effort is going to be introducing a new database into
Nova. This has been an opportunity to rethink and approach a few
things differently, including how we should handle migrations. There
have been discussions
Le 05/12/2014 21:14, Matt Riedemann a écrit :
On 12/5/2014 1:45 PM, Andrew Laski wrote:
The cells v2 effort is going to be introducing a new database into
Nova. This has been an opportunity to rethink and approach a few things
differently, including how we should handle migrations. There
Hello All,
I am trying to deploy bare-metal nodes using openstack-ironic. It is a 2 -
node architecture with controller/keystone/mysql on a virtual machine, and
cinder/compute/nova network on a physical machine on a CentOS 7 environment.
openstack-ironic-common-2014.2-2.el7.centos.noarch
Hi Lohit,
In the future, please do not cross-post or copy-and-paste usage questions
on the development list. Since you posted this question on the general list
(*) -- which is exactly where you should post it -- I will respond there.
Regards,
Devananda
(*)
On Dec 5, 2014, at 3:14 PM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
On 12/5/2014 1:45 PM, Andrew Laski wrote:
The cells v2 effort is going to be introducing a new database into
Nova. This has been an opportunity to rethink and approach a few things
differently, including how
Hey list -
I’m posting this here just to get some ideas on what might be happening here,
as it may or may not have some impact on Openstack if and when we move to MySQL
drivers that are async-patchable, like MySQL-connector or PyMySQL. I had a
user post this issue a few days ago which I’ve
I apologize. I was not sure about where to post the errors.
I will post to the general list from next time.
Thank you,
Lohit
On Friday, December 5, 2014, Devananda van der Veen devananda@gmail.com
wrote:
Hi Lohit,
In the future, please do not cross-post or copy-and-paste usage
Hi folks,
For a few weeks now the Neutron team has worked tirelessly on [1].
This initiative stems from the fact that as the project matures, evolution
of processes and contribution guidelines need to evolve with it. This is to
ensure that the project can keep on thriving in order to meet the
For anyone who had an interest in following this thread, they might want to
have a look at [1], and [2] (which is the tl;dr version [1]).
HTH
Armando
[1] https://review.openstack.org/#/c/134680
[2]
http://lists.openstack.org/pipermail/openstack-dev/2014-December/052346.html
This is a friendly reminder that our weekly IRC meetings have begun
alternating times every week to try to accommodate more of our contributors.
Next week's meeting will be at 0500 UTC Tuesday (9pm PST Monday) in the
#openstack-meeting-3 channel. Details, as always, are on the wiki [0].
Regards,
1. Alembic release - I worked through some regressions introduced by Alembic
0.7.0 and the subsequent 0.7.1 with the Neutron folks. This started on Monday
with https://review.openstack.org/#/c/137989/, and by Wednesday I had
identified enough small regressions in 0.7.0 that I had to put 0.7.1
this was sent to the wrong list! please ignore. (or if you find it
interesting, then great!)
On Dec 5, 2014, at 6:13 PM, Mike Bayer mba...@redhat.com wrote:
1. Alembic release - I worked through some regressions introduced by Alembic
0.7.0 and the subsequent 0.7.1 with the Neutron
Hello, Davanum,
Thanks for your reply.
Cells can't meet the demand for the use cases and requirements described in the
mail.
1. Use cases
a). Vodafone use case[4](OpenStack summit speech video from 9'02 to 12'30
), establishing globally addressable tenants which result in efficient
Ian Wells ijw.ubu...@cack.org.uk writes:
On 4 December 2014 at 08:00, Neil Jerram neil.jer...@metaswitch.com
wrote:
Kevin Benton blak...@gmail.com writes:
I was actually floating a slightly more radical option than that:
the
idea that there is a VIF type (VIF_TYPE_NOOP) for
Kevin Benton blak...@gmail.com writes:
I see the difference now.
The main concern I see with the NOOP type is that creating the virtual
interface could require different logic for certain hypervisors. In
that case Neutron would now have to know things about nova and to me
it seems like
Hello,
Suppose I have a backend specification in cinder.conf as follows:
[nfs_pradipm]
volume_backend_name=nfs_pradipm
volume_driver=cinder.volume.drivers.netapp.common.NetAppDriver
netapp_server_hostname=IP
netapp_server_port=80
netapp_storage_protocol=nfs
netapp_storage_family=ontap_cluster
I have no problem with standardising the API, and I would suggest that a
service that provided nothing but endpoints could be begun as the next
phase of 'advanced services' broken out projects to standardise that API.
I just don't want it in Neutron itself.
On 5 December 2014 at 00:33, Erik Moe
Hi All,
In the most recent team meeting we briefly discussed: [1] where the
console.log grows indefinitely, eventually causing guest stalls. I mentioned
that I was working on a spec to fix this issue.
My original plan was fairly similar to [2] In that we'd switch libvirt/qemu to
using a
On Fri, Dec 05, 2014 at 02:26:46PM +, Jeremy Stanley wrote:
On 2014-12-04 18:37:48 -0700 (-0700), Carl Baldwin wrote:
+1 I've been meaning to say something like this but never got
around to it. Thanks for speaking up.
https://storyboard.openstack.org/#!/story/1172753
I think Ryan
66 matches
Mail list logo
