There also another bug you can link/duplicate with #1192381 is
https://bugs.launchpad.net/neutron/+bug/1185916.
I proposed a fix but it's not the good way. I abandoned it.
Édouard.
On Wed, Dec 4, 2013 at 10:43 PM, Carl Baldwin wrote:
> I have offered up https://review.openstack.org/#/c/60082/ as
Hi all!
> -Ursprüngliche Nachricht-
> Von: Kenichi Oomichi [mailto:oomi...@mxs.nes.nec.co.jp]
> Gesendet: Donnerstag, 5. Dezember 2013 01:37
> An: OpenStack Development Mailing List (not for usage questions)
> Betreff: Re: [openstack-dev] [qa] Moving the QA meeting time
>
>
> Hi Matthew,
Hi,
I would be happy with this model. Yes, longer term it might be nice to
have an independent certificate store so that when you need to be able
to validate ssl you can, but this is a good intermediate step.
Cheers,
On 02/12/13 09:16, Vijay Venkatachalam wrote:
LBaaS enthusiasts: Your vo
On Dec 4, 2013, at 6:34 PM, Yair Fried wrote:
> Hi
> In tempest.conf, Is the parameter "tenant_networks_reachable" affected by
> anything other than neutron using ip name-spaces (which is the default
> setting) or not, and if not using it - if the tempest host is the same as the
> neutron ser
Hi Morgan!
Stackforge projects can be configured to make the CLA optional. I am willing to
speak to the HTTPretty maintainers about the benefits of stackforge. Do we
happen to know any of them? If not I can track them down through email.
Adrian
--
Adrian
Original message
F
Excerpts from Adrian Otto's message of 2013-12-04 16:53:16 -0800:
> Clint,
>
> On Dec 4, 2013, at 4:06 PM, Clint Byrum
> wrote:
>
> > Excerpts from Adrian Otto's message of 2013-12-04 15:44:45 -0800:
> >> Jamie,
> >>
> >> Thanks for the guidance here. I am checking to see if any of our
> >> d
usly and integrate it with the L3 agent efforts brought by Shixiong
and Randy.
Please see below for Webex recording.
https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=MC&rID=73520027&rKey=8e508b63604bb9d0
IPv6 / Neutron synch-up-20131204 0204-1
Tuesday, December 3, 2013 9:04 p
On 5 December 2013 15:55, Steve Baker wrote:
> Yes, point taken.
>
> heat-core does a reasonable job of keeping up with review load, so there is
> not yet a bottleneck. However the load is taken by a small team which would
> definitely need to grow if we were to take on a new project.
Yup.
> Th
On 12/4/2013 10:16 AM, Nikola Đipanov wrote:
On 11/19/2013 05:52 PM, Peter Feiner wrote:
On Tue, Nov 19, 2013 at 11:19 AM, Chuck Short wrote:
Hi
On Tue, Nov 19, 2013 at 10:43 AM, Peter Feiner wrote:
A substantive reason for switching from mox to mock is the derelict
state of mox release
solutions.
>> 5) We reached consensus to leverage the work Sean, Da Zhao have done
>> previously and integrate it with the L3 agent efforts brought by Shixiong
>> and Randy.
>>
>>
>> Please see below for Webex recording.
>
On Thu, Dec 5, 2013 at 11:06 AM, Kenichi Oomichi
wrote:
>
> Hi Matthew,
>
> Thank you for picking this up.
>
> > -Original Message-
> > From: Matthew Treinish [mailto:mtrein...@kortar.org]
> > Sent: Thursday, December 05, 2013 6:04 AM
> > To: openstack-dev@lists.openstack.org
> > Subject:
On 12/05/2013 02:47 PM, Robert Collins wrote:
> On 5 December 2013 12:34, Tim Schnell wrote:
>> Hi Heaters,
> ...
>
> So, I'm very glad someone is going to work on this; I believe there
> may be use for it in Tuskar too.
>
>> Start Heater as a Stackforge project with a different core team that is
On 2013-12-04 21:44:53 -0500 (-0500), Shixiong Shang wrote:
[...]
> I was swamped today to prepare for the presentation that Randy and
> I jointly delivered tonight to local OpenStack community in the
> meet-up sponsored by Cisco.
[...]
Also, just wanted to congratulate you--the presentation was
e
nt efforts brought by Shixiong and
> Randy.
>
>
> Please see below for Webex recording.
>
> https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=MC&rID=73520027&rKey=8e508b63604bb9d0
>
> IPv6 / Neutron synch-up-20131204
to leverage the work Sean, Da Zhao have done
> previously and integrate it with the L3 agent efforts brought by Shixiong and
> Randy.
>
>
> Please see below for Webex recording.
>
> https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=MC&rID=73520027&rKey=8e508b6
On December 4, 2013 at 18:05:07, Jamie Lennox (jamielen...@redhat.com) wrote:
On Wed, 2013-12-04 at 20:48 -0500, David Stanek wrote:
> On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto
> wrote:
> Jamie,
>
> Thanks for the guidance here. I am checking to see if any of
> our developers might take
On Wed, 2013-12-04 at 20:48 -0500, David Stanek wrote:
> On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto
> wrote:
> Jamie,
>
> Thanks for the guidance here. I am checking to see if any of
> our developers might take an interest in helping with the
> upstream w
On 5 December 2013 03:24, Joe Hakim Rahme wrote:
> I am in favor of class level exceptions for the obvious reasons:
...
> If proper fixtures are meant to replace setUpClass in the future (something I
> would really love to see in Tempest), we still need to take into account that
> setUpClass might
Why not just use glance?
On 12/04/2013 06:34 PM, Tim Schnell wrote:
> Hi Heaters,
>
> We would like to start a dialog on the general direction of the proposed
> Heater project:
> blueprint: https://blueprints.launchpad.net/heat/+spec/heat-template-repo
> wiki: https://wiki.openstack.org/wiki/Heat
Thanks for your suggestion, Brant. And, I experimented multiple
approaches like that in Tempest, annotating testtools.skipIf above
setUp() method can deliver a similar result.
How about this annotation approach, Joe? This approach can meet both
requirements we said, avoiding code duplication
On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto wrote:
> Jamie,
>
> Thanks for the guidance here. I am checking to see if any of our
> developers might take an interest in helping with the upstream work. At the
> very least, it might be nice to have some understanding of how much work
> there is to be
On 5 December 2013 12:34, Tim Schnell wrote:
> Hi Heaters,
...
So, I'm very glad someone is going to work on this; I believe there
may be use for it in Tuskar too.
> Start Heater as a Stackforge project with a different core team that is
> dedicated to actively working on Heater
This would silo
On Wed, Dec 4, 2013 at 6:29 PM, Jamie Lennox wrote:
> Adrian,
>
> The main blocker for the time being with keystoneclient and py3 is our
> use of a library called HTTPretty in our testing - on which there is a
> very recent thread. There is upstream work to make this py3 compatible
> but i'm not
On 12/04/2013 04:34 PM, Tim Schnell wrote:
Hi Heaters,
We would like to start a dialog on the general direction of the
proposed Heater project:
blueprint: https://blueprints.launchpad.net/heat/+spec/heat-template-repo
wiki: https://wiki.openstack.org/wiki/Heat/htr
It is important to us to sta
Adrian,
I had a look a little while ago and I don't *think* it's too bad.
Because it's hooking into sockets and dealing with web requests though
there is a lot of messing with what is unicode vs ascii and the py2 vs
py3 differences.
I'm sure it's doable, but i hate those kind of problems :)
>
On Dec 4, 2013, at 4:06 PM, "Fox, Kevin M"
wrote:
> What is the difference between Heater, Cloudify
> (http://appcatalog.cloudifysource.org/#/?tumblr)
Cloudify is a Java based open source cloud management tool from Gigaspaces.
Cloudify developers are part of the Solum project as well, and are
Hi all,
The [state-management] project team holds a weekly meeting in
#openstack-meeting on thursdays, 2000 UTC. The next meeting is tomorrow,
2013-12-05!!!
As usual, everyone is welcome :-)
Link: https://wiki.openstack.org/wiki/Meetings/StateManagement
Taskflow: https://wiki.openstack.org/Tas
In my experience doing any kind of http request inside a of a db
transaction kills performance vastly (and can lead to situations where
deadlock often occurs due to eventlet+sqlalchemly). This topic also was
recently discussed here:
http://lists.openstack.org/pipermail/openstack-dev/2013-November/0
Clint,
On Dec 4, 2013, at 4:06 PM, Clint Byrum
wrote:
> Excerpts from Adrian Otto's message of 2013-12-04 15:44:45 -0800:
>> Jamie,
>>
>> Thanks for the guidance here. I am checking to see if any of our developers
>> might take an interest in helping with the upstream work. At the very least,
Hi Matthew,
Thank you for picking this up.
> -Original Message-
> From: Matthew Treinish [mailto:mtrein...@kortar.org]
> Sent: Thursday, December 05, 2013 6:04 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [qa] Moving the QA meeting time
>
> Hi everyone,
>
> I'm
What is the difference between Heater, Cloudify
(http://appcatalog.cloudifysource.org/#/?tumblr) and Murano
(https://wiki.openstack.org/wiki/Murano)
If Heater is intended to be a subset of Cloudify/Murano that they both would
use, it might be good to start off like the Solum folks are?
Thanks,
On Wed, 2013-12-04 at 14:59 -0800, Abhishek Chanda wrote:
> I am a new contributor. While poking around, I thought that a standard
> way to print information to stdout is necessary in a number of places.
> Is there a plan to put this into oslo? I could not find any existing
> blueprint on this. I'd
Excerpts from Adrian Otto's message of 2013-12-04 15:44:45 -0800:
> Jamie,
>
> Thanks for the guidance here. I am checking to see if any of our developers
> might take an interest in helping with the upstream work. At the very least,
> it might be nice to have some understanding of how much work
In Keystone, we've got some tests that "raise self.skipTest('...')" in the
test class setUp() method (not setUpClass). My testing shows that if
there's several tests in the class then it shows all of those tests as
skipped (not just 1 skip). Does this do what you want?
Here's an example:
http://gi
Jamie,
Thanks for the guidance here. I am checking to see if any of our developers
might take an interest in helping with the upstream work. At the very least, it
might be nice to have some understanding of how much work there is to be done
in HTTPretty.
Cheers,
Adrian
On Dec 4, 2013, at 3:2
Hi Heaters,
We would like to start a dialog on the general direction of the proposed Heater
project:
blueprint: https://blueprints.launchpad.net/heat/+spec/heat-template-repo
wiki: https://wiki.openstack.org/wiki/Heat/htr
It is important to us to start the discussion early but please note that t
Adrian,
The main blocker for the time being with keystoneclient and py3 is our
use of a library called HTTPretty in our testing - on which there is a
very recent thread. There is upstream work to make this py3 compatible
but i'm not sure how quickly it's moving.
Any code in keystoneclient itsel
On 05/12/13 01:14, Brent Eagles wrote:
> Hi,
>
> As part of the Icehouse nova-networking parity effort, we need to
> describe how nova-networking managers work and how the behavior is
> mapped to neutron. The benefits are:
>
> 1. It aides migration: deployers who are nova-network savvy can see ho
Gregory and Ben,
Awesome, thanks!!
Adrian
On Dec 4, 2013, at 2:01 PM, Georgy Okrokvertskhov
mailto:gokrokvertsk...@mirantis.com>>
wrote:
I opened a bug https://bugs.launchpad.net/solum/+bug/1257929 for that issue.
Ben, thank you for a quick fix proposal.
Thanks
Georgy
On Wed, Dec 4, 2013
Boris,
On Dec 4, 2013, at 2:53 PM, Boris Pavlovic
mailto:bpavlo...@mirantis.com>>
wrote:
All,
Thank you guys for your opinion.
As a conclusion of this thread, I think that I shouldn't hesitate to raise all
discussion about Rally in mailing list also.. Right?
Yes, if your team feels that it
> As a developer think about the fact that when you log something as
> ERROR, you are expecting a cloud operator to be woken up in the middle
> of the night with an email alert to go fix the cloud immediately. You
> are intentionally ruining someone's weekend to fix this issue - RIGHT
NOW!
was go
Hi all,
I am a new contributor. While poking around, I thought that a standard way
to print information to stdout is necessary in a number of places. Is there
a plan to put this into oslo? I could not find any existing blueprint on
this. I'd be happy to take care of this.
Thanks
_
All,
Thank you guys for your opinion.
As a conclusion of this thread, I think that I shouldn't hesitate to raise
all discussion about Rally in mailing list also.. Right?
Best regards,
Boris Pavlovic
On Thu, Dec 5, 2013 at 2:42 AM, Robert Collins wrote:
> On 5 December 2013 11:39, Boris Pavl
On 20 November 2013 00:22, Robert Collins wrote:
> On 20 November 2013 13:00, Sean Dague wrote:
> > So we recently moved devstack gate to do con fig drive instead of
> metadata
> > service, and life was good (no one really noticed). In what ways is
> > configdrive insufficient compared to metada
On 5 December 2013 11:39, Boris Pavlovic wrote:
> Russell,
>
> Actually what I said is not only related to Solumn or any other project.
>
> Main "idea" of it was that, well structured etherpads are much better
> instrument for such discussions.
>
> Do you disagree with this also?
I disagree with
Russell,
Actually what I said is not only related to Solumn or any other project.
Main "idea" of it was that, well structured etherpads are much better
instrument for such discussions.
Do you disagree with this also?
Best regards,
Boris Pavlovic
On Thu, Dec 5, 2013 at 2:12 AM, Russell Bryant
Boris,
Thanks for expressing your concern about this. For those reading the Solum
topic on this list, we really want this to be a community building resource
were we are free to discuss ideas and as a primary mechanism for gauging
consensus. Applying restrictions to how the list is used by proj
This is a follow up to https://review.openstack.org/59621 to get
broader discussion..
So at the moment we capture a bunch of details in the image - what
parameters the image was built with and some environment variables.
Last week we were capturing everything, which there is broad consensus
was t
On Wednesday, December 4, 2013, Flavio Percoco wrote:
> On 04/12/13 01:13 +, Adrian Otto wrote:
>
>> Jay is right. What we have is probably close enough to what's in Nova to
>> qualify for oslo-incubator. The simplifications seem to me to have general
>> appeal so this code would be more attra
On 12/04/2013 05:07 PM, Boris Pavlovic wrote:
> Guys,
>
> I really appreciate that all discussion are real open, and you are doing
> a great job, discussing all arch stuff of the project. But for such
> things there are:
> 1) IRC chats
> 2) WIKI pages
> 3) ehterpads
>
> E.g. in Rally we have 1
Guys,
I really appreciate that all discussion are real open, and you are doing a
great job, discussing all arch stuff of the project. But for such things
there are:
1) IRC chats
2) WIKI pages
3) ehterpads
E.g. in Rally we have 1 page:
https://etherpad.openstack.org/p/Rally_Main that contains all
I opened a bug https://bugs.launchpad.net/solum/+bug/1257929 for that issue.
Ben, thank you for a quick fix proposal.
Thanks
Georgy
On Wed, Dec 4, 2013 at 1:41 PM, Ben Nemec wrote:
> I don't think so. It looks like ./solum/api/controllers/v1/assembly.py
> is calling unicode(). It will need
I don't think so. It looks like ./solum/api/controllers/v1/assembly.py
is calling unicode(). It will need to be changed to six.text_type() for
Python 3 compat.
-Ben
On 2013-12-04 15:41, Adrian Otto wrote:
> Am I interpreting this to mean that WSME is calling unicode()?
>
> On Dec 4, 2013
Matt,
2200 UTC Wed. or Thurs. is fine with me
Cheers
On Wed, Dec 4, 2013 at 3:04 PM, Matthew Treinish wrote:
> Hi everyone,
>
> I'm looking at changing our weekly QA meeting time to make it more globally
> attendable. Right now the current time of 17:00 UTC doesn't really work for
> people who
No,
This is Solum code:
https://github.com/stackforge/solum/blob/master/solum/api/controllers/v1/assembly.py#L59
Thanks
Georgy
On Wed, Dec 4, 2013 at 1:41 PM, Adrian Otto wrote:
> Am I interpreting this to mean that WSME is calling unicode()?
>
> On Dec 4, 2013, at 1:32 PM, Georgy Okrokverts
I have offered up https://review.openstack.org/#/c/60082/ as a
backport to Havana. Interest was expressed in the blueprint for doing
this even before this thread. If there is consensus for this as the
stop-gap then it is there for the merging. However, I do not want to
discourage discussion of o
Am I interpreting this to mean that WSME is calling unicode()?
On Dec 4, 2013, at 1:32 PM, Georgy Okrokvertskhov
mailto:gokrokvertsk...@mirantis.com>>
wrote:
Hi,
I am working on unit tests for Solum as a side effect of new unit tests I found
that we use unicode strings in the way which is not
- Original Message -
> With the comments that we've received, I would recommend that Clayton
> remove the option to select the MySQL storage engine from Oslo config and
> just "hardcode" InnoDB. I believe it entails just removing a few lines of
> code. It doesn't sound like anyone has a r
Sorry to have taken the discussion on a slight tangent. I meant only
to offer the solution as a stop-gap. I agree that the fundamental
problem should still be addressed.
On Tue, Dec 3, 2013 at 8:01 PM, Maru Newby wrote:
>
> On Dec 4, 2013, at 1:47 AM, Stephen Gran wrote:
>
>> On 03/12/13 16:08
Hi,
I am working on unit tests for Solum as a side effect of new unit tests I
found that we use unicode strings in the way which is not compatible with
python3.
Here is an exception form python3 gate:
Server-side error: "global name 'unicode' is not defined". Detail:
2013-12-04 Traceback (most re
With the comments that we've received, I would recommend that Clayton
remove the option to select the MySQL storage engine from Oslo config and
just "hardcode" InnoDB. I believe it entails just removing a few lines of
code. It doesn't sound like anyone has a reason to use any other storage
engine
On 12/4/13 3:06 PM, "Adrian Otto" wrote:
>
>On Dec 4, 2013, at 12:32 PM, Monty Taylor wrote:
>
>> On 12/04/2013 03:25 PM, Clint Byrum wrote:
>>> Excerpts from Paul Montgomery's message of 2013-12-04 12:04:06 -0800:
TLDR: Should Solum log a warning if operators do not use the InnoDB
s
Hi everyone,
I'm looking at changing our weekly QA meeting time to make it more globally
attendable. Right now the current time of 17:00 UTC doesn't really work for
people who live in Asia Pacific timezones. (which includes a third of the
current core review team) There are 2 approaches that I can
On Dec 4, 2013, at 12:32 PM, Monty Taylor wrote:
> On 12/04/2013 03:25 PM, Clint Byrum wrote:
>> Excerpts from Paul Montgomery's message of 2013-12-04 12:04:06 -0800:
>>> TLDR: Should Solum log a warning if operators do not use the InnoDB
>>> storage engine with MySQL in Solum's control plane?
>
Looks like there's some recent progress here:
https://github.com/gabrielfalcao/HTTPretty/pull/124
On Wed, Nov 20, 2013 at 9:30 PM, Morgan Fainberg wrote:
> I'd be more willing to toss in and help to maintain/fix appropriately
> on StackForge if that is needed. Though I am very much hoping
>
On 12/04/2013 12:40 PM, David Chadwick wrote:
Hi Adam
I understand your problem: having projects and services which have the
same name, then the lineage of a role containing this name is not
deterministically known without some other rule or syntax that can
differentiate between the two.
Since
Dolph,
Is anyone already focusing on py33 compatibility for python-keystoneclient? Has
that effort been scoped? I'd like to judge whether it's reasonable to expect us
to patch it up to be compatible in the near term, or relax our expectations.
For Solum, we are trying to make all our code py33
For people who's patches got killed earlier today because django 1.6 was
allowed into global requirements, please use the following bug for
recheck - https://bugs.launchpad.net/horizon/+bug/1257885
The horizon team is working towards 1.6 compatibility, but it's not
there yet. This will be a good t
On 12/04/2013 03:25 PM, Clint Byrum wrote:
> Excerpts from Paul Montgomery's message of 2013-12-04 12:04:06 -0800:
>> TLDR: Should Solum log a warning if operators do not use the InnoDB
>> storage engine with MySQL in Solum's control plane?
>>
>>
>> Details:
>>
>> I was looking at: https://review
On Wed, Dec 4, 2013 at 1:26 PM, Georgy Okrokvertskhov <
gokrokvertsk...@mirantis.com> wrote:
> Hi,
>
> I have failed tests in gate-solum-python33 because kesytoneclient fails to
> import xmlrpclib.
> The exact error is:
> "File
> "/home/jenkins/workspace/gate-solum-python33/.tox/py33/lib/python3.3
Excerpts from Paul Montgomery's message of 2013-12-04 12:04:06 -0800:
> TLDR: Should Solum log a warning if operators do not use the InnoDB
> storage engine with MySQL in Solum's control plane?
>
>
> Details:
>
> I was looking at: https://review.openstack.org/#/c/57024/
> Models.py to be specifi
On Dec 4, 2013, at 2:44 PM, Lyle, David wrote:
> On 5 December 2013 12:10, Robert Collins wrote:
>
> -snip-
>
>>
>> That said, perhaps we should review these projects.
>>
>> Tuskar as an API to drive deployment and ops clearly belongs in
>> TripleO - though we need to keep pushing features ou
- Original Message -
> TLDR: Should Solum log a warning if operators do not use the InnoDB
> storage engine with MySQL in Solum's control plane?
>
>
> Details:
>
> I was looking at: https://review.openstack.org/#/c/57024/
> Models.py to be specific.
>
> The default storage engine is I
Hi Eugene,
Right now (before the model change discussed during the summit) our
implementation, in regards to your question, can be summarized as follows:
- Whenever a Pool is created, a port on the specific subnet/network is
created and associated to it;
- Whenever a VIP is
TLDR: Should Solum log a warning if operators do not use the InnoDB
storage engine with MySQL in Solum's control plane?
Details:
I was looking at: https://review.openstack.org/#/c/57024/
Models.py to be specific.
The default storage engine is InnoDB for MySQL which is good. I took a
quick look
Excerpts from Sean Dague's message of 2013-12-04 10:51:16 -0800:
> On 12/04/2013 11:56 AM, Ben Nemec wrote:
> > On 2013-12-04 06:07, Sean Dague wrote:
> >> On 12/03/2013 11:21 PM, Clint Byrum wrote:
> >>> Excerpts from Sean Dague's message of 2013-12-03 16:05:47 -0800:
> On 12/03/2013 06:13 PM
Thanks David,
Appended line # 119 with my reply. "endpoint" sounds perfect to me.
In a nutshell we are agreeing on following new data model for role-def.
{
"role": {
"id": "76e72a",
"name": "admin", (you can give whatever name you like)
"scope": {
"id": "---id--", (ID should
On 5 December 2013 12:10, Robert Collins wrote:
-snip-
>
> That said, perhaps we should review these projects.
>
> Tuskar as an API to drive deployment and ops clearly belongs in
> TripleO - though we need to keep pushing features out of it into more
> generalised tools like Heat, Nova and Sol
Hi,
I have failed tests in gate-solum-python33 because kesytoneclient fails to
import xmlrpclib.
The exact error is:
"File
"/home/jenkins/workspace/gate-solum-python33/.tox/py33/lib/python3.3/site-packages/
keystoneclient/openstack/common/jsonutils.py", line 42, in
2013-11-28 18:27:12.655 | i
On 2013-12-04 12:51, Sean Dague wrote:
On 12/04/2013 11:56 AM, Ben Nemec wrote:
On 2013-12-04 06:07, Sean Dague wrote:
On 12/03/2013 11:21 PM, Clint Byrum wrote:
Excerpts from Sean Dague's message of 2013-12-03 16:05:47 -0800:
On 12/03/2013 06:13 PM, Ben Nemec wrote:
On 2013-12-03 17:09, Sea
On 5 December 2013 06:55, James Slagle wrote:
> On Wed, Dec 4, 2013 at 2:12 AM, Robert Collins
>> Jan, Jordan, Martyn, Jiri and Jaromir are still actively contributing
>> to TripleO and OpenStack, but I don't think they are tracking /
>> engaging in the code review discussions enough to stay in -c
Hi David,
The biggest problems in my opinion are,
1. We are overloading and adding extra complexities on role name to maintain
the generalization for role-def data model.
2. Name spacing the role name is not going to resolve all the issues listed in
BP.
3. All the namespaces are derived from
On Dec 3, 2013, at 9:30 AM, Tzu-Mainn Chen wrote:
> Hey folks,
>
> I opened 2 issues on UX discussion forum with TripleO UI topics:
>
> Resource Management:
> http://ask-openstackux.rhcloud.com/question/95/tripleo-ui-resource-management/
> - this section was already reviewed before, there is n
On 12/04/2013 11:56 AM, Ben Nemec wrote:
> On 2013-12-04 06:07, Sean Dague wrote:
>> On 12/03/2013 11:21 PM, Clint Byrum wrote:
>>> Excerpts from Sean Dague's message of 2013-12-03 16:05:47 -0800:
On 12/03/2013 06:13 PM, Ben Nemec wrote:
> On 2013-12-03 17:09, Sean Dague wrote:
>> On 1
On 04/12/2013 17:28, Tiwari, Arvind wrote:
> Hi David,
>
> Thanks for your valuable comments.
>
> I have updated
> https://etherpad.openstack.org/p/service-scoped-role-definition line
> #118 explaining the rationale behind the field.
#119 for my reply
>
> I wd also appreciate your thoughts o
On Wed, Dec 4, 2013 at 11:16 AM, Nikola Đipanov wrote:
> On 11/19/2013 05:52 PM, Peter Feiner wrote:
> > On Tue, Nov 19, 2013 at 11:19 AM, Chuck Short
> wrote:
> >> Hi
> >>
> >>
> >> On Tue, Nov 19, 2013 at 10:43 AM, Peter Feiner
> wrote:
> >>>
> >>> A substantive reason for switching from mox
On Wed, Dec 4, 2013 at 2:12 AM, Robert Collins
wrote:
> In this months review:
> - Ghe Rivero for -core
+1. Has been doing very good reviews.
> - Jan Provaznik for removal from -core
> - Jordan O'Mara for removal from -core
> - Martyn Taylor for removal from -core
> - Jiri Tomasek for remo
On 12/04/2013 06:15 PM, Peter Feiner wrote:
> On Wed, Dec 4, 2013 at 11:16 AM, Nikola Đipanov wrote:
>> 1) Figure out what is the deal with mox3 and decide if owning it will
>> really be less trouble than porting nova. To be hones - I was unable to
>> even find the code repo for it, only [3]. If a
Hi Adam
I understand your problem: having projects and services which have the
same name, then the lineage of a role containing this name is not
deterministically known without some other rule or syntax that can
differentiate between the two.
Since domains contain projects which contain services
On 4 Dec 2013, at 13:28, Dolph Mathews wrote:
>
> On Sun, Nov 24, 2013 at 9:39 PM, Adam Young wrote:
> The #1 pain point I hear from people in the field is that they need to
> consume read only LDAP but have service users in something Keystone
> specific. We are close to having this, but w
Hi David,
Thanks for your valuable comments.
I have updated https://etherpad.openstack.org/p/service-scoped-role-definition
line #118 explaining the rationale behind the field.
I wd also appreciate your thoughts on
https://etherpad.openstack.org/p/1Uiwcbfpxq too, which is support
https://bl
Hi Adam,
I have added my comments in line.
As per my request yesterday and David's proposal, following role-def data model
is looks generic enough and seems innovative to accommodate future extensions.
{
"role": {
"id": "76e72a",
"name": "admin", (you can give whatever name you like)
Have a question regarding calling an external SDN controller in a plugin.
The ML2 model brings up the fact that it is preferred not to call an
external controller within a database session by splitting up each call
into two calls: *_precommit and *_postcommit. Makes sense.
Looking at the existin
On Wed, Dec 4, 2013 at 11:16 AM, Nikola Đipanov wrote:
> 1) Figure out what is the deal with mox3 and decide if owning it will
> really be less trouble than porting nova. To be hones - I was unable to
> even find the code repo for it, only [3]. If anyone has more info -
> please weigh in. We'll al
On 12/04/2013 11:16 AM, Nikola Đipanov wrote:
> Resurrecting this thread because of an interesting review that came up
> yesterday [1].
>
> It seems that our lack of a firm decision on what to do with the mocking
> framework has left people confused. In hope to help - I'll give my view
> of where
On 2013-12-04 06:07, Sean Dague wrote:
On 12/03/2013 11:21 PM, Clint Byrum wrote:
Excerpts from Sean Dague's message of 2013-12-03 16:05:47 -0800:
On 12/03/2013 06:13 PM, Ben Nemec wrote:
On 2013-12-03 17:09, Sean Dague wrote:
On 12/03/2013 05:50 PM, Mark McLoughlin wrote:
On Tue, 2013-12-03
On 12/04/2013 11:58 AM, Digambar Patil wrote:
> Hi Russell,
>
>Thank you for your inputs on launchpad. Can you tell me what is
> exactly expected in-terms of design detail, so I can ensure that I send
> you the correct details in the first go itself.
It looked like you described a schedul
Hi Russell,
Thank you for your inputs on launchpad. Can you tell me what is
exactly expected in-terms of design detail, so I can ensure that I send you
the correct details in the first go itself.
Best Regards,
Digambar
___
OpenStack-dev mailing l
On 12/04/2013 11:32 AM, Joe Hakim Rahme wrote:
> On 04 Dec 2013, at 17:05, Sean Dague wrote:
>> That will require someone signing up to writing that though.
>
> I could do that.
>
> Since you know the code better than me, can you confirm that
> tempest/test.py is the best place to define this d
How frequent do you imagine these notifications being? There's a wide
variation here between the 'blue moon' case where disk space is low and
frequent notifications of things like OS performance, which you might want
to display in Horizon or another monitoring tool on an every-few-seconds
basis, o
1 - 100 of 150 matches
Mail list logo
