[openstack-dev] [all] List of all Boston Forum Session Etherpads

[Tom Fifield]

Hi all,

With the forum not long away, it's time to start listing your session 
etherpads. I've gathered all that I knew about on:


https://wiki.openstack.org/wiki/Forum/Boston2017


Please add yours ASAP!


Regards,


Tom

__
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] Ops Meetup Team

[Melvin Hillsman]

Hey everyone,

We have been having some great momentum since the Foundation enlisted a
small group of operators to manage the Midcycle and to form the Ops Meetup
Team. We have a few asks related to the teaml:

   1. More people! We need more folks to participate in the team meetings
   and activities; the more the merrier. You do not have to be an "operator";
   everyone is welcome!
   2. Themed midcycle. In an effort to continue to ensure the midcycle is
   relevant, we would like feedback on if folks agree with the midcycle being
   themed. Basically wherever the midcycle is being held, contact some folks
   in the region and focus on content that is more relevant to the folks in
   the region.

More information on the team can be found on the wiki[1]. Meeting day and
time is Tuesdays @ 1500UTC in #openstack-operators. We will also have a
session[2] in Boston around the team, its purpose, and some items to make
decisions on; looking forward to seeing you all in Boston!

[1] https://wiki.openstack.org/wiki/Ops_Meetups_Team
[2] https://www.openstack.org/summit/boston-2017/summit-schedule
/events/18935/openstack-operators-ops-meetup-team-catch-up

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646

Learner | Ideation | Belief | Responsibility | Command
__
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] project on-board schedule

[Kendall Nelson]

Yes, I should be able to make that happen :)

- Kendall

On Tue, Apr 25, 2017, 10:03 PM joehuang  wrote:

> Hello, Kendall,
>
> Thank you very much for the slot you provided, but consider that it's
> launch time, I am afraid that audience need to have launch too.
>
> I just discussed with Hongbin, the PTL of Zun, he said it's OK to exchange
> the project on-boarding time slot between Zun[1] and Tricircle[2].
>
> After exchange, Tricircle will share with Sahara and use the first half
> (45 minutes) just like Zun in this time slot. And Zun's on-boarding session
> will be moved to Monday 2:00pm~3:30pm.
>
> Is this exchange is feasible?
>
> [1]
> https://www.openstack.org/summit/boston-2017/summit-schedule/events/18701/zunsahara-project-onboarding
> [2]
> https://www.openstack.org/summit/boston-2017/summit-schedule/events/18693/tricircle-project-onboarding
>
> Best Regards
> Chaoyi Huang (joehuang)
> --
> *From:* Kendall Nelson [kennelso...@gmail.com]
> *Sent:* 26 April 2017 4:07
> *To:* OpenStack Development Mailing List (not for usage questions);
> joehuang
>
> *Subject:* Re: [openstack-dev] project on-board schedule
> Hello Joe,
>
> I can offer TriCircle a lunch slot on Wednesday from 12:30-1:50?
>
> -Kendall
>
>
> On Tue, Apr 25, 2017 at 4:08 AM joehuang  wrote:
>
>> Hi,
>>
>> Thank you Tom, I found that the on-boarding session of Tricircle [1] is
>> overlapping with my talk{2]:
>>
>> [1]
>> https://www.openstack.org/summit/boston-2017/summit-schedule/events/18693/tricircle-project-onboarding
>> [2]
>> https://www.openstack.org/summit/boston-2017/summit-schedule/events/18076/when-one-cloud-is-not-enough-an-overview-of-sites-regions-edges-distributed-clouds-and-more
>>
>> Is there any other project can help us to exchange the on-boarding
>> session? Thanks a lot, I just find the issue.
>>
>> Best Regards
>> Chaoyi Huang (joehuang)
>>
>> 
>> From: Tom Fifield [t...@openstack.org]
>> Sent: 25 April 2017 16:50
>> To: openstack-dev@lists.openstack.org
>> Subject: Re: [openstack-dev] project on-board schedule
>>
>> On 25/04/17 16:35, joehuang wrote:
>> > Hello,
>> >
>> > Where can I find the project on-board schedule in OpenStack Boston
>> > summit? I haven't found it yet, and maybe I missed some mail. Thanks a
>> lot.
>>
>> It's listed on the main summit schedule, under the Forum :)
>>
>> Here's a direct link to the Forum category:
>>
>> https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146
>>
>>
>> __
>> 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] [nova] Owners needed for approved but orphaned OSIC blueprints

[Ghanshyam Mann]

Thanks Matt, John.

I would be able to help on policy stuff where needed.

-gmann


