On Thu, Mar 02, 2017 at 06:24:32PM +1100, Tony Breeds wrote:
> I know I'm talking to myself .
Still.
> A project on $branch without constraints is going to get pbr 2.0.0 and then
> hit
> version conflicts with projects that have pbr <2.0.0 caps *anyway* regardless
> of what hacking says rig
+1
Thanks for his great contribution.
Best Regards
Ronghui Cao__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.o
I am working on some improvements for Kolla. Part of that work is
sending patches for review.
Once patch is set for review.openstack.org there is a set of Jenkins
jobs started to make sure that patch does not break already working
code. And this is good thing.
How it is done is not good ;(
1. Ko
Hi Andrea,
I am not sure why the new tempest.scenario.manager has to be developed that
way. May I humbly suggest another path? Roughly goes like:
1) Rename the present class to "OldScenarioTest", set the original name to
point to it (ScenarioTest=OldScenarioTest) (in a single commit)
2) Create a
Marcin,
You can submit a bug for issue #1 you raised and fix it yourself or another
community member can fix it after a bug is filed.
Regarding issue #2, FWIW, I agree local mirroring is the answer. Kolla needs
to locally mirror several repositories in OpenStack Infra so the random
failures w
Hi!
Anyone who is happy to help out with the liaison role, I am happy to work
alongside them and ensure they are pointed in the right direction.
As Matt said, the position at least means attending docs meetings, helping to
review docs patches that are related to nova, helping to alert the docs
On Thu, Mar 02, 2017 at 05:06:34AM +, Brandon B. Jozsa wrote:
>+1 for the monthly meetings and a long standing, cross-team, collaborative
>etherpad.
Yes the etherpad is a good idea, thanks!
I guess we'll want one per-release, so I created one for Pike here:
https://etherpad.openstack
FYI, there's a few bugs for the Configuration Reference mentioning
options for some services require updating. I've gone through the doc
and created additional bugs and included the relevant PTL and docs liaison.
Thank you, Darren! I will review this morning :(
From: John Dickinson
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, March 1, 2017 at 11:50 PM
To: OpenStack Development Mailing List
Cc: "[email protected]"
Subject: Re: [openstack-dev] [docs][release][ptl] Adding docs to the releas
On 03/01/2017 08:15 PM, Pavlo Shchelokovskyy wrote:
Greetings ironicers,
I'd like to discuss the state of the gates in ironic and other related projects
for stable/mitaka branch.
Hi!
Thanks for raising this. I need to apologize, I haven't been doing great job as
a stable liaison recently. I'
On 03/01/2017 08:19 PM, Jay Faulkner wrote:
On Mar 1, 2017, at 11:15 AM, Pavlo Shchelokovskyy
wrote:
Greetings ironicers,
I'd like to discuss the state of the gates in ironic and other related projects
for stable/mitaka branch.
Today while making some test patches to old branches I discov
Greetings,
Just wanted to give a heads up that we're tagging all the containers related
bugs with the... guess what?... containers tag. If you find an issue with one of
the containers jobs or running tripleo on containers, please, file a bug and tag
it accordingly.
https://bugs.launchpad.net/tri
On 2 March 2017 at 10:40, Flavio Percoco wrote:
> Greetings,
>
> Just wanted to give a heads up that we're tagging all the containers
> related
> bugs with the... guess what?... containers tag. If you find an issue with
> one of
> the containers jobs or running tripleo on containers, please, file
On 02/03/17 10:57 +, Dougal Matthews wrote:
On 2 March 2017 at 10:40, Flavio Percoco wrote:
Greetings,
Just wanted to give a heads up that we're tagging all the containers
related
bugs with the... guess what?... containers tag. If you find an issue with
one of
the containers jobs or runni
On 2 March 2017 at 10:18, Steven Hardy wrote:
> On Thu, Mar 02, 2017 at 05:06:34AM +, Brandon B. Jozsa wrote:
> >+1 for the monthly meetings and a long standing, cross-team,
> collaborative
> >etherpad.
>
> Yes the etherpad is a good idea, thanks!
>
> I guess we'll want one per-releas
Hi Matt,
I'd be interested as well. Maybe Zhenyu and I could split this
role, although I am not a native English speaker either :)
Nick
On Wed, Mar 01, 2017 at 09:45:05AM -0600, Matt Riedemann wrote:
There is a need for a liaison from Nova for the docs team to help with
compute-specific docs
Hey folks,
We decided in Wednesday’s 16:00 UTC Kolla meeting to start tackling some of the
blocking items for 1.0.0 of kolla-kubernetes. One of those items is a
deployment guide. The start of the deployment guide is here:
https://etherpad.openstack.org/p/kolla-kubernetes-deploy-guide-BP
We wi
On Mon, 27 Feb 2017, Sean Dague wrote:
However, when there is magic applied it means that stops being true. And
now folks think the APIs work like the magic works, not realizing it's
all client side magic, and when they try to do this in node next month,
it will all fall apart.
+many
It's goo
On Mon, 27 Feb 2017, Clint Byrum wrote:
So, I'll ask more generally: do you believe that the single openstack-dev
mailing list is working fine and we should change nothing? If not, what
problems has it created for you?
No, it is not working fine, but that may be normal and the best we
can do.
Thank you all, I am happy to join the core team and take on the new
responsibilities that comes with it :)
All the best,
Michal Gershenzon
Software Engineer, CloudBand
Application & Analytics , Nokia
Contact number: +972 9 793 3163
From: Renat Akhmerov [mailto:[email protected]]
Sent: T
Hello, devstack!
I want to draw some attention to the fact, that install_libvirt function
now (since https://review.openstack.org/#/c/438325 landed)
only works for Centos 7, but not for other RHEL-based distributions:
Virtuozzo and, probably, RHEV.
Both of above have own version for qemu-kvm pac
>n Wed, 18 May 2016 14:30:00 -0500, Matt Riedemann wrote:
>>> While convenient as a workaround, I'm not in favor of the idea of adding
>>> something to the REST API so a user can force refresh the connection
>>> info - this is a bug and leaks information out of the API about how the
>>> cloud is co
On 03/02/2017 08:18 AM, Evgeny Antyshev wrote:
> Hello, devstack!
>
> I want to draw some attention to the fact, that install_libvirt function
> now (since https://review.openstack.org/#/c/438325 landed)
> only works for Centos 7, but not for other RHEL-based distributions:
> Virtuozzo and, probab
Hello,
We are experiencing an blocking issue with our integrated job since some
days.
Basically the job creates a heat stack and call nova API to list
instances and see if the stack have upscaled.
The autoscaling itself work well, but our test assertion fails because
listing nova instances does
I really believe that this idea will makes us work harder on keeping our
docs in place and will make it for a better documented producted by release
date.
As shared before, I do believe that this is isn't easy and will demand a
lot of effort from some teams, specially smaller teams with too much to
Example of failure:
Our test assertion (that does a GET /v2.1/servers/detail HTTP/1.1) that
returns [] instead of the list of instances
http://logs.openstack.org/56/439156/2/check/gate-telemetry-dsvm-integration-gnocchi-ubuntu-xenial/d4a6c69/console.html#_2017-03-02_09_28_59_334619
The 'opensta
On Wed, Mar 1, 2017 at 11:52 AM, Alexandra Settle
wrote:
> Hi everyone,
>
>
>
> I would like to propose that we introduce a “Review documentation” period
> on the release schedule.
>
>
>
> We would formulate it as a deadline, so that it fits in the schedule and
> making it coincide with the RC1 d
From: Anne Gentle
Date: Thursday, March 2, 2017 at 2:16 PM
To: Alexandra Settle
Cc: "OpenStack Development Mailing List (not for usage questions)"
, "[email protected]"
Subject: Re: [OpenStack-docs] [docs][release][ptl] Adding docs to the release
schedule
On Wed, Mar 1,
On 15/11/16 04:53 AM, Julien Danjou wrote:
> Yeah in the case of the Swift driver for Gnocchi, I'm not really sure
> how much buckets we should create. Should we make the user pick a random
> number like the number of partition in Swift and then create the
> containers in Swift? Or can we have so
On 3/2/2017 8:14 AM, Mehdi Abaakouk wrote:
Example of failure:
Our test assertion (that does a GET /v2.1/servers/detail HTTP/1.1) that
returns [] instead of the list of instances
http://logs.openstack.org/56/439156/2/check/gate-telemetry-dsvm-integration-gnocchi-ubuntu-xenial/d4a6c69/console.ht
-Original Message-
From: Chris Dent
Reply: OpenStack Development Mailing List (not for usage questions)
Date: March 2, 2017 at 06:50:11
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all][swg] per-project "Business only"
moderated mailing
-Original Message-
From: Telles Nobrega
Reply: OpenStack Development Mailing List (not for usage questions)
Date: March 2, 2017 at 08:01:29
To: OpenStack Development Mailing List (not for usage questions)
Cc: [email protected]
Subject: Re: [openstack-dev] [docs][releas
On Thu, Mar 02 2017, gordon chung wrote:
Hi gordon,
> i was thinking more about this yesterday. i've an idea.
You should have seen my face when I read that! ;-P
> how we store new measures
> -
>
> when we add new measures to be processed, the metric itself is already
>
On 02/03/17 09:52 AM, Julien Danjou wrote:
>> using hashring idea, the buckets will be distributed among all the
>> > active metricd agents. the metricd agents will loop through all the
>> > assigned buckets based on processing interval. the actual processing of
>> > each bucket will be similar t
On 02/03/17 09:52 AM, Julien Danjou wrote:
> Sounds good. What's interesting is how you implement a shard/bucket in
> each driver. I imagine it's a container/bucket/directory.
yeah, same as whatever is used now... except more of them :)
--
gord
_
On Thu, Mar 02 2017, gordon chung wrote:
> one of the issues we can't effectively partition the single bucket is
> partly because we have multiple agents on a single bucket. in theory we
> can use markers to partition the single bucket but because of multiple
> workers, the marker has a very hi
Thanks everyone for voting, I started recently and I’m sure that I’ve many
things to learn but something that I discover since the beginning was the
enthusiasm and welcoming aptitudes of this community. I’m going to do my best
for keeping high standards of the code
Thanks
Victor Morales
irc: e
Hi Ironicers.
Recently we have added one-time boot feature to OneView drivers. However, now
for be able to activate the onetime-boot feature , that make oneview driver's
to save some time during the deployment , we need to find a common place to
turn the onetime-boot On and not-persistent.
T
On Tue, Feb 28, 2017 at 11:49:53AM -0500, Matthew Treinish wrote:
> Hello,
>
> We have a few particularly annoying bugs that have been impacting the
> reliability of gate testing recently. It would be great if we could get
> volunteers to look at these bugs to improve the reliability of our testin
Hi All,
I'm working to get a strategy in place for delivery of OpenStack snaps.
Below I've outlined an initial strategy, and I'd like to get your input.
I'm particularly interested in input from snap folks of course, but also
from projects that install OpenStack and may want to be involved in sna
On 02/03/17 10:07 AM, Julien Danjou wrote:
> That also means we may be able to get rid of the scheduler process?
i think we should probably keep it. the scheduler process of agent will
loop through each bucket and start dumping metrics to process on queue
and the processing processes will gree
On Thu, Mar 02 2017, gordon chung wrote:
> On 02/03/17 10:07 AM, Julien Danjou wrote:
>> That also means we may be able to get rid of the scheduler process?
>
> i think we should probably keep it. the scheduler process of agent will
> loop through each bucket and start dumping metrics to process
On Thu, Mar 02, 2017 at 10:13:07AM +0100, Marcin Juszkiewicz wrote:
> I am working on some improvements for Kolla. Part of that work is
> sending patches for review.
>
> Once patch is set for review.openstack.org there is a set of Jenkins
> jobs started to make sure that patch does not break alrea
+1 for my vote
Best wish
Hejiawei
At 2017-03-01 10:38:00, "joehuang" wrote:
Hi Team,
Victor Morales has made many review contributions[1] to Trircircle since the
Ocata cycle, and he also created the python-tricircleclient sub-project[2]. I
would like to nominate him to be Tricircle core
On Wed, Feb 22, 2017 at 10:31:34AM -0500, Thomas Morin wrote:
> Hi,
>
> A bit of context to make my question clearer: openstack/networking-bagpipe
> relies on bagpipe-bgp which is not an openstack project although done by the
> same people, and we would see a significant benefit in moving the code
Adding the [deployment] tag as the catch-all for deployment projects as I think
they’d be interested.
From: Corey Bryant
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Thursday, March 2, 2017 at 3:31 PM
To: OpenStack Development Mailing List
Subject: [openstack
On Thu, Mar 2, 2017 at 10:41 AM, Paul Belanger
wrote:
> In fact, the openstack-infra team does mirror a
> lot of things today
I bumped into this the other day:
https://specs.openstack.org/openstack-infra/infra-specs/specs/unified_mirrors.html
... but so far haven't found any specific details
I got this link[11] from Ankur, apparently Nova and Neutron has already started
a common effort
[11] https://review.openstack.org/#/c/330027/
Regards,
Victor Morales
irc: electrocucaracha
On 3/1/17, 5:53 PM, "Mike Perez" wrote:
>Hey all,
>
>I kicked off a thread [1] to start talking about
Excerpts from Alexandra Settle's message of 2017-03-02 14:29:07 +:
>
>
> From: Anne Gentle
> Date: Thursday, March 2, 2017 at 2:16 PM
> To: Alexandra Settle
> Cc: "OpenStack Development Mailing List (not for usage questions)"
> , "[email protected]"
>
> Subject: Re: [Ope
On Thu, Mar 2, 2017 at 10:57 AM, Jesse Pretorius <
[email protected]> wrote:
> Adding the [deployment] tag as the catch-all for deployment projects as I
> think they’d be interested.
>
>
>
>
>
Ah thanks Jesse, appreciate that. I didn't realize that tag existed.
Corey
__
On 3/2/2017 8:29 AM, Matt Riedemann wrote:
On 3/2/2017 8:14 AM, Mehdi Abaakouk wrote:
Example of failure:
Our test assertion (that does a GET /v2.1/servers/detail HTTP/1.1) that
returns [] instead of the list of instances
http://logs.openstack.org/56/439156/2/check/gate-telemetry-dsvm-integrat
On Thu, Mar 02, 2017 at 11:00:26AM -0500, Clay Gerrard wrote:
> On Thu, Mar 2, 2017 at 10:41 AM, Paul Belanger
> wrote:
>
> > In fact, the openstack-infra team does mirror a
> > lot of things today
>
>
> I bumped into this the other day:
>
> https://specs.openstack.org/openstack-infra/infra-s
On 3/2/17, 4:08 PM, "Doug Hellmann" wrote:
Excerpts from Alexandra Settle's message of 2017-03-02 14:29:07 +:
>
>
> From: Anne Gentle
> Date: Thursday, March 2, 2017 at 2:16 PM
> To: Alexandra Settle
> Cc: "OpenStack Development Mailing List (not for usage qu
Hi Dmitry,
> I'm not sure why removing of *_ssh drivers from master should
> necessary break stable/mitaka, where these drivers are present. Could
> you elaborate?
My main concern is the following: both project-config and devstack-gate are
branch-less. When removing the *_ssh drivers from tree, w
Excerpts from Tony Breeds's message of 2017-03-02 19:41:17 +1100:
> On Thu, Mar 02, 2017 at 06:24:32PM +1100, Tony Breeds wrote:
>
> > I know I'm talking to myself .
>
> Still.
>
> > A project on $branch without constraints is going to get pbr 2.0.0 and then
> > hit
> > version conflicts wi
Greetings OpenStack community,
Only two of us in attendance at today's API-WG meeting. We mostly reflected on
the work that needs to be done to summarize activity at the PTG last week.
Despite not having a room of our own until the last minute, on Monday and
Tuesday we had a large gathering w
> On Mar 1, 2017, at 6:01 PM, Rodrigo Duarte wrote:
>
> On Wed, Mar 1, 2017 at 7:10 PM, Lance Bragstad wrote:
> During the PTG, Morgan mentioned that there was the possibility of keystone
> removing the v2.0 API [0]. This thread is a follow up from that discussion to
> make sure we loop in t
Excerpts from Alexandra Settle's message of 2017-03-02 16:25:46 +:
>
>
> On 3/2/17, 4:08 PM, "Doug Hellmann" wrote:
>
> Excerpts from Alexandra Settle's message of 2017-03-02 14:29:07 +:
> >
> >
> > From: Anne Gentle
> > Date: Thursday, March 2, 2017 at 2:16 PM
>
On 3/2/17, 4:42 PM, "Doug Hellmann" wrote:
Excerpts from Alexandra Settle's message of 2017-03-02 16:25:46 +:
>
>
> On 3/2/17, 4:08 PM, "Doug Hellmann" wrote:
>
> Excerpts from Alexandra Settle's message of 2017-03-02 14:29:07 +:
> >
> >
Hi everyone,
I added Gary Kotton and Russell Boden to the release team to help with
reviews for patches to unblock stadium projects as we go through and
pull out deprecated things in Neutron and adjust gate jobs, etc.
Tag the release team (neutron-release) on any critical reviews to
quickly unblo
Hi Emilien,
Thanks for the feedback! I'm aware that IRC is the standard for OpenStack
folks, but at this current stage it's just easier to hold the discussion in
Slack as Picasso ties into the IronFunctions open source project and
important context would be lost if we were to maintain different ch
On Thu, Mar 2, 2017 at 8:13 AM, Pavlo Shchelokovskyy
wrote:
> I'm also kind of wondering what the grenade job in stable/newton will test
> after mitaka EOL? upgrade from mitaka-eol tag to stable/newton branch? Then
> even that might be affected if devstack-gate + project config will not be
> able
Any updates on the problem? It still bumps patches off gate queue,
resetting it and backing off progress for the whole integrated gate.
Is the work followed up somewhere? Any patches to chew?
Ihar
On Wed, Feb 1, 2017 at 5:14 PM, Tony Breeds wrote:
> On Wed, Feb 01, 2017 at 07:49:21AM -0800, Ihar
On Wed, Mar 1, 2017, at 07:10 PM, Richard Jones wrote:
> Hi folks,
>
> We've run into some issues with various folks installing Horizon and
> its dependencies using just requirements.txt which doesn't limit the
> versions of xstatic packages beyond some minimum version. This is a
> particular prob
Post PTG there has been some discussion regarding quotas as well as limits.
While most of the discussion has been off and on in #openstack-dev, we also
have a mailing list thread on the topic [0].
I don't want to derail the thread on quotas and limits with this thread,
but today's discussion [1] h
The new 0.12.0 version was tagged and released to pypi, it'll land in
a mirror near you soon!
I'll write a blog post about the release soon, until then, the release
notes are here [1].
[1]: https://github.com/openstack/ara/releases/tag/0.12.0
David Moreau Simard
Senior Software Engineer | Openst
On Thu, Mar 02, 2017 at 05:41:24PM +, Derek Schultz wrote:
> Hi Emilien,
>
> Thanks for the feedback! I'm aware that IRC is the standard for OpenStack
> folks, but at this current stage it's just easier to hold the discussion in
> Slack as Picasso ties into the IronFunctions open source projec
Address scopes allow traffic to go across a router without performing any
NAT. The rules you see there ensure that traffic isn't routed directly if
it crosses from one address scope to another.
On Wed, Mar 1, 2017 at 7:21 AM, zhi wrote:
> Hi, all.
>
> I have some questions about l3 address scope
Excerpts from Clark Boylan's message of 2017-03-02 10:40:39 -0800:
> On Wed, Mar 1, 2017, at 07:10 PM, Richard Jones wrote:
> > Hi folks,
> >
> > We've run into some issues with various folks installing Horizon and
> > its dependencies using just requirements.txt which doesn't limit the
> > versio
Excerpts from Ihar Hrachyshka's message of 2017-03-02 10:18:16 -0800:
> Any updates on the problem? It still bumps patches off gate queue,
> resetting it and backing off progress for the whole integrated gate.
> Is the work followed up somewhere? Any patches to chew?
I suspect this is a case where
So this is a general start of a large discussion that is similar to the
other one I started[1], and this time around I wanted to start this on
the mailing instead of a spec first approach.
The general question is around something I keep on noticing popping up
in various projects and worry abou
Marcin Juszkiewicz wrote:
I am working on some improvements for Kolla. Part of that work is
sending patches for review.
Once patch is set for review.openstack.org there is a set of Jenkins
jobs started to make sure that patch does not break already working
code. And this is good thing.
How it i
Hey everyone,
Sorry for the late notice, but there will be no Horizon-Keystone cross project
meeting this week, as we've little to discuss with the PTG so recent. The
meeting will resume as normal next week.
For those interested in joining, see
http://eavesdrop.openstack.org/#Keystone/Horizon_
On 03/02/2017 12:57 PM, Doug Hellmann wrote:
> Right, friends don't let friends cap dependencies.
>
> Let's work on getting constraints rolled out where needed instead.
This is the basic response I have to this. More specifically it can
cause more churn in consuming projects, even if it's done p
Hello Stackers!
We're opening up the sign-up sheet for leadership training beyond the TC,
Board and Foundation staff to the whole community.
What: Leadership Training, customized for members of the OpenStack Community
When: April 11/12/13
Where: ZingTrain, in Ann Arbor, Michigan.
If you can conf
On 3/2/2017 10:26 AM, Matt Riedemann wrote:
Tracking this under bug:
https://bugs.launchpad.net/nova/+bug/1669473
The details are in the bug. We've figured out the root cause and I've
got a workaround patch up in nova and Mehdi has a workaround patch up in
devstack, and we're testing the nova
Greetings,
During the PTG we discussed about the two goals that we picked for Pike:
https://governance.openstack.org/tc/goals/pike/index.html
Like we did during Ocata cycle, PTLs have to update the governance
repository with the artifacts planned or done in their projects.
Some guidance for PTLs
On Thu, Jan 12, 2017 at 3:06 PM, Yolanda Robla Mota wrote:
> From my point of view, i've been using that either on infra with
> puppet-infracloud, glean.. and now with TripleO. So in my opinion, it shall
> be an independent project, with core contributors from both sides.
>
> On Thu, Jan 12, 2017
Hi,
I'm canceling the drivers meeting today due to a last minute conflict for
me.
If you have a feature you want for Pike, try to get the RFE filed soon
otherwise you will risk the chance of us being over-committed for Pike if
you submit it later in the cycle.
Cheers,
Kevin Benton
__
On 02/03/17 03:19 PM, Matt Riedemann wrote:
> This is the fix:
>
> https://review.openstack.org/#/c/440739/
yay! thanks for the help!
--
gord
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: op
W dniu 02.03.2017 o 20:19, Joshua Harlow pisze:
>> 1. Kolla output is nightmare to debug.
>>
>> There is --logs-dir option to provide separate logs for each image build
>> but it is not used. IMHO it should be as digging through such logs is
>> easier.
>>
>
> I to find the kolla output a bit painf
On Thu, Mar 02 2017, Joshua Harlow wrote:
> So before I start to go much farther on this (and start to dive into what
> people are doing and why the various implementations exist and proposing a
> cross-project solution, tooz, or etcd, or zookeeper or other...) I wanted to
> get general feedback (
I mentioned this in the nova meeting today [1] but wanted to post to the
ML for feedback.
We didn't talk about spec or feature freeze dates at the PTG. The Pike
release schedule is [2].
Spec freeze
---
In Newton and Ocata we had spec freeze on the first milestone.
I'm proposing that
On 3/2/17 9:45 AM, Ian Cordasco wrote:
> -Original Message-
> From: Telles Nobrega
> Reply: OpenStack Development Mailing List (not for usage questions)
>
> Date: March 2, 2017 at 08:01:29
> To: OpenStack Development Mailing List (not for usage questions)
>
> Cc: [email protected]
Julien Danjou wrote:
On Thu, Mar 02 2017, Joshua Harlow wrote:
So before I start to go much farther on this (and start to dive into what
people are doing and why the various implementations exist and proposing a
cross-project solution, tooz, or etcd, or zookeeper or other...) I wanted to
get ge
That's right, one more countdown email for Ocata.
Focus
-
The release team will be ready to tag the final releases for all
cycle-trailing projects on 8 March.
Release Tasks
-
Liaisons for cycle-trailing projects should prepare their final
release candidate tags by Monday 6 March
Hi Anil,
I met the same issue in my local devstack environment.
Do you use proxy when you execute stack.sh script in your environment?
If so, please try to set no_proxy parameter.
See also:
https://answers.launchpad.net/devstack/+question/245480
Regards,
Kaz
From: Anil Rao
Subject: [openstack
Bug/RFE is up!
https://bugs.launchpad.net/neutron/+bug/1669630
Hopefully that sums of what I'm ideally after well enough, and is useful
to the greater community and project as a whole.
Cheers,
Adrian Turjak
On 01/03/17 22:00, Adrian Turjak wrote:
> Hello Kevin,
>
> Thanks for the prompt respons
On 03/02/2017 03:31 PM, Emilien Macchi wrote:
>>> 1) Move diskimage-builder into own (big tent?) project. Setup a new PTL,
>>> etc.
> Let's move forward with this one if everybody agrees on that.
>
> DIB folks: please confirm on this thread that you're ok to move out
> DIB from TripleO and be an i
On Mon, Feb 27, 2017 at 11:20 AM, Emilien Macchi wrote:
> On Mon, Feb 27, 2017 at 11:02 AM, Steven Hardy wrote:
>> Hi all,
>>
>> Over the recent PTG, and previously at the design summit in Barcelona,
>> we've had some productive cross-project discussions amongst the various
>> deployment teams.
>
Hi cinder team:
We met a problem about backup create recently.
The backup can be created from volumes or snapshots. In the both cases, the
volume' s status is set to 'backing-up'.
But as I know, when users create backup with snapshots, the volume is not
used(Correct me if I'm wrong). So why the v
As discussed in today's Glance meeting, we'll have a one-hour virtual
meetup next week to get things rolling. Please indicate your
availability on this doodle poll:
http://doodle.com/poll/eh2mk4fdwgd4sv7b
If none of those time options work, reply to this email with a
counter-proposal. Please re
Hi Team,
I have question regarding multi-networks and multi-tenants
Currently Gluon supported only one network and subnet i.e GluonNetwork and
GluonSubnet respectively
which i can see hard code values at path
https://github.com/openstack/gluon/blob/aa7edbf878c64829ef2e028c8cd0e5bb36ea1d51/gluon/pl
Hello folks,
we discussed a lot since the PTG about issues with gate stability; we need
a stable and reliable gate to ensure smooth progress in Pike.
One of the issues that stands out is that most of the times during test
runs our test VMs are under heavy load.
This can be the common cause behind
94 matches
Mail list logo
