Hi all,
While requesting a openstack/designate-dashboard project from the TC/
Infra - The topic of why Designate panels, as an incubated project, can't
be merged into openstack/horizon was raised.
In the openstack/governance review[1], Russell asked:
Hm, I think we should discuss this with
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: 09 September 2014 15:13
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack]
Supporting code for incubated projects
On 09/09/2014 07:58 AM, Mac Innes, Kiall
Hi all,
I'd like to announce my candidacy for the DNS Services Program PTL position.
I've been involved in Designate since day one, as the both original author and
as pseudo-PTL pre-incubation. Designate and the DNS Services program have come
a long way since the project was first introduced
Hi Rich - Welcome!
We're mostly all on the #openstack-dns IRC channel, drop by and say
hello ;)
Thanks,
Kiall
On Wed, 2014-01-15 at 18:24 -0700, Rich Megginson wrote:
Hello. My name is Rich Megginson. I am a Red Hat employee interested
in working on Designate (DNSaaS), primarily in the
On Fri, 2014-03-14 at 08:44 +, Yuzhou (C) wrote:
Hi stackers,
Are there any plans about DNSaaS on the neutron roadmap?
As far as I known, Designate provides DNSaaS services for
OpenStack.
Why DNSaaS is Independent service , not a network service like LBaas
or
On Sat, 2014-05-24 at 17:24 +, Hayes, Graham wrote:
Hi all,
Designate would like to apply for incubation status in OpenStack.
Our application is here:
https://wiki.openstack.org/wiki/Designate/Incubation_Application
As part of our application we would like to apply for a new
On Thu, 2014-06-12 at 11:36 -0400, Sean Dague wrote:
If someone can point me to a case where we've actually found this kind
of bug with tempest / devstack, that would be great. I've just *never*
seen it. I was the one that did most of the fixing for pg support in
Nova, and have helped other
Yep - I know I'll join in :)
Thanks,
Kiall
On Tue, 2014-04-29 at 14:09 -0600, Carl Baldwin wrote:
The design summit discussion topic I submitted [1] for my DNS
blueprints [2][3][4] and this one [5] just missed the cut for the
design session schedule. It stung a little to be turned down but I
On Tue, 2014-05-27 at 17:42 -0700, Joe Gordon wrote:
On Sat, May 24, 2014 at 10:24 AM, Hayes, Graham graham.ha...@hp.com
wrote:
* You mention nova's dns capabilities as not being adequate one of the
incubation requirements is:
Project should not inadvertently duplicate functionality
On Thu, 2014-05-29 at 11:26 +0200, Thierry Carrez wrote:
Back to the topic, the tension here is because DNS is seen as a
network thing and therefore it sounds like it makes sense under
Networking. But programs are not categories or themes. They are
teams aligned on a mission statement. If the
On Thu, 2014-05-29 at 08:00 +0930, Michael Davies wrote:
On Thu, May 29, 2014 at 4:22 AM, Sean Dague s...@dague.net wrote:
I would agree this doesn't make sense in Neutron.
I do wonder if it makes sense in the Network program. I'm getting
suspicious of the programs for projects model if
Several of the TC requested we have an openstack-infra managed DevStack
gate enabled before they would cast their vote - I'm happy to say, we've
got it :)
With the merge of [1], Designate now has voting devstack /
requirements / docs jobs. An example of the DevStack run is at [2].
Vote Designate
On Mon, 2014-06-09 at 07:25 -0400, Sean Dague wrote:
On 06/06/2014 12:06 PM, Mac Innes, Kiall wrote:
Several of the TC requested we have an openstack-infra managed DevStack
gate enabled before they would cast their vote - I'm happy to say, we've
got it :)
With the merge of [1
If you have a recent version of kombu, and amqp[1] rather than amqplib
installed, things will just start using AMQP 0.9.1.
Ubuntu doesn't package a new enough Kombu, and they don't package amqp
at all.. Not sure about other distro's.
Thanks,
Kiall
[1]: https://pypi.python.org/pypi/amqp
On
On 17/07/13 19:51, Matthew Treinish wrote:
I think that setting a requirement of =1.3.0 is fine it should get us
around this.
Watch out! There was a mis-release of 2.0 under the version 1.4.0. The
OpenStack mirror still has this release, ever after it was pulled from pypi.
On 05/08/13 16:09, John Garbutt wrote:
On 5 August 2013 15:15, Anne Gentleannegen...@justwriteclick.com wrote:
On Mon, Aug 5, 2013 at 8:55 AM, John Garbuttj...@johngarbutt.com wrote:
Given we seem to be leaning towards WSME:
On 06/08/13 21:56, Jonathan LaCour wrote:
James Slagle james.sla...@gmail.com wrote:
WSME + pecan is being used in Tuskar:
https://github.com/tuskar/tuskar (OpenStack management API)
We encountered the same issue discussed here. A solution we settled
on for now was to use a custom Renderer
So, Are we saying that UIs built on OpenStack APIs shouldn't be able to
show traditional pagination controls? Or am I missing how this should
work with marker/limit?
e.g. for 11 pages of content, something like: 1 2 3 .. 10 11
Thanks,
Kiall
On 13/08/13 22:45, Jay Pipes wrote:
On 08/13/2013
On 21/08/13 16:07, Doug Hellmann wrote:
IIUC, git sub-modules point to a specific revision of the external
repository,
right? So would projects still have to explicitly update to newer versions of
the incubator code by changing that sub-module reference?
Normally - Yes.
With Gerrit -
On 21/08/13 19:48, Boris Pavlovic wrote:
So why submodules are terrible and oslo-sync is good?=)
I think the biggest mistake people make with submodules, which oslo's
sync avoids, is dropping commits / Going backwards / Switching
branches on submodule - or worse - pointing at a detached commit.
20 matches
Mail list logo
