Re: [openstack-dev] [neutron] - Team photo

[Kevin Benton]

Clothes are strongly recommended as far as I understand it.

On Mon, Feb 20, 2017 at 1:47 AM, Gary Kotton  wrote:

> What is the dress code J
>
>
>
> *From: *"Das, Anindita" 
> *Reply-To: *OpenStack List 
> *Date: *Monday, February 20, 2017 at 5:16 AM
> *To: *OpenStack List 
> *Subject: *Re: [openstack-dev] [neutron] - Team photo
>
>
>
> +1
>
>
>
> *From: *Kevin Benton 
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" 
> *Date: *Friday, February 17, 2017 at 5:08 PM
> *To: *"openstack-dev@lists.openstack.org"  openstack.org>
> *Subject: *[openstack-dev] [neutron] - Team photo
>
>
>
> Hello!
>
>
>
> Is everyone free Thursday at 11:20AM (right before lunch break) for 10
> minutes for a group photo?
>
>
>
> Cheers,
> Kevin Benton
>
> __
> 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
>
>
__
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

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

[Gary Kotton]

+1

On 2/20/17, 12:17 AM, "Daniel Alvarez"  wrote:

+1

Enviado desde mi iPhone

> El 19 feb 2017, a las 11:45, Isaku Yamahata  
escribió:
> 
> +1
> 
> On Fri, Feb 17, 2017 at 11:18:41AM -0800,
> Kevin Benton  wrote:
> 
>> 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,
>> Kevin Benton
> 
>> 
__
>> 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
> 
> 
> -- 
> Isaku Yamahata 
> 
> __
> 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

__
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


__
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

Re: [openstack-dev] [neutron] - Team photo

[Gary Kotton]

What is the dress code ☺

From: "Das, Anindita" 
Reply-To: OpenStack List 
Date: Monday, February 20, 2017 at 5:16 AM
To: OpenStack List 
Subject: Re: [openstack-dev] [neutron] - Team photo

+1

From: Kevin Benton 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, February 17, 2017 at 5:08 PM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [neutron] - Team photo

Hello!

Is everyone free Thursday at 11:20AM (right before lunch break) for 10 minutes 
for a group photo?

Cheers,
Kevin Benton
__
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

[openstack-dev] [Zun]Use 'uuid' instead of 'id' as object ident in data model

[Wenzhi Yu]

Hi team,

I need your advice on this patch[1], which aims to implement etcd DB data model 
and API
for 'ResourceClass' object.

As you may know, in mysql implementation, mysql will generate a 'id' field, 
which is an
unique and auto increase integer. The 'id' is also used as 'primary key' or 
'foreign key'
in mysql[2].

However, in etcd implementation, etcd will NOT generate this 'id' itself, so I 
intend to
use the 'uuid' attribute of the object instead of 'id', and modify the DB API 
method to use
'uuid' as object ident instead of 'id', like[3]. Personally I feel using 'uuid' 
is more
reasonable because 'id' is a specific field in DB like mysql, seems it does not 
have actual
meaning in data model, right?

An alternative way Hongbin suggested is to generate an unique 'id' like mysql 
by ourselves
and insert the 'id' into etcd data model. But he said he's OK with the idea to 
replace 'id'
with 'uuid' if it does not break anything.

What's your opinion on this issue? Thanks in advance!

[1]https://review.openstack.org/#/c/434909/
[2]https://github.com/openstack/zun/blob/c0cebba170b8e3ea5e62e335536cf974bbbf08ec/zun/db/sqlalchemy/models.py#L200
[3]https://github.com/openstack/zun/blob/c0cebba170b8e3ea5e62e335536cf974bbbf08ec/zun/db/etcd/api.py#L209
 


Best Regards,
Wenzhi Yu (yuywz)



__
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

Re: [openstack-dev] [neutron][ovo] port bindings

[Kevin Benton]

I added a note to the section on OVO to the etherpad to discuss this.

On Sun, Feb 19, 2017 at 9:02 AM, Gary Kotton  wrote:

> Hi,
>
> We have encountered a few issues with the Port object. This makes use of
> the ml2 database model. Mono lithic plugins do not populate the information
> and this can lead to breakages. My understanding is that plugin specific
> objects should be in the directory: neutron/objects/plugins. I am wondering
> if we should take the same approach here for the port bindings?
>
> Any thoughts on this matter? I guess we can discuss this next week.
>
> Thanks
>
> Gary
>
> __
> 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
>
>
__
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

Re: [openstack-dev] [all] What's new in StoryBoard?

[Kevin Benton]

Thanks for the pointers.

So the plan for the projects with a lot of cross bug reports then is to
wait until a unified switch then?