On Tue, Apr 25, 2017 at 5:32 PM, John Garbutt  wrote:
> Hi,
>
> Matt, thanks for pulling that list together.
>
> I have context on most of those, if people would like to take those on.
> I hope to review most of those an clarify where everything is at.
>
> I am going to take a look at where we are at with policy stuff first.
>
> Thanks,
> johnthetubaguy
>
> On 24 April 2017 at 22:45, Matt Riedemann  wrote:
>>
>> Hi everyone,
>>
>> With the recent unfortunate news about OSIC ending abruptly and several Nova 
>> developers no longer being able to work on the project, I wanted to go over 
>> the list of blueprints which were approved for Pike and which now no longer 
>> have an owner. I am starting this thread to look for owners for each 
>> blueprint. If you have questions about picking one up but you're maybe too 
>> shy to ask questions about it in the mailing list, feel free to email me 
>> directly or send me a private message in IRC. The list is in no particular 
>> order.
>>
>> * 
>> https://blueprints.launchpad.net/nova/+spec/live-migration-per-instance-timeout
>>
>> This is not started but there is a spec with the design.
>>
>> * 
>> https://blueprints.launchpad.net/nova/+spec/remove-discoverable-policy-rules
>>
>> This is not started but is a specless blueprint that is straight-forward.
>>
>> * https://blueprints.launchpad.net/nova/+spec/remove-nova-cert
>>
>> This is not started but should be pretty straightforward, and has a spec 
>> with the details.
>>
>> * https://blueprints.launchpad.net/nova/+spec/ironic-rescue-mode
>>
>> The nova side of this is dependent on Ironic changes which were owned by 
>> OSIC developers. So the nova blueprint is effectively blocked now.
>>
>> * https://blueprints.launchpad.net/nova/+spec/live-migrate-rescued-instances
>>
>> This is started, and was picked up from some work started by HPE in previous 
>> releases. I'm not sure what state it is in however.
>>
>> * https://blueprints.launchpad.net/nova/+spec/policy-docs
>>
>> Most of this is done. There might be a few more non-discoverable policy 
>> rules that need documentation, but I haven't gone through what's left in 
>> detail yet.
>>
>> * 
>> https://blueprints.launchpad.net/nova/+spec/prep-for-network-aware-scheduling-pike
>>
>> I'm not sure if John is going to continue trying to work on this or not yet, 
>> but I think it would probably be good to get a helping hand here regardless 
>> as it's stalled since Newton (really due to lack of reviews).
>>
>> * https://blueprints.launchpad.net/nova/+spec/use-service-tokens-pike
>>
>> This was started and made progress in Ocata but needs someone to take over 
>> the remaining changes. This overlaps somewhat with 
>> https://blueprints.launchpad.net/nova/+spec/use-service-catalog-for-endpoints.
>>
>> * https://blueprints.launchpad.net/nova/+spec/centralize-config-options-pike
>>
>> This is an ongoing multi-contributor effort. Stephen Finucane would be a 
>> good organizer here if no one else is interested in formally "owning" it.
>>
>> * 
>> https://blueprints.launchpad.net/nova/+spec/live-migration-force-after-timeout
>>
>> This has been started but needs work. There is also a spec for the design.
>>
>> --
>>
>> If you are interested in owning one of these, please reply so I and others 
>> know, or contact me privately.
>>
>> --
>>
>> Thanks,
>>
>> Matt
>>
>> __
>> 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][networking-midonet] networking-midonet core reviewer proposal

[Ryu Ishimoto]

+1 !

On Wed, Apr 26, 2017 at 11:41 AM Takashi Yamamoto 
wrote:

> unless anyone objects, i'll add the following people to
> networking-midonet project's core reviewers.
>
> - Antonio Ojea
> - Brandon Berg
> - Xavi León
>
> http://stackalytics.com/report/contribution/networking-midonet/30
> http://stackalytics.com/report/contribution/networking-midonet/90
>
> __
> 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] project on-board schedule

[joehuang]

Hello, Kendall,

Thank you very much for the slot you provided, but consider that it's launch 
time, I am afraid that audience need to have launch too.

I just discussed with Hongbin, the PTL of Zun, he said it's OK to exchange the 
project on-boarding time slot between Zun[1] and Tricircle[2].

After exchange, Tricircle will share with Sahara and use the first half (45 
minutes) just like Zun in this time slot. And Zun's on-boarding session will be 
moved to Monday 2:00pm~3:30pm.

Is this exchange is feasible?

[1] 
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18701/zunsahara-project-onboarding
[2] 
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18693/tricircle-project-onboarding

Best Regards
Chaoyi Huang (joehuang)

From: Kendall Nelson [kennelso...@gmail.com]
Sent: 26 April 2017 4:07
To: OpenStack Development Mailing List (not for usage questions); joehuang
Subject: Re: [openstack-dev] project on-board schedule

Hello Joe,

I can offer TriCircle a lunch slot on Wednesday from 12:30-1:50?

-Kendall


On Tue, Apr 25, 2017 at 4:08 AM joehuang 
> wrote:
Hi,

Thank you Tom, I found that the on-boarding session of Tricircle [1] is 
overlapping with my talk{2]:

[1] 
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18693/tricircle-project-onboarding
[2] 
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18076/when-one-cloud-is-not-enough-an-overview-of-sites-regions-edges-distributed-clouds-and-more

Is there any other project can help us to exchange the on-boarding session? 
Thanks a lot, I just find the issue.

Best Regards
Chaoyi Huang (joehuang)


From: Tom Fifield [t...@openstack.org]
Sent: 25 April 2017 16:50
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] project on-board schedule

On 25/04/17 16:35, joehuang wrote:
> Hello,
>
> Where can I find the project on-board schedule in OpenStack Boston
> summit? I haven't found it yet, and maybe I missed some mail. Thanks a lot.

It's listed on the main summit schedule, under the Forum :)

Here's a direct link to the Forum category:

https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146


__
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] [neutron][networking-midonet] networking-midonet core reviewer proposal

[Takashi Yamamoto]

unless anyone objects, i'll add the following people to
networking-midonet project's core reviewers.

- Antonio Ojea
- Brandon Berg
- Xavi León

http://stackalytics.com/report/contribution/networking-midonet/30
http://stackalytics.com/report/contribution/networking-midonet/90

__
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] TC Report 17

[Chris Dent]

_This is published both as email and a blog post._

# Intro

As promised, here's my first attempt at providing a weekly overview
of what's happening with the TC. The structure here is subject to
change as I figure out what makes sense. Suggestions welcome.

This one is short because it is based on today. Next week's will be
based on the entire week.

# Meeting

## Settling in the new folk

Welcoming the new people and covering house rules[^1]. The fun part
of this was by the 5th minute of the meeting we had already
identified a lack of shared understanding on when to use a
code-review vote and when to use a rollcall vote. There were a few
different opinions. Before I get accused of casting shade before
I've even started I think a) different opinions are _great_, b)
highlighting those differences (so we can resolve them) even more so.

One opinion that seemed to make sense was that code-review was for
expressing a comment on the correctness of the content (as in, a -1
is for many spelling mistakes, or poorly formatted yaml) and
rollcall is the actual vote being made on the proposed change (yes,
this is something I agree with; no, I disagree).

[^1]: 

