It’s definitely a nice feature to have for end user, actually we implemented it
our own because we need this but
nova doesn’t support.
Yingjun
> On May 24, 2017, at 6:58 AM, Jay Bryant wrote:
>
>
> On 5/23/2017 9:56 AM, Duncan Thomas wrote:
>>
>>
>> On 23 May 2017
Currently horizon doesn’t support LBaaS v2, there is a blueprint related
but it doesn’t implement yet:
https://blueprints.launchpad.net/horizon/+spec/lbaas-v2-panel
2015-07-21 9:49 GMT+08:00 jiangshan0...@139.com jiangshan0...@139.com:
Hi all,
I have configured these lines in my
Nice!
On May 5, 2015, at 8:11 PM, Roman Vasilets rvasil...@mirantis.com wrote:
Hi, Rally Team.
I have created Rally Gerrit dashboard that organized patches in groups:
Critical for next release, Waiting for final approve, Bug fixes, Proposed
specs, Important patches, Ready for review, Has
Nice!
On Mar 13, 2015, at 1:03 AM, Boris Pavlovic bo...@pavlovic.me wrote:
Hi stackers,
For those who doesn't know Rally team started making releases.
There are 3 major reasons why we started doing releases:
* A lot of people started using Rally in their CI/CD.
Usually
Currently when booting multiple instances, the instance display-names will be
something like 'test-1,test-2' if we set
multi_instance_display_name_template = %(name)s-%(count)s. Here is the problem,
if we need more instances
and want the instance names start with 'test-3', there is no such way
From a user’s aspect i do think Rally is more suitable for a product-ready
cloud, and seems like it is where it focused on. It’s very easy to evaluate
that if the performance of the cloud is better after we adjust some configs or
some other tuning. It also provides SLA which maybe not
so
Cool, Rally is really helpful for performance benchmarking and optimizing for
our openstack cloud.
On Jul 22, 2014, at 5:53, Boris Pavlovic bo...@pavlovic.me wrote:
Hi Stackers and TC,
The Rally contributor team would like to propose a new OpenStack program
with a mission to provide
+1
On Jul 22, 2014, at 2:38, Boris Pavlovic bpavlo...@mirantis.com wrote:
Hi,
I would like to propose my candidacy for Rally PTL.
I started this project to make benchmarking of OpenStack simple as possible.
This means not only load generation, but as well OpenStack specific benchmark
+1, if doing so, a related bug related bug may be solved as well:
https://bugs.launchpad.net/nova/+bug/1323538
On Jun 3, 2014, at 21:29, Jay Pipes jaypi...@gmail.com wrote:
Hi Stackers,
tl;dr
=
Move CPU and RAM allocation ratio definition out of the Nova scheduler and
into the
Glad to see this, i will be glad to contribute on it if the project could move
on..
On Apr 4, 2014, at 10:01, Cazzolato, Sergio J sergio.j.cazzol...@intel.com
wrote:
Glad to see that, for sure I'll participate of this session.
Thanks
-Original Message-
From: Jay Pipes
On Jan 29, 2014, at 22:48, Vinod Kumar Boppanna vinod.kumar.boppa...@cern.ch
wrote:
Hi,
In the Documentation, it was mentioned that there are two API's to see the
quotas of a tenant.
1. v2/{tenant_id}/os-quota-sets - Shows quotas for a tenant
2.
I reported a bug here: https://bugs.launchpad.net/openstack-manuals/+bug/1274153
On Jan 29, 2014, at 23:33, Anne Gentle a...@openstack.org wrote:
Hi can you point out where you're seeing documentation for the first without
tenant_id?
At
Hi, The patch https://review.openstack.org/43583 was approved but failed to
get merged. Could any core reviewer take a look at this after rebase ?
Thanks
Yingjun
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Hi, all,
Could any one from the nova core team take a look at the patch
https://review.openstack.org/#/c/40171/
Clean destroy for project quota
* Destroy user quotas under the project when deleting project quota.
* Fixes bug 1206479 https://code.launchpad.net/bugs/1206479
Change-Id:
Thanks for address the issues. About the bad state for fixed_ips,
floating_ips, i think we could make the user_id column=NULL when creating
the quota usage and reservation, so the usages for fixed_ips and
floating_ips will be synced within the project.
Does this make sense?
2013/8/20 Andrew
Hi, all.
Currently, there is only one pid running for neutron-server. It's not
enough to handle the requests when undering lots of API access. So multiple
workers for neutron-server are urgrent necessary.
Please refer to
https://blueprints.launchpad.net/neutron/+spec/multi-workers-for-api-server
16 matches
Mail list logo