On Sun, Feb 19, 2017 at 4:30 PM, Zara Zaimeche  wrote:

> On 19/02/17 12:19, Jeremy Stanley wrote:
>
>> On 2017-02-19 03:53:15 -0500 (-0500), Kevin Benton wrote:
>>
>>> If an existing project (e.g. Neutron) wants to adopt StoryBoard, is there
>>> some migration tooling to bring stuff from launchpad? It would be nice if
>>> we can have all of the existing bugs copied over so Storyboard would
>>> become
>>> the single source of truth rather than a mix between both storyboard and
>>> launchpad.
>>>
>> Absolutely. It has existed for years and is how the various Infra
>> bugs were pulled into SB originally. It hasn't been exercised in a
>> while and so needs a little fixing to catch up to the current
>> story/task schemas, but that's in progress.
>>
>
> Yep, I should add that we're planning to spend some time on this at the PTG
> at the start of the week, so if anyone is interested in helping out with
> these,
> feel free to wave in #storyboard and we'll arrange something! We'll likely
> be
> somewhere in the infra space.
>
> Best Wishes,
>
> Zara
>
>
> __
> 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
>
__
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

Re: [openstack-dev] [neutron] - Team photo

[Kevin Benton]

Ok. I've added it into the Neutron-related calendar here.

HTML:
https://calendar.google.com/calendar/embed?src=khbmhi1mhtthrmgv2gnejtul3o%40group.calendar.google.com=America/New_York

ICAL feed:
https://calendar.google.com/calendar/ical/khbmhi1mhtthrmgv2gnejtul3o%40group.calendar.google.com/public/basic.ics

On Sun, Feb 19, 2017 at 5:18 PM, Miguel Lavalle  wrote:

> I'll be there
>
> On Sun, Feb 19, 2017 at 9:14 AM, Dariusz Śmigiel <
> smigiel.dari...@gmail.com> wrote:
>
>> You're the boss
>>
>> 2017-02-19 8:52 GMT-05:00 reedip banerjee :
>> > +1
>> >
>> > On Sat, Feb 18, 2017 at 4:38 AM, Kevin Benton  wrote:
>> >>
>> >> Hello!
>> >>
>> >> Is everyone free Thursday at 11:20AM (right before lunch break) for 10
>> >> minutes for a group photo?
>> >>
>> >> Cheers,
>> >> Kevin Benton
>> >>
>> >> 
>> __
>> >> OpenStack Development Mailing List (not for usage questions)
>> >> Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>
>> >
>> >
>> >
>> > --
>> > Thanks and Regards,
>> > Reedip Banerjee
>> > IRC: reedip
>> >
>> >
>> >
>> >
>> >
>> > 
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>>
>>
>> --
>> Darek "dasm" Śmigiel
>>
>> 
>> Q: Why is this email five sentences or less?
>> A: http://five.sentenc.es
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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.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.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

[Steven Dake (stdake)]

Jeremy,

I understood your original message that it was a logistical nightmare to sort 
out scaling remote participation across the entire ODS or (now the new PTGs) 
and it is not a software tools problem but rather a logistics problem 
independent of whatever software platform is used.  I agree, even on a small 
scale in a ~10-20-person setting is difficult even though you were able to sort 
it out with the infrastructure team.

Michal will do the best he can to provide remote participation.  He called me 
this afternoon to verify I brought a mic and I did plan ahead and brought the 
best mic I could.  I brought only one mic as I had to borrow it from my 
daughter’s holiday stash.  It is an omni-directional gaming grade mic [1].  
There is only one of them and a litany of things could go wrong during the 
event which make remote participation for Kolla difficult or even an 
impossibility.

Neither Michal nor I can guarantee people will have a positive experience or 
any experience with remote participation as based upon my experience handling 
remote participation at previous midcycles as well as others experiences on 
this thread have already stated.  Michal as requested support, and I’ve 
personally provided the best level of support I can to our PTL.  If he wants to 
cancel remote participation, he should do so tonight as people will be 
expecting remote participation Monday at 9:00AM sharp.

If Michal wishes to proceed, I would highly recommend Michal request someone in 
the PTG sessions to proxy questions or statements from IRC as I have no 
speakers to connect with the microphone and the harmonics of everyone in the 
room connecting to webex may break the I/O of the mic.  The mic may also not 
pick up all conversations.

YMMV on the quality of the remote participation including a complete inability 
to participate remotely even though we have tried very hard to enable remote 
participation on a shoestring budget. 

Regards,
-steve

[1] 
https://www.amazon.com/Blue-Yeti-USB-Microphone-Blackout/dp/B00N1YPXW2/ref=sr_1_1?ie=UTF8=1487566448=8-1=yeti+blackout

