hi,
Recently, I saw a patch which fixed the listener's admin_state_up
status[1]. This patch is already merged in master branch. But it is not
merged into stable/liberty.
So I upload a new patch[2] to merge that patch into stable/liberty.
[1]: https://review.openstack.org/#/c/266816/
[2]
There is no such blueprint at the moment.
You are more than welcome to add one, in case you have some ideas for
improvements.
Ifat.
From: Yujun Zhang
Date: Monday, 8 August 2016 at 09:21
Great, it works.
But it would be better if we could improve the default layout. Is there any
blueprint in
Great, it works.
But it would be better if we could improve the default layout. Is there any
blueprint in progress?
--
Yujun
On Sun, Aug 7, 2016 at 1:09 PM Afek, Ifat (Nokia - IL)
wrote:
> Hi,
>
> It is possible to adjust the layout of the graph. You can double-click on
> a vertex and it will re
+1 Tom will be a great addition!
On Thu, Aug 04, 2016 at 01:02:06PM +0300, Valeriy Ponomaryov wrote:
> Yeah, Tom consists of experience. +1
>
> On Thu, Aug 4, 2016 at 12:35 PM, Ramana Raja wrote:
>
> > +1. Tom's reviews and guidance are helpful
> > and spot-on.
> >
> > -Ramana
> >
> > On Thurs
Hi Ricardo,
Great to have feedback from real use case. Spyros and I had a
discussion on this in Austin
and we sketched out the implementation. Once you open the blueprint, we
will add the details
and consider additional scenarios.
Ton,
From: Ricardo Rocha
To: "OpenStack Developmen
Tackers,
Here is the agenda for this week's irc meeting,
https://wiki.openstack.org/wiki/Meetings/Tacker
- Announcements
- Newton release deadlines
- Newton priorities - feature / RFE go/no-go check
- Mistral workflow BP
- Open Discussion
Let me know if you've anything else to discuss.
thanks,
On 08/06/2016 08:44 AM, John Dennis wrote:
On 08/05/2016 06:06 PM, Adam Young wrote:
Ah...just noticed the redirect is to :5000, not port :13000 which is
the HA Proxy port.
OK, this is due to the SAML request:
https://identity.ayoung-dell-t1700.test/auth/realms/openstack/protocol/saml";
Cons
Chris, thanks for the blog to explain your idea! It helps me understand
your idea better.
I agree the goal for API interface design in your blog. But one point I
guess you also agree, that is "The interface is easy to understand for API
user". So look at the example of API request flow with gabbi,
2016-08-05 21:16 GMT+08:00 Chris Dent :
> On Tue, 2 Aug 2016, Alex Xu wrote:
>
> Chris have a thought about using ResourceClass to describe Capabilities
>> with an infinite inventory. In the beginning we brain storming the idea of
>> Tags, Tan Lin have same thought, but we say no very quickly, due
Hi,
There are a few additional items needed here before you can use the container
work
from tht in the undercloud.
First, we deploy on Atomic. Atomic already has docker started when it boots.
We can't
use Atomic for the undercloud because there is no yum to install the clients.
The clients
w
Excerpts from Steve Baker's message of 2016-08-08 10:11:29 +1200:
> On 05/08/16 21:48, Ricardo Rocha wrote:
> > Hi.
> >
> > Quick update is 1000 nodes and 7 million reqs/sec :) - and the number
> > of requests should be higher but we had some internal issues. We have
> > a submission for barcelon
On Wed, Jul 27, 2016 at 11:13:03AM -0500, Tony Breeds wrote:
> I'd like to nominate for PTL of the, to be formed, requirements project.
I'd just like to clarify something as I've been asked by several people
privately. The gist of the question is:
You're the Stable PTL if elected to requirem
On 05/08/16 21:48, Ricardo Rocha wrote:
Hi.
Quick update is 1000 nodes and 7 million reqs/sec :) - and the number
of requests should be higher but we had some internal issues. We have
a submission for barcelona to provide a lot more details.
But a couple questions came during the exercise:
HI,
Great to hear it! From the view of Rally team=)
-Best regards, Roman Vasylets
On Sun, Aug 7, 2016 at 10:55 PM, Ricardo Rocha
wrote:
> Hi Ton.
>
> I think we should. Also in cases where multiple volume types are available
> (in our case with different iops) there would be additional parame
Hi,
This feature is under the work. We have made already the great work:
Introduced task format converter [1] and made patch related to DB
refactoring [2]. After we will merge [2] patch we will be able to move on
and implement next work items. [2] was the hardest part thus it takes a lot
of time.
Hi Ton.
I think we should. Also in cases where multiple volume types are available
(in our case with different iops) there would be additional parameters
required to select the volume type. I'll add it this week.
It's a detail though, spawning container clusters with Magnum is now super
easy (and
Added to the agenda of next team meeting:
https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2016-08-09_1600_UTC
.
Best regards,
Hongbin
> -Original Message-
> From: Murali Allada [mailto:murali.all...@rackspace.com]
> Sent: August-04-16 12:38 PM
> To: openstack-dev@lists.op
Hey Koalaians,
See review:
https://review.openstack.org/352101
What I'd like to see happen is everyone working on scale testing commit their
work by pulling down that review, modifying it, and submitting it to gerrit.
Lets not mege it until the OSIC cluster is no longer in our hands. If you w
On Tue, Aug 2, 2016 at 11:29 AM, Thierry Carrez wrote:
>
> Doug Hellmann wrote:
> > [...]
> >> Likewise, what if the Manila project team decides they aren't interested
> >> in supporting Python 3.5 or a particular greenlet library du jour that
> >> has been mandated upon them? Is the only filesyst
Hi, OpenStack Developers,
I came across this rally spec [1]. The spec mentions defining and
executing multiple scenarios
in a single rally task file. However, as this was written about 8month
ago, may I know if this
feature is implemented in rally? If not, is there any related patch?
Thanks in adva
20 matches
Mail list logo
