On Jul 30, 2014, at 10:57 AM, Samuel Merritt s...@swiftstack.com wrote:
On 7/30/14, 10:18 AM, Shrinand Javadekar wrote:
Hi,
Swift v1 allowed for geo replication using read and write affinity
rules. Now, Swift v2 allows setting storage policies (which can affect
replication) per container.
Hi all,
i have a server which was build with foreman and it gives me a double port see
below:
swiftclient.exceptions.ClientException: Object PUT failed:
http://20.19.19.19:8080:8080/v1/AUTH_f3a3a9be2dbf4ac3b3b846c4ec68ac89/container2/obj
and it returns a 503 of course .
Thanks,
Remo
Hi Remo,
most likely the exception message itself is wrong (the shown double
port), but it got fixed a while ago:
https://github.com/openstack/python-swiftclient/commit/2e1a5b7e28211b0b2e2f7a2f961d7fcbd7e8abe3
Can you access the proxy server logs to see what's going on there?
Christian
Am
On 28-Jul-14 22:37, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700:
On 26/07/14 00:04, Anant Patil wrote:
When the stack is updated, a diff of updated template and current
template can be stored to optimize database. And perhaps Heat should
have an API to
On 07/29/2014 07:24 PM, Davanum Srinivas wrote:
The Oslo team is pleased to announce the first release of oslo.utils,
the library that replaces several utils modules from oslo-incubator:
https://github.com/openstack/oslo.utils/tree/master/oslo/utils
The new library has been uploaded to PyPI,
Greetings to All!
Your review / feedback is much awaited on the proposals in this blueprint.
Just wanted to let you know that we are planning to start implementing design
#3 later next week in case there isn't any further advice from you.
Appreciate your time here...
Many thanks!
Raghu
From:
On 07/30/2014 12:57 AM, Bhandaru, Malini K wrote:
Hello Everyone!
We were discussing the following blueprint in Glance:
Enhanced-Platform-Awareness-OVF-Meta-Data-Import
:https://review.openstack.org/#/c/104904/
The OVA format is very rich and the proposal here in its first incarnation is
On 07/29/2014 09:01 PM, Russell Bryant wrote:
On 07/29/2014 12:12 PM, Daniel P. Berrange wrote:
Sure there was some debate about what criteria were desired acceptance
when stable trees were started. Once the criteria are defined I don't
think it is credible to say that people are incapable of
Hi Jay,
Thanks for your comment. You suggestion is good but I am wondering why
we cannot use or leverage Ceilometer to monitor infrastructure-related,
as it can used to monitor tenant-related things.
Regards,
Gary
On 07/29/2014 02:05 AM, Duan, Li-Gong (Gary at
On 07/23/2014 06:05 PM, Rob Crittenden wrote:
Rob Crittenden wrote:
It looks like the switch to requests in python-glanceclient
(https://review.openstack.org/#/c/78269/) has broken nova when SSL is
enabled.
I think it is related to the custom object that the glanceclient uses.
If another
Hi Daniel,
For now (IceHouse), it's not possible to boot from iso and attach volume
after boot. Libvirt present ISO disk via an IDE controller (/dev/hda)
and new volume try to be added as IDE too (/dev/hdb).
Do you mean that with the new block device mapping code, we will be able
to boot from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 30/07/14 04:00, Kyle Mestery wrote:
I'm personally ok with this hard limit, but I'd really like to
hear from distribution people here to understand their thoughts,
including what versions of dnsmasq ship with their products and how
this would
On Tue, Jul 29, 2014 at 02:48:12PM -0400, Russell Bryant wrote:
On 07/29/2014 11:43 AM, Tracy Jones wrote:
3. We have bugs that are really not bugs but features, or performance
issues. They really should be a BP not a bug, but we don’t want these
things to fall off the radar so they are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 29/07/14 18:12, Daniel P. Berrange wrote:
On Tue, Jul 29, 2014 at 08:30:09AM -0700, Jay Pipes wrote:
On 07/29/2014 06:13 AM, Daniel P. Berrange wrote:
On Tue, Jul 29, 2014 at 02:04:42PM +0200, Thierry Carrez
wrote:
Ihar Hrachyshka a écrit :
On Wed, Jul 30, 2014 at 11:16:00AM +0200, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 29/07/14 18:12, Daniel P. Berrange wrote:
On Tue, Jul 29, 2014 at 08:30:09AM -0700, Jay Pipes wrote:
On 07/29/2014 06:13 AM, Daniel P. Berrange wrote:
On Tue, Jul 29, 2014
On 30/07/2014 07:53, Matt Riedemann wrote:
On 7/25/2014 2:38 PM, Clark Boylan wrote:
Hello,
The recent release of tox 1.7.2 has fixed the {posargs} interpolation
issues we had with newer tox which forced us to be pinned to tox==1.6.1.
Before we can remove the pin and start telling people to
On Fri, Jul 25, 2014 at 02:38:49PM -0700, Clark Boylan wrote:
Hello,
The recent release of tox 1.7.2 has fixed the {posargs} interpolation
issues we had with newer tox which forced us to be pinned to tox==1.6.1.
Before we can remove the pin and start telling people to use latest tox
we need
Hello guys.
In the last time I meet again change related with changing content of
README for Docker resource.
https://review.openstack.org/#/c/110541/
https://review.openstack.org/#/c/101144/
Both changes try to improve current description.
I looked on other README files in contrib directories
Hello, Stackers.
Since Trove gives an ability to create post-deployment configuration for
instances, it would be nice to have an ability to pass database
configuration file location through configuration file location.
I’d like to propose feature that would improve usability of CLI for
On Tue, 29 Jul 2014, Chris Dent wrote:
Let me know whenever you have a new release, without mechanize as new
dependency, or with it being optional.
It will be soon (a day or so).
https://pypi.python.org/pypi/wsgi_intercept is now at 0.8.0
All traces of mechanize removed. Have at. Enjoy. If
On Fri, Jul 25, 2014 at 02:38:49PM -0700, Clark Boylan wrote:
New tox sets a random PYTHONHASHSEED value by default. Arguably this is
a good thing as it forces you to write code that handles unknown hash
seeds, but unfortunately many projects' unittests don't currently deal
with this very
Hi Kyle,
SUSE Cloud ships dnsmasq 2.71 . For us it's fine to bump the minimum
version supported
to 2.63 .
cheers,
Rossella
On 07/30/2014 04:00 AM, Kyle Mestery wrote:
On Tue, Jul 29, 2014 at 8:51 PM, Xuhan Peng pengxu...@gmail.com wrote:
We bumped the minimum version of dnsmasq to 2.63 a
James Slagle wrote:
Finally, the juno-2 milestone has passed. Many (if not all?)
integrated projects have already -2'd specs that have not been
approved, indicating they are not going to make Juno. There are many
valid reasons to do this: focus, stabilization, workload, etc.
Personally, I
Morgan Fainberg wrote:
The Keystone team is looking for feedback from the community on what type of
Keystone Token is being used in your OpenStack deployments. This is to help
us understand the use of the different providers and get information on the
reasoning (if possible) that that token
On Wed, 2014-07-30 at 13:41 +0400, Sergey Kraynev wrote:
Hello guys.
In the last time I meet again change related with changing content of
README for Docker resource.
https://review.openstack.org/#/c/110541/
I can ditch mine, just making a change after helping someone
on IRC through
Swartzlander, Ben wrote:
On Tue, 2014-07-29 at 13:38 +0200, Thierry Carrez wrote:
Swartzlander, Ben a écrit :
Manila has come a long way since we proposed it for incubation last autumn.
Below are the formal requests.
https://wiki.openstack.org/wiki/Manila/Incubation_Application
Russell Bryant wrote:
On 07/29/2014 12:12 PM, Daniel P. Berrange wrote:
Sure there was some debate about what criteria were desired acceptance
when stable trees were started. Once the criteria are defined I don't
think it is credible to say that people are incapable of following the
rules. In
Greetings,
Apologies for the cross-post: this should be of interest to both infra
and olso.messaging developers.
The blueprint [0] that adds support for version 1.0 of the AMQP messaging
protocol is blocked due to CI test failures [1]. These failures are due
to a new package dependency this
On 30 July 2014 16:21, Angus Salkeld angus.salk...@rackspace.com wrote:
On Wed, 2014-07-30 at 13:41 +0400, Sergey Kraynev wrote:
Hello guys.
In the last time I meet again change related with changing content of
README for Docker resource.
So we need to create a decorator method for create(), save(), destroy() etc
as following?
NOTIFICATION_FIELDS = ['host', 'metadata', ...]
@notify_on_save(NOTIFICATION_FIELDS)
@base.remotable
def save(context):
@notify_on_create(NOTIFICATION_FIELDS)
@base.remotable
def
On Wed, Jul 30, 2014 at 08:54:01AM -0400, Ken Giusti wrote:
Greetings,
Apologies for the cross-post: this should be of interest to both infra
and olso.messaging developers.
The blueprint [0] that adds support for version 1.0 of the AMQP messaging
protocol is blocked due to CI test
Hi Brandon, Doug
Thanks for your explanations and feedback
I think I understand now what should be done.
I made a commit today to my TLS change https://review.openstack.org/#/c/109035
And my barbican module change https://review.openstack.org/#/c/109849
It caused:
1. patch commit to New
I noticed yesterday that trying to rebuild tox in nova fails because it
won't pull down the oslo alpha packages (config, messaging, rootwrap).
It looks like you need the --pre option with pip install to get these
normally.
Also sounds like tox should already be doing --pre, but it doesn't
This change:
https://review.openstack.org/#/c/105501/
Tries to pull in libvirt-python = 1.2.5 for testing.
I'm on Ubuntu Precise for development which has libvirt 0.9.8.
The latest libvirt-python appears to require libvirt = 0.9.11.
So do I have to move to Trusty?
--
Thanks,
Matt Riedemann
On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote:
This change:
https://review.openstack.org/#/c/105501/
Tries to pull in libvirt-python = 1.2.5 for testing.
I'm on Ubuntu Precise for development which has libvirt 0.9.8.
The latest libvirt-python appears to require
On 07/30/2014 02:21 AM, Daniel P. Berrange wrote:
On Wed, Jul 30, 2014 at 11:16:00AM +0200, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 29/07/14 18:12, Daniel P. Berrange wrote:
On Tue, Jul 29, 2014 at 08:30:09AM -0700, Jay Pipes wrote:
On 07/29/2014 06:13 AM,
I deployed a single node devstack on Ubuntu 14.04.
This devstack belongs to Juno.
When i am running tempest api volume test, i am getting some tests failed.
Below are steps for devstack deployment:
1) git clone https://github.com/openstack-dev/devstack.git
2)cd devstack
3)vi local.conf
I noticed yesterday that trying to rebuild tox in nova fails because it
won't pull down the oslo alpha packages (config, messaging, rootwrap).
i ran into this yesterday as well. Doug suggested i update my virtualenv and
that worked. i went from 1.10.1 to 1.11.x
cheers,
gord
On 07/30/2014 06:51 AM, Nikesh Kumar Mahalka wrote:
I deployed a single node devstack on Ubuntu 14.04.
This devstack belongs to Juno.
When i am running tempest api volume test, i am getting some tests failed.
Below are steps for devstack deployment:
1) git clone
On Wed, Jul 30, 2014 at 7:52 AM, Thierry Carrez thie...@openstack.org wrote:
Russell Bryant wrote:
On 07/29/2014 12:12 PM, Daniel P. Berrange wrote:
Sure there was some debate about what criteria were desired acceptance
when stable trees were started. Once the criteria are defined I don't
On Tue, Jul 29, 2014 at 10:12 AM, Jonathan Proulx j...@jonproulx.com wrote:
Hi All,
Would making an nova-network mechanism driver for the ml2 plugin be possible?
This has been discussed a bit, and yes, in theory this is possible.
Nachi has started looking into this as far as I know. I also
Given the fact most of the key players are at the nova mid-cycle this
week, lets cancel the parity meeting [1] for today. Next week, lets
focus on what came out of the nova mid-cycle and a plan for the final
weeks of Juno.
Thanks!
Kyle
[1]
On 07/30/2014 12:12 AM, Duan, Li-Gong (Gary@HPServers-Core-OE-PSC) wrote:
Hi Jay,
Thanks for your comment. You suggestion is good but I am wondering why
we cannot use or leverage Ceilometer to monitor infrastructure-related,
as it can used to monitor tenant-related things.
You *could* use
If all you want to do is publish a notification you can use oslo.messaging
directly. Or, for something lighter weight, we have Notabene, which is a small
wrapper on Kombu.
An example of how our notification simulator/generator uses it is available
here:
Hi all,
We had the APAC docs team meeting and here are the minutes and logs:
http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-30-03.01.html
http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-30-03.01.log.html
Lots going on in doclandia so let's get started.
We recently merged an implementation for GET /v3/catalog which finally
enables POST /v3/auth/tokens?nocatalog to be a reasonable default behavior,
at the cost of an extra HTTP call from remote service back to keystone
where necessary.
Spec:
ceilometer/objectstore/swift_middleware.py[1] counts the size of web
request and reponse bodies through the swift proxy server and publishes
metrics of the size of the request and response and that a request
happened at all.
There are (at least) two bug reports associated with this bit of code:
Hello, Stackers.
I’d like to gather Trove team around question related to
Datastores/Version API responses (request/response payloads and HTTP codes).
Small INFO
When deployer creates datastore and versions for it Troves` backend
receives request to store DBDatastore and
On 07/28/2014 11:20 AM, Bogdan Dobrelya wrote:
Hello.
I'd like to bring your attention to major RPC failover issue in
impl_rabbit.py [0]. There are several *related* patches and a number of
concerns should be considered as well:
- Passive exchanges fix [1] (looks like the problem is much
Hello, Stackers.
I’ve been working on several specs and i’d like to receive early
feedbacks on updated specs for:
-
Database log manipulations. Describes initial feature description.
-
https://wiki.openstack.org/wiki/Trove/DBInstanceLogOperation
-
Events
The hard limit should be 2.63 since that is supported in all of the modern long
term releases from the distros. I’d prefer we not exit processes because we’ve
been removing active checks on process starts.
mark
On Jul 29, 2014, at 9:51 PM, Xuhan Peng
Hello everyone!
Some recent change requests ([1], [2]) show that there is a number of
issues with locking db resources in Neutron.
One of them is initialization of drivers which can be performed
simultaneously by several neutron servers. In this case locking is
essential for avoiding conflicts
Hi everyone, we have discussed a few new names for the project to avoid
trademark issues. Previously, we had chosen “Naav” but several people weren’t
feeling great about that name. So, we discussed this today in
#openstack-marconi and got consensus to rename Marconi to Zaqar. If anyone has
Please do not re-invent locking.. the way we reinvented locking in Heat.
;)
There are well known distributed coordination services such as Zookeeper
and etcd, and there is an abstraction for them already called tooz:
https://git.openstack.org/cgit/stackforge/tooz/
Excerpts from Elena Ezhova's
Hi folks,
I would add the pxe boot capability to Nova/libvirt and Horizon too.
Currently, compute instances must be booted from images (or snapshots)
stored in Glance or volumes stored in Cinder.
Our idea (as you can find below) is already described there [1] [2] and
aims to provide a design
Hi everyone, sorry for the short notice, but we are going to hold a special
roadmap planning meeting today. Everyone is welcome to attend, but I esp. need
core reviewers to attend:
When: 2100 UTC
Where: #openstack-marconi
Agenda: https://etherpad.openstack.org/p/marconi-scratch
Hope to see you
There's also no need to use locks at all for this (distributed or
otherwise).
You can use a compare and update strategy with an exponential backoff
similar to the approach taken here:
https://review.openstack.org/#/c/109837/
I'd have to look at the Neutron code, but I suspect that a simple
I'd have to look at the Neutron code, but I suspect that a simple
strategy of issuing the UPDATE SQL statement with a WHERE condition that
I¹m assuming the locking is for serializing code, whereas for what you
describe above, is there some reason we wouldn¹t just use a transaction?
Thanks,
On 07/30/2014 09:48 AM, Doug Wiegley wrote:
I'd have to look at the Neutron code, but I suspect that a simple
strategy of issuing the UPDATE SQL statement with a WHERE condition that
I¹m assuming the locking is for serializing code, whereas for what you
describe above, is there some reason we
On 7/30/2014 9:20 AM, Matt Riedemann wrote:
On 7/30/2014 6:43 AM, Daniel P. Berrange wrote:
On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote:
This change:
https://review.openstack.org/#/c/105501/
Tries to pull in libvirt-python = 1.2.5 for testing.
I'm on Ubuntu Precise
Excerpts from Doug Wiegley's message of 2014-07-30 09:48:17 -0700:
I'd have to look at the Neutron code, but I suspect that a simple
strategy of issuing the UPDATE SQL statement with a WHERE condition that
I¹m assuming the locking is for serializing code, whereas for what you
describe
i.e. 'optimistic locking' as opposed to the 'pessimistic locking'
referenced in the 3rd link of the email starting the thread.
On Wed, Jul 30, 2014 at 9:55 AM, Jay Pipes jaypi...@gmail.com wrote:
On 07/30/2014 09:48 AM, Doug Wiegley wrote:
I'd have to look at the Neutron code, but I suspect
-Original Message-
From: Jay Pipes jaypi...@gmail.com
Reply: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: July 30, 2014 at 09:59:15
To: openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org
Subject: Re:
On 7/30/2014 6:43 AM, Daniel P. Berrange wrote:
On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote:
This change:
https://review.openstack.org/#/c/105501/
Tries to pull in libvirt-python = 1.2.5 for testing.
I'm on Ubuntu Precise for development which has libvirt 0.9.8.
The
On 7/30/2014 2:27 AM, Michele Paolino wrote:
On 30/07/2014 07:53, Matt Riedemann wrote:
On 7/25/2014 2:38 PM, Clark Boylan wrote:
Hello,
The recent release of tox 1.7.2 has fixed the {posargs} interpolation
issues we had with newer tox which forced us to be pinned to tox==1.6.1.
Before we
hi,
what's the right procedure to deprecate a plugin? we (ryu team) are
considering deprecating ryu plugin, in favor of ofagent. probably in
K-timeframe, if it's acceptable.
YAMAMOTO Takashi
___
OpenStack-dev mailing list
Excerpts from Anant Patil's message of 2014-07-29 23:21:05 -0700:
On 28-Jul-14 22:37, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700:
On 26/07/14 00:04, Anant Patil wrote:
When the stack is updated, a diff of updated template and current
template can
On 7/30/2014 9:57 AM, Matt Riedemann wrote:
On 7/30/2014 9:20 AM, Matt Riedemann wrote:
On 7/30/2014 6:43 AM, Daniel P. Berrange wrote:
On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote:
This change:
https://review.openstack.org/#/c/105501/
Tries to pull in libvirt-python
On Wed, 2014-07-30 at 09:01 +0200, Flavio Percoco wrote:
As a stable-maint, I'm always hesitant to review patches I've no
understanding on, hence I end up just checking how big is the patch,
whether it adds/removes new configuration options etc but, the real
review has to be done by someone
On 07/30/2014 10:05 AM, Kevin Benton wrote:
i.e. 'optimistic locking' as opposed to the 'pessimistic locking'
referenced in the 3rd link of the email starting the thread.
No, there's no locking.
On Wed, Jul 30, 2014 at 9:55 AM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
On Wed, Jul 30, 2014 at 12:17 PM, YAMAMOTO Takashi
yamam...@valinux.co.jp wrote:
hi,
what's the right procedure to deprecate a plugin? we (ryu team) are
considering deprecating ryu plugin, in favor of ofagent. probably in
K-timeframe, if it's acceptable.
The typical way is to announce the
On 7/30/14, 8:06 AM, Chris Dent wrote:
ceilometer/objectstore/swift_middleware.py[1] counts the size of web
request and reponse bodies through the swift proxy server and publishes
metrics of the size of the request and response and that a request
happened at all.
There are (at least) two bug
I wanted to send an email to let everyone know where we're at in the
Juno cycle. We're hitting our stride in Juno-3 development now, and we
have a lot of BPs targeted [1]. Due to this, I'm not going to approve
any more spec exceptions other than possibly flavors [2] and even less
possibly rootwrap
On 30/07/14 02:21, Anant Patil wrote:
On 28-Jul-14 22:37, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700:
On 26/07/14 00:04, Anant Patil wrote:
When the stack is updated, a diff of updated template and current
template can be stored to optimize database.
Hello,
I stop to improve vxlan population and remove SELECT FOR UPDATE[1] because
i am not sure the current approach is the right approach to handle
vxlan/gre tenant pools:
1- Do we really to populate vxlan/gre tenant pools?
The neutron-server could also choose randomly an vxlan vni in
Using the UPDATE WHERE statement you described is referred to as optimistic
locking. [1]
https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/The_CMP_Engine-Optimistic_Locking.html
On Wed, Jul 30, 2014 at 10:30 AM, Jay Pipes jaypi...@gmail.com wrote:
On 07/30/2014 10:05 AM,
On 07/30/2014 10:53 AM, Kevin Benton wrote:
Using the UPDATE WHERE statement you described is referred to as
optimistic locking. [1]
https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/The_CMP_Engine-Optimistic_Locking.html
SQL != JBoss.
It's not optimistic locking in the
Hi,
Adding this CLI command seems to be a good way to provide support for the
second model. This can be submitted as a new review patch to work through
the approaches to implement this. I suggest the current CLI patch [1] be
reviewed for the existing spec and completed.
Ryan, would it possible
In a normal DevStack install, each Compute instance causes one Ceilometer
Sample every 10 minutes. Except, there is an extra one every hour. And a
lot of extra ones at the start. What's going on here?
For example:
$ ceilometer sample-list -m instance -q
Meeting summary
https://etherpad.openstack.org/p/nfv-meeting-agenda (russellb, 14:00:32)
review actions from last week (russellb, 14:00:48)
ACTION: bauzas to update list with link to new dash (sgordon, 14:02:34)
https://review.openstack.org/#/c/95805/2 (sgordon,
- Original Message -
From: Isaku Yamahata isaku.yamah...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Hi Steve.
The timeslot of 5:00AM UTC(Tuesday) 30min clashes with it.
On Wed, Jul 30, 2014 at 6:43 AM, Daniel P. Berrange berra...@redhat.com
wrote:
On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote:
This change:
https://review.openstack.org/#/c/105501/
Tries to pull in libvirt-python = 1.2.5 for testing.
I'm on Ubuntu Precise for
Hi all,
I support this API proposal. It is simple and conveys clear semantics. Thanks
Ryan!
Cathy
From: Hemanth Ravi [mailto:hemanthrav...@gmail.com]
Sent: Wednesday, July 30, 2014 11:13 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Subrahmanyam Ongole
Subject: Re:
On Wed, 30 Jul 2014 14:25:46 +0100, Daniel P. Berrange wrote:
On Wed, Jul 30, 2014 at 08:54:01AM -0400, Ken Giusti wrote:
Greetings,
Apologies for the cross-post: this should be of interest to both infra
and olso.messaging developers.
The blueprint [0] that adds support for version
- Original Message -
From: Angelo Matarazzo matarazzoang...@gmail.com
To: openstack-dev@lists.openstack.org
Hi folks,
I would add the pxe boot capability to Nova/libvirt and Horizon too.
Currently, compute instances must be booted from images (or snapshots)
stored in Glance or
In a normal DevStack install, each Compute instance causes one Ceilometer
Sample every 10 minutes. Except, there is an extra one every hour. And a
lot of extra ones at the start. What's going on here?
instance is one meter which is generated through both polling and notifications
(see
On 7/30/2014 11:49 AM, Joe Gordon wrote:
On Wed, Jul 30, 2014 at 6:43 AM, Daniel P. Berrange berra...@redhat.com
mailto:berra...@redhat.com wrote:
On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote:
This change:
https://review.openstack.org/#/c/105501/
Hi,
There are a few other issues which may be related:
- https://review.openstack.org/103091
- https://review.openstack.org/103094
They are both related to the attachment of new interfaces to a VM
Thanks
Gary
On 7/30/14, 9:38 PM, Steve Gordon sgor...@redhat.com wrote:
Meeting summary
In Nova we have done the following:
- add a warning in the current version that this will be deprecated in K
- start of K drop the code
It is also important to have an upgrade path. What happens if I have my
RYU plugin in production and I upgrade to the next version. That should be
clearly
Hi Ryan:
As I stated in the patch review, the suggestion to use a profiled API
like IETF/CCITT is indeed very interesting. As a profiled API has not
been tried with any neutron model before, and as there is no existing
design pattern/best practices for how best to structure that, my
Maybe I misunderstood your approach then.
I though you were suggesting where a node performs an UPDATE record WHERE
record = last_state_node_saw query and then checks the number of affected
rows. That's optimistic locking by every definition I've heard of it. It
matches the following statement
On 7/30/14, 7:26 AM, Dan Smith d...@danplanet.com wrote:
When reviewing https://review.openstack.org/#/c/107954/ it occurred to
me that maybe we should consider having some kind of generic object
wrapper that could do notifications for objects. Any thoughts on this?
I think it might be good
On 7/30/14, 8:22 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Wed, 2014-07-30 at 09:01 +0200, Flavio Percoco wrote:
As a stable-maint, I'm always hesitant to review patches I've no
understanding on, hence I end up just checking how big is the patch,
whether it adds/removes
Also, can I recommend that to avoid last minute rush of all the code in
Juno-3 (and then clogging up the gate at that time), we work as a team to
re-review patches that have addressed all previously identified issues?
For example, the for the GBP plugin, the first series of patches have been
On 07/30/2014 01:22 PM, Kevin L. Mitchell wrote:
On Wed, 2014-07-30 at 09:01 +0200, Flavio Percoco wrote:
As a stable-maint, I'm always hesitant to review patches I've no
understanding on, hence I end up just checking how big is the patch,
whether it adds/removes new configuration options etc
Hi all,
This thread is very useful. We've detect issue related to the mission
statement and name of proposed program on early steps. Seems like mission
statement and name are totally unclear and don't present in the right
perspective goals of this program.
I updated name and mission statement:
On Wed, Jul 30, 2014 at 12:11 PM, Matt Riedemann mrie...@linux.vnet.ibm.com
wrote:
On 7/30/2014 11:49 AM, Joe Gordon wrote:
On Wed, Jul 30, 2014 at 6:43 AM, Daniel P. Berrange berra...@redhat.com
mailto:berra...@redhat.com wrote:
On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt
From: Gary Kotton [mailto:gkot...@vmware.com]
On 7/30/14, 8:22 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Wed, 2014-07-30 at 09:01 +0200, Flavio Percoco wrote:
As a stable-maint, I'm always hesitant to review patches I've no
understanding on, hence I end up just
On 07/30/2014 12:21 PM, Kevin Benton wrote:
Maybe I misunderstood your approach then.
I though you were suggesting where a node performs an UPDATE record
WHERE record = last_state_node_saw query and then checks the number of
affected rows. That's optimistic locking by every definition I've
Excerpts from Jay Pipes's message of 2014-07-30 13:53:38 -0700:
On 07/30/2014 12:21 PM, Kevin Benton wrote:
Maybe I misunderstood your approach then.
I though you were suggesting where a node performs an UPDATE record
WHERE record = last_state_node_saw query and then checks the number of
1 - 100 of 146 matches
Mail list logo
