-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/05/14 02:48, W Chan wrote:
> Regarding config opts for keystone, the keystoneclient middleware already
> registers the opts at
> https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L325
>
> u
Shixiong,
Sean and I were thinking about throwing out an error when someone is
trying to attach a router to subnet when gateway is already set (for
IPv6, it could be LLA). In the long term, we need to figure out how to
use the link local address IP of the gateway port to overwrite the
gateway
Hi-
Our CI FTP server is active now.
You may check the same at http://115.249.211.42/
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: trinath.soman...@freescale.com [mailto:trinath.soman...@freescale.com]
Sent: Wednesday, May 28, 2014
No failures in the last 24 hours. \o/
On 26 May 2014 23:44, Kieran Spear wrote:
> Hi peeps,
>
> Could I ask reviewers to prioritise the following:
>
> https://review.openstack.org/#/c/95392/
>
> It should eliminate our selenium gate failures, which seem to be happening
> many times per day now.
On 27/05/14 17:14, Kyle Mestery wrote:
> 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,
Hi folks,
>From lbaas design session I have an impression that we need to have a kind
of merge of existing API and new proposed API.
E.g. the blueprint implementation should not be brand new API and DB
backend.
So I'd say from implementation perspective we may want to minimize amount
of changes fo
Hi Joe,
On 28/05/2014, at 11:21 AM, Joe Gordon wrote:
>
>
>
> On Tue, May 27, 2014 at 1:30 PM, Kieran Spear wrote:
>
> 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] tha
Hi,
Sorry somehow I missed this email. I don't think you want to disable it,
though we can definitely have it run less often. The issue with disabling
it is if one of the notifications from neutron->nova never gets sent
successfully to nova (neutron-server is restarted before the event is sent
or
On 05/23/2014 03:58 PM, James E. Blair wrote:
> This is complete. The actual list of renamed projects is:
[...]
have any of these projects changed also their launchpad name?
thanks
.stef
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Paul, do you have enough to be able to put up a WIP in gerrit? This
discussion is getting to the point where having a discussion in gerrit
will be beneficial.
Carl
On Tue, May 27, 2014 at 12:37 PM, Paul Michali (pcm) wrote:
> So I hit some more complexity, when I got to the IPSec connection res
Hi Stephen,
> Doug: What do you think of the idea of having both IPv4 and IPv6 attributes
> on a 'load balancer' object? One doesn't need to have a single appliance
> serving both types of addresses for the listener, but there's certainly a
> chance (albeit small) to hit an async scenario if t
On Tue, May 27, 2014 at 8:13 PM, Mike Spreitzer wrote:
> Joe Gordon wrote on 05/27/2014 07:31:16 PM:
>
> > From: Joe Gordon
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > ,
> > Date: 05/27/2014 07:32 PM
> > Subject: Re: [openstack-dev] [neutron] Supporting retries in
Hi folks!
We have yet to have any kind of meaningful discussion on this list around
load balancer stats (which, I presume to include data that will eventually
need to be consumed by a billing system). I'd like to get the discussion
started here, as this will have significant meaning for how we bot
Joe Gordon wrote on 05/27/2014 07:31:16 PM:
> From: Joe Gordon
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 05/27/2014 07:32 PM
> Subject: Re: [openstack-dev] [neutron] Supporting retries in
neutronclient
>
>
> On Tue, May 27, 2014 at 1:51 PM, Eugene Nik
Hi y'all!
On Tue, May 27, 2014 at 12:32 PM, Brandon Logan wrote:
> 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.
Hi,
Is it possible to detect when the ssl handshaking error occurs on the
client side (and only retry for that)? If so I think we should do that
rather than retrying multiple times. The danger here is mostly for POST
operations (as Eugene pointed out) where it's possible for the response to
not ma
On Wed, May 21, 2014 at 6:21 AM, Assaf Muller wrote:
> Dear Nova aficionados,
>
> Please make sure I understand this correctly:
> Each nova compute instance selects a single VM out of all of the VMs
> that it hosts, and every seconds
> queries Neutron for all of its networking information, then
Hi y'all!
On Fri, May 23, 2014 at 1:24 PM, Carlos Garza wrote:
> Right so are you advocating that the front end API never return a
> private key back to the user once regardless if the key was generated
> on the back end or sent in to the API from the user? We kind of are
> already are imply
Hey Angus,
If I understand the scenario correctly,
I think you might run into the same problem with OAuth Access Tokens.
>> We currently use a trust token and that fails
because both mistral and
>> heat want to create trust tokens as well :-O (trust tokens can't
be
>> rescoped).
i.e.: Use OAuth
I believe this patch should fix the issue, It seems to for me:
https://review.openstack.org/#/c/95938/ (It's in the process of merging
into icehouse and havana now). Thanks for the report.
arosen@arosen-MacBookPro:~/devstack$ neutron net-list
+--+-+---
On Tue, May 27, 2014 at 1:11 PM, 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
> (accident
On Tue, May 27, 2014 at 1:30 PM, Kieran Spear wrote:
>
> 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 defau
Hi，
Does anyone use the latest libvirt + xen +openstack ? In my ubuntu
environment, It can not create VM , Because the blktap2 does not work.
-Original Message-
From: Daniel P. Berrange [mailto:berra...@redhat.com]
Sent: Tuesday, May 27, 2014 5:11 PM
To: OpenStack Development Mailing
On 28/05/14 03:15, Gauvain Pocentek wrote:
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
During our Solum meeting it was felt we should make sure that all three
team are on the same page wrt $subject.
I'll describe the use case we are trying to solve and hopefully get some
guidance from the keystone team about the best way forward
On Fri, May 23, 2014 at 11:11 AM, Ben Nemec wrote:
> On 05/22/2014 06:31 PM, Johannes Erdfelt wrote:
> > I noticed recently that some tests are being skipped in the Nova gate.
> >
> > Some will always be skipped, but others are conditional.
> >
> > In particular the ZooKeeper driver tests are bei
I am reading the meeting minute, and saw the discussion on this BP submitted by
xuhanp:
https://review.openstack.org/#/c/76125/
I don’t see any reason why we need it….do you?
Shixiong
On May 27, 2014, at 12:47 PM, Collins, Sean
wrote:
> http://eavesdrop.openstack.org/meetings/neutron_ipv6
On Sat, May 24, 2014 at 10:24 AM, Hayes, Graham wrote:
>
> Hi all,
>
> Designate would like to apply for incubation status in OpenStack.
> Our application is here:
> https://wiki.openstack.org/wiki/Designate/Incubation_Application
Based on
http://git.openstack.org/cgit/openstack/governance/tr
On Fri, May 23, 2014 at 7:38 PM, Devananda van der Veen <
devananda@gmail.com> wrote:
> Hi all!
>
> This is a follow-up to several summit discussions on
> how-do-we-deprecate-baremetal, a summary of the plan forward, a call to
> raise awareness of the project's status, and hopefully gain some
On Fri, May 23, 2014 at 1:13 PM, Nachi Ueno wrote:
> Hi Ben, Joe
>
> Thank you for your reply
>
> (2) Avoid duplication of works
> I have several experience of this. Anyway, we should encourage people
> to check listed bug before
> writing patches.
>
That's a very good point, but I don't think
Hi Brandon,
The current reviews of the schema itself are absolutely valid and
necessary, and must go on. However, the place of implementation of this
schema needs to be clarified. Rather than make any changes whatsoever to
the existing neutron db schema for LBaaS, this new db schema outlined needs
On Tue, May 27, 2014 at 1:51 PM, Eugene Nikanorov
wrote:
> 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;
> ret
Hi Aaron!
The BUG report https://bugs.launchpad.net/neutron/+bug/1322945 is about
this problem, I posted there the instructions to reproduce it...
Basically, after attaching a private IPv6 subnet to your L3 Router, it will
break the "External Network" and its "Floating IPs", then, it becomes
impo
Thanks Kyle.
One more question: I have a BP for changes in python-neutronclient. Do I
need to have add a neutron-spec for that?
Thanks,
Nader.
On Tue, May 27, 2014 at 10:08 AM, Kyle Mestery wrote:
> On Tue, May 27, 2014 at 12:01 PM, Nader Lahouti
> wrote:
> > Hi Kyle,
> >
> ... But I j
On 05/27/2014 06:25 PM, Adrian Otto wrote:
> Team,
>
> If you would like to declare a candidacy for PTL for Solum, you may send an
> email with the subject "[Solum] Solum PTL Candidacy” to this mailing list
> declaring your candidacy. Please respond with candidacy notices no later than
> 00:00
Hi Folks,
Tomorrow's ( May 28th 2014) Distributed Virtual Router will be cancelled. (
Since most of our team will be in an internal meeting).
We will resume our meeting next week.
Thanks
Swaminathan Vasudevan
Systems Software Engineer (TC)
HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S
Team,
If you would like to declare a candidacy for PTL for Solum, you may send an
email with the subject "[Solum] Solum PTL Candidacy” to this mailing list
declaring your candidacy. Please respond with candidacy notices no later than
00:00 UTC on 2014-06-02.
The following rules apply:
https:
Latest outage was due to nodepool having a stuck TCP connection to the
HP1 region again.
I've filed https://bugs.launchpad.net/python-novaclient/+bug/1323862
about it. If someone were to pick this up and run with it it would be
super useful.
-Rob
On 24 May 2014 05:01, Clint Byrum wrote:
> I for
I’m not sure that this is the right approach. We really have to add the old
extension back for compatibility, so it might be best to simply keep that
extension instead of adding a new way to do it.
Vish
On May 27, 2014, at 1:31 PM, Cazzolato, Sergio J
wrote:
> I have created a blueprint to a
Hi Michael,
* Phase 1 has one review left - https://review.openstack.org/#/c/92691/
* I'll update the phase 2 patch shortly -
https://review.openstack.org/#/c/87002/
* Once the 2 reviews above get approved, we will resurrect the
oslo.vmware BP/review - https://review.openstack.org/#/c/70175/
Ther
That is great information, thanks Eugene.
Eugene Nikanorov wrote on 05/27/2014 03:51:36 PM:
> From: Eugene Nikanorov
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 05/27/2014 03:56 PM
> Subject: Re: [openstack-dev] [neutron] Supporting retries in
neutronclien
Hi.
I've been looking at the current state of the vmware driver spawn
refactor work, and as best as I can tell phase one is now complete.
However, I can only find one phase two patch, and it is based on an
outdated commit. That patch is:
https://review.openstack.org/#/c/87002/
There also are
Hi,
can you open a bug report on this and provide your setup configuration? I
just tested this with ML2 and wasn't able to reproduce the issue.
arosen@arosen-MacBookPro:~/devstack$ neutron net-create asdf
--provider:network_type vlan --provider:segmentation_id 124
--provider:physical_network a
On May 22, 2014, at 4:28 AM, Thierry Carrez
mailto:thie...@openstack.org>> wrote:
Now I understand it can be confusing, especially for people without a
Launchpad Bugs background. Maybe we can find a better term for "tasks"
("work items" ? "steps" ? "commits" ?), maybe we need to
educate/document
On May 20, 2014, at 3:37 PM, Liz Blanchard
mailto:lsure...@redhat.com>> 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 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
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
I have created a blueprint to add this functionality to nova.
https://review.openstack.org/#/c/94519/
-Original Message-
From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]
Sent: Tuesday, May 27, 2014 5:11 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject:
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
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
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
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:
>
>
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:pgue...@sandvine.com]
Sent: Thursday, May 22,
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
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
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
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
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
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
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 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
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
On 05/27/2014 02:42 PM, trinath.soman...@freescale.com 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
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
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: openstack-dev@lists.openstack.org
Subj
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 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
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
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/op
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
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_
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
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
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
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,
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
On 05/27/2014 01:03 PM, trinath.soman...@freescale.com 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
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
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: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
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, trinath.soman...@freescale.com <
trinat
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:
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-
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
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, "trinath.soman...@freescale.com"
wrote:
>Hi Kyle
>
>Kindly consider my BP spec (https://review.openstack.org/#/c/88190/) too
>for Ju
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-05-27-14.01.html
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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
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
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
On Tue, May 27, 2014 at 11:23 AM, trinath.soman...@freescale.com
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 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/
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 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
charles_w...@symantec.com
On 5/26/14, 8:16 AM, "Sergey Lukjanov" wrote:
>Hi folks,
>
>due to
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
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
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
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
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
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
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
1 - 100 of 144 matches
Mail list logo
