Hello,
Is there any method to move A container DB to another container server of
different physical disk of original one ?
I have a very large container (having 70 million objects).
This container IO makes other customer's container read/write operation very
slow, so I'd like to move it to anot
Hi Alex,
Finally we have it! Thank you. BTW, any chance to use upstream infra
[1] for this purpose?
[1] http://specs.openstack.org
Thanks,
Igor
On Mon, Aug 10, 2015 at 6:11 PM, Alexander Charykov
wrote:
> Hello all.
>
> We have launched fuel specs service at [1] where you can read fuel
> proje
Thanks to all that attended the Monasca Mid-cycle Meetup last week. The
meet-up was well attended and we had good overviews, content and
discussions.
The minutes for the meetup are at,
https://etherpad.openstack.org/p/monasca_liberty_mid_cycle. If anyone
would like to discuss further or would like
@Duncan and John, I have a idea about this issue, if volume is in-use but
the instance which it's attached to is power-off, so can we avoid data
corruption? If it's true, cinder could free the "available" restriction,
let user decide if they want to restore the boot disk, and they should shut
down
@Duncan and John, thank you both and I have understood this. The reason I
ask this question is we can't restore the boot volume of instance which is
boot-from-volume, since Nova can't detach the boot disk now. So we need to
figure out a way to solve this issue.
Maybe we should let nova can detach
Hi, I didn't reproduce this bug, maybe you can explain more details.
On Tue, Aug 11, 2015 at 8:37 AM, 郑岳 wrote:
> Hello everyone:
> I found a bug in openstack about project's quota usage in newest version.
>
> The link of bug description: https://bugs.launchpad.net/nova/+bug/1482444
>
> Reproduc
I did it using the master branch.
On Tue, Aug 11, 2015 at 10:58 AM, Zhenyu Zheng
wrote:
> Hi, I didn't reproduce this bug, maybe you can explain more details.
>
> On Tue, Aug 11, 2015 at 8:37 AM, 郑岳 wrote:
>
>> Hello everyone:
>> I found a bug in openstack about project's quota usage in newest
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
As of Mon, Aug 10 (diff with Aug 3)
- Open: 142. 6 new (-2), 50 in progress (+2), 0 critical, 12 high and 9
incomplete
- Nova bugs with Ironi
-Original Message-
From: Doug Hellmann [mailto:d...@doughellmann.com]
Sent: Monday, August 10, 2015 4:00 PM
To: openstack-dev
Subject: Re: [openstack-dev] [oslo] Question on oslo_i18n._message
Excerpts from Okuma, Wayne's message of 2015-08-10 21:22:09 +:
> Hello All,
>
> I have a
Haha, thanks Everett, you're totally right.
Anyway, with or without "f_", I want to ensure we will use "updated_at
=gte:some_timestamp" like guideline said, or use "changes-since=
some_timestamp". Since I think this function it's useful to query resources
and we should introduce it into projects(s
On Sun, Aug 9, 2015 at 11:59 PM, Tony Breeds
wrote:
> Hi All,
> Nova has bug: https://bugs.launchpad.net/nova/+bug/1447679 (service
> No-VNC
> (port 6080) doesn't require authentication).
>
> Which explains that if you know the 'token'[1] associated with an instances
> console you can get acc
- Original Message -
> From: "Jamie Lennox"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Tuesday, 11 August, 2015 10:09:33 AM
> Subject: Re: [openstack-dev] [Keystone] [Horizon] Federated Login
>
>
>
> - Original Message -
> > From: "David C
Hello everyone:
I found a bug in openstack about project's quota usage in newest version.
The link of bug description: https://bugs.launchpad.net/nova/+bug/1482444
Reproduce steps:
1. Enable soft delete via set reclaim_instance_interval in nova.conf.
2. A normal project: ProjectA create a new i
On Mon, Aug 10, 2015 at 01:34:03PM -0400, Andrew Laski wrote:
> I'm only one data point, but we have a short TTL on tokens so it is not
> something that our users could reasonably due. And the Nova default TTL is
> 10 minutes, which is also out of bookmarking range IMO.
So that's a good point.
Hello Anita,
Thank you for the email and for checking into the Postman open ness! There
might be some mis-comunication here. Postman is not an official part of the
project and never will be. Neither will any non-open source code base. As
mentioned in the IRC logs, I personally like to perform a
- Original Message -
> From: "David Chadwick"
> To: openstack-dev@lists.openstack.org
> Sent: Tuesday, 11 August, 2015 12:50:21 AM
> Subject: Re: [openstack-dev] [Keystone] [Horizon] Federated Login
>
>
>
> On 10/08/2015 01:53, Jamie Lennox wrote:
> >
> >
> > - Original Message
On 08/10/2015 06:28 PM, Tripp, Travis S wrote:
> At our last weekly IRC meeting we decided that we should have a short video
> conference meetup to talk about the Liberty 3 release. The purpose will be to
> walk through the Liberty Blueprints / Bugs and finalize the list for Liberty
> 3. I promi
Excerpts from Okuma, Wayne's message of 2015-08-10 21:22:09 +:
> Hello All,
>
> I have a question on the usage of oslo_i18n._message and hope to get an
> answer.
>
> Some background first:
> I'm working on a portion of Glance - the Glance Metadata Definitions (i.e.,
> metadefs) section.
> W
On Aug 9, 2015, at 11:03 PM, hao wang
mailto:sxmatch1...@gmail.com>> wrote:
Hi, stackers
Since now we have merged filtering guideline[1], is that said we should
implement this feature according this guideline? like this:
"GET /app/items?f_updated_at=gte:some_timestamp"
Do we have reached a c
At our last weekly IRC meeting we decided that we should have a short video
conference meetup to talk about the Liberty 3 release. The purpose will be to
walk through the Liberty Blueprints / Bugs and finalize the list for Liberty 3.
I promised to create a doodle poll for choosing the time, so h
Hello All,
I have a question on the usage of oslo_i18n._message and hope to get an answer.
Some background first:
I'm working on a portion of Glance - the Glance Metadata Definitions (i.e.,
metadefs) section.
We have about ~20 .JSON files which hold data. The .JSON files get loaded into
the Gla
Hmmm,
I'm pretty sure what u want exists,
For example:
https://github.com/openstack/taskflow/blob/master/taskflow/examples/persistence_example.py
That uses sqlite (or a file) to store information,
U just have to decide what backend is best for u,
Is that what u are looking for? (or possibly
Hi all,
(I've been away for a couple of weeks and I tried to send this before I
left. I didn't see it come through so my apologies if this is the second
time you've seen this.)
I recall markvan mentioning a while ago that there was a need for services
to restart when the underlying package change
Hi folks,
We had about 40 blueprints for Kolla marked for L3. Our community can
typically process about 20-25 blueprints in a 1 month period. As a result, I
pushed a bunch of blueprints to Mitaka, and got our blueprint count down to
about 24 blueprints. The Essential/High blueprints are what
On 08/10/2015 10:24 AM, Rich Megginson wrote:
>> As an operator, I like the "::$domain" notation. I think the benefits it
>> brings in terms of clarity outweigh any downsides.
>
> If you have to add "::$domain" to all of your manifests and supporting
> code, what impact does that have?
Practically
On 4 August 2015 at 12:20, Jim Rollenhagen wrote:
> On Mon, Jul 27, 2015 at 01:35:25PM -0700, Jim Rollenhagen wrote:
> >
> > Now we've landed a patch[0] with a new version (1.11) that is not
> > backward compatible. It causes newly added Node objects to begin life in
> > the ENROLL state, rather
Hi all,
As I understand it, the persistence and related backends are intended to store
atom and flow state. This will only persist until the end of an entirely
successful run (unless explicitly configured to not purge for auditing and
other such reasons). My question is: Is there a way to confi
Hi everyone,
The openstack-ansible community is pleased to announce our release of the
Kilo 11.1.0 milestone.
This release fixes 57 bugs and implements 4 major blueprints, including:
* Keystone as a Federated Identity Provider
* Keystone as a Federated Service Provider
* Horizon Federation Singl
On 08/10/15 at 03:59pm, Tony Breeds wrote:
Hi All,
Nova has bug: https://bugs.launchpad.net/nova/+bug/1447679 (service No-VNC
(port 6080) doesn't require authentication).
Which explains that if you know the 'token'[1] associated with an instances
console you can get access to said console wit
On 08/10/2015 10:45 AM, Richard Raseley wrote:
On 08/07/2015 01:58 PM, Rich Megginson wrote:
Would someone who actually has to deploy/maintain puppet manifests and
supporting code chime in here? How do you feel about having to ensure
that every domain scoped Keystone resource name must end in
"
It appears that the patch related to this discussion were rushed through
rather quickly, and without appropriate updates to the documentation. The
documentation of the library no longer matches the actual functionality,
and will need to be updated before we can release a new version of
oslo_middlew
Thanks everyone for coming!
Meeting minutes:
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-08-10-16.03.txt
Meeting log:
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-08-10-16.03.log.html
The next meeting will be on Aug 17. You can post your agenda items at
On 08/07/2015 01:58 PM, Rich Megginson wrote:
> Would someone who actually has to deploy/maintain puppet manifests and
> supporting code chime in here? How do you feel about having to ensure
> that every domain scoped Keystone resource name must end in
> "::domain"? At the very least, if not usin
On 08/10/2015 10:11 AM, Dugger, Donald D wrote:
In re: Different architectures.
I'm not saying we should create architecture specific definitions in our
APIs. I like the idea of capabilities being exposed as arbitrary strings
like "AES" or "AltiVec". An Intel user would be providing an IA arch
Hi all,
(I've been away for a couple of weeks and I tried to send this before I left. I
didn't see it come through so my apologies if this is the second time you've
seen this.)
I recall markvan mentioning a while ago that there was a need for services to
restart when the underlying package chang
On 08/10/2015 09:55 AM, Dugger, Donald D wrote:
In re: user specifying requirements
Note that we have 2 different requirements here:
1) The cloud user needs to be able to specify "I want to run this image on a machine
that supports capability `foo'".
2) The cloud provider needs to be able to
On Mon, Aug 10, 2015 at 3:47 AM, hao wang wrote:
> Sorry if I missed something, since now we have supported backup in-use
> volumes in L, so I wonder is there some plan or design to support
> restoring on-line volumes.
>
> Thanks.
>
> --
>
> Best Wishes For You!
>
>
> ___
Thanks Juan :) for your response.
On Sun, Aug 9, 2015 at 12:32 PM, Juan Antonio Osorio
wrote:
> It only runs the unit tests.
>
> BR
> On 9 Aug 2015 02:19, "Asha Seshagiri" wrote:
>
>> Thanks a lot Juan for your response:)
>> One question I had was the barbican.sh script would run only the unit
In re: Different architectures.
I'm not saying we should create architecture specific definitions in our APIs.
I like the idea of capabilities being exposed as arbitrary strings like "AES"
or "AltiVec". An Intel user would be providing an IA architecture image and
should know that it makes no
On Mon, Aug 10, 2015 at 9:24 AM, Dulko, Michal
wrote:
> Hi,
>
> In Kilo cycle [1] was merged. It started passing AZ of a booted VM to
> Cinder to make volumes appear in the same AZ as VM. This is certainly a
> good approach, but I wonder how to deal with an use case when administrator
> cares abo
In re: user specifying requirements
Note that we have 2 different requirements here:
1) The cloud user needs to be able to specify "I want to run this image on a
machine that supports capability `foo'".
2) The cloud provider needs to be able to say "If you want capability `foo'
it'll cost you".
On 8/10/2015 9:40 AM, Matt Riedemann wrote:
On 8/9/2015 7:16 PM, Matt Riedemann wrote:
On 8/9/2015 7:09 PM, Robert Collins wrote:
On 8 August 2015 at 08:52, Matt Riedemann
wrote:
Well it's a Friday afternoon so you know what that means, emails
about the
stable branches being all busted
> -Original Message-
> From: Gary Kotton [mailto:gkot...@vmware.com]
> Sent: Monday, August 10, 2015 4:18 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Stable][Nova] VMware NSXv Support
>
>
>
> On 8/10/15, 6:05 PM, "Gary Kotton" wrote:
>
> >
> >
> >On 8/10/
Hi,
In Kilo cycle [1] was merged. It started passing AZ of a booted VM to Cinder to
make volumes appear in the same AZ as VM. This is certainly a good approach,
but I wonder how to deal with an use case when administrator cares about AZ of
a compute node of the VM, but wants to ignore AZ of vol
On 08/10/2015 08:05 AM, Jay Pipes wrote:
The Glance metadefs stuff is problematic in a number of ways:
1) It wasn't written with Nova in mind at all, but rather for UI needs. This
means it introduces a bunch of constants that are different from the constants
in Nova.
2) It uses a custom JSON f
On 07/08/15 14:02 +, Jesse Cook wrote:
I largely agree with the points made in the messages by Nikhil and Erno. A
few additional points.
One of the biggest use cases that I heard for glance_store (true, false,
or otherwise) was that Glance is a bottleneck and an unnecessary proxy to
the stor
On 8/10/15, 6:05 PM, "Gary Kotton" wrote:
>
>
>On 8/10/15, 6:03 PM, "Gary Kotton" wrote:
>
>>
>>
>>On 8/10/15, 5:46 PM, "Matt Riedemann" wrote:
>>
>>>
>>>
>>>On 8/10/2015 9:17 AM, Gary Kotton wrote:
Hi,
I am not really sure what to say here. The code was in review for over
8
>>>
On Mon, Aug 10, 2015 at 10:56:00AM +, Lenny Verkhovsky wrote:
> Hi all,
> Lately we discovered a bug[1] in tempest after the code was merged.
> To minimize such things in the future we are asking permission for our CI
> to comment as non-voting CI to tempest commits.
As long as it's not leavin
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 openstackclient/keystone experts to settle this.
I'm referring to the comments in https://review.openstack.org/#/c/207873/
Specifically comments from Richard Megginso
Hello all.
We have launched fuel specs service at [1] where you can read fuel
project specifications.
[1] http://specs.fuel-infra.org/fuel-specs-master/
--
Alexander C. DevOps Engineer.
__
OpenStack Development Mailing Lis
Please ignore this thread. The issue was the line ' device_owner:
"network:dhcp" ' from the server_port resource. Once removed the port was
created with the security group attached.
On Mon, Aug 10, 2015 at 10:11 AM, jason witkowski wrote:
> Just to confirm as well if I use the CLI to create a
On 8/10/15, 6:03 PM, "Gary Kotton" wrote:
>
>
>On 8/10/15, 5:46 PM, "Matt Riedemann" wrote:
>
>>
>>
>>On 8/10/2015 9:17 AM, Gary Kotton wrote:
>>> Hi,
>>> I am not really sure what to say here. The code was in review for over
>>>8
>>> months. On a side note but related - we have a patch for a
On 8/10/15, 5:46 PM, "Matt Riedemann" wrote:
>
>
>On 8/10/2015 9:17 AM, Gary Kotton wrote:
>> Hi,
>> I am not really sure what to say here. The code was in review for over 8
>> months. On a side note but related - we have a patch for a plugin
>> developed in Liberty - https://review.openstack.o
On 8/7/15, 07:19, "Nicolas Trangez" wrote:
>On Fri, 2015-08-07 at 01:21 -0400, Nikhil Komawar wrote:
>> 3. ease of addition of newer drivers for the developers -- drivers
>> are
>> only being removed since.
>
>The OpenStack team at Scality developed a Glance Store driver for RING,
>currently ou
On 07/08/15 01:21 -0400, Nikhil Komawar wrote:
Hi,
During the mid-cycle we had another proposal that wanted to put back the
glance_store library back into the Glance repo and not leave it is as a
separate repo/project.
I replied to a different email in this thread but I'd like to reply to
the
On 10/08/2015 01:53, Jamie Lennox wrote:
>
>
> - Original Message -
>> From: "David Chadwick" To:
>> openstack-dev@lists.openstack.org Sent: Sunday, August 9, 2015
>> 12:29:49 AM Subject: Re: [openstack-dev] [Keystone] [Horizon]
>> Federated Login
>>
>> Hi Jamie
>>
>> nice presentati
Mike:
We are looking into the CI issues now, thank you for bringing to our attention.
Tim
-Original Message-
From: Mike Perez [mailto:thin...@gmail.com]
Sent: Sunday, August 09, 2015 5:35 PM
To: OpenStack Development Mailing List
Cc: DL-GRP-ENG-Brocade-Openstack-CI
Subject: [cinder] B
On 8/10/2015 9:17 AM, Gary Kotton wrote:
Hi,
I am not really sure what to say here. The code was in review for over 8
months. On a side note but related - we have a patch for a plugin
developed in Liberty - https://review.openstack.org/#/c/165750/. This has
been in review since March. I really
On 8/9/2015 7:16 PM, Matt Riedemann wrote:
On 8/9/2015 7:09 PM, Robert Collins wrote:
On 8 August 2015 at 08:52, Matt Riedemann
wrote:
Well it's a Friday afternoon so you know what that means, emails
about the
stable branches being all busted to pieces in the gate.
Tracking in the usual p
Sorry my bad. 7 months :)
On 8/10/15, 5:17 PM, "Gary Kotton" wrote:
>Hi,
>I am not really sure what to say here. The code was in review for over 8
>months. On a side note but related - we have a patch for a plugin
>developed in Liberty - https://review.openstack.org/#/c/165750/. This has
>been i
On 09/08/15 18:41 -0700, Mike Perez wrote:
On 13:07 Aug 07, Jay Pipes wrote:
Hi Nik, some comments inline, but tl;dr I am strongly against
returning the glance_store library to the Glance source repository.
Explanations inline...
On 08/07/2015 01:21 AM, Nikhil Komawar wrote:
>Hi,
>
>During the
On Mon, Aug 10, 2015 at 8:52 AM, Matt Riedemann
wrote:
> Looks like this is blocking any jobs in kilo that use neutron:
>
>
> http://logs.openstack.org/70/210870/1/check/gate-grenade-dsvm-neutron/20f794e/logs/new/screen-q-svc.txt.gz?level=TRACE
>
> This is the bug I reported:
>
> https://bugs.lau
Hi,
I am not really sure what to say here. The code was in review for over 8
months. On a side note but related - we have a patch for a plugin
developed in Liberty - https://review.openstack.org/#/c/165750/. This has
been in review since March. I really hope that that lands in Liberty. If
not we wi
I like that idea a lot – I also think there would be value in adding
pre-deployment sanity checks that could be called from the Health Check
screen prior to deployment. Thoughts?
*From:* Simon Pasquier [mailto:spasqu...@mirantis.com]
*Sent:* Monday, August 10, 2015 9:00 AM
*To:* OpenStack Devel
On Sun, Aug 9, 2015 at 8:28 PM, Matt Riedemann
wrote:
>
>
> On 8/9/2015 7:55 PM, Matt Riedemann wrote:
>
>>
>>
>> On 8/9/2015 7:09 PM, Matt Riedemann wrote:
>>
>>>
>>>
>>> On 8/9/2015 6:57 PM, Robert Collins wrote:
>>>
On 8 August 2015 at 12:45, Matt Riedemann
wrote:
> What I
Just to confirm as well if I use the CLI to create a neutron port after the
Heat stack has ran and created the security group everything works fine and
the security group is attached to the neutron port as expected. However
heat is not managing to make this happen, even if I run a check or an
upda
On 08/03/2015 09:57 AM, Dulko, Michal wrote:
-Original Message-
From: Dugger, Donald D [mailto:donald.d.dug...@intel.com]
Sent: Monday, August 3, 2015 7:40 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] How should we expose host capabilities t
Hello Samuel,
This looks like an interesting idea. Do you have any concrete example to
illustrate your point (with one of your plugins maybe)?
BR,
Simon
On Mon, Aug 10, 2015 at 12:04 PM, Samuel Bartel wrote:
> Hi all,
>
> actually with fuel plugins there are test for the plugins used by the
> CI
Looks like this is blocking any jobs in kilo that use neutron:
http://logs.openstack.org/70/210870/1/check/gate-grenade-dsvm-neutron/20f794e/logs/new/screen-q-svc.txt.gz?level=TRACE
This is the bug I reported:
https://bugs.launchpad.net/neutron/+bug/1483266
What is the Neutron team doing to re
Sorry to everyone for bringing up this old thread, but it seems we may need
more openstackclient/keystone experts to settle this.
I'm referring to the comments in https://review.openstack.org/#/c/207873/
Specifically comments from Richard Megginson and Gilles Dubreuil indicating
openstackclient be
Lets move these types of things into the devref. You can link from the wiki
to the official devref.
On Mon, Aug 10, 2015 at 7:41 AM, Sean M. Collins wrote:
> Link.
>
> Frankly if we have something in DevRef - we should link to it from the
> wiki. I hate how stuff gets put in the wiki and then it
Thanks Salv. I'll add an item to tomorrow's meeting agenda to discuss this
a bit more and come up with a plan.
On Mon, Aug 10, 2015 at 2:39 AM, Salvatore Orlando
wrote:
> Kyle,
>
> I can speak very little about the QoS branch, but from what I gather it is
> mature enough to be merged back.
> How
Link.
Frankly if we have something in DevRef - we should link to it from the
wiki. I hate how stuff gets put in the wiki and then it goes stale real
quick. At least with DevRef, when functionality is added we can push people to
add things to devref, and changes undergo review, as opposed to the fr
>"GET /app/items?f_updated_at=gte:some_timestamp"
I guess this should only return existing entries in a collection, while the
proposition was to add deleted entries to the result too (if we use
changes_since). More like a delta, than simple filtering.
--
Kirill Zaitsev
Murano team
Software Eng
Hi,
Had you tried removing oslo_db package?
I saw a similar issues and usually uninstalling or upgrading packages solved
the problem
L.
-Original Message-
From: Mike Bayer [mailto:mba...@redhat.com]
Sent: Saturday, August 08, 2015 1:43 AM
To: OpenStack Development Mailing List (not for
Hello,
Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC
in #openstack-meeting-4:
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150811
Colleen will lead the meeting.
Please add additional items you'd like to discuss.
If our schedule allows it, we'll make
Hi,
I wonder if it makes sense to update the section "Proposing and
Implementing a Feature" [1] of the Neutron development wiki with the new
RFE workflow described here [2]. Or even better just add a link?
Thanks
[1]
https://wiki.openstack.org/wiki/NeutronDevelopment#Proposing_and_Implementing
>These two subjects have probably been discussed already, but I couldn't find
>any info on them, so very much appreciate if someone could clarify.
>1. Why is the HOT template that is fed to package-create command renamed to
>"template.yaml"? Any issue with keeping the original name?
>2. Why HOT
With no strong preference showing up by the major contributors here I'm
going to suggest Tuesday as the right day -
https://review.openstack.org/#/c/211104/ - (John has a slight preference
for Tuesday).
If you have an issue with that, place a vote on the review.
-Sean
On 08/07/2015 09:26
Hi all,
Lately we discovered a bug[1] in tempest after the code was merged.
To minimize such things in the future we are asking permission for our CI
to comment as non-voting CI to tempest commits.
We are running SR-IOV tempest tests on Mellanox HW.
Our CI results can be viewed here[2]
Our CI pag
Does restoring a volume online make any logical sense? Generally operating
systems don't like it when a mounted volume changes contents, and a
restore, being a slow sequential write is likely to be even worse. Since
you have to unmount anyway, attaching a new volume should not be an issue.
Just be
Hi all,
actually with fuel plugins there are test for the plugins used by the CICD,
but after a deployment it is not possible for the user to easily test if a
plugin is crrectly deploy or not.
I am wondering if it could be interesting to improve the fuel plugin
framework in order to be able to def
Sorry if I missed something, since now we have supported backup in-use
volumes in L, so I wonder is there some plan or design to support
restoring on-line volumes.
Thanks.
--
Best Wishes For You!
__
OpenStack Development M
Hi,
Replying to my own post... i found how/where to put the "pre_test_hook" (in
the jenkins job, in the step that executes the devstack-vm script)
The problem is that now i need to execute code BETWEEN installation of
devstack and start of tests.
Is there a hook i can define that will be execute
Kyle,
I can speak very little about the QoS branch, but from what I gather it is
mature enough to be merged back.
However, I believe the Pecan work is still incomplete as we need a solution
to run the RPC over AMQP server independently. Once we have that we can
start merging back what we have.
Sa
Hi Everyone -
We'll open registration for the Tokyo Upstream training soon, and we're
doing something a little different this time: we are pairing students
with mentors right away and allowing them to work through some of the
technical details of OpenStack contribution before class begins.
86 matches
Mail list logo
