Hi Stackers,
I know that I can add metadata information (Key - Value parameters) to a VM
through 'nova boot' command.
But, I didn't find the facility through Harizon pages. Does anybody know
whether the feature is available through Openstack Dashboard?
Please let me know.
Regards,
Srikanth.
no worries... can't speak for that Dolph fellow though :)
i think it's good to understand/learn different testing/benchmarking
strategies.
cheers,
gord
Date: Thu, 11 Jun 2015 17:34:57 +1200
From: robe...@robertcollins.net
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev]
Salvatore, thanks for the info, will try to review as soon as possible. Hope we
get consistent implementation.
From: Salvatore Orlando [mailto:sorla...@nicira.com]
Sent: Wednesday, June 10, 2015 4:51 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev]
Hi,
We have merged the spec that describes the priorities for the Liberty
release, as discussed at the summit:
http://specs.openstack.org/openstack/nova-specs/priorities/liberty-priorities.html
The tracking of spec and code reviews for these is happening in the
usual etherpad:
Hi, all.
I create a vm and it's neutron port's mac address is fa:16:3e:3f:02:ff. I see
fa:16:3e:3f:02:ff inside vm when I run ifconfig eth0. Why does vm's tap
device's mac address is fe:16:3e:3f:02:ff? Why different between neutron
port's mac address and tap device's mac address? Does libvirt
On 06/09/2015 06:42 PM, Jeremy Stanley wrote:
As discussed in the Liberty Design Summit Moving apps to Python 3
cross-project workshop, the way forward in the near future is to
switch to the pure-python PyMySQL library as a default.
+1
On 6/10/15, 10:11 PM, Carl Baldwin c...@ecbaldwin.net wrote:
Folks,
As the Neutron L3 Lieutenant [1] under the PTL, Kyle, I'd like to
propose Brian Haley as a member of the Neutron L3 core reviewer team.
Brian has been a long time contributor in Neutron showing expertise
particularly in
On 11/06/15 10:47, changzhi wrote:
Hi, all.
I create a vm and it's neutron port's mac address is
fa:16:3e:3f:02:ff. I see fa:16:3e:3f:02:ff inside vm when I run
ifconfig eth0. Why does vm's tap device's mac address is
fe:16:3e:3f:02:ff? Why different between neutron port's mac address
and tap
On Thursday, 11 June 2015, 12:00:46, Neil Jerram neil.jer...@metaswitch.com
wrote:
On 11/06/15 10:47, changzhi wrote:
Hi, all.
I create a vm and it's neutron port's mac address is
fa:16:3e:3f:02:ff. I see fa:16:3e:3f:02:ff inside
vm when I run
ifconfig eth0. Why does vm's tap
On 06/02/2015 01:39 PM, Alexandre Levine wrote:
Thank you Nikola.
We'll be adding the required tickets and will follow your reviews,
however the person working primarily on this subject (Feodor Tersin) is
out for his vacation for a couple of weeks so some of our responses
might be delayed
+1 for the thread, I would also like to hear from Mirantis on this.
The Fork on fuel/puppet has been actively seen patching and
consolidation.It seems like parallel effort why not merge it.
regards
/sanjay
On Thu, Jun 11, 2015 at 9:12 AM, Emilien Macchi emil...@redhat.com wrote:
Hi,
Before
Victor,
Monty had a github repo, that's where we are starting from. The idea
is to rely on our day to day tools here in the openstack ecosystem to
maintain the project. If one of the original authors shows up, we'll
see what we can do. Given that the code is Apache License 2.0, we are
ok to pick
Ian, Neil, thanks for your input!
There may be a set of races you need to deal with, too - what happens
if
Nova starts a VM attached to a Neutron network binding that has yet
to
be set up? Neutron doesn't (well, technically, shouldn't be
expected
to) do things instantaneously on a call,
Yes, that's the official position - Avoid mox, use mock, worst case
use mox3 for existing
-- dims
On Thu, Jun 11, 2015 at 3:37 AM, Jordan Pittier
jordan.pitt...@scality.com wrote:
Hi,
Shouldn't we move to use mock instead ? If mox3 is supported and active, why
would we recommend to use mock ?
Thomas,
oslo.vmware (master) moved to suds-jurko for both python2 and python3.
we deleted references in nova and other places directly to suds and
rely on transitively loading the suds-jurko specified from
oslo.vmware. cinder (master) has a reference to suds-jurko as well.
-- dims
On Thu, Jun
On Thu, 2015-06-11 at 09:30 +0100, Daniel P. Berrange wrote:
It seems the main reason for your new proposal is to deal with
the fact that on migration, you need to specify a different
NIC name in the XML. This is not particularly difficult - Nova
already has code for dealing with pdating the
On 6 June 2015 at 11:16, Kashyap Chamarthy kcham...@redhat.com wrote:
On Fri, Jun 05, 2015 at 10:47:31AM +0100, John Garbutt wrote:
Hi,
So in the interests of filling up your inbox yet further...
We have lots of etherpads from the summit:
Yesterday we landed the infrastructure for Grenade external plugins -
https://review.openstack.org/#/c/185050/
The first user of this is the Heat project, with a patch that's nearly
ready to land (still sorting out an issue because heat's cli commands
aren't console entry points) -
As one of the Lieutenants [1] for the API and DB areas under the PTL, I would
like to propose Ann Kamyshnikova as a member of the Neutron API and DB core
reviewer team.
Ann has been a long time contributor in Neutron showing expertise particularly
in database matters. She has also worked with and
On 11/06/15 09:38, Kyle Mestery wrote:
On Thu, Jun 11, 2015 at 6:11 AM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
Yesterday we landed the infrastructure for Grenade external plugins -
https://review.openstack.org/#/c/185050/
The first user of this is the Heat project,
Hi Emilien,
I can see why you might be unhappy with Fuel's actions with regards to
the OpenStack Puppet modules. You could make this argument about many
components in Fuel. The heart of the matter is that we bundle the
upstream OpenStack Puppet modules with all the other modules,
developed both
On 6/10/15 11:48 PM, Dolph Mathews wrote:
tl;dr *.iteritems() is faster and more memory efficient than .items()
in python2*
Using xrange() in python2 instead of range() because it's more memory
efficient and consistent between python 2 and 3...
# xrange() + .items()
python -m timeit -n
On Thu, Jun 11, 2015 at 12:54:54PM +0200, Andreas Scheuring wrote:
On Thu, 2015-06-11 at 09:30 +0100, Daniel P. Berrange wrote:
It seems the main reason for your new proposal is to deal with
the fact that on migration, you need to specify a different
NIC name in the XML. This is not
On 11/06/15 06:53 -0700, Richard Raseley wrote:
Flavio Percoco wrote:
Greetings,
I'm reaching out to our puppet community looking for help on creating
Zaqar's puppet manifests. We've started doing lots of work to help the
community adopt Zaqar and it'd be a shame to get at the end of the
road
On 2015-06-11 07:51:55 +0200 (+0200), Philipp Marek wrote:
[...]
I still stand by my opinion (as voiced in Vancouver) that for such
one-off things (that contributors are not likely to repeat over
and over again) it might make sense to have -infra simply *do*
them[3].
[...]
To reiterate my
I could use some help with setting up git-review in a slightly unfriendly
firewall situation.
I'm trying to set up git-review on my CentOS7 VM, and our firewall blocks the
non-standard ssh port. I'm following the instructions at
Hi Folks,
As we have discussed in the last Keystone meeting, we created an etherpad
with the alternatives to solve this problem:
https://etherpad.openstack.org/p/reseller-project-token
We have also decided to take a vote to choose the best option in the next
Keystone Meeting (#openstack-meeting -
Hi Radek,
1. You can't use column references on any table except those created by a
datasource, mainly because Congress doesn't know the name of the columns
for those tables. We've kicked around the idea of letting policy-writers
declare the column names of any table, but it's trickier than it
it is just me, or are these differences pretty negligible considering
this is the 1 million item dictionary, which in itself is a unicorn
in openstack code or really most code anywhere?
as was stated before, if we have million-item dictionaries floating
around, that code has problems. I
On 6/5/2015 4:47 AM, John Garbutt wrote:
Hi,
So in the interests of filling up your inbox yet further...
We have lots of etherpads from the summit:
https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads#Nova
I have extracted all the action items here:
Hi,
Le 10/06/2015 02:15, Robert Collins a écrit :
python2.7 -m timeit -s 'd=dict(enumerate(range(100)))' 'for i in
d.items(): pass'
10 loops, best of 3: 76.6 msec per loop
python2.7 -m timeit -s 'd=dict(enumerate(range(100)))' 'for i in
d.iteritems(): pass'
100 loops, best of 3: 22.6
Flavio Percoco wrote:
Greetings,
I'm reaching out to our puppet community looking for help on creating
Zaqar's puppet manifests. We've started doing lots of work to help the
community adopt Zaqar and it'd be a shame to get at the end of the
road without having OPs friendly deployment tools.
I
On 06/11/2015 01:16 AM, Robert Collins wrote:
But again - where in OpenStack does this matter the slightest?
Precisely. I can't think of a single case where we are iterating over
anywhere near the number of dictionary items that we would see any
impact whatsoever.
Best,
-jay
Hello,
Is it possible to have named parameters on rule's left side, for example:
1. predeploy_modify(eid,oid,add_property,5, name=image, value=pvalue)
:- Glancev2:images(name=pvalue,...)
2. predeploy_modify(eid,oid,add_object, 10, type=monitoring,
port=8190, path=/aa/bb) :-
Greetings,
I'm reaching out to our puppet community looking for help on creating
Zaqar's puppet manifests. We've started doing lots of work to help the
community adopt Zaqar and it'd be a shame to get at the end of the
road without having OPs friendly deployment tools.
I tried to work on this
On Thu, Jun 11, 2015 at 6:11 AM, Sean Dague s...@dague.net wrote:
Yesterday we landed the infrastructure for Grenade external plugins -
https://review.openstack.org/#/c/185050/
The first user of this is the Heat project, with a patch that's nearly
ready to land (still sorting out an issue
Hi, I know that neutron port's mac address was generated by neutron.conf and
default value is fa:16:3e which from base_mac configuration. I don't know how
the tap device's mac address generates and why tap device mac address was
fe:16:3e:xxx. I think that tap device mac address was generated by
Hey,
On 06/11/2015 09:29 AM, Flavio Percoco wrote:
Greetings,
I'm reaching out to our puppet community looking for help on creating
Zaqar's puppet manifests. We've started doing lots of work to help the
community adopt Zaqar and it'd be a shame to get at the end of the
road without having
Following feedback for increasing working group participation from
Vancouver summit[1] and discussions in the weekly meetings[2], we have
decided to move the Wednesday working group meeting times and reduce their
frequency. The Monday Office Hours meetings will remain unchanged.
The options for
On 06/11/2015 09:02 AM, Jay Pipes wrote:
On 06/11/2015 01:16 AM, Robert Collins wrote:
But again - where in OpenStack does this matter the slightest?
Precisely. I can't think of a single case where we are iterating over
anywhere near the number of dictionary items that we would see any
Hi Carl et al.,
I see from [1] that L3 routed network segments are on the Neutron L3
subteam's roadmap for Liberty, and I wanted to say that I'm very
interested in this work, and - if there isn't someone else already -
happy to take the lead on making it happen.
I'm aware already of several
On 06/11/2015 12:54 PM, James E. Blair wrote:
The Infrastructure program has a unique three-tier team structure:
contributors (that's all of us!), core members (people with +2 ability
on infra projects in Gerrit) and root members (people with
administrative access). Read all about it here:
Hello all,
There has been a lot of discussion around Share Migration lately. This
feature has two main code paths:
- Driver Migration: optimized migration of shares from backend A to backend
B where both backends belong to the same driver vendor. The driver is
responsible for migrating and just
Hi all,
Cross posting to openstack-dev and openstack-operators
We discussed supporting multiple types of routers within a Neutron in
the L3 meeting this morning [1]. The team would like more feedback
from the community in order to refine use cases and also to consider
possible approaches to
Hi Chen Li,
You are correct in that setting up a CI system is not a trivial task. IMO
it would make sense to have this eventually tested with infras
infrastructure but as Jeremy mentioned, they don't have the bandwidth to do
the setup. Below are some links to get started if you all are interested
Hi David,
Following git config options are supported by git-review (
https://review.openstack.org/116035)
git config --global gitreview.scheme https
git config --global gitreview.port 443
BUT the feature was merged after 1.24 (it's highlighted by your git review
-vs)
so the feature is
Hello,
I've been doing some research about file injection in VM instances at boot
time, I found[1] that there are several ways of doing it, including
mounting images[2] (using guestfs, loops and nbd), using config drive
(creating a device and making it available to mount it in the instance) and
Hi Matthew,
Thanks for your reply, please see inline:
On 06/11/2015 10:36 AM, Matthew Mosesohn wrote:
Hi Emilien,
I can see why you might be unhappy with Fuel's actions with regards to
the OpenStack Puppet modules. You could make this argument about many
components in Fuel. The heart of
Hi Thomas:
I just checked and I don't see suds as a requirement for trove.
I don't think it should be a requirement for the trove debian package,
either.
Thanks,
Nikhil
On Thu, Jun 11, 2015 at 3:03 AM, Davanum Srinivas dava...@gmail.com wrote:
Thomas,
oslo.vmware (master) moved to
I am not able to say whether this works for Nova. Surely works for Neutron
- from a functional perspective at least.
I still don't know however whether this choice is the best way to proceed,
and perhaps you can help me understand better.
Role checks are always expressed through policy.json and
Aloha!
As you know I pushed spec [1] during the Kilo lifecycle, but given the lazy
procrastinator that I am, I did not manage to complete in time for the
release.
This actually gave me a chance to realise that the spec that I pushed and
had approved did not make a lot of sense. Even worse, there
We as a community don't do a great job watching bugs, so personally I'd
prefer that fuel developers just push patches, filing a bug too if you
want. (Note: we do need to improve our bug tracking!) However, I don't
think that asking puppet openstack devs to ask in the fuel channel if a
given bug is
On 2015-06-11 19:53:25 + (+), KARR, DAVID wrote:
Ok, the output from git remote -v is this:
--
originhttps://github.com/openstack/horizon.git (fetch)
originhttps://github.com/openstack/horizon.git (push)
---
So there's obviously nothing to
-Original Message-
From: Jeremy Stanley [mailto:fu...@yuggoth.org]
Sent: Thursday, June 11, 2015 1:11 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Looking for help getting git-review to
work over https
On 2015-06-11 19:53:25
I followed the instructions for installing and configuring corkscrew, similar
to what you provided here. The result seems to indicate it did something, but
the overall result is the same:
2015-06-11 13:07:25.866568 Running: git log --color=never --oneline HEAD^1..HEAD
2015-06-11 13:07:25.869309
+1
On 11 June 2015 at 12:42, Carl Baldwin c...@ecbaldwin.net wrote:
+1
On Thu, Jun 11, 2015 at 12:15 PM, Kevin Benton blak...@gmail.com wrote:
Hello all!
As the Lieutenant of the built-in control plane[1], I would like YAMAMOTO
Takashi to be a member of the control plane core reviewer
I see. I would guess a footnote on the instructions about this would be
useful. Is https://github.com/openstack-infra/git-review the proper location to
get the buildable source? I don’t see any obvious build instructions there.
From: ZZelle [mailto:zze...@gmail.com]
Sent: Thursday, June 11,
Hey Matt other OpenStack folks,
I agree that pinging #fuel-dev would not be scalable for every
request. But I think it was more of if someone notices something is
fixed in fuel-library but not in an OpenStack puppet library, then by
all means come and poke someone so we can try and get it in to
On 06/12/2015 12:34 AM, Thomas Goirand wrote:
On 06/10/2015 11:23 PM, Mike Bayer wrote:
On 6/10/15 5:18 PM, Thomas Goirand wrote:
On 06/10/2015 04:52 PM, Mike Bayer wrote:
whew! :)
Do you know why it fails with Kilo?
https://review.openstack.org/#/c/190062/
I noticed this, I don't know
First of all, thank you Emilien for bringing this up, and thank you Matt for
confirming our commitment to collaborate with puppet-openstack and other
Puppet modules that Fuel developers consider upstream.
I'd like to add some more concrete examples of what Fuel team has
already done, is doing,
This is just going swimmingly.
% sudo python setup.py install
Download error on https://pypi.python.org/simple/pbr/: [Errno 110] Connection
timed out -- Some packages may not be found!
Couldn't find index page for 'pbr' (maybe misspelled?)
Download error on https://pypi.python.org/simple/: [Errno
As most of you already know, work is beginning to move forward on the
micro-versioned Neutron API, for which a specification is available at [1]
From a practical perspective there is one non-negligible preliminary issue
that needs attention. then Neutron API URI prefix includes the full version
What gateway address do you give to regular clients via dhcp when you have
multiple?
On Jun 11, 2015 12:29 PM, Shraddha Pandhe spandhe.openst...@gmail.com
wrote:
Hi,
Currently, the Subnets in Neutron and Nova-Network only support one
gateway. For provider networks in large data centers, quite
Making progress. I didn’t realize I had to reset proxy vars after sudo.
From: KARR, DAVID
Sent: Thursday, June 11, 2015 4:16 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Looking for help getting git-review to work over
https
***Security
I managed to install pip, but I don’t understand what “pip install git-review”
is doing. It doesn’t appear to be replacing the already installed git-review.
From: ZZelle [mailto:zze...@gmail.com]
Sent: Thursday, June 11, 2015 3:50 PM
To: OpenStack Development Mailing List (not for usage
Hi,
Before you read me, please remember I know almost nothing about puppet. :)
On 06/11/2015 11:03 PM, Matt Fischer wrote:
We as a community don't do a great job watching bugs, so personally I'd
prefer that fuel developers just push patches, filing a bug too if you
want. (Note: we do need to
On 06/10/2015 11:23 PM, Mike Bayer wrote:
On 6/10/15 5:18 PM, Thomas Goirand wrote:
On 06/10/2015 04:52 PM, Mike Bayer wrote:
whew! :)
Do you know why it fails with Kilo?
https://review.openstack.org/#/c/190062/
I noticed this, I don't know very well how the requirements get
The idea is to round-robin between gateways by using some sort of mod
operation
So logically it can look something like:
idx = len(gateways) % ip
gateway = gateways[idx]
This is just one idea. I am open to more ideas.
On Thu, Jun 11, 2015 at 3:10 PM, Kevin Benton blak...@gmail.com
On 06/11/2015 05:35 PM, Salvatore Orlando wrote:
I am not able to say whether this works for Nova. Surely works for
Neutron - from a functional perspective at least.
I still don't know however whether this choice is the best way to
proceed, and perhaps you can help me understand better.
Hi!
On Fri, Jun 12, 2015 at 7:07 AM, Mark Boo mrkzm...@gmail.com wrote:
[snip]
Now my questions are:
- Is this (file injection using image mounting) likely to be deprecated at
some point in the future?
Yes, we've been building up to that for a long time and I can't see is
not doing it. Its
Indeed, the doc[1] is unclear
git-review can be installed using: python setup.py install or pip install .
[1]
http://docs.openstack.org/infra/manual/developers.html#accessing-gerrit-over-https
On Thu, Jun 11, 2015 at 11:16 PM, KARR, DAVID dk0...@att.com wrote:
I see. I would guess a
Try creating/updated ~/.pip/pip.conf
With contents:
[global]
proxy = http://your_proxy:port/
From: KARR, DAVID [mailto:dk0...@att.com]
Sent: Thursday, June 11, 2015 4:16 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Looking for help getting
Hi,
We now have a working CI on below patches:
https://review.openstack.org/#/c/187707/
https://review.openstack.org/#/c/187853/
@jgriffith: we will sure start to give back to community.Thanks for
pointing this out.
Regards
Nikesh
On Thu, Jun 4, 2015 at 1:46 PM, Alex Meade
Just want to add that for logging purposes, consistency, as Devananda explains
and Adrian and Sean agree, is really important. The number of fields in a
header response should be consistent. If the field is not always used, a
placeholder should be put in (usually a “-“ in logs). Makes parsing
I've looking at using puppet-swift to deploy a swift cluster.
Firstly - without
http://git.openstack.org/cgit/stackforge/puppet-swift/tree/tests/site.pp
I would have struggled a great deal more to get up and running, so a big
thank you for a nice worked example of how to do multiple nodes!
It is however interesting that both lock wait timeouts and missing
savepoint errors occur in operations pertaining the same table -
securitygroups in this case.
I wonder if the switch to pymysl has not actually uncovered some other bug
in Neutron.
I have no opposition to a revert, but since this
+1
2015-06-11 23:34 GMT+09:00 Henry Gessau ges...@cisco.com:
As one of the Lieutenants [1] for the API and DB areas under the PTL, I
would
like to propose Ann Kamyshnikova as a member of the Neutron API and DB core
reviewer team.
Ann has been a long time contributor in Neutron showing
Hi,
Meeting: Thursday at 1600
UTChttp://www.timeanddate.com/worldclock/fixedtime.html?hour=16min=00sec=0
in #openstack-meeting-3
Agenda: https://wiki.openstack.org/wiki/Meetings/cloudpulse
Thanks
Vinod.
__
OpenStack
Thx for your help. I resolve this problem by change gerrit url. Command like
this:
git remote set-url gerrit
https://changzhi:gT1w.openstack.org/stackforge/tacker
-- Original --
From: Tom Fifieldt...@openstack.org;
Date: Thu, Jun 11, 2015 11:56 AM
To:
Hi all
can anybody please take a look on my PR[1]?
[1] https://review.openstack.org/#/c/189564/
Thanks Limor
-Original Message-
From: BORTMAN, Limor (Limor) [mailto:limor.bort...@alcatel-lucent.com]
Sent: Wednesday, June 03, 2015 2:28 PM
To: openstack-dev@lists.openstack.org
Subject:
Hi,
The current maintainer of suds in Debian sent bug reports against all
packages depending on it. We would like to get rid of suds completely.
See:
https://bugs.debian.org/788080
https://bugs.debian.org/788081
https://bugs.debian.org/788083
https://bugs.debian.org/788085
Hi,
Shouldn't we move to use mock instead ? If mox3 is supported and active,
why would we recommend to use mock ?
Jordan
On Wed, Jun 10, 2015 at 10:17 PM, Davanum Srinivas dava...@gmail.com
wrote:
Oslo folks, everyone,
mox3 needs to be maintained since some of our projects use it and we
Glad to see the schedule is determined. +1 for it.
Regards,
Xuhaiwei
-Original Message-
From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com]
Sent: Thursday, June 11, 2015 1:12 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Senlin] Project weekly meeting starts June
Last reminder, if you are interested, take the poll :)
On Mon, Jun 8, 2015 at 9:45 PM, Zhipeng Huang zhipengh...@gmail.com wrote:
Hi Iben , if u are interestEd dont forget to participate the time pool :)
On Jun 5, 2015 11:03 PM, Rodriguez, Iben iben.rodrig...@spirent.com
wrote:
Hello Joe,
On 11 June 2015 at 15:34, Michael Still mi...@stillhq.com wrote:
On Fri, Jun 12, 2015 at 7:07 AM, Mark Boo mrkzm...@gmail.com wrote:
- What functionality is missing (if any) in config drive / metadata
service
solutions to completely replace file injection?
None that I am aware of. In
On 11 June 2015 at 12:37, Richard Raseley rich...@raseley.com wrote:
Andrew Laski wrote:
There are many reasons a deployer may want to live-migrate instances
around: capacity planning, security patching, noisy neighbors, host
maintenance, etc... and I just don't think the user needs to know
On Thu, Jun 11, 2015 at 05:39:28PM -0400, Emilien Macchi wrote:
On 06/11/2015 10:36 AM, Matthew Mosesohn wrote:
I'm not saying it's the most community-oriented approach, but Fuel
would have never evolved and matured without it. The attribution in
commits is lost because our directory
Thanks all. I promise to not break things too much!
Cheers,
Josh
On Fri, Jun 12, 2015 at 2:54 AM, James E. Blair cor...@inaugust.com wrote:
The Infrastructure program has a unique three-tier team structure:
contributors (that's all of us!), core members (people with +2 ability
on infra
All,
I'm writing a BP for meter rename @ https://review.openstack.org/#/c/183419/
Simply speaking, we will translate meter querying API for both input and output
if ender user specify an known renamed meter.
Gordon has a performance concern to translate the output given possible huge
number
On 2015-06-12 12:42:11 +1000 (+1000), Joshua Hesketh wrote:
Thanks all. I promise to not break things too much!
All I ask is that you fix whatever you've broken by the time I wake
up. ;)
--
Jeremy Stanley
__
OpenStack
Dmitry, thank you for taking your time. Please read inline:
On 06/11/2015 07:12 PM, Dmitry Borodaenko wrote:
First of all, thank you Emilien for bringing this up, and thank you Matt for
confirming our commitment to collaborate with puppet-openstack and other
Puppet modules that Fuel developers
On 06/11/2015 10:31 PM, Dmitry Borodaenko wrote:
On Thu, Jun 11, 2015 at 05:39:28PM -0400, Emilien Macchi wrote:
On 06/11/2015 10:36 AM, Matthew Mosesohn wrote:
I'm not saying it's the most community-oriented approach, but Fuel
would have never evolved and matured without it. The attribution
On 2015-06-11 23:32:58 + (+), KARR, DAVID wrote:
I managed to install pip, but I don’t understand what “pip install
git-review” is doing. It doesn’t appear to be replacing the
already installed git-review.
`pip install git-review` installs the latest git-review release from
On 2015-06-11 23:00:52 +0200 (+0200), ZZelle wrote:
Following git config options are supported by git-review (
https://review.openstack.org/116035)
git config --global gitreview.scheme https
git config --global gitreview.port 443
BUT the feature was merged after 1.24 (it's
If I understand the bp correctly,
the apiserver_port is for public access or API call service endpoint. If it
is that case, user would use that info
htttp(s)://ip:port
so port is good information for users.
If we believe above assumption is right. Then
1) Some user not needed to change port,
On Thu, Jun 11, 2015 at 5:03 PM, Salvatore Orlando sorla...@nicira.com
wrote:
As most of you already know, work is beginning to move forward on the
micro-versioned Neutron API, for which a specification is available at [1]
Yes, I just approved the spec in fact.
From a practical perspective
Hi neutrons,
I'd like to draw your attention to an issue discovered by rally gate job:
http://logs.openstack.org/96/190796/4/check/gate-rally-dsvm-neutron-rally/7a18e43/logs/screen-q-svc.txt.gz?level=TRACE
I don't have bandwidth to take a deep look at it, but first impression is
that it is some
+1
On Jun 11, 2015, at 4:52 PM, Rochelle Grober
rochelle.gro...@huawei.commailto:rochelle.gro...@huawei.com wrote:
Just want to add that for logging purposes, consistency, as Devananda explains
and Adrian and Sean agree, is really important. The number of fields in a
header response should be
Team,
We are fortunate enough to have a thriving community of developers who want to
make OpenStack great, and several of us have pledged support for this work in
Magnum. Due to the amount of interest expressed in this pursuit, and the small
amount of overlap between the developers in
I've just done another run of abandons as a pre-cursor to the spec
review day this Friday. I'd suggest if you have a spec which has been
sitting with unresolved review comments for a fair while taking a look
at those before Friday would be a good idea.
Cheers,
Michael
On Fri, May 22, 2015 at
1 - 100 of 154 matches
Mail list logo