-Original Message-
From: Jeremy Stanley 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Sunday, February 19, 2017 at 6:44 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

On 2017-02-19 23:17:27 + (+), Serguei Bezverkhi (sbezverk) wrote:
> @Jeremy if you have not tried thelatest webex, then sharing your
> Havana time frame webex experience is not very useful. I think you
> would agree if Havana release had some issues it would not
> automatically mean that newton has them :-)

It may seem that I was complaining about Webex, but really the bulk
of the issues were logistics-related. The way we do large rooms of
in-person participation is hard to capture with a conference call
system: managing local soundboards for all the microphones and
dozens of on-site computers scattered in different rooms, trying to
relay numerous streams over unstable network connections shared by
hundreds of on-site attendees, and the fact that it ends up being a
mostly one-way channel because making it possible for many remote
attendees to interject successfully into in-person conversations
probably requires a different style of discussion altogether.

At a smaller scale, we've successfully conferenced-bridged a couple
of remote participants into Infra team design summit sessions and
mid-cycles where there were between 10 and 20 people on site, but
that's substantially different from declaring the event is able to
support an arbitrary number of remote attendees. I've seen it work
out well in telepresence facilities, but not ad hoc installations
for conferences of the size we're talking about.
-- 
Jeremy Stanley

__
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


__
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

Re: [openstack-dev] [networking-sfc] Stable/Ocata Version

[Cathy Zhang]

We have been preparing for the ocata release. We are currently working on 
getting some final patches reviewed and merged.
Once those are merged, we will pull a stable/ocata branch around end of Feb or 
early March the latest.

Thanks,
Cathy

From: Gary Kotton [mailto:gkot...@vmware.com]
Sent: Sunday, February 19, 2017 4:29 AM
To: OpenStack List
Subject: [openstack-dev] [networking-sfc] Stable/Ocata Version

Hi,
When will this repo have a stable/ocata branch?
Thanks
Gary
__
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

Re: [openstack-dev] [all] [ptg] [goals] Pike WSGI Goal Planning

[Emilien Macchi]

On Mon, Feb 13, 2017 at 11:56 AM, Thierry Carrez  wrote:
> Emilien Macchi wrote:
>> I created https://etherpad.openstack.org/p/ptg-pike-wsgi so we can
>> start discussing on this goal.
>> Thierry confirmed to me that we would have a room on either Monday or
>> Tuesday. Please let us know in the etherpad if you have schedule
>> constraints.
>
> Sorry if I was unclear... you actually have the room available on both
> days !

That's awesome, so we have a room for 2 days: Georgia 11; Level 1.

Because folks are busy to attend different cross-projects sessions, I
think it would be great to kick-off the session on Monday morning with
a group of people representing different projects.

We might want to see some folks from Keystone and / or Telemetry who
have been involved in WSGI work; so they can share their experience,
feedback and the path they took to get there.
These 2 days could be used to:

1) Share the feedback of how some projects moved to WSGI only
deployments (Keystone, Telemetry, etc).
2) Dress a list of technical challenges.
3) Evaluate the amount of work for each project (we'll need a
representative of each project involved in API work).
4) Target some work for Pike (blueprints, specs, etc).

There is no specific agenda now, we hope to have dynamic discussions
each others, where team can share their experience.

I'll be at the room for 9am and stay around during the morning (note:
I might also say Hi to SWG to see how things are being organized).

Also, because there are 2 goals for Pike (this one and Python 3.5), we
might need to sync with Doug, to avoid overlaps of sessions, so we
allow folks to attend both topics. Our rooms will be neighbors, so I
guess we can easily communicate.

Please let us know any question or propose any session during these 2
days about $topic.

See you tomorrow,
Thanks,

> --
> Thierry Carrez (ttx)
>
> __
> 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



-- 
Emilien Macchi

__
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

Re: [openstack-dev] [monasca] Ideas to work on

[An Qi YL Lu]