## User Survey findings

Summary info about the findings of the user survey[^2]. Good question
from the sidelines about the same big issues coming up in the
findings of every survey. This then led to questions about what
impact can the TC have in driving corporate contributors to focus on
those issues (such as long term support and upgrade difficulty).
There's a ever present need to make sure that stuff is effectively
highlighted.

Which then moved to the complicated problem of OpenStack moving both
too fast and too slow at the same time, depending on who was
looking. And the difficulty with lack of centralized control over
the technical direction of OpenStack and (probably most importantly)
the application of resources. It turned into a bit of black hole so
the decision was to move the discussion to the mailing list, which I
hope actually happens.

heidijoy is going to provide some further analysis of "net promoter
scores" to see what correlations exists. I was curious whether
openstack devs like openstack more or less than other respondents.

[^2]: 

## Maybe dropping the meeting

Flavio has introduced a proposal to drop the regularly scheduled TC
meeting[^3] in favor of more mailing list discussion and more ad-hoc
meetings. This is something that could greatly change how the
community interacts with the TC, so if you have a preference you can
state it on the review.

[^3]: 

# Other Stuff in Progress

## Draft vision for the TC

It's 2019 and the TC is looking back on itself[^4]. This is an exercise
to think about where the TC wants to be in the future, and from
there derive some goals to get there. From some of the feedback it
is pretty clear that not everyone understands the nature of the
exercise. This isn't a plan of action, more of a limbering exercise
to figure out a plan of action.

As you've probably seen there's been a big push to get feedback on
this. It's worth providing.

[^4]: 

## Lingering Proposals

The following proposals are languishing, awaiting either feedback or
further effort from the author. If these matter to you, you can add
your voice.

* [Add tag assert:never-breaks-compat](https://review.openstack.org/#/c/446561/)
* [deprecate postgresql in OpenStack](https://review.openstack.org/#/c/427880/)
* [Describe what upstream support 
means](https://review.openstack.org/#/c/440601/)

# Colophon

This is intentionally a biased and incomplete view of events. I
can't hope to report things objectively or completely so it is
better to be open about it and hope that if there is disagreement
with my interpretation of events or what I felt was worth mentioning
people will respond saying so. Responses, engagement, feedback are
the entire point for doing these. If, over time, my interpretation
proves to be too out of bounds maybe someone else will start their
own newsletter. And then after a while every member of the TC will
be writing their own report.

--
Chris Dent  ┬──┬◡ﾉ(° -°ﾉ)   https://anticdent.org/
freenode: cdent tw: @anticdent__
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] [api-wg][all] API-WG Liaison Update request

[Ravi, Goutham]

Hey Ed,

I’m listed as a API WG liaison to manila. Alex Meade has moved on from his 
OpenStack involvement. I’m however continuing my involvement; my meeting 
participation has been bleak, I’m mostly reading scroll back because of a time 
conflict.

Thanks,
Goutham Pacha Ravi 

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

Date: Tuesday, April 25, 2017 at 8:19 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [api-wg][all] API-WG Liaison Update request

An important step in the process of creating API guidelines is getting feedback 
from the projects that will be affected by those guidelines before we approve 
them. To that end, we have encouraged projects to appoint a liaison, and when a 
guideline is approved by the WG, these liaisons are added to the review, and 
thus receive an email from Gerrit, which ideally should result in the liaisons 
reviewing the proposed change to either approve or express whatever concern 
they may have. Only when we have buy-in from the liaisons do we go ahead and 
merge the guideline.

That has worked reasonably well, but lately there have been some concerns. One 
such concern is that many of the liaisons may no longer be in the same position 
they were when they signed up. If that is the situation for you, please let me 
know so we can update our list and start looking for someone else to represent 
your project. We also don’t have a way to directly contact liaisons except 
through Gerrit, and that is not ideal. So we’d like to update the liaison list 
[0] with the email address for each liaison, so that we can reach out to you 
when needed. I’ve included a list of the current liaisons
below my sig.

So if you are a liaison, please reply to me (off-list, to reduce spam) with 
your project, whether you are able to continue in the liaison role, and your 
email address. I will update the official list, and then start the process of 
finding replacements for those who have moved on.

[0] http://specs.openstack.org/openstack/api-wg/liaisons.html

-- Ed Leafe

Barbican: Douglas Mendizábal
Ceilometer: Chris Dent
Cinder: Scott DAngelo
Congress: Masahito Muroi
Designate: 
Glance: Stuart McLaren
Glance: Nikhil Komawar
Heat: Ryan Brown
Horizon: Cindy Lu
Ironic: Vladyslav Drok
Keystone: David Stanek
MagnetoDB: Ilya Sviridov
Magnum: Eli Qiao
Magnum: Hua Wang
Manila: Alex Meade
Manila: Goutham Pacha Ravi
Mistral: Renat Akhmerov
Murano: Nikolay Starodubtsev
Neutron: Henry Gessau
Nova: Matthew Gilliard
Nova: Alex Xu
Rally: 
Sahara: Michael McCune
Senlin: Qiming Teng
Swift: John Dickinson
Trove: Peter Stachowski
Trove: Amrith Kumar
Tripleo: 
Zaqar: Fei Long Wang

__
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] project on-board schedule

[Kendall Nelson]

Hello Joe,

I can offer TriCircle a lunch slot on Wednesday from 12:30-1:50?

-Kendall


On Tue, Apr 25, 2017 at 4:08 AM joehuang  wrote:

> Hi,
>
> Thank you Tom, I found that the on-boarding session of Tricircle [1] is
> overlapping with my talk{2]:
>
> [1]
> https://www.openstack.org/summit/boston-2017/summit-schedule/events/18693/tricircle-project-onboarding
> [2]
> https://www.openstack.org/summit/boston-2017/summit-schedule/events/18076/when-one-cloud-is-not-enough-an-overview-of-sites-regions-edges-distributed-clouds-and-more
>
> Is there any other project can help us to exchange the on-boarding
> session? Thanks a lot, I just find the issue.
>
> Best Regards
> Chaoyi Huang (joehuang)
>
> 
> From: Tom Fifield [t...@openstack.org]
> Sent: 25 April 2017 16:50
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] project on-board schedule
>
> On 25/04/17 16:35, joehuang wrote:
> > Hello,
> >
> > Where can I find the project on-board schedule in OpenStack Boston
> > summit? I haven't found it yet, and maybe I missed some mail. Thanks a
> lot.
>
> It's listed on the main summit schedule, under the Forum :)
>
> Here's a direct link to the Forum category:
>
> https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146
>
>
> __
> 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] [neutron][networking-vpp]networking-vpp for VPP 17.04 is available

