This discussion was expected when we implemented the Tempest patch,
then I sent a mail to defcore comittee[1]
As the above ml, "A DefCore Guideline typically covers three OpenStack
releases".
That means the latest guideline needs to cover Mitaka, Liberty and Kilo, right?
In the Kilo development, w
That is what I want. It is better to map the day into the release schedule in
the future. Can we make it since Otaca?
And everyone is encouraged.
Regards.
--
Shane
-Original Message-
From: Rochelle Grober [mailto:rochelle.gro...@huawei.com]
Sent: Wednesday, June 15, 2016 9:53 AM
To: Dani
Yes, sure, we encourage every company to host bug smash at its city globally,
as the company wants, but should align with us. Actually last time it followed
the model, for example, we have SUSE to host at Germany, and in the last minute
we have Taiwan.
For Hangzhou in PRC, we are also calling fo
OK, Got you, Sean, will let you know if there is any change.
Regards.
--
Shane
-Original Message-
From: Sean McGinnis [mailto:sean.mcgin...@gmx.com]
Sent: Tuesday, June 14, 2016 3:10 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Zhuangzhen; anni@huawei.com; L
I heard that from Doug, the best timing is before July 11.
Thank you for the reminder.
Regards.
--
Shane
-Original Message-
From: Daniel P. Berrange [mailto:berra...@redhat.com]
Sent: Monday, June 13, 2016 5:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Zhuan
Welcome to join us, Duncan.
Regards.
--
Shane
From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: Monday, June 13, 2016 4:14 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Zhuangzhen; anni@huawei.com; Liang, Maggie
Subject: Re: [openstack-dev] Invitation to join
Thanks everyone for your input.
I generally agree that there is something that doesn't quite feel right
about purely trusting this information to be passed from service to
service, this is why i was keen for outside input and I have been
rethinking the approach.
To this end i've proposed reservat
On Jun 14, 2016 14:42, "Doug Hellmann" wrote:
>
> Excerpts from Matthew Treinish's message of 2016-06-14 15:12:45 -0400:
> > On Tue, Jun 14, 2016 at 02:41:10PM -0400, Doug Hellmann wrote:
> > > Excerpts from Matthew Treinish's message of 2016-06-14 14:21:27 -0400:
> > > > On Tue, Jun 14, 2016 at 1
> -Original Message-
> From: GHANSHYAM MANN [mailto:ghanshyamm...@gmail.com]
> Sent: Wednesday, June 15, 2016 9:59 PM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [tempest][nova][defcore] Add option to
> disable some strict response c
Hi folks,
It's been a lng time coming, but we're almost there. I've put up a BP
outlining the steps we need to get over the line and start releasing those
looong awaited updates of our xstatic packages:
https://blueprints.launchpad.net/horizon/+spec/xstatic-release-process
I'll be workin
Thanks for the updates.
From: Aaron Rosen
Reply-To: OpenStack List
Date: Wednesday, June 15, 2016 at 10:19 PM
To: OpenStack List
Subject: Re: [openstack-dev] [Neutron] Stable/liberty breakage
Sorry I think I gave Gary some bad information here.
After digging into this more, the actually under
Hi, Matthew,
Ok, Got it, will follow the Zaqar example. Thank you pointing out that not to
reply in an existing thread.
Best Regards
Chaoyi Huang ( Joe Huang )
-Original Message-
From: Matthew Treinish [mailto:mtrein...@kortar.org]
Sent: Thursday, June 16, 2016 3:40 AM
To: OpenStack D
On 16 June 2016 at 03:33, Matt Riedemann wrote:
> On 6/13/2016 3:35 AM, Daniel P. Berrange wrote:
>
>> On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote:
>>
>>> Hi,
>>>
>>> You may or may not be aware of the vlan-aware-vms effort [1] in
>>> Neutron. If not, there is a spec and a fair
On 16 June 2016 at 00:31, Carl Baldwin wrote:
> I know I've been pretty quiet since I started this thread. Y'all have
> been doing so well, I've just been reading the thread every day and
> enjoying it. I thought I'd top post here to kind of summarize.
>
> I see wisdom in the strategy suggested
This might come across a little trolly/devils advocate, but I mulled
on it for a few days, and I think I need to send it, so... fingers
crossed you can extract some value from my questions.
On 15 June 2016 at 01:57, Thierry Carrez wrote:
> Hi everyone,
>
> I just proposed a new requirement for Op
On Wed, Jun 15, 2016 at 6:12 AM, Matthew Treinish wrote:
> On Tue, Jun 14, 2016 at 12:19:54PM -0700, Chris Hoge wrote:
>>
>> > On Jun 14, 2016, at 11:21 AM, Matthew Treinish
>> > wrote:
>> >
>> > On Tue, Jun 14, 2016 at 10:57:05AM -0700, Chris Hoge wrote:
>> >> Last year, in response to Nova mic
On 6/14/2016 8:57 AM, Thierry Carrez wrote:
Hi everyone,
I just proposed a new requirement for OpenStack "official" projects,
which I think is worth discussing beyond the governance review:
https://review.openstack.org/#/c/329448/
From an upstream perspective, I see us as being in the business
Hi all,
I would like to evaluate bgpvpn and bagpipe driver in my local
machine. I cannot find any useful deployment guide about it.
I find a github repository for it, but it seems out of date (3 months
ago). I'd appreciate it if someone can provide a working devstack
configuration for multiple no
On 6/13/2016 3:35 AM, Daniel P. Berrange wrote:
On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote:
Hi,
You may or may not be aware of the vlan-aware-vms effort [1] in
Neutron. If not, there is a spec and a fair number of patches in
progress for this. Essentially, the goal is to all
Tackers,
It gives me great pleasure to propose Kanagaraj Manickam to join the Tacker
core team. In a short time, Kanagaraj has grown into a key member of the
Tacker team. His enthusiasm and dedication to get Tacker code base on par
with other leading OpenStack projects is very much appreciated. He
Very exciting development indeed!
From: "SULLIVAN, BRYAN L"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, June 14, 2016 at 8:58 PM
To: "OpenStack Development Mailing List (not for usage questions)"
Cc: "opnfv-tech-disc...@lists.opnfv.org"
Subject:
Big +1 for that which makes pre-provisioned cred testing more thoroughly.
And at the end we should divide the existing jobs among dynamic and
pre-provisioned account so that we would not leave any of them less tested.
Thanks
gmann
From: Andrea Frittoli [mailto:andrea.fritt...@gmail.com]
Sent: 15
QEMU has the ability to directly connect to iSCSI volumes. Running the
iSCSI connections through the nova-compute host *seems* somewhat
inefficient.
There is a spec/blueprint and implementation that landed in Kilo:
https://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/qemu-built
Join us Thursday for our weekly meeting, scheduled for June 16th at
17:00UTC in #openstack-meeting-3
The agenda can be found here, and please add to if you want to discuss
something with the Community App Catalog team:
https://wiki.openstack.org/wiki/Meetings/app-catalog
In addition to status upd
On Wed, Jun 15, 2016 at 09:10:30AM -0400, Doug Hellmann wrote:
> Excerpts from Chris Hoge's message of 2016-06-14 16:37:06 -0700:
> > Top posting one note and direct comments inline, I’m proposing
> > this as a member of the DefCore working group, but this
> > proposal itself has not been accepted
Ryan,
In-line
Regards
John
From: Ryan Moats mailto:rmo...@us.ibm.com>>
Date: Tuesday, June 14, 2016 at 9:42 PM
To: John McDowall
mailto:jmcdow...@paloaltonetworks.com>>
Cc: Na Zhu mailto:na...@cn.ibm.com>>, Srilatha Tangirala
mailto:srila...@us.ibm.com>>, "OpenStack Development
Mailing List
I know I've been pretty quiet since I started this thread. Y'all have
been doing so well, I've just been reading the thread every day and
enjoying it. I thought I'd top post here to kind of summarize.
I see wisdom in the strategy suggested by Sean Mooney to make a very
minimal change to os-vif t
On 6/15/2016 3:10 PM, Paul Michali wrote:
Is the plan to back port that change to Mitaka?
Thanks,
PCM
On Wed, Jun 15, 2016 at 1:31 PM Matt Riedemann
mailto:mrie...@linux.vnet.ibm.com>> wrote:
On 6/14/2016 3:09 PM, Jay Pipes wrote:
>
> Yes. Code merged recently from Sahid does thi
>I wouldn't say linux bridges are totally outside of its domain because it
relies on them for security groups.
It relies on a side effect of their existence - iptables rules being
applied to the veth interface. It does nothing to the actual linux bridge
itself. If there was a way to plug a veth di
On Wed, Jun 15, 2016 at 07:01:17PM +0200, Jordan Pittier wrote:
> On Wed, Jun 15, 2016 at 6:21 PM, Matt Riedemann
> wrote:
>
...
> > Does someone have a link to a successful job run for one of those drivers?
> > I'd like to see if they are testing volume snapshot and that it's properly
> > callin
Hey all,
The weekly ironic meeting for June 20 will be cancelled because it
overlaps with our midcycle. Join the midcycle instead. :)
We'll resume our normal schedule on June 27.
// jim
__
OpenStack Development Mailing List
Hi all,
Just a reminder that our midcycle is next week!
Details are here:
https://wiki.openstack.org/wiki/VirtualSprints#Ironic_Virtual_Newton_Midcycle
https://wiki.openstack.org/wiki/Sprints#Future_sprints_for_Newton
Etherpad: https://etherpad.openstack.org/p/ironic-newton-midcycle
Please add
On Wednesday, June 15, 2016 12:45 PM, Mooney, Sean K [sean.k.moo...@intel.com]
wrote:
> > On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub)
> > wrote:
> > > >which generates an arbitrary name
> > >
> > > I'm not a fan of this approach because it requires coordinated
> > assumption
Is the plan to back port that change to Mitaka?
Thanks,
PCM
On Wed, Jun 15, 2016 at 1:31 PM Matt Riedemann
wrote:
> On 6/14/2016 3:09 PM, Jay Pipes wrote:
> >
> > Yes. Code merged recently from Sahid does this:
> >
> > https://review.openstack.org/#/c/277422/
> >
> > Best,
> > -jay
> >
>
> Th
> On 15 Jun 2016, at 22:06, Ihar Hrachyshka wrote:
>
>
>> On 15 Jun 2016, at 21:19, Aaron Rosen wrote:
>>
>> Sorry I think I gave Gary some bad information here.
>>
>> After digging into this more, the actually underlying issue that we hit is
>> that the packaged 'distro' version of stable
> On 15 Jun 2016, at 21:19, Aaron Rosen wrote:
>
> Sorry I think I gave Gary some bad information here.
>
> After digging into this more, the actually underlying issue that we hit is
> that the packaged 'distro' version of stable/liberty that was running with
> the vmware-nsx repo included t
I'll be away next week attending OPNFV Summit. Hence cancelling Tacker irc
meeting on Jun 21st. We will resume the week after - on Tuesday Jun 28th,
https://wiki.openstack.org/wiki/Meetings/Tacker
- Sridhar
__
OpenStack Devel
Just a note, please don't start a new thread as a reply to an existing thread.
(well unless you remove the In-Reply-To header from the message) There is more
details on this here:
https://wiki.openstack.org/wiki/MailingListEtiquette#Threading
I almost missed this because it was part of a differen
Sorry I think I gave Gary some bad information here.
After digging into this more, the actually underlying issue that we hit is
that the packaged 'distro' version of stable/liberty that was running with
the vmware-nsx repo included this patch set which is not in upstream
stable/liberty
https://gi
On Wed, Jun 15, 2016 at 2:59 PM, Ihar Hrachyshka wrote:
>
>> On 15 Jun 2016, at 20:18, Gary Kotton wrote:
>>
>> Hi,
>> The following patch breaks stable liberty drivers -
>> https://review.openstack.org/#/c/238745/
>> This means that plugins will need to be updated to support this.
>
> Would you
> On 15 Jun 2016, at 20:18, Gary Kotton wrote:
>
> Hi,
> The following patch breaks stable liberty drivers -
> https://review.openstack.org/#/c/238745/
> This means that plugins will need to be updated to support this.
Would you mind sharing details about the breakage? It was assumed that the
> -Original Message-
> From: Peters, Rawlin [mailto:rawlin.pet...@hpe.com]
> Sent: Wednesday, June 15, 2016 7:02 PM
> To: Kevin Benton
> Cc: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability
> for wir
On Wed, Jun 15, 2016 at 2:01 PM, Peters, Rawlin wrote:
> On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub) wrote:
>> >which generates an arbitrary name
>>
>> I'm not a fan of this approach because it requires coordinated assumptions.
>> With the OVS hybrid plug strategy we have to
Hi,
The following patch breaks stable liberty drivers -
https://review.openstack.org/#/c/238745/
This means that plugins will need to be updated to support this.
What do we do:
1. Revert – which could break people using latest stable/liberty
2. Have a requirement that Neutron plugins be upd
On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub) wrote:
> >which generates an arbitrary name
>
> I'm not a fan of this approach because it requires coordinated assumptions.
> With the OVS hybrid plug strategy we have to make guesses on the agent side
> about the presence of bridge
On 6/15/2016 5:17 AM, Evgeny Antyshev wrote:
Hello, Matt!
First of all, I want to apologize for the inconvenience.
This all started yesterday when I updated Virtuozzo CI using latest
puppets, Zuul, Jenkins and other stuff.
The update somehow led to Zuul not passing environment variables like
ZUU
On 2016-06-15 13:17:54 +0300 (+0300), Evgeny Antyshev wrote:
[...]
> This all started yesterday when I updated Virtuozzo CI using latest puppets,
> Zuul, Jenkins and other stuff.
> The update somehow led to Zuul not passing environment variables like
> ZUUL_CHANGE, LOG_PATH to Jenkins job.
[...]
V
On 6/14/2016 3:09 PM, Jay Pipes wrote:
Yes. Code merged recently from Sahid does this:
https://review.openstack.org/#/c/277422/
Best,
-jay
That was actually reverted out of mitaka:
https://review.openstack.org/#/c/292290/
The feature change that got into newton was this:
https://review.o
Excerpts from Kyle Mestery's message of 2016-06-15 09:05:59 -0500:
> On Tue, Jun 14, 2016 at 9:15 AM, Doug Hellmann wrote:
> > Excerpts from Thierry Carrez's message of 2016-06-14 15:57:10 +0200:
> >> Hi everyone,
> >>
> >> I just proposed a new requirement for OpenStack "official" projects,
> >>
There have been a number of bug fixes to the NUMA code in both Mitaka
and Newton. I think you would need to be very careful in your backporting :)
-jay
On 06/15/2016 09:55 AM, Paul Michali wrote:
Yeah, was thinking more of technically vs policy. Wondering if there are
other dependencies or if
On Wed, Jun 15, 2016 at 6:21 PM, Matt Riedemann
wrote:
> In the nova-api meeting today we were talking about the nova
> os-assisted-volume-snapshots API and whether or not it was a proxy API to
> cinder. We determined it's not, it performs an action on a server resource.
> But what a few of us di
Yeah, was thinking more of technically vs policy. Wondering if there are
other dependencies or if I could patch this into a Liberty code base.
On Wed, Jun 15, 2016 at 12:38 PM Jay Pipes wrote:
> On 06/15/2016 03:58 AM, Paul Michali wrote:
> > Awesome Jay!
> >
> > Do you think this is something
+1
Finally!
On Wed, Jun 15, 2016 at 3:33 AM, Ihor Dvoretskyi
wrote:
> +1 for Alexander Tivelkov.
>
> Good effort.
>
> On Wed, Jun 15, 2016 at 1:08 PM, Artem Silenkov
> wrote:
>
>> Hello!
>>
>> +1
>>
>> Regards,
>> Artem Silenkov
>> ---
>> paas-team
>>
>> On Wed, Jun 15, 2016 at 12:56 PM, Dmytr
On 06/15/2016 03:58 AM, Paul Michali wrote:
Awesome Jay!
Do you think this is something that can be backporting to Liberty w/o
other dependencies? We're running Liberty on our system right now.
Doubtful, Paul :( The policy for upstream is not to backport feature
patches. This would be somethi
Amrith Kumar wrote:
Thanks for writing this up and for the interesting discussion that has come up
in this ML thread.
While I think I get the general idea of the motivation, I think the verbiage
doesn't quite do justice to your intent.
One area which I would like to highlight is the situation
In the nova-api meeting today we were talking about the nova
os-assisted-volume-snapshots API and whether or not it was a proxy API
to cinder. We determined it's not, it performs an action on a server
resource. But what a few of us didn't realize was it's an admin API in
nova only for cinder Re
First, some context: we talked it thru with Eugene on IRC, and Eugene reported
that he cannot reproduce the issue on his setup using Ubuntu hypervisor with
ovs 2.4:
http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2016-06-13.log.html#t2016-06-13T19:45:22
So I wen
For most of the mid cycles we've set up some video conferencing for remote
people to participate. I'll add a new section in the etherpad for remote
people so we can set up all that information in one location.
-Trevor
From: Nir Magnezi
Sent: Wednesday, June
Thierry,
Thanks for writing this up and for the interesting discussion that has come up
in this ML thread.
While I think I get the general idea of the motivation, I think the verbiage
doesn't quite do justice to your intent.
One area which I would like to highlight is the situation with the un
-Original Message-
From: gordon chung
Reply: gordon chung
Date: June 14, 2016 at 21:14:17
To: Ian Cordasco , OpenStack Development Mailing List
(not for usage questions)
Subject: Re: [openstack-dev] [ceilometer] [stable] Re:
[Openstack-stable-maint] Stable check of openstack/ceilom
Hey folks,
For a while now we've been working on virt device role tagging.
The full spec is here [1], but the quick gist of it is that device
tagging is a way for the user to assign arbitrary string tags to
either vNICs or block devices. Those tags then get exposed by the
metadata API to the gues
On Tue, Jun 14, 2016 at 9:15 AM, Doug Hellmann wrote:
> Excerpts from Thierry Carrez's message of 2016-06-14 15:57:10 +0200:
>> Hi everyone,
>>
>> I just proposed a new requirement for OpenStack "official" projects,
>> which I think is worth discussing beyond the governance review:
>>
>> https://r
> On Jun 15, 2016, at 8:01 AM, Sean Dague wrote:
>
> On 06/15/2016 12:14 AM, Mark Voelker wrote:
>
>>
>> It is perhaps important to note here that the DefCore seems to have two
>> meanings to a lot of people I talk to today: it’s a mark of interoperability
>> (the OpenStack Powered badge tha
Excerpts from mohammad shahid's message of 2016-06-15 16:32:10 +0530:
> Hi,
>
> Can someone look at this networking-onos 2.0.0 not on our pypi please ?
>
> reference links:
> https://launchpad.net/networking-onos
> https://pypi.python.org/pypi/networking-onos
>
>
> Thanks and Regards,
> Mohamma
Excerpts from Chris Hoge's message of 2016-06-14 16:37:06 -0700:
> Top posting one note and direct comments inline, I’m proposing
> this as a member of the DefCore working group, but this
> proposal itself has not been accepted as the forward course of
> action by the working group. These are my ow
You can define several backends with the same volume_backend_name and call
that a group. For example:
[groupA-be1]
volume_backend_name=fast-ssd
[groupA-be2]
volume_backend_name=fast-ssd
[groupB-be3]
volume_backend_name=slow-disk
So, no matter what storage is behind every backend, it will be filt
Hi John,
I update the networking-sfc and networking-ovn for the new schema.
I think the most important now is nail down the ovsdb schema for SFC, as
you know, it is not hard to implement networking-sfc and networking-ovn,
but if the schema changes, we have to update networking-sfc and
networki
Neil,
On Wed, Jun 15, 2016 at 3:17 AM, Neil Jerram wrote:
> On Wed, Jun 15, 2016 at 9:52 AM Thierry Carrez
> wrote:
>>
>> [...]
>> Those are good points. Note that I do not advocate for those projects to
>> be kept closed/private: I'm simply saying that those (open source)
>> projects should not
On 06/15/2016 12:14 AM, Mark Voelker wrote:
>
> It is perhaps important to note here that the DefCore seems to have two
> meanings to a lot of people I talk to today: it’s a mark of interoperability
> (the OpenStack Powered badge that says certain capabilities of this cloud
> behave like other
Hi,
Can someone look at this networking-onos 2.0.0 not on our pypi please ?
reference links:
https://launchpad.net/networking-onos
https://pypi.python.org/pypi/networking-onos
Thanks and Regards,
Mohammad Shahid
__
OpenStac
Awesome Jay!
Do you think this is something that can be backporting to Liberty w/o other
dependencies? We're running Liberty on our system right now.
On Tue, Jun 14, 2016 at 4:10 PM Jay Pipes wrote:
> On 06/14/2016 12:30 PM, Paul Michali wrote:
> > Well, looks like we figured out what is going
Hi Michael,
Will there be an option to participate from remote?
Thanks,
Nir
On Fri, Jun 10, 2016 at 1:51 AM, Michael Johnson
wrote:
> Just a reminder, we have a proposed mid-cycle meeting set for the week
> of August 22nd in San Antonio.
>
> If you would like to attend and have not yet signed
+1 for Alexander Tivelkov.
Good effort.
On Wed, Jun 15, 2016 at 1:08 PM, Artem Silenkov
wrote:
> Hello!
>
> +1
>
> Regards,
> Artem Silenkov
> ---
> paas-team
>
> On Wed, Jun 15, 2016 at 12:56 PM, Dmytro Dovbii
> wrote:
>
>> +1
>> 15 июня 2016 г. 6:47 пользователь "Yang, Lin A"
>> написал:
>>
Hi David,
I agree with this completely. Gates continue to be a problem for Kolla,
reasons why have been discussed in the past but at least for me it's not
clear what the key issues are.
I've added this item to agenda for todays IRC meeting (16:00 UTC -
https://wiki.openstack.org/wiki/Meeting
Hello, Matt!
First of all, I want to apologize for the inconvenience.
This all started yesterday when I updated Virtuozzo CI using latest
puppets, Zuul, Jenkins and other stuff.
The update somehow led to Zuul not passing environment variables like
ZUUL_CHANGE, LOG_PATH to Jenkins job.
Therefore
On Wed, Jun 15, 2016 at 9:52 AM Thierry Carrez
wrote:
> [...]
> Those are good points. Note that I do not advocate for those projects to
> be kept closed/private: I'm simply saying that those (open source)
> projects should not be blessed as "official" and be put under the
> Technical Committee o
Hello!
+1
Regards,
Artem Silenkov
---
paas-team
On Wed, Jun 15, 2016 at 12:56 PM, Dmytro Dovbii
wrote:
> +1
> 15 июня 2016 г. 6:47 пользователь "Yang, Lin A"
> написал:
>
> +1 both for Alexander Tivelkov and Zhu Rong. Well deserved.
>>
>> Regards,
>> Lin Yang
>>
>> On Jun 15, 2016, at 3:17 AM
+1
15 июня 2016 г. 6:47 пользователь "Yang, Lin A"
написал:
> +1 both for Alexander Tivelkov and Zhu Rong. Well deserved.
>
> Regards,
> Lin Yang
>
> On Jun 15, 2016, at 3:17 AM, Kirill Zaitsev wrote:
>
> Hello team, I want to annonce the following changes to murano core team:
>
> 1) I’d like to
Hello:
Context: try to develop a driver for this feature in OVS.
During the last week I’ve been testing several scenarios to make a POC of this
feature.
Scenario 1:
3 VM connected to br-int, sending traffic through br-physical to other host (an
external physical machine).
The first VM will hav
15.06.2016 0:51, Matt Riedemann пишет:
It was pointed out today in IRC that the Virtuozzo CI has been failing
on this change for the libvirt imagebackend refactor:
https://review.openstack.org/#/c/282580/
Diana was having a hard time sorting out the line numbers in the stack
trace though fro
Sean Dague wrote:
On 06/14/2016 07:28 PM, Monty Taylor wrote:
On 06/14/2016 05:42 PM, Doug Hellmann wrote:
I think this is the most important thing to me as it relates to this.
I'm obviously a huge proponent of clouds behaving more samely. But I
also think that, as Doug nicely describes above
Doug Hellmann wrote:
From our perspective, we (designate) currently have a few drivers from
proprietary vendors, and would like to add one in the near future.
The current drivers are marked as "release compatible" - aka someone is
nominated to test the driver throughout the release cycle, and th
On Wed, Jun 15, 2016 at 2:00 AM, Andrea Frittoli
wrote:
> Dear all,
>
> TL;DR: I'd like to propose to start running some of the existing dsvm
> check/gate jobs using Tempest pre-provisioned credentials.
>
> Full Text:
> Tempest provides tests with two mechanisms to acquire test credentials
> [0]:
Fox, Kevin M wrote:
Some counter arguments for keeping them in:
* It gives the developers of the code that's being plugged into a better view
of how the plugin api is used and what might break if they change it.
* Vendors don't tend to support drivers forever. Often they drop support for a d
Hi Hongbin.
Thanks for considering it, maybe it works next time the offer stays :)
Cheers,
Ricardo
On Tue, Jun 14, 2016 at 10:26 PM, Hongbin Lu wrote:
> Hi Tim,
>
>
>
> Thanks for providing the host. We discussed the midcycle location at the
> last team meeting. It looks a significant number of
Hi,
IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every
Wednesday starting from UTC 13:00.
Today's agenda:
# spec review and status of 'cross pod L2 networking' and 'dynamic pod binding'
# integration test in the CI pipeline
# policy enforcement for API access
If you
Hi,
Vitrage weekly meeting on June 22 will be skipped due to OPNFV summit.
We will meet again on June 29.
Thanks,
Ifat.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
Hi peers,
Welcome Thai!!
I have closed this vote window, five days since the proposal posted onto ML,
according to following guide.
https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess
This proposal have been approved from majority of the active Core Developers
without rejection
On 15/06/16 09:20, Matthias Runge wrote:
> On 15/06/16 08:14, A mailing list for the OpenStack Stable Branch test
> reports. wrote:
>> Build failed.
>>
>> - periodic-horizon-docs-liberty
>> http://logs.openstack.org/periodic-stable/periodic-horizon-docs-liberty/b029b21/
>> : SUCCESS in 7m 13s
>>
Dear Shinobu,
I have revised the description of dynamic pod binding and submitted a new
patch. Here is the link of the path:
https://review.openstack.org/#/c/306224/12. Is the description clear enough
to help readers understand the patch. Could you please go through the
description and give me som
90 matches
Mail list logo