Hi Roland
I went on holiday for last week. I’ll send you a notification next time. Sorry for being absent from last weekly meeting.
According to the comments that you gave, I can see the retention policy partly depends on metrics deleting. There can also be an option that we make a patch for influxDB to enable the basic support for retention on series. But this option seems take great effort. So in my opinion, we should implement metrics deleting before retention policy.
If we decide to run a scheduled job to simulate the retention policy, what tools will you suggest to host the job? I know there is a schedule module in python. (https://docs.python.org/2/library/sched.html) But it doesn’t seem appropriate for our consequence.
I think we can begin from metrics deleting. You talked about changing the storage of metrics. Shall we start from redesign the data storage structure? What is in your mind? I am going to study the current storage structure for a bit further now.
What shall I do next if I decide to work on metrics deleting? Do I need to write a whiteboard describing the detailed design?
Best,Anqi
 
 
- Original message -From: "Hochmuth, Roland M" To: "openstack-dev@lists.openstack.org" Cc: An Qi YL Lu/China/IBM@IBMCNSubject: Re: [monasca] Ideas to work onDate: Tue, Feb 14, 2017 10:05 AM 
Hi Anqi, See my comments listed below. Regards --Roland
 
  
From: An Qi YL Lu Date: Sunday, February 12, 2017 at 8:29 PMTo: Roland Hochmuth Cc: OpenStack List Subject: Re: [monasca] Ideas to work on 
  
Hi Roland
 
I am not sure whether you received my last email because I got a delivery failure notification. I am sending this again to ensure that you can see this email.
 
Best,
Anqi
 
- Original message -From: An Qi YL Lu/China/IBMTo: roland.hochm...@hpe.comCc: openstack-dev@lists.openstack.orgSubject: Re: [monasca] Ideas to work onDate: Fri, Feb 10, 2017 5:14 PM  
Hi Roland
 
Thanks for your suggestions. The list you made is useful, helping me get clues in areas that I can work on. I spent some time doing investigation in the bps that you introduced.
 
I am most interested in data retention and metrics deleting.
 
Data retention: I had a quick look into the data retention policy of influxDB. It apparently support different retention policy for different series. To my understanding, the whiteboard in this bp has a straightforward design for this feature. I didn't quite get what is the complex point. Could you please shed some light so I can learn where the complicated part is?  
The retention policy specified in the bp, https://blueprints.launchpad.net/monasca/+spec/per-project-data-retention,  is per project. InfluxDB allows retention policies to be set per database, https://docs.influxdata.com/influxdb/v1.2/query_language/database_management/#create-retention-policies-with-create-retention-policy.
 
Currently, we store all metrics for all tenants in one database. One approach, which would involve a bit of re-engineering if we choose to do it, would be to store metrics for a project in a database for each project.
 
I could also imagine having retention policies per metric per tenant. For example, there might be metrics for metering that should be stored for a longer period than operational metrics. There isn't a way to do this directly in InfluxDB using the built-in data retention policy. However, it could possibly be done using delete and scheduling jobs that periodically run that prune the database.
 
For the Vertica database, we, as in HPE, simulate retention policies by running a cron job that drops partitions after some period of time, such as 45 days. Charter has a more sophisticated cron job that deletes metrics from specific tenants at different periods than the operational metrics. For example, tenants of the cloud might have their metrics deleted every two weeks. Metering metrics might be deleted every 13 months.
 
The problem with deleting specific metrics is the performance. Dropping partitions is extremely fast. However, deleting metrics might be slow and also lock the database and prevent writes and/or queries to it. Therefore, to delete metrics, you could trickle deletes in, reducing the overall impact for any period of time, or do in the Charter case, run the deletion script at 2:00 AM in the morning, when usage of the system is light. 
 
Metrics deleting: In influxDB 1.1 (or any version after 0.9), it supports deleting series, though you cannot specify time interval for this operation. It simply deletes all points from a series in a database. I think one of the tricky parts is to decide the data dependent on a metric to be deleted, such as measurements, alarms. Please point it out if my understanding is not precise. 
The problem I believe is that a single series in InfluxDB has the data for multiple tenants. Deleting a single series would then 

Re: [openstack-dev] [neutron] - Team photo

[Das, Anindita]

+1

From: Kevin Benton 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, February 17, 2017 at 5:08 PM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [neutron] - Team photo

Hello!

Is everyone free Thursday at 11:20AM (right before lunch break) for 10 minutes 
for a group photo?

Cheers,
Kevin Benton
__
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

[openstack-dev] [release] please review the Ocata final release tags

[Doug Hellmann]

Release liaisons and PTLs,

The patch to tag the Ocata final releases for milestone-based
projects is up at [1]. Please check the patch to verify that it
matches your expectations and then sign off with a +1.

Thanks,
Doug

[1] https://review.openstack.org/#/c/435816/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

Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

[Jeremy Stanley]

On 2017-02-19 23:17:27 + (+), Serguei Bezverkhi (sbezverk) wrote:
> @Jeremy if you have not tried thelatest webex, then sharing your
> Havana time frame webex experience is not very useful. I think you
> would agree if Havana release had some issues it would not
> automatically mean that newton has them :-)

It may seem that I was complaining about Webex, but really the bulk
of the issues were logistics-related. The way we do large rooms of
in-person participation is hard to capture with a conference call
system: managing local soundboards for all the microphones and
dozens of on-site computers scattered in different rooms, trying to
relay numerous streams over unstable network connections shared by
hundreds of on-site attendees, and the fact that it ends up being a
mostly one-way channel because making it possible for many remote
attendees to interject successfully into in-person conversations
probably requires a different style of discussion altogether.