[Ian Wells]

In conjunction with the release of VPP 17.04, I'd like to invite you all to
try out networking-vpp for VPP 17.04.  VPP is a fast userspace forwarder
based on the DPDK toolkit, and uses vector packet processing algorithms to
minimise the CPU time spent on each packet and maximise throughput.
networking-vpp is a ML2 mechanism driver that controls VPP on your control
and compute hosts to provide fast L2 forwarding under Neutron.

This version has a few additional features:
- resync - this allows you to upgrade the agent while packets continue to
flow through VPP, and to update VPP and get it promptly reconfigured, and
should mean you can do maintenance operations on your cloud with little to
no network service interruption (per NFV requirements)
- VXLAN GPE - this is a VXLAN overlay with a LISP-based control plane to
provide horizontally scalable networking with L2FIB propagation.  You can
also continue to use the standard VLAN and flat networking.
- L3 support - networking-vpp now includes a L3 plugin and driver code
within the agent to use the L3 functionality of VPP to provide Neutron
routers.

Along with this, there have been the usual bug fixes, code and test
improvements.

The README [1] explains how you can try out VPP using devstack, which is
even simpler than before the devstack plugin will deploy etcd, the
mechanism driver and VPP itself and should give you a working system with a
minimum of hassle.

We will continuing development between now and VPP's 17.07 release in
July.  There are several features we're planning to work on (you'll find a
list in our RFE bugs at [2]), and we welcome anyone who would like to come
help us.

Everyone is welcome to join our new biweekly IRC meetings, every Monday
(including next Monday), 0900 PST = 1600 GMT.

[1]https://github.com/openstack/networking-vpp/blob/master/README.rst
-- 
Ian.
__
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] [scientific][nova][cyborg] Special Hardware Forum session

[Tim Bell]

I think there will be quite a few ops folk… I can promise at least one ☺

Blair and I can also do a little publicity in 
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18751/future-of-hypervisor-performance-tuning-and-benchmarking
 which is on Tuesday.

Tim

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

Date: Tuesday 25 April 2017 19:11
To: Blair Bethwaite , 
"openstack-dev@lists.openstack.org" , 
openstack-operators 
Cc: Matthew Riedemann , huangzhipeng 

Subject: Re: [openstack-dev] [scientific][nova][cyborg] Special Hardware Forum 
session


I know that some cyborg folks and nova folks are planning to be there. Now we 
need to drive some ops folks.


Sent from HUAWEI AnyOffice
From:Blair Bethwaite
To:openstack-dev@lists.openstack.org,openstack-oper.
Date:2017-04-25 08:24:34
Subject:[openstack-dev] [scientific][nova][cyborg] Special Hardware Forum 
session

Hi all,

A quick FYI that this Forum session exists:
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18803/special-hardware
(https://etherpad.openstack.org/p/BOS-forum-special-hardware) is a
thing this Forum.

It would be great to see a good representation from both the Nova and
Cyborg dev teams, and also ops ready to share their experience and
use-cases.

--
Cheers,
~Blairo

__
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] [scientific][nova][cyborg] Special Hardware Forum session

[Rochelle Grober]

I know that some cyborg folks and nova folks are planning to be there. Now we 
need to drive some ops folks.


Sent from HUAWEI AnyOffice
From:Blair Bethwaite
To:openstack-dev@lists.openstack.org,openstack-oper.
Date:2017-04-25 08:24:34
Subject:[openstack-dev] [scientific][nova][cyborg] Special Hardware Forum 
session

Hi all,

A quick FYI that this Forum session exists:
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18803/special-hardware
(https://etherpad.openstack.org/p/BOS-forum-special-hardware) is a
thing this Forum.

It would be great to see a good representation from both the Nova and
Cyborg dev teams, and also ops ready to share their experience and
use-cases.

--
Cheers,
~Blairo

__
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] [neutron] neutron-lib impact: neutron.callbacks moved to neutron-lib

[Boden Russell]

If you work on a neutron sub-project that uses neutron.callbacks, please
read on. If not, it's probably safe to discard this message.

We've been talking about it for awhile, but it's finally coming to
fruition; we're transitioning over to neutron-lib's callbacks.

To ease sync issues across projects, we've taken a happy-path approach
that stages the transition as described in the commit message of [1].

Suggested per-project actions:
- If you're a stadium project, you're likely already covered [2]. Just
help shepherd the patch through review and ensure there's no issues.
- If not and your project uses neutron.callbacks, consider moving over
to neutron-lib's callbacks in the near future. You can use the work in
[2] as reference.

Once we get projects moved over to neutron-lib's callbacks we'll be
deleting the neutron.callbacks package all together. We can discuss when
the "right time" is for this during our weekly neutron meeting.

Thanks

[1] https://review.openstack.org/#/c/439146/
[2]
https://review.openstack.org/#/q/message:%22+consume+neutron-lib+callbacks%22

__
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] [Openstack][Neutron]Why we use secuirity group which only support dispatching whiltelist rules?

[Gary Kotton]

