+1
2017/02/18 4:21 "Kevin Benton" :
Hi all,
I'm organizing a Neutron social event for Thursday evening in Atlanta
somewhere near the venue for dinner/drinks. If you're interested, please
reply to this email with a "+1" so I can get a general count for a
reservation.
Cheers,
Reflash
2017年2月17日 下午3:37,"Rico Lin" 寫道:
> Hi guys
>
> As usual, we will have a team dinner (and beer session) during PTG.
> Feel free to join us!
> And please vote for any preferred schedule here:
> https://framadate.org/DiYtBWG2VqTRxMs5
>
> We will find some place
Jeremy,
Completely makes sense. I believe the prior experience the foundation has had
with remote participation probably won’t be much improved at the Pike PTG as
there is no dedicated production staff and I’m not sure what type of
teleconference hardware Michal is bringing to the PTG. Not
+1
On 19 February 2017 at 00:32, Miguel Lavalle wrote:
> +1
>
> On Sat, Feb 18, 2017 at 11:44 AM, Korzeniewski, Artur
> wrote:
>>
>> +1
>>
>>
>>
>> From: Kevin Benton [mailto:ke...@benton.pub]
>> Sent: Friday, February 17, 2017 8:19 PM
>> To:
On 2017-02-18 15:46:19 + (+), Steven Dake (stdake) wrote:
[...]
> In the past the foundation has been wary of enabling remote
> participation.
[...]
Only wary because of prior experience: Cisco donated Webex service
and dedicated remote production staff for us throughout the Havana
design
On 02/18/2017 05:14 PM, Andrew Bogott wrote:
> Does this
> announcement mean that the Mirantis apt servers (e.g.
> mitaka-jessie.pkgs.mirantis.com) will also be discontinued
Correct, I've been told the server would be decommitionned. In fact, I'm
surprised it is still up-and-running. I've
On 02/18/2017 07:59 AM, Clint Byrum wrote:
> Indeed, DPMT uses all the worst choices for maintaining most of the
> python module packages in Debian. However, something will need to be
> done to spread the load of maintaining the essential libraries, and the
> usual answer to that for Python
+1
On Sat, Feb 18, 2017 at 11:44 AM, Korzeniewski, Artur <
artur.korzeniew...@intel.com> wrote:
> +1
>
>
>
> *From:* Kevin Benton [mailto:ke...@benton.pub]
> *Sent:* Friday, February 17, 2017 8:19 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [neutron] - Neutron team
Hi everyone,
I am Freezer PTL and I will be available in the PTG in Atlanta next week.
We are not having any scheduled sessions for Freezer but I will be around
if anyone wants to ask questions about Freezer.
See you in Atlanta :)
Best Regards,
Saad!
Brandon,
Happy to help where I can. I can’t be everywhere sadly.
Regards
-steve
From: "Brandon B. Jozsa"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Saturday, February 18, 2017 at 9:32 AM
To:
Hi All,
Here is a rough outline of the order in which I want to cover the items:
https://etherpad.openstack.org/p/neutron-ptg-pike-final
I've also put together a calendar that has the meeting times as well as a
few relevant cross project sessions and our team dinner/photo.
I suggest watching
Hi,
I apologize but I had to move the Neutron/Ironic session to Monday at
2:30-3:30PM instead of Tuesday. That time conflicted with a
networking-guide session that I want to encourage people to attend.
Cheers,
Kevin Benton
On Fri, Feb 17, 2017 at 3:16 AM, Kevin Benton wrote:
I really appreciate this Steve:) No, I haven't setup the zoom.us yet, so
let's stick to your webex to avoid confusion.
See you all in ATL!
On 17 February 2017 at 23:17, Steven Dake (stdake) wrote:
> Hey folks,
>
>
>
> To take some load off Michal I’ve setup remote
- Original Message -
> From: "Artom Lifshitz"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Saturday, February 18, 2017 8:11:10 AM
> Subject: Re: [openstack-dev] [nova] Device tagging: rebuild
> On Feb 18, 2017, at 12:54, Dmitry Tantsur wrote:
>
>
> 2017-02-17 19:16 GMT+01:00 Clint Byrum :
>> Hello, I'm looking forward to seeing many of you next week in Atlanta.
>> We're going to be working on Arch-WG topics all day Tuesday, and if
>> you'd
A few good points were made:
* the config drive could be VFAT, in which case we can't trust what's
on it because the guest has write access
* if the config drive is ISO9660, we can't selectively write to it, we
need to regenerate the whole thing - but in this case it's actually
safe to read from
I haven't fully dug into testing this, but I got wondering about this
question from reviewing a change [1] which would make the unshelve
operation start to check the volume AZ compared to the instance AZ when
the compute manager calls _prep_block_device.
That change is attempting to remove
2017-02-17 19:16 GMT+01:00 Clint Byrum :
> Hello, I'm looking forward to seeing many of you next week in Atlanta.
> We're going to be working on Arch-WG topics all day Tuesday, and if
> you'd like to join us for that in general, please add your topic here:
>
>
+1
From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Friday, February 17, 2017 8:19 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday
Hi all,
I'm organizing a Neutron social event for Thursday evening in Atlanta somewhere
On Sat, Feb 18, 2017 at 10:23 AM, Clint Byrum wrote:
> But I believe Michael is not saying "it's unsafe to read the json
> files" but rather "it's unsafe to read the whole config drive". It's
> an ISO filesystem, so you can't write to it. You have to read the whole
> contents
On 2/17/2017 5:52 PM, Augustina Ragwitz wrote:
As I announced in our last bug team meeting, I will be stepping down
from the Bug Coordinator role. Since taking on the Bug Team Coordinator
role I was laid off from my position where I was able to focus on
upstream Openstack 100% of the time. I've
From: Steven Dake (stdake)
Sent: Saturday, February 18, 2017 10:46 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation
Brandon,
It is really up to
Excerpts from Artom Lifshitz's message of 2017-02-18 08:11:10 -0500:
> In reply to Clint:
>
> > Agreed. What if we simply have a second config drive that is for "things
> > that change" and only rebuild that one on reboot?
>
> We've already set the precedent that there's a single config drive
>
On 2/15/17 8:22 PM, gustavo panizzo wrote:
On Wed, Feb 15, 2017 at 01:42:51PM +0100, Thomas Goirand wrote:
Hi there,
Its really sad news, for both You and OpenStack & Debian.
Thank you for your work, Thomas -- I hope you are able to continue it.
I'm slow on the uptake here, for which I
Excerpts from Dean Troyer's message of 2017-02-18 08:21:29 -0600:
> On Sat, Feb 18, 2017 at 7:11 AM, Artom Lifshitz wrote:
> > In reply to Michael:
> > I hadn't even thought of the security implication. That's a very good
> > point, there's no way to persist admin_pass in
Brandon,
It is really up to the individual projects to enable remote participation. The
foundation greenlit Kolla’s Monday and Tuesday design sessions enabling remote
participation if the Kolla project did the legwork on providing the remote
participation mechanism. In the past the
On Sat, Feb 18, 2017 at 7:11 AM, Artom Lifshitz wrote:
> In reply to Michael:
> I hadn't even thought of the security implication. That's a very good
> point, there's no way to persist admin_pass in securely. We'll have to
> read it at some point, so no amount of encryption
In reply to Michael:
> We have had this discussion several times in the past for other reasons. The
> reality is that some people will never deploy the metadata API, so I feel
> like we need a better solution than what we have now.
Aha, that's definitely a good reason to continue making the
This is a great idea Steve! I didn't realize that this option was available.
Could all the sessions do this? We have some folks that aren't able to come due
to budget constraints, but this would allow them to participate at the PTG
sessions.
--
Brandon B. Jozsa
On Thu, Feb 16 2017, Sheng Liu wrote:
Hi liusheng,
> Thanks for clarifying, for the convenience to land Panko, we need to
> provide a python client library, I have finished a basic python-pankoclient
> in these two days, see[1]. which provides a Python API (`pankoclient`
> module) and a OSC
On Mon, Feb 13 2017, gordon chung wrote:
> i assume this is a vendor specific solution. we don't/prefer not to
> store drivers in Ceilometer. you can take a look at how powervm does
> this[1]. they basically extend the existing interfaces we provide[2]. i
> suspect you want to do something
Thomas Herve wrote:
> [...]
> At any rate, it's a matter of trust, a subject that comes from time to
> time, and it's fairly divisive. In this case though, I find it ironic
> that I can approve whatever garbage I want on master, it can make its
> way into a release, but if I want a bugfix
32 matches
Mail list logo