The OpenStack miniconf organisers for PyCon AU are pleased to announce
their call for proposals is now open!
The OpenStack miniconf is a one day conference held on Friday the 1st of
August 2014 in Brisbane before PyCon Australia. The day is dedicated to
talks related to the OpenStack project and
John,
Do it make sense to support storage policy work in devstack so that it can
be more easily tested?
-Edward Zhang
John Dickinson
+1!
Congratulations Carl!
Thanks,
Oleg
On Tue, May 27, 2014 at 9:07 AM, Gary Kotton wrote:
> +1
>
> On 5/26/14 1:35 PM, "Akihiro Motoki" wrote:
>
> >+1 from me too.
> >
> >
> >Akihiro
> >
> >On Thu, May 22, 2014 at 5:59 AM, Kyle Mestery
> >wrote:
> >> I would like to propose a few changes to
On Tue, May 27, 2014 at 10:02 AM, Hua ZZ Zhang wrote:
> Do it make sense to support storage policy work in devstack so that it can
> be more easily tested?
>
> -Edward Zhang
>
> I don't think storage policy on one VM (which has other OpenStack
services) like usually setup for devstack is very p
On Tue, May 27, 2014 at 12:04:23PM +0530, abhishek jain wrote:
> Hi
> Below is the code to which I'm going to reffer to..
>
> vim /opt/stack/nova/nova/virt/disk/vfs/api.py
>
> #
>
> try:
> LOG.debug(_("Trying to imp
+1
On 05/26/2014 07:39 PM, Devananda van der Veen wrote:
Hi all!
I'd like to nominate Dmitry (dtantsur) to ironic-core. He's been very
active in Ironic over the last few months, in particular finding and
fixing bugs and adding support for CentOS and Fedora. His reviews have
been insightful a
On Mon, May 26, 2014 at 09:45:07AM -0400, Alvin Starr wrote:
>
> What is the status of Xen and libvirt under Openstack?
> I noticed bits of discussions about deprecating the interface but I did not
> see any clear answers.
There is *no* intention to deprecated it. It was merely marked as being
in
- Original Message -
> Hello Stackers,
>
> Disclaimer: I'm on a quest to develop a new agent, already have coding a few
> lines. The next step is Unit Testing and enabling me to create a patch to
> test on a devstack. So, this is what brings me here, the need to understand
> and learn th
Hi Stan,
I don't understand well your third problem/solution statement. Could you
please give an example of the proposed behaviour vs the current one?
The last solution - to have not-nullable primitive types by default - looks
good to me, but it breaks the compatibility with the existing contract
Hi Daniel
Thanks for the help.
The end result of my setup is that the VM is stucking at Spawning state on
my compute node whereas it is working fine on the controller node.
Therefore I'm comparing nova-compute logs of both compute node as well as
controller node and trying to proceed step by step.
Hi,
I am observing that here there are overlapping functionality between Routing
and Topology ..
1. Adding Routing into OpenStack ( by link state protocol : OSPF/other) to
learn prefix of underlay network and inject into overlay network.
Builds for CN + Physical Switch/Router ..
2. Use
If anyone has agenda items they'd like to discuss in today's Nova Libvirt
sub-team meeting[1] please add them to the etherpad:
https://etherpad.openstack.org/p/nova-libvirt-meeting-agenda
Regards,
Daniel
[1] https://wiki.openstack.org/wiki/Meetings/Libvirt
--
|: http://berrange.com -o-
Hi all,
We want to schedule the bug scrub meeting for Murano project to 06/02/14
(June 2), at 1700 UTC.
On this meeting we will discuss all new bugs, which we plan to fix in
juno-1 release cycle.
All actual descriptions of Murano bugs are available here:
https://bugs.launchpad.net/murano
If you
Hi All,
> • Federated Keystone and Horizon
> □ Completely open-ended, there isn't much an expectation that we deliver
> this in Juno, but it's something we should start thinking about.
> □
I have just registered a new blueprint for this point:
https://blueprints.launchpad
The Bug Triage is today, let's coordinate using the #openstack-sahara channel.
On Mon, May 26, 2014 at 2:07 PM, Sergey Lukjanov wrote:
> Hey sahara folks,
>
> reminder: tomorrow will be bug triage day for Sahara.
>
> Thanks.
>
> https://wiki.openstack.org/wiki/Sahara/BugTriage
>
> --
> Sincerely
Is this perhaps considered off-topic? If so, is there a better place to discuss
future enhancements?
From: Shaheed Haque [mailto:[email protected]]
Sent: 17 May 2014 20:12
To: [email protected]
Subject: A VM with multiple images that boot off a non-first image
Hi all,
I ha
Hi stackers:
I have a question about the relationship between the release versions of
the projects and their clients. As we already know, upstream client
releases are independent on OpenStack releases and milestones, which are
supposed to be backward compatible.
So, how could I get the correspond
sorry for the inappropriate title...
2014-05-27 19:34 GMT+08:00 Lingxian Kong :
> Hi stackers:
>
> I have a question about the relationship between the release versions of
> the projects and their clients. As we already know, upstream client
> releases are independent on OpenStack releases and m
Thanks for the comments Mandeep! Responses in-line #PCM
On May 23, 2014, at 8:57 PM, Mandeep Dhami wrote:
> My preferences:
>
> For where, I'd go with Gary's recommendation (A) for two reasons (1)
> Consistency and (2) I don't think it will create any boilerplate requirements
> since the abs
Hello fuelers,
we(I and Kamil) would like start discussion about "Enforce access control
for Fuel UI" blueprint
https://blueprints.launchpad.net/fuel/+spec/access-control-master-node.
First question to David, as he proposed this bp. Do you want to add more
requirements?
To all. What do you think
Hi Alex,
1. This is directly related to the bug mentioned above.
Taking an example from launchpad
networks:
Contract:
environment: $.bool().notNull()
flat: $.bool().notNull()
custom: [$.class(Network).notNull()]
Default:
environment: true
flat: false
curr
Please, share your plans for bug triage day to the irc channel to
avoid efforts duplication.
On Tue, May 27, 2014 at 3:32 PM, Sergey Lukjanov wrote:
> The Bug Triage is today, let's coordinate using the #openstack-sahara channel.
>
> On Mon, May 26, 2014 at 2:07 PM, Sergey Lukjanov
> wrote:
>>
Got it.
What about this "it is easier to set attribute value to None rather then
deleting attribute from object if default value is desired, especially for
generic clients"?
Do I understand correctly that setting some property to None should leads
to automatic assignment of the default value?
As f
Hi openstackers,
While working on bulk load, I found previously proposed batch-oriented
asynchronous approach both resource consuming on server side and somewhat
complicated to use.
So I tried to outline some more straightforward streaming way of uploading
data.
By the link below you can found a
On Tue, May 27, 2014 at 6:30 AM, Marco Fargetta
wrote:
> Hi All,
>
>
> > • Federated Keystone and Horizon
> > □ Completely open-ended, there isn't much an expectation that we
> deliver
> > this in Juno, but it's something we should start thinking about.
> > □
>
> I have just
Some comments:
First 5nines is 99.999 % 7nines is a theoretical goal.
1. I disagree if talking about the VMs. Years ago we decided in Scope
Alliance that HA is by definition build on top of unreliable ressources
the HA framework and applications linkage is in charge of the resulting
HA. VMs can s
You're correct for not-nullable contract types. I agree that it is less
obvious. But on the other side it simplifies contract understanding because
otherwise developer needs to know not only how null is treated but also how
NoValue is treated. This also make UI development easier as with null equal
Hi Monty,
> As a next step - why not take the Javascript you've got there and submit
> it as a patch to the file above? We can probably figure out a way to
> template the third party CI names ... but starting one step at a time is
> a great idea.
>
Thanks for the pointer, I have submitted https:
Hi Chmouel,
Storage policies can be fully tested and exercised on an SAIO; the docs that
were recently merged to the feature/ec branch also include a second example
policy using 2x replication to show this. No reason why devstack can’t be used
but I’d propose it doesn’t make anything easier an
On Tue, May 27, 2014 at 07:39:01AM -0500, Dolph Mathews wrote:
> On Tue, May 27, 2014 at 6:30 AM, Marco Fargetta
> wrote:
>
> > Hi All,
> >
> >
> > > • Federated Keystone and Horizon
> > > □ Completely open-ended, there isn't much an expectation that we
> > deliver
> > > this in Ju
Hi, Bartosz
First of all, we are using openstack-dev for such discussions.
Second, there is also Percona's RA for Percona XtraDB Cluster, which looks
like pretty similar, although it is written in Perl. May be we could derive
something useful from it.
Next, if you are working on this stuff, let'
On Wed, May 21, 2014 at 04:47:48PM EDT, Kevin Benton wrote:
> +1
Looks like we have consensus - I'll conduct a meeting today (Tue May
27th 2014) at 1800 UTC.
--
Sean M. Collins
___
OpenStack-dev mailing list
[email protected]
http://lis
On Thu, May 22, 2014 at 06:51:56PM EDT, Itsuro ODA wrote:
> BTW, where do you begin a discussion ? I thought you countinue
> work in Icehose. Or do you argue from the beginning of the API
> definition ?
My plan is to introduce the REST API and the work that has already been
done, and help bring
- Original Message -
> From: "Sean Dague"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Friday, May 23, 2014 3:40:16 AM
> Subject: Re: [openstack-dev] [QA] Tempest Release Naming
>
> On 05/22/2014 08:33 PM, Jeremy Stanley wrote:
> > On 2014-05-22 18:33:3
In the case a single service VM: you have 1 VNF composed of 1 VNFC.
Specs tries to cover most cases, hence makes the simple ones looks too
complex.
The next question will be the type of services you want to put in this
VM. If it ends up providing services to manage your VNF(C) then you will
end
+1 for Dmitry!
--ruby
From: Devananda van der Veen
mailto:[email protected]>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:[email protected]>>
Date: Monday, May 26, 2014 at 12:39 PM
To: OpenStack Development Mailing List
mailto:openstack
Radoslav Gerganov writes:
> Hi Monty,
>
>> As a next step - why not take the Javascript you've got there and submit
>> it as a patch to the file above? We can probably figure out a way to
>> template the third party CI names ... but starting one step at a time is
>> a great idea.
>>
>
> Thanks f
On Mon, May 26, 2014 at 7:52 PM, Henry Gessau wrote:
> On 5/26/2014 8:31 PM, Monty Taylor wrote:
>> On 05/25/2014 05:23 AM, Radoslav Gerganov wrote:
>>> Hi,
>>>
>>> I created a small userscript that allows you to hide CI comments in Gerrit.
>>> That way you can read only comments written by human
On Tue, May 27, 2014 at 8:12 AM, Marco Fargetta
wrote:
> On Tue, May 27, 2014 at 07:39:01AM -0500, Dolph Mathews wrote:
> > On Tue, May 27, 2014 at 6:30 AM, Marco Fargetta
> > wrote:
> >
> > > Hi All,
> > >
> > >
> > > > • Federated Keystone and Horizon
> > > > □ Completely open-ended, the
On Tue, May 27, 2014 at 07:07:54AM -0700, James E. Blair wrote:
> Radoslav Gerganov writes:
>
> > Hi Monty,
> >
> >> As a next step - why not take the Javascript you've got there and submit
> >> it as a patch to the file above? We can probably figure out a way to
> >> template the third party CI
Hi Neutron developers:
I've spent some time cleaning up the BPs for Juno-1, and they are
documented at the link below [1]. There are a large number of BPs
currently under review right now in neutron-specs. If we land some of
those specs this week, it's possible some of these could make it into
Jun
On 05/27/2014 10:16 AM, Daniel P. Berrange wrote:
> On Tue, May 27, 2014 at 07:07:54AM -0700, James E. Blair wrote:
>> Radoslav Gerganov writes:
>>
>>> Hi Monty,
>>>
As a next step - why not take the Javascript you've got there and submit
it as a patch to the file above? We can probably
On 26/05/14 09:39 -0700, Devananda van der Veen wrote:
Hi all!
I'd like to nominate Dmitry (dtantsur) to ironic-core. He's been very
active in Ironic over the last few months, in particular finding and
fixing bugs and adding support for CentOS and Fedora. His reviews have
been insightfu
On 27 May 2014 13:42, Lukasz Oles wrote:
> Hello fuelers,
>
> we(I and Kamil) would like start discussion about "Enforce access control
> for Fuel UI" blueprint
> https://blueprints.launchpad.net/fuel/+spec/access-control-master-node.
>
> First question to David, as he proposed this bp. Do you wa
Thanks for the continued interest in discussing Group Policy (GP). I
believe these discussions with the larger Neutron community can benefit the
GP work.
GP like any other Neutron extension can have different implementations. Our
idea has been to have the GP code organized similar to how ML2 and
Hi Dmitriy,
Thank you very much for your feedback.
Although it looks like MagnetoDB Events & Notifications component has some
similarities to Ceilometer, it is much narrower scope. We only plan to provide
immediate and periodic notifications of MagnetoDB table/data item CRUD
activities based o
The other challenge of utilizing Keystone is which one to use. Fuel enables
the deployment of multiple cloud environments from one UI; so when accessing
the Fuel Master Node, it would be ambiguous which already deployed Keystone
to contact for authentication. If/When Triple-O is utilized, one cou
On 23/05/14 06:38, Andreas Jaeger wrote:
On 05/23/2014 12:13 PM, Steven Hardy wrote:
[...]
I'll hold my hand up as one developer who tried to contribute but ran away
screaming due to all the XML-java-ness of the current process.
I don't think markup complexity is a major barrier to contribution
Le 2014-05-23 15:57, Anne Gentle a écrit :
On Fri, May 23, 2014 at 8:42 AM, Steven Hardy
wrote:
On Fri, May 23, 2014 at 08:09:06AM -0500, Anne Gentle wrote:
On Fri, May 23, 2014 at 6:19 AM, Steven Hardy
wrote:
On Fri, May 23, 2014 at 12:38:40PM +0200, Andreas Jaeger wrote:
On 05/23/2014
There is some misunderstanding here. By using keystone I mean running
keystone on fuel master node. After all it's just python program. It's used
by OpenStack as authorization tool but it also can be used as standalone
software or by different tools completely not connected with OpenStack.
In futur
On Tue, May 27, 2014 at 10:32:58AM -0400, Anita Kuno wrote:
> On 05/27/2014 10:16 AM, Daniel P. Berrange wrote:
> > On Tue, May 27, 2014 at 07:07:54AM -0700, James E. Blair wrote:
> >> Radoslav Gerganov writes:
> >>
> >>> Hi Monty,
> >>>
> As a next step - why not take the Javascript you've g
Hi Sergey,
A couple of questions with regard to the process:
1. Is it self nomination only or we can nominate someone else?
2. Is the PTL for Juno, or for a length of 6 months?
Thanks,
Charles Wang
[email protected]
On 5/26/14, 8:16 AM, "Sergey Lukjanov" wrote:
>Hi folks,
>
>due to
Hi Everyone,
Here are the meeting minutes from today's meeting.
Meeting ended Tue May 27 16:13:45 2014 UTC. Information about MeetBot at
http://wiki.debian.org/MeetBot . (v 0.1.4)
Minutes:
http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-05-27-16.01.html
Minutes (text):
Hi Kyle
Kindly consider my BP spec (https://review.openstack.org/#/c/88190/) too for
Juno1.
I have been mailing the reviewer to kindly make some to to review the BP spec.
I have code too in place for review along with working CI.
The Code for review : https://review.openstack.org/#/c/78092/
On Tue, May 27, 2014 at 11:23 AM, [email protected]
wrote:
> Hi Kyle
>
> Kindly consider my BP spec (https://review.openstack.org/#/c/88190/) too for
> Juno1.
>
> I have been mailing the reviewer to kindly make some to to review the BP spec.
>
> I have code too in place for review a
Hi Mohammad,
Thanks, I understand now. I appreciate that the mapping driver is one way
of doing things and that the design has been familiarized for a while. I
wish I could follow infinite channels but unfortunately the openstack
information overload is astounding and sometimes I fail :) Gerrit is
Hi Illia,
Looks good. But I suggest to return all of these fields for positive
request as well as for error request:
"read": "string",
"processed": "string",
"failed": "string",
but leave next fields optional and fill them in case of error response
("failed" > 0) to specify what exac
I'm going to bump this thread based on some of the discussions we had
today during the IRC meeting.
I also added a comment to a review on the tempest side after our
discussion (I made some adjustments to my comment for context and
clarification)
https://review.openstack.org/#/c/93400/
>> The onl
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-05-27-14.01.html
--
Sean M. Collins
___
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
My only comment is that the name of the topic should be:
bp/fsl-sdn-os-mech-driver
Instead of:
bp/https
I guss we can pass this..
Edgar
On 5/27/14, 9:23 AM, "[email protected]"
wrote:
>Hi Kyle
>
>Kindly consider my BP spec (https://review.openstack.org/#/c/88190/) too
>for Ju
Hi-
Sure!. Will change the topic and update you.
Thanks a lot for the reply and review.
Your review helps me a lot to proceed further with code.
Thanking you ..
-
Trinath Somanchi
From: Edgar Magana Perdomo (eperdomo)
Sent: Tuesday, May 27, 2014 10:18
Hi Kyle,
>>> ... But I just wanted to highlight
>>> that I removed a large number of BPs from targeting Juno-1 now which
>>> did not have specifications linked to them...
Will those BP be reviewed after updating the link to the specification?
Thanks,
Nader.
On Tue, May 27, 2014 at 7:14 AM,
Hi-
Thanks a lot Salvatore.
I'm looking into that issue. I'm troubleshooting the same.
Will update this mail chain when its accessible for review.
Thanks a lot for the review Salvatore.
--
Trinath
From: Salvatore Orlando
Sent: Tuesday, May 27, 2014 10:
Too late.
I just approved the specification.
I don't think there is any need for reverting the blueprint and just
updating the topic in the patch.
Please have a look at Freescale CI - logs are not accessible at the moment.
Salvatore
On 27 May 2014 18:51, [email protected] <
trinat
On Tue, May 27, 2014 at 12:01 PM, Nader Lahouti wrote:
> Hi Kyle,
>
... But I just wanted to highlight
>
that I removed a large number of BPs from targeting Juno-1 now which
did not have specifications linked to them...
>
> Will those BP be reviewed after updating the link to the sp
Hi,
I have been working on the port mirroring blueprint and i was asked to
submit a neutron spec related to this
I have drafter the spec and ready to commit it to the '
git://git.openstack.org/openstack/neutron-specs' repository for
review. Since the blueprint for this was old i was asked to submi
On Tue, May 27, 2014 at 12:12 PM, Vinay Yadhav wrote:
> Hi,
>
> I have been working on the port mirroring blueprint and i was asked to
> submit a neutron spec related to this
> I have drafter the spec and ready to commit it to the
> 'git://git.openstack.org/openstack/neutron-specs' repository for
On 05/27/2014 01:03 PM, [email protected] wrote:
> Hi-
>
>
> Thanks a lot Salvatore.
>
>
> I'm looking into that issue. I'm troubleshooting the same.
>
>
> Will update this mail chain when its accessible for review.
>
>
> Thanks a lot for the review Salvatore.
>
>
> --
>
> T
Hi,
On 27 May 2014, at 15:55, Mohammad Banikazemi wrote:
> GP like any other Neutron extension can have different implementations. Our
> idea has been to have the GP code organized similar to how ML2 and mechanism
> drivers are organized, with the possibility of having different drivers for
>
Team,
Today the OpenStack Containers Team[1] held our weekly IRC meeting, and reached
consensus among a few areas of initial focus. They are:
1) Container support in OpenStack, with minimum code duplication
2) Drive agreement on where containers belong
3) API support for using features from Cont
Are you aware that there is already a way to do this through the cli using
quota-class-update?
http://docs.openstack.org/user-guide-admin/content/cli_set_quotas.html (near
the bottom)
Are you suggesting that we also add the ability to use just regular
quota-update? I’m not sure i see the need
Hi John,
Now that we have agreement during the summit on how to proceed in order to get
it in to Juno, please take a look at this:
https://review.openstack.org/#/c/86606/16
Please let us know your comments or what is still missing. I’m also not sure if
your –2 needs to be removed before the o
Also I would prefer that we not add "special" tenant names. Roles already
had/has problems with "admin", "Member" and "_member_" having special
meaning in some projects.
~ Scott
On Tue, May 27, 2014 at 1:20 PM, Vishvananda Ishaya
wrote:
> Are you aware that there is already a way to do this thr
Just a heads up:
Repository stackforge/murano-api was renamed to stackforge/murano on
May 23. All the commit and review history is preserved and can be
viewed under the new name [1], [2].
We also renamed [3]:
* internal package name from muranoapi to murano
* config file names under etc/murano
No
So I hit some more complexity, when I got to the IPSec connection resource’s
update API…
I was doing code like this:
In VPN plugin:
def create_ipsec_site_connection(self, context, ipsec_site_connection):
driver = self._get_driver_for_ipsec_site_connection(
context, ipsec_
Currently, neutronclient is hardcoded to only try a request once in
retry_request by virtue of the fact that it uses self.retries as the retry
count, and that's initialized to 0 and never changed. We've seen an issue
where we get an ssl handshaking error intermittently (seems like more of an
ssl
http://eavesdrop.openstack.org/meetings/neutron_qos/2014/neutron_qos.2014-05-27-18.01.html
See everyone next week!
--
Sean M. Collins
___
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/op
Hi Kyle-
The BP Spec approved.
https://review.openstack.org/#/c/88190/
Kindly consider my BP spec for Juno-1.
Thanking all the code reviewers for their time to review my ML2 MD Spec and
making me to improve the spec.
-
Trinaths
From: Kyle Mestery
Sen
AFIK, if we implement ironic as a replacement for cobbler, we will
have Keystone on the fuel-master anyway. Supporting OAuth as an
additional authentication entry would awesome too, but I'm not sure if
there would be much demand over Keystone.
On Tue, May 27, 2014 at 8:31 AM, Lukasz Oles wrote:
>
Hi-
Sure Anita. I have been attending meeting for ML2 at #openstack-meeting-alt.
Will also, attend the below mentioned meetings ..
Thanking you.
-
Trinaths
From: Anita Kuno
Sent: Tuesday, May 27, 2014 10:45 PM
To: [email protected]
Subj
I've marked it as Juno-1 for now, but as Salvatore indicated, there
are some issues with third party testing which need to be addressed
before this can be merged. It would be a good idea to attend the IRC
meeting Anita pointed out as well.
Thanks,
Kyle
On Tue, May 27, 2014 at 1:45 PM, trinath.som
On 05/27/2014 02:42 PM, [email protected] wrote:
>
> Hi-
>
> Sure Anita. I have been attending meeting for ML2 at #openstack-meeting-alt.
>
> Will also, attend the below mentioned meetings ..
>
> Thanking you.
>
> -
> Trinaths
Great. Have you ever considered spending time in the c
On Tue, May 27, 2014 at 12:48 PM, Paul Ward wrote:
> Currently, neutronclient is hardcoded to only try a request once in
> retry_request by virtue of the fact that it uses self.retries as the retry
> count, and that's initialized to 0 and never changed. We've seen an issue
> where we get an ssl h
Hi Kyle-
I'm working the issues with our FTP server which is hosting the CI testing logs.
Will update the status of the Server in this Email chain.
-
Trinath
From: Kyle Mestery
Sent: Wednesday, May 28, 2014 12:24 AM
To: OpenStack Development Mailing Li
Trove-Gate appears to sit idle after the last output from the test run. See the
following samples:
Excerpt from https://rdjenkins.dyndns.org/job/Trove-Gate/3792/console
12:59:47 202.03 proboscis.case.MethodTest
(test_instance_returns_to_active_after_resize)
13:47:06
Hi Vish,
I think quota classes have been removed from Nova now.
Phil
Sent from Samsung Mobile
Original message
From: Vishvananda Ishaya
Date:27/05/2014 19:24 (GMT+00:00)
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [nova] no
Hey Charles,
it's a self-nomination and it's for the Juno dev cycle (to adjust next
elections with dev cycle).
Thanks.
On Tue, May 27, 2014 at 7:48 PM, Charles Wang wrote:
> Hi Sergey,
>
> A couple of questions with regard to the process:
>
> 1. Is it self nomination only or we can nominate som
Referencing this blueprint:
https://review.openstack.org/#/c/89903/5/specs/juno/lbaas-api-and-objmodel-improvement.rst
Anyone who has suggestions to possible issues or can answer some of
these questions please respond.
1. LoadBalancer to Listener relationship M:N vs 1:N
The main reason we went w
Thanks, Brandon. My opinion, reproduced from an IRC conversation that we
had earlier today:
I don't have a strong objection, just an implementation shudder. Of the
two backends that I'm familiar with, they support 1:N, not N:N So, we
fake it by duping listeners on the fly. But, consider the ext
There seems to be a fair bit of confusion with the PoC/prototype
patches. As such, and per reviewer feedback to introduce the Endpoint
Group related patch sooner than later, we will start a new series. You
will see this first patch land shortly, and we can incrementally make
progress from there.
O
Meeting ended Tue May 27 20:00:28 2014 UTC
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-27-19.01.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-27-19.01.txt
Log:
http://e
Are there any best practices defined around extending the Keystone JSON
documents,
or is there a better source to go to in order to get some guidance on this?
Thanks again for your time,
-PG
-Original Message-
From: Phillip Guerin [mailto:[email protected]]
Sent: Thursday, May 22,
I'm not aware of any such change at the moment, no.
On Tue, May 27, 2014 at 3:06 PM, Paul Ward wrote:
> Great! Do you know if there's any corresponding nova changes to support
> this as a conf option that gets passed in to this new parm?
>
>
>
> Kyle Mestery wrote on 05/27/2014 01:56:12 PM:
>
>
Phil,
You are correct and this seems to be an error. I don’t think in the earlier ML
thread[1] that anyone remembered that the quota classes were being used for
default quotas. IMO we need to revert this removal as we (accidentally) removed
a Havana feature with no notification to the community
Great! Do you know if there's any corresponding nova changes to support
this as a conf option that gets passed in to this new parm?
Kyle Mestery wrote on 05/27/2014 01:56:12 PM:
> From: Kyle Mestery
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 05/27/2014 0
On 28/05/2014, at 6:11 AM, Vishvananda Ishaya wrote:
> Phil,
>
> You are correct and this seems to be an error. I don’t think in the earlier
> ML thread[1] that anyone remembered that the quota classes were being used
> for default quotas. IMO we need to revert this removal as we (accidentall
I have created a blueprint to add this functionality to nova.
https://review.openstack.org/#/c/94519/
-Original Message-
From: Vishvananda Ishaya [mailto:[email protected]]
Sent: Tuesday, May 27, 2014 5:11 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject:
In fact, nova should be careful about changing number of retries for
neutron client.
It's known that under significant load (people test serial VM creation)
neutron client may timeout on POST operation which does port creation;
retrying this again leads to multiple fixed IPs assigned to a VM
Thank
> +1 to code names.
Technically, if a program contains multiple projects, it would be more
correct to use the program name, but at this point I think it is pretty
ingrained in our culture (including IRC, mailing list and summits) to
refer to things by their code/project names, so IMO using those n
On May 20, 2014, at 3:37 PM, Liz Blanchard
mailto:[email protected]>> wrote:
I put together a page on the wiki [1] capturing a first draft of some ideas on
how to improve the User Experience of the messaging in Horizon. These are not
technical and really just focus on the presentation layer
1 - 100 of 144 matches
Mail list logo
