Hi all
You can edit the etherpad if you want to update agenda...or reply be email on
item1-4 below.
https://etherpad.openstack.org/p/meghdwar
Would like to meet for discussions for BOF and agenda as we can not wait for
2nd Wednesday, so lets meet Wednesday
from 7-8am PDT (Wed 14:00-15:00
I see. I'll draft a blueprint after essential study on this requirement.
And thank you for the information on add-new-datasource document.
--
Yujun
On Wed, Sep 7, 2016 at 1:31 PM Weyl, Alexey (Nokia - IL) <
alexey.w...@nokia.com> wrote:
> Hi Yujun,
>
> I don’t think we have a support for
Hi Yujun,
I don’t think we have a support for different versions of openstack at the same
time at the moment.
We have thought of such a requirement yet, but I think it can be done.
If you can, please add a blueprint with all the details for such a feature.
In addition, we now have a
One additional question about openstack datasource.
Is it possible to connect *multiple* openstack data sources, furthermore,
different version of openstack (liberty, newton), at the same time?
To monitor existing systems, this might be a common requirement.
On Thu, Sep 1, 2016 at 5:16 PM Yujun
I have no vote, but my nonvote is a hearty +1
Tony is amazing.
--Rocky
-Original Message-
From: Amrith Kumar [mailto:amr...@tesora.com]
Sent: Tuesday, September 06, 2016 10:56 AM
To: d...@doughellmann.com
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
An explicit tag would be helpful to catch the eyes of the team. :)
Br,
Chao
-原始邮件-
发件人: "Li Hao"
发送时间: 2016年9月6日 星期二
收件人: "openstack-dev@lists.openstack.org"
抄送:
主题: [openstack-dev] 转发: A mail from BJUT student
As a
On Tue, Sep 6, 2016 at 6:16 AM, Attila Darazs wrote:
> I think Third party gating is solid enough to make it vote, not just post
> results.
>
> Currently we have a gate job breaking and I almost submitted something
> without everything passing. Would be useful to make it
Welcome persisyemcelzy!
From: persistencelzy [persistence...@163.com]
Sent: 06 September 2016 19:22
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]
Hello。
Welcome, seems lots of contributors are joining the mail-list and landing in
tricircle after the message sent in the irc.
From: liukun [kk_li...@163.com]
Sent: 06 September 2016 19:43
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]
Welcome yuquanle, new contributor!
From: yuquanle [yuqua...@126.com]
Sent: 06 September 2016 19:36
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]
hello!
__
> On 6 Sep 2016, at 11:14 PM, Maxime Belanger wrote:
>
> Hey Sam,
>
> Are the driver you are implementing stores the index in Gnocchi index or
> directly in influx?
> In other words, are you fully using influx under gnochi API?
Hi Max,
The index lives in gnocchi
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 managers team.
On Tue, Sep 6, 2016 at 2:17 PM, Jeremy Stanley
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 provided assistance to new folks. How is it normally handled if
more than one
On Tue, Sep 6, 2016 at 4:24 PM, Jim Rollenhagen wrote:
> On Mon, Aug 29, 2016 at 5:03 AM, Lucas Alvares Gomes
> wrote:
>> Hi,
>>
>> I overall agree with the proposed plan. I like the idea of having a
>> "supported" flag (or another name as per
On 9/6/2016 2:48 PM, Martin Millnert wrote:
Hi,
Goal:
I'd like to replicate the industry standard of providing a on-by-
default (UI) option to auto-assign a floating IP to a newly launched
instance. It must be toggleable however (to follow industry standard).
Floating IPs aren't required
Hi Timofei,
Based on your post, it sounds like you plan to take over the bug team
meetings? Maybe with Markus stepping down, this could be a good
opportunity to reconsider our meeting schedule. Our meetings are
generally not well attended and I'm not sure if a weekly meeting is
necessary.
Also,
On Mon, Aug 29, 2016 at 5:03 AM, Lucas Alvares Gomes
wrote:
> Hi,
>
> I overall agree with the proposed plan. I like the idea of having a
> "supported" flag (or another name as per Kurt's email) that makes it
> easy mark a driver as "unsupported" indicating it might be
Hi,
Goal:
I'd like to replicate the industry standard of providing a on-by-
default (UI) option to auto-assign a floating IP to a newly launched
instance. It must be toggleable however (to follow industry standard).
With openstackclient I'm hoping the feature could be added through e.g
Hello everyone,
Bug team meeting on Sept. 13 is canceled. So the next time it will be Sept.
20 18:00 UTC.
By that time I'll update agenda [1], everyone is welcome to do the same.
Timofey
[1] - https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam
Hi Kuryrs!
Yesterday in the meeting we discussed about the need to design a way for the
functional testing to happen for the Kuryr-Kubernetes integration. I studied
the possibilities today and came up with the following proposal (After the
proposal I'll put more detailed explanations).
Tony Breeds wrote:
On Fri, Sep 02, 2016 at 12:29:04PM -0400, Mike Bayer wrote:
is the failure here something that comes up in gnocchi's test suite?
Could there be some way that oslo libraries run the test suites of all
consuming projects before a patch and/or a release? (apologies if we
We are excited to announce the release of:
oslo.db 4.13.2: Oslo Database library
This release is part of the newton stable release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.db
With package available at:
https://pypi.python.org/pypi/oslo.db
Please
On 2016-09-06 14:05:19 -0400 (-0400), Doug Hellmann wrote:
> Excerpts from Jeremy Stanley's message of 2016-09-06 17:53:57 +:
> > On 2016-09-06 11:36:01 -0400 (-0400), Doug Hellmann wrote:
> > > I would like to add Tony Breeds to the "Release Managers" team in
> > > gerrit. This would give him
Excerpts from Jeremy Stanley's message of 2016-09-06 17:53:57 +:
> On 2016-09-06 11:36:01 -0400 (-0400), Doug Hellmann wrote:
> > I would like to add Tony Breeds to the "Release Managers" team in
> > gerrit. This would give him +2 permissions on openstack-infra/release-tools
> > and on
It's been great working with you and you've done such a great job with
the bugs team!
I'd be more than happy to pick up the Bug Czar role and continue with
the great work you started.
--
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
Doug,
This is a great addition; Tony's reviews are very helpful, he asks great
questions and provides insightful feedback. And when you are in a bind, he has
great suggestions.
+1
Thanks,
-amrith
> -Original Message-
> From: Doug Hellmann [mailto:]
> Sent: Tuesday, September 06,
On 2016-09-06 11:36:01 -0400 (-0400), Doug Hellmann wrote:
> I would like to add Tony Breeds to the "Release Managers" team in
> gerrit. This would give him +2 permissions on openstack-infra/release-tools
> and on openstack/releases. I feel his reviews on both of those repos
> have already
Hey all,
here is a summary of TripleO-UI related TripleO RC1 work:
Tripleo-common patches required by TripleO-UI:
- roles listing: https://review.openstack.org/#/c/330283/
- validations run_groups workflow fix:
https://review.openstack.org/#/c/366055/
- Include environments which aren't
On 09/06/2016 11:42 AM, Ihar Hrachyshka wrote:
> Jeremy Stanley wrote:
>
>> On 2016-09-06 15:36:42 +0200 (+0200), Andreas Jaeger wrote:
>>> On 2016-09-06 15:30, Ihar Hrachyshka wrote:
Andreas Jaeger wrote:
> On 2016-09-06 15:02, Ihar Hrachyshka
On Tue, Sep 6, 2016 at 1:23 PM, Jim Rollenhagen wrote:
> We're cancelling the next two meetings as well, for the same reason.
>
> We'll meet again on September 27.
I'm bad at counting, apparently, the next meeting will be September 20.
// jim
>
> On Tue, Aug 30, 2016
We're cancelling the next two meetings as well, for the same reason.
We'll meet again on September 27.
// jim
On Tue, Aug 30, 2016 at 1:32 PM, Jim Rollenhagen
wrote:
> Sorry for the late notice, but we decided we'd rather keep working on
> Newton things this week
Hi Takashi,
Yes, this update was for bug 1529595.
Thanks,
Anil
-Original Message-
From: Takashi Yamamoto [mailto:yamam...@midokura.com]
Sent: Monday, September 05, 2016 11:29 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev]
On 2016-09-06 17:42:03 +0200 (+0200), Ihar Hrachyshka wrote:
[...]
> There are two related but separate questions here:
> - is there time when we can drop API from api-ref when it’s removed in code?
> - if so, when is it: right when the API is dropped, or when all branches
> supporting it are
Hi,
we have this latent bug where we pass objects for subnetpools into
extension functions. (That was a mistake made when switching to using
objects in base db plugin for the resource.) Now, we want to revert to
passing db models as we did before, so that our plugin api is consistent
and
+1. def.
I have always found his reviews quite detailed and constructive.
On 9/6/16 11:36 AM, Doug Hellmann wrote:
> Team,
>
> I would like to add Tony Breeds to the "Release Managers" team in
> gerrit. This would give him +2 permissions on openstack-infra/release-tools
> and on
Gyorgy Szombathelyi wrote:
-Original Message-
From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
Gyorgy Szombathelyi wrote:
Hi!
Maybe I'm overseeing something, but I'm wondering if table renames
> -Original Message-
> From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
>
> Gyorgy Szombathelyi wrote:
>
> > Hi!
> >
> > Maybe I'm overseeing something, but I'm wondering if table renames
> > breaks rolling upgrades.
>
> Yes, they would. Do
On Tue, Sep 6, 2016 at 10:44 AM, Ihar Hrachyshka
wrote:
> Alexander wrote:
>
> FYI,
>>
>> A similar discussion was held for an api-ref change in Glance:
>> https://review.openstack.org/#/c/356693/
>>
>
> Thanks for the link, it led me to this
Davanum Srinivas wrote:
> +1 Welcome Tony!
+1
Hopefully we won't break him by stretching him even more :)
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Alexander wrote:
FYI,
A similar discussion was held for an api-ref change in Glance:
https://review.openstack.org/#/c/356693/
Thanks for the link, it led me to this discussion:
http://lists.openstack.org/pipermail/openstack-dev/2016-August/101501.html
From
Thanks Ihar for taking the lead on this while everyone in the US was
(mostly) on vacation, much appreciated :)
Ihar Hrachyshka wrote:
Ihar Hrachyshka wrote:
Julien Danjou wrote:
On Fri, Sep 02 2016, Mike Bayer wrote:
I've augmented it with
Jeremy Stanley wrote:
On 2016-09-06 15:36:42 +0200 (+0200), Andreas Jaeger wrote:
On 2016-09-06 15:30, Ihar Hrachyshka wrote:
Andreas Jaeger wrote:
On 2016-09-06 15:02, Ihar Hrachyshka wrote:
[...]
Since neutron-lib is branched on stable/* boundary, I
+1 Welcome Tony!
-- Dims
On Tue, Sep 6, 2016 at 11:36 AM, Doug Hellmann wrote:
> Team,
>
> I would like to add Tony Breeds to the "Release Managers" team in
> gerrit. This would give him +2 permissions on openstack-infra/release-tools
> and on openstack/releases. I feel
Team,
I would like to add Tony Breeds to the "Release Managers" team in
gerrit. This would give him +2 permissions on openstack-infra/release-tools
and on openstack/releases. I feel his reviews on both of those repos
have already demonstrated a good attention to detail, especially
of the release
On 2016-09-06 15:36:42 +0200 (+0200), Andreas Jaeger wrote:
> On 2016-09-06 15:30, Ihar Hrachyshka wrote:
> > Andreas Jaeger wrote:
> >
> >> On 2016-09-06 15:02, Ihar Hrachyshka wrote:
> >>> [...]
> >>> Since neutron-lib is branched on stable/* boundary, I feel that it would
> >>>
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. Since then the code has grown, but we kept
with
FYI,
A similar discussion was held for an api-ref change in Glance:
https://review.openstack.org/#/c/356693/
On Sep 6, 2016, at 6:39 AM, Andreas Jaeger
> wrote:
On 2016-09-06 15:30, Ihar Hrachyshka wrote:
Andreas Jaeger >
We are jubilant to announce the release of:
XStatic-smart-table 1.4.13.2: smart-table 1.4.13 (XStatic packaging
standard)
With package available at:
https://pypi.python.org/pypi/XStatic-smart-table
For more details, please see below.
Changes in XStatic-smart-table 1.4.13.1..1.4.13.2
Hi!
Maybe I'm overseeing something, but I'm wondering if table renames breaks
rolling upgrades.
E.g. if I'm upgrading neutron server instances one-by-one, and doing a db
expand during the process,
the old neutron-server instances will continue to work. However, without the
new renamed tables,
Gyorgy Szombathelyi wrote:
Hi!
Maybe I'm overseeing something, but I'm wondering if table renames breaks
rolling upgrades.
Yes, they would. Do you suggest that we allowed such a migration anywhere
in Newton?
E.g. if I'm upgrading neutron server
Hi,
We have weekly Nova API meeting tomorrow. The meeting is being held
Wednesday UTC1300 and irc channel is #openstack-meeting-4.
The proposed agenda and meeting details are here:
https://wiki.openstack.org/wiki/Meetings/NovaAPI
Please feel free to add items to the agenda.
Thanks
On Tue, Sep 6, 2016 at 10:28 AM, Qasim Sarfraz wrote:
>
>>
>> It is not clear to me what this module would deploy.
>> Could you give more details here?
>> Would it deploy PLUMgrid IO Visor and dependencies?
>
> It will install PLUMgrid SDN Platform and PLUMgrid IO Visor which
Ian Wienand wrote:
> diskimage-builder would like to request a feature/v2 branch.
> [...]
Sure thing.
What would you like the branching SHA to be ? Current HEAD ?
We can continue this discussion on #openstack-release.
--
Thierry Carrez (ttx)
> It is not clear to me what this module would deploy.
> Could you give more details here?
> Would it deploy PLUMgrid IO Visor and dependencies?
>
It will install PLUMgrid SDN Platform and PLUMgrid IO Visor which are
dependencies for PLUMgrid Neutron Plugin. All the calls from PLUMgrid
Neutron
Although we are in a release freeze for libraries, we have several
bug fix release requests. We're evaluating these on a case-by-case
basis, and processing some of them. To make that easier, please
make sure to include information about the critical bugs being fixed
by the proposed release when
Hi,
1) lets call it for the times - Overview
2) Actions statistics - because there is a statistic by actions
3) I suggest to keep it. And add to the docs that we have idle and load
durations. I think people not fully understand those two terms and to
change report is not the best way to improve
Ihar Hrachyshka wrote:
Julien Danjou wrote:
On Fri, Sep 02 2016, Mike Bayer wrote:
I've augmented it with mapper-level SQLAlchemy API use.
Awesome, thanks. :)
And "augmented" makes it sounds so futurist, whoohhh. :)
Ouch, sorry for that bug in
A formal networking-ovn team meeting has been setup. The first meeting
is this Thursday 18:00 UTC. See [1] for meeting details. See [2] for
meeting agenda.
[1] https://review.openstack.org/#/c/363906/
[2]
On 2016-09-06 15:30, Ihar Hrachyshka wrote:
> Andreas Jaeger wrote:
>
>> On 2016-09-06 15:02, Ihar Hrachyshka wrote:
>>> [...]
>>> Since neutron-lib is branched on stable/* boundary, I feel that it would
>>> be fine to keep one-to-one relationship between neutron and neutron-lib
Andreas Jaeger wrote:
On 2016-09-06 15:02, Ihar Hrachyshka wrote:
[...]
Since neutron-lib is branched on stable/* boundary, I feel that it would
be fine to keep one-to-one relationship between neutron and neutron-lib
api-ref branches.
We only publish the api-ref documents
Hi! We still have not landed the arch-wg spec [1] just yet, but there
seems to be broad base consensus. So I believe it is time to start
having regular IRC meetings to keep forward momentum.
I've proposed [2] that we have meetings on Thursdays at 1900 UTC. I
noticed that Poppy was scheduled to
Hi all -
I've got a handful of volunteers (BCC'd here), which should be plenty
for round 1. Please expect some further communication with me this
afternoon with details on how to access the app, what to test, and to
log in, etc...
Thank you for the assist!
Jimmy McArthur
Major Hayden
On 2016-09-06 15:02, Ihar Hrachyshka wrote:
> [...]
> Since neutron-lib is branched on stable/* boundary, I feel that it would
> be fine to keep one-to-one relationship between neutron and neutron-lib
> api-ref branches.
We only publish the api-ref documents from master,
Andreas
--
Andreas
On 9/6/16, 2:02 PM, "Ihar Hrachyshka" wrote:
>Akihiro Motoki wrote:
>
>> What releases should we support in API references?
>> There are several options.
>>
>> 1. The latest stable release + master
>> 2. All supported stable releases + master
>> 3. more
2016-09-06 22:02 GMT+09:00 Ihar Hrachyshka :
> Akihiro Motoki wrote:
>
>> What releases should we support in API references?
>> There are several options.
>>
>> 1. The latest stable release + master
>> 2. All supported stable releases + master
>> 3. more
Hey Sam,
Are the driver you are implementing stores the index in Gnocchi index or
directly in influx?
In other words, are you fully using influx under gnochi API?
Max
From: Sam Morrison
Sent: September 5, 2016 9:24:21 PM
To: Julien
Excerpts from joehuang's message of 2016-09-06 02:12:45 +:
>
> > A full rewrite of the library that doesn't take under consideration the
> > existing
> > deployed technologies is not going to be of any help, IMHO. The reason being
> > that upgradability would be broken and that's a no-go. I
Akihiro Motoki wrote:
What releases should we support in API references?
There are several options.
1. The latest stable release + master
2. All supported stable releases + master
3. more older releases too?
Option 2 sounds reasonable to me.
This question is raised in the
Option 2 sounds reasonable to me too. :)
On Tue, Sep 6, 2016 at 2:39 PM, Akihiro Motoki wrote:
> What releases should we support in API references?
> There are several options.
>
> 1. The latest stable release + master
> 2. All supported stable releases + master
> 3. more
What releases should we support in API references?
There are several options.
1. The latest stable release + master
2. All supported stable releases + master
3. more older releases too?
Option 2 sounds reasonable to me.
This question is raised in the neutron api-ref patch [1].
This patch drops
Hi all!
We are gong to release fuel-devops framework version 3.0.2.
This thread is in active development.
Changes since 3.0.1:
- Do not print `k e y s` if no environments registered (Bug #1605599) [1]
- Extend _ManageSSH docstring with a note for current directory [2]
- Fix documentation about
On 09/05/2016 07:19 AM, Markus Zoeller wrote:
> Thanks a lot to the people who helped making Nova a better project by
> doing bug triage! Special thanks to auggy who put a lot(!) of effort
> into that.
>
> See you (hopefully) in Barcelona!
Thanks you for all your service here. It's been
Thanks all for your feedback.
I'll work on the changes Tues and push to Gerrit as a WIP.
Eric - thanks for pointing out eventlet.monkey_patch(thread=False). I
read about
that last week and will include pertinent info in the patch.
aimee
On Fri, Sep 2, 2016 at 1:34 PM, Tim Hinrichs
On Tue, Sep 6, 2016 at 5:25 AM, Qasim Sarfraz wrote:
> Hi,
>
> I wanted to start a thread around the creation of a new puppet module
> (puppet-plumgrid) for PLUMgrid OpenStack Networking Suite installation as
> per [1].
>
> The is required for PLUMgrid Neutron Plugin [2]
On 05.09.2016 18:33, Timofei Durakov wrote:
> Hi, folks,
>
> Thanks, Markus, for doing this job! I'm interested in this activity.
>
> Timofey
Awesome! Thanks a ton! We can use https://appear.in/os-nova-bugs for a
kickoff. I'll catch up with you in IRC for finding time and date. I'm in
the UTC+1
Here are some updates on the mentioned issues:
puppet-ceph not idempotent - Fixed with 363164
Ceph RGW needing a CI test (scenario004) - Passing excepted a Xenial issue
in 339106
The status of the RGW role related patches are:
289027 Deploying RGW role: being rechecked after a merge conflict
Hi,
The next notification subteam meeting will be held on 2016.09.06 17:00 UTC [1]
on #openstack-meeting-4.
Cheers,
Gibi
[1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160906T17
__
OpenStack
Dear all,
Ironic community needs a help to decide on the specification
of the openstack client command that provide the same functionality as
'ironic driver-raid-logical-disk-properties' .
Some propositions violate openstack client conventions for a user.
For now the available propositions
Triangel +1
At 2016-09-06 16:27:22, "joehuang" wrote:
Hello,
After the discussion in the #openstack-tricircle channel and mail-list, 4
candidates
available now, please vote the name for the new sub-project for api-gateway
functionality:
1. Triangel, 2 votes
The
+1 for trio2o.
At 2016-09-06 16:27:22, "joehuang" wrote:
Hello,
After the discussion in the #openstack-tricircle channel and mail-list, 4
candidates
available now, please vote the name for the new sub-project for api-gateway
functionality:
1. Triangel, 2 votes
The
Tricircle,I am coming!__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
There will be a live migration sub team meeting today, see:
https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration
Paul
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
+1 for trio2o
At 2016-09-06 19:29:54, "hejiawei" wrote:
Forwarding messages
From: "joehuang"
Date: 2016-09-06 16:27:22
To: "OpenStack Development Mailing List (not for usage questions)"
hello!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> From: Roman Podoliaka [mailto:rpodoly...@mirantis.com]
> Sent: September 06, 2016 11:55
>
> Looks like we already have something like that in the virt drivers interface:
>
> https://github.com/openstack/nova/blob/master/nova/virt/driver.py#L205-
> L216
>
> which is used in the resource
Hello。
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
-1 to the proposal. We have the ability (and we use it) to add guys to
several core groups. So, AFAIC, Vladimir's pros point #1 is covered. IMO,
pros point #2 looks questionable and not so important. Cons could be worse
(agree with Lukasz).
Thanks,
Aleksey Kasatkin
On Tue, Sep 6, 2016
Hi,
Fuel repositories include several languages/technologies (puppet, python,
ruby, make ...) Core engineer nominated for achievements in one project
may have average skills in another language/technology.
So, I give '-1' the suggestion.
However, we may have one group for python project, one
I think Third party gating is solid enough to make it vote, not just
post results.
Currently we have a gate job breaking and I almost submitted something
without everything passing. Would be useful to make it blocking.
Is there any reason not to do this?
Attila
Looks like we already have something like that in the virt drivers interface:
https://github.com/openstack/nova/blob/master/nova/virt/driver.py#L205-L216
which is used in the resource tracker.
On Tue, Sep 6, 2016 at 10:40 AM, Balázs Gibizer
wrote:
> Hi,
>
> In our
Hi all,
We're approaching release time, and there are still some concerns
whether or not we can make convergence the default. In particular we
have a somewhat longstanding issue with canceling creation [1]. The
good news is that this is almost fixed [2], and update cancel is
almost there too [3].
Hi,
I wanted to start a thread around the creation of a new puppet module
(puppet-plumgrid) for PLUMgrid OpenStack Networking Suite installation as
per [1].
The is required for PLUMgrid Neutron Plugin [2] whose changes are already
part of puppet neutron [3]. Let me know what do you people think
Hello!
Last time I created Third-Party CI in new environment, I faced
difficulties installing Jenkins by puppet-jenkins:
1) It really doesn't allow to pin Jenkins version, due to bug (or lack
of functionality) in Jenkins infrastructure:
https://issues.jenkins-ci.org/browse/INFRA-92
Hi,
-1 for the proposal
Regards,
Alex
On Tue, Sep 6, 2016 at 10:42 AM, Alexey Stepanov
wrote:
> Guys, I have one serious question: WHO will be global core?
> Example:
> I'm core reviewer in 2 repos, but I'm absolutely could not be core
> reviewer in puppet!
>
> On
Hi everyone,
As you probably know, the OpenStack Foundation staff has been busy over
the past year reorganizing how our events are laid out. Starting in
2017, the "Design Summit" part of the OpenStack Summit will be
refactored into two separate events: a general "Forum" for
community-wide
On Fri, 2 Sep 2016, Dan Smith wrote:
We should try to get this figured out before newton ships if possible. I
don't think I see it locally, but I have a large dev machine, so I'll
have to try to poke it harder.
I'm not clear on where we left this issue with allocation violations
on Friday?
trio2o +1
--
Best regards,
Ronghui Cao, Ph.D. Candidate
College of Information Science and Engineering
Hunan University, Changsha 410082, Hunan, China
At 2016-09-06 16:55:12, "hejiawei" wrote:
Forwarding messages
From: "joehuang"
trio2o +1, it's concise
At 2016-09-06 16:27:22, "joehuang" wrote:
Hello,
After the discussion in the #openstack-tricircle channel and mail-list, 4
candidates
available now, please vote the name for the new sub-project for api-gateway
functionality:
1. Triangel, 2
Guys, I have one serious question: WHO will be global core?
Example:
I'm core reviewer in 2 repos, but I'm absolutely could not be core
reviewer in puppet!
On Tue, Sep 6, 2016 at 11:31 AM, Igor Kalnitsky wrote:
> -1 for the proposal. I see no problems to add guys who're
-1 for the proposal. I see no problems to add guys who're familiar
with various sub-projects to multiple core groups.
On Tue, Sep 6, 2016 at 10:38 AM, Evgeniy L wrote:
> +1 to Lukasz.
> -1 to the proposal, we had it this way for a quite some time, and it was not
> good for the
1 - 100 of 114 matches
Mail list logo