Hi,
I would like us to think of considering enabling an API that would allow 
‘deny’, for example an admin could overwrite a tenant’s security groups. For 
example, and admin may not want a specific source range to access the tenants 
VM’s. The guys working on FWaaS say that this may happen in V2, but that looks 
very far away. Making this change in Neutron would be pretty simple and give us 
a nice feature add. 
If you would like to work on this I would be happy to develop this with you. It 
could be added an extension.
Thanks
Gary

On 4/24/17, 6:37 AM, "Ihar Hrachyshka"  wrote:

All traffic is denied by default. OpenStack security groups API is
modeled to reflect what AWS does. You may find your needs better
served by fwaas plugin for neutron that is not constrained by AWS
compatibility.

Ihar

On Sun, Apr 23, 2017 at 8:33 PM, 田明明  wrote:
> Can we add an "action" to security group rule api, so that we could 
dispatch
> rules with "deny" action? Until now， security group only supports add
> white-list rules but this couldn't satisfy many people's needs.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> __
> 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] [scientific][nova][cyborg] Special Hardware Forum session

[Blair Bethwaite]

Hi all,

A quick FYI that this Forum session exists:
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18803/special-hardware
(https://etherpad.openstack.org/p/BOS-forum-special-hardware) is a
thing this Forum.

It would be great to see a good representation from both the Nova and
Cyborg dev teams, and also ops ready to share their experience and
use-cases.

-- 
Cheers,
~Blairo

__
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][all] API-WG Liaison Update request

[Edward Leafe]

An important step in the process of creating API guidelines is getting feedback 
from the projects that will be affected by those guidelines before we approve 
them. To that end, we have encouraged projects to appoint a liaison, and when a 
guideline is approved by the WG, these liaisons are added to the review, and 
thus receive an email from Gerrit, which ideally should result in the liaisons 
reviewing the proposed change to either approve or express whatever concern 
they may have. Only when we have buy-in from the liaisons do we go ahead and 
merge the guideline.

That has worked reasonably well, but lately there have been some concerns. One 
such concern is that many of the liaisons may no longer be in the same position 
they were when they signed up. If that is the situation for you, please let me 
know so we can update our list and start looking for someone else to represent 
your project. We also don’t have a way to directly contact liaisons except 
through Gerrit, and that is not ideal. So we’d like to update the liaison list 
[0] with the email address for each liaison, so that we can reach out to you 
when needed. I’ve included a list of the current liaisons   below my sig.

So if you are a liaison, please reply to me (off-list, to reduce spam) with 
your project, whether you are able to continue in the liaison role, and your 
email address. I will update the official list, and then start the process of 
finding replacements for those who have moved on.

[0] http://specs.openstack.org/openstack/api-wg/liaisons.html 


-- Ed Leafe

Barbican: Douglas Mendizábal
Ceilometer: Chris Dent
Cinder: Scott DAngelo
Congress: Masahito Muroi
Designate: 
Glance: Stuart McLaren
Glance: Nikhil Komawar
Heat: Ryan Brown
Horizon: Cindy Lu
Ironic: Vladyslav Drok
Keystone: David Stanek
MagnetoDB: Ilya Sviridov
Magnum: Eli Qiao
Magnum: Hua Wang
Manila: Alex Meade
Manila: Goutham Pacha Ravi
Mistral: Renat Akhmerov
Murano: Nikolay Starodubtsev
Neutron: Henry Gessau
Nova: Matthew Gilliard
Nova: Alex Xu
Rally: 
Sahara: Michael McCune
Senlin: Qiming Teng
Swift: John Dickinson
Trove: Peter Stachowski
Trove: Amrith Kumar
Tripleo: 
Zaqar: Fei Long Wang

__
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] [gnocchi] Moving python-gnocchiclient to GitHub

[Julien Danjou]

Hi,

We're in the process of moving python-gnocchiclient to GitHub. The
patches are up for review:

  https://review.openstack.org/#/c/459748/

and its dependencies need to be merged before this happen. As soon as
this patch is merged, the repository will officially be available at:

  https://github.com/gnocchixyz/python-gnocchiclient

Cheers,
-- 
Julien Danjou
// Free Software hacker
// https://julien.danjou.info


signature.asc
Description: PGP 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

[openstack-dev] [ptls][doc] Doc CPL update

[Alexandra Settle]

Hi everyone,

In light of the unfortunate news with OSIC, the documentation team has been hit 
pretty hard. As a result, we need more than ever for our documentation liaisons 
to step up and help us out.

However, looking at this list[1] it is unfortunately clear that a lot of people 
listed are a part of the OSIC work.

If your name is on this list, and you are unable to continue your role as 
documentation liaison for Pike, please contact the PTL of your project to 
arrange for there to be a new representative.

PTLs – could you please help us out and make sure there is a new assigned 
liaison to the role so that we don’t have any issues when it comes to release 
time.

Thank you to everyone for your cooperation during this difficult time.

Alex

[1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation
__
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] Monasca with out openstack

[Shah Zaib]

Hi all,

I want to install the monsaca with out openstack.

for the alternative of  keystone, i want to use the openladap.

but i didn't find any configuration and any help on web.

any thoughts and suggestions on this ??



Best Regards
 *Shahzaib*
__
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] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

[Alexandra Settle]

On 4/25/17, 3:40 AM, "Emilien Macchi"  wrote:

