Hello,
there is some inconsistency here. Currently I'm fixing bug[1] in
fuelmemu. In my fix[2] I changed paths to repos. As I see,
unfortunatly script which you recommend to use does not use this
paths. Instead it have hardcoded values.
Now we need to update paths in two places. Why is that?
1.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks a lot for the reply! I think it raises some good points here
that I would like to clarify with other team members. I don't think
those should interface with the current nomination run, so I spin it
into a separate thread.
Some comments
Hi all,
I've been pushing for a while now to convert devstack to completely use
the identity v3 API as we try to deprecate the v2.0 API. Currently all
the functions in functions-common consume the v3 API via setting --os
-identity-api-version 3 for each command to override the v2 default.
On 10/07/15 12:43, Mark Kirkwood wrote:
Hi,
I am using puppet-swift to deploy a swift multi node cluster (Icehouse),
following the setup in supplied tests/site.pp. I am running into two
issues that seem to be related to the subject above:
1/ Errors when the storage replication services try to
Thanks a lot Brian.
-Paddu
On 8/13/15, 7:59 AM, Brian Haley brian.ha...@hp.com wrote:
On 08/13/2015 04:04 AM, Padmanabhan Krishnan wrote:
Hello,
Is there a Neutron public API to get the list of router ports?
Something similar
to what the command neutron router-port-list {tenant} gives.
On Aug 14, 2015 03:13, Mike Perez wrote:
It gives me great pleasure to nominate Gorka Eguileor for Cinder core.
Gorka's contributions to Cinder core have been much apprecated:
https://review.openstack.org/#/q/owner:%22Gorka+Eguileor%22+project:o
penstack/cinder,p,0035b6410002dd11
60/90
and here's the video:
http://www.ajo.es/post/126667247769/neutron-qos-service-plugin
Cheers,
Miguel Ángel.
Miguel Angel Ajo wrote:
I owe you all a video of the feature to show how does it work.
I was supposed to deliver today, but I've been partly sick during
today,
The script is ready, I
So far we have WSGI support for puppet-keystone pupper-ceilometer.
I'm currently working on other components to easily deploy OpenStack
running API services using apache/wsgi instead of eventlet.
I would like to propose some change in our beaker tests:
stable/kilo:
*
On Fri, Aug 14, 2015 at 6:29 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks a lot for the reply! I think it raises some good points here
that I would like to clarify with other team members. I don't think
those should interface with the
+1 Nice job!
-Ryan
- Original Message -
From: Steven Dake (stdake) std...@cisco.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Friday, August 14, 2015 9:29:10 AM
Subject: [openstack-dev] [kolla] Proposing Swapnil Kulkarni
Hi Rui,
The problem with the following rule is that there are a bunch of hidden
variables in the not cinder:volumes(...) literal. The error message
shows the hidden variables. The syntax restriction is that every variable
in a negative literal must appear in a positive literal in the body.
+1, Swapnil has made a ton of useful contributions and continues to do so :)
On 14/08/15 14:29, Steven Dake (stdake) wrote:
Hi folks,
Swapnil has done a bunch of great technical work, participates heavily in IRC,
and has contributed enormously to the implementation of Kolla. I’d like to see
Hi feisky,
I think thats a great question, not because of port-mapping in particular
:) but because
we need to think on a feature by feature basis and map all the features the
dockers API allow which
we cannot support directly with Neutron API or its services sub-projects
API.
(apuimedo, maybe we
Hi Telles,
you technically don't get a vote, but thanks anyway :)
Trev
On Fri, 2015-08-14 at 12:14 +, Telles Nobrega wrote:
+1
On Fri, Aug 14, 2015 at 7:11 AM Alexander Ignatov
aigna...@mirantis.com wrote:
+1
Regards,
Alexander Ignatov
+1
On 08/13/2015 02:13 PM, Mike Perez wrote:
It gives me great pleasure to nominate Gorka Eguileor for Cinder core.
Gorka's contributions to Cinder core have been much apprecated:
https://review.openstack.org/#/q/owner:%22Gorka+Eguileor%22+project:openstack/cinder,p,0035b6410002dd11
60/90
Hi folks,
Swapnil has done a bunch of great technical work, participates heavily in IRC,
and has contributed enormously to the implementation of Kolla. I’d like to see
more reviews from Swapnil, but he has committed to doing more reviews and
already has gone from something like 0 reviews to
On 08/14/15 at 01:06pm, stuart.mcla...@hp.com wrote:
I got zero responses on the mailing list raising a problem with Glance v2 [1].
I got zero responses on cross project meeting raising a problem with Glance v2
[2].
I'm very happy with my choice of words, because I think this hand slap on
Yeah I know, I'm just supporting :)
On Fri, Aug 14, 2015 at 10:30 AM Trevor McKay tmc...@redhat.com wrote:
Hi Telles,
you technically don't get a vote, but thanks anyway :)
Trev
On Fri, 2015-08-14 at 12:14 +, Telles Nobrega wrote:
+1
On Fri, Aug 14, 2015 at 7:11 AM Alexander
On 08/14/2015 06:47 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/14/2015 08:15 AM, Jamie Lennox wrote:
Hi all,
I've been pushing for a while now to convert devstack to completely
use the identity v3 API as we try to deprecate the v2.0 API.
Currently all the
Hi Eric,
First off welcome to OpenStack! Generally for security related
questions we use the OpenStack-dev mailing list and preface the
subject with a [Security] tag.
One of the functions of a hypervisor is to ensure proper isolation of
tenant VMs. That being said I highly recommend deploying
On Fri, Aug 14, 2015 at 12:43 AM, Mike Perez thin...@gmail.com wrote:
It gives me great pleasure to nominate Gorka Eguileor for Cinder core.
Gorka's contributions to Cinder core have been much apprecated:
This option can not be used in show stack call.
Regards,
Wanghua
On Fri, Aug 14, 2015 at 4:54 PM, 英哲 zengyz1...@live.cn wrote:
Can this option be used for in show stack details call?
Date: Fri, 14 Aug 2015 04:30:19 -0400
From: the...@redhat.com
To: openstack-dev@lists.openstack.org
We can get stacks by stack list call, but it does not provide info about
stack parameters. If we need stack parameters, we have to use stack.get.
Yeah that part is right. I believe we consider stack parameters somewhat
private to the user, which may be the reason they are not easily
On Fri, 14 Aug 2015, Robert Collins wrote:
The vast majority of our developers do not fix such bugs. They react
by blacklisting the proximate cause of the issue - the new release -
locally, submit a patch to openstack/requirements *sometimes* and if
we're really lucky file a bug upstream.
Magnum creates a stack when a bay is created and update the stack
parameters when the bay is updated. Magnum needs a periodic task to synchronize
stack status and parameters from heat to keep data consistency.
Regards,
Wanghua
On Fri, Aug 14, 2015 at 5:02 PM, Thomas Herve the...@redhat.com
Excerpts from Chris Dent's message of 2015-08-14 02:08:28 -0700:
On Fri, 14 Aug 2015, Robert Collins wrote:
The vast majority of our developers do not fix such bugs. They react
by blacklisting the proximate cause of the issue - the new release -
locally, submit a patch to
On 14 August 2015 at 21:08, Chris Dent chd...@redhat.com wrote:
Awesome, thanks for pointing this out, that will be useful.
But again: Underlying my assertion is that we don't _just_ need more
tools and automation we also need to remind ourselves of the kind of
environment that we're
Hi all,
Magnum creates a stack when a bay is created and update the stack
parameters when the bay is updated. Magnum has a periodic task
to synchronize stack status from heat.
And now we want to synchronize stack parameters from heat, too. But heat
don't allow admin user to show stack in other
+1
On Fri, Aug 14, 2015 at 4:05 PM, Deepak Shetty dpkshe...@gmail.com wrote:
On Fri, Aug 14, 2015 at 12:43 AM, Mike Perez thin...@gmail.com wrote:
It gives me great pleasure to nominate Gorka Eguileor for Cinder core.
Gorka's contributions to Cinder core have been much apprecated:
Hi all,
Magnum creates a stack when a bay is created and update the stack
parameters when the bay is updated. Magnum has a periodic task
to synchronize stack status from heat.
And now we want to synchronize stack parameters from heat, too. But heat
don't allow admin user to show stack
On Thu, 13 Aug 2015, Sean M. Collins wrote:
Do we want to make it a default to True for users of DevStack? I think
it may be worth considering since I'm not familiar with this issue
with crypto and having something that protects devs who are trying to
work on stuff and using DevStack , sounds
I just read this thread so decided to add my 2 cents into the collection of
opinions.
Guys, I tried it out a couple of weeks ago (was told about it by one of my
colleagues). This is really incredible! Especially given that you completed it
in 24 hours :) I think as YAQL attracts more and more
Excerpts from 王华's message of 2015-08-14 00:52:43 -0700:
Hi all,
Magnum creates a stack when a bay is created and update the stack
parameters when the bay is updated. Magnum has a periodic task
to synchronize stack status from heat.
And now we want to synchronize stack parameters from
On 14 August 2015 at 20:31, Chris Dent chd...@redhat.com wrote:
On Thu, 13 Aug 2015, Sean M. Collins wrote:
Do we want to make it a default to True for users of DevStack? I think
it may be worth considering since I'm not familiar with this issue
with crypto and having something that protects
The expire time is determined by keystone. Keystone do not allow users to
change it. So it is impossible to get a token which has no expiry.
On Fri, Aug 14, 2015 at 10:42 AM, Adrian Otto adrian.o...@rackspace.com
wrote:
You can specify the timeout when you create it, so it is possible to make
We can get stacks by stack list call, but it does not provide info about
stack parameters. If we need stack parameters, we have to use stack.get.
Regards,
Wanghua
On Fri, Aug 14, 2015 at 4:30 PM, Thomas Herve the...@redhat.com wrote:
Hi all,
Magnum creates a stack when a bay is created
Can this option be used for in show stack details call?
Date: Fri, 14 Aug 2015 04:30:19 -0400
From: the...@redhat.com
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [openstack][magnum][heat]problems for
synchronizing stack parameters from heat
Hi all,
Magnum
From: ildiko.van...@ericsson.com
To: openstack-dev@lists.openstack.org
Date: Fri, 14 Aug 2015 12:57:27 +
Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup
Hi,
I will try to join if I can, I have an overlapping meeting on Tuesdays.
In general I think it
On 08/14/2015 06:51 AM, Matthew Mosesohn wrote:
Gilles,
I already considered this when looking at another openstackclient
issue. Version 1.0.4 has almost no changes from 1.0.3, which is the
official release for Kilo. Maybe we can get this keystone URL handling
fix backported to the 1.0.X
+1
On 8/13/15, 3:13 PM, Mike Perez thin...@gmail.com wrote:
It gives me great pleasure to nominate Gorka Eguileor for Cinder core.
Gorka's contributions to Cinder core have been much apprecated:
https://review.openstack.org/#/q/owner:%22Gorka+Eguileor%22+project:openst
The port mapping feature is the -p flag on the docker run command. It
determines which ports in the network namespace of the container are exposed to
the root namespace. It configures iptables rules and docker proxy capabilities
to achieve the desired result. This feature is essential, so we
There isn't currently any way to directly move a container DB from one drive to
another. As you said, the placement is based on the hash of the container name,
so you can't change that.
One thing you can do is lower the weight of the drive that is very busy. This
will cause less partitions to
On 08/14/2015 09:14 AM, Morgan Fainberg wrote:
As a quick note the api-ref you are linking to has some gaps/has not
been kept in sync with the official api specifications.
The official API specification is located at
http://specs.openstack.org/openstack/keystone-specs/ (v2 and v3 sections
at
On Fri, Aug 14, 2015 at 01:29:10PM +, Steven Dake (stdake) wrote:
Hi folks,
Swapnil has done a bunch of great technical work, participates heavily
in IRC, and has contributed enormously to the implementation of Kolla.
I’d like to see more reviews from Swapnil, but he has committed to
On 08/13/2015 03:13 PM, Mike Perez wrote:
It gives me great pleasure to nominate Gorka Eguileor for Cinder core.
Cinder core, please reply with a +1 for approval. This will be left
open until August 19th. Assuming there are no objections, this will go
forward after voting is closed.
+1
On Fri, Aug 14, 2015 at 10:00 AM, Flavio Percoco fla...@redhat.com wrote:
On 14/08/15 10:42 -0400, Assaf Muller wrote:
First I'd like to say that I recognize that this discussion is incredibly
personal. Brandon and Russell, please do not be offended, but I know that
I
probably would be if
On Fri, Aug 14, 2015 at 9:42 AM, Assaf Muller amul...@redhat.com wrote:
First I'd like to say that I recognize that this discussion is incredibly
personal. Brandon and Russell, please do not be offended, but I know that I
probably would be if this very public thread involved myself. That being
On 14/08/15 10:14 -0500, Kyle Mestery wrote:
On Fri, Aug 14, 2015 at 10:00 AM, Flavio Percoco fla...@redhat.com wrote:
On 14/08/15 10:42 -0400, Assaf Muller wrote:
First I'd like to say that I recognize that this discussion is
incredibly
personal. Brandon and
On 14/08/15 09:29 -0400, Trevor McKay wrote:
Hi Telles,
you technically don't get a vote, but thanks anyway :)
Hi Trevor,
Technically, everyone gets to vote and speak up. Regardless of whether
you're a core-reviewer or not. Most of the time, non-core contributors
provide amazing feedback on
On 09:44 Aug 14, Rick Chen wrote:
HI Mike:
Sorry again, I already add email alert agent in our CI Jenkins
server to capture each failed build result.
[1] -
http://lists.openstack.org/pipermail/third-party-announce/2015-June/000192.h
tml
[2] -
On 14/08/15 10:42 -0400, Assaf Muller wrote:
First I'd like to say that I recognize that this discussion is incredibly
personal. Brandon and Russell, please do not be offended, but I know that I
probably would be if this very public thread involved myself. That being said,
please know that from
For the identity (users and groups) backend as long as we support LDAP (and as
side note federated users never show up in this list anyway) and with the drive
towards pushing all user management out of keystone itself to ldap or other
tools that do it better, I don't see pagination as something
Hi Adrian,
Thanks for the explanation, i agree with you that we shouldn't break
anything useful in docker, but from what i understand
(and please correct me if i am wrong) you are describing an implementation
detail of docker networking (at its default current state).
Kuryr is not an
While this includes me, I'm really not taking this personally. I'm
thinking about it in the general sense.
On 08/14/2015 11:03 AM, Kyle Mestery wrote:
I'd argue the system is built on a web of trust. If you trust me, and I
trust Russell and Brandon, then you should likely trust Russell and
That's clear, thanks Gal. The feature benchmark should be parity with how the
majority of other (complete) remote drivers for libnetwork behave. From a
Magnum perspective we value consistency from an end user perspective when you
use containers on OpenStack compared to when you run them outside
I don't want to jump in where i am not suppose to, and i know everyone
saying it isn't personal, but
i have had the pleasure to work with Russell on the OVN project for the
last couple of months, i think his dedication
to the project and Neutron, his understanding of what open source community
Pagination in ldap requires holding a cursor open. You would have to map the
requests to the same cursor each time. It costs memory and holds a client
connected to the ldap server. In a REST api it is a bad idea. With regard to
searching it can be done, but each query can be a different set of
On Aug 14, 2015, at 12:19, Morgan Fainberg morgan.fainb...@gmail.com wrote:
Pagination in ldap requires holding a cursor open. You would have to map the
requests to the same cursor each time. It costs memory and holds a client
connected to the ldap server. In a REST api it is a bad
Surely ldap supports some form of pagination/searching natively. If any
storage system of users needs to scale up to large numbers of users, its ldap...
Thanks,
Kevin
From: Timur Sufiev [tsuf...@mirantis.com]
Sent: Friday, August 14, 2015 9:20 AM
To: OpenStack
Flavio,
thanks, bad joke on my part. I work with Telles on Sahara, just poking
him in jest. Apologies, didn't mean to create an issue on the list.
Trev
On Fri, 2015-08-14 at 17:30 +0200, Flavio Percoco wrote:
On 14/08/15 09:29 -0400, Trevor McKay wrote:
Hi Telles,
you technically don't
great! +1 :)
Op 14-08-15 om 15:38 schreef Paul Bourke:
+1, Swapnil has made a ton of useful contributions and continues to do
so :)
On 14/08/15 14:29, Steven Dake (stdake) wrote:
Hi folks,
Swapnil has done a bunch of great technical work, participates
heavily in IRC, and has contributed
So I was one of the keystone folks who looked at pagination (hell, I even had
an implementation - and the framework for it still exists in keystone).
However, I think it is true to say that there were as many people (external to
keystone) who thought pagination was a bad idea, as thought it was
I don't have a horse in the What should keystone support race. I do,
however, need to point out that any UX argument made about how a UI should
work should, at this point, ask the OpenStack UX program for help! Thus
I've changed the topic of this email to make sure Piet and the UX teams get
a
Morgan,
Your reasoning is perfectly fine from the Keystone point of view. Yet I
believe this approach is harmful for both Horizon and the whole OpenStack
ecosystem.
It is harmful for the ecosystem, because it breaks API uniformity in one of
the few areas where this uniformity could be achieved.
I would suggest considering docker port mapping as a creation of an
apropriate security group's rule and also creation of something which was
never exist in Neutron before which will be responsible for port
forwarding. This feature could be useful for VMs also instead of/jointly
with using
At the midcycle, we had only 1 session on upgrade, and we didn’t come to any
clear consensus on how it should be handled. I took a stab at writing what I
think are the requirements for upgrade in this blueprint:
https://blueprints.launchpad.net/kolla/+spec/upgrade-strategy
The blueprint can
HI Mike:
Ok, Thanks. I will refine my CI configuration to follow Ramy's
comment. I will notify you when I refine Ramy's comment.
Another my latest review log should been today:
http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds
?Hi Gareth,
The reason for this is because lbaas v1 is in the services/loadbalancer/drivers
path. This path was maintained from when neutron-lbaas was just another
directory in the neutron repo. Once we moved to neutron-lbaas as its own repo
and going forward with lbaas v2, the decision was
I understand the reasoning, but there are use cases for indexing (re:
searchlight) and auditing that are completely unsupported in keystone v3.
As from keystone, I have no way to exhaustively list who has accounts in my
cloud using OpenStack APIs. That seems like a hole that should be filled.
Not
On 08/14/2015 12:43 PM, Michael Krotscheck wrote:
1- Do users want to page through search results?
Does not matter: in Federation, the User list is not available.
2- Do users want to page through filter results? (do they use filter
results?)
This is the only practical tool available for
On Aug 14, 2015, at 15:10, Jay Pipes jaypi...@gmail.com wrote:
On 08/14/2015 05:24 PM, Adam Young wrote:
On 08/14/2015 12:43 PM, Michael Krotscheck wrote:
1- Do users want to page through search results?
Does not matter: in Federation, the User list is not available.
OK, so hobble the
All patches to oslo.messaging are currently failing the
gate-tempest-dsvm-neutron-src-oslo.messaging job because the neutron service
dies. amuller, kevinbenton, and I spent a bunch of time looking at it today,
and I think we have an issue introduced by some asymmetric gating between the
two
+1
It gives me great pleasure to nominate Gorka Eguileor for Cinder core.
Gorka's contributions to Cinder core have been much apprecated:
https://review.openstack.org/#/q/owner:%22Gorka+Eguileor%22+project:openstack/cinder,p,0035b6410002dd11
60/90 day review stats:
Hi,
As mentioned previously[1], we are retiring the stackforge/ namespace
for git repositories and creating new projects in openstack/. This is
largely a cosmetic change and does not change the governance model for
new projects.
As part of this we want to move all of the projects that are
On Aug 14, 2015, at 14:22, Adam Young ayo...@redhat.com wrote:
On 08/14/2015 02:31 PM, David Lyle wrote:
I understand the reasoning, but there are use cases for indexing (re:
searchlight) and auditing that are completely unsupported in keystone v3. As
from keystone, I have no way to
On 08/14/2015 06:30 PM, Morgan Fainberg wrote:
On Aug 14, 2015, at 15:10, Jay Pipes jaypi...@gmail.com wrote:
On 08/14/2015 05:24 PM, Adam Young wrote:
On 08/14/2015 12:43 PM, Michael Krotscheck wrote:
1- Do users want to page through search results?
Does not matter: in Federation, the User
On 08/14/2015 02:31 PM, David Lyle wrote:
I understand the reasoning, but there are use cases for indexing (re:
searchlight) and auditing that are completely unsupported in keystone
v3. As from keystone, I have no way to exhaustively list who has
accounts in my cloud using OpenStack APIs. That
It's Friday, no fear.
Our Beaker (functional testing) jobs now deploy OpenStack Liberty using
RDO (delorean which is trunk) and Liberty-Staging (Ubuntu).
It will allow people to push features in master that are Liberty specific.
Some recommendation for our group though:
* please report on
Fox, Kevin M kevin@pnnl.gov writes:
What is the process for current stackforge projects to move into the
openstack namespace then? Is it a simple request now, or a more
complicated process?
Great question. I have proposed a process for that in a new thread:
On 08/14/2015 05:24 PM, Adam Young wrote:
On 08/14/2015 12:43 PM, Michael Krotscheck wrote:
1- Do users want to page through search results?
Does not matter: in Federation, the User list is not available.
OK, so hobble the entire REST API for the
deficiencies/architecture/reality of a
Currently, The FCZM doesn't support this. Also, from my experience
Brocade and Cisco switches don't play well together when managing the
same fabrics.
Walt
Hi, guys
I am using Brocade FC switch in my OpenStack environment. I have
a question about OpenStack cinder zonemanger driver.
On Fri, Aug 14, 2015 at 3:55 PM, Jay Pipes jaypi...@gmail.com wrote:
On 08/14/2015 06:30 PM, Morgan Fainberg wrote:
On Aug 14, 2015, at 15:10, Jay Pipes jaypi...@gmail.com wrote:
On 08/14/2015 05:24 PM, Adam Young wrote:
On 08/14/2015 12:43 PM, Michael Krotscheck wrote:
1- Do users want
On Fri, Aug 14, 2015 at 6:06 PM, Walter A. Boring IV walter.bor...@hp.com
wrote:
+1
It gives me great pleasure to nominate Gorka Eguileor for Cinder core.
Gorka's contributions to Cinder core have been much apprecated:
On Thu, Aug 13, 2015 at 11:01 PM, Guo, Ruijing ruijing@intel.com
wrote:
If you can commit it to devstack, it will benefit everyone
-Original Message-
From: Tony Breeds [mailto:t...@bakeyournoodle.com]
Sent: Friday, August 14, 2015 12:21 PM
To: OpenStack Development Mailing List
On Fri, Aug 14, 2015 at 10:03 PM, John Griffith john.griffi...@gmail.com
wrote:
On Thu, Aug 13, 2015 at 11:01 PM, Guo, Ruijing ruijing@intel.com
wrote:
If you can commit it to devstack, it will benefit everyone
-Original Message-
From: Tony Breeds
I vote for #3. ;)
But seriously, please do help review it so we make sure everyone's use cases
are handled ok.
Thanks,
Kevin
From: 王华 [wanghua.hum...@gmail.com]
Sent: Thursday, August 13, 2015 6:25 PM
To: OpenStack Development Mailing List (not for usage
Today, trusts can only be scoped to roles, not to individual files/containers.
And its only subtractive. So you can only drop roles to restrict roles granted.
Most OpenStack services today don't use many roles, so they are mostly all or
nothing (only Member role for example). So Trusts usually
On 13/08/15 23:29, Rich Megginson wrote:
On 08/13/2015 12:41 AM, Gilles Dubreuil wrote:
Hi Matthew,
On 11/08/15 01:14, Rich Megginson wrote:
On 08/10/2015 07:46 AM, Matthew Mosesohn wrote:
Sorry to everyone for bringing up this old thread, but it seems we may
need more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/14/2015 08:15 AM, Jamie Lennox wrote:
Hi all,
I've been pushing for a while now to convert devstack to completely
use the identity v3 API as we try to deprecate the v2.0 API.
Currently all the functions in functions-common consume the v3
I have checked with infra team members. For two instances, 10GB each should
be OK.
So I add some steps to create magnum specific flavor(8 GB disk), instead of
use the existed devstack flavors (m1.small needs 20GB, m1.tiny can not be
used)
Magnum creates one for jenkins job and delete it when
I got zero responses on the mailing list raising a problem with Glance v2 [1].
I got zero responses on cross project meeting raising a problem with Glance v2
[2].
I'm very happy with my choice of words, because I think this hand slap on
Glance is the first time I got acknowledgement in my
+1
On Fri, Aug 14, 2015 at 7:11 AM Alexander Ignatov aigna...@mirantis.com
wrote:
+1
Regards,
Alexander Ignatov
On 13 Aug 2015, at 18:29, Sergey Reshetnyak sreshetn...@mirantis.com
wrote:
+2
2015-08-13 18:07 GMT+03:00 Matthew Farrellee m...@redhat.com:
On 08/13/2015 10:56 AM,
On 2015-08-14 10:52:55 +0100 (+0100), Chris Dent wrote:
On Fri, 14 Aug 2015, Clint Byrum wrote:
The same is true for these bugs. Yes they're real, yes more orgs
should devote developers to fixing them.
This may be the root of my concern and something that we're going
to have to address
On Fri, Aug 14, 2015 at 05:34:59PM +0800, 王华 wrote:
Hi Clint Byrum,
Trusts can solve this problem, but it may cause performance problem.
When we want to get a stack, we need to get the trust_id from db first,
andA
authenticate with the trust_id, then we can get the stack. A
On 14/08/15 13:06 +0100, stuart.mcla...@hp.com wrote:
I got zero responses on the mailing list raising a problem with Glance v2 [1].
I got zero responses on cross project meeting raising a problem with Glance v2
[2].
I'm very happy with my choice of words, because I think this hand slap on
Hi,
I will try to join if I can, I have an overlapping meeting on Tuesdays.
In general I think it would be really good to start a closer collaboration, the
componentization work in Ceilometer gives a really good opportunity as Chris
described.
Best Regards,
Ildikó
-Original Message-
Hello, Keystone folks!
I've just discovered an unfortunate fact that Horizon pagination for
Tenants/Projects list that worked with Keystone v2 doesn't work with
Keysone v3 anymore - its API call simply lacks the 'marker' and 'limit'
parameters [1] that Horizon is relying upon. Meanwhile having
Gilles,
I already considered this when looking at another openstackclient issue.
Version 1.0.4 has almost no changes from 1.0.3, which is the official
release for Kilo. Maybe we can get this keystone URL handling fix
backported to the 1.0.X branch of openstackclient?
-Matthew
On Fri, Aug 14,
On 14/08/15 20:45, Gilles Dubreuil wrote:
On 13/08/15 23:29, Rich Megginson wrote:
On 08/13/2015 12:41 AM, Gilles Dubreuil wrote:
Hi Matthew,
On 11/08/15 01:14, Rich Megginson wrote:
On 08/10/2015 07:46 AM, Matthew Mosesohn wrote:
Sorry to everyone for bringing up this old thread, but
Hi Clint Byrum,
Trusts can solve this problem, but it may cause performance problem.
When we want to get a stack, we need to get the trust_id from db first, and
authenticate with the trust_id, then we can get the stack.
On Fri, Aug 14, 2015 at 5:13 PM, Clint Byrum cl...@fewbar.com wrote:
1 - 100 of 104 matches
Mail list logo
