Excerpts from Zane Bitter's message of 2015-01-09 14:57:21 -0800:
On 08/01/15 05:39, Anant Patil wrote:
1. The stack was failing when there were single disjoint resources or
just one resource in template. The graph did not include this resource
due to a minor bug in dependency_names(). I
Once more, I'd like to revisit the VIF_VHOSTUSER discussion [1]. I still
think this is worth getting into Nova's libvirt driver - specifically
because there's actually no way to distribute this as an extension; since
we removed the plugin mechanism for VIF drivers, it absolutely requires a
code
Hello Nova Community,
Please grant a freeze exception for the nova spec more image
properties support at https://review.openstack.org/#/c/138937/ .
The potential changes in nova are limited, affecting only to the
corresponding scheduler filters. Its purpose is to ensure and
On 01/09/2015 06:12 PM, Solly Ross wrote:
Hi,
I just noticed that noVNC was disabled by default in devstack (the relevant
change was
2015-01-09 22:22 GMT+08:00 Sylvain Bauza sba...@redhat.com:
Le 09/01/2015 14:58, Alex Xu a écrit :
2015-01-09 17:17 GMT+08:00 Sylvain Bauza sba...@redhat.com:
Le 09/01/2015 09:01, Alex Xu a écrit :
Hi, All
There is bug when running nova with ironic
On Fri, Jan 09, 2015 at 09:11:50AM -0500, Sean Dague wrote:
boto 2.35.0 just released, and makes hmac-v4 authentication mandatory
for EC2 end points (it has been optionally supported for a long time).
Nova's EC2 implementation does not do this.
The short term approach is to pin boto -
On 01/09/2015 09:50 AM, Thierry Carrez wrote:
What do you think ? Could that work ? If not, do you have alternate
suggestions ?
This seems incorporate more of what people have found incredibly useful
(work sessions) and organizes things in a way to accommodate the
anticipated growth in projects
Hi, All
There is bug when running nova with ironic
https://bugs.launchpad.net/nova/+bug/1402658
The case is simple: one baremetal node with 1024MB ram, then boot two
instances with 512MB ram flavor.
Those two instances will be scheduling to same baremetal node.
The problem is at scheduler side
Adam Gandelman wrote:
Flavio has been actively involved in stable branch maintenance for as
long as I can remember, but it looks like his +2 abilities were removed
after the organizational changes made to the stable maintenance teams.
He has expressed interest in continuing on with general
Hi Mike,
after reviewing your latest patch [1], I think that a possible solution
could be to add a new entry in fdb RPC message.
This entry would specify whether the port is multi-bound or not.
The new fdb message would look like this :
{net_id:
{port:
{agent_ip:
{mac, ip,
Morgan Fainberg wrote:
As of Juno all projects are using the new keystonemiddleware package for
auth_token middleware. Recently we’ve been running into issues with
maintenance of the now frozen (and deprecated)
keystoneclient.middleware.auth_token code. Ideally all deployments should
move
Stefano Maffulli wrote:
The wiki served for many years the purpose of 'poor man CMS' when we
didn't have an easy way to collaboratively create content. So the wiki
ended up hosting pages like 'Getting started with OpenStack', demo
videos, How to contribute, mission, to document our culture /
On Fri, Jan 09, 2015 at 04:07:51PM +1000, Angus Salkeld wrote:
On Fri, Jan 9, 2015 at 3:22 PM, Murugan, Visnusaran
visnusaran.muru...@hp.com wrote:
Steve,
A
My reasoning to have a a**--continuea** like functionality was to run it
as a periodic task and
Maru Newby wrote:
On Jan 8, 2015, at 3:54 PM, Sean Dague s...@dague.net wrote:
The crux of it comes from the fact that the operator voice (especially
those folks with large nova-network deploys) wasn't represented there.
Once we got back from the mid-cycle and brought it to the list, there
On 01/09/2015 08:43 AM, Jerry Xinyu Zhao wrote:
tuskar-ui is supposed to enroll nodes into ironic.
Right. And it has support for discoverd IIRC.
On Thu, Jan 8, 2015 at 4:36 AM, Zhou, Zhenzan zhenzan.z...@intel.com
mailto:zhenzan.z...@intel.com wrote:
Sounds like we could add something
On 9 January 2015 at 02:57, Tom Fifield t...@openstack.org wrote:
On 09/01/15 08:06, Maru Newby wrote:
The fact that operators running nova-network would like the upstream
community to pay for implementing an automated migration solution for them
is hardly surprising. It is less clear to me
Hi Liuxinguo,
Thanks for the suggestion, I'll try and make it work.
On Fri, Jan 9, 2015 at 1:24 PM, liuxinguo liuxin...@huawei.com wrote:
Hi Abhishek,
For the error in the first line:
“mkdir: cannot create directory `/logs': Permission denied”
and the error at the end:
“ln: failed
- Original Message -
Hi Mike,
after reviewing your latest patch [1], I think that a possible solution
could be to add a new entry in fdb RPC message.
This entry would specify whether the port is multi-bound or not.
The new fdb message would look like this :
{net_id:
{port:
Let's ask the operators opinions too on openstack-operators mailing list. There
was some duplication during the summit between the tracks but there is also a
significant operator need outside the pure code area which comes along with the
big tent tagging for projects. We need to make sure that
Hi Eduard,
I am going through the same process of setting up a CI with the same
instructions/tools (migrating from one using jaypipes instructions w/
static slaves). What I learned the other day in IRC is that the gearman
plugin will only register the job if there are build slaves with labels
Inline
~sean
On Jan 9, 2015, at 9:30 AM, Thierry Carrez thie...@openstack.org wrote:
sean roberts wrote:
I like it. Thank you for coming up with improvements to the
summit planning. One caveat on the definition of project for summit
space. Which projects get considered for space is always
On Jan 9, 2015, at 5:28 AM, Thierry Carrez thie...@openstack.org wrote:
Dean Troyer wrote:
On Fri, Jan 9, 2015 at 4:22 AM, Thierry Carrez thie...@openstack.org
mailto:thie...@openstack.org wrote:
This is probably a very dumb question, but could you explain why
Hi
We'd like to ask for a spec freeze exception for the Blue Print on
Quota Management in Nested Projects,kindly see:
https://review.openstack.org/#/c/129420/
The required keystone related bits are already in Kilo, and this proposal will
allow people to actually exploit this new
Dear all,
if you've tried the topics on this mailing list and haven't received
emails, well... we had a problem on our side: the topics were not setup
correctly.
Luigi Toscano helped isolate the problem and point at the solution[1].
He noticed that only the QA topic was working and that's the
(X-posted to -operators.)
Any thoughts on how the ops track spaces would be requested, since there
is not a real ‘operators project’, PTL, etc.?
I assume this would come from the operators group as a whole, so probably
something we should put on the agenda at the ops meet up in March. (I’ve
I like it. Thank you for coming up with improvements to the
summit planning. One caveat on the definition of project for summit
space. Which projects get considered for space is always difficult. Who is
going to fill the rooms they request or are they going to have them mostly
empty? I'm sure the
Regarding SSH Keys and logging into nodes, you need to set the NODEPOOL_SSH_KEY
variable
1. I documented my notes here
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/nodepool/nodepool.yaml.erb.sample#L48
2. This is also documented ‘officially’ here:
sean roberts wrote:
I like it. Thank you for coming up with improvements to the
summit planning. One caveat on the definition of project for summit
space. Which projects get considered for space is always difficult. Who
is going to fill the rooms they request or are they going to have them
On 2015-01-09 08:28:39 -0800 (-0800), Patrick East wrote:
[...]
On a related note, I am having issues with the ssh keys. Nodepool
is able to log in to the node to set up the template and create an
image from it, but then fails to log in to a build node. Have you
run into any issues with that?
Hi Ivan, thanks !!
On Fri, Jan 9, 2015 at 10:42 AM, Ivan Kolodyazhny e...@e0ne.info wrote:
Hi Erlon,
We've got a thread mailing-list [1] for it and some details in wiki [2].
Anyway, need to get confirmation from our core devs and/or Mike.
[1]
Ah yea, sorry, should have specified; I am having it run
the prepare_node_devstack.sh from the infra repo. I see it adding the same
public key to the user specified in my nodepool.yaml. The strange part (and
I need to double check.. feel like it can't be right) is that on my master
node the
If we were standing at a place with a detailed manual upgrade document
that explained how to do minimal VM downtime, that a few ops had gone
through and proved out, that would be one thing. And we could figure out
which parts made sense to put tooling around to make this easier for
everyone.
Thanks Patrick,
Indeed it seems the cloud provider was setting up vms on a bridge whose eth
was DOWN so the vms could not connect to the outside world so the prepare
script was failing.
Looking into that.
Thanks,
Eduard
On Fri, Jan 9, 2015 at 6:44 PM, Patrick East patrick.e...@purestorage.com
On Fri, 2015-01-09 at 10:35 +0100, Thierry Carrez wrote:
One of the issues here is that the wiki also serves as a default
starting page for all things not on www.openstack.org (its main page
is a list of relevant links). So at the same time we are moving
authoritative content out of the wiki
On 1/8/2015 1:28 PM, Matt Riedemann wrote:
On 4/25/2014 4:13 AM, Alexandre Levine wrote:
Joe,
In regard to your first question - yes we'll be going in this direction
very soon. It's being discussed with Randy now.
As for the second question - we'd love to participate in fixing it (in
fact
So the only comment I'll put in is one that I know not everyone agrees
with but might as well throw it out there.
http://freenode.net/channel_guidelines.shtml (this page has a bunch of
useful advice IMHO).
From that; something useful to look/think over at least...
If you're considering
Huge +1 from me. Thank you, Thierry.
-jay
On 01/09/2015 09:50 AM, Thierry Carrez wrote:
Hi everyone,
The OpenStack Foundation staff is considering a number of changes to the
Design Summit format for Vancouver, changes on which we'd very much like
to hear your feedback.
The problems we are
Let's not forget that more than a quarter of OpenStack production deployments
are using the EC2 interface from my memory of the user survey. Our experience
is that the basic functionality is OK but you need to keep into the appropriate
subset.
Any plans for depreciation of the EC2 inside Nova
The response on the review is overwhelmingly positive (or, strictly speaking,
unanimously non-negative).
If anyone has an objection, could you please register it before 12:00 UTC on
Monday, January 12?
https://review.openstack.org/#/c/145025/
thanks,
brian
Thanks for the links!
After digging around in my configs I figured out the issue, I had a typo in
my JENKINS_SSH_PUBLIC_KEY_NO_WHITESPACE (copy pasta cut off a
character...). But I managed to put the right one in the key for nova to
use so it was able to log in to set up the instance, but didn't
Minwoo,
It is important to understand that Icehouse has gone into a security
fixes only mode. It is too late in the stable process to be making
notable changes for anything other than security issues.
The patch for the fork bomb like problem in object-auditor is in
Icehouse:
Minwoo,
The cherry-picks for the contain-updater and object-updater back to
stable/juno are now available for review:
https://review.openstack.org/146211 and https://review.openstack.org/134082
Jay
On 01/08/2015 09:21 AM, Minwoo Bae wrote:
Hi, to whom it may concern:
Jay Bryant and I
On 01/09/2015 01:59 AM, Morgan Fainberg wrote:
That was a copy paste error. The response was meant to be:
Yes, that is the issue, unbounded version on the stable branches.
So if that is the root issue, there are other fixes. Our current policy
of keeping clients uncapped on stable branches
On 08/01/15 05:39, Anant Patil wrote:
1. The stack was failing when there were single disjoint resources or
just one resource in template. The graph did not include this resource
due to a minor bug in dependency_names(). I have added a test case and
fix here:
Hi,
I just noticed that noVNC was disabled by default in devstack (the relevant
change was
https://review.openstack.org/#/c/140860/).
Dear All,
I am trying to integrate Openstack + vCenter + Neutron + VMware dvSwitch
ML2 Mechanism driver.
I deployed a two node openstack environment (controller + compute with KVM)
with Neutron VLAN + KVM using fuel 5.1. Again I installed nova-compute
using yum in controller node and configured
One thing that has come up in the past couple of API WG meetings [1] is just
how useful a proper API definition would be for the OpenStack projects.
By API definition I mean a format like Swagger, RAML, API Blueprint, etc. These
formats are a machine/human readable way of describing your API.
Le 09/01/2015 09:01, Alex Xu a écrit :
Hi, All
There is bug when running nova with ironic
https://bugs.launchpad.net/nova/+bug/1402658
The case is simple: one baremetal node with 1024MB ram, then boot two
instances with 512MB ram flavor.
Those two instances will be scheduling to same
Hi stable-maint people,
We seem to still have a number of issues with stable branch in the gate,
both in Icehouse and Juno. I'd like to help where I can but I have a bit
of a hard time tracking down the remaining failures and things that have
already been worked on (we really need a dashboard
On Fri, Jan 09, 2015 at 09:15:39AM +0800, Lingxian Kong wrote:
There is an excellent post describing this, for your information:
http://blog.oddbit.com/2014/12/22/accessing-the-serial-console-of-your-nova-servers/
Good reference, you can also get some information here:
On 08/01/15 23:46, Matthew Farina wrote:
Thanks for humoring me as I ask these questions. I'm just trying to
connect the dots.
How would system packages work in practice? For example, when it comes
to ubuntu lucid (10.04 LTS) there is no system package meeting the
jQuery requirement and for
On 01/09/2015 11:44 AM, Thierry Carrez wrote:
Hi stable-maint people,
We seem to still have a number of issues with stable branch in the gate,
both in Icehouse and Juno. I'd like to help where I can but I have a bit
of a hard time tracking down the remaining failures and things that have
Some of my comments inline prefixed with deepakcs
On Fri, Jan 9, 2015 at 6:43 AM, Li, Chen chen...@intel.com wrote:
Thanks for the explanations!
Really helpful.
My questions are added in line.
Thanks.
-chen
-Original Message-
From: Ben Swartzlander
Hi all, hi cinder core devs,
I have read on IRC discussions about a deadline for drivers vendors to have
their CI running and voting until kilo-2, but I didn't find any post on
this list to confirm this. Can anyone confirm this?
Thanks,
Erlon
___
There is bug when running nova with ironic
https://bugs.launchpad.net/nova/+bug/1402658
I filed this bug – it has been a problem for us.
The problem is at scheduler side the IronicHostManager will consume all the
resources for that node whatever
how much resource the instance used. But at
boto 2.35.0 just released, and makes hmac-v4 authentication mandatory
for EC2 end points (it has been optionally supported for a long time).
Nova's EC2 implementation does not do this.
The short term approach is to pin boto -
https://review.openstack.org/#/c/146049/, which I think is a fine long
Hi folks,
according to the Fuel client refactoring plan [1] it’s necessary to move it out
to a separate repository on Stackforge.
The process of doing that consists of two major steps:
- Landing a patch [2] to project-config for creating a new Stackforge project
- Creating an initial core group
Adding [api] topic.
On 01/08/2015 07:47 PM, Kevin Benton wrote:
Is there another openstack service that allows this so we can make the
API consistent between the two when this change is made?
Kevin, thank you VERY much for asking the above question and caring
about consistency in the APIs!
Le 09/01/2015 15:07, Murray, Paul (HP Cloud) a écrit :
There is bug when running nova with ironic
https://bugs.launchpad.net/nova/+bug/1402658
I filed this bug – it has been a problem for us.
The problem is at scheduler side the IronicHostManager will consume
all the resources for that
Le 09/01/2015 14:58, Alex Xu a écrit :
2015-01-09 17:17 GMT+08:00 Sylvain Bauza sba...@redhat.com
mailto:sba...@redhat.com:
Le 09/01/2015 09:01, Alex Xu a écrit :
Hi, All
There is bug when running nova with ironic
https://bugs.launchpad.net/nova/+bug/1402658
The
On 01/09/2015 02:25 PM, Ihar Hrachyshka wrote:
Hi all,
I assumed that we still support py26 for clients, but then I saw [1]
that removed corresponding tox environment from ironic client.
What's our take on that? Shouldn't clients still support Python 2.6?
[1]:
On 01/09/2015 02:33 PM, Andreas Jaeger wrote:
On 01/09/2015 02:25 PM, Ihar Hrachyshka wrote:
Hi all,
I assumed that we still support py26 for clients, but then I saw [1]
that removed corresponding tox environment from ironic client.
What's our take on that? Shouldn't clients still support
On 01/09/2015 05:04 AM, Thierry Carrez wrote:
Maru Newby wrote:
On Jan 8, 2015, at 3:54 PM, Sean Dague s...@dague.net wrote:
The crux of it comes from the fact that the operator voice (especially
those folks with large nova-network deploys) wasn't represented there.
Once we got back from the
On 01/09/2015 02:37 PM, Ihar Hrachyshka wrote:
On 01/09/2015 02:33 PM, Andreas Jaeger wrote:
On 01/09/2015 02:25 PM, Ihar Hrachyshka wrote:
Hi all,
I assumed that we still support py26 for clients, but then I saw [1]
that removed corresponding tox environment from ironic client.
What's our
On 09/01/15 01:07, Angus Salkeld wrote:
I am not in favor of the --continue as an API. I'd suggest responding to
resource timeouts and if there is no response from the task, then
re-start (continue)
the task.
Yeah, I am not in favour of a new API either. In fact, I believe we
already have
2015-01-09 17:17 GMT+08:00 Sylvain Bauza sba...@redhat.com:
Le 09/01/2015 09:01, Alex Xu a écrit :
Hi, All
There is bug when running nova with ironic
https://bugs.launchpad.net/nova/+bug/1402658
The case is simple: one baremetal node with 1024MB ram, then boot two
instances with 512MB
Oh hi list!
Feel free to discuss the a project just getting started content that ends
up on the wiki -- where would that go?
Anne
On Thu, Jan 8, 2015 at 9:51 PM, Anne Gentle a...@openstack.org wrote:
Hi Stef, thanks for writing this up. One aspect this proposal doesn't
address is the
Hi Erlon,
We've got a thread mailing-list [1] for it and some details in wiki [2].
Anyway, need to get confirmation from our core devs and/or Mike.
[1]
http://lists.openstack.org/pipermail/openstack-dev/2014-October/049512.html
[2]
Hi all,
I assumed that we still support py26 for clients, but then I saw [1]
that removed corresponding tox environment from ironic client.
What's our take on that? Shouldn't clients still support Python 2.6?
[1]:
hi danny,
if you're using neutron, you can use the option :
NEUTRON_CREATE_INITIAL_NETWORKS=False
in your local.conf.
This way no router or network are created. You have to create it manually,
and of course you can do it once every agent is up is Neutron.
Mathieu
On Thu, Jan 8, 2015 at 3:46
On Fri, Jan 9, 2015 at 4:22 AM, Thierry Carrez thie...@openstack.org
wrote:
This is probably a very dumb question, but could you explain why
keystoneclient.middleware can't map to keystonemiddleware functions
(adding keystonemiddleware as a dependency of future keystoneclient)? At
first
Hi all,
Back with the same error.
Did a complete (clean) install based on rasselin's tutorial, now i have a
working jenkins master + a dedicated cloud provider.
Testing with noop looks ok, but dsvm-tempest-full returns NOT_REGISTERED.
Here is some debug.log:
2015-01-09 14:08:06,772 DEBUG
Ihar Hrachyshka wrote:
On 01/09/2015 11:44 AM, Thierry Carrez wrote:
Another topic is the mentoring of new propose $PROJECT-stable-maint
members. We have a number of proposed people to contact and introduce
the stable branch policy to (before we add them to the group):
Erno Kuvaja
Dean Troyer wrote:
On Fri, Jan 9, 2015 at 4:22 AM, Thierry Carrez thie...@openstack.org
mailto:thie...@openstack.org wrote:
This is probably a very dumb question, but could you explain why
keystoneclient.middleware can't map to keystonemiddleware functions
(adding
-Original Message-
From: Jeremy Stanley [mailto:fu...@yuggoth.org]
Sent: 08 January 2015 22:26
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [horizon] packaging problem production
build question
On 2015-01-08 15:11:24 -0700 (-0700),
Hi everyone,
The OpenStack Foundation staff is considering a number of changes to the
Design Summit format for Vancouver, changes on which we'd very much like
to hear your feedback.
The problems we are trying to solve are the following:
- Accommodate the needs of more OpenStack projects
- Reduce
2015-01-09 22:07 GMT+08:00 Murray, Paul (HP Cloud) pmur...@hp.com:
There is bug when running nova with ironic
https://bugs.launchpad.net/nova/+bug/1402658
I filed this bug – it has been a problem for us.
The problem is at scheduler side the IronicHostManager will consume all
the
Anne Gentle wrote:
Oh hi list!
Feel free to discuss the a project just getting started content that
ends up on the wiki -- where would that go?
I think that's still fine for nascent projects to use the wiki as a
poor man CMS. This hardly qualifies as authoritative content and falls
more into
I understand that you're moving content out of the wiki, which I think will be
fine, as long as the wiki provides links to the new content location. Is that
the intention?
Carol
-Original Message-
From: Thierry Carrez [mailto:thie...@openstack.org]
Sent: Friday, January 09, 2015 1:36
79 matches
Mail list logo
