Hi,
I stumbled into a situation today where in I had to write few tests that
modifies the oslo.config.cfg and in turn resets the values back in a tear
down. Acc to the docs, oslo.cfg reset() *Clears the object state and
unsets overrides and defaults. *but, it doesn't seem to be happening, as
Hello, Adam.
On Tue, Dec 10, 2013 at 6:55 PM, Adam Young ayo...@redhat.com wrote:
With only a change to the import and requirements, it builds and runs,
but raises:
Traceback (most recent call last):
File keystone/tests/test_revoke.py, line 65, in test_list_is_sorted
These look good! Quick question - can you explain the purpose of Node Tags?
Are they
an additional way to filter nodes through nova-scheduler (is that even
possible?), or
are they there solely for display in the UI?
Mainn
- Original Message -
Thanks everybody for your feedback.
Hey folks,
after a bit longer but very useful discussion about requirements (almost
60 e-mails so far) I think we need to get to some conclusion what to
deliver in Icehouse, what are the steps and what we should continue
discussing to get better understanding for. Time is running mercilessly
Russell Bryant wrote:
$ git shortlog -s -e | sort -n -r
172John Wood john.w...@rackspace.com
150jfwood john.w...@rackspace.com
65Douglas Mendizabal douglas.mendiza...@rackspace.com
39Jarret Raim jarret.r...@rackspace.com
17Malini K.
Nice list! Questions and comments in-line:
- Original Message -
Hey folks,
after a bit longer but very useful discussion about requirements (almost
60 e-mails so far) I think we need to get to some conclusion what to
deliver in Icehouse, what are the steps and what we should
Nice list! Questions and comments in-line:
- Original Message -
Hey folks,
after a bit longer but very useful discussion about requirements (almost
60 e-mails so far) I think we need to get to some conclusion what to
deliver in Icehouse, what are the steps and what we should
Robert Collins wrote:
Confirmed The bug was reproduced or confirmed as a genuine bug
Triaged The bug comments contain a full analysis on how to properly
fix the issue
From wiki.openstack.org/wiki/Bugs
Putting aside the difficulty of complete reproduction sometimes, I
don't understand
On 2013/13/12 11:20, Tzu-Mainn Chen wrote:
These look good! Quick question - can you explain the purpose of Node Tags?
Are they
an additional way to filter nodes through nova-scheduler (is that even
possible?), or
are they there solely for display in the UI?
Mainn
We start easy, so that's
Can neutron manage the networking for bare metal instance created by
ironic/nova-baremetal
Can we assign floating IPs using neutron to bare metal instances
Also, what features of neutron can be used with ironic/nova-baremetal
Thanks,
Tushar Bankar
--
*Disclaimer*
The information
Dear All,
My blueprint for Python-troveclient tests (
https://blueprints.launchpad.net/tempest/+spec/add-python-troveclient-tests)
has been approved.
I have wrote the tests (https://review.openstack.org/#/c/61937/).
Now wait for a trove infrastructure in tempest gates to verify the changes.
Quick note - I want to keep this discussion a bit high-level and not to
get into big implementation details. For everyone, please, let's agree
in this thread on the direction and approach and we can start follow-up
threads with bigger details of how to get those things done.
On 2013/13/12
On 12.12.2013 17:10, Mark McLoughlin wrote:
On Wed, 2013-12-11 at 13:33 +0100, Jiří Stránský wrote:
Hi all,
TL;DR: I believe that As an infrastructure administrator, Anna wants a
CLI for managing the deployment providing the same fundamental features
as UI. With the planned architecture
Hi,
Just noticed the following configuration options in heat.conf(.sample),
I'm wondering if some of them are not so relevant now. Leaving these
options
there may cause some confusion, especially for new comers like me.
Some of the options may be place holders for future extension, some
Hi wu jiang,
On Wed, Dec 11, 2013 at 12:26 PM, wu jiang win...@gmail.com wrote:
Hi Chris Rob,
Thanks for your reply ,and sorry for my late response..
- I tested again. The modification won't effect tempest test because it's
an optional argument, so I can commit it later in tempest.
On 12.12.2013 17:10, Mark McLoughlin wrote:
On Wed, 2013-12-11 at 13:33 +0100, Jiří Stránský wrote:
Hi all,
TL;DR: I believe that As an infrastructure administrator, Anna wants a
CLI for managing the deployment providing the same fundamental features
as UI. With the planned
On 12/13/2013 11:36 AM, Jaromir Coufal wrote:
*VERSION 0*
===
Enable user to deploy OpenStack with the simpliest TripleO way, no
difference between hardware.
Target:
- end of icehouse-2
Features we need to get in:
- Enable manual nodes registration (Ironic)
- Get images available for
Horizoners,
As discussed in TripleO and Horizon meetings, we are proposing to move
Tuskar UI under the Horizon umbrella. Since we are building our UI
solution on top of Horizon, we think this is a good fit. It will allow
us to get feedback and reviews from the appropriate group of developers.
On 12/12/2013 04:46 PM, Robert Collins wrote:
Hi, I'm trying to overhaul the bug triage process for nova (initially)
to make it much lighter and more effective.
I'll be sending a more comprehensive mail shortly
before you do, let's agree what we're trying to solve. Perhaps you were
going to
On Dec 13, 2013, at 8:04 AM, Jaromir Coufal jcou...@redhat.com wrote:
On 2013/12/12 15:31, Mike Scherbakov wrote:
Folks,
Most of you by now have heard of Fuel, which we’ve been working on as a
related OpenStack project for a period of time
-https://github.com/stackforge/fuel-mainsee
On Tue, 10 Dec 2013, Ian Wells wrote:
On 10 December 2013 20:55, Clint Byrum cl...@fewbar.com wrote:
If it is just a network API, it works the same for everybody. This
makes it simpler, and thus easier to scale out independently of compute
hosts. It is also something we already support
+1 in support of Sandy. He is a proven contributor and reviewer and he
brings a great business vision and experience to the team.
Cheers,
Nick
On Wed, Dec 11, 2013 at 8:18 PM, Gordon Chung chu...@ca.ibm.com wrote:
To that end, I would like to nominate Sandy Walsh from Rackspace to
* ability to 'preview' changes going to the scheduler
What does this give you? How detailed a preview do you need? What
information is critical there? Have you seen the proposed designs for
a heat template preview feature - would that be sufficient?
Will will probably have a better answer to
Robert,
As you've deliberately picked on me I feel compelled to reply!
Jokes apart, I am going to retire that patch and push the new default in
neutron. Regardless of considerations on real loads vs gate loads, I think
it is correct to assume the default configuration should be one that will
On 12/12/13 17:52 +0100, Thierry Carrez wrote:
Russell Bryant wrote:
On 12/12/2013 11:23 AM, Justin Hammond wrote:
I am a developer who is currently having troubles keeping up with the
mailing list due to volume, and my inability to organize it in my client.
I am nearly forced to use Outlook
Good point...
In this case however, couldn't you solve this by simply allowing the user
to specify a list of multiple id's for both the datastore-id's and
datastore-version-id's? That way the user can directly control which
configurations apply to different types and versions (choosing to apply
Excerpts from Scott Moser's message of 2013-12-13 06:28:08 -0800:
On Tue, 10 Dec 2013, Ian Wells wrote:
On 10 December 2013 20:55, Clint Byrum cl...@fewbar.com wrote:
If it is just a network API, it works the same for everybody. This
makes it simpler, and thus easier to scale out
On 13/12/13 15:53 +0100, Thierry Carrez wrote:
Hi everyone,
TL;DR:
Incubation is getting harder, why not ask efforts to apply for a new
program first to get the visibility they need to grow.
Long version:
Last cycle we introduced the concept of Programs to replace the
concept of Official
As per Anita's email, we're not to approve anything until the following tox fix
merges: https://review.openstack.org/#/c/60825
Please keep an eye on the change, and once it merges, make sure that the
following patches merge before regular approval rules resume:
Hi Alessandro,
it's a good idea to setup an IRC meeting for the unified agents. IMO it'll
seriously speedup discussion. The first one could be used to determine the
correct direction, then we can use them to discuss details and coordinate
efforts, it will be necessary regardless of the approach.
On 12/13/2013 10:37 AM, Flavio Percoco wrote:
On 13/12/13 15:53 +0100, Thierry Carrez wrote:
Hi everyone,
TL;DR: Incubation is getting harder, why not ask efforts to apply
for a new program first to get the visibility they need to grow.
Long version:
Last cycle we introduced the
On Dec 12, 2013, at 1:39 PM, devdatta kulkarni
devdatta.kulka...@rackspace.com wrote:
We followed on the Zuul question in this week's git-integration working group
meeting.
mordred has created an etherpad with a high-level description of Zuul and how
it might
fit with Solum't git
On 13 December 2013 16:13, Alessandro Pilotti
apilo...@cloudbasesolutions.com wrote:
2) The HTTP metadata service accessible from the guest with its magic
number is IMO quite far from an optimal solution. Since every hypervisor
commonly
used in OpenStack (e.g. KVM, XenServer, Hyper-V, ESXi)
Hello all,
On Wednesday, at the ML2 meeting we had an agenda item[1] to discuss the
blueprint ovs-firewall-driver’s progress and technical challenges. We didn’t
have time to discuss everything, so at the suggestion of Bob K. I am scheduling
a meeting for Monday.
Looking at the calendar of
While I agree with most of what Thierry said, I need clarifications though,
on what a Program is, and what is the key point where an idea should get
its own Program instead of being headed by an already existing Program.
For example, take Barbican which is providing extra features to Keystone,
or
On Fri, Dec 13, 2013 at 03:04:09PM +0100, Imre Farkas wrote:
On 12/13/2013 11:36 AM, Jaromir Coufal wrote:
*VERSION 0*
===
Enable user to deploy OpenStack with the simpliest TripleO way, no
difference between hardware.
Target:
- end of icehouse-2
Features we need to get in:
Sylvain Bauza wrote:
While I agree with most of what Thierry said, I need clarifications
though, on what a Program is,
A team is a group of people working on a given mission. They can be
freely created. They apply to become an OpenStack Program if they feel
their (well-established) mission is
Excerpts from Alessandro Pilotti's message of 2013-12-13 07:13:01 -0800:
Hi guys,
This seems to become a pretty long thread with quite a lot of ideas. What do
you think about setting up a meeting on IRC to talk about what direction to
take?
IMO this has the potential of becoming a
On Mon Dec 9 15:22:04 2013, Robert Collins wrote:
On 9 December 2013 23:56, Jaromir Coufal jcou...@redhat.com wrote:
Ironic today will want IPMI address + MAC for each NIC + disk/cpu/memory
stats
For registration it is just Management MAC address which is needed right? Or
does Ironic need
On 13/12/13 10:44 -0500, Russell Bryant wrote:
On 12/13/2013 10:37 AM, Flavio Percoco wrote:
On 13/12/13 15:53 +0100, Thierry Carrez wrote:
Hi everyone,
TL;DR: Incubation is getting harder, why not ask efforts to apply
for a new program first to get the visibility they need to grow.
Long
Thanks Thierry.
AFAIK, Compute (Nova) is not having yet its own mission statement, so I
guess any project with different people than regular Nova ATCs should
consider an request for new Program if they feel there is difference in
terms of feature delivery ?
-Sylvain
2013/12/13 Thierry Carrez
Apologies for the miss, I just double-checked and Nova does have its own
mission statement :
http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml
Thanks,
-Sylvain
2013/12/13 Sylvain Bauza sylvain.ba...@gmail.com
Thanks Thierry.
AFAIK, Compute (Nova) is not having
Excerpts from Sergey Lukjanov's message of 2013-12-13 07:46:34 -0800:
Hi Alessandro,
it's a good idea to setup an IRC meeting for the unified agents. IMO it'll
seriously speedup discussion. The first one could be used to determine the
correct direction, then we can use them to discuss
-Original Message-
From: Krishna Raman kra...@gmail.com
Sent: Friday, December 13, 2013 9:44am
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Solum] Using Zuul in the Git-pull blueprint
On Dec 12, 2013, at
That's a great idea. How about the proposal below be changed such that the
metadata-proxy forwards the /connect like calls to marconi queue A, and the
response like ur's go to queue B.
The agent wouldn't need to know which queue's in marconi its talking to then,
and could always talk to it.
On 13/12/13 11:36 +0100, Jaromir Coufal wrote:
*VERSION 0*
===
Enable user to deploy OpenStack with the simpliest TripleO way, no
difference between hardware.
Target:
- end of icehouse-2
Features we need to get in:
- Enable manual nodes registration (Ironic)
- Get images available
On 2013-12-13 02:44, Amala Basha Alungal wrote:
Hi,
I stumbled into a situation today where in I had to write few tests that
modifies the oslo.config.cfg and in turn resets the values back in a tear
down. Acc to the docs, oslo.cfg reset() _Clears the object state and unsets
That's exactly why I proposed Marconi :
- Notifications ('Marconi') is already an incubated Openstack program and
consequently we need to envisage any already existing solutions in the
Openstack ecosystem before writing a new one (aka. silos...)
- Salt and other any other solutions are good but
On Dec 13, 2013, at 8:56 AM, devdatta kulkarni
devdatta.kulka...@rackspace.com wrote:
-Original Message-
From: Krishna Raman kra...@gmail.com
Sent: Friday, December 13, 2013 9:44am
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
On Dec 13, 2013, at 9:32 AM, Georgy Okrokvertskhov
gokrokvertsk...@mirantis.com wrote:
Hi,
After reading the etherpad for Solum\Zuul integration I feel that I need more
clarity on this. First of all, what is missed is a positioning of Zuul in
overall Solum architecture. Let me explain a
On Thu, Dec 12, 2013 at 9:22 PM, Christopher Yeoh cbky...@gmail.com wrote:
On Fri, Dec 13, 2013 at 4:12 AM, Jay Pipes jaypi...@gmail.com wrote:
On 12/11/2013 11:47 PM, Mike Perez wrote:
On 10:06 Thu 12 Dec , Christopher Yeoh wrote:
On Thu, Dec 12, 2013 at 8:59 AM, Doug Hellmann
18:39 , Clint Byrum cl...@fewbar.com wrote:
Excerpts from Alessandro Pilotti's message of 2013-12-13 07:13:01 -0800:
Hi guys,
This seems to become a pretty long thread with quite a lot of ideas. What do
you think about setting up a meeting on IRC to talk about what direction to
take?
Hi,
I have definitely seen a drop off in the proposed Container-Service API
discussion. I think peple are still mauling over the ideas that were
presented so far. However with looking at the discussion so far, and
possibly trying to get the discussion going again, I don't think we are at
the
Hi,
Recently a Heater proposal was announced in openstack-dev mailing list.
This discussion lead to a decision to add unified metadata service \
catalog capabilities into Glance.
On the Glance weekly meeting this initiative was discussed and Glance team
agreed to take a look onto BPs and API
On 2013/13/12 11:20, Tzu-Mainn Chen wrote:
These look good! Quick question - can you explain the purpose of Node
Tags? Are they
an additional way to filter nodes through nova-scheduler (is that even
possible?), or
are they there solely for display in the UI?
Mainn
We start
On Fri, 13 Dec 2013, Fox, Kevin M wrote:
Hmm.. so If I understand right, the concern you started is something like:
* You start up a vm
* You make it available to your users to ssh into
* They could grab the machine's metadata
I hadn't thought about that use case, but that does sound
Thanks for the reply! Let me try and address one particular section for now,
since it seems to be the part causing the most confusion:
* SERVICE CLASS - a further categorization within a service role for a
particular deployment.
* NODE PROFILE - a set of requirements
Thanks Mainn, comments inline :)
On Fri, 2013-12-13 at 19:31 -0500, Tzu-Mainn Chen wrote:
Thanks for the reply! Let me try and address one particular section for now,
since it seems to be the part causing the most confusion:
* SERVICE CLASS - a further categorization within a service
I've now pulled out jobs from the gate queue on stable/grizzly for both
heat and keystone. The docs jobs are still broken in stable/grizzly on
both of those trees, which means that pushing a commit to the Gate will
100% fail.
But worse than that, what will actually happen is it will fail. Get
Hi All,
At present cinder driver can be only configured with adding entries in conf
file. Once these driver related entries are modified or added in conf file,
we need to restart cinder-volume service to validate the conf entries and
create a child process that runs in background.
I am thinking
60 matches
Mail list logo
