Dear TC team,
Blazar team is thinking to push a request about adding Blazar project
into the OpenStack BigTent.
Based on documents in the governance repository[1], what the team is
required to do for the request is just adding project's definition to
references/projects.yaml. Is there anothe
Thanks Akihiro. From an FWaaS perspective, in agreement with Takashi on
points below. On repository name, I am not religious as long as we keep
things consistent.
Thanks
Sridar
On 6/1/17, 12:59 AM, "Takashi Yamamoto" wrote:
>On Wed, May 31, 2017 at 10:12 PM, Akihiro Motoki
>wrote:
>> Hi all,
Hello, stackers
I am just curious about the results of lots of discussions on the below
blueprint.
https://blueprints.launchpad.net/nova/+spec/support-volume-type-with-bdm-parameter
Can I ask what the concolusion is?
__
Open
Option 3 sound reasonable if wiki can be searchable.
-Original Message-
From: Blair Bethwaite [mailto:blair.bethwa...@gmail.com]
Sent: Thursday, June 01, 2017 8:44 PM
To: Alexandra Settle
Cc: OpenStack Operators ;
openstack-d...@lists.openstack.org; OpenStack Development Mailing List (n
On Thu, Jun 01, 2017 at 11:09:56AM +0100, Chris Dent wrote:
> A lot of this results, in part, from there being no single guiding
> pattern and principle for how (and where) the tests are to be
> managed.
It sounds like you want to write a general testing guide for openstack.
Have you started this
We caught up with some of the Catalyst guys at the Melbourne OpenStack
Australia day and they gave us a demo of this. Looks like a really nice
project that I think might replace some of existing user management
workflow.
Allowing project managers to invite collaborators and self-manage their
permi
Hi guys,
Karbor weekly meeting will be held at 1500 UTC each even week and
0900 UTC each odd week #openstack-meeting.
So next karbor IRC meeting will be held at 2017-06-06 0900 UTC.
Please feel free to add your topics here.
https://wiki.openstack.org/wiki/Meetings/Karbor
Hi Alex,
Likewise for option 3. If I recall correctly from the summit session
that was also the main preference in the room?
On 2 June 2017 at 11:15, George Mihaiescu wrote:
> +1 for option 3
>
>
>
> On Jun 1, 2017, at 11:06, Alexandra Settle wrote:
>
> Hi everyone,
>
>
>
> I haven’t had any fe
+1 for option 3
> On Jun 1, 2017, at 11:06, Alexandra Settle wrote:
>
> Hi everyone,
>
> I haven’t had any feedback regarding moving the Operations Guide to the
> OpenStack wiki. I’m not taking silence as compliance. I would really like to
> hear people’s opinions on this matter.
>
> To
On Thu, Jun 01, 2017 at 11:57:00AM -0400, Doug Hellmann wrote:
> Excerpts from Thierry Carrez's message of 2017-06-01 11:51:50 +0200:
> > Graham Hayes wrote:
> > > On 01/06/17 01:30, Matthew Treinish wrote:
> > >> TBH, it's a bit premature to have the discussion. These additional
> > >> programs d
Hi Team,
Given that there had been no objections, I would like to congrat and
welcome Justin and Rushil to our core team :)
On Thu, May 25, 2017 at 8:27 PM, Harm Sluiman
wrote:
> +1
> I haven't had time to actively participate these past months but have
> monitored and agree :)
>
> Thanks for y
On Thu, Jun 1, 2017 at 3:46 PM, Andrey Grebennikov <
agrebenni...@mirantis.com> wrote:
> We had a very similar conversation multiple times with Keystone cores
> (multi-site Keystone).
>
Geo-rep Galera was suggested first and it was immediately declined (one of
> the reasons was the case of complet
>
> And yes, I agree with the argument that we should be fair and treat
> all projects the same way. If we're going to move tests out of the
> tempest repository, we should move all of them. The QA team can
> still help maintain the test suites for whatever projects they want,
> even if those test
We had a very similar conversation multiple times with Keystone cores
(multi-site Keystone).
Geo-rep Galera was suggested first and it was immediately declined (one of
the reasons was the case of complete corruption of Keystone DB everywhere
in case of accidental table corrupt in one site) by me as
Hi Emilien,
I noticed that the configuration file was created using puppet. I submitted a
patch[1] that was targeting to include the changes in Devstack. My major
concern is with the value of WSGIScriptAlias which should be pointing to WSGI
script.
Regards/Saludos
Victor Morales
[1] https:/
On 1 Jun 2017, at 7:38, Thierry Carrez wrote:
> Thierry Carrez wrote:
>> In a previous thread[1] I introduced the idea of moving the PTG from a
>> purely horizontal/vertical week split to a more
>> inter-project/intra-project activities split, and the initial comments
>> were positive.
>>
>> We
On 06/01/2017 11:31 AM, Jeremy Stanley wrote:
On 2017-06-01 10:40:34 -0500 (-0500), Ben Nemec wrote:
[...]
Okay, so we're all set up, but now it appears we're all subscribed to every
tripleo bug as well. I think oslo-coresec used to be the same way, but at
some point it changed so I only get
Hey David,
Yeah I agree.
I responded to Rob with the same thinking.
I don’t mind taking a first pass at the Horizon blueprint / work to provide
an extensible space in the page header for plugins to post content.
And I will then move the content of this blueprint, as you suggest,
to the Vitrage-D
Greetings OpenStack community,
A very lively meeting today, with all the participants in a seemingly jovial
mood. Must be something in the water. Or maybe June just brings out
lightheartedness.
Much of the discussion centered on Monty Taylor's chain of patches [4]
regarding version discovery a
Hi all,
I've proposed a community-wide goal for Queens to move policy into code and
supply documentation for each policy [0]. I've included references to
existing documentation and specifications completed by various projects and
attempted to lay out the benefits for both developers and operators.
On 05/31/2017 11:06 PM, Mike Bayer wrote:
I'd also throw in, there's lots of versions of Galera with different
bugfixes / improvements as we go along, not to mention configuration
settings if Jay observes it working great on a distributed cluster
and Clint observes it working terribly, it c
OK, I'd assumed that from earlier conversations about py35 being a
multi-release goal, that it would have been a shoe-in. But yes, if it is still
a possibility that the community would do py1.75 in pike and not commit to the
other py1.75 in queens, sure, there's only one committed goal for queen
As discussed at today's Glance meeting, the priorities for this week
are to prepare for the P-2 milestone release. The changes below must
be merged by 12:00 UTC Wednesday 7 June 2017. Please give them your
full attention.
1 Image import refactor MVP
- https://review.openstack.org/#/c/443636/
-
There have been a couple of projects that would like some space in the
page header. I think the work in Horizon is to provide an extensible
space in the page header for plugins to post content. The UI plugin
for Vitrage, in this case, would then be responsible for populating
that content if desired
Thanks Doug for this one!
---
Emilien Macchi
On Jun 1, 2017 6:21 PM, "Doug Hellmann" wrote:
> Excerpts from jenkins's message of 2017-05-31 20:26:33 +:
> > Build failed.
> >
> > - puppet-nova-releasenotes http://logs.openstack.org/d9/
> d913ccd1ea88f3661c32b0fcfdac58d749cd4eb2/tag/puppet-no
Michał Jastrzębski wrote:
> Looks good! What is approximate size of L room?
L can fit 30-50 people. We'll get more precise once we start mapping
those to actual rooms.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailin
On 1 June 2017 at 09:22, Jeremy Stanley wrote:
> On 2017-06-01 16:38:05 +0200 (+0200), Thierry Carrez wrote:
> [...]
>> For teams that are placed on the Wednesday-Friday segment, please
>> let us know whether you'd like to make use of the room on Friday
>> (pick between 2 days or 3 days).
> [...]
Renat Akhmerov wrote:
> We have a weekly meeting next Monday, will it be too late?
Before Thursday EOD (when the Pike-2 deadline hits) should be OK.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usa
Amrith Kumar wrote:
> Thierry, isn't the py35 goal continuing for Queens?
That's an open question, which is discussed in its own thread:
http://lists.openstack.org/pipermail/openstack-dev/2017-May/117746.html
--
Thierry Carrez (ttx)
__
On 2017-06-01 10:40:34 -0500 (-0500), Ben Nemec wrote:
[...]
> Okay, so we're all set up, but now it appears we're all subscribed to every
> tripleo bug as well. I think oslo-coresec used to be the same way, but at
> some point it changed so I only get explicitly notified of security bugs.
> Does
On 2017-06-01 16:38:05 +0200 (+0200), Thierry Carrez wrote:
[...]
> For teams that are placed on the Wednesday-Friday segment, please
> let us know whether you'd like to make use of the room on Friday
> (pick between 2 days or 3 days).
[...]
As you didn't specify how to let you know, I'll just rep
Excerpts from jenkins's message of 2017-05-31 20:26:33 +:
> Build failed.
>
> - puppet-nova-releasenotes
> http://logs.openstack.org/d9/d913ccd1ea88f3661c32b0fcfdac58d749cd4eb2/tag/puppet-nova-releasenotes/cefa30a/
> : FAILURE in 2m 13s
>
This failure only prevented the release notes from
Excerpts from jenkins's message of 2017-05-31 22:46:21 +:
> Build failed.
>
> - swift-releasenotes
> http://logs.openstack.org/e9/e9032fbea361df790901022740ac837a2a02daa0/tag/swift-releasenotes/687d120/
> : FAILURE in 1m 47s
>
This failure was just with publishing the release notes after t
Sorry for the short notice but today's meeting has been cancelled. We'll
resume with our bug-triage on Tuesday and our next Meeting on next Thursday
at their usual times and places.
Amy (spotz)
__
OpenStack Development Mailing
Hey everybody!
I have submitted two potential goals for Queens:
https://review.openstack.org/#/c/468436 - add collection links
https://review.openstack.org/#/c/468437 - full discovery alignment
One is a subset of the other, so the decision is two-fold
* do we do this at all?
* do we do the sma
Excerpts from Chris Dent's message of 2017-06-01 11:09:56 +0100:
> On Wed, 31 May 2017, Doug Hellmann wrote:
> > Yeah, it sounds like the current organization of the repo is not
> > ideal in terms of equal playing field for all of our project teams.
> > I would be fine with all of the interop tests
Excerpts from Thierry Carrez's message of 2017-06-01 11:51:50 +0200:
> Graham Hayes wrote:
> > On 01/06/17 01:30, Matthew Treinish wrote:
> >> TBH, it's a bit premature to have the discussion. These additional
> >> programs do
> >> not exist yet, and there is a governance road block around this. R
Hi,
Due to a conflict today I am canceling the drivers meeting.
Cheers,
Kevin Benton
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
h
On 05/30/2017 10:05 AM, Emilien Macchi wrote:
On Tue, May 30, 2017 at 3:43 PM, Ben Nemec wrote:
On 05/30/2017 08:00 AM, Emilien Macchi wrote:
On Mon, May 29, 2017 at 9:02 PM, Jeremy Stanley wrote:
On 2017-05-29 15:43:43 +0200 (+0200), Emilien Macchi wrote:
On Wed, May 24, 2017 at 7:4
Excerpts from Emilien Macchi's message of 2017-06-01 15:31:10 +0200:
> On Wed, May 31, 2017 at 10:38 PM, Mike wrote:
> > Hello everyone,
> >
> > For this thread we will be discussing continuing Python 3.5+ support.
> > Emilien who has been helping with coordinating our efforts here with
> > Pike c
On Thu, Jun 01, 2017 at 01:46:21PM +0200, Julien Danjou wrote:
On Wed, May 31 2017, gordon chung wrote:
[…]
i'm not entirely sure this is an issue, just thought i'd raise it to
discuss.
It's a really interesting point you raise. I never thought we could do
that but indeed, we could. Maybe w
From: "Yujun Zhang (ZTE)"
Date: Thursday, 1 June 2017 at 18:10
On Thu, Jun 1, 2017 at 10:49 PM Afek, Ifat (Nokia - IL/Kfar Sava)
mailto:ifat.a...@nokia.com>> wrote:
So for now we agree that we need to add a UI for configuration information and
datasources status.
Sounds good. In order to i
We have encountered similar issue also in OPNFV.
It seems to be a problem of setuptools 36.0.0 and it is now removed from
pypi. Hope it resolves the vitrage gate tests as well.
See discussion in https://github.com/pypa/setuptools/issues/1042
On Thu, Jun 1, 2017 at 11:08 PM Afek, Ifat (Nokia - I
On Thu, Jun 1, 2017 at 3:47 PM, Abhishek Kane wrote:
> Hi Emilien,
>
> The bin does following things on controller:
> 1. Install core HyperScale packages.
Should be done by Puppet, with Package resource.
> 2. Start HyperScale API server
Should be done by Puppet, with Service resource.
> 3. Ins
On Thu, Jun 1, 2017 at 10:49 PM Afek, Ifat (Nokia - IL/Kfar Sava) <
ifat.a...@nokia.com> wrote:
So for now we agree that we need to add a UI for configuration information
> and datasources status.
>
>
Sounds good. In order to implement in UI, we shall also need api to expose
them right?
--
Yujun
Hi everyone,
I haven’t had any feedback regarding moving the Operations Guide to the
OpenStack wiki. I’m not taking silence as compliance. I would really like to
hear people’s opinions on this matter.
To recap:
1. Option one: Kill the Operations Guide completely and move the
Administratio
Hi,
Note that we are currently having problems with the Vitrage gate tests, related
to python-setuptools. Other projects experience similar problems. We hope to
fix it by the beginning of next week.
Best Regards,
Ifat.
__
On 01/06/17 07:46 AM, Julien Danjou wrote:
> Yes, write doc or log an issue at least. It's best way to keep a public
> track now on ideas and what's going on since it's what people are going
> to read and search into.
added here: https://github.com/gnocchixyz/gnocchi/issues/60
--
gord
Hi Yujun,
Indeed, during the initialization phase it might be beneficial to make sure the
user is aware of configuration problems (although I’m not sure that crashing is
the solution). The problem is that the same code is executed both in
initialization and later on, so telling the difference i
Thierry Carrez wrote:
> In a previous thread[1] I introduced the idea of moving the PTG from a
> purely horizontal/vertical week split to a more
> inter-project/intra-project activities split, and the initial comments
> were positive.
>
> We need to solidify how the week will look like before we o
We have a weekly meeting next Monday, will it be too late?
Renat Akhmerov
@Nokia
On 1 Jun 2017, 20:10 +0700, Thierry Carrez , wrote:
> Note that it's technically too late to change the release model
> (milestone-1 is the deadline), but since that kills two birds with one
> stone, I'd be willing t
Hi Emilien,
The bin does following things on controller:
1. Install core HyperScale packages.
2. Start HyperScale API server
3. Install UI packages. This will add new files to and modify some existing
files of Horison.
4. Create HyperScale user in mysql db. Create database and dump config. Add
p
Thierry, isn't the py35 goal continuing for Queens?
--
Amrith Kumar
amrith.ku...@gmail.com
> -Original Message-
> From: Thierry Carrez [mailto:thie...@openstack.org]
> Sent: Thursday, June 1, 2017 4:35 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [tc][ptls][a
On Wed, May 31, 2017 at 10:38 PM, Mike wrote:
> Hello everyone,
>
> For this thread we will be discussing continuing Python 3.5+ support.
> Emilien who has been helping with coordinating our efforts here with
> Pike can probably add more here, but glancing at our goals document
> [1] it looks like
Note that it's technically too late to change the release model
(milestone-1 is the deadline), but since that kills two birds with one
stone, I'd be willing to grant mistral an exception (as long as it's
done before milestone-2, which is next week).
Renat Akhmerov wrote:
> Thanks Thierry.
>
> To
Hi all,
thanks Monty for the feedback. I've started this set of patches in ironic
[0] (very WiP currently), and would really like some eyes on them (not
right now, as I plan to rewrite those basing on this conversation :) but
soon I hope). Also I have some questions/comments inline:
On Thu, May 2
On 01/06/17 03:51 AM, rajeev.satyanaray...@wipro.com wrote:
> I am working on bringing up Newton version of Openstack on 3
> Nodes(Controller, Compute and Network). I am using OVS with DPDK on my
> Compute Node and to get dpdk port related statistics on my Ceilometer, I
> have configured collectd
Thanks Thierry.
To me it sounds like even a better release model for us. We can discuss it with
a team at the next team meeting and make a decision.
Renat Akhmerov
@Nokia
On 1 Jun 2017, 17:06 +0700, Thierry Carrez , wrote:
> Renat Akhmerov wrote:
> > On 31 May 2017, 15:08 +0700, Thierry Carrez
On 31.5.2017 17:40, Dnyaneshwar Pawar wrote:
Hi Ben,
On 5/31/17, 8:06 PM, "Ben Nemec"
mailto:openst...@nemebean.com>> wrote:
I think we would need to see what your custom config templates look like
as well.
Custom config templates: http://paste.openstack.org/show/64/
Hello Dnyaneshwar,
Having heard only affirmative responses, I've added Mikhail Fedosin to
the Glance core group, with all the rights and privileges pertaining
thereto.
Welcome back to the Glance core team, Mike!
I'd also like to express my personal thanks to you for stepping up to
help out the Glance project in the
On Wed, May 31 2017, gordon chung wrote:
[…]
> i'm not entirely sure this is an issue, just thought i'd raise it to
> discuss.
It's a really interesting point you raise. I never thought we could do
that but indeed, we could. Maybe we built a great architecture after
all. ;-)
Easy solution: di
Another observation -
Steps:
1. openstack overcloud deploy --templates -e myconfig_1.yaml
2. openstack overcloud update overcloud
3. openstack overcloud deploy --templates -e myconfig_2.yaml
With this steps in sequence, configuration of myconfig_2.yaml is applied
successfully. (still config in st
On Thu, Jun 1, 2017 at 3:39 PM, Chris Dent wrote:
> On Wed, 31 May 2017, Doug Hellmann wrote:
>
>> Yeah, it sounds like the current organization of the repo is not
>> ideal in terms of equal playing field for all of our project teams.
>> I would be fine with all of the interop tests being in a pl
On Wed, 31 May 2017, Doug Hellmann wrote:
Yeah, it sounds like the current organization of the repo is not
ideal in terms of equal playing field for all of our project teams.
I would be fine with all of the interop tests being in a plugin
together, or of saying that the tempest repo should only c
Thanks for that Kirill. Optional sounds good. Right now I'm leaning
towards encrypting the full object model in the database rather than
selective attributes, I can't think of a reason not to do this and it
makes things more transparent and straight forward for the user. I've
added a spec for t
Renat Akhmerov wrote:
> On 31 May 2017, 15:08 +0700, Thierry Carrez , wrote:
>>> [mistral]
>>> mistral - blocking sqlalchemy - milestones
>>
>> I wonder why mistral is in requirements. Looks like tripleo-common is
>> depending on it ? Could someone shine some light on this ? It might just
>> mean m
On 31/05, Matt Riedemann wrote:
> On 5/31/2017 6:58 AM, Gorka Eguileor wrote:
> > Hi,
> >
> > As some of you may know I've been working on improving iSCSI connections
> > on OpenStack to make them more robust and prevent them from leaving
> > leftovers on attach/detach operations.
> >
> > There are
Graham Hayes wrote:
> On 01/06/17 01:30, Matthew Treinish wrote:
>> TBH, it's a bit premature to have the discussion. These additional programs
>> do
>> not exist yet, and there is a governance road block around this. Right now
>> the
>> set of projects that can be used defcore/interopWG is limit
Hey everyone,
The docs meeting will continue today in #openstack-meeting as scheduled
(Thursday at 16:00 UTC). For more details, and the agenda, see the meeting
page: -
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
The meeting chair will be me! Hope you can al
On 01/06/17 01:30, Matthew Treinish wrote:
> On Wed, May 31, 2017 at 03:45:52PM +, Jeremy Stanley wrote:
>> On 2017-05-31 15:22:59 + (+), Jeremy Stanley wrote:
>>> On 2017-05-31 09:43:11 -0400 (-0400), Doug Hellmann wrote:
>>> [...]
it's news to me that they're considering reversin
Amrith Kumar wrote:
> I agree, this would be a good thing to do and something which will definitely
> improve the overall ease of upgrades. We already have two Queens goals
> though; do we want to add a third?
Hmm, we only have one so far ?
https://governance.openstack.org/tc/goals/queens/index
Jeremy Stanley wrote:
> On 2017-05-19 09:22:07 -0400 (-0400), Sean Dague wrote:
> [...]
>> the project,
>
> I hosted the onboarding session for the Infrastructure team. For
> various logistical reasons discussed on the planning thread before
> the PTG, it was a shared session with many other "hori
On 31/05/17 15:12, Akihiro Motoki wrote:
Hi all,
As discussed last month [1], we agree that each neutron-related
dashboard has its own repository.
I would like to move this forward on FWaaS and VPNaaS
as the horizon team plans to split them out as horizon plugins.
A couple of questions hit me.
On Wed, May 31, 2017 at 10:12 PM, Akihiro Motoki wrote:
> Hi all,
>
> As discussed last month [1], we agree that each neutron-related
> dashboard has its own repository.
> I would like to move this forward on FWaaS and VPNaaS
> as the horizon team plans to split them out as horizon plugins.
>
> A
Hi All,
I am working on bringing up Newton version of Openstack on 3 Nodes(Controller,
Compute and Network). I am using OVS with DPDK on my Compute Node and to get
dpdk port related statistics on my Ceilometer, I have configured collectd to
use DPDKSTAT plugin and also enabled the collectd-ceil
75 matches
Mail list logo