+1.
__
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 Client,
> Don't do it? Evolve v1 as needed, bud I'd recommend keeping whatever users
> you currently have functional for as long as possible. Work with the API-WG
> to make sure what you're doing is driving toward an API that fits inside
> their best practices.
Thanks for your advice, surely
Hello,
I have registered a BP[1] for that.
Please let me know if you have any concerns.
[1]https://blueprints.launchpad.net/monasca/+spec/kairosdb-support
Thanks,
Pradeep Singh
On Fri, Feb 24, 2017 at 2:20 PM, Shinya Kawabata
wrote:
> Hi Pradeep
>
> Basic Cassandra support is already impleme
Hi All,
Do we have support for Baremetal and LXD monitoring in monasca?
Are we planning this support ?
Thanks,
Santhosh
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.
Hi All,
Earlier today the release team tagged PBR 2.0.0. The reason for the major
version bump is because warnerrors has been removed in favor of
warning-is-error from sphinx >= 1.5.0.
It seems that several projects outside both inside and outside OpenStack have
capped pbr <2.0.0 so we can't
Hi Julia,
Thank you for the proposal. It's a good idea to use a time slot of
ironic-neutron meeting.
Thanks,
Hiro Shiina
> -Original Message-
> From: Julia Kreger [mailto:juliaashleykre...@gmail.com]
> Sent: Tuesday, February 28, 2017 11:43 PM
> To: OpenStack Development Mailing List (no
Hello, team,
According to the discussion in the IRC, we'd like to move the weekly meeting
from UTC1300 to UTC1400, there are several options for this time slot, please
vote before next Monday, then I'll submit a patch to occupy the new time slot
and release the old time slot.
Poll link: http:/
Hi Kirill, Serg,
Thanks to your help, I could find a slight mistake at Heat url in
murano.conf.
And the situation progressed a little.
Thank you very much:)
Best regards
On 2017/02/28 22:57, Serg Melikyan wrote:
Atsumi,
I've checked the guide you are refering too, make sure your endpoint is
Hello Openstack-Devs,
I'm just trying to find out if there is any proposed work to make the
network RBAC a bit safer.
For context, I'm part of a company running a public cloud and we would
like to expose Network RBAC to customers who have multiple projects so
that they can share networks between
+1 from my vote.
Best Regards
Chaoyi Huang (joehuang)
From: Vega Cai [luckyveg...@gmail.com]
Sent: 01 March 2017 11:42
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle
C
+1
Zhiyuan
On Wed, 1 Mar 2017 at 11:41 Devale, Sindhu wrote:
> +1
>
> Sindhu
>
> From: joehuang
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Tuesday, February 28, 2017 at 8:38 PM
> To: openstack-dev
> Subject: [opens
It's wonderful for Victor Morales to be Tricircle core. Thanks for his
great contribution.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscri
On Tue, Feb 28, 2017 at 6:48 PM, Jay Pipes wrote:
> On 02/27/2017 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.
>>
>> It's clea
+1
Sindhu
From: joehuang mailto:joehu...@huawei.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, February 28, 2017 at 8:38 PM
To: openstack-dev
mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-
I think it a good solution, I already put +1 :)
And, as to the scenario testcases, shall we:
1) remove test steps/checks already coverd in API test
2) remove sequence test cases (such as test_server_sequence_suspend_resume),
othersize scenario will get fatter and fatter
Original Mail
Doing gradual refactoring and fixing plugins time to time needs lot of wait
and sync.
That needs:
1. Plugins to switch from current method usage. Plugins to have some other
function or same copy paste code what current scenario base class has.
2. Tempest patch to wait for plugin fix.
3. Plugins to
Hi Dave,
Thanks for your reply. I would like to answer your email like below:
> Offline rolling upgrades is part of the current Barbican project
Do you mean that Barbican supported to upgrade? Currently, there are 4 main
level during upgrade [1]
1. Support upgrade
2. Support roll
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 reviewer. I really think his
experience will help us substantially improve Trircirc
hi,
On Mon, Feb 27, 2017 at 8:34 PM, Andrea Frittoli
wrote:
> Hello folks,
>
> TL;DR: if today you import manager,py from tempest.scenario please maintain
> a copy of [0] in tree until further notice.
>
> Full message:
> --
>
> One of the priorities for the QA team in the Pike cyc
On Tue, Feb 28, 2017 at 7:04 PM, Clark Boylan wrote:
> On Tue, Feb 28, 2017, at 04:53 PM, Lance Bragstad wrote:
> > I took some time to consolidate my notes from the PTG [0]. Let me know if
> > there are big things I've missed, or if you have summaries of your own.
> >
> > Thanks to everyone who
On Tue, Feb 28, 2017, at 04:53 PM, Lance Bragstad wrote:
> I took some time to consolidate my notes from the PTG [0]. Let me know if
> there are big things I've missed, or if you have summaries of your own.
>
> Thanks to everyone who attended and participated!
>
> [0] http://lbragstad.com/keyston
I took some time to consolidate my notes from the PTG [0]. Let me know if
there are big things I've missed, or if you have summaries of your own.
Thanks to everyone who attended and participated!
[0] http://lbragstad.com/keystone-pike-ptg-summary/
_
So cool! Look forward to multi-node jobs as first class
Best Regards
Chaoyi Huang (joehuang)
From: Monty Taylor [mord...@inaugust.com]
Sent: 01 March 2017 7:26
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] Zuul v
On 02/27/2017 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.
It's clear that we share many common problems, such as patterns for major
version
Hi everybody!
This content can also be found at
http://inaugust.com/posts/whats-coming-zuulv3.html - but I've pasted it
in here directly because I know that some folks don't like clicking links.
tl;dr - At last week's OpenStack PTG, the OpenStack Infra team ran the
first Zuul v3 job, so it's time
On 28 February 2017 at 20:42, Rob Cresswell
wrote:
>> - Use [horizon-plugin] mailer tag to keep people up to date
>
> So the idea here is to send an email for changes that are likely to affect
> plugins; new libs for example, or changes to core components, with the
> [horizon-plugin] tag.
OK, tha
On Thursday morning at the PTG the Cinder team invaded the Nova room to
talk about cross-project items. The full etherpad is here [1].
Volume multi-attach
---
This got it's own very special etherpad [2]. We went over some of the
current status, like Cinder's 3.27 microversion (
The PTG was great. Not only was there three full days of Swift-specific dev
work, we had lots of opportunity to work with other projects. Here's a quick
rundown of the highs and lows of the week.
The first obvious benefit to the PTG is the relatively easy access to other
projects. Yes, there's
As some of you already know, I have been putting off releasing a
new version of reno until after the Ocata final release was tagged.
Now that Ocata is done and we're all back from the PTG, I've proposed
a version 2.1.0 in [1].
As described in the reno release notes [2], this new release changes th
Congrats everybody! well deserved.
Jean-Emile thank you for all your hard work!
On Tue, Feb 21, 2017 at 12:06 AM, Shedimbi, Prudhvi Rao <
prudhvi.rao.shedi...@intel.com> wrote:
> Thank You for giving me this opportunity. I will try to fulfill my role in
> the Core team to the best of my ability.
Hey Julia,
I like the idea of a using the old neutron/ironic meeting time as
general purpose meeting time slot. As the usage of the meeting changes,
would new the same meeting name and agenda page be used, or would
subteams rename the meeting and create a new agenda page? Personally I
would p
Hi Bernard,
Thanks for the notes! I just talked with Louis. We will pull the stable branch
for networking-sfc today.
I hope after the branch is pulled, everyone can help doing more testing on the
stable branch to make it more stable:-)
Thanks,
Cathy
-Original Message-
From: Bernard C
Hi ironic team,
Last cycle, I started holding some informal "review parties" for new
members of OSIC [0] to come together with other OSIC people who had
been working on OpenStack for a while and have group discussions about
technical topics related to ironic and generally how to be more
effective
Excerpts from na...@vn.fujitsu.com's message of 2017-02-28 09:52:13 +:
> Hi everyone,
>
> Recently, there are many emails to discuss a topic that "Why are projects
> trying to avoid Barbican, still?" [0]. That is very an interesting topic. Now
> I would like to make a new topic related to Ro
You will also need the related Neutron and ansible patch to run it.
Please keep me posted –
German
From: Michael Johnson
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, February 28, 2017 at 11:54 AM
To: "'OpenStack Development Mailing List (not for usag
Hello all,
The Picasso team will be running our first meeting next Tuesday. All those
interested in the project are welcome!
For those of you not familiar with Picasso, it provides a platform for
Functions as a Service (FaaS) on OpenStack [1].
*Tuesday, March 7th, 2017 Meeting Agenda:*
Starting
Hi Santhosh,
The correct path to the git repo is:
http://git.openstack.org/cgit/openstack/openstack-ansible-os_octavia/
Though at this point the code has not merged, so you will need to pull from the
patch if you want to try it out:
https://review.openstack.org/#/c/417210/
Michael
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 testing as we
start working on Pike.
These two issues have been identified by ela
>
> I am usually on freenode during US daytime, #openstack-third-party-ci
> and #openstack-infra are good places to ask questions.
>
Forgot to mention my IRC nick is mmedvede
__
OpenStack Development Mailing List (not for usa
On Mon, Feb 27, 2017 at 11:12 PM, Nilesh Savant
wrote:
> Hello Mikhail,
>
>
>
> We are operating CI for Veritas HyperScale, Due to this changes our CI
> started failing,
>
>
>
> Could you please help us by providing the sample local.conf file as per new
> changes.
>
>
> It will be great if you can
Hi all,
Reminding that the Common Classification Framework meeting today hasn't been
canceled.
The meeting will be held on 1700 UTC @ #openstack-meeting.
Agenda:
https://wiki.openstack.org/wiki/Neutron/CommonFlowClassifier#Discussion_Topic_28_February_2017
Best regards,
Igor.
_
On 02/27/2017 04:53 PM, Emilien Macchi wrote:
> Here's a summary of what was said at PTG. Feel free to comment if I
> missed something.
...
> # Deriving TripleO Parameters from Introspected Data
> Driver: fultonj, skramaja
> Summary: Set automatically some parameters based on the deployment
> type
On Tue, Feb 28 2017, gordon chung wrote:
> this is a continuation of the ceilometer-api is deprecated discussion.
> with that marked as deprecated as of Ocata, what do we do with threshold
> rule alarms as it relies on ceilometer-api? logically, we'd deprecate it
> as well. this will require he
hi,
this is a continuation of the ceilometer-api is deprecated discussion.
with that marked as deprecated as of Ocata, what do we do with threshold
rule alarms as it relies on ceilometer-api? logically, we'd deprecate it
as well. this will require heat as well to deprecate it on their end.
wha
Hi,
I will miss the next two IRC meetings, so here is a quick summary
email of PTG topics of interest for networking-sfc in the Pike cycle.
* Release, stable branching, stadium requirements
For Ocata, neutron-lib patches are waiting for our stable branch
creation (should be OK today?). The releas
Kevin,
Thanks for putting this together. Regarding the point about DVR, "Allow DVR
to perform floating IP translations at central node if
compute node has no external network access", we already have a RFE, thanks
to Swami: https://bugs.launchpad.net/neutron/+bug/1667877
Cheers
On Tue, Feb 28, 2
Greetings fellow ironic humanoids!
As many have known, I've been largely attempting to drive Boot from
Volume functionality in ironic over the past two years. Largely, in a
slow incremental approach, which is in part due to how I perceived it
to best fit into the existing priorities when the disc
Hi,
The next notification subteam meeting will be held on 2017.02.28 17:00
UTC [1] on #openstack-meeting-4.
Cheers,
gibi
[1]
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170228T17
__
OpenStack Devel
Hi Nam--
Thanks for writing. Offline rolling upgrades is part of the current
Barbican project. Better support and documentation for upgrades would be
a welcome addition.
1) API Versioning
Currently, Barbican only has one API version. The wiki you reference is
an old list of ideas that we st
Hi All
Just a reminder that we'll be running our regular bug day on the 2nd March
(this coming thursday).
Focus, as always, is to touch new bugs and work through in priority order
for any fixes!
Please co-ordinate any activity in the #openstack-charms channel!
Cheers
James
On Tue, Feb 28, 2017 at 07:49:01AM -0600, Mikhail Medvedev wrote:
> On Tue, Feb 28, 2017 at 2:52 AM, Guo, Ruijing wrote:
> > Hi, CI Team,
> >
> >
> >
> > I’d like to know if openstack CI VM support nested virtualization.
> >
>
> OpenStack CI infrastructure is using nested visualization inside of
Atsumi,
I've checked the guide you are refering too, make sure your endpoint is
setup properly in Keystone. List endpoints and services in Keystone and
make sure that they mapped to correct region
On Tue, Feb 28, 2017 at 1:07 AM, Kirill Zaitsev
wrote:
> Well, looks like you don’t have murano-ap
On Tue, Feb 28, 2017 at 2:52 AM, Guo, Ruijing wrote:
> Hi, CI Team,
>
>
>
> I’d like to know if openstack CI VM support nested virtualization.
>
OpenStack CI infrastructure is using nested visualization inside of
devstack VMs to perform tempest testing. But at the moment accel=tcg
is used (emulat
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
Thanks for notice that Alex, as you said, a typo. Here comes the correct
information just to be super clear - including the agenda.
Wednesday 1st March 2017
1400 UTC #openstack-meeting-3
Agenda
1. Reveiw last weeks agenda items (APs)
2. Report from PTG in Atlanta
3. Discuss "User story templat
Hi,
> have you tried to disable port security?
I have disabled security group from both the ports. After disabling I am not
able to ping on the instances.
===
neutron CLI is deprecated and will be removed in the fut
**IMPORTANT** We are planning to transition the first batch of jobs on
the very beginning of the Pike cycle! What this means is that on, or
very close to 10th of March we're going to switch over at least the
multinode scenario jobs (1 to 5) to be driven by Quickstart, but
possibly more.
As al
Hi everyone,
Following below is a high-level update of what was discussed during
the PTG. If there is something I left out, I either forgot about it or
didn't get a chance to sync up with the contributors and I don't have
a summary so please reply to this email thread to add it. However, if
you wa
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.
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?
>>
>> As a person who sends a lot of process-driven email to this list,
>> it is not wor
Hey everyone,
Horizon is moving to requiring only a single core review for code approval.
Note that cores are not obliged to approve on a single +2; if a core would like
a second opinion for patches that are complex or high risk, that is also fine.
We still require at least one of the core revi
On Tue, Feb 28, 2017 at 4:05 PM, Manik Bindlish
wrote:
> Hi All,
>
>
>
> I am facing an issue in visualizing port-mirroring information.
>
>
>
> 1.)Created 2 VMs:
>
> VM1: ubuntu3(10.0.0.3, floating IP: 192.168.200.252) – Tap service created
>
> VM2: ubuntu2(10.0.0.12, floating ip: 192.168
Hi everyone,
Recently, there are many emails to discuss a topic that "Why are projects
trying to avoid Barbican, still?" [0]. That is very an interesting topic. Now I
would like to make a new topic related to Rolling upgrade. I am trying to find
information about the strategy to support rollin
On Tue, Feb 28, 2017 at 3:10 AM, Zhenyu Zheng
wrote:
Matt,
Thanks for the recap, it's a pity I cannot attend PTG due to personal
reason, I will be willing to take the work you mentioned, and will
check the details with you.
And another thing, I don't know whether you guys discussed or no
> - Use [horizon-plugin] mailer tag to keep people up to date
So the idea here is to send an email for changes that are likely to affect
plugins; new libs for example, or changes to core components, with the
[horizon-plugin] tag.
> Was there much discussion around project health, and the lack o
Well, looks like you don’t have murano-api endpoint in keystone service
catalog. Have you tried adding it?
--
Kirill Zaitsev
On 28 February 2017 at 09:05:34, 渥美 慶彦 (atsumi.yoshih...@po.ntts.co.jp)
wrote:
Hi everyone,
I tried to execute "environment-deploy", but failed.
2017-02-27 15:40:21.066
Ruijing,
I'm not sure about other cases, but XenServer CI is using nested
virtualization.
Regards,
Jianghua
From: Guo, Ruijing [mailto:ruijing@intel.com]
Sent: Tuesday, February 28, 2017 4:52 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [thir
Hi, CI Team,
I'd like to know if openstack CI VM support nested virtualization.
Thanks,
-Ruijing
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
On Tue, Feb 28, 2017 at 7:54 AM, Sergey Kraynev wrote:
> Zane,
> as I understand, all related code was removed. Probably we may to remove our
> Hidden resource too.
We can't remove our hidden resources, because it breaks stacks that
reference them (to the point that you can't delete them).
> If
On 27/02/17 16:53 -0500, Emilien Macchi wrote:
Here's a summary of what was said at PTG. Feel free to comment if I
missed something.
# Container roadmap
Driver: flaper87
Summary: Goal is to support all services deployed in containers. Bring
new CI job for undercloud-container. Stabilize ovb-cont
Correction, the time is February 28 at 18:30 UTC/10:30 PT, zoom
room https://deis.zoom.us/j/668276583
My sincere apologies for the error.
> On Feb 27, 2017, at 11:45 AM, Chris Hoge wrote:
>
> We will be holding an OpenStack on Helm Workgroup meeting on Tuesday,
> February 28 at 19:30 UTC/11:30
On 28/02/17 08:01 +, Jesse Pretorius wrote:
On 2/28/17, 12:52 AM, "Michał Jastrzębski" wrote:
I think instead of adding yet-another-irc-channel how about create
weekly meetings? We can rant in scheduled time and it probably will
get more attention
Happy to meet, in fact I think it
On 27/02/17 09:56 -0700, Steven Dake wrote:
On Mon, Feb 27, 2017 at 9:36 AM, Steven Hardy wrote:
On Mon, Feb 27, 2017 at 09:25:46AM -0700, Steven Dake wrote:
>comments inline.
>On Mon, Feb 27, 2017 at 9:02 AM, Steven Hardy
wrote:
>
> Hi all,
>
> Over the recent PTG, and prev
The Architecture Working Group was lucky enough to have a room allocated
to us for all day Tuesday of the Pike PTG. We made good use of it
to do what we are here to do: Facilitate the development of a shared
architecture amongst OpenStack project teams.
We had an etherpad[1] that is a bit of a str
On 2/28/17, 12:52 AM, "Michał Jastrzębski" wrote:
I think instead of adding yet-another-irc-channel how about create
weekly meetings? We can rant in scheduled time and it probably will
get more attention
Happy to meet, in fact I think it’ll be important for keeping things on track –
Dear all,
A gentle reminder for our meeting tomorrow.
As usual, the agenda is available at:
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line
251)
Please feel free to add items.
Best,
Ad_rien_
__
76 matches
Mail list logo
