On 06/06/2015 00:24, Adam Young wrote:
On 06/05/2015 01:15 PM, Henry Nash wrote:
I am sure I have missed something along the way, but can someone
explain to me why we need this at all. Project names are unique
within a domain, with the exception of the project that is acting as
its domain
In order to do this fully, you will need to work out what all the
possible supply chains are in OpenStack, so that when any customer
starts any chain of events, there is sufficient information in the
message passed to the supplier that allows that supplier to order from
its supplier. This has to
On 2015-06-06 09:03:13 +0200 (+0200), Alan Pevec wrote:
2015-06-05 15:16 GMT+02:00 Jeremy Stanley fu...@yuggoth.org:
[...]
I think the recommendation from the PyPI maintainers is to not use
.postN suffixes since they are intended to indicate non-code
changes.
So that's PBR bug then and
Hi Fatih,
Definitely interested in it :) Tricircle Ironic Containers is also
something we've been wanting to try out for a long time :)
On Sat, Jun 6, 2015 at 6:07 PM, Daniel Smith daniel.sm...@ericsson.com
wrote:
Hello there.
Fatih and I were discussing TripleO the other day and were
Hi Daniel ,
Definitely interested in it :) Tricircle Ironic Containers is also
something we've been wanting to try out for a long time :)
On Sat, Jun 6, 2015 at 6:07 PM, Daniel Smith daniel.sm...@ericsson.com
wrote:
Hello there.
Fatih and I were discussing TripleO the other day and were
On Fri, Jun 05, 2015 at 10:47:31AM +0100, John Garbutt wrote:
Hi,
So in the interests of filling up your inbox yet further...
We have lots of etherpads from the summit:
https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads#Nova
I have extracted all the action items here:
Hi Fatih,
Definitely interested in it :) Tricircle Ironic Containers is also
something we've been wanting to try out for a long time :)
On Sat, Jun 6, 2015 at 6:07 PM, Daniel Smith daniel.sm...@ericsson.com
wrote:
Hello there.
Fatih and I were discussing TripleO the other day and were
On 2015-06-05 22:04:05 -0700 (-0700), Georgy Okrokvertskhov wrote:
+1 for the periodic job. I don't know how it fits to the current
OpenStack infrastructure, but we definitely need this. As I know
there is a place for 3rd party gates and CI\CD systems, so
probably, the best way to do this for
Good Ideas, we could also try Mesos with k8Ns
On Jun 6, 2015 8:44 PM, Zhipeng Huang zhipengh...@gmail.com wrote:
Hi Daniel ,
Definitely interested in it :) Tricircle Ironic Containers is also
something we've been wanting to try out for a long time :)
On Sat, Jun 6, 2015 at 6:07 PM, Daniel
On Jun 5, 2015, at 19:25, Bhandaru, Malini K malini.k.bhand...@intel.com
wrote:
Continuing with David’s example and the need to control access to a Swift
object that Adam points out,
How about using the Glance token from glance-API service to glance-registry
but carry along extra
Hi, Iben,
You are correct, Tricircle mainly focuses on use of APIs of OpenStack services,
for example, all APIs pass the DefCore test, so that different infrastructure
(like different hypervisor, different SDN controller, etc) in underclouds can
work together in multisite cloud.
Tricircle
On Sat, Jun 6, 2015 at 4:56 AM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-06-05 22:04:05 -0700 (-0700), Georgy Okrokvertskhov wrote:
+1 for the periodic job. I don't know how it fits to the current
OpenStack infrastructure, but we definitely need this. As I know
there is a place for
100 percent agree with you Daniel, let's work on it next week :)
On Sat, Jun 6, 2015 at 9:35 PM, Daniel Smith daniel.sm...@ericsson.com
wrote:
+1 as well.. Mesos was the subject of quite a bit of discussion in Van
as well.
We should maybe think about coming up with a wiki page for “wanted
On 6/6/15, 02:03, Alan Pevec ape...@gmail.com wrote:
2015-06-05 15:16 GMT+02:00 Jeremy Stanley fu...@yuggoth.org:
On 2015-06-05 14:56:30 +0200 (+0200), Thierry Carrez wrote:
[...]
I was wondering if we could switch to post-versioning on stable
branches, and basically generate:
That would be awesome.
Should we start requiring an extra field for maintainer contact email address?
Thanks,
Kevin
From: Georgy Okrokvertskhov
Sent: Saturday, June 06, 2015 7:15:45 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
On 2015-06-06 17:04:14 + (+), Fox, Kevin M wrote:
Should we start requiring an extra field for maintainer contact
email address?
Well, the contact info is per Zuul pipeline. If you wanted to have
the job conditionally send to various E-mail addresses that's not
really going to work.
Kennan,
Welcome to the magnum-core team!
Regards
-steve
From: Steven Dake std...@cisco.commailto:std...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Saturday, May 30, 2015 at
2015-06-04 22:23 GMT+08:00 Ruby Loo rlooya...@gmail.com:
On 4 June 2015 at 02:58, Xu, Hejie hejie...@intel.com wrote:
...
And another guideline for when we should bump Mircoversion
*https://review.openstack.org/#/c/187896/*
https://review.openstack.org/#/c/187896/
This is timely
GRATZ, Kai Qiang!
On Sun, Jun 7, 2015 at 7:59 AM, Steven Dake (stdake) std...@cisco.com
wrote:
Kennan,
Welcome to the magnum-core team!
Regards
-steve
From: Steven Dake std...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
On 06/02/2015 02:39 PM, Colleen Murphy wrote:
In today's meeting we discussed implementing a policy for whether and
when core reviewers should abandon old patches whose author's were
inactive. (This doesn't apply to authors that want to abandon their own
changes, only for core reviewers to
+1 Really funny, and helpful for innovation.
Best Regards
Chaoyi Huang ( joehuang )
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Daniel Smith
[daniel.sm...@ericsson.com]
Sent: 06 June 2015 21:35
2015-06-05 5:35 GMT+08:00 Devananda van der Veen devananda@gmail.com:
On Jun 4, 2015 11:11 AM, Chris Friesen chris.frie...@windriver.com
wrote:
On 06/04/2015 10:14 AM, Devananda van der Veen wrote:
On Jun 4, 2015 8:57 AM, Monty Taylor mord...@inaugust.com
So, seriously -
2015-06-05 19:35 GMT+08:00 Sean Dague s...@dague.net:
On 06/05/2015 01:28 AM, Adrian Otto wrote:
On Jun 4, 2015, at 11:03 AM, Devananda van der Veen
devananda@gmail.com mailto:devananda@gmail.com wrote:
On Jun 4, 2015 12:00 AM, Xu, Hejie hejie...@intel.com
Good news everyone, our internal tests have completed successfully and
we now have RC build. Fuel DevOps team members are unavailable during
the weekend, so we will create stable/6.1 branches for our repos on
Monday, June 8th. Once created, we will officially declare Hard Code
Freeze status
24 matches
Mail list logo