On Fri, Mar 24, 2017 at 11:35 AM, Emilien Macchi  wrote:
> On Wed, Mar 22, 2017 at 2:25 PM, Emilien Macchi  
wrote:
>> Thanks to these who volunteered, it's appreciated.
>>
>> I'm going to kick-off initial work here:
>>
>> 1. Create CI job that build deploy-guide on tripleo-docs repo (when
>> required) - https://review.openstack.org/448740
>
> Step 1 done.
>
>> 2. In tripleo-docs, modify tox.ini and create initial structure for
>> deployment guide (I'll kick it off once we have the CI job)
>
> Step 2, done and ready for review: 
https://review.openstack.org/#/c/449684/
>
>> 3. Start moving deployment related bits from doc/source/ to
>> deploy-guide/source/ (I'll need your help for this step). We also need
>> to include Alexendra and her team to make sure we're moving the right
>> bits.
>
> Keep posted, that will be the next step.

So this step is ready now, since we have the directory in place:
https://github.com/openstack/tripleo-docs/tree/master/deploy-guide/source

I would need some help and feedback on the bits that we're going to move:

* what chapters do we want to move? (related to Deployment)
* how do we handle redirection from old URLs (to keep web search valid
until it's indexed again)

Redirection can be handled in multiple ways. You can look at doing what the 
kolla team did and not move it at all, but rather, use ‘includes’. For example: 
https://github.com/openstack/kolla-ansible/blob/master/deploy-guide/source/quickstart.rst
 

However, I would personally not recommend this action. Simply because if you 
are planning to have a deployment guide, I would recommend you commit to this 
action so there is one source of truth when people are looking for the guide 
itself. The OpenStack-Ansible team ‘created’ a new deployment guide, and moved 
most of their install content across. The team then linked to the Deployment 
Guide on their docs.o.o/dev page. You can see that here: 
https://docs.openstack.org/developer/openstack-ansible/ 

It is entirely up to the TripleO team what they intend to do here. But there 
are options, basically. There will be broken links without, we recommend 
implementing this method: 
https://docs.openstack.org/contributor-guide/project-deploy-guide.html#deployment-guide-and-installation-guide-links
 

>> 4. Expose TripleO deployment guide to deployment guides front page and
>> drink a gin tonic.

I haven't figured yet how to expose the guide to the frontpage but
maybe Alexandra or someone from Docs team can help. It's unclear to me
how to handle that since we have a branchless doc repo, so we would
likely have a versionless documentation link (and handle
version-specific bits inline).

I don’t think the versioning should matter so much here. We will not version 
your guides, and if you do not, there is no problem. To ‘publish’ the guides, 
you need to add your deployment guide to our www/project-deploy-guide/draft 
file. See here: 
https://github.com/openstack/openstack-manuals/blob/master/www/project-deploy-guide/draft/index.html
 Also for Ocata: 
https://github.com/openstack/openstack-manuals/blob/master/www/project-deploy-guide/ocata/index.html
 

Again, any help is welcome. It would be great to achieve this goal in
Pike: having an official TripleO deployment guide among other
deployment tools guides.

Hopefully this helps a bit ( ping me if you have any questions/concerns.

Thanks,

>> I'll give an update when 2. is done so we can start working on the 
content.
>>
>> Thanks,
>>
>> On Wed, Mar 22, 2017 at 8:22 AM, Flavio Percoco  
wrote:
>>> On 20/03/17 08:01 -0400, Emilien Macchi wrote:

 I proposed a blueprint to track the work done:

 https://blueprints.launchpad.net/tripleo/+spec/tripleo-deploy-guide
 Target: pike-3

 Volunteers to work on it with me, please let me know.
>>>
>>>
>>> It'd be awesome to have some input from the containers squad on this 
effort
>>> too.
>>> Put me on the list for now while we find another volunteer in the 
containers
>>> DFG.
>>>
>>> Flavio
>>>
 Thanks,

 On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle 

 wrote:
>
> Hey Emilien,
>
> You pretty much covered it all! Docs team is happy to provide 
guidance,
> but in reality, it should be a fairly straight forward process.
>
> The Kolla team just completed their deploy-guide patches and were 
able to
> help refine the process a bit further. Hopefully this should help the
> TripleO team :)
>
> Reach out if you have any questions at 

Re: [openstack-dev] [vitrage] about "is_admin" in ctx

[Weyl, Alexey (Nokia - IL/Kfar Sava)]

Hi Wenjuan,

This is a good question, I need to check it a bit more thoroughly.

It’s just that at the moment we are preparing for the Boston Openstack Summit 
and thus it will take me a bit more time to answer that.

Sorry for the delay.

Alexey ☺

From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn]
Sent: Friday, April 21, 2017 11:08 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [vitrage] about  "is_admin" in ctx


Hi all,

I'm a little confused about the "is_amdin" in ctx.

From the 
hook(https://github.com/openstack/vitrage/blob/master/vitrage/api/hooks.py#L73),
 "is_admin" means admin user,.

But we define the macro as "admin project"( 
https://github.com/openstack/vitrage/blob/master/vitrage/api_handler/apis/base.py#L94
 ). But in my opinion,  it should be the admin role. Correct me if i'm wrong :).



BR,

dwj






__
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] [Forum] Unanswered Requirements

[Melvin Hillsman]

Hey everyone,

I would like to take the opportunity to open the discussion up for feedback
from the community leading into the Boston Forum.

*Session Description*: Collaborate/communicate around user stories, gap
analysis, what fits in the current state of tech, prioritize what would
have the greatest impact in reducing pain for users. Ideally we would like
to discuss in this session successes and failures of the current state of
our feedback loop. We should be able to identify patterns that fit within a
larger system/process that we are able to iterate through as the way to get
user requirements implemented into code. [1]

Moving the conversation forward is the aim with the ultimate goal being the
first iteration of a plan that can be implemented, and one that gathers
data/insight consistently to make specific and relevant improvements.

[1] https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646

Learner | Ideation | Belief | Responsibility | Command
__
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] OpenStack Kolla-Kubernetes Workshop: Demystifying the Gate - video conferencing information

[sasi kiran]

Thank you Steven,

I'll try webex audio then

BR,
Sasikiran

On 25-Apr-2017 10:18 AM, "Steven Dake (stdake)"  wrote:

> Sasikiran,
>
>
>
> Webex audio is sufficient for me – this is what I use all the time.  A
> headset helps, however.
>
>
>
> For those that must dial in, the global dial-in is here:
> https://cisco.webex.com/cmp3200/webcomponents/widget/
> globalcallin/globalcallin.do?serviceType=MC=MC&
> serviceType=MC=MC=383520252=383520252=
> 383520252=383520252=1=1&
> tollFree=1=1=ciscosales=ciscosales&
> siteurl=ciscosales=globalcallin.php=
> globalcallin.php=globalcallin.php=
> false=false=false=2015755778=2015755778=
> 2015755778=cmp3200=cmp3200=/
> webcomponents/widget/globalcallin/gcnredirector.do&
> actname=/webcomponents/widget/globalcallin/gcnredirector.do=0
>
> Those are listed as “toll” # ‘s but some may be local to you.
>
>
>
> Regards
>
> -steve
>
>
>
>
>
>
>
>
>
> *From: *sasi kiran 
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" 
> *Date: *Monday, April 24, 2017 at 6:56 AM
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> *Subject: *Re: [openstack-dev] [kolla] OpenStack Kolla-Kubernetes
> Workshop: Demystifying the Gate - video conferencing information
>
>
>
> Hi,
>
> I'm interested to join for this session.
>
> Could you please let us know if there is any tollfree number inorder to
> call from India & Hungary or joining webex is sufficient enough for audio
> even?
>
> BR,
>
> Sasikiran
>
>
>
> On Sun, Apr 23, 2017 at 2:59 AM, Steven Dake (stdake) 
> wrote:
>
> As proposed earlier on the mailing list, A 2 week 6 session workshop has
> been organized From April 25th – May 4th Tu/W/Th for 45 minutes in length.
>
>
>
> The agenda for this workshop is as follows:
>
>
>
> Learn how OpenStack’s kolla-kubernetes gating functions to enable yourself
> to contribute more effectively to kolla-kubernetes.  This workshop will run
> for two weeks on Tuesday, Wednesday and Thursday for 45 minutes beginning
> April 25th, 2017 and concluding May 4th, 2017 via Webex.  There is no
> need to actually have a camera; the only purpose of the video conferencing
> is to share a screen.  The workshop will be recorded.
>
>
>
> Connection details are below:
>
>
>
> I am using Webex for this video conferencing session.  Webex now supports
> Windows, Mac, and Linux.  To connect via Linux, use the web based version
> of Webex (not the client).  For those that can’t install a client, the web
> based version should meet your organization’s security requirements.
>
>
>
> If your struggling to join the meeting, please join #openstack-kolla and
> speak up there.
>
>
>
> Regards
>
> -stevve
>
>
>
> *OpenStack Kolla-Kubernetes Workshop: Demystifying the Gate*
>
> Every Tuesday, Wednesday, Thursday, from Tuesday, April 25, 2017, to
> Thursday, May 4, 2017
>
> 17:00 UTC | 45 minutes
>
>
>
> https://cisco.webex.com/ciscosales/j.php?MTID=
> m726d1915a1fa61470a810c9c9b01a4ef
>
>
>
> Meeting number:
>
> 202 310 134
>
> Meeting password:
>
> openstack (67367822 from phones)
>
>
>
>
>
> *Join by phone*
>
> *+1-866-432-9903 <(866)%20432-9903>* Call-in toll-free number (US/Canada)
>
> *+1-408-525-6800 <(408)%20525-6800>* Call-in toll number (US/Canada)
>
> Access code: 202 310 134
>
> Global call-in numbers
> 
>   |  Toll-free calling restrictions
> 
>
>
>
>
>
>
>
> Add this meeting
> 
>  to your calendar. (Cannot add from mobile devices.)
>
>
>
>
>
>
> __
> 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] project on-board schedule