At a smaller scale, we've successfully conferenced-bridged a couple
of remote participants into Infra team design summit sessions and
mid-cycles where there were between 10 and 20 people on site, but
that's substantially different from declaring the event is able to
support an arbitrary number of remote attendees. I've seen it work
out well in telepresence facilities, but not ad hoc installations
for conferences of the size we're talking about.
-- 
Jeremy Stanley

__
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

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

[Michael Still]

Config drive over read-only NFS anyone?

Michael

On Sun, Feb 19, 2017 at 6:12 AM, Steve Gordon  wrote:

> - Original Message -
> > From: "Artom Lifshitz" 
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> > Sent: Saturday, February 18, 2017 8:11:10 AM
> > Subject: Re: [openstack-dev] [nova] Device tagging: rebuild config drive
> upon instance reboot to refresh metadata on
> > it
> >
> > 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 config
> > drive a first-class citizen.
>
> The other reason is that the metadata API as it stands isn't an option for
> folks trying to do IPV6-only IIRC.
>
> -Steve
>
> __
> 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
>



-- 
Rackspace Australia
__
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

Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

[Serguei Bezverkhi (sbezverk)]

@Jeremy if you have not tried thelatest webex, then sharing your Havana time 
frame webex experience is not very useful. I think you would agree if Havana 
release had some issues it would not automatically mean that newton has them :-)
Serguei 

-Original Message-
From: Britt Houser (bhouser) 
Sent: Sunday, February 19, 2017 6:43 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

I’ve attended two Kolla midcycles remotely everything Steve said here is true.  
But, as long as your expectations are set accordingly, suboptimal is better 
than nothing at all. =)

Thx,
britt

On 2/19/17, 1:09 AM, "Steven Dake (stdake)"  wrote:

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 to mention the fact 
that the wireless services may be in a DOS state because of the number of 
attendees.

Michal asked the foundation if remote participation was an option, and they 
stated it was.  Michal had then suggested to use zoom.us and promised remote 
participation, however, that didn’t get done until Friday.  Cisco isn’t 
donating the webex services in this case; I am as a community member and Kolla 
core.

I have also found during Kolla midcycle events we have held since the 
founding of Kolla and prior to the PTG (which is the new midcycle) that every 
midcycle event with remote participation is not very optimal for participants 
for the litany of reasons you mention.

Clearly in-person PTG participation is superior to the hacked-together 
telepresence we may have available at the PTG.  I do think whatever 
teleconference hardware Michal brings to summit is better than looking at the 
output of an Etherpad where all kinds of context is lost.

For folks attending from their office remotely, don’t expect a great 
experience.  Face to face participation is always better as Jeremy has stated.

Regards
-steve

-Original Message-
From: Jeremy Stanley 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Saturday, February 18, 2017 at 5:11 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

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 summit in Portland, OR. As one of the volunteers who agreed
to monitor the local systems, I can say that it was a suboptimal
solution at best. Supplied laptops acting as the "presenter"
consoles crashed/hung repeatedly, slight instabilities in conference
networking were a major impediment to streaming, omnidirectional
microphones placed throughout the conference rooms still failed to
pick up much of the conversation, and for those who did attempt to
participate remotely we heard numerous complaints about how they
couldn't follow heated discussions with dozens of participants in a
room together.
-- 
Jeremy Stanley


__
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


__
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


__
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
__
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

[openstack-dev] [api-wg][ptg] Room for API-WG in Atlanta PTG

[Ed Leafe]

Just to let everyone know - we’ve been given our own room for the PTG: Georgia 
5: Level 1 on Monday and Tuesday. So we won’t have to be crowding out the 
Architecture WG. :)

-- Ed Leafe






__
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

Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

[Vikram Hosakote (vhosakot)]

Great, thanks a lot for setting this up Steve!

Regards,
Vikram Hosakote
IRC: vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Saturday, February 18, 2017 at 8:16 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

Hey folks,

To take some load off Michal I've setup remote participation for day #1 of the 
PTG.

Michal had suggested he might setup zoom instead of webex, however, I haven't 
seen that happen and several people have asked on IRC how remote participation 
will work at the PTG.  If Michal sets up remote participation in some othe 
rway, ignore this email (and he will follow up with a zoom.us calendar invite).

Note I feel like google hangouts is difficult to manage and is a non-starter 
because google Is not available to our worldwide participants.

See below for details:



From: Steven Dake >
Reply-To: "Steven Dake (stdake)" >
Date: Saturday, February 18, 2017 at 12:02 AM
To: "Steven Dake (stdake)" >
Subject: (Forward to others) WebEx meeting invitation: Kolla PTG Day #1

