On Feb 6, 2014, at 11:07 PM, Joshua Harlow wrote:
> +1
>
> To give an example as to why eventlet implicit monkey patch the world isn't
> especially great (although it's what we are currently using throughout
> openstack).
>
> The way I think about how it works is to think about what librarie
Thanks to work by several colleagues, I can share a non-trivial Heat
template for a system that we have been using as an example to work. It
is in the TAR archive here:
https://drive.google.com/file/d/0BypF9OutGsW3Z2JqVTcxaW1BeXc/edit?usp=sharing
Start at connections.yaml. Also in the archive
+1
To give an example as to why eventlet implicit monkey patch the world isn't
especially great (although it's what we are currently using throughout
openstack).
The way I think about how it works is to think about what libraries that a
single piece of code calls and how it is very hard to pre
hello,
I made http://www.xrefs.info available to open source community in
the hope of make open source developers more productive.
The site hosts many open source code projects' cross references based
on OpenGrok,
which is a very fast cross reference tool, and easy to use.
OpenStack is a big open
Hi Alex,
> -Original Message-
> From: Alex Glikson [mailto:glik...@il.ibm.com]
> Sent: Monday, February 03, 2014 7:01 PM
> To: OpenStack Development Mailing List (not for usage questions); Oomichi,
> Kenichi
> Subject: Re: [openstack-dev] [Nova] bp: nova-ecu-support
>
> Similar capabili
On 02/06/2014 05:18 AM, Florent Flament wrote:
Vish:
+1 for hierchical IDs (e.g:
b04f9ea01a9944ac903526885a2666de.c45674c5c2c6463dad3c0cb9d7b8a6d8)
Please keep names and identifiers separate. Identifiers should *NOT* be
hierarchical. Names can be.
Think of the operating system distinction
Dolph Mathews writes:
> On Thu, Feb 6, 2014 at 6:38 AM, Noorul Islam Kamal Malmiyoda <
> noo...@noorul.com> wrote:
>
>> Hello stackers,
>>
>> We have a database with tables users, projects, roles, etc. Is there
>> any reference implementation or best practices to make keystone use
>> this DB inst
On 06/02/14 13:22, Joshua Harlow wrote:
Has there been any investigation into heat.
Heat has already used parts of the coroutine approach (for better or
worse).
An example:
https://github.com/openstack/heat/blob/master/heat/engine/scheduler.py#L230
"""
Decorator for a task that needs to d
On Thu, Feb 6, 2014 at 1:19 AM, Clint Byrum wrote:
> Excerpts from Mike Spreitzer's message of 2014-02-05 22:17:50 -0800:
> > > From: Prasad Vellanki
> > > To: "OpenStack Development Mailing List (not for usage questions)"
> > > ,
> > > Date: 01/21/2014 02:16 AM
> > > Subject: Re: [openstack-dev
Hi Doug,
> -Original Message-
> From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com]
> Sent: Thursday, February 06, 2014 11:55 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] WSME 0.6 released
>
> I have just tagged WSME 0.6. It is now on PyPI, and should be pi
On 04/02/14 13:53, Kevin Conway wrote:
On 2/4/14 12:07 PM, "victor stinner" wrote:
>The purpose of replacing eventlet with asyncio is to get a well defined
>control flow, no more surprising task switching at random points.
I disagree with this. Eventlet and gevent yield the execution context
Hi Chris,
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Friday, February 07, 2014 8:53 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] RFC: Generate API sample files from API
> schemas
>
> On Thu, 6 Feb 2014 13:38:22 +0
Shawn,
We are waiting on this infra review to pass - to create the
oslo.vmware git repo.
https://review.openstack.org/#/c/70761/
-- dims
On Thu, Feb 6, 2014 at 5:23 PM, Shawn Hartsock wrote:
> Hi folks,
>
> Just following up on what we were talking about in IRC.
>
> The BP:
> https://blueprint
Hi Jay,
Thanks for bringing this up. I have been trying to make the recheck work
and have not had much success. Therefore, I agree that we should go with
option a) for the short term until b) or c) becomes available.
I would prefer b) because we have already invested a lot in our solution
and it i
On Thu, 6 Feb 2014 13:38:22 +
Kenichi Oomichi wrote:
>
> Hi,
>
> I'd like to propose one idea that autogenerates API sample files from
> API schema for Nova v3 API.
>
> We are working on API validation for v3 API, the works require API
> schema which is defined with JSONSchema for each API
+1
Really lots more than just +1
This leads to so many more efficiencies and increase in effectiveness.
--Rocky
-Original Message-
From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]
Sent: Thursday, February 06, 2014 10:17 AM
To: OpenStack Development Mailing List (not for usage qu
Hello Folks,
We are running into a situation where we are not able to create multiple
provider networks with the same VLAN id. We would like to propose a
solution to remove this restriction through a configuration option. This
approach would not conflict with the present behavior where it is not
p
Hi all,
Taskflow 0.1.3 we released today (0.2.0 to arrive soon).
It was a minor patch release to help fix the unicode/str() issue we
discovered in cinder.
It also includes a few other changes around testing, comments, utility
functions and zookeeper backends.
Full git changes:
$ git log --form
Hi,
During our last meeting, there was an action item to share the Devstack
configuration that we have in the lab. Anthony Veiga, Paul Richie,
and other members of the infrastructure team did the majority of
the work involved in setting up the lab, while I was given the easier
task of just modifyi
+1 lots of respect for zane in doing this :)
I'm still very much interested in seeing how we can connect taskflow in to
your model.
I think the features that you guys were wanting (remote workers) are
showing up and hopefully will be all they can be!
It helps (imho) that taskflow doesn't connect
Hi folks,
Just following up on what we were talking about in IRC.
The BP:
https://blueprints.launchpad.net/nova/+spec/vmware-soap-session-management
Is supposed to capture some of this work/discussion. Earlier in
Icehouse we had thought that having some kind of pseudo transaction
that could enc
On Thu, Feb 6, 2014 at 3:24 PM, Renat Akhmerov wrote:
> Doug, is it backwards compatible with 0.5b6?
>
Yes, it should be. If you find otherwise, let me know so we can address
the problem.
Doug
>
> Renat Akhmerov
> @ Mirantis Inc.
>
> On 06 Feb 2014, at 07:58, Doug Hellmann
> wrote:
>
>
>
>
>
On Thu, Feb 6, 2014 at 6:38 AM, Noorul Islam Kamal Malmiyoda <
noo...@noorul.com> wrote:
> Hello stackers,
>
> We have a database with tables users, projects, roles, etc. Is there
> any reference implementation or best practices to make keystone use
> this DB instead of its own?
>
What's the prob
During the design of HA deployments for Neutron, I have found
that agent's could run into problems, and they keep running,
but they have no methods to expose status to parent process
or which could be queried via an init.d script.
So I'm proposing this blueprint,
https://blueprints.launchpad.n
Hello, Kevin.
On Fri, Feb 7, 2014 at 12:32 AM, Kevin Conway wrote:
> There's an incredibly valid reason why we use green thread abstractions
> like eventlet and gevent in Python. The CPython implementation is
> inherently single threaded so we need some other form of concurrency to get
> the most
On Feb 6, 2014, at 2:32 PM, Kevin Conway wrote:
> There's an incredibly valid reason why we use green thread abstractions like
> eventlet and gevent in Python. The CPython implementation is inherently
> single threaded so we need some other form of concurrency to get the most
> effective use
Hello,
Currently, there is a blueprint for creating a Domain in New Quota Driver
who is waiting approval, but that is already implemented. I believe that is
worth checking out.
https://blueprints.launchpad.net/nova/+spec/domain-quota-driver
Any questions I am available.
Regards,
Raildo Mascena
All due respect to Zane who created the scheduler. We simply could not
do what we do without it (and I think one of the first things I asked
for was parallel create ;).
IMO it is the single most confusing thing in Heat whenever one has to
deal with it. If we could stick to a threading model instea
There's an incredibly valid reason why we use green thread abstractions
like eventlet and gevent in Python. The CPython implementation is
inherently single threaded so we need some other form of concurrency to get
the most effective use out of our code. You can "import threading" all you
want but i
Doug, is it backwards compatible with 0.5b6?
Renat Akhmerov
@ Mirantis Inc.
On 06 Feb 2014, at 07:58, Doug Hellmann wrote:
>
>
>
> On Thu, Feb 6, 2014 at 10:11 AM, Sylvain Bauza
> wrote:
> Thanks Doug,
>
>
>
>
> 2014-02-06 15:54 GMT+01:00 Doug Hellmann :
>
> cdf74daac2a204d5fe77f4b2bf
I guess it should be but just in case…
Renat Akhmerov
@ Mirantis Inc.
On 06 Feb 2014, at 07:58, Doug Hellmann wrote:
>
>
>
> On Thu, Feb 6, 2014 at 10:11 AM, Sylvain Bauza
> wrote:
> Thanks Doug,
>
>
>
>
> 2014-02-06 15:54 GMT+01:00 Doug Hellmann :
>
> cdf74daac2a204d5fe77f4b2bf5a956f
On 02/06/2014 12:07 PM, Stefano Maffulli wrote:
> Hello folks,
>
> we're ready to import the answers from Launchpad into Ask OpenStack. A
> script will import all questions, answers, comments (and data abou user
> accounts) from LP into Ask, tag them as the project of origin (nova,
> swift, etc).
On Thu, Feb 6, 2014 at 10:34 PM, Joshua Harlow wrote:
> Its a good question, I see openstack as mostly like the following 2
> groups of applications.
>
> Group 1:
>
> API entrypoints using [apache/nginx]+wsgi (nova-api, glance-api…)
>
> In this group we can just let the underlying framework/ap
Hi, guys:
I looked briefly at a bug/fix, which looks exceedingly strange to me:
https://review.openstack.org/59689
As much as I can tell, the problem (lp:1238604) is that pending delete
fails because by the time the delete actually occurs, Glance API does
not have proper permissions to talk to G
Hi alex,
I think u are referring to the following:
https://blueprints.launchpad.net/nova/+spec/glance-snapshot-tasks
Can u describe the #2 part in more detail. Do some of the drivers already
implement these new steps?
The goal I think u are having is to make the snapshot functionality resume
Its a good question, I see openstack as mostly like the following 2 groups of
applications.
Group 1:
API entrypoints using [apache/nginx]+wsgi (nova-api, glance-api…)
In this group we can just let the underlying framework/app deal with the
scaling and just use native wsgi as it was intended. S
Has there been any investigation into heat.
Heat has already used parts of the coroutine approach (for better or
worse).
An example:
https://github.com/openstack/heat/blob/master/heat/engine/scheduler.py#L230
"""
Decorator for a task that needs to drive a subtask.
This is essentially a
On Feb 6, 2014, at 5:38 AM, Kenichi Oomichi wrote:
>
> Hi,
>
> I'd like to propose one idea that autogenerates API sample files from API
> schema for Nova v3 API.
>
> We are working on API validation for v3 API, the works require API schema
> which is defined with JSONSchema for each API. On
Hello.
On Tue, Feb 4, 2014 at 5:38 PM, victor stinner
wrote:
> I would like to replace eventlet with asyncio in OpenStack for the
> asynchronous programming. The new asyncio module has a better design and is
> less "magical". It is now part of python 3.4 arguably becoming the de-facto
> standard
On 02/06/2014 02:19 AM, Clint Byrum wrote:
Excerpts from Mike Spreitzer's message of 2014-02-05 22:17:50 -0800:
From: Prasad Vellanki
To: "OpenStack Development Mailing List (not for usage questions)"
,
Date: 01/21/2014 02:16 AM
Subject: Re: [openstack-dev] [heat] Sofware Config progress
Steve
Daniel,
Couple questions.
So what happens if/when the volume is different on the nodes in the
replication cluster? If you need to resize the volume larger to handle more
data are you required to resize all the nodes individually? It makes sense
that maybe all the instances could have a different
On 02/06/2014 10:07 AM, Stefano Maffulli wrote:
Hello folks,
we're ready to import the answers from Launchpad into Ask OpenStack. A
script will import all questions, answers, comments (and data abou user
accounts) from LP into Ask, tag them as the project of origin (nova,
swift, etc). You can se
Sounds like a good plan. My only concern with the import is that the users are
matched up, and it looks like that's being handled. The only reason I've wanted
to keep LP Answers open is to not lose that content, and this takes care of
that. Thanks for doing it, and lgtm.
--John
On Feb 6, 201
Hello folks,
we're ready to import the answers from Launchpad into Ask OpenStack. A
script will import all questions, answers, comments (and data abou user
accounts) from LP into Ask, tag them as the project of origin (nova,
swift, etc). You can see the results of the test runs on
http://ask-stagi
On Feb 6, 2014, at 3:09 AM, Édouard Thuleau wrote:
> Hi all,
>
> Just to point 2 reviews [1] & [2] I submitted to correct l2-pop
> mechanism driver into the ML2 plugin.
> I had some reviews and +1 but they doesn't progress anymore.
> Could you check them ?
> I also like to backport them for sta
On Wed, Feb 5, 2014 at 3:01 PM, Doug Hellmann
wrote:
>
>
>
> On Wed, Feb 5, 2014 at 1:25 PM, Ben Nemec wrote:
>
>> On 2014-02-05 10:58, Doug Hellmann wrote:
>>
>>
>>
>>
>> On Wed, Feb 5, 2014 at 11:44 AM, Ben Nemec wrote:
>>
>>> On 2014-02-05 09:05, Doug Hellmann wrote:
>>>
>>>
>>> On Tue, Feb
On Feb 6, 2014, at 2:56 AM, Andreas Jaeger wrote:
>
> Should other OpenStack projects adjust, e.g. Horizon shows
> "Orchestration". I guess this is fine - isn't it?
Yes, Horizon’s usage is fine, and in my opinion preferred for clarity.
Jonathan
__
On Feb 6, 2014, at 8:08 AM, Dolph Mathews wrote:
> I'm curious about the level of granularity that's envisioned in each
> definition. "Designated sections" could be as broad as keystone.* or as
> narrow as keystone.token.controllers.Auth.validate_token_head(). It could be
> defined in terms of
What a corporate thing to do :) Good call though John
-Paul
-Original Message-
From: John Dickinson [mailto:m...@not.mn]
Sent: Thursday, February 6, 2014 9:16 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Swift] meeting time updated
Histo
Historically, the Swift team meetings have been every other week. In order to
keep better track of things (and hopefully to get more specific attention on
languishing reviews), we're moving to a weekly meeting schedule.
New meeting time: every Wednesday at 1900UTC in #openstack-meeting
The meet
On Thu, Feb 6, 2014 at 10:11 AM, Sylvain Bauza wrote:
> Thanks Doug,
>
>
>
>
> 2014-02-06 15:54 GMT+01:00 Doug Hellmann :
>
>>
>> cdf74daac2a204d5fe77f4b2bf5a956f65a73a6f Support dynamic types
>> f191f32a722ef0c2eaad71dd33da4e7787ac2424 Add IntegerType and some classes
>> for validation
>>
>> Doug
Thanks Doug,
2014-02-06 15:54 GMT+01:00 Doug Hellmann :
>
> cdf74daac2a204d5fe77f4b2bf5a956f65a73a6f Support dynamic types
> f191f32a722ef0c2eaad71dd33da4e7787ac2424 Add IntegerType and some classes
> for validation
>
> Doug
>
>
Do you know when the docs will be updated ? [1]
Some complex typ
Hi,
(Scroll down for tl;dr)
Unfortunately due to networking constraints I don't have the leisure
of a large and flat layer two network.
As such, different compute nodes and network nodes will be in separate
distinct subnets on the same network.
There will be hundreds if not thousands of subnets
Howdy!
My name is Luke and I'm helping my friends at Tail-f Systems to
support Neutron with their NCS [1] product. This went really smoothly
for us on the Havana cycle, but lately we're having a harder time with
Icehouse. In particular, our attempt to fulfill the 3rd party testing
requirements has
I have just tagged WSME 0.6. It is now on PyPI, and should be picked up
automatically by gate jobs as soon as the mirror updates.
Changes since the 0.5b6 release we have been using:
$ git log --format=oneline 0.5b6..0.6
e26d1b608cc5a05940c0b6b7fc176a0d587ba611 Add 'readonly' parameter to wsattr
9
Swapnil-
Tnx (dyslexics of the world Untie :)
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
From: Swapnil Kulkarni [mailto:swapnilkulkarni2...@gmail.com]
Sent: Thursday, February 6, 2014 3:26 AM
To: OpenStack Development Mailing List (not for usage questions)
On Wed, Feb 5, 2014 at 11:38 AM, Jonathan Bryce wrote:
> On Feb 5, 2014, at 10:18 AM, Steve Gordon wrote:
>
> > - Original Message -
> >> From: "Andreas Jaeger"
> >> To: "Mark McLoughlin" , "OpenStack Development
> Mailing List (not for usage questions)"
> >>
> >> Cc: "Jonathan Bryce"
Mike, exactly: we would like to allow flexibility & complexity at the
Advisor level without it affecting the placement computation.
Advisors are expected to manifest complex behavior as suggested by these
BPs and gather constraints from multiple sources (users and providers).
The idea is indeed
On Thu, Feb 6, 2014 at 9:21 AM, Thierry Carrez wrote:
> Dolph Mathews wrote:
> > I'm curious about the level of granularity that's envisioned in each
> > definition. "Designated sections" could be as broad as keystone.* or as
> > narrow as keystone.token.controllers.Auth.validate_token_head(). It
On Thu, Feb 6, 2014 at 8:42 AM, Thierry Carrez wrote:
> Russell Bryant wrote:
> > Perhaps going through this process for a single project first would be
> > helpful. I agree that some clarification is needed on the details of
> > the expected result.
>
> At this point, I think we can break their
Dolph Mathews wrote:
> I'm curious about the level of granularity that's envisioned in each
> definition. "Designated sections" could be as broad as keystone.* or as
> narrow as keystone.token.controllers.Auth.validate_token_head(). It
> could be defined in terms of executables, package paths, or l
Probably all PTLs could be asked to prepare initial report for requirements
like it was done last time for graduating projects.
On Thu, Feb 6, 2014 at 6:07 PM, Dina Belova wrote:
> I propose we do this in future TC meetings, time permitting. I
>> propose we start with projects where the PTL was
>
> I propose we do this in future TC meetings, time permitting. I
> propose we start with projects where the PTL was also elected to the TC,
> so that we give this new review's process some mileage.
+1, good idea
On Thu, Feb 6, 2014 at 5:47 PM, Thierry Carrez wrote:
> Dina Belova wrote:
> >
On Wed, Feb 5, 2014 at 10:22 AM, Thierry Carrez wrote:
> (This email is mostly directed to PTLs for programs that include one
> integrated project)
>
> The DefCore subcommittee from the OpenStack board of directors asked the
> Technical Committee yesterday about which code sections in each
> integ
We're looking for answers and a response on this thread from the
Foundation/board. Just wanted to be sure you all know I'm following up and
getting clarity is a priority.
Thanks,
Anne
From: Steve Gordon [sgor...@redhat.com]
Sent: Tuesday, February 04, 201
Raja, this is one of a few workable approaches that I've thought about. I'm not
convinced it's the best approach, but it does look to be less effort so we
should examine it carefully. One thing to consider is that if we go down the
route of using service VMs for the mediated drivers (such as glu
Dina Belova wrote:
> Perhaps we should start putting each project on the TC agenda for a
> review of its current standing. For any gaps, I think we should set a
> specific timeframe for when we expect these gaps to be filled.
>
>
> Really good idea. New requirements are great, but fr
Mark Washenberger wrote:
> I don't have any issue defining what I think of as typical extension /
> variation seams in the Glance code base. However, I'm still struggling
> to understand what all this means for our projects and our ecosystem.
> Basically, why do I care? What are the implications of
Russell Bryant wrote:
> Perhaps going through this process for a single project first would be
> helpful. I agree that some clarification is needed on the details of
> the expected result.
At this point, I think we can break their request into two separate
questions.
The first one is high level,
Hi,
I'd like to propose one idea that autogenerates API sample files from API
schema for Nova v3 API.
We are working on API validation for v3 API, the works require API schema
which is defined with JSONSchema for each API. On the other hand, API sample
files of v3 API are autogenerated from the
Andreas Jaeger wrote:
> On 02/05/2014 06:38 PM, Jonathan Bryce wrote:
>> In this case, we are talking about documentation that is produced and
>> distributed with the integrated release to cover the Core OpenStack Project
>> and the “modules" that are distributed together with the Core OpenStack
Hi Bob and Irena,
Thanks for the clarification. Irena, I am not opposed to a
SriovMechanismDriverBase/Mixin approach, but I want to first figure out
how much common functionality there is. Have you already looked at this?
Thanks,
Sandhya
On 2/5/14 1:58 AM, "Irena Berezovsky" wrote:
>Please s
Hello stackers,
We have a database with tables users, projects, roles, etc. Is there
any reference implementation or best practices to make keystone use
this DB instead of its own?
I have been reading
https://wiki.openstack.org/wiki/Keystone/Federation/Blueprint but I
could not find a open refere
On 05/02/14 17:32, Jaromir Coufal wrote:
[snip]
> Other concern will be with compilers. So far I've found 3 ways:
> * rails dependency (how big problem would it be?)
> * https://pypi.python.org/pypi/scss/0.7.1
> * https://pypi.python.org/pypi/SassPython/0.2.1
> * ... (other suggestions?)
The firs
On 05/02/14 17:46, Jay Pipes wrote:
> On Wed, 2014-02-05 at 16:29 +, Greg Hill wrote:
>> I'm new, so I'm sure there's some history I'm missing, but I find it bizarre
>> that we have to put the same license into every single file of source code
>> in our projects.
>
> Meh, probably just habit
On 2/6/14 1:58 PM, "Matthew Booth" wrote:
>On 06/02/14 11:24, Gary Kotton wrote:
>> Hi,
>> Thanks for the detailed mail. For the first step of moving the code into
>> OSLO we are trying to be as conservative as possible (similar to the
>>fork
>> lift of the scheduler code). That is, we are taki
On 06/02/14 11:24, Gary Kotton wrote:
> Hi,
> Thanks for the detailed mail. For the first step of moving the code into
> OSLO we are trying to be as conservative as possible (similar to the fork
> lift of the scheduler code). That is, we are taking working code and
> moving it to the common library
Hey,
Switching to SASS/Compass seems to me like a nice idea. Although reading
Compass docs on using it in django/python projects [1], they recommend
to serve compiled css in as output for production, so the production
servers don't have to carry ruby/compass gems dependencies.
Also in django
If there is agreement that it's a change worth making, then I expect
something like:
1/ Add a warning for users who use period of 0 or use the default. Both in
the literal sense of log.warning() and in the documentation.
2/ wait for a full release-cycle
3/ make the actual change in Juno.
Does th
Hi,
Thanks for the detailed mail. For the first step of moving the code into
OSLO we are trying to be as conservative as possible (similar to the fork
lift of the scheduler code). That is, we are taking working code and
moving it to the common library, not doing any rewrites and using the same
func
Hi, Alexander,
In general I am completely agree with Clint and Robert, and as one of
contributors of Murano I don't see any practical reasons for repositories
reorganization. And regarding of your proposal I have a few thoughts that I
would like to share below:
>This enourmous amount of repositor
There's currently an effort to create a common internal API to the
vSphere/ESX API:
https://blueprints.launchpad.net/oslo/+spec/vmware-api
I see there's some code already in place which essentially copies what's
currently in Nova. Having spent some time digging in this code recently,
I would take
Small correction inline
s/filter_shceduler/filter_scheduler in SCHEDULER environment variable.
On Wed, Feb 5, 2014 at 5:35 AM, Dugger, Donald D
wrote:
> Now that a preview version of the new gantt scheduler is available there
> is the problem of configuring devstack to utilize this new tree.
Vish:
+1 for hierchical IDs (e.g:
b04f9ea01a9944ac903526885a2666de.c45674c5c2c6463dad3c0cb9d7b8a6d8)
(names used for clarity of explanations).
Chris:
+1 for hierarchical /project flavors, images, and so on ..
Vinod, Vish:
Starting new Thread "[openstack-dev][keystone] Centralized policy rules
Spliting from thread "[openstack-dev][keystone][nova] Re: Hierarchicical
Multitenancy Discussion"
Vinod, Vish:
I understand that actions are different from one service to the
other. What I meant is that the RBAC enforcement engine, doesn't need
to understand the "meaning" of an action. It can al
Hi,
A blue print was created and Joshua even wrote quite huge text. Right now
this BP in Drafting stage, so I want to bring this BP to life and continue
working on the topic. I even tried to make some changes without approvement
(only just as experiment) and got negative feedbacks.
These steps I d
Sean Dague wrote:
> First, very cool!
Thanks.
> This is very promising work. It might be really interesting to figure
> out if there was a smaller project inside of OpenStack that could be
> test ported over to this (even as a stackforge project), and something
> we could run in the gate.
Oslo M
Hi,
Joshua Harlow:
> Any mysql DB drivers (I think the majority of openstack deployments use
> mysql?).
I don't know. Here are some asynchronous clients for MySQL:
https://github.com/PyMySQL/PyMySQL/
https://launchpad.net/myconnpy
https://github.com/hybridlogic/txMySQL
http://chartio.com/blog/20
On Thu, Feb 6, 2014 at 8:16 PM, Matthew Gilliard
wrote:
> Hello everyone.
>
> wrt these bugs: https://bugs.launchpad.net/nova/+bug/1276203
> https://bugs.launchpad.net/nova/+bug/1272830 - I'd just like to make sure
> that the approach I'm planning makes sense.
>
> To summarise: Currently there
Hi,
It has come to my attention that this blueprint
(https://blueprints.launchpad.net/nova/+spec/vmware-image-cache-management) has
been deferred to the next milestone series. The blueprint ensures that the
driver has aging for cached images. This is a critical issue for the driver and
is impor
Hi,
Let's discuss lbaas progress and plans in #openstack-meetings 14-00 UTC
today.
Meeting agenda: https://wiki.openstack.org/wiki/Network/LBaaS
Thanks,
Eugene.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org
Hi,
The following patches will really help minesweeper:
1. Treat exceptions that are caused by parallel tests. This enables us to
run parallel jobs (we have very promising results of running 8 parallel
test jobs):
https://review.openstack.org/#/c/70137/
https://review.openstack.org/#/c/
Excerpts from Mike Spreitzer's message of 2014-02-05 22:17:50 -0800:
> > From: Prasad Vellanki
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > ,
> > Date: 01/21/2014 02:16 AM
> > Subject: Re: [openstack-dev] [heat] Sofware Config progress
> >
> > Steve & Clint
> >
>
Hello everyone.
wrt these bugs: https://bugs.launchpad.net/nova/+bug/1276203
https://bugs.launchpad.net/nova/+bug/1272830 - I'd just like to make sure
that the approach I'm planning makes sense.
To summarise: Currently there are a number of methods in
compute/manager.py that use the @periodic
Hi all,
Just to point 2 reviews [1] & [2] I submitted to correct l2-pop
mechanism driver into the ML2 plugin.
I had some reviews and +1 but they doesn't progress anymore.
Could you check them ?
I also like to backport them for stable Havana branch.
[1] https://review.openstack.org/#/c/63917/
[2]
On 02/06/2014 07:42 AM, Andreas Jaeger wrote:
> On 02/05/2014 06:38 PM, Jonathan Bryce wrote:
>> On Feb 5, 2014, at 10:18 AM, Steve Gordon wrote:
>>
>>> - Original Message -
From: "Andreas Jaeger"
To: "Mark McLoughlin" , "OpenStack Development Mailing
List (not for usage q
Hello Joe.
Thanks for pointing this issue. We will investigate this situation and fix
it.
In the future in such cases you can just create a bug on launchpad.
Also feel free to ping me (and another db maintainers) in IRC.
Thanks,
Victor
On Wed, Feb 5, 2014 at 9:12 PM, Joe Gordon wrote:
> Hi B
97 matches
Mail list logo
