Hi,
We have an openstack deployment (Havana on CentOS) in HA mode with
nova-network service deployed using Mirantis Fuel v4.0 .
When uploading images with large filesize (more than 1 GB) from dashboard,
after upload is done the dashboard is showing 504 Gateway Timeout. What
could be the problem?
Do you have a loadbalancer or something that limits the request time in the
path? That would be my guess, you probably need to raise the
request_termination_timeout.
Best,
Aaron
On Thu, May 22, 2014 at 10:59 PM, Tizy Ninan tizy.e...@gmail.com wrote:
Hi,
We have an openstack deployment
Adding one more renaming last day - murano-api repo to murano
(https://review.openstack.org/95085).
On Fri, May 23, 2014 at 9:41 AM, Sergey Lukjanov slukja...@mirantis.com wrote:
For specs repo renaming old github links will still work due to the
github feature that makes a redirect while
I’d like to attend all the Barbican stuff and I’m sure there’ll be some
interesting Keystone things too.
I think it’s likely we’d do more parallel ‘OSSG’ stuff on the Keystone days
though
I’m free on these dates.
From: Bryan Payne bdpa...@acm.orgmailto:bdpa...@acm.org
Date: Friday, 23 May
Hi,
Please find reply in line ..
Thanks regards,
Keshava.A
-Original Message-
From: Mike Grima [mailto:mike.r.gr...@gmail.com]
Sent: Thursday, May 22, 2014 3:55 PM
To: A, Keshava
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev]
Hi All,
I’m newbie to Openstack, so I want to clarify how OpenStack can implement
ETSI NFV Architecture.
The concept of Advanced service looks like Network Service in ETSI NFV
Architecture as shown in Figure 3 below:
http://docbox.etsi.org/ISG/NFV/Open/Published/gs_NFV002v010101p.pdf
As the
Hi,
Pl find the reply inline
Thanks regards,
Keshava.A
-Original Message-
From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com]
Sent: Thursday, May 22, 2014 8:24 PM
To: OpenStack Development Mailing List (not for usage questions); Kyle Mestery
Subject: Re: [openstack-dev]
Great to see the discussions on the ML.
Mohammad - Good summary.
I would like to make few points
1) The current GP API is tuned towards person deploying the application as
opposed to the networking person. This is probably a better way as one
starts to think about self service infrastructure
Nachi,
I will be glad if the solution was as easy as sticking a task_state
attribute to a resource! I'm afraid however that would be only the tip of
the iceberg, or the icing of the cake, if you want.
However, I agree with you that consistency across Openstack APIs is very
important; whether this
Hi,
I have one basic question, what is this tunneled over to network node means ?
( At this point, the packet will go back out to br-int and but tunneled over
to the network node just like any other intra-network traffic.)
What kind of tunnel between Compute to Network Node during SNAT ?
Why
Hello,
I think the Mistral Project[1] aims the same goal, isn't it?
Regards,
jaume
[1]: https://wiki.openstack.org/wiki/Mistral
On 23 May 2014 09:28, Salvatore Orlando sorla...@nicira.com wrote:
Nachi,
I will be glad if the solution was as easy as sticking a task_state
attribute to a
Keshava,
Tunneled over to network node means:
OVS VXLAN Tunnel will be established between compute node and network node and
packets will flow
through that OVS VXLAN Tunnel.
NAT'ing and tunneling are not related here. NAT'ing happens in network node.
Packets that need to
reach the external
On Fri, May 23, 2014 at 09:26:44AM +1200, Steve Baker wrote:
On 23/05/14 08:56, Anne Gentle wrote:
On Tue, May 20, 2014 at 6:42 PM, Steve Baker sba...@redhat.com
mailto:sba...@redhat.com wrote:
On 21/05/14 02:31, Doug Hellmann wrote:
On Fri, May 16, 2014 at 2:10 PM,
Hi,
With apologies to the specs repos we just created, the more I think
about this, the more I think that the right answer is that we should
stick with codenames for the spec repos. The codenames are actually
more discoverable for potential contributors and collaborators. If
you're looking for
On Fri, May 23, 2014 at 03:27:11AM -0700, James E. Blair wrote:
Hi,
With apologies to the specs repos we just created, the more I think
about this, the more I think that the right answer is that we should
stick with codenames for the spec repos. The codenames are actually
more discoverable
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. Needing
to use a closed source
Good day, Trove community.
I would like to start thread related to Trove notification framework.
Notification design was defined as: “Trove will emit events for
resources as they are manipulated. These events can be used to meter the
service and possibly used to calculate bills.”
Dear UXers,
I am happy with your interest in regular OpenStack UX IRC meetings.
Based on the poll (http://doodle.com/3m29dkn3ef2em5in), there are few
slots which fit majority of interested people. Unfortunately few other
teams took empty slots in the meantime so I had to pick first free slot
On Fri, May 23, 2014 at 12:38:40PM +0200, 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
James E. Blair wrote:
[...]
When I look at the two of those, I have to admit that it's the second
one I find more intuitive and I'm pretty sure I'll end up calling it
'sahara-specs' in common usage no matter the name.
+1
Also the program codename is actually defined in programs.yaml:
Apologies, the time was already in conflict with other meetings. But I
managed to find a slot for the one on Monday, so the kick-off meeting
will be:
* Monday, June 2, 2014 at 17000 UTC
* openstack-meeting-3
One more time apologies for this change
-- Jarda
On 2014/23/05 12:58, Jaromir Coufal
+1 for using program codename.
So, we'll need to rename some existing program-named spec repos.
On Fri, May 23, 2014 at 3:40 PM, Thierry Carrez thie...@openstack.org wrote:
James E. Blair wrote:
[...]
When I look at the two of those, I have to admit that it's the second
one I find more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
+1, I also don't see any significant value in using generic names
instead of project names, while the drawbacks are obvious.
/Ihar
On 23/05/14 14:30, Sergey Lukjanov wrote:
+1 for using program codename.
So, we'll need to rename some existing
On Fri, May 23, 2014 at 5:27 AM, James E. Blair jebl...@openstack.org wrote:
Hi,
With apologies to the specs repos we just created, the more I think
about this, the more I think that the right answer is that we should
stick with codenames for the spec repos. The codenames are actually
more
I'd like to formally announce a mid-cycle sprint focused on driving
code for LBaaS in Neutron. Rackspace has graciously offered to host
this at their San Antonio headquarters. The dates will be June 17-19.
More detailed information is at the etherpad here [1]. Please add your
name and sign-up
On Fri, May 23, 2014 at 6:19 AM, Steven Hardy sha...@redhat.com wrote:
On Fri, May 23, 2014 at 12:38:40PM +0200, 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
Hi Mike. I think we still owe you a response to your earlier email as we
recover from the summit but let me address your current questions below.
On May 22, 2014, at 6:55 PM, Mike Grima mike.r.gr...@gmail.com wrote:
Hello,
Just to make sure I understand:
1.) I’m assuming that you can
On Fri, May 23, 2014 at 7:47 AM, Kyle Mestery mest...@noironetworks.comwrote:
On Fri, May 23, 2014 at 5:27 AM, James E. Blair jebl...@openstack.org
wrote:
Hi,
With apologies to the specs repos we just created, the more I think
about this, the more I think that the right answer is that
On Thu, May 22, 2014 at 7:32 PM, Kieran Spear kisp...@gmail.com wrote:
Hi,
I notice that the templated catalog doesn't support the V3 API*. This
is a blocker for us, particularly for Heat since it uses V3
internally. We could switch to the SQL backend, but I'm sure others
are affected by
The Keystone team is going to be making sure the code that needs to be
in by J2 is in. That means the API changes.
I'll be there.
On 05/23/2014 03:09 AM, Clark, Robert Graham wrote:
I’d like to attend all the Barbican stuff and I’m sure there’ll be some
interesting Keystone things too.
I think Cinder has some of the same sauce ?
https://review.openstack.org/#/c/94742/
https://review.openstack.org/#/c/95037/
2014-05-23 10:57 GMT+02:00 Jaume Devesa devv...@gmail.com:
Hello,
I think the Mistral Project[1] aims the same goal, isn't it?
Regards,
jaume
[1]:
Hello, neutroners.
I'm a GSoC participant at OpenStack this year and I'm working on the
cross-services scheduler. For my work I need to build a network topology
of OpenStack deployment. As most of network equipment are switches and
LLDP support is not very large, I tried to look at network
On Fri, May 23, 2014 at 08:09:06AM -0500, Anne Gentle wrote:
On Fri, May 23, 2014 at 6:19 AM, Steven Hardy sha...@redhat.com wrote:
On Fri, May 23, 2014 at 12:38:40PM +0200, Andreas Jaeger wrote:
On 05/23/2014 12:13 PM, Steven Hardy wrote:
[...]
I'll hold my hand up as one
I made a first draft about Translatable strings rules:
https://wiki.openstack.org/wiki/I18n/TranslatableStrings
Please feel free to comment :-)
--
Yves-Gwenaël Bourhis
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
- Original Message -
From: Doug Hellmann doug.hellm...@dreamhost.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, May 22, 2014 3:18:22 PM
Subject: Re: [openstack-dev] [Ironic] handling drivers that will not be
On Fri, May 23, 2014 at 8:42 AM, Steven Hardy sha...@redhat.com 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 sha...@redhat.com wrote:
On Fri, May 23, 2014 at 12:38:40PM +0200, Andreas Jaeger wrote:
On 05/23/2014
While Mistral is a service with its own REST API endpoint, taskflow is a
library (shoot me if I'm wrong here).
Also, mistral appears, in my opinion, to satisfy a set of use cases aimed
at cloud operators rather than for building tasks within an application.
These are the reasons for which I did
On Fri, May 23, 2014 at 9:49 AM, Dan Prince dpri...@redhat.com wrote:
- Original Message -
From: Doug Hellmann doug.hellm...@dreamhost.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, May 22, 2014 3:18:22 PM
Using standard formats such as PEM and PKCS12 (most people don't use
PKCS8 directly) is a good approach. Be mindful that some cryptographic
services do not provide *any* direct access to private keys (makes
sense, right?). Private keys are shielded in some hardened container and
the only way to
From the original ask:
I know that there is possibility to create port with IP
and later connect VM to this port. This solution is almost ok
for me but problem is when user delete this instance - then
port is also deleted and it is not reserved still for the same
user and tenant.
This
Hi Jack,
Do you mean this change by any chance?
https://review.openstack.org/#/c/77043/
Salvatore
On 23 May 2014 15:10, McCann, Jack jack.mcc...@hp.com wrote:
From the original ask:
I know that there is possibility to create port with IP
and later connect VM to this port. This
Hi,
I’m working on a task for a BP to separate validation from persistence logic in
L3 services code (VPN currently), so that providers can override/extend the
validation logic (before persistence).
So I’ve separated the code for one of the create APIs, placed the default
validation into an
On Fri 23 May 2014 06:00:37 AM MDT, Jaromir Coufal wrote:
Apologies, the time was already in conflict with other meetings. But I
managed to find a slot for the one on Monday, so the kick-off meeting
will be:
* Monday, June 2, 2014 at 17000 UTC
* openstack-meeting-3
One more time apologies
One of the things that OpenStack does really well is review our process
for various activities. I don't believe we have had a discussion in the
past reviewing our electoral process and I think it would be good to
have this discussion.
There are two issues that I feel need to be addressed:
Item
On 23/05/14 01:34, Salvatore Orlando wrote:
As most of you probably know already, this is one of the topics discussed
during the Juno summit [1].
I would like to kick off the discussion in order to move towards a concrete
design.
Preamble: Considering the meat that's already on the plate
On 23/05/14 05:41, Mohammad Banikazemi wrote:
Well, for a use case we had in mind we were trying to figure out how to
simply get an IP address on a subnet. We essentially want to use such an
address internally by the controller and make sure it is not used for a
port that gets created on a
Hi all,
We will have the meeting today?
Pablo.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 23 May 2014 16:02, mar...@redhat.com mandr...@redhat.com wrote:
On 23/05/14 05:41, Mohammad Banikazemi wrote:
Well, for a use case we had in mind we were trying to figure out how to
simply get an IP address on a subnet. We essentially want to use such an
address internally by the
Hi Clint,
Please count me in.
Cristian
On 22/05/14 19:24, Clint Byrum cl...@fewbar.com wrote:
Ahoy there, TripleO interested parties. In the last few months, we've
gotten a relatively robust, though not nearly complete, CI system for
TripleO. It is a bit unorthodox, as we have a strong desire
Vivek,
CN to NN Vxlan tunnel is something user/customer configured ?
Or DVR is mandating this VxLan tunnel to reach from NN from CN ?
Means the packets are encapsulated over network even they are not mandated to
do so ?
Then there should be standard if something is getting done like this.
On Thu, May 22, 2014 at 7:31 PM, Johannes Erdfelt johan...@erdfelt.comwrote:
I noticed recently that some tests are being skipped in the Nova gate.
Some will always be skipped, but others are conditional.
I'd like to hear a bit more about why some will always be skipped.
If it's a Python
+1 to merge the allocation pool update patch [3]. I've reviewed the
code and I think that it is good. I haven't run the current patch
myself yet but I can do that soon.
I was also thinking in the context of shared or external networks.
The use case that Salvatore described is exactly the use
+1
It is easier to match spec with codenames
On 5/23/14, 3:27 AM, James E. Blair jebl...@openstack.org wrote:
Hi,
With apologies to the specs repos we just created, the more I think
about this, the more I think that the right answer is that we should
stick with codenames for the spec repos.
Folks,
Please take a look at the initial draft of MagnetoDB Events and Notifications
wiki page: https://wiki.openstack.org/wiki/MagnetoDB/notification. Your
feedback will be appreciated.
Thanks,
Charles Wang
charles_w...@symantec.com
___
I've watched this thread and I wanted to wait a bit before replying to
this. I also read the meeting minutes from the GBP IRC meeting yesterday
[1]. What I sense is there is no general objection to the GBP work in
general, but rather an objection to the way it's being done. I'd like to
see the
Hi Artem:
Can you provide reference to that network tomography work? I would be
interested in a follow up.
In a vendor specific plugin, I have used LLDPs for link discovery using
LLDPs (and by transitivity, the ToR discovery), but I did not build a more
complete topology view since neutron does
Mohammad Banikazemi wrote:
in Atlanta the support was overwhelmingly positive in my opinion. I just
wanted to make sure this does not get lost in our discussions.
Absolutely. I hadn't been following the group policy discussions prior to the
summit but I was very impressed with what I saw and
Thanks Paul. Feedback like this, from actual users of neutron in large
deployments, is the very reason why I feel so strongly that we need to keep
this a high priority work item.
Regards,
Mandeep
On Fri, May 23, 2014 at 9:28 AM, CARVER, PAUL pc2...@att.com wrote:
Mohammad Banikazemi wrote:
Hi, Paul,
If the backend driver maintains its own database, I think the pre_commit
and post_commit approach has an advantage. The typical code flow is able to
keep the driver and plugin database consistent.
Regarding question 1, where validation methods should be added, I am
leaning towards A,
On Fri, May 23, 2014, Rick Harris rconradhar...@gmail.com wrote:
On Thu, May 22, 2014 at 7:31 PM, Johannes Erdfelt johan...@erdfelt.comwrote:
I noticed recently that some tests are being skipped in the Nova gate.
Some will always be skipped, but others are conditional.
I'd like to hear
Paul good points, and I am very happy to read that your expectations
are very closely aligned with the direction we have taken (in terms of
decoupling of the group policy layer from the underlying building
blocks).
Thanks also Kyle for your earlier email. I believe the team has always
been
I forgot to include a link explaining our cloud:
https://wiki.openstack.org/wiki/TripleO/TripleOCloud
Thanks!
Excerpts from Clint Byrum's message of 2014-05-22 15:24:05 -0700:
Ahoy there, TripleO interested parties. In the last few months, we've
gotten a relatively robust, though not nearly
Hi,
I previously spend 7 years involved in a group that drove voter
engagement in a large organisation that faced similar issues.
We learnt a few things in that time.
1. Easy access to information is key.
1. Don't assume people will read the mailing lists - there
I'm happy to announce that python-swiftclient 2.1.0 has just been released!
https://pypi.python.org/pypi/python-swiftclient/
This release includes support for Python 3.3. I want to specifically thank
Tristan Cacqueray, Chmouel Boudjnah, Alex Gaynor, and Christian Schwede for
working on the py3
Hi folks
I believed we should link bug or bp for any commit except automated
commit by infra.
However, I found also there is no written policy for this.
so may be, I'm wrong for here.
The reason, we need bug or bp linked , is
(1) Triage for core reviewing
(2) Avoid duplication of works
(3)
Hi,
Sorry for the late reply. Some comments on Maru's and Amando's points
below:
(1) this model is more complex than linked based
--- as one of the three original members who had action items during the
very first network-policy IRC meeting, I can say that we actually
originally went with
Guys,
I'm trying to delete a network in Neutron but it is failing, from Horizon
it triggers the error message above (subject), and from CLI, it shows this:
---
root@psuaa-1:~# neutron net-delete a1654832-8aac-42d5-8837-6d27b7421892
Request Failed: internal server error while processing your
This is a discussion that definitely belongs on the users list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 05/23/2014 01:36 AM, Aaron Rosen wrote:
Do you have a loadbalancer or something that limits the request time in the
path? That would be my guess, you
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 being skipped because an
underlying python module is missing.
It
On 05/23/2014 12:23 PM, Nachi Ueno wrote:
Hi folks
I believed we should link bug or bp for any commit except automated
commit by infra.
However, I found also there is no written policy for this.
so may be, I'm wrong for here.
The reason, we need bug or bp linked , is
(1) Triage for
+1 to code names. I didn't feel strongly enough about it to object to
the name change for oslo-specs, but we do refer to the program as oslo
pretty much _everywhere_ else.
-Ben
On 05/23/2014 05:27 AM, James E. Blair wrote:
Hi,
With apologies to the specs repos we just created, the more I
On Sat, May 24, 2014 at 2:23 AM, Nachi Ueno na...@ntti3.com wrote:
Hi folks
I believed we should link bug or bp for any commit except automated
commit by infra.
However, I found also there is no written policy for this.
so may be, I'm wrong for here.
The reason, we need bug or bp linked ,
Thanks for the comments Gary!
Typically, the device driver (backend) and service driver, for a provider won’t
have any database requirements (at least for VPN). For the Cisco VPN, the
service driver has one additional table that it maintains for mapping, but even
in that case, there is no
On Sat, May 24, 2014 at 4:02 AM, Joe Gordon joe.gord...@gmail.com wrote:
On Sat, May 24, 2014 at 2:23 AM, Nachi Ueno na...@ntti3.com wrote:
Hi folks
I believed we should link bug or bp for any commit except automated
commit by infra.
However, I found also there is no written policy for
On 5/23/14, 12:46 AM, Mandeep Dhami wrote:
Hi Armando:
Those are good points. I will let Bob Kukura chime in on the specifics
of how we intend to do that integration. But if what you see in the
prototype/PoC was our final design for integration with Neutron core,
I would be worried about
On 5/23/14, 3:07 PM, Paul Michali (pcm) wrote:
Thanks for the comments Gary!
Typically, the device driver (backend) and service driver, for a
provider won't have any database requirements (at least for VPN). For
the Cisco VPN, the service driver has one additional table that it
maintains
Hi Salvatore.
Nice. That ought to do it. Thanks for the pointer.
- Jack
From: Salvatore Orlando [mailto:sorla...@nicira.com]
Sent: Friday, May 23, 2014 10:24 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] reservation of fixed ip
Hi
Hi Bob, The approach towards having the neutron.manager.NeutronManager
provide access to the Controller classes seems like something worth
exploring for the shorter term.
Thanks,
~Sumit.
On Fri, May 23, 2014 at 12:31 PM, Robert Kukura
kuk...@noironetworks.com wrote:
On 5/23/14, 12:46 AM,
Hello,
Thanks for link to this patch. It should solve my current need :)
--
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl
Dnia Fri, 23 May 2014 15:23:49 +0100
Salvatore Orlando sorla...@nicira.com napisał:
Hi Jack,
Do you mean this change by any chance?
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.
(3) Release management
- TTX is doing this after each release. so we can know how many bugs we fixed.
(or we can
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 implying that they can refer to the key via a private
key id.
On May 23,
Just my thoughts,
One thing that makes it hard to determine who to vote for (especially for
those who are or have been on the TC before) is determining during their
past term what they accomplished or helped get through the TC. In a way if
I vote for X candidate and they have been on the TC
On 05/23/2014 03:02 PM, Joe Gordon wrote:
On Sat, May 24, 2014 at 2:23 AM, Nachi Ueno na...@ntti3.com
mailto:na...@ntti3.com wrote:
Hi folks
I believed we should link bug or bp for any commit except automated
commit by infra.
However, I found also there is no written
Hello,
One small remark:
Work in Progress can be set only by change owners (defined in
All-Projects ACLs) which could be a limitation when multiple people
contribute to the same change.
Cedric
ZZelle@IRC
On Thu, May 22, 2014 at 1:43 PM, Sergey Lukjanov slukja...@mirantis.comwrote:
Great, I
Hi Avishay-san,
Thank you for your review and comments for my proposal. I commented in-line.
So the way I see it, the value here is a generic driver that can work with
any storage. The downsides:
A generic driver for any storage is an one of benefit.
But main benefit of proposed driver is as
On May 23, 2014, at 3:35 PM, Robert Kukura kuk...@noironetworks.com wrote:
On 5/23/14, 3:07 PM, Paul Michali (pcm) wrote:
Thanks for the comments Gary!
Typically, the device driver (backend) and service driver, for a provider
won’t have any database requirements (at least for VPN). For
On 05/23/2014 04:56 PM, ZZelle wrote:
Hello,
One small remark:
Work in Progress can be set only by change owners (defined in
All-Projects ACLs) which could be a limitation when multiple people
contribute to the same change.
Cedric
ZZelle@IRC
Work in Progress can be set by the core
I've been looking in to enabling Kerberos for Horizon. Since Horizon
passes the Users credentials on to Keystone to get a token, Kerberos
requires an additional delegation mechanism. This leads to some
questions about how to handle delegation in the case of Federated Identity.
In
All,
Susanne and I had a demonstration of life code by HP's Barbican team today for
certificate storage. The code is submitted for review in the Barbican project.
Barbican will be able to store all the certificate parts (cert, key, pwd) in a
secure container. We will follow up with more
Chen,
Let me know if I can help on anything!
I see that Gary and Rosella already sent you good pointers to get involve in
Neutron development but I am happy to help if needed.
Edgar
From: Rossella Sblendido rsblend...@suse.commailto:rsblend...@suse.com
Reply-To: OpenStack Development Mailing
+1 for Carl! He is a great developer
Edgar
Neutron cores, please vote +1/-1 for the proposed addition of Carl
Baldwin to Neutron core.
I also wanted to mention the process for adding, removing, and
maintaining neutron-core membership is now documented on the wiki here
[3].
Thank you!
Kyle
Paul,
On Fri, May 23, 2014 at 8:24 AM, Paul Michali (pcm) p...@cisco.com wrote:
Hi,
I’m working on a task for a BP to separate validation from persistence logic
in L3 services code (VPN currently), so that providers can override/extend
the validation logic (before persistence).
So I’ve
We've been working for a long time on the feature/ec branch in the swift repo.
It's now done and needs to be merged into master to be generally available.
Here's how the integration is going to work:
1) The feature/ec branch will be refactored into a series of dependent
reviewable patches
2)
jebl...@openstack.org (James E. Blair) writes:
Hi,
On Friday, May 23 at 21:00 UTC Gerrit will be unavailable for about 20
minutes while we rename some projects. Existing reviews, project
watches, etc, should all be carried over.
This is complete. The actual list of renamed projects is:
Thanks for the comment Carl. See @PCM inline
PCM (Paul Michali)
MAIL …..…. p...@cisco.com
IRC ……..… pcm_ (irc.freenode.com)
TW ………... @pmichali
GPG Key … 4525ECC253E31A83
Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83
On May 23, 2014, at 6:09 PM, Carl Baldwin
Hello Team:
Just a quick reminder that the Trove Blueprint meeting on May 26th is
canceled since most folks will be unavailable on Memorial Day.
The next Blueprint meeting will be on Monday, June 2nd. The agenda can
be found at the usual location at:
Joshua Harlow harlo...@yahoo-inc.com writes:
Is there any kind of central location where we can look at what a TC
candidate has done before (what their proposals we, what they voted on, or
any other similar kind of information; in a way this is similar to having
visibility into what a US
Following a lengthy discussion under the subject Alternating meeting tmie
for more TZ friendliness, the TripleO meeting now alternates between
Tuesday 1900UTC (the former time) and Wednesday 0700UTC, for better
coverage across Australia, India, China, Japan, and the other parts of the
world that
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 abstract class provides the default implementation.
For naming, I'd prefer to go with ML2 terminology for two reasons (1)
Neat thanks, I did not know about this :-)
-Original Message-
From: James E. Blair jebl...@openstack.org
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Friday, May 23, 2014 at 5:01 PM
To: OpenStack Development Mailing List
1 - 100 of 125 matches
Mail list logo