You can forward this invitation to others.


Hello,

Steven Dake invites you to join this WebEx meeting.





Kolla PTG Day #1

Monday, February 20, 2017

9:00 am  |  Eastern Standard Time (New York, GMT-05:00)  |  6 hrs





Join WebEx 
meeting


Meeting number:

204 403 514

Meeting password:

OpenStackKolla (67367822 from phones)


Join from a video conferencing system or application

Dial 204403...@cisco.webex.com<%20sip:204403...@cisco.webex.com>

>From the Cisco internal network, dial *267* and the 9-digit meeting number. If 
>you are the host, enter your PIN when prompted.





Join by phone

+1-866-432-9903 Call-in toll-free number (US/Canada)

+1-408-525-6800 Call-in toll number (US/Canada)

Access code: 204 403 514

Global call-in 
numbers
  |  Toll-free calling 
restrictions





Add this 
meeting
 to your calendar. (Cannot add from mobile devices.)





Can't join the meeting? Contact support.





IMPORTANT NOTICE: Please note that this WebEx service allows audio and other 
information sent during the session to be recorded, which may be discoverable 
in a legal matter. By joining this session, you automatically consent to such 
recordings. If you do not consent to being recorded, discuss your concerns with 
the host or do not join the session.




__
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

Re: [openstack-dev] [neutron] - Team photo

[Miguel Lavalle]

I'll be there

On Sun, Feb 19, 2017 at 9:14 AM, Dariusz Śmigiel 
wrote:

> You're the boss
>
> 2017-02-19 8:52 GMT-05:00 reedip banerjee :
> > +1
> >
> > On Sat, Feb 18, 2017 at 4:38 AM, Kevin Benton  wrote:
> >>
> >> Hello!
> >>
> >> Is everyone free Thursday at 11:20AM (right before lunch break) for 10
> >> minutes for a group photo?
> >>
> >> Cheers,
> >> Kevin Benton
> >>
> >> 
> __
> >> 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
> >>
> >
> >
> >
> > --
> > Thanks and Regards,
> > Reedip Banerjee
> > IRC: reedip
> >
> >
> >
> >
> >
> > 
> __
> > 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
> >
>
>
>
> --
> Darek "dasm" Śmigiel
>
> 
> Q: Why is this email five sentences or less?
> A: http://five.sentenc.es
>
> __
> 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
>
__
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

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

[Daniel Alvarez]

+1

Enviado desde mi iPhone

> El 19 feb 2017, a las 11:45, Isaku Yamahata  
> escribió:
> 
> +1
> 
> On Fri, Feb 17, 2017 at 11:18:41AM -0800,
> Kevin Benton  wrote:
> 
>> 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,
>> Kevin Benton
> 
>> __
>> 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
> 
> 
> -- 
> Isaku Yamahata 
> 
> __
> 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

__
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

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

[Thomas Morin]

+1 !

-Thomas

Fri Feb 17 2017 20:18:41 GMT+0100 (CET), 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,
Kevin Benton


__
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




__
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

Re: [openstack-dev] [all] What's new in StoryBoard?

[Zara Zaimeche]

On 19/02/17 12:19, Jeremy Stanley wrote:

On 2017-02-19 03:53:15 -0500 (-0500), Kevin Benton wrote:

If an existing project (e.g. Neutron) wants to adopt StoryBoard, is there
some migration tooling to bring stuff from launchpad? It would be nice if
we can have all of the existing bugs copied over so Storyboard would become
the single source of truth rather than a mix between both storyboard and
launchpad.

Absolutely. It has existed for years and is how the various Infra
bugs were pulled into SB originally. It hasn't been exercised in a
while and so needs a little fixing to catch up to the current
story/task schemas, but that's in progress.


Yep, I should add that we're planning to spend some time on this at the PTG
at the start of the week, so if anyone is interested in helping out with 
these,
feel free to wave in #storyboard and we'll arrange something! We'll 
likely be

somewhere in the infra space.

Best Wishes,

Zara

__
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

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Clint Byrum]

Excerpts from Thomas Goirand's message of 2017-02-19 00:58:01 +0100:
> 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 libraries is DPMT.
> 
> I wish the Python team was more like the Perl one, who really is a well
> functioning with a strong team spirit and commitment, with a sense of
> collective responsibility. It's far from being the case in the DPMT.
> 
> Moving packages to the DPMT will not magically get you new maintainers.
> Even within the team, there's unfortunately *a lot* of strong package
> ownership.
> 

Whatever the issues are with that team, there's a _mountain_ of packages
to maintain, and only one team whose charter is to maintain python
modules. So we're going to have to deal with the shortcomings of that
relationship, or find more OpenStack specific maintainers.

