For API to move cloudlets, I propose to design API which can talk directly from
destination edge gateway to the source gateway, for example, Pull(
srcEdgeGateway, Cloudlet). Using pull will make the destination talk to the
source directly, but not to introduce any broker or coordinator for the
Hello,
As we discussed these weeks, splitting Tricircle needs to be on the table for
discussion. I prepared some topics in
https://etherpad.openstack.org/p/TricircleSplitting
It's also linked in the Tricircle wiki.
Let's discussed how to address the challenge in the splitting.
Best Regards
Ch
Hello, team,
Agenda of Sept.7 weekly meeting, let's continue the topics:
# progress review and concerns on the features like micro versions, policy
control, dynamic pod binding, cross pod L2 networking
# preparation for the Tricircle splitting:
https://etherpad.openstack.org/p/TricircleSpli
Hi Matt,
On Tue, 2016-09-06 at 16:39 -0500, Matt Riedemann wrote:
> Floating IPs aren't required in OpenStack deployments, and anyone
> running with cells v1 (Rackspace, GoDaddy, NeCTAR, CERN) doesn't use
> or
> support them, at least without patching Nova. So I'm not sure what
> 'industry stan
On Tue, Sep 06, 2016 at 03:41:04PM -0700, Augustina Ragwitz wrote:
> I should add that I also expressed interest in taking over the Bug Czar
> role. I've been actively involved with the bugs team since Markus
> revived it earlier this year. I've run meetings when he was unavailable
> and also provi
Hi All,
Tags for servers are supported in microversion 2.26, but currently we can
only add tags to
instances that are already existed in the cloud, that is, we can not set
tags to instances
when we boot the instances. User will have to first find the instances and
then add tags
with another API ca
Le 07/09/2016 10:50, Kashyap Chamarthy a écrit :
On Tue, Sep 06, 2016 at 03:41:04PM -0700, Augustina Ragwitz wrote:
I should add that I also expressed interest in taking over the Bug Czar
role. I've been actively involved with the bugs team since Markus
revived it earlier this year. I've run m
I prefer this.
4. Trio2o, 3 votes
But I would like to make sure what this actually means more specifically.
How can we define this word?
openstack-to-openstack
Cheers,
Shinobu
On Tue, Sep 6, 2016 at 9:01 PM, liukun wrote:
> Triangel +1
>
> At 2016-09-06 16:27:22, "joehuang" wrote:
>
> Hell
More updates on resource providers work:
Yesterday we realized that a SQL join for associating inventories
with allocations and resource providers was missing a critical and
clause. This was leading to allocations failing to be written when
there should have been plenty of capacity.
This was fi
Preface: IANAL (I-am-not-a-lawyer).
ReactJS claims to be BSD licensed. However, it has a non-BSD patent rider
with a very aggressive "Strong Retaliation Clause", meaning that if there's
ever a patent dispute between [React Project] and Facebook, the patents are
revoked.
This might be fine. It mig
Hello,
During the Mitaka cycle we merged a new feature into the python-neutronclient
called 'neutron purge'. This enables a simple CLI command that deletes all of
the neutron resources owned by a given tenant. It's documented in the
networking guide[1].
We did this in response to feedback from
https://review.openstack.org/366631
The combination of oslo.context 2.9.0 + positional 1.0.1 (which is the
current minimum requirement) results in various unit test failures in
barbican, related to parsing of request headers in generated contexts
for unit testing. Updating to 1.1.1 resolves this
On Thu, Sep 1, 2016 at 11:48 AM, Emilien Macchi wrote:
> On Thu, Aug 25, 2016 at 9:16 AM, Steven Hardy wrote:
>> On Wed, Aug 17, 2016 at 07:20:59AM -0400, James Slagle wrote:
>>> On Wed, Aug 17, 2016 at 4:04 AM, Dmitry Tantsur wrote:
>>> > However, the current gate system allows to run jobs base
On 09/01/2016 05:48 PM, Emilien Macchi wrote:
On Thu, Aug 25, 2016 at 9:16 AM, Steven Hardy wrote:
On Wed, Aug 17, 2016 at 07:20:59AM -0400, James Slagle wrote:
On Wed, Aug 17, 2016 at 4:04 AM, Dmitry Tantsur wrote:
However, the current gate system allows to run jobs based on files affected.
https://review.openstack.org/366298
This is just a bump to upper-constraints so is more minor to get testing
working and fix the bug that occurred in Gnocchi (and possibly others).
We are able to mask the 'bad' versions of oslo.db and unmask pymysql
0.7.7 after the freeze (and backport them to st
-Original Message-
From: Matthew Thode
Reply: prometheanf...@gentoo.org ,
OpenStack Development Mailing List (not for usage questions)
Date: September 7, 2016 at 08:12:15
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [requirements][FFE] global
On Wed, Sep 7, 2016 at 9:18 AM, Dmitry Tantsur wrote:
> On 09/01/2016 05:48 PM, Emilien Macchi wrote:
>>
>> On Thu, Aug 25, 2016 at 9:16 AM, Steven Hardy wrote:
>>>
>>> On Wed, Aug 17, 2016 at 07:20:59AM -0400, James Slagle wrote:
On Wed, Aug 17, 2016 at 4:04 AM, Dmitry Tantsur
wr
On 09/06/2016 05:27 PM, Alon Marx wrote:
> I want to share our plans to open the IBM Storage driver source code.
> Historically we started our way in cinder way back (in Essex if I'm
> not mistaken) with just a small piece of code in the community while
> keeping most of the driver code closed. S
> -Original Message-
> From: duon...@vn.fujitsu.com [mailto:duon...@vn.fujitsu.com]
> Sent: Wednesday, August 24, 2016 5:42 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [kolla] Need clarify about baremetal host
> group and role in Ansible
>
> Hi all, sean-k-moone
Hi
Whilst fixing CI test failures/preparing b3 uploads for OpenStack Newton
for Ubuntu, we tripped over [0], symptomatically in Barbican's unit test
suite starting to throw failures when oslo.context was updated to the
latest newton version.
Global requirement currently details 1.0.1 of positiona
Dear colleagues,
I'm glad to announce that we have working BVT jobs on Fuel CI that do not
use ISO but instead deploy Fuel admin node from packages onto vanilla
Centos 7.
Please take a look at [1]. There are jobs '10.0.repos.*' [2], [3], [4].
We continue to work on re-implementing review jobs li
On Tue, Sep 6, 2016 at 9:27 AM, Alon Marx wrote:
> I want to share our plans to open the IBM Storage driver source code.
> Historically we started our way in cinder way back (in Essex if I'm not
> mistaken)
You're mistaken, Cinder didn't exist at that time... but it's irrelevant.
> with jus
To focus on the Newton work. The Ironic QA meeting is cancelled for today.
Thanks,
John
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
On Wed, 7 Sep 2016 at 14:51 Ian Cordasco wrote:
> Hey James!
>
> There's already a discussion about this with the [requirements] and
> [ffe] tags by Matthew Thode. Could we centralize the discussion on
> that thread please?
>
Of course - missed that whilst eating lunch!
_
Hey James!
There's already a discussion about this with the [requirements] and
[ffe] tags by Matthew Thode. Could we centralize the discussion on
that thread please?
Thanks,
Ian
-Original Message-
From: James Page
Reply: OpenStack Development Mailing List (not for usage questions)
Date
Excerpts from Matthew Thode's message of 2016-09-07 08:21:50 -0500:
> https://review.openstack.org/366298
>
> This is just a bump to upper-constraints so is more minor to get testing
> working and fix the bug that occurred in Gnocchi (and possibly others).
>
> We are able to mask the 'bad' versio
On 07 Sep 2016, at 15:05, John Davidge
mailto:john.davi...@rackspace.com>> wrote:
Hello,
During the Mitaka cycle we merged a new feature into the python-neutronclient
called ’neutron purge’. This enables a simple CLI command that deletes all of
the neutron resources owned by a given tenant. I
On 07 Sep 2016, at 15:05, John Davidge
mailto:john.davi...@rackspace.com>> wrote:
Hello,
During the Mitaka cycle we merged a new feature into the python-neutronclient
called ’neutron purge’. This enables a simple CLI command that deletes all of
the neutron resources owned by a given tenant. I
On Wed, 7 Sep 2016 at 14:30 Ian Cordasco wrote:
[...]
> https://review.openstack.org/366631
> >
> > The combination of oslo.context 2.9.0 + positional 1.0.1 (which is the
> > current minimum requirement) results in various unit test failures in
> > barbican, related to parsing of request headers
On 09/07/2016 08:58 AM, Doug Hellmann wrote:
> Excerpts from Matthew Thode's message of 2016-09-07 08:21:50 -0500:
>> https://review.openstack.org/366298
>>
>> This is just a bump to upper-constraints so is more minor to get testing
>> working and fix the bug that occurred in Gnocchi (and possibly
Hello,
I wonder if it would be worth integrating ospurge into openstackclient.
Are there any osc sessions planned at the summit?
On 09/07/2016 04:05 PM, John Davidge wrote:
Hello,
During the Mitaka cycle we merged a new feature into the
python-neutronclient called ’neutron purge’. This enable
Hey,
This is just a quick update on the Mistral API transition. We are now at a
point where all the major CLI commands (node registration, introspection
and deployment) are being powered by mistral workflows.
We have an etherpad that is tracking all the reviews in quite a bit of
detail:
https://e
On Wed, Sep 7, 2016, at 05:15 AM, Zhenyu Zheng wrote:
> Hi All,
>
> Tags for servers are supported in microversion 2.26, but currently we
> can only add tags to
> instances that are already existed in the cloud, that is, we can not
> set tags to instances
> when we boot the instances. User will
On Wed, Sep 7, 2016, at 04:31 AM, Martin Millnert wrote:
> Hi Matt,
>
> On Tue, 2016-09-06 at 16:39 -0500, Matt Riedemann wrote:
> > Floating IPs aren't required in OpenStack deployments, and anyone
> > running with cells v1 (Rackspace, GoDaddy, NeCTAR, CERN) doesn't use
> > or
> > support the
On Wed, Sep 7, 2016 at 4:18 PM, Boris Bobrov wrote:
> Hello,
>
> I wonder if it would be worth integrating ospurge into openstackclient.
>
> Are there any osc sessions planned at the summit?
>
>
> Hi,
I am the current "PTL" of the openstack/ospurge project. The project is
still alive and we have
There's been a bug filed against OSC to implement ospurge for cleaning up
resources in (compute, network, storage, image and identity) [1] for a
while now. As Jordan said, this is something we want to be modular, and
pluggable, so other OSC plugins could extend this clean up command.
[1] https://b
On Tue, Sep 06, 2016 at 07:37:55PM -0400, Emilien Macchi wrote:
> My vote doesn't count but I still have feedback to share.
>
> As a PTL I have to release multiple projects and Tony was always very
> helpful and responsive in the reviews.
> I would be super happy to have him part of release manage
On Wed, Sep 7, 2016 at 9:48 AM, Steve Martinelli
wrote:
> There's been a bug filed against OSC to implement ospurge for cleaning up
> resources in (compute, network, storage, image and identity) [1] for a
> while now. As Jordan said, this is something we want to be modular, and
> pluggable, so ot
Hi all!
Today while playing with my installation I noticed that we do try to run
cleaning for nodes in maintenance mode. This leads to a somewhat
confusing result, because we no-op heartbeats for such nodes. So
cleaning gets stuck in "clean wait" forever [1].
However, it seems like some folk
Hi everyone,
As you probably know by now, starting with the Boston event in 2017, the
Summit will happen further away from the release day and more around the
middle of the next development cycle. You can find more info on the
rationale for that at [1] and [2] if interested, this is not the topic
On 09/07/2016 06:46 AM, Chris Dent wrote:
>
> More updates on resource providers work:
>
> Yesterday we realized that a SQL join for associating inventories
> with allocations and resource providers was missing a critical and
> clause. This was leading to allocations failing to be written when
>
On 09/07/2016 03:31 AM, Martin Millnert wrote:
> Hi Matt,
>
> On Tue, 2016-09-06 at 16:39 -0500, Matt Riedemann wrote:
>> Floating IPs aren't required in OpenStack deployments, and anyone
>> running with cells v1 (Rackspace, GoDaddy, NeCTAR, CERN) doesn't use
>> or
>> support them, at least with
Excerpts from Thierry Carrez's message of 2016-09-07 17:43:59 +0200:
> Hi everyone,
>
> As you probably know by now, starting with the Boston event in 2017, the
> Summit will happen further away from the release day and more around the
> middle of the next development cycle. You can find more info
On 09/07/2016 10:43 AM, Thierry Carrez wrote:
> Hi everyone,
>
> As you probably know by now, starting with the Boston event in 2017, the
> Summit will happen further away from the release day and more around the
> middle of the next development cycle. You can find more info on the
> rationale for
Doug, Thierry,
Do we want the stewards to serve as the CPL for Release team as well?
-- Dims
[1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management
On Wed, Sep 7, 2016 at 11:57 AM, Doug Hellmann wrote:
> Excerpts from Thierry Carrez's message of 2016-09-07 17:43:59 +0200:
On 09/07/2016 11:43 AM, Thierry Carrez wrote:
> Hi everyone,
>
> As you probably know by now, starting with the Boston event in 2017, the
> Summit will happen further away from the release day and more around the
> middle of the next development cycle. You can find more info on the
> rationale for
Adding [infra].
Simon proposed a patch to make it work.
https://review.openstack.org/#/c/366803/1
-Original Message-
From: Evgeny Antyshev [mailto:eantys...@virtuozzo.com]
Sent: Tuesday, September 06, 2016 2:22 AM
To: OpenStack Development Mailing List (not for usage questions)
Subjec
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: Wednesday, September 07, 2016 9:05 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] Timeframe for future elections & "Release
stewards"
On 09/07/2016 11:43 AM, Thierry Carrez wrote:
> Hi everyo
Davanum Srinivas wrote:
> Doug, Thierry,
>
> Do we want the stewards to serve as the CPL for Release team as well?
Yes, they probably would be an evolution of the current release
liaisons. Like I said in the email, "a sort of per-cycle release liaison
on steroids".
--
Thierry Carrez (ttx)
Barrett, Carol L wrote:
> From: Sean Dague [mailto:s...@dague.net]
>> I think another option would be to run the PTL election early, but just
>> don't have the turn over happen until the master release opens up. The
>> current transition period is > > >
>> actually quite short as noted by the c
On the flip side, so is "I want my vm on a private network and I want a
floating ip to attach it to the public network."
As some clouds don't support it.
Thanks,
Kevin
From: Monty Taylor [mord...@inaugust.com]
Sent: Wednesday, September 07, 2016 8:55 AM
T
On 16-09-07 12:20 PM, Barrett, Carol L wrote:
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: Wednesday, September 07, 2016 9:05 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] Timeframe for future elections & "Release
stewards"
On 09/07/20
On Wed, Sep 7, 2016 at 11:43 AM, Thierry Carrez wrote:
> Hi everyone,
>
> As you probably know by now, starting with the Boston event in 2017, the
> Summit will happen further away from the release day and more around the
> middle of the next development cycle. You can find more info on the
> rati
-Original Message-
From: Monty Taylor
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 7, 2016 at 10:58:52
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] Timeframe for future elections & "Release
stewards"
> On 09/07/201
On Wed, Sep 7, 2016 at 12:35 PM, Ian Cordasco wrote:
>
>
> -Original Message-
> From: Monty Taylor
> Reply: OpenStack Development Mailing List (not for usage questions)
>
> Date: September 7, 2016 at 10:58:52
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [all]
just a heads up, oslo.db 4.13.2 is also broken. we will need this:
https://review.openstack.org/#/c/366362/ or something that fixes issue :)
On 07/09/16 09:21 AM, Matthew Thode wrote:
> https://review.openstack.org/366298
>
> This is just a bump to upper-constraints so is more minor to get testin
On 16-09-07 12:43 PM, Davanum Srinivas wrote:
On Wed, Sep 7, 2016 at 12:35 PM, Ian Cordasco wrote:
-Original Message-
From: Monty Taylor
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 7, 2016 at 10:58:52
To: openstack-dev@lists.openstack.org
Sub
On 09/07/2016 11:43 AM, Davanum Srinivas wrote:
> On Wed, Sep 7, 2016 at 12:35 PM, Ian Cordasco wrote:
>>
>>
>> -Original Message-
>> From: Monty Taylor
>> Reply: OpenStack Development Mailing List (not for usage questions)
>>
>> Date: September 7, 2016 at 10:58:52
>> To: openstack-dev@
On 09/07/2016 11:27 AM, Fox, Kevin M wrote:
> On the flip side, so is "I want my vm on a private network and I want a
> floating ip to attach it to the public network."
>
> As some clouds don't support it.
Yes.
I'd categorize the main things possible as:
"I want a VM on a public network"
"I wa
On Wed, Sep 7, 2016 at 11:35 AM, Ian Cordasco
wrote:
> One question, should "Release Stewards" also be members of the Stable Team
> for that project or will they become members of the Stable Team? It seems
> like there should be a relationship there to me (although maybe not a
> strictly enforced
On 09/07/2016 12:27 PM, Thierry Carrez wrote:
> Barrett, Carol L wrote:
>> From: Sean Dague [mailto:s...@dague.net]
>>> I think another option would be to run the PTL election early, but just
>>> don't have the turn over happen until the master release opens up. The
>>> current transition period
For reasons discussed in last week's IRC meeting, we have vacated the
previous logo choice and are redoing the vote.
http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&;
akey=d34a751f2d084d79
This time I'm using the CIVS system because it will allow us to
determine a #2 and #3 ch
Hi folks,
We are about a week away from cutting our first release candidate [0]. In
preparation for that event, we need to make sure our postmortem [1] and FFE
requests are in good order.
For those of you have not had the chance of commenting on [1], please go
ahead and provide your input. Anythi
Thierry, thanks for writing this up. I think this is a great idea, and
something that will help focus the release stewards on a specific release while
the PTL can coordinate activities for all aspects of the project. Where
appropriate, and where a project decides to take this route, it allows PT
On 09/07/2016 01:20 PM, Ben Swartzlander wrote:
For reasons discussed in last week's IRC meeting, we have vacated the
previous logo choice and are redoing the vote.
http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&;
akey=d34a751f2d084d79
http://civs.cs.cornell.edu/cgi-bin/vote.
Excerpts from Matthew Thode's message of 2016-09-07 09:11:58 -0500:
> On 09/07/2016 08:58 AM, Doug Hellmann wrote:
> > Excerpts from Matthew Thode's message of 2016-09-07 08:21:50 -0500:
> >> https://review.openstack.org/366298
> >>
> >> This is just a bump to upper-constraints so is more minor to
Right.
I use floating ip's because I need the flexibility to have an ip out last the
vm its attached to.
auto floating ip's are in the "just put this on the network, I don't care what
happens when I need to delete my vm" kind of thing. which just having public
ip's also could also solve.
Than
On Wed, Sep 7, 2016 at 10:19 AM, Dean Troyer wrote:
> I created the OSC session Etherpad[0] to start tracking these topic
> suggestions.
>
> [0]https://etherpad.openstack.org/p/osc-otaka-summit
>
/me sighs loudly
I wish I could blame the lack of caffeine, but alas, that URL is just wrong:
[0]h
On 2016-09-07 16:20:49 + (+), Barrett, Carol L wrote:
[...]
> Why not have a PTL own the release from start to finish, with the
> PTL for the next release getting elected as above.
[...]
An overwhelming majority (87%) of our official project teams'
deliverables do not follow a synchronous
-Original Message-
From: Anita Kuno
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 7, 2016 at 12:03:25
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] Timeframe for future elections & "Release
stewards"
> On 16-09-07 12
On 9/7/2016 9:25 AM, Andrew Laski wrote:
On Wed, Sep 7, 2016, at 05:15 AM, Zhenyu Zheng wrote:
Hi All,
Tags for servers are supported in microversion 2.26, but currently we
can only add tags to
instances that are already existed in the cloud, that is, we can not
set tags to instances
when we
On 16-09-07 01:59 PM, Ian Cordasco wrote:
-Original Message-
From: Anita Kuno
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 7, 2016 at 12:03:25
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] Timeframe for future elec
On 09/07/2016 01:29 PM, Doug Hellmann wrote:
Excerpts from Matthew Thode's message of 2016-09-07 09:11:58 -0500:
On 09/07/2016 08:58 AM, Doug Hellmann wrote:
Excerpts from Matthew Thode's message of 2016-09-07 08:21:50 -0500:
https://review.openstack.org/366298
This is just a bump to upper-
-Original Message-
From: Anita Kuno
Reply: Anita Kuno
Date: September 7, 2016 at 13:08:44
To: Ian Cordasco , OpenStack Development Mailing List
(not for usage questions)
Subject: Re: [openstack-dev] [all] Timeframe for future elections & "Release
stewards"
> On 16-09-07 01:59 PM,
On 9/7/2016 11:35 AM, Ian Cordasco wrote:
-Original Message-
From: Monty Taylor
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 7, 2016 at 10:58:52
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] Timeframe for future elec
On 16-09-07 02:19 PM, Ian Cordasco wrote:
-Original Message-
From: Anita Kuno
Reply: Anita Kuno
Date: September 7, 2016 at 13:08:44
To: Ian Cordasco , OpenStack Development Mailing List (not
for usage questions)
Subject: Re: [openstack-dev] [all] Timeframe for future elections &
On 9/7/2016 11:33 AM, Jim Rollenhagen wrote:
I like this. As someone that has been PTL for multiple cycles, it is
incredibly stressful trying to finish the release, start planning for the
next one, manage summit planning, etc. I'd love to have someone
designated to manage the release-specific bi
Hi
I recently introduced a new baremetal role/group which is used as part of the
kolla-host playbook.
https://github.com/openstack/kolla/tree/master/ansible/roles/baremetal
This baremetal role is used to install all the dependencies required to deploy
kolla containers on a "baremetal" host.
The h
Excerpts from Thierry Carrez's message of 2016-09-07 18:24:46 +0200:
> Davanum Srinivas wrote:
> > Doug, Thierry,
> >
> > Do we want the stewards to serve as the CPL for Release team as well?
>
> Yes, they probably would be an evolution of the current release
> liaisons. Like I said in the email,
This is the FFE to get this change in for newton:
https://review.openstack.org/#/c/365165/
The os-vif 1.2.1 release was a bug fix patch release to get a high
priority bug [1] in for newton that is impacting the neutron linuxbridge
job in the gate [2].
So we already have the release done, we
On Wed, Sep 07, 2016 at 01:07:22PM -0400, Sean Dague wrote:
> On 09/07/2016 12:27 PM, Thierry Carrez wrote:
> > Barrett, Carol L wrote:
> >> From: Sean Dague [mailto:s...@dague.net]
> >>> I think another option would be to run the PTL election early, but just
> >>> don't have the turn over happen
Excerpts from Mike Bayer's message of 2016-09-07 14:09:06 -0400:
>
> On 09/07/2016 01:29 PM, Doug Hellmann wrote:
> > Excerpts from Matthew Thode's message of 2016-09-07 09:11:58 -0500:
> >> On 09/07/2016 08:58 AM, Doug Hellmann wrote:
> >>> Excerpts from Matthew Thode's message of 2016-09-07 08:2
Hi all,
I would like to propose bug days for Glance next week Tuesday 13th
September and Wednesday 14th September (during your work hours / in your
time zone).
We've a plenty of bugs to address [1, 2, 3] and looks like the the right
time in the cycle when we would get a good benefit of these bu
Hi team,
The RC period for a release spans multiple weeks, see Newton schedule
here [1]. There are about 4 more weeks in Newton when potential RC
releases could take place. The RC1 is bound to happen next week and
there will most likely be a RC2 with translations. If there are more
critical fixes
Congratulations, Vladimir, that's a huge step in a right direction for Fuel.
--
Best regards,
Oleg Gelbukh
On Wed, Sep 7, 2016 at 6:47 AM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> Dear colleagues,
>
> I'm glad to announce that we have working BVT jobs on Fuel CI that do not
> use
For an ongoing project here at Puppet I needed to validate the stable/mitaka
branches against Puppet 4. I've done that for all three scenarios but doing so
required a few backports of items currently in master.
https://review.openstack.org/#/c/296557/
https://review.openstack.org/#/c/310794/
ht
> -Original Message-
> From: Sean McGinnis [mailto:sean.mcgin...@gmx.com]
> Sent: September-07-16 3:17 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [all] Timeframe for future elections &
> "Release stewards"
>
> On Wed, Sep 07, 2016
Hi!
As the title says here are the patches that set up app-catalog-ui and
murano-dashboard to work under common panel structure [1] Repositories would
now share a couple of small config files to allow both dashboards be installed
independently, if needed [2], [3]
Here is also a small script I
This is exactly what something like Minstral would be fantastic for. Multi-project workflow.
Rather than try and build logic like this directly into nova, looks at extending something like Minstral with a basic easy to call task.
_
On 9/7/2016 8:47 AM, John Griffith wrote:
On Tue, Sep 6, 2016 at 9:27 AM, Alon Marx mailto:alo...@il.ibm.com>> wrote:
I want to share our plans to open the IBM Storage driver source
code. Historically we started our way in cinder way back (in Essex
if I'm not mistaken)
You're mis
Sean,
I’d recommend deploy-hosts (I assume this is the bootstrap renamed?)
I’d also add a duplicate API of “deploy” and mark deploy as deprecated and
follow the standard deprecation policies. I’d recommend making the new
OpenStack specific deploy command deploy-openstack
Regards
-steve
From
I've typically used heat to do this too. As it has a nice way out of the box to
to undo the actions it does.
Thanks,
Kevin
From: Adrian Turjak [adri...@catalyst.net.nz]
Sent: Wednesday, September 07, 2016 2:34 PM
To: OpenStack Development Mailing List (not for usa
Heat is a bit of overkill for something as tiny as this.
I was mainly responding to Andrew Laski's comment talking about a service exactly like Minstral, for smaller cross project orchestration of finite tasks.
On 8/09/2016 10:12 AM, "Fox, Kevin M" wrote:
>
> I've typically used heat to do this to
On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote:
> This is exactly what something like Minstral would be fantastic for.
> Multi-project workflow.
> Rather than try and build logic like this directly into nova, looks
> at extending something like Minstral with a basic easy to call task.
I ha
Hello,
I would like to nominate Serhii Ovsianikov to fuel-virtualbox core due to
his significant contribution to the project [1] and [2]. He is the second
reviewer and for the last half of the year [2] acts as an unoficial QA in
the fuel-virtualbox project.
[1]
http://stackalytics.com/?user_id=so
Hello,
I would like to nominate Stanislaw Bogatkin to fuel-library core due to his
significant contribution to the project [1] and [2]. He is one of the top
reviewers and contributors in the project.
[1]
http://stackalytics.com/?user_id=sbogatkin&project_type=all&release=all&metric=marks&module=f
+1
On Fri, Aug 26, 2016 at 11:59 PM, Dieterly, Deklan
wrote:
> +1
> --
> Deklan Dieterly
>
> Senior Systems Software Engineer
> HPE
>
>
>
>
> On 8/25/16, 9:33 AM, "Mathieu, Pierre-Arthur"
> wrote:
>
> >Hello,
> >
> >I would like to propose some modifications regarding the Freezer core
> >team.
On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote:
> On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote:
> > This is exactly what something like Minstral would be fantastic for.
> > Multi-project workflow.
> > Rather than try and build logic like this directly into nova, looks
> > at ex
On Wed, Sep 7, 2016, at 06:33 PM, Adrian Turjak wrote:
> Heat is a bit of overkill for something as tiny as this.
I agree. And though it's been a while since I've looked at Heat I didn't
get the impression that it was designed for this sort of usage: a simple
API call that orchestrates networki
Congratulations Ron. Welcome aboard.
On 3 September 2016 at 04:13, Brad Topol wrote:
> Shh! Let them get the leg irons welded shut on him first :-). Pay no
> attention Ron... Congratulations!
>
>
> Brad Topol, Ph.D.
> IBM Distinguished Engineer
> OpenStack
> (919) 543-0646
> Internet: bto...
1 - 100 of 116 matches
Mail list logo