[joehuang]

Hi, 

Thank you Tom, I found that the on-boarding session of Tricircle [1] is 
overlapping with my talk{2]:

[1] 
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18693/tricircle-project-onboarding
[2] 
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18076/when-one-cloud-is-not-enough-an-overview-of-sites-regions-edges-distributed-clouds-and-more

Is there any other project can help us to exchange the on-boarding session? 
Thanks a lot, I just find the issue.

Best Regards
Chaoyi Huang (joehuang)


From: Tom Fifield [t...@openstack.org]
Sent: 25 April 2017 16:50
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] project on-board schedule

On 25/04/17 16:35, joehuang wrote:
> Hello,
>
> Where can I find the project on-board schedule in OpenStack Boston
> summit? I haven't found it yet, and maybe I missed some mail. Thanks a lot.

It's listed on the main summit schedule, under the Forum :)

Here's a direct link to the Forum category:

https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146


__
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] project on-board schedule

[Tom Fifield]

On 25/04/17 16:35, joehuang wrote:

Hello,

Where can I find the project on-board schedule in OpenStack Boston
summit? I haven't found it yet, and maybe I missed some mail. Thanks a lot.


It's listed on the main summit schedule, under the Forum :)

Here's a direct link to the Forum category:

https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146


__
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] project on-board schedule

[joehuang]

Hello,

Where can I find the project on-board schedule in OpenStack Boston summit? I 
haven't found it yet, and maybe I missed some mail. Thanks a lot.

Best Regards
Chaoyi Huang (joehuang)
__
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] Owners needed for approved but orphaned OSIC blueprints

[John Garbutt]

Hi,

Matt, thanks for pulling that list together.

I have context on most of those, if people would like to take those on.
I hope to review most of those an clarify where everything is at.

I am going to take a look at where we are at with policy stuff first.

Thanks,
johnthetubaguy