My main concern is making sure Debian users can interact with OpenStack.
It's truly unfortunate that we may not have OpenStack's core kept well
maintained in Debian (though I can't see any reason Ubuntu's developers
wouldn't help with that -- feel free to chime in Ubuntu folks). But it's
vital to OpenStack and Debian's interests that Debian users be able
to grab the pieces of the OpenStack SDK that they need to communicate
with OpenStack clouds. It's also important that the generic libraries
we maintain, like stevedore, remain up to date in Debian so they don't
fall out of favor with users. Nothing kills a library like old versions
breaking apps.

I'm not going to rush off and do anything now. I don't have time. But
it's now on my radar, and when I find a window for it to fall into, I'll
start looking at how best to transition these. In the mean time I'll
hold out hope that we'll have good news and you can continue your work.

__
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

[openstack-dev] [QA][ptg] QA Team social evening

[Andrea Frittoli]

Hello,

I'd like to propose a social evening for the folks in the QA sessions.
I prepared a doodle [0] so if you're interested please vote :)

I added the link to the main QA etherpad [1] as well.
If you know a good place to go for food or drinks please add it to the
etherpad as well.

Andrea

[0] http://doodle.com/poll/yxy8ts8s8te8rwwh
[1] https://etherpad.openstack.org/p/qa-ptg-pike
__
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

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

[Isaku Yamahata]

+1

On Fri, Feb 17, 2017 at 11:18:41AM -0800,
Kevin Benton  wrote:

> 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,
> Kevin Benton

> __
> 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


-- 
Isaku Yamahata 

__
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

Re: [openstack-dev] [neutron] - Team photo

[Dariusz Śmigiel]

You're the boss

2017-02-19 8:52 GMT-05:00 reedip banerjee :
> +1
>
> On Sat, Feb 18, 2017 at 4:38 AM, Kevin Benton  wrote:
>>
>> Hello!
>>
>> Is everyone free Thursday at 11:20AM (right before lunch break) for 10
>> minutes for a group photo?
>>
>> Cheers,
>> Kevin Benton
>>
>> __
>> 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
>>
>
>
>
> --
> Thanks and Regards,
> Reedip Banerjee
> IRC: reedip
>
>
>
>
>
> __
> 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
>



-- 
Darek "dasm" Śmigiel


Q: Why is this email five sentences or less?
A: http://five.sentenc.es

__
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

[openstack-dev] [neutron][ovo] port bindings

[Gary Kotton]

Hi,
We have encountered a few issues with the Port object. This makes use of the 
ml2 database model. Mono lithic plugins do not populate the information and 
this can lead to breakages. My understanding is that plugin specific objects 
should be in the directory: neutron/objects/plugins. I am wondering if we 
should take the same approach here for the port bindings?
Any thoughts on this matter? I guess we can discuss this next week.
Thanks
Gary
__
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

Re: [openstack-dev] [neutron] - Team photo

[reedip banerjee]

+1

On Sat, Feb 18, 2017 at 4:38 AM, Kevin Benton  wrote:

> Hello!
>
> Is everyone free Thursday at 11:20AM (right before lunch break) for 10
> minutes for a group photo?
>
> Cheers,
> Kevin Benton
>
> __
> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

[Akihiro Motoki]

+1

2017-02-17 14:18 GMT-05:00 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,
> Kevin Benton
>
> __
> 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
>
>
__
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

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

[Anna Taraday]

+1

On Sun, Feb 19, 2017 at 11:03 AM Takashi Yamamoto 
wrote:

> +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,
> Kevin Benton
>
> __
> 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
>
> __
> 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
>
-- 
Regards,
Ann Taraday
__
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

[openstack-dev] [networking-sfc] Stable/Ocata Version

[Gary Kotton]

Hi,
When will this repo have a stable/ocata branch?
Thanks
Gary
__
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

Re: [openstack-dev] [all] What's new in StoryBoard?

[Jeremy Stanley]

On 2017-02-19 03:53:15 -0500 (-0500), Kevin Benton wrote:
> If an existing project (e.g. Neutron) wants to adopt StoryBoard, is there
> some migration tooling to bring stuff from launchpad? It would be nice if
> we can have all of the existing bugs copied over so Storyboard would become
> the single source of truth rather than a mix between both storyboard and
> launchpad.

Absolutely. It has existed for years and is how the various Infra
bugs were pulled into SB originally. It hasn't been exercised in a
while and so needs a little fixing to catch up to the current
story/task schemas, but that's in progress.

The challenge for Neutron is that it shares lots of multi-project
bugs in LP with the likes of Nova, Keystone, Oslo, et cetera so we
can't effectively import one of those projects without doing them
all (otherwise the bugs continue to get updated in both places and
start to diverge). This is why we're investing as much effort as
possible into collecting feedback from stakeholders on various
teams, so we can make sure SB gets to a point where everyone is
comfortable migrating at the same time.
-- 
Jeremy Stanley

__
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

[openstack-dev] [trove] session schedule for Pike PTG

[Amrith Kumar]

For those attending the Pike PTG and interested in the trove sessions,
please fill in your participation (and IRC nick) at the etherpad[1].

We will have a complete schedule by end of day on Tuesday. If you are
specifically interested in a session and have time constraints, please put
that into the etherpad. Let's plan to start on Wednesday morning at 9am in
the dedicated Trove room with a quick scheduling session; if you are able to
attend in person that's great, if you are not make sure that your interest
and constraints are in the etherpad.

Thanks,

-amrith

[1] https://etherpad.openstack.org/p/trove-pike-ptg-topics

--
Amrith Kumar
GPG: 0x5e48849a9d21a29b



smime.p7s
Description: S/MIME cryptographic signature
__
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

Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

[Britt Houser (bhouser)]

I’ve attended two Kolla midcycles remotely everything Steve said here is true.  
But, as long as your expectations are set accordingly, suboptimal is better 
than nothing at all. =)

