Eugene and Mark,
We get interest in the current OpenStack LBaaS solution.
Backward compatibility should be considered as part of any feature we add for
icehouse.
I think that the any such BP should first address the best way to implement the
feature (as Eugene did) but then also solve the
Hi,
We’ve create two more etherpads to start discussing Mistral Dataflow and Error
Handling mechanisms:
https://etherpad.openstack.org/p/MistralDataFlow
https://etherpad.openstack.org/p/MistralErrorHandling
Feel free to contribute your ideas.
Thanks!
Renat Akhmerov
@ Mirantis
Boris Pavlovic bpavlo...@mirantis.com wrote on 18/11/2013 08:31:20 AM:
Actually schedulers in nova and cinder are almost the same.
Well, this is kind of expected, since Cinder scheduler started as a
copy-paste of the Nova scheduler :-) But they already started diverging
(not sure whether
On Fri, Nov 15, 2013 at 5:59 AM, Stephen Gran
stephen.g...@theguardian.comwrote:
On 15/11/13 13:14, Eugene Nikanorov wrote:
Hi folks,
I've created a brief description of this feature.
You can find it here:
https://wiki.openstack.org/wiki/Neutron/LBaaS/LoadbalancerInstance
Hi,
We’ve created the initial set of blueprints for Mistral functionality at
Launchpad. They summarize our discussions in mailing list, etherpads and at
Hong Kong summit. You can find them here:
https://blueprints.launchpad.net/mistral
If you have any new ideas please share them.
Thanks!
On 11/18/2013 01:03 PM, Christopher Armstrong wrote:
On Sun, Nov 17, 2013 at 2:57 PM, Steve Baker sba...@redhat.com
mailto:sba...@redhat.com wrote:
On 11/15/2013 05:19 AM, Christopher Armstrong wrote:
http://docs.heatautoscale.apiary.io/
I've thrown together a rough
On 17/11/13 21:57, Steve Baker wrote:
On 11/15/2013 05:19 AM, Christopher Armstrong wrote:
http://docs.heatautoscale.apiary.io/
I've thrown together a rough sketch of the proposed API for
autoscaling. It's written in API-Blueprint format (which is a simple
subset of Markdown) and provides
Hi,
As I understood Juniper/contrail developers have also troubles with IPAM.
The Hooks you are talking about in Nova, is handled with service
plugin in Neutron. May be there is a place to implement an IPAMaaS
service, or DHCPaaS?
On Thu, Nov 14, 2013 at 6:32 AM, Lari Partanen
I think we can discuss backward compatibility further.
So the gist of the feature is that loadbalancer resource is introduced that
should be created first and becomes the root object of the existing lbaas
object graph.
There could be 2 options of preserving API compatibility:
1) preserve it on
On 16/11/13 11:11, Angus Salkeld wrote:
On 15/11/13 16:32 +0100, Zane Bitter wrote:
On 14/11/13 19:53, Christopher Armstrong wrote:
I'm a little unclear as to what point you're making here. Right now, the
launch configuration is specified in the scaling group by the
resources property of the
On 16/11/13 23:08 +0800, Zhi Yan Liu wrote:
Enhancing Image Locations:
--
https://etherpad.openstack.org/p/icehouse-summit-enhance-image-location-property
This session proposed adding several attributes to image locations
1. Add 'status' to each location.
I think
Boris,
Is it really OK to drop these tables? Could Nova can work without them
(e.g. rollback)? And if Ceilometer is about to ask nova for host state
metrics ?
Yes it is OK, because now ceilometer and other projects could ask
scheduler about host state. (I don't see any problems)
IMO,
Hi Oslo developers,
It seems my latest patch¹ on oslo.messaging scared Mark, so I'll try to
discuss it a bit on this mailing list as it is more convenient.
I've created a blueprint² as requested by Mark. That seems necessary
since it will be spread on several patch.
Now to the core.
Morgan Fainberg wrote:
TL;DR Don't split the community, work to improve the tools for those
who are overwhelmed. (Email clients, enforcing use of subject tags,
etc)
Thanks everyone for the insightful comments ! Like I said earlier, we
can keep it the way it is, but I just wanted to make sure
Oh no, not another *aas!
Seriously, I don't think IP address management should be a service of its
own independent from Neutron and/or nova-network.
Neutron currently has an IPAM logic which is entirely coded in
db_base_plugin_v2.py, and is more or less loosely coupled with the DHCP
agent.
We
I'm editing tempest/scenario/test_network_basic_ops.py for external
connectivity as the TODO listed in its docstring.
the test cases are for pinging against external ip and url to test
connectivity and dns respectivly.
since default deployement (devstack gate) doesn't have external
Thanks everyone who have joined Climate weekly meeting.
Here are logs from it:
Minutes:
http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-11-18-10.04.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-11-18-10.04.txt
Log:
On Sat, Nov 16, 2013 at 9:09 AM, Monty Taylor mord...@inaugust.com wrote:
Can I suggest that you don't try purely mechanical filtering into
folders? Instead, for a while, try using a threaded client, and
configure it to show threads unexpanded by default.
if we are into mail client tips,
On Fri, 15 Nov 2013 12:46:44 +0100
Zane Bitter zbit...@redhat.com wrote:
Yes, but you don't know the UUID until you know it, and by then it's too
late (the resource has been created). So the idempotency token has to be
something passed in by the user.
I completely agree with you that token
Hi,
This is just a reminder that we are NOT having the IRC meeting today due to
reschedule: the meeting is moved to Tuesday 17:00 UTC. So, see you in IRC
tomorrow!
--
Regards,
Alexander Tivelkov
2013/11/13 Serg Melikyan smelik...@mirantis.com
Hello, OpenStack developers!
We rescheduled our
Hi Flavio,
Thank you for your reply.
I'm going to read the blueprint.
-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: Friday, November 15, 2013 9:37 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Glance]
On 16/11/13 11:15, Angus Salkeld wrote:
On 15/11/13 08:46 -0600, Christopher Armstrong wrote:
On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter zbit...@redhat.com wrote:
On 15/11/13 02:48, Christopher Armstrong wrote:
On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld asalk...@redhat.com
On 18/11/13 12:15, Mitsuru Kanabuchi wrote:
On Fri, 15 Nov 2013 12:46:44 +0100
Zane Bitter zbit...@redhat.com wrote:
Yes, but you don't know the UUID until you know it, and by then it's too
late (the resource has been created). So the idempotency token has to be
something passed in by the
On 11/18/2013 11:41 AM, Yair Fried wrote:
I'm editing tempest/scenario/test_network_basic_ops.py for external
connectivity as the TODO listed in its docstring.
the test cases are for pinging against external ip and url to test
connectivity and dns respectivly.
since default deployement
Hi Yair,
I had in mind of doing something similar. I also registered a tempest
blueprint for it.
Basically I think we can assume test machines have access to the Internet,
but the devstack deployment might not be able to route packets from VMs to
the Internet.
Being able to ping the external
On 15/11/13 21:06, Mike Spreitzer wrote:
Zane Bitter zbit...@redhat.com wrote on 11/14/2013 12:56:22 PM:
...
My 2c: the way I designed the Heat API was such that extant stacks can
be addressed uniquely by name. Humans are pretty good with names, not so
much with 128 bit numbers. The
I've pushed https://review.openstack.org/#/c/56923/ trying to follow this
protocol.
Salvatore
On 14 November 2013 16:38, Zhi Kun Liu liuzhi...@gmail.com wrote:
+1, This is a great idea. We could consider it as a general process for
all tests.
2013/11/14 Koderer, Marc m.kode...@telekom.de
Hi all,
I have reworked the wiki page [1] I created last week to reflect
discussions we had on the mail list and in IRC. From ML discussions last
week it looked like we were all basically on the same page (with some
details to be worked out), and I hope the new draft eliminates some
confusion
Hey,
still trying to get https://review.openstack.org/#/c/39237/ through the gate :)
As per David Kranz's request, I am now handling client isolation, but about 50%
of the time the tests fail because of an integrity error, see
Do we need to register on event brite if joining over IRC / Google Hangout?
On Saturday, November 16, 2013 3:43 AM, Roshan Agrawal
roshan.agra...@rackspace.com wrote:
We are all set for the Solum design workshops at SFO on Nov 19,20. The etherpad
page below has schedule and agenda details
Thierry Carrez wrote:
The two candidates who nominated themselves in time for this election are:
* David Lyle
* Matthias Runge
The election will be set up tomorrow, and will stay open for voting for
a week.
Election closes at 21:59 UTC Tuesday, so Horizon contributors have a bit
more
Yong, if you read Mark's proposal closely, the third party tests will only run
when the specific third party code is touched, or when the Jenkins user submits
code.
On Nov 17, 2013, at 11:50 PM, Yongsheng Gong gong...@unitedstack.com wrote:
For third party testing, I am afraid these tests
Most projects follow a review rule that a patch needs 2 +2s before being
approved. I suggest we do the same for Solum. I bring it up since I've
noticed some inconsistency with this so far.
Thanks,
--
Russell Bryant
___
OpenStack-dev mailing list
On 11/18/2013 08:42 AM, Kyle Mestery (kmestery) wrote:
Yong, if you read Mark's proposal closely, the third party tests will only
run when the specific third party code is touched, or when the Jenkins user
submits code.
On Nov 17, 2013, at 11:50 PM, Yongsheng Gong gong...@unitedstack.com
On 11/18/2013 05:05 AM, Julien Danjou wrote:
Hi Oslo developers,
It seems my latest patch¹ on oslo.messaging scared Mark, so I'll try to
discuss it a bit on this mailing list as it is more convenient.
I've created a blueprint² as requested by Mark. That seems necessary
since it will be spread
On 11/18/2013 05:32 AM, Salvatore Orlando wrote:
Oh no, not another *aas!
Seriously, I don't think IP address management should be a service
of its own independent from Neutron and/or nova-network. Neutron
currently has an IPAM logic which is entirely coded in
db_base_plugin_v2.py, and is more
On 11/18/2013 08:56 AM, Russell Bryant wrote:
Most projects follow a review rule that a patch needs 2 +2s before being
approved. I suggest we do the same for Solum. I bring it up since I've
noticed some inconsistency with this so far.
+2.
-jay
Hi,
I read the qa-meeting log[1]. And I registered a blueprint[2] for
tracking and avoiding duplication.
I think if we put Partially Implements: blueprint
add-scenario-tests-in-icehouse in the commit message,
we can avoid the duplication and tracking the scenarios. Because the
commit subject and
On 11/18/2013 07:31 AM, Jay Pipes wrote:
On 11/18/2013 08:56 AM, Russell Bryant wrote:
Most projects follow a review rule that a patch needs 2 +2s before being
approved. I suggest we do the same for Solum. I bring it up since I've
noticed some inconsistency with this so far.
+2.
+2/+A
On Sat 16 Nov 2013 (17:43), Russell Bryant wrote:
On 11/16/2013 11:18 AM, Álvaro López García wrote:
On Fri 15 Nov 2013 (07:28), Dan Smith wrote:
Hi all,
Hi Dan.
As you know, Nova adopted a plan to require CI testing for all our
in-tree hypervisors by the Icehouse release. At the
I'd like to suggest that we take a step back and identify the actual
requirement(s) we're trying address, independent of the actual implementation
(current or otherwise). Once that requirement is clearly stated, we can think
of viable approaches and then, lastly, how the current architecture
On 11/18/2013 09:55 AM, Álvaro López García wrote:
On Sat 16 Nov 2013 (17:43), Russell Bryant wrote:
On 11/16/2013 11:18 AM, Álvaro López García wrote:
On Fri 15 Nov 2013 (07:28), Dan Smith wrote:
Hi all,
Hi Dan.
As you know, Nova adopted a plan to require CI testing for all our
in-tree
At IBM Research, we are actively working on metadata search in Swift and
would like to join in on this initiative to help form a standard search API
and reference implementation for Swift. We recently implemented a metadata
search research prototype for Swift, and have been working on metadata
Hi,
Please take a look at
https://wiki.openstack.org/wiki/Blueprints#Creation for tips on the
blueprint creation process. Blueprint reviewers are going to look at
the criteria listed at
https://wiki.openstack.org/wiki/Blueprints#Blueprint_Review_Criteria so
you should make sure you address
Tuomas,
Have you published your code/blueprints anywhere? Looks like we’re working on
the same stuff. I have implemented almost the same feature set (haven’t
published anything yet because of this thread), except for the scheduler part.
The main goal is to be able to pin VCPUs in NUMA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 15/11/13 13:14, Eugene Nikanorov wrote:
I've created a brief description of this feature. You can find it
here:
https://wiki.openstack.org/wiki/Neutron/LBaaS/LoadbalancerInstance
On 11/15/13 at 04:01pm, yunhong jiang wrote:
On Fri, 2013-11-15 at 17:19 -0500, Andrew Laski wrote:
On 11/15/13 at 07:30am, Dan Smith wrote:
You're not missing anything. But I think that's a bug, or at least an
unexpected change in behaviour from how it used to work. If you follow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Monty,
On 18/11/13 15:17, Monty Taylor wrote:
On 11/18/2013 07:14 AM, Andrew Hutchings wrote:
Hi,
On 15/11/13 13:14, Eugene Nikanorov wrote:
I've created a brief description of this feature. You can find
it here:
On 13/11/13 18:49, Doug Hellmann wrote:
On Mon, Nov 11, 2013 at 6:08 PM, Mark McLoughlin mar...@redhat.com
mailto:mar...@redhat.com wrote:
Hi Nikola,
On Mon, 2013-11-11 at 12:44 +0100, Nikola Đipanov wrote:
Hey all,
During the summit session on the the
+2
Yes, thanks for raising that concern. I did approve a few patches before we had
other core reviewers configured, and I think I also may have also approved a
.gitignore patch after. I will strictly conform to our two +2 workflow going
forward, as I agree that merge policy is a good one.
--
No. Registration is for in person attendance only.
--
Adrian
Original message
From: Rajdeep Dua
Date:11/18/2013 5:39 AM (GMT-08:00)
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Solum] SFO Design Workshop
Do we need to
Another issue that we might want to try and solve with this (and imho
another reason to keep the framework for this in oslo) is that we might
want to make these update aware, and allow for some graceful degradation
or something similar when for example an updated service is stated with
an
On 11/18/2013 09:34 AM, Masayuki Igawa wrote:
Hi,
I read the qa-meeting log[1]. And I registered a blueprint[2] for
tracking and avoiding duplication.
I think if we put Partially Implements: blueprint
add-scenario-tests-in-icehouse in the commit message,
we can avoid the duplication and
Hi,
On Mon, Nov 18, 2013 at 11:05:20AM +0100, Julien Danjou wrote:
Hi Oslo developers,
It seems my latest patch¹ on oslo.messaging scared Mark, so I'll try to
discuss it a bit on this mailing list as it is more convenient.
I've created a blueprint² as requested by Mark. That seems
To be fair, we test only the subset that is set via devstack on the stable
side. That should be a common subset, but it is far from fully
comprehensive. Nova has over 600 config variables, so additional tooling
here would be goodness.
Sean Dague
http://dague.net
On Nov 18, 2013 7:35 AM, Dan Smith
It seems to me that having this separation of concerns in oslo.messaging
would be good idea. My plan is to move out the configuration object out
of the basic object, like I did in the first patch.
I don't plan to break the configuration handling or so, I just think it
should be handled in a
On 11/18/2013 09:57 AM, Paula Ta-Shma wrote:
At IBM Research, we are actively working on metadata search in Swift and
would like to join in on this initiative to help form a standard search API
and reference implementation for Swift. We recently implemented a metadata
search research prototype
Hi, David
Thanks for your reply.
On Tue, Nov 19, 2013 at 12:37 AM, David Kranz dkr...@redhat.com wrote:
On 11/18/2013 09:34 AM, Masayuki Igawa wrote:
Hi,
I read the qa-meeting log[1]. And I registered a blueprint[2] for
tracking and avoiding duplication.
I think if we put Partially
On Mon, Nov 18 2013, Eric Windisch wrote:
Hi Eric,
I agree with Mark that a clear blueprint and plan should be outlined.
I'm not happy with the blueprint as written, it is sparse, outlining
your intention, rather than a plan of attack. I'd really like to know
what the plan of attack here is,
On Mon, Nov 18, 2013 at 5:05 AM, Julien Danjou jul...@danjou.info wrote:
Hi Oslo developers,
It seems my latest patch¹ on oslo.messaging scared Mark, so I'll try to
discuss it a bit on this mailing list as it is more convenient.
I've created a blueprint² as requested by Mark. That seems
Hi Julien,
On Mon, 2013-11-18 at 11:05 +0100, Julien Danjou wrote:
Hi Oslo developers,
It seems my latest patch¹ on oslo.messaging scared Mark, so I'll try to
discuss it a bit on this mailing list as it is more convenient.
Scared, heh :)
I've created a blueprint² as requested by Mark.
On Mon, Nov 18 2013, Mark McLoughlin wrote:
Ok, so it's a ceilometer blueprint and says:
The goal of this blueprint is to be able to use oslo.messaging
without using a configuration file/object, while keeping its usage
possible and not breaking compatibility with OpenStack
On Nov 15, 2013, at 10:04 AM, Garry Chen garryc...@icloud.com wrote:
Hi
Liz Jirka, thanks for ur advise, I will make the design post on UX askbot
next time, I'm just a newbie in Openstack.
By the way, i do understand the column will get narrow if have more data to
represent, will u
On Mon, 2013-11-18 at 17:37 +0100, Julien Danjou wrote:
On Mon, Nov 18 2013, Mark McLoughlin wrote:
I'm struggling to care about this until I have some insight into why
it's important. And it's a bit frustrating to have to guess the
rationale for this. Like commit messages, blueprints
Hey Doug,
On Mon, 2013-11-18 at 11:29 -0500, Doug Hellmann wrote:
On Mon, Nov 18, 2013 at 5:05 AM, Julien Danjou jul...@danjou.info wrote:
Hi Oslo developers,
It seems my latest patch¹ on oslo.messaging scared Mark, so I'll try to
discuss it a bit on this mailing list as it is more
Hi,
Thanks for joining today’s community meeting in IRC at #openstack-meeting. Here
are the minutes and the full log:
http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-11-18-16.00.html
http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-11-18-16.00.log.html
Join
Random OSLO updates with no list of what changed, what got fixed etc
are unlikely to get review attention - doing such a review is
extremely difficult. I was -2ing them and asking for more info, but
they keep popping up. I'm really not sure what the best way of
updating from OSLO is, but this
Hi Lianhao Lu,
I briefly summarized my recollection of that session in this blueprint:
https://blueprints.launchpad.net/ironic/+spec/add-ceilometer-agent
I've responded to your questions inline as well.
On Sun, Nov 17, 2013 at 10:24 PM, Lu, Lianhao lianhao...@intel.com wrote:
Hi stackers,
Dear OpenStack devs,
A recent review [1] dragged into spotlight how damaging improper use of
external code inside migrations can be.
Basically in my mind the incident raises 2 issues that I think we should
look into:
1) How can we make reviewing changes with db migrations more robust
Since we
Is there easy parking at the rackspace office?
On Nov 18, 2013, at 7:33 AM, Adrian Otto adrian.o...@rackspace.com wrote:
No. Registration is for in person attendance only.
--
Adrian
Original message
From: Rajdeep Dua
Date:11/18/2013 5:39 AM (GMT-08:00)
To:
On Mon, 2013-11-18 at 10:18 -0500, Andrew Laski wrote:
On 11/15/13 at 04:01pm, yunhong jiang wrote:
On Fri, 2013-11-15 at 17:19 -0500, Andrew Laski wrote:
If yes, would it be possible to create a special task_state as IDLE, to
distinguish it better? When no task on-going, the task_state will
To be fair, we test only the subset that is set via devstack on the
stable side. That should be a common subset, but it is far from fully
comprehensive. Nova has over 600 config variables, so additional tooling
here would be goodness.
I'm surely not arguing against additional testing of
On Mon, Nov 18, 2013 at 12:25 PM, Devananda van der Veen
devananda@gmail.com wrote:
Hi Lianhao Lu,
I briefly summarized my recollection of that session in this blueprint:
https://blueprints.launchpad.net/ironic/+spec/add-ceilometer-agent
I've responded to your questions inline as
On Mon, Nov 18, 2013 at 12:50 AM, Pedro Roque Marques
pedro.r.marq...@gmail.com wrote:
Does it address the catch-22 problem that a Neutron reviewer asks for the
plugin to be accepted upstream into devstack as pre-condition for
acceptance whether a devstack reviewer as for the plugin to be
Greetings,
I'm on a quest to address Nova's project management growing pains and to
make sure the Nova PTL is never an unnecessary bottleneck. One area
that has been identified as needing a small team is handling Nova
security vulnerability reports.
We have the nova-coresec team on launchpad
No, it does not have any parking. I suggest coming in on BART and exit at the
Montgomery station and coming south on 2nd to Folsom by foot.
The Courtyard hotel across the street has parking but that is very expensive
and may be full.
Parking at the meters on the street is not a great option
On Mon, Nov 18, 2013 at 9:40 AM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:
On Mon, Nov 18, 2013 at 12:25 PM, Devananda van der Veen
devananda@gmail.com wrote:
Hi Lianhao Lu,
I briefly summarized my recollection of that session in this blueprint:
It's worth noting that right now, just a few blocks from the office
DreamForce is going on, so it's going to be crowded, I strongly recommend
avoiding driving if you can.
Alex
On Mon, Nov 18, 2013 at 9:50 AM, Adrian Otto adrian.o...@rackspace.comwrote:
No, it does not have any parking. I
If you want to drive to the Rackspace office, here's a list of parking garages
in the area. Street parking will be hard to find.
http://goo.gl/maps/yuoWW
On Nov 18, 2013, at 11:50 AM, Adrian Otto
adrian.o...@rackspace.commailto:adrian.o...@rackspace.com
wrote:
No, it does not have any
Honestly, with that reasoning, this approach strikes me as a technical solution
to a political problem, a band-aid on a sprained ankle, and so on and so forth
in that pattern.
There was no shortage of talk about cross-project coordination challenges in HK
and Portland, so it shouldn't be news
Greetings all stackers,
I propose that we add Anastasia Karpinska to the taskflow-core team [1].
Anastasia has been actively contributing to taskflow for a while now, both in
code and reviews. She provides high quality reviews and is doing an awesome job
with the various taskflow concepts (and
I see it as important (and not theoretical).
I'd like to use oslo.messaging (and oslo.messaging.rpc) in taskflow (to
prototype how a distributed engine would work using it) and bringing in a
library which requires global configuration is almost a non-starter for
me. Although taskflow is targeted
Hi,
I think that in the Atlas/Libra model loadbalancer is used in a similar way
as the VIP object in Neutron/LBaaS.
Regards,
-Sam.
-Original Message-
From: Andrew Hutchings [mailto:and...@linuxjedi.co.uk]
Sent: Monday, November 18, 2013 5:23 PM
To:
The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting tomorrow, Tuesday November 19th, at 19:00 UTC in
#openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone interested in
Hi,
I summarized a list of requirements to the config validation framework from
this thread and other sources, including IRC discussions so far:
https://gist.github.com/ogelbukh/7533029
Seems like we have 2 work items here, one being extension which adds more
complex flags types to Oslo.config,
Oleg - this is great! I tried to find you on IRC to recommend we put this on a
etherpad so several of us can collaborate together on requirements and
brainstorming.
On Nov 18, 2013, at 10:54 AM, Oleg Gelbukh ogelb...@mirantis.com wrote:
Hi,
I summarized a list of requirements to the
On 18/11/13 18:46, Nikola Đipanov wrote:
1) How can we make reviewing changes with db migrations more robust
Since we use sqlalchemy-migrate to version our database, the package's
documentation [2] states how care needs to be taken when importing code
inside a db migration script. It seems
Russell,
(ccing Bryan, Rob)
Thanks for the initiative. We at the OpenStack Security Group
https://launchpad.net/~openstack-ossgare doing
large part of these tasks now and are looking for more help (particularly
around reviews from people that are intimate to the project internals).
Here are some
There were some concerns expressed at the summit about scheduler
scalability in Nova, and a little recollection of Boris' proposal to keep
the needed state in memory. I also heard one guy say that he thinks Nova
does not really need a general SQL database, that a NOSQL database with a
bit of
On Mon, Nov 18, 2013 at 1:35 PM, Ladislav Smola lsm...@redhat.com wrote:
Hello. I have a couple of additional questions.
1. What about IPMI data that we want to get by polling. E.g. temperatures,
etc. Will the Ironic be polling these kind of
data and send them directly to collector(or
I'm not sure the problem is that we use a general SQL database. The
problems as I see it are:
-Multi-master in MySQL sucks. Complicated, problematic and not performant.
Also, no great way to do multi-master over higher latency networks.
-MySQL and Postgres require tuning to scale.
-We tend to
+1 on changing the relationship between data persistence and scheduler rules.
That's a directly addressable problem.
There was a thread on the ML a while ago dealing with the work load on the
scheduler. The problem was that when the scheduler rules fire 55 times a second
subsequent rules were
On 11/18/2013 02:35 PM, Mike Spreitzer wrote:
There were some concerns expressed at the summit about scheduler
scalability in Nova, and a little recollection of Boris' proposal to
keep the needed state in memory.
While it could be possible to do all of the scheduler state in memory, I
think a
Developers,
This topic has been discussed before but I do not remember if we have a good
solution or not.
Basically, if concurrent API calls are sent to Neutron, all of them are sent
to the plug-in level where two actions have to be made:
1. DB transaction No just for data persistence but also
+1
Thanks
Changbin
On Mon, Nov 18, 2013 at 1:05 PM, Joshua Harlow harlo...@yahoo-inc.comwrote:
Greetings all stackers,
I propose that we add Anastasia Karpinska to the taskflow-core team [1].
Anastasia has been actively contributing to taskflow for a while now,
both in
code and
On Mon, 2013-11-18 at 18:46 +0100, Nikola Đipanov wrote:
Dear OpenStack devs,
A recent review [1] dragged into spotlight how damaging improper use of
external code inside migrations can be.
Basically in my mind the incident raises 2 issues that I think we should
look into:
1) How can
This actually doesn't solve the issue because if you run multiple neutron
servers behind a loadbalancer you will still run into the same issue with
the transaction on the database I believe.
We handle this issue in the NVP plugin by removing the transaction and
attempt to manually delete the port
On 11/18/2013 03:25 PM, Edgar Magana wrote:
Developers,
This topic has been discussed before but I do not remember if we have a
good solution or not.
The ML2 plugin addresses this by calling each MechanismDriver twice. The
create_network_precommit() method is called as part of the DB
On 11/18/2013 02:25 PM, Edgar Magana wrote:
The problem that we are experiencing is when concurrent calls to the
same API are sent, the number of operation at the plug-in back-end are
long enough to make the next concurrent API call to get stuck at the DB
transaction level, which creates a hung
Sorry for the delay in responding to this...
* Moved the _obj_classes registry magic out of ObjectMetaClass and into
its own method for easier use. Since this is a subclass based
implementation,
having a separate method feels more appropriate for a factory/registry
pattern.
1 - 100 of 152 matches
Mail list logo