On 24 April 2017 at 22:45, Matt Riedemann  wrote:
>
> Hi everyone,
>
> With the recent unfortunate news about OSIC ending abruptly and several Nova 
> developers no longer being able to work on the project, I wanted to go over 
> the list of blueprints which were approved for Pike and which now no longer 
> have an owner. I am starting this thread to look for owners for each 
> blueprint. If you have questions about picking one up but you're maybe too 
> shy to ask questions about it in the mailing list, feel free to email me 
> directly or send me a private message in IRC. The list is in no particular 
> order.
>
> * 
> https://blueprints.launchpad.net/nova/+spec/live-migration-per-instance-timeout
>
> This is not started but there is a spec with the design.
>
> * https://blueprints.launchpad.net/nova/+spec/remove-discoverable-policy-rules
>
> This is not started but is a specless blueprint that is straight-forward.
>
> * https://blueprints.launchpad.net/nova/+spec/remove-nova-cert
>
> This is not started but should be pretty straightforward, and has a spec with 
> the details.
>
> * https://blueprints.launchpad.net/nova/+spec/ironic-rescue-mode
>
> The nova side of this is dependent on Ironic changes which were owned by OSIC 
> developers. So the nova blueprint is effectively blocked now.
>
> * https://blueprints.launchpad.net/nova/+spec/live-migrate-rescued-instances
>
> This is started, and was picked up from some work started by HPE in previous 
> releases. I'm not sure what state it is in however.
>
> * https://blueprints.launchpad.net/nova/+spec/policy-docs
>
> Most of this is done. There might be a few more non-discoverable policy rules 
> that need documentation, but I haven't gone through what's left in detail yet.
>
> * 
> https://blueprints.launchpad.net/nova/+spec/prep-for-network-aware-scheduling-pike
>
> I'm not sure if John is going to continue trying to work on this or not yet, 
> but I think it would probably be good to get a helping hand here regardless 
> as it's stalled since Newton (really due to lack of reviews).
>
> * https://blueprints.launchpad.net/nova/+spec/use-service-tokens-pike
>
> This was started and made progress in Ocata but needs someone to take over 
> the remaining changes. This overlaps somewhat with 
> https://blueprints.launchpad.net/nova/+spec/use-service-catalog-for-endpoints.
>
> * https://blueprints.launchpad.net/nova/+spec/centralize-config-options-pike
>
> This is an ongoing multi-contributor effort. Stephen Finucane would be a good 
> organizer here if no one else is interested in formally "owning" it.
>
> * 
> https://blueprints.launchpad.net/nova/+spec/live-migration-force-after-timeout
>
> This has been started but needs work. There is also a spec for the design.
>
> --
>
> If you are interested in owning one of these, please reply so I and others 
> know, or contact me privately.
>
> --
>
> Thanks,
>
> Matt
>
> __
> 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] OpenStack Kolla-Kubernetes Workshop: Demystifying the Gate - video conferencing information

[Steven Dake (stdake)]

Sasikiran,

Webex audio is sufficient for me – this is what I use all the time.  A headset 
helps, however.

For those that must dial in, the global dial-in is here: 
https://cisco.webex.com/cmp3200/webcomponents/widget/globalcallin/globalcallin.do?serviceType=MC=MC=MC=MC=383520252=383520252=383520252=383520252=1=1=1=1=ciscosales=ciscosales=ciscosales=globalcallin.php=globalcallin.php=globalcallin.php=false=false=false=2015755778=2015755778=2015755778=cmp3200=cmp3200=/webcomponents/widget/globalcallin/gcnredirector.do=/webcomponents/widget/globalcallin/gcnredirector.do=0
Those are listed as “toll” # ‘s but some may be local to you.

Regards
-steve




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

Date: Monday, April 24, 2017 at 6:56 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [kolla] OpenStack Kolla-Kubernetes Workshop: 
Demystifying the Gate - video conferencing information

Hi,
I'm interested to join for this session.
Could you please let us know if there is any tollfree number inorder to call 
from India & Hungary or joining webex is sufficient enough for audio even?
BR,
Sasikiran

On Sun, Apr 23, 2017 at 2:59 AM, Steven Dake (stdake) 
> wrote:
As proposed earlier on the mailing list, A 2 week 6 session workshop has been 
organized From April 25th – May 4th Tu/W/Th for 45 minutes in length.

The agenda for this workshop is as follows:

Learn how OpenStack’s kolla-kubernetes gating functions to enable yourself to 
contribute more effectively to kolla-kubernetes.  This workshop will run for 
two weeks on Tuesday, Wednesday and Thursday for 45 minutes beginning April 
25th, 2017 and concluding May 4th, 2017 via Webex.  There is no need to 
actually have a camera; the only purpose of the video conferencing is to share 
a screen.  The workshop will be recorded.

Connection details are below:

I am using Webex for this video conferencing session.  Webex now supports 
Windows, Mac, and Linux.  To connect via Linux, use the web based version of 
Webex (not the client).  For those that can’t install a client, the web based 
version should meet your organization’s security requirements.

If your struggling to join the meeting, please join #openstack-kolla and speak 
up there.

Regards
-stevve

OpenStack Kolla-Kubernetes Workshop: Demystifying the Gate

Every Tuesday, Wednesday, Thursday, from Tuesday, April 25, 2017, to Thursday, 
May 4, 2017

17:00 UTC | 45 minutes

https://cisco.webex.com/ciscosales/j.php?MTID=m726d1915a1fa61470a810c9c9b01a4ef


Meeting number:

202 310 134

Meeting password:

openstack (67367822 from phones)



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: 202 310 134

Global call-in 
numbers
  |  Toll-free calling 
restrictions





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




__
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] [nova] Compute Node restart

[Ajay Kalambur (akalambu)]

Hi
I see that when a host is gracefully rebooted nova-compute receives a lifecycle 
event to shutdown the instance and it updates the database with the state set 
to SHUTOFF.
Now when compute node reboot and libvirt brings the VM back up nova checks its 
database and issues stop api and hence shuts down the VM

So even though resume guest state on reboot is set it does not work. Why does 
nova compute ignore the lifecycle event from libvirt saying bring up the VM and 
reconciles with database


How do we ensure Vms come back up on a graceful reboot

Note on a non graceful reboot libvirt does not send any lifecycle event to nova 
and hence nova database always shows the VM in Running State

This is with Newton code base of nova


Ajay

__
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] [tricircle]poll for new weekly meeting time

[Yipei Niu]

Wed  UTC 01:00, Beijing 9:00 AM, PDT(-1 day) 6:00 PM +1.

Best regards,
Yipei
__
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