Hi folks,
due to OpenStack Summit I'm canceling the next Tue May 9th upstream meeting.
Cheers,
Jakub
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On 5/8/2017 1:24 PM, Octave J. Orgeron wrote:
Now for Oracle, we definitely need more 3rd party CI to make it easier
to test our drivers, components, and patches against so that it's easier
for the community to validate things. However, it takes time, resources,
and money to make that happen.
On 5/8/2017 1:10 PM, Octave J. Orgeron wrote:
I do agree that scalability and high-availability are definitely issues
for OpenStack when you dig deeper into the sub-components. There is a
lot of re-inventing of the wheel when you look at how distributed
services are implemented inside of
Please disregard that last email! Typing in the wrong window fail. I will
let you all know details about more sticker pickup soon!
-Kendall Nelson
On Mon, May 8, 2017 at 6:54 PM Kendall Nelson wrote:
> Hello PTLs!
>
> If you didn't get your stickers today, they will
Hello PTLs!
If you didn't get your stickers today, they will still be available in the
foundation staff loungejung
On Mon, May 8, 2017 at 1:12 PM Kendall Nelson wrote:
> Hello PTLs!
>
> The first pickup time will be from 2 to 4 pm today in the Foundation
> Lounge Hynes
All,
networking-sfc meetings will resume on May 18.
- Louis
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
Dear Neutrinos,
I am working with Legal Sea Foods on a reservation for 30 people, Wednesday
at 7pm. I am assuming the 30 people who registered in the etherpad will
attend (https://etherpad.openstack.org/p/neutron-boston-summit-attendees).
If your name is in the etherpad and you DON'T plan to
Excerpts from Jeremy Stanley's message of 2017-05-08 20:18:35 +:
> On 2017-05-08 11:24:00 -0600 (-0600), Octave J. Orgeron wrote:
> [...]
> > none of those products that those drivers are written for are open
> > sourced and they meet less resistance to committing code upstream.
> > So I have
Hello Everyone,
If you are interested in hearing how the Upstream Institute training went
this last weekend come join us! We will be discussing what we though went
well, what we need to work on for next time, next steps etc.
There is a reserved hacking room slot in Hynes MR111 from 3-3:50 on
Instead of a meeting, come to our talk about the migration to StoryBoard[1]!
There will be no meeting at 19:00 UTC on Wednesday May 10th. If you have
any questions or anything pressing, we will be around in the #storyboard
channel. The next meeting will be Wednesday May 17th.
-Kendall Nelson
Hi,
As there has not been produced any activity related to freezer project from Tim
and Deklan during the last year +1 for removing them from core list from my
side.
Regards,
Vitaliy
> 9 мая 2017 г., в 00:03, Saad Zaher написал(а):
>
> Hello everyone,
>
> I would like
Hello everyone,
I would like to propose some core member updates to the Freezer core team.
I would like to remove the following users from core as they became
inactive members now
- Tim Buckley
- Deklan Dieterly
Please, If you agree to these changes vote +1 otherwise explain your
Hello Everyone,
As most of the people are in the summit we're not going to have a freezer
meeting this week. Freezer meetings will be continued next week on the
usual time slot (Thursday @ 2 O'clock GMT) in #openstack-meeting-alt
--
Best Regards,
Saad!
On 2017-05-08 11:24:00 -0600 (-0600), Octave J. Orgeron wrote:
[...]
> none of those products that those drivers are written for are open
> sourced and they meet less resistance to committing code upstream.
> So I have to call BS on your comment that the community can't work
> with us because
Hello folks,
We are all in Boston this week. So we will cancel the IRC meeting this week May
10 and will re-convene next week May 17.
Thanks
Bin
[1] https://wiki.openstack.org/wiki/Gluon
[2] https://wiki.openstack.org/wiki/Meetings/Gluon
Hello!
If you are running a project onboarding session and have etherpads/slides/
etc you are using to educate new contributors please send them to me! I am
collecting all the resources you are sharing into a single place for people
that weren't able to attend sessions.
Thanks!
Kendall
+1, some great contributions!
Thanks
On 8 May 2017 at 19:11, Kwasniewska, Alicja
wrote:
> +1 Congrats☺
>
> Regards,
> Alicja Kwasniewska
>
>
>
> *From: *"Vikram Hosakote (vhosakot)"
> *Reply-To: *"OpenStack Development Mailing List (not for
Dear Edgar,
As indicated into the WG chairs' session pad [1], the WG was previously
entitled ``Massively Distributed Cloud''.
The description appears on the WG wiki page [2] (and I sent an email to the
user ML a few months ago to ask for the official creation [3]).
After exchanging with the
+1 Congrats☺
Regards,
Alicja Kwasniewska
From: "Vikram Hosakote (vhosakot)"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Monday, May 8, 2017 at 6:54 AM
To: "OpenStack Development Mailing List (not for
Thank you for information !
So, you mean the situation is not changed from the reference thread[1]
in qemu-devel ML 3 years ago, and the difficulties of ivshmem you
mentioned is described in this thread. Am I right?
[1] "[Qemu-devel] Why I advise against using ivshmem"
Hi Jeremy,
I'm sure everyone would love to see Solaris open sourced again. I know I
do! But unfortunately, it's not something within my power or control.
However, there is the reality that OpenStack wouldn't be as successful
without commercial companies contributing to it. A good example is
Hello PTLs!
The first pickup time will be from 2 to 4 pm today in the Foundation Lounge
Hynes 2nd Floor outside 206 from Ildiko Vancsa.
>From there you are free to distribute them as you like :)
-Kendall Nelson
__
OpenStack
Hi Kevin,
I agree that OpenStack may need to re-architect and rethink certain
design choices. That eventually has to happen to any open source or
commercial product where it becomes to bloated and complex. k8s is a
good example of something that has grown rapidly and is simple at this
point.
.
2017-05-04 12:08 GMT+08:00 Rico Lin :
> Hi all,
>
> Boston Summit is near, and we need your help and feedback! We really hope
> to improve your orchestration experiences,
> so *if you're a User, Operator, or Developer,* please join us on
> *`Large Orchestration
Hello,
In behalf of the User Community I would like to understand if this is
considering officially to request to create the Working Group. I could have
missed another email request the inclusion but if not, I would like to discuss
the goals and objective from the WG. The User Committee will
Hello team,
I'm trying to get an idea about how many of us (QA) will be (or intend to
be) at the PTG in Denver.
Could you reply to me only or ping in IRC and let me know?
Thanks
andrea
__
OpenStack Development Mailing List
On 08.05.2017 16:06, Doug Hellmann wrote:
>>>
>>> option #3: Do not support or nurse gates for stable branches upstream.
>>> Instead, only create and close them and attach 3rd party gating, if
>>> asked by contributors willing to support LTS and nurse their gates.
>>> Note, closing a branch should
Excerpts from Davanum Srinivas (dims)'s message of 2017-05-08 06:12:51 -0400:
> On Mon, May 8, 2017 at 3:52 AM, Bogdan Dobrelya wrote:
> > On 06.05.2017 23:06, Doug Hellmann wrote:
> >> Excerpts from Thierry Carrez's message of 2017-05-04 16:14:07 +0200:
> >>> Chris Dent
On Fri, Apr 28, 2017 at 09:38:38AM +0100, sfinu...@redhat.com wrote:
> On Fri, 2017-04-28 at 13:23 +0900, TETSURO NAKAMURA wrote:
> > Hi Nova team,
> >
> > I'm writing this e-mail because I'd like to have a discussion about
> > DPDK support at OpenStack Summit in Boston.
> >
> > We have
Let's plan for a social Wednesday night. I'll update this with a location
once we find a place.
On May 8, 2017 08:50, "MCCASLAND, TREVOR" wrote:
> Looking forward to it! RSVP? +1
>
>
>
> *From:* Sukhdev Kapur [mailto:sukhdevka...@gmail.com]
> *Sent:* Saturday, May 06, 2017 12:31
Looking forward to it! RSVP? +1
From: Sukhdev Kapur [mailto:sukhdevka...@gmail.com]
Sent: Saturday, May 06, 2017 12:31 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] - are you attending the Boston
Thank you for reply!
On 2017/04/28 4:38, sfinu...@redhat.com wrote:
On Fri, 2017-04-28 at 13:23 +0900, TETSURO NAKAMURA wrote:
Hi Nova team,
I'm writing this e-mail because I'd like to have a discussion about
DPDK support at OpenStack Summit in Boston.
We have developed a dpdk-based patch
Hi folks, after some discussion locally with colleagues about improving the
upgrades experience, one of the items that came up was pre-upgrade and
update validations. I took an AI to look at the current status of
tripleo-validations [0] and posted a simple WIP [1] intended to be run
before an
+1 Great job Bertrand!
Regards,
Vikram Hosakote
IRC: vhosakot
From: Michał Jastrzębski >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date:
Hi,
Here is the status update / focus setting mail about notification work
for week 19.
Bugs
[Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance
notifications are sent with inconsistent timestamp format. The solution
still needs time and effort from the subteam
On Mon, May 8, 2017 at 3:52 AM, Bogdan Dobrelya wrote:
> On 06.05.2017 23:06, Doug Hellmann wrote:
>> Excerpts from Thierry Carrez's message of 2017-05-04 16:14:07 +0200:
>>> Chris Dent wrote:
On Wed, 3 May 2017, Drew Fisher wrote:
> "Most large customers move slowly
Hello everyone,
We’ll not have an openstack-ansible bug triage this week, as many of our
contributors are on the summit!
See you next week!
Best regards,
Jean-Philippe Evrard
(@)evrardjp
Rackspace Limited is a company registered in England & Wales (company
Hi Julie,
I generated one example javascript file containing the translatable
strings.
URL: https://pwu.fedorapeople.org/openstack-i18n/tripleo/tripleo-heat
-templates.js
And the code to generate the above file is in:
https://pwu.fedorapeople.org/openstack-i18n/tripleo/
The generated
On Mon, May 8, 2017 at 2:48 AM, Michael Still wrote:
> It would be interesting for this to be built in a way where other
> endpoints could be added to the list that have extra headers added to them.
>
> For example, we could end up with something quite similar to EC2 IAMS if
>
On 06.05.2017 23:06, Doug Hellmann wrote:
> Excerpts from Thierry Carrez's message of 2017-05-04 16:14:07 +0200:
>> Chris Dent wrote:
>>> On Wed, 3 May 2017, Drew Fisher wrote:
"Most large customers move slowly and thus are running older versions,
which are EOL upstream sometimes before
40 matches
Mail list logo