Thx,
britt

On 2/19/17, 1:09 AM, "Steven Dake (stdake)"  wrote:

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 to mention the fact 
that the wireless services may be in a DOS state because of the number of 
attendees.

Michal asked the foundation if remote participation was an option, and they 
stated it was.  Michal had then suggested to use zoom.us and promised remote 
participation, however, that didn’t get done until Friday.  Cisco isn’t 
donating the webex services in this case; I am as a community member and Kolla 
core.

I have also found during Kolla midcycle events we have held since the 
founding of Kolla and prior to the PTG (which is the new midcycle) that every 
midcycle event with remote participation is not very optimal for participants 
for the litany of reasons you mention.

Clearly in-person PTG participation is superior to the hacked-together 
telepresence we may have available at the PTG.  I do think whatever 
teleconference hardware Michal brings to summit is better than looking at the 
output of an Etherpad where all kinds of context is lost.

For folks attending from their office remotely, don’t expect a great 
experience.  Face to face participation is always better as Jeremy has stated.

Regards
-steve

-Original Message-
From: Jeremy Stanley 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Saturday, February 18, 2017 at 5:11 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

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 summit in Portland, OR. As one of the volunteers who agreed
to monitor the local systems, I can say that it was a suboptimal
solution at best. Supplied laptops acting as the "presenter"
consoles crashed/hung repeatedly, slight instabilities in conference
networking were a major impediment to streaming, omnidirectional
microphones placed throughout the conference rooms still failed to
pick up much of the conversation, and for those who did attempt to
participate remotely we heard numerous complaints about how they
couldn't follow heated discussions with dozens of participants in a
room together.
-- 
Jeremy Stanley


__
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


__
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


__
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

Re: [openstack-dev] [all] What's new in StoryBoard?

[Kevin Benton]

Hi,

If an existing project (e.g. Neutron) wants to adopt StoryBoard, is there
some migration tooling to bring stuff from launchpad? It would be nice if
we can have all of the existing bugs copied over so Storyboard would become
the single source of truth rather than a mix between both storyboard and
launchpad.

Cheers,
Kevin Benton

On Wed, Feb 15, 2017 at 3:28 PM, Kendall Nelson 
wrote:

> Hello All!
>
> In your continued education about our new task tracking tool, we have
> a new blog post! It's focus is on the new functionalities that Storyboard
> provides [1]. We hope that all of these posts are helping you get more
> comfortable with the tool.
>
> If you missed any of our previous posts:
> - Why Storyboard?[2]
> - Mapping Launchpad to Storyboard [3]
>
> And if you want to play around in a StoryBoard sandbox [4], check out the
> real thing [5], read the docs [6], or attend a meeting [7], please do!
>
> We are looking at moving teams over as soon as possible (more stand alone
> projects first before larger ones with multi project bugs and features) so
> if you think your project is ready, please let us know!
>
> -Kendall Nelson (diablo_rojo) and the StoryBoard team
>
> [1] https://storyboard-blog.io/things-that-storyboard-does-
> differently.html
> [2] https://storyboard-blog.io/why-storyboard-for-openstack.html
> [3] https://storyboard-blog.io/mapping-launchpad-to-storyboard.html
> [4] https://storyboard-dev.openstack.org/
> [5] https://storyboard.openstack.org/
> [6] http://docs.openstack.org/infra/storyboard/
> [7] https://wiki.openstack.org/wiki/StoryBoard
>
> __
> 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
>
>
